Event notification method, device and system

Abstract

The embodiments of the present application disclose an event notification method, device and system, which relate to the field of communication technology. When UPF (PSA) reselection occurs, the corresponding event report can be obtained without the application server reissuing the event subscription information, thereby reducing the acquisition delay of the event report. The specific scheme is: receiving first information and second information, the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the destination address for receiving the event notification information. The second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. Select a first user plane network element corresponding to the first data network access identifier for the terminal device. Send third information and the first event notification address, wherein the third information is determined based on the second information.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular, to an event notification method, device and system. Background Art

[0002] In the current communication architecture (such as the fourth generation mobile communication or the fifth generation mobile communication), the terminal device can interact with the application server after accessing the network. During the interaction process, the application server can send event subscription information to the access network device (such as the user plane function (UPF)) connected to the terminal device to collect some data (including business-related data and business-irrelevant data) during the communication process between the terminal device and the corresponding application server, thereby providing better communication services.

[0003] In the fifth generation mobile networks (5G), the terminal device is the user equipment (UE), and the event subscribed by the application server can be the quality of service (QoS) monitoring information. Figure 1 As shown, the application server can send the QoS monitoring request information for the UE to the UPF through the application function (AF), policy control function (PCF), and session management function (SMF). The UPF can obtain the QoS monitoring event report during the communication with the UE based on the QoS monitoring request information, and feed back the QoS monitoring event report to the AF. Among them, the UPF can return the QoS monitoring event report through the path of receiving the QoS monitoring request information, that is, the UPF sends the QoS monitoring event report to the corresponding application server through the SMF, PCF and AF. In order to save the delay of UPF returning the QoS monitoring event report, the UPF can also directly send the QoS monitoring event report through the following Figure 1 The dashed arrow shown is sent to the AF. It should be noted that, generally speaking, when the UPF performs event subscription detection such as QoS monitoring, the corresponding UE is the UE that establishes a protocol data unit (PDU) session with the UPF.

[0004] UE is often in a mobile state, and as the UE moves, the UPF may be reselected. In this way, when the application server needs to obtain the event report corresponding to the event subscription during the communication between the UPF and the UE, it needs to re-send the event subscription information to the reselected UPF through the AF, PCF, and SMF. This also results in the application server being unable to quickly obtain the event report corresponding to the monitoring information. Summary of the invention

[0005] The present application provides an event notification method, device and system, which can obtain the corresponding event report without the application server reissuing event subscription information when UPF (PSA) reselection occurs due to terminal device movement, thereby reducing the delay in obtaining the event report and reducing the system's signaling overhead.

[0006] In order to achieve the above objectives, this application adopts the following technical solutions:

[0007] In a first aspect, an event notification method is provided, the method comprising: sending first information and second information, the first information comprising at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier being used to indicate the location of an application server of an application, the event notification address being a destination address for receiving event notification information, the destination address being an address of a local capability exposure network element corresponding to the application or an address of an application function (AF). The second information is used to subscribe to a first event of a terminal device, the terminal device being a device accessing the application server of the application. Based on the scheme, the application server can send a corresponding relationship including a data network access identifier and a corresponding event notification address through the AF. The application server can also send event subscription information through the AF. Thus, when the UPF is reselected, other network elements (such as SMF) can determine the event subscription address corresponding to the new PSA according to the latest PSA and the above-mentioned corresponding relationship, so that the application server does not need to send the event subscription information through the AF again, thereby significantly reducing the delay and streamlining the signaling overhead of the system in the process of repeatedly sending the event subscription information. It should be noted that, in different implementations, the application server may send the above correspondence relationship and event subscription information through the same AF, or may send the above correspondence relationship and event subscription information through different AFs.

[0008] In a possible design, the second information also includes: a notification association identifier, which is used to associate the event notification information of the first event with the first information. Based on this solution, the AF can also send down the related contact information (such as the first notification association information) corresponding to the event subscription information, so that when the UPF reports the event report, it can also feed back the notification association information to the application server. So that the application server can determine the association between the event report and the sent event subscription information based on the association information.

[0009] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information. Based on this scheme, an example of a specific second information is provided, that is, the second information can be information for making a QoS monitoring request, or information for a QoS notification control request, or information for a location request of a terminal device. It should be understood that QoS-related information is business-related information, while location request information is non-business-related information. Therefore, for other business information and non-business information, the above-mentioned first aspect and the scheme in its possible design can be used to realize event reporting and obtain corresponding beneficial effects, and therefore should also be included in the scope of protection of this application.

[0010] In a second aspect, an event notification device is provided, which includes: a determination unit and a sending unit. The determination unit is used to determine the first information and the second information, the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the destination address for receiving the event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function (AF). The second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. The sending unit is used to send the first information and the second information. As an example, the determination unit can specifically determine the specific content of the first information and the second information according to the instructions of the application server.

[0011] In one possible design, the second information also includes: a notification association identifier, which is used to associate event notification information of the first event with the first information.

[0012] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.

[0013] In a third aspect, an application function (AF) entity is provided, wherein the AF entity includes one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. When the one or more processors execute the computer instructions, the AF entity executes the event notification method as described in any one of the first aspect and possible designs thereof.

[0014] According to a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes computer instructions. When the computer instructions are executed, the event notification method as described in any one of the first aspect and possible implementations thereof is executed.

[0015] In a fifth aspect, a chip system is provided, the chip comprising a processing circuit and an interface. The processing circuit is used to call and run a computer program stored in a storage medium from a storage medium to execute an event notification method as described in any one of the first aspect and possible implementations thereof.

[0016] It should be understood that the solutions provided in the second, third, fourth and fifth aspects can all correspond to the first aspect or its possible designs, so the beneficial effects that can be obtained are similar and will not be repeated here.

[0017] In a sixth aspect, an event notification method is provided, the method comprising: receiving first information and second information, the first information comprising at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier being used to indicate the location of the application server of the application, the event notification address being the destination address for receiving the event notification information, the destination address being the address of the local capability open network element corresponding to the application or the address of the application function AF. The second information is used to subscribe to the first event of the terminal device, the terminal device being a device for accessing the application server of the application. Sending third information and the first information, wherein the third information is determined according to the second information and is used to subscribe to the first event. Based on the scheme, the core network element may receive the first information and the second information from the AF, and perform response processing thereon, so as to facilitate other network elements to perform response processing. Exemplarily, the core network element may be a PCF, the PCF may generate corresponding PCC rules according to the first information and the second information, and issue the PCC rules to other network elements (such as SMF). The PCC rules may include at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier (such as the first information), and third information for subscribing to the first event. The third information may be the same as the second information, or may be determined by the PCF based on the second information (e.g., the PCF performs transcoding and other processing on the content of the second information to obtain the third information). It should be noted that some events corresponding to the time subscription information correspond to terminal devices, so the PCC rule may also include identification information of the target terminal device. The identification information may be used to indicate a terminal device or a terminal device group.

[0018] In a possible design, the second information also includes: a notification association identifier, which is used to associate the event notification information of the first event with the first information, and the third information also includes a notification association identifier. Based on this solution, the AF can also send down the related contact information (such as the first notification association information) corresponding to the event subscription information, so that when the UPF reports the event report, it can also feed back the notification association information to the application server. So that the application server can determine the association between the event report and the sent event subscription information based on the association information.

[0019] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information. Based on this scheme, an example of a specific second information is provided, that is, the second information can be information for making a QoS monitoring request, or information for a QoS notification control request, or information for a location request of a terminal device. It should be understood that QoS-related information is business-related information, while location request information is non-business-related information. Therefore, for other business information and non-business information, the above-mentioned first aspect and the scheme in its possible design can be used to realize event reporting and obtain corresponding beneficial effects, and therefore should also be included in the scope of protection of this application.

[0020] In a seventh aspect, an event notification device is provided, the device comprising: a receiving unit and a sending unit. The receiving unit is used to receive first information and second information, the first information comprising at least one data network access identifier and an event notification address corresponding to at least one data network access identifier, the network access identifier is used to indicate the location of an application server of an application, and the event notification address is a destination address for receiving event notification information, and the destination address is an address of a local capability exposure network element corresponding to the application or an address of an application function AF. The second information is used to subscribe to a first event of a terminal device, and the terminal device is a device that accesses the application server of an application. The sending unit is used to send third information and the first information, wherein the third information is determined based on the second information and is used to subscribe to the first event.

[0021] In one possible design, the second information also includes: a notification association identifier, the notification association identifier is used to associate the event notification information of the first event with the first information, and the third information also includes the notification association identifier.

[0022] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.

[0023] In an eighth aspect, a policy control function (PCF) entity is provided, wherein the PCF entity includes one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. When the one or more processors execute the computer instructions, the PCF entity executes the event notification method as described in any one of the sixth aspect and possible designs thereof.

[0024] In a ninth aspect, a computer-readable storage medium is provided, the computer-readable storage medium comprising computer instructions, which, when executed, execute an event notification method as described in any one of the sixth aspect and its possible implementation methods.

[0025] In a tenth aspect, a chip system is provided, the chip comprising a processing circuit and an interface. The processing circuit is used to call and run a computer program stored in a storage medium from a storage medium to execute an event notification method as described in any one of the sixth aspect and possible implementations thereof.

[0026] It should be understood that the solutions provided in the seventh, eighth, ninth and tenth aspects mentioned above can all correspond to the sixth aspect or its possible design, so the beneficial effects that can be obtained are similar and will not be repeated here.

[0027] In an eleventh aspect, an event notification method is provided, the method comprising: receiving first information and second information, the first information comprising at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier being used to indicate the location of an application server of an application, the event notification address being a destination address for receiving event notification information, the destination address being an address of a local capability open network element corresponding to the application or an address of an application function AF. The second information is used to subscribe to a first event of a terminal device, the terminal device being a device accessing an application server of an application. Selecting a first user plane network element for the terminal device, the first user plane network element corresponding to a first data network access identifier, and at least one data network access identifier including the first data network access identifier. Sending third information and a first event notification address. The third information is determined according to the second information and is used to subscribe to the first event. The first event notification address is determined according to the first data network access identifier, at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier. Based on the scheme, the network element may receive information from other network elements and perform response processing. Exemplarily, the network element may be an SMF. The SMF may receive a PCC rule from a PCF, the PCC rule may include the first information and the second information. SMF can select the corresponding UPF as PSA for the terminal device according to the DNAI in the first information. Since SMF knows the correspondence between DNAI and the event notification address, SMF can also know the feedback address of the report corresponding to the event subscribed by the second information. SMF can send the third information corresponding to the event subscription information and the corresponding event notification address to UPF, so that UPF can obtain and feedback the event report accordingly. The third information can be determined according to the second information. In different embodiments, the third information can be the same as the second information or different from the second information.

[0028] In one possible design, a second event notification address is sent, and the second event notification address is the address of the local capability exposure network element corresponding to the first user plane network element. Based on this scheme, the SMF can also send the address of the NEF corresponding to the currently selected PSA to the UPF. Exemplarily, in general, if a local NEF is set in the system architecture, the NEF may correspond to the local AF. In some scenarios, the event report may need to be reported to other NEFs (such as the NEF in the central DC) first. Therefore, the SMF can send the address of the NEF to the UPF so that the UPF can report the event report to the correct address.

[0029] In a possible design, the second information also includes: a notification association identifier, which is used to associate the event notification information of the first event with the first information, and the third information also includes a notification association identifier. Based on this solution, the AF can also send down the related contact information (such as the first notification association information) corresponding to the event subscription information, so that when the UPF reports the event report, it can also feed back the notification association information to the application server. So that the application server can determine the association between the event report and the sent event subscription information based on the association information.

[0030] In one possible design, the method also includes: selecting a corresponding second user plane network element for a terminal device that accesses an application server of an application, the second user plane network element corresponding to a second data network access identifier, and at least one data network access identifier including a second data network access identifier. Sending a fourth message and a third event notification address. The fourth message is determined based on the second information and is used to subscribe to the first event. The third event notification address is determined based on the second data network access identifier, at least one data network access identifier, and an event notification address corresponding to at least one data network access identifier. Based on this scheme, when PSA reselection is required (such as when the terminal device moves), the SMF can select a new UPF as the PSA for the terminal device based on the DNAI in the PCC rule. The DNAI corresponding to the updated PSA has an updated event notification address, so the SMF can send the updated event notification address to the UPF after reselecting the PSA so that the UPF can report the event correctly based on the address.

[0031] In one possible design, the method also includes: sending a fourth event notification address, the fourth event notification address is the address of the local capability open network element corresponding to the second user plane network element. Based on this solution, a processing solution is provided when PSA reselection occurs. Exemplarily, when PSA is reselected, SMF can determine the reporting address (such as the fourth event notification address) of the event report after PSA reselection based on the DNAI corresponding to the reselected PSA. SMF can send the updated reporting address to the corresponding updated UPF, so that UPF can obtain the corresponding event report based on the event subscription information, and report the event report to the updated address.

[0032] In one possible design, the second information further includes: a notification association identifier, the notification association identifier is used to associate the event notification information of the first event with the first information, and the fourth information further includes the notification association identifier. Based on this solution, the SMF can send the corresponding notification association identifier when sending the updated event notification address, so that the application server can determine the association between the event report and the sent event subscription information based on the association information.

[0033] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information. Based on this scheme, an example of a specific second information is provided, that is, the second information can be information for making a QoS monitoring request, or information for a QoS notification control request, or information for a location request of a terminal device. It should be understood that QoS-related information is business-related information, while location request information is non-business-related information. Therefore, for other business information and non-business information, the above-mentioned first aspect and the scheme in its possible design can be used to realize event reporting and obtain corresponding beneficial effects, and therefore should also be included in the scope of protection of this application.

[0034] In a twelfth aspect, an event notification device is provided, the device comprising: a receiving unit and a sending unit. The receiving unit is used to receive first information and second information, the first information comprising at least one data network access identifier and an event notification address corresponding to at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the destination address for receiving the event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function AF. The second information is used to subscribe to a first event of a terminal device, and the terminal device is a device that accesses the application server of the application. A first user plane network element is selected for the terminal device, the first user plane network element corresponds to a first data network access identifier, and at least one data network access identifier includes the first data network access identifier. A sending unit is used to send third information and a first event notification address. The third information is determined according to the second information and is used to subscribe to the first event. The first event notification address is determined according to the first data network access identifier, at least one data network access identifier, and the event notification address corresponding to at least one data network access identifier.

[0035] In one possible design, the sending unit is also used to send a second event notification address, where the second event notification address is the address of a local capability exposure network element corresponding to the first user plane network element.

[0036] In one possible design, the second information also includes: a notification association identifier, the notification association identifier is used to associate the event notification information of the first event with the first information, and the third information also includes the notification association identifier.

[0037] In one possible design, the device also includes a configuration unit for selecting a corresponding second user plane network element for a terminal device of an application server accessing an application, the second user plane network element corresponding to a second data network access identifier, and at least one data network access identifier including the second data network access identifier. Send fourth information and a third event notification address. The fourth information is determined based on the second information and is used to subscribe to the first event. The third event notification address is determined based on the second data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.

[0038] In one possible design, the sending unit is also used to send a fourth event notification address, where the fourth event notification address is the address of the local capability opening network element corresponding to the second user plane network element.

[0039] In one possible design, the second information also includes: a notification association identifier, the notification association identifier is used to associate the event notification information of the first event with the first information, and the fourth information also includes the notification association identifier.

[0040] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.

[0041] In a thirteenth aspect, a session management function (SMF) entity is provided, the SMF entity comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. When the one or more processors execute the computer instructions, the SMF entity executes the event notification method as described in any one of the eleventh aspect and its possible designs.

[0042] In a fourteenth aspect, a computer-readable storage medium is provided, which includes computer instructions. When the computer instructions are executed, an event notification method as described in any one of the eleventh aspect and its possible implementation methods is executed.

[0043] In a fifteenth aspect, a chip system is provided, the chip comprising a processing circuit and an interface. The processing circuit is used to call and run a computer program stored in a storage medium from a storage medium to execute an event notification method as described in any one of the eleventh aspect and possible implementations thereof.

[0044] It should be understood that the solutions provided in the above-mentioned twelfth, thirteenth, fourteenth and fifteenth aspects can all correspond to the eleventh aspect or its possible design, so the beneficial effects that can be obtained are similar and will not be repeated here.

[0045] In the sixteenth aspect, an event notification method is provided, the method comprising: receiving first information, a first event notification address and a second event notification address, the first information being used to subscribe to a first event of a terminal device, the terminal device being a device for accessing an application server of an application. The first event notification address is a destination address for receiving event notification information of a first event, the destination address being the address of an application function AF corresponding to the application. The second event notification address is an address of a local capability open network element corresponding to a first user plane network element. A second information is sent to the first event notification address through the local capability open network element corresponding to the second event notification address, the second information including event notification information of the first event. Based on this scheme, the UPF can receive the first information from the SMF, and acquire an event report based on the first information, and then report the event report to the address indicated in the first information. It should be understood that since the first event notification address and the second event notification address obtained by UPF from the first information are the latest addresses determined by SMF, regardless of whether PSA reselection occurs, UPF can obtain the correct event notification address on the premise that AF does not repeatedly send event subscription information. As a result, UPF can smoothly report event reports on the premise that AF does not repeatedly send event subscription information.

[0046] In a possible design, the first information also includes: a notification association identifier, which is used to associate the event notification information of the first event with the event notification address, and the second information also includes a notification association identifier. Based on this solution, the AF can also send down the relevant contact information (such as the first notification association information) corresponding to the event subscription information, so that when the UPF reports the event report, it can also feed back the notification association information to the application server. So that the application server can determine the association between the event report and the sent event subscription information based on the association information.

[0047] In one possible design, the first information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information. Based on this scheme, an example of a specific second information is provided, that is, the second information can be information for making a QoS monitoring request, or information for a QoS notification control request, or information for a location request of a terminal device. It should be understood that QoS-related information is business-related information, while location request information is non-business-related information. Therefore, for other business information and non-business information, the above-mentioned first aspect and the scheme in its possible design can be used to realize event reporting and obtain corresponding beneficial effects, and therefore should also be included in the scope of protection of this application.

[0048] In the seventeenth aspect, an event notification device is provided, which may include a receiving unit and a sending unit. The receiving unit is used to receive first information, a first event notification address, and a second event notification address, the first information is used to subscribe to a first event of a terminal device, and the terminal device is a device for accessing an application server of an application. The first event notification address is a destination address for receiving event notification information of the first event, and the destination address is the address of an application function AF corresponding to the application. The second event notification address is the address of a local capability open network element corresponding to the first user plane network element. The sending unit is used to send second information to the first event notification address through the local capability open network element corresponding to the second event notification address, and the second information includes event notification information of the first event.

[0049] In one possible design, the first information also includes: a notification association identifier, where the notification association identifier is used to associate the event notification information of the first event with the event notification address, and the second information also includes the notification association identifier.

[0050] In one possible design, the first information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

[0051] In an eighteenth aspect, a user plane function UPF entity is provided, the UPF entity comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. When the one or more processors execute the computer instructions, the UPF entity performs the event notification method as described in any one of the sixteenth aspect and its possible worlds.

[0052] In a nineteenth aspect, a computer-readable storage medium is provided, which includes computer instructions. When the computer instructions are executed, an event notification method as described in any one of the sixteenth aspect and its possible implementation methods is executed.

[0053] In a twentieth aspect, a chip system is provided, the chip comprising a processing circuit and an interface. The processing circuit is used to call and run a computer program stored in a storage medium from a storage medium to execute an event notification method as described in any one of the sixteenth aspect and possible implementations thereof.

[0054] It should be understood that the solutions provided in the above-mentioned seventeenth aspect, eighteenth aspect, nineteenth aspect, and twentieth aspect can all correspond to the sixteenth aspect or its possible design, so the beneficial effects that can be obtained are similar and will not be repeated here.

[0055] In a twenty-first aspect, a communication system is provided, the system comprising: a first network element, a second network element, a third network element and a fourth network element. The first network element is used to send first information and second information, the first information includes at least one data network access identifier and an event notification address corresponding to at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the destination address for receiving the event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function AF. The second information is used to subscribe to a first event of a terminal device, and the terminal device is a device that accesses the application server of the application. The second network element is used to receive the first information and the second information. The third information and the first information are sent, wherein the third information is determined according to the second information and is used to subscribe to the first event. The third network element is used to receive the first information and the third information. A first user plane network element is selected for the terminal device, the first user plane network element corresponds to the first data network access identifier, and the at least one data network access identifier includes the first data network access identifier. The fourth information and the first event notification address are sent. The fourth information is determined according to the third information and is used to subscribe to the first event. The first event notification address is determined according to the first data network access identifier, at least one data network access identifier, and the event notification address corresponding to the at least one data network access identifier. The fourth network element is configured to receive fourth information and the first event notification address. Fifth information is sent to the first event notification address, and the fifth information includes event notification information of the first event.

[0056] In one possible design, the first network element is an AF network element, the second network element is a policy control function PCF network element, the third network element is a session management function SMF network element, and the fourth network element is a user plane function UPF network element.

[0057] It should be understood that the technical features of the communication system and its possible design provided in the above-mentioned twenty-first aspect can correspond to any method in the above-mentioned first aspect and its possible design, the sixth aspect and its possible design, the eleventh aspect and its possible design, and / or the sixteenth aspect and its possible design, and thus can achieve the same beneficial effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 A schematic diagram of a network architecture;

[0059] Figure 2 A logical schematic diagram of a communication architecture provided for an embodiment of the present application;

[0060] Figure 3 A schematic diagram of a communication architecture provided in an embodiment of the present application;

[0061] Figure 4A schematic diagram of another communication architecture provided in an embodiment of the present application;

[0062] Figure 5 A schematic diagram of another communication architecture provided in an embodiment of the present application;

[0063] Figure 5A A flowchart of an event notification method provided for an application embodiment;

[0064] Figure 6 A flowchart of another event notification method provided in an embodiment of the present application;

[0065] Figure 7 A flowchart of another event notification method provided in an embodiment of the present application;

[0066] Figure 8 A flowchart of another event notification method provided in an embodiment of the present application;

[0067] Fig. 9 A flowchart of another event notification method provided in an embodiment of the present application;

[0068] Fig.10 A schematic diagram of a PSA reselection provided in an embodiment of the present application;

[0069] Fig.11 A flowchart of another event notification method provided in an embodiment of the present application;

[0070] Fig.12 A schematic diagram of the composition of an event notification device provided in an embodiment of the present application;

[0071] Fig.13 A schematic diagram of the composition of an application function entity provided in an embodiment of the present application;

[0072] Fig.14 A schematic diagram of the composition of a chip system provided in an embodiment of the present application;

[0073] Fig.15 A schematic diagram of the composition of another event notification device provided in an embodiment of the present application;

[0074] Fig.16 A schematic diagram of the composition of a policy control function entity provided in an embodiment of the present application;

[0075] Fig.17 A schematic diagram of the composition of another chip system provided in an embodiment of the present application;

[0076] Fig.18 A schematic diagram of the composition of another event notification device provided in an embodiment of the present application;

[0077] Fig.19 A schematic diagram of the composition of a session management function entity provided in an embodiment of the present application;

[0078] Fig. 20 A schematic diagram of the composition of another chip system provided in an embodiment of the present application;

[0079] Fig.21 A schematic diagram of the composition of another event notification device provided in an embodiment of the present application;

[0080] Fig. 22 A schematic diagram of the composition of a user plane functional entity provided in an embodiment of the present application;

[0081] Fig.23 A schematic diagram of the composition of another chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0082] Currently, after the terminal device moves, in order to optimize the service access path, the terminal device can reselect the UPF and application server deployed locally. If the application server still needs to obtain the event report, it needs to subscribe to the event again. This will cause a delay in the UPF obtaining and feeding back the event report.

[0083] In order to solve the above problems, the embodiment of the present application provides an event notification method, which can enable the core network element (such as the session management function) to instruct the UPF to report the acquired event report to the corresponding address according to the event notification address corresponding to the new UPF configured by the application server when the UPF changes due to reasons such as the movement of the terminal device. In this way, there is no need for the application server to re-send the event subscription information through AF, PCF, and SMF again, thereby significantly saving the number of communications between different network elements, while saving signaling overhead and ensuring the rapid feedback of event reports.

[0084] The technical solution provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0085] First, the environment in which this method is applied is described.

[0086] Please refer to Figure 2 , which is a logical schematic diagram of a communication architecture provided in an embodiment of the present application.

[0087] like Figure 2 As shown, the communication architecture may include terminal equipment, RAN, UPF, AMF, SMF, PCF and AF.

[0088] Application function (AF). The AF may be a functional entity corresponding to the application server. In different implementations, one application server may correspond to one or more AFs. Exemplarily, in an embodiment of the present application, the application server may send event subscription information through the AF to subscribe to the corresponding UPF to obtain and report the corresponding event report. In some implementations, the application server may also send address correspondence information including at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier through the AF. It should be noted that in the present application, the application server may send the above-mentioned event subscription information and address correspondence information through the same AF. In other implementations, the application server may also send the above-mentioned event subscription information and address correspondence information through different AFs. Of course, the AF that receives the event report on the application server may be the same as or different from the AF that sends the event subscription information and / or address correspondence information. The embodiment of the present application does not limit this.

[0089] Policy control function (PCF). The PCF can be used to customize corresponding policy and charging control (PCC) rules according to the message from the AF. And the PCC rules are issued to other network elements so that other network elements can execute corresponding events according to the PCC rules. Exemplarily, in an embodiment of the present application, the PCF can be used to customize PCC rules including address correspondences according to address correspondence information from the AF, and issue the PCC rules to other network elements, so that other network elements can learn the correspondence between the event report notification address and the data network access identifier according to the PCC rules. The PCF can also be used to customize corresponding PCC rules according to event subscription information from the AF (or network exposure function (NEF)), or update existing PCC rules, and issue the PCC rules to other network elements, so that other network elements can execute corresponding events according to the PCC rules and feedback event reports to the corresponding addresses.

[0090] Session management function (SMF). The SMF is mainly responsible for interacting with the separated data plane, creating, updating and deleting PDU sessions, and managing the session context with the UPF. Exemplarily, in an embodiment of the present application, the SMF can be used to receive the PCC rules of the PCF and execute corresponding events according to the PCC rules. For example, the SMF can be used to select the corresponding UPF for the terminal device according to the data network access identifier included in the PCC rule. Among them, in different embodiments, the SMF can use the UPF closest to the terminal device as the protocol data unit anchor (PDU Session Anchor, PSA) for establishing a PDU session with the terminal device. In other embodiments, the SMF can also configure the PSA for the terminal device according to other rules, for example, the SMF can configure the PSA for the terminal device according to the historical communication quality. The embodiment of the present application is not limited to this. The SMF can also be used to receive PCC rules including address correspondence information and event subscription information, select and determine the corresponding event report notification address according to the PSA currently selected for the terminal device, and send the address and event subscription information to the corresponding PSA so that the PSA performs corresponding operations.

[0091] Core access and mobility management function (AMF). For example, the AMF is mainly responsible for the access authentication of terminal equipment, mobility management, signaling interaction between various functional network elements, such as: managing the user's registration status, user connection status, user registration, tracking area update, cell switching user authentication and key security.

[0092] User plane function (UPF). Exemplarily, UPF can establish a PDU session with the corresponding terminal device based on the information sent by SMF to implement functions such as packet routing and forwarding, data packet inspection, and implementation of some user plane policy rules. In an embodiment of the present application, UPF can execute corresponding events and obtain corresponding event reports based on event subscription information from SMF. UPF can also feedback the event report through the event report notification address sent by SMF, so that when UPF reselection occurs after UE moves, AF does not need to re-send event subscription information, and the application server can also obtain the corresponding event report.

[0093] The terminal device may include user equipment (UE) or mobile station (MS) or mobile terminal (MT), etc. As an example, the terminal device may be a mobile phone, a tablet computer or a computer with wireless transceiver function, or a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in unmanned driving, a wireless terminal device in telemedicine, a wireless terminal device in smart grid, a wireless terminal device in smart city, a smart home, and a vehicle-mounted terminal device. In this example, the terminal device can establish a PDU session with the UPF to achieve communication with the data network (DN). The following description takes the terminal device as UE as an example.

[0094] The radio access network (RAN) is an access network element that provides wireless access services. For example, in a 5G communication system, the network element may be called NR-RAN. In some implementations, the RAN may be implemented by a base station. For example, in a 5G communication system, the RAN may be a node that provides a new radio (NR) user plane and control plane protocol terminal to a terminal device, and is connected to the 5G core network via an NG interface. The RAN may also be a node that provides an evolved universal terrestrial radio access network (E-UTRAN) user plane and control plane protocol terminal to a terminal device, and is connected to the 5G core network via an NG interface.

[0095] In order to expand the network function of AF, in some embodiments, the network architecture may also include NEF. The NEF is an example of a capability open network element. In other implementations, the NEF may also be replaced by other capability open network elements. Exemplarily, the NEF may be set at the front end of the AF to perform secondary processing on the information sent / received by the AF, so that the address of the AF can be protected while ensuring the communication function of the AF. In an embodiment of the present application, the NEF may be set in a local network, and each NEF may be configured with an address (such as a NEF address). The NEF may receive event reports reported from the UPF through the corresponding NEF address. When the event subscription information corresponding to the event report is subscribed by the AF of the NEF backend, the NEF may also be used to send the received event report to the AF corresponding to the local NEF. To realize that the event report is feedback to the application server. In other embodiments, the NEF may also be set in the central network to play a similar function to the local NEF. It should be understood that in some implementations, different NEFs may be set in the central network and the local network at the same time to achieve multiple levels of network function expansion.

[0096] Specifically, as a possible deployment method, Figure 3-Figure 5 It shows that based on Figure 2 The specific deployment method of the logic diagram shown in the figure. In particular, hierarchical management of data can be achieved by setting up multiple data centers (DCs) on the layer side. For example, a central DC covering a larger area can be set up, and one or more local DCs can also be included in the coverage area of ​​the central DC.

[0097] In one possible deployment, Figure 3 As shown, AMF, SMF, PCF and NEF can be set in the central DC. It should be noted that one or more local DCs can also be deployed in different locations. For ease of explanation, the central DC and a local DC are taken as examples in the embodiments of the present application. UPF and AF can be set in the local DC. In the embodiments of the present application, the UPF set in the local DC can be called a local UPF (local UPF), and the AF set in the local DC can be called a local AF (local AF).

[0098] For example, in Figure 3In the deployment shown, the data interaction of each network element is exemplified by taking the AF sending QoS monitoring request information as an example. The AF can send a message including the QoS monitoring request information to the NEF through the N33 interface, and the NEF can send the message to the PCF through the N6 interface. The PCF can customize the corresponding PCC rules and send them to the SMF through the N7 interface. The SMF can send relevant signaling to the AMF through the N11 interface so that the AMF can perform corresponding signaling interaction with the terminal device through the N1 interface, and / or perform corresponding signaling interaction with the RAN through the N2 interface. The SMF can also send the QoS monitoring request information and the event report notification address corresponding to the QoS monitoring request information (such as the address of the AF) to the UPF through the N4 interface. The UPF performs corresponding monitoring based on the QoS monitoring request information to obtain an event report. Then, the UPF can feed back the event report to the AF with the corresponding event report notification address through the N4a interface.

[0099] Combined with the above description, when sending an event report, UPF selects the corresponding transmission channel according to the event notification address sent by SMF. Figure 3 In the deployment shown, the event notification address sent by the SMF is the same as the AF that sends the QoS monitoring request information, so the UPF can feed back the event report to the AF. In other implementations, when the event notification address sent by the SMF is different from the AF that sends the QoS monitoring request information, the UPF sends the corresponding event report to the corresponding network element according to the event notification address.

[0100] In other deployments, such as Figure 4 As shown, the NEF may also be set in the local DC. In this way, after the UPF obtains the event report, the event report may be sent to the NEF in the local DC through the N4a interface, so that the NEF sends the event report to the corresponding AF.

[0101] In other deployments, such as Figure 5 As shown, multiple NEFs can be deployed simultaneously to achieve multi-level expansion of network functions. Figure 5Take setting up an NEF in the local DC and the central DC respectively (such as setting up NEF1 in the local DC and setting up NEF2 in the central DC) as an example. In this way, when AF sends event subscription information (such as QoS monitoring request information), it can send the information to NEF1 through the N33 interface, and NEF1 can forward the information (or send it after transcoding it) to NEF2 through the N33a interface. So that NEF2 can pass the information on until it is published to UPF. After obtaining the corresponding event report, UPF can send the event report to NEF1 through the N4a interface. So that NEF1 can send the event report to the corresponding application server.

[0102] The event notification method provided in the embodiment of the present application can be applied to the network architecture of 4G / 5G service capability intercommunication, and can also be applied to the future sixth generation (6th generation, 6G) communication system or other communication systems, and the present application does not limit this. Figure 2 The communication network shown in the logic diagram can also be applied to Figure 3 or Figure 4 or Figure 5 In the communication network of the deployment shown.

[0103] The event notification method provided in the embodiment of the present application is described in detail below.

[0104] Please refer to Figure 5A , is a flow chart of an event notification method provided in an embodiment of the present application. The method can be applied to Figure 3 or Figure 4 or Figure 5 Alternatively, the method can also be applied to other communication networks having Figure 2 The logic shown is in a communication network. The following method is applied to Figure 4 The communication network shown is used as an example for explanation.

[0105] like Figure 5A As shown, the method may include S501-S508.

[0106] S501. AF sends first information and second information.

[0107] Among them, the first information may include at least one data network access identifier and an event notification address corresponding to at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function AF.

[0108] As an example, the data network access identifier may be a data network access identifier (DNAI). It should be understood that the DNAI may be used to indicate the location of the application server of the application. When the application deploys multiple application servers, each application server at each location may correspond to a DNAI. It should be understood that the event report generally needs to be reported to the AF or NEF that subscribes to the corresponding event. Figure 4 , the AF and NEF applied in the local DC are generally set up correspondingly, and the application server and AF may also have a corresponding relationship. Therefore, the DNAI corresponding to an application server has a corresponding relationship with the AF (and / or NEF). In this example, a correspondence between the DNAI and the address (such as the destination address) at which the AF or NEF receives the event report (or event notification information) can be established, that is, the above-mentioned at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier. And it is carried in the first information and sent to other core network elements, such as PCF, etc. In an embodiment of the present application, the correspondence between the data network access identifier and the corresponding event notification address can be referred to as address correspondence information.

[0109] The second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. It should be noted that the second information can be used to subscribe to events related to the business. Exemplarily, in some implementations, the second information may include quality of service QoS monitoring request information, and / or QoS notification control request information. In other embodiments, the second information can also be used to subscribe to events that are not related to the business. Exemplarily, the second information may include location request information.

[0110] In addition, the first information and the second information may be sent by the application server controlling the same AF in one message stream, or by the application server controlling the same AF in different message streams, or by the application server controlling different AFs in different message streams. This embodiment of the application does not limit this.

[0111] In some embodiments of the present application, the second information may also include a notification association identifier, which is used to associate the event notification information of the first event with the first information. It should be understood that since the first information and the second information can be sent in different message streams, it is necessary to use the above-mentioned notification association identifier so that other core network elements (such as PCF, SMF, etc.) can know the association between the address corresponding information in the first information and the first event subscribed in the second information.

[0112] S502: PCF receives first information and second information.

[0113] The first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function AF.

[0114] The second information is used to subscribe to a first event of a terminal device, where the terminal device is a device that accesses an application server of an application.

[0115] S503. PCF sends the third information and the first information.

[0116] Among them, the third information is determined according to the second information, and is used to subscribe to the first event. It should be understood that in some implementations, after receiving the second information, the PCF may perform certain processing on the second information before sending it to other network elements (such as SMF). As an example, the PCF may encapsulate the address corresponding information included in the first information and the corresponding information for subscribing to the first event indicated in the second information in the PCC rule, and send the PCC rule to the SMF. Among them, the information in the PCC rule used to indicate the subscription to the first event may be the same as the second information, that is, the third information is the same as the second information. The information in the PCC rule used to indicate the subscription to the first event may also be different from the second information, that is, the third information is different from the second information. The embodiment of the present application does not limit the specific form of the third information.

[0117] In some embodiments, when the second information received by the PCF also includes the first association identifier, the PCF may send the first association identifier to the SMF. Exemplarily, the PCF may carry the first association identifier in the PCC rule and send it to the SMF.

[0118] It should be noted that the above description is based on the example that the PCF encapsulates the first information, the third information and the first association identifier in the PCC rule and sends it. In some other implementations, the PCF can also send the first information, the third information and the first association identifier to other network elements (such as SMF) in other ways. Among them, the PCF can send the first information, the third information and the first association identifier in the same message stream, and the PCF can also send the first information, the third information and the first association identifier separately in different message streams. The embodiment of the present application does not limit the way in which the PCF sends the first information, the third information and the first association identifier.

[0119] S504. SMF receives the first information and the third information.

[0120] The first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function AF.

[0121] The third information is used to subscribe to the first event of the terminal device, where the terminal device is a device that accesses the application server of the application.

[0122] In combination with the description in S503, the SMF may receive the first information and the third information by receiving the PCC rule sent by the PCF.

[0123] S505. SMF selects a first user plane network element for the terminal device.

[0124] The first user plane network element corresponds to a first data network access identifier, and the at least one data network access identifier includes the first data network access identifier.

[0125] Exemplarily, the SMF may select a corresponding UPF as a PSA for the terminal device according to the DNAI included in the PCC rule to establish a PDU session so that the terminal device can access the data network.

[0126] After the PSA is selected and determined, the SMF can determine the corresponding event notification address based on the first information in the PCC rule (which may include address correspondence information) and the DNAI corresponding to the current PSA.

[0127] When the PSA is reselected due to reasons such as the movement of the terminal device, the SMF can reselect the corresponding UPF as the PSA for the terminal device based on the DNAI included in the PCC rule. After determining the reselected PSA, the SMF can determine the corresponding event notification address based on the first information in the PCC rule (which may include address correspondence information) and the DNAI corresponding to the current PSA. It can be seen that when PSA reselection occurs, since the SMF is able to know the correspondence between different DNAIs and event notification addresses, after the SMF reselects the PSA for the terminal device, it can determine the event notification address corresponding to the new PSA through the correspondence (i.e., address correspondence information) without the need for the AF to resend the event subscription information. This can greatly save the reporting delay of the corresponding event. In this example, the event notification address corresponding to the PSA can be referred to as the first event notification address.

[0128] It should be noted that, in some other embodiments, there may be a situation where the event report needs to be forwarded by other NEFs before it can be sent to the first event notification address. In this example, the SMF can also obtain the address of the forwarding NEF (such as the second event notification address) so as to send the second event notification address to the UPF, so that the UPF can report the event report to the first event notification address through the second event notification address.

[0129] S506. SMF sends the fourth information and the first event notification address.

[0130] The first event notification address is a destination address for receiving event notification information of the first event.

[0131] The fourth information can be determined based on the third information and used to subscribe to the first event. As an example, the first event notification address can be determined by the SMF based on the first data network access identifier, at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier (such as the above-mentioned address corresponding information).

[0132] In addition, similar to the above description, the fourth information may also include a notification association identifier for associating the event notification information of the first event with the event notification address.

[0133] It should be understood that when the SMF determines the address of the forwarding NEF (such as the second event notification address), the SMF can send the second event notification address to the UPF. It should be noted that the fourth information, the first event notification address and the second event notification address can be sent in the same message or in different messages. The embodiment of the present application does not limit the method of sending relevant information.

[0134] S507. UPF receives the fourth information and the first event notification address.

[0135] The UPF may be the first user plane network element selected by the SMF for the terminal device. The first information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. The first event notification address is the destination address for receiving the event notification information of the first event, and the destination address is the address of the application function AF corresponding to the application.

[0136] In combination with S506, the UPF may also receive a second event notification address, which may be an address of a local capability exposure network element corresponding to the first user plane network element. The first user plane network element may report the event to the first event notification address through the second event notification address.

[0137] It should be noted that, in this example, the second event notification address may be the address of the NEF used to forward the event report. Of course, the second event notification address may also be the address of other network elements that can implement the forwarding function of the event report to the network element with the first event notification address. This embodiment of the present application does not limit this.

[0138] Exemplarily, taking the address of the NEF that forwards the event report as the second event notification address as an example, the UPF can receive the address of the NEF with forwarding function (such as the second event notification address). So that after obtaining the event report, the event report and the corresponding destination address (such as the first event notification address) can be sent together to the NEF corresponding to the second event notification address, so that the NEF can send the event report to the network element corresponding to the first event notification address.

[0139] S508. UPF sends the fifth information.

[0140] The fifth information may include event notification information of the first event. For example, when the first event includes quality of service QoS monitoring request information, the fifth information may include an event report corresponding to the QoS monitoring request. When the first event includes QoS notification control request information, the fifth information may include an event report corresponding to the QoS notification control request. When the first event includes location request information, the fifth information may include an event report corresponding to the location request information.

[0141] It should be understood that when the UPF also receives the second event notification address, the fifth information can be sent to the second event notification address. The UPF can also send the first event notification address to the network element (such as NEF) corresponding to the second event notification address, so that the NEF can send the event report included in the fifth information to the first event notification address.

[0142] Of course, if the UPF does not receive the second event notification address, the UPF may directly send the fifth information to the network element (such as AF or NEF) corresponding to the first event notification address.

[0143] In addition, in some embodiments, the fifth information may further include a notification association identifier, so that the network element receiving the event report can clarify the association between the event notification information of the first event and the event notification address according to the notification association identifier.

[0144] Based on the above Figure 5AAs shown in the method, SMF can determine the event notification address of the event report of the event subscription information based on the DNAI corresponding to the current PSA and the address corresponding information. Therefore, when PSA reselection occurs, since SMF knows the correspondence between all DNAIs and event notification addresses, there is no need for AF to resend event subscription information. SMF can determine the event notification address corresponding to the new PSA and send it to UPF so that UPF can report accurately. This can significantly reduce the delay in event report reporting and save signaling interaction between core network elements.

[0145] In order to enable those skilled in the art to more accurately understand Figure 5A The method shown is further described below with reference to an example. Figure 6 The specific implementation method of AF sending address corresponding information is shown. Figure 7 For Figure 6 An example of a method for implementing PSA selection based on . Figure 8 This is an example of sending event subscription information and reporting the corresponding event report. Fig. 9 An example of event reporting in a PSA reselection scenario is shown. Fig.11 An example of sending and reporting event subscription information in a scenario where the subscription event is a non-business related event is shown. Figure 6 , Figure 7 , Figure 8 , Fig. 9 ,as well as Fig.11 The methods shown can be applied to Figure 2 The logical architecture shown in the figure can also be applied to Figure 3 or Figure 4 or Figure 5 In the deployment shown.

[0146] It should be noted that in the following example, the terminal device is UE, and the application server sends the data network access identifier and the corresponding event notification address (such as address correspondence information), event subscription information and received event report through the same AF. Figure 4 The network architecture shown is taken as an example.

[0147] For example, AF can be based on Figure 6 The method shown implements the configuration of address corresponding information.

[0148] like Figure 6 As shown, the method may include S601-S603.

[0149] S601. AF sends information 6-1 to NEF.

[0150] Among them, the information 6-1 may include address correspondence information. In the address correspondence information, at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier may be included. Exemplarily, in some embodiments, a data network access identifier may correspond to an event notification address. In other embodiments, a data network access identifier may also correspond to multiple event notification addresses. The following is an example of a data network access identifier corresponding to an event notification address.

[0151] As a possible implementation, the information 6-1 may be sent via a Nnef_TrafficInfluence_CreateRequest message. The data network access identifier may be a DNAI. The event notification address may be a receiving address for an event report corresponding to the DNAI. It should be noted that the event notification address may be an NEF address corresponding to an application server of an application, or an AF address corresponding to an application server of an application.

[0152] It should be understood that DNAI represents the location information of the application, that is, the location information of the application server of the application. An application can be set up with multiple different application servers under different local DCs. If the application server wants to interact with the PCF, the application server needs to interact with the AF deployed in the local DC, and then the AF interacts with the PCF. Therefore, an application server can generally correspond to an AF address, so DNAI can also correspond to an AF. If a local NEF is deployed in the local DC, DNAI can also correspond to an NEF. The address correspondence information in the example can include the correspondence between the DNAI corresponding to each AF in different local DCs and the address at which the AF receives event notifications. So that other network elements (such as SMF) can determine the address of the AF or NEF that can receive event reports based on the DNAI corresponding to the selected local UPF.

[0153] In some implementations, the information 6-1 may also include Traffic Steering Info, which may include an application service provider (ASP) identifier, service description information, and an identifier of the corresponding UE. It should be understood that different applications may set up multiple application servers in different local DCs. Correspondingly, multiple application servers may be set up in the local DC to support corresponding services of different applications. Therefore, in this example, the information 6-1 may also include an ASP identifier that can identify the application, service description information, and identification information of the target UE (such as the IP address of the UE, indication information of any UE, external identifier of the UE or external group identifier).

[0154] S602. NEF sends information 6-2 to PCF.

[0155] After obtaining the information 6-1 from the AF, the NEF can process it, such as transcoding, so as to hide the information 6-1 and achieve the purpose of protecting the AF. For example, the NEF can achieve the above purpose by mapping the external group identifier in the Nnef_TrafficInfluence_CreateRequest to the internal group identifier and the external identifier of the UE to the internal identifier. Then the NEF can send the information 6-2 obtained according to the information 6-1 to the PCF. The NEF can directly send the information 6-2 to the PCF or the NEF can send the information 6-2 to the PCF through the Unified Data Repository (UDR) that provides data storage services.

[0156] As an example, if the identification information of the target UE is the IP address of the UE, the NEF sends it to the PCF via Npcf_PolicyAuthorization Request. The information 6-2 includes relevant information indicating the address corresponding information, ASP identification, and service description information. The function is similar to the relevant information in S601, which will not be repeated here.

[0157] As an example, if the identification information of the target UE is the indication information of any UE, the external identification of the UE, or the external group identification, the NEF can send the information 6-2 to the UDR through the Nudr_DM_Update Request. The UDR can store the Nudr_DM_Update Request after receiving it. For the PCF that needs to obtain the information, it generally subscribes to the corresponding Traffic Steering Info from the UDR. The UDR can send the Nudr_DM_Update Request to the PCF that has subscribed to the corresponding Traffic Steering Info. In this way, the transmission of information 6-2 to the PCF is realized.

[0158] It should be noted that, in the embodiment of the present application, when an NEF is provided between the AF and the PCF, the information 6-2 may correspond to the following: Figure 5A When there is no NEF between AF and PCF, the above information 6-1 can correspond to the following: Figure 5A The first message in the illustrated scheme.

[0159] S603. The PCF generates a first PCC rule according to the information 6-2.

[0160] After receiving the information 6 - 2 , the PCF may generate corresponding PCC rules according to the information 6 - 2 , so that other network elements may perform corresponding operations according to the PCC rules.

[0161] Exemplarily, after receiving Nudr_DM_Update Request, PCF can customize the corresponding PCC rule (such as PCC rule 1). In the PCC rule 1, only DNAI or the correspondence between DNAI and event notification address can be included. For example, the correspondence between multiple DNAIs corresponding to application 1 and event notification address is included in Nudr_DM_Update Request. In PCC rule 1, multiple DNAIs corresponding to application 1 or the correspondence between multiple DNAIs and event notification address can be included.

[0162] It should be understood that, in this example, the address correspondence information included in the first PCC rule may be the same as Figure 5A The address correspondence information in the first information in the illustrated solution is the same.

[0163] In this way, the address corresponding information corresponding to the application is reflected in the PCC rule.

[0164] It should be understood that when the UE establishes a PDU session or the UE establishes a PDU session, the SMF can select the corresponding UPF as the PSA for the UE according to the PCC rules.

[0165] For example, please refer to Figure 7 , PCF can send the first PCC rule to SMF (i.e., execute S701). When the UE establishes a PDU session or after the UE establishes a PDU session, the SMF can select UPF as PSA for the UE according to the first PCC rule (i.e., DNAI) (i.e., execute S702). As a possible implementation method, when the UE establishes a PDU session for accessing application 1, the SMF can determine the application server corresponding to the application 1 according to the first PCC rule. Since there is a corresponding relationship between the application server and the UPF in different local DCs, the SMF can obtain a list of UPFs that can access application 1. The SMF can select the corresponding UPF as the PSA for the UE according to preset rules. For example, the SMF can select the UPF in the above UPF list that is closest to the UE as the PSA to establish a PDU session with the UE according to the current location of the UE. Of course, the SMF can also select a PSA for the UE according to other rules, which will not be repeated here. It should be understood that, if Figure 7 In the scheme shown, the PSA determined by the SMF for the UE according to the first PCC rule may correspond to the following: Figure 5A The first user plane network element in the illustrated solution.

[0166] Thus, a PDU session between the UE and the PSA is realized. The UE can access the DN through the PDU session. For example, the UE can access the application server corresponding to the application 1 through the PDU session.

[0167] After the UE establishes a PDU session, the UE can interact with the application server through application layer signaling, and the application server can send event subscription information to the UPF through the AF. It should be noted that the event subscription information can be service-related information, such as QoS monitoring information. The event subscription information can also be information unrelated to the service. For example, the event subscription information can be used to subscribe to the location information of the UE. This embodiment of the present application does not limit this. The following takes the event subscription information used to subscribe to QoS monitoring information as an example.

[0168] like Figure 8 As shown, a flow chart of an event notification method provided by an embodiment of the present application is shown. It can be understood that the method can be applied to the scenario where the UE performs relevant detection on the communication process after establishing a PDU session with the UPF. For example, the method can be applied to the UE establishing a PDU session such as Figure 7 After the PDU session shown.

[0169] like Figure 8 As shown, the method may include S801-S808. The method may be applied to Figure 7 After the PDU session is established. It should be noted that in some other implementations, the Figure 8 The method shown can also be used with Figure 7 The method shown is performed simultaneously. Figure 7 The method shown is Figure 8 The execution order of the method shown is not limited. Figure 8 The method shown was previously established as Figure 7 The PDU session shown is taken as an example.

[0170] S801. AF sends information 8-1 to NEF.

[0171] The information 8-1 may include event subscription information.

[0172] For example, the event subscription information can be used to request service-related communication data (such as QoS-related data). The event subscription information can include description information of the service data flow, ASP identification, etc.

[0173] As an example, when the event subscription information is used for quality of service monitoring (QoS Monitoring), the event subscription information may also include QoS Monitoring information or QoS Monitoring information and QoS Monitoring event identifier. The QoS Monitoring information may include but is not limited to requesting QoS Monitoring Parameter (i.e., the measured delay type, which may include uplink data, downlink data, or round-trip data), reporting frequency (periodicity, event triggering), and other information. When the event subscription information is used to request QoS Notification Control (QoS Notification Control) event notification, the event subscription information may also include QoS Notification Control indication (such as QoS Notification Control event identifier), etc.

[0174] In addition, the information 8-1 can be sent to the NEF via the Nnef_AFsessionWithQoS_Create request message, which can include a notification association identifier. After detecting the corresponding event, the UPF can carry the notification association identifier in the corresponding event report, so that the AF or NEF receiving the event report can know that the event report is associated with this event subscription.

[0175] S802. NEF sends information 8-2 to PCF.

[0176] Similar to the above Figure 6 In S602 shown, the NEF may perform similar processing on the information 8-1, obtain information 8-2 and send it to the PCF. The processing process is similar and will not be repeated here. Of course, the NEF may also transmit the information 8-2 via the UDR, which is not limited in this example. For example, the information 8-2 sent by the NEF may be Npcf_PolicyAuthorization Request.

[0177] In the embodiment of the present application, when NEF is provided between AF and PCF, information 8-2 may correspond to the following: Figure 5A When there is no NEF between AF and PCF, the above information 8-1 can correspond to the following: Figure 5A Second information in the illustrated scheme.

[0178] S803. The PCF obtains a second PCC rule according to the information 8-2 and the first PCC rule.

[0179] It is understandable that according to Figure 6 and Figure 7The PCF stores a first PCC rule. The first PCC rule may include address corresponding information corresponding to the application.

[0180] After receiving the information 8-2, the PCF may update the first PCC rule to obtain an updated PCC rule (i.e., a second PCC rule). The second PCC rule may include event subscription information and address corresponding information of an application corresponding to the event subscription information. The second PCC rule in this example may include information corresponding to Figure 5A The event subscription information of the third information in the scheme shown, and Figure 5A The address of the first information in the illustrated scheme corresponds to the information.

[0181] Since the address corresponding information corresponding to the application and the information 8 - 2 may not be received at the same time, the PCF may associate the address corresponding information of the application with the information 8 - 2 according to the ASP identifier in the information 8 - 2.

[0182] In some implementations, after receiving information 8-2, the PCF can determine the address corresponding information of the corresponding application in the first PCC rule according to the ASP identifier corresponding to the event subscription information included in the information 8-2. For example, the ASP identifier corresponding to the event subscription information indicates that the event subscription information corresponds to application 1, then the PCF can carry the address corresponding information 6-1 corresponding to the application 1 in the second PCC rule according to the ASP identifier. In addition, the second PCC rule may also include other information, for example, the second PCC rule may include the notification association identifier in the information 8-2.

[0183] S804. The PCF sends the second PCC rule to the SMF.

[0184] S805. SMF determines event notification address 1 according to the second PCC rule.

[0185] Since the SMF selects the PSA for the UE according to the first PCC rule, when the SMF receives the second PCC rule (i.e., event subscription information), the SMF further determines the event notification address 1 according to the DNAI used to select the PSA and the address correspondence information of the application. In this example, the event notification address 1 may correspond to Figure 5A First event notification address in the illustrated scenario.

[0186] S806. SMF sends information 8-3 to UPF.

[0187] SMF can include event subscription information (such as Figure 5A The fourth information in the scheme shown), the event notification address 1, and the notification association identifier information 8-3 are sent to the UPF corresponding to the event.

[0188] S807. UPF obtains an event report.

[0189] UPF can perform corresponding monitoring based on the acquired event subscription information. Exemplarily, since the UPF is generally the PSA that establishes a PDU session with the UE, the UPF obtaining an event report can also be referred to as the PSA obtaining an event report. When the event subscription information is QoS Monitoring, the PSA can measure the packet transmission delay between the UE and the PSA, and when the conditions indicated by the reporting frequency are met, the event corresponding to QoS Monitoring is detected. When the event subscription information is QoS NotificationControl, when the PSA receives a notification from the RAN that the bandwidth cannot be guaranteed or the bandwidth can be guaranteed again, the QoS Notification Control event is detected.

[0190] S808. UPF sends information 8-4 to AF.

[0191] After obtaining the event report corresponding to the event subscription information, the UPF can perform feedback of the event report. Exemplarily, the UPF can feed back the event report to the network element with event notification address 1. In different implementation scenarios, the network element can be AF or NEF. In this example, the network element corresponding to event notification address 1 is AF as an example.

[0192] Combined with Figure 4 In the communication architecture shown, the UPF can transmit data with the NEF in the local DC through the N4a interface. Further, the NEF can transmit the corresponding data to the AF in the local DC. In this example, the event notification address 1 can be the address of the local NEF. The UPF can send information 8-4 including the event report and the notification association identifier to the NEF. In this way, the UPF completes the reporting of the event report to the event notification address 1. In this example, the information 8-4 can correspond to Figure 5A The fifth message in the scheme shown.

[0193] It should be noted that in some other implementations, the event notification address may be the address corresponding to the AF in the local DC, or the address corresponding to the AF in other local DCs, or the address corresponding to the AF in the central DC. In this example, the information 8-3 sent by the SMF to the UPF may include, in addition to the event notification address 1, the address of the NEF corresponding to the event notification address (such as event notification address 2). In this way, the UPF can report the event report and the event notification address 1 to the network element corresponding to the event notification address 2. After receiving the event notification address, the NEF can further transmit the event report to the network element (such as AF) with the event notification address 1. Thereby, the feedback of the event report to the network element with the event notification address 1 is realized. In this example, the event notification address 2 can correspond to, for example, Figure 5A Second event notification address in the illustrated scenario.

[0194] It is understandable that based on the above Figure 6 , Figure 7 , Figure 8 Regarding the description of the event reporting method, since SMF can obtain the correspondence between all possible DNAIs and event notification addresses, when PSA reselection occurs due to UE mobility, etc., SMF determines the event notification address corresponding to the new PSA based on the saved event subscription information, and sends the new event notification address together with the event subscription information to UPF. This can avoid the problem that after PSA reselection, AF must resend event subscription information to ensure that UPF transmits the event report to the correct address.

[0195] As an example, Fig. 9 A flow chart of a method for reporting an event after PSA reselection is given. The example of UE causing PSA reselection is taken as an example. Fig. 9 As shown, the method may include S901-S905.

[0196] S901. SMF reallocates PSA for the moving UE.

[0197] It should be understood that when the UE moves, in order to provide better communication services for the UE, the SMF can adjust the PSA for the UE as it moves so as to access the DN. In itself, the reallocated PSA can be called a second user plane network element, that is, a second UPF.

[0198] For example, please refer to Fig.10When the UE moves from position 1 to position 2, the SMF may also switch the PSA for the PDU session with the UE from UPF1 in the local DC1 to UPF2 in the local DC2. Obviously, when the quality of service provided by UPF1 and UPF is the same, when the UE is in position 2, UPF2 can provide better communication services for the UE.

[0199] When the UE moves, since the UPF that establishes the PDU session with it has changed, when the application server wants to obtain the event report corresponding to the current subscription event information of the UE, it cannot obtain the event report monitored and obtained by UPF2 in the local DC2 through the AF in the local DC1 (the AF through which the application server obtains the event report before the UE moves). In the embodiment of the present application, since the SMF can know the correspondence between all DNAIs corresponding to the application and the event notification address (such as the above-mentioned address correspondence information), when the PSA is updated, the SMF can also determine the corresponding updated event notification address.

[0200] In this embodiment, the application server in DC1 will also send the event subscription information to the application server in DC2 through the application layer (such as notification association identifier), after which DC2 can interact with the corresponding AF and notify AF to send the corresponding event notification to the application server.

[0201] S902. SMF determines event notification address 3 according to the second PCC rule.

[0202] After the SMF allocates a new PSA to the UE, the SMF may determine the new PSA (such as Fig.10 The event notification address 3 corresponding to the DNAI corresponding to the UPF2 shown in FIG. Figure 8 The S805 shown in FIG. 1 is similar to the S805 shown in FIG. 1 , and will not be described in detail here.

[0203] S903. SMF sends information 9-1 to UPF.

[0204] S904. UPF obtains an event report.

[0205] S905. UPF sends information 9-2 to AF.

[0206] After obtaining the new event notification address, SMF can continue to execute S903-S905. Their respective execution methods can correspond to the following: Figure 8 S806-S808 shown in FIG. 1 will not be described in detail here. Among them, the information 9-1 may include: Figure 5A The fourth information in the scheme shown and the first event notification address. Information 9-2 may include the following: Figure 5A The fifth message in the scheme shown.

[0207] It should be noted that after the SMF reselects the PSA for the UE, a UPF in a network can be selected as a branching point or uplink classifier, and the uplink data sent by the UE when accessing the application can be forwarded to the reselected PSA through the UPF by configuring the diversion rules to the intermediate UPF. This enables smooth uplink communication of the UE after the PSA is reselected.

[0208] Combined with the above description, AF can be Figure 6 The method shown in FIG. 1 configures the corresponding information of different addresses into the PCF. The AF can also configure the corresponding information of different addresses into the PCF by Figure 8 The method shown sends event subscription information. So that the SMF can determine the event notification address corresponding to the selected PSA based on the interaction with the PCF, and instruct the UPF to report the event report corresponding to the event subscription information through the event notification address. As an example, when the event report that the AF (or the application server corresponding to the AF) wants to obtain is an event report related to the service (such as an event report related to QoS monitoring), the application server can control the same or different AFs, and send the event subscription information and the information including the corresponding information of different addresses to other network elements through the same signaling. In another implementation, the application server can also control the same or different AFs, and send the event subscription information and the information including the corresponding information of different addresses to other network elements through different signaling. In other embodiments, when the event report that the AF (or the application server corresponding to the AF) wants to obtain is an event report that is not related to the service (such as an event report of the UE location), the application server can control the same or different AFs, and send the event subscription information and the information including the corresponding information of different addresses to other network elements through the same signaling. In order to enable those skilled in the art to more quickly and clearly understand the application method of the method provided in the embodiment of the present application in a scenario where an application server obtains event reports unrelated to the business, the specific implementation method in this scenario is exemplified below.

[0209] Please refer to Fig.11 , is a flow chart of another event reporting method provided in an embodiment of the present application, wherein the AF that sends the event subscription information and address information is the same as the AF that receives the event report.

[0210] like Fig.11 As shown, the method may include S1101-S1107.

[0211] S1101. AF sends information 11-1 to PCF.

[0212] In this example, the information 11-1 may be sent via Nnef_TrafficInfluence_Create Request. The information 11-1 may include at least the correspondence between the DNAI and the event notification address (i.e., address correspondence information), the event identifier corresponding to the event subscription information, and an optional identifier assigned by the AF to the event subscription information (e.g., NotificationCorrelation Id). Figure 5A The first information and the second information in the illustrated scheme.

[0213] Combined with the description in S601-S602 above, in different network architectures, the AF can send the information 11-1 to the PCF through the NEF, the AF can also send the information 11-1 to the PCF through the NEF and the UDR, or the AF can directly send the information 11-1 to the PCF. The specific implementation method is similar to the method in S601-S602, and will not be repeated here.

[0214] S1102. PCF customizes corresponding PCC rules according to information 11-1.

[0215] The PCF can customize the corresponding PCC rules based on the received new 11-1. Exemplarily, the PCC rules can carry a Traffic Steering Policy, which can include a list of DNAIs for the SMF to select a PSA based on the Traffic Steering Policy. If the identification information of the target UE indicated by information 11-1 is the indication information of any UE or an internal group identifier, the PCC rules also include an indication of sending the UE identifier.

[0216] In this example, the Traffic Steering Policy may also include address correspondence information, event identifier, and Notification Correlation Id. It should be understood that in this example, the PCC rule may include: Figure 5A The third and fourth information in the illustrated scheme.

[0217] S1103. PCF sends PCC rules to SMF.

[0218] S1104. SMF determines the event notification address according to the PCC rule.

[0219] Combined with the description in S804-S806 above, SMF can determine the event notification address corresponding to the event subscription information according to the address corresponding information in the PCC rule, that is, the currently selected PSA (such as the first user plane network element). Among them, the event notification address can be as follows Figure 5A First event notification address in the illustrated scenario.

[0220] S1105. SMF sends information 11-2 to UPF.

[0221] The information 11-2 may include event subscription information and a corresponding event notification address. If the PCC rule includes an instruction to send a UE identifier, the information 11-2 also includes an external identifier of the UE. In some implementations, the information 11-2 may include: Figure 5A The fourth information in the illustrated scheme and the first event notification address.

[0222] S1106. UPF obtains event report.

[0223] S1107. UPF sends an event report to AF.

[0224] UPF can report the obtained event report through the event notification address indicated by SMF. As an example, the event report can be as follows: Figure 5A The fifth message in the scheme shown.

[0225] It should be noted that when the AF sends information 11-1, it can also send a notification association identifier so that when the UPF reports the event, it can upload the notification association identifier together, so that the application server can know the association between the acquired event report and the event subscription information sent. In addition, in some embodiments, the event subscription information corresponds to certain terminal devices. Therefore, when the UE reports the event report, it can report the Notification Correlation Id configured by the AF for it, so that the application server can associate the event report with the UE. If the information 11-2 includes the external identifier of the UE, the external identifier of the UE is also reported in the event report.

[0226] Through Fig.11 It should be understood that the SMF can determine the event notification address of the event report corresponding to the event subscription information according to the selected PSA. Therefore, when PSA (UPF) reselection occurs due to reasons such as UE mobility, it can be based on the following example: Fig. 9 The method shown executes the corresponding event reporting mechanism, thereby avoiding the problem of excessive delay caused by the AF needing to re-send event subscription information when the PSA changes.

[0227] In addition, in some embodiments, when the event report needs to be fed back to the AF through other NEFs, the SMF can also obtain and send the address of the NEF (such as address 2) when sending the event subscription information and the corresponding event notification address (such as address 1) to the UPF (i.e., executing S1105). The UPF can obtain the event subscription information, address 1 and address 2 from the SMF. After the UPF obtains the corresponding event report, the event report can be sent to the address 2, and the address 1 can be sent to the NEF corresponding to the address 2. In this way, the NEF can send the event report to the corresponding AF according to the address 1, thereby realizing the smooth sending of the event report.

[0228] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of each network element. In order to realize the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this document, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0229] The embodiment of the present application can divide the functional modules of the above-mentioned network elements according to the above-mentioned method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0230] Please refer to Fig.12 , is a schematic block diagram of an event notification device 1200 provided in an embodiment of the present application. The event notification device 1200 can be arranged in Figure 2 or Figure 3 or Figure 4 or Figure 5 The AF shown is used to implement any event notification method provided in the embodiments of the present application.

[0231] like Fig.12As shown, the event notification device 1200 may include: a determination unit 1201 and a sending unit 1202. The determination unit 1201 is used to determine the first information and the second information, the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the destination address for receiving the event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function (AF). The second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. The sending unit 1202 is used to send the first information and the second information. As an example, the determination unit 1201 can specifically determine the specific content of the first information and the second information according to the instruction of the application server.

[0232] In one possible design, the second information also includes: a notification association identifier, which is used to associate event notification information of the first event with the first information.

[0233] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.

[0234] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here. As an option but not a necessity, when necessary, the event notification device 1200 provided in the embodiment of the present application may also include a processing module or a control module for supporting the above-mentioned determination unit 1201 and / or sending unit 1202 to complete the corresponding functions.

[0235] Fig.13 A schematic diagram of the composition of an application function entity 1300 is shown. The application function entity 1300 may include: a processor 1301 and a memory 1302. The memory 1302 is used to store computer-executable instructions. Exemplarily, in some embodiments, when the processor 1301 executes the instructions stored in the memory 1302, the application function entity 1300 may perform the operations that the AF needs to perform in the above example.

[0236] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0237] Fig.14A schematic diagram of the composition of a chip system 1400 is shown. The chip system 1400 may include: a processor 1401 and a communication interface 1402, which are used to support AF to implement the functions involved in the above embodiments. In a possible design, the chip system 1400 also includes a memory for storing program instructions and data necessary for AF. The chip system 1400 may be composed of chips, or may include chips and other discrete devices.

[0238] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0239] Please refer to Fig.15 , is a schematic block diagram of another event notification device 1500 provided in an embodiment of the present application. The event notification device 1500 can be arranged as follows: Figure 2 or Figure 3 or Figure 4 or Figure 5 The PCF shown is used to implement any event notification method provided in the embodiments of the present application.

[0240] like Fig.15 As shown, the event notification device 1500 may include: a receiving unit 1501 and a sending unit 1502. The receiving unit 1501 is used to receive first information and second information, the first information includes at least one data network access identifier and an event notification address corresponding to at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function AF. The second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. The sending unit 1502 is used to send third information and the first information, wherein the third information is determined based on the second information and is used to subscribe to the first event.

[0241] In one possible design, the second information also includes: a notification association identifier, the notification association identifier is used to associate the event notification information of the first event with the first information, and the third information also includes the notification association identifier.

[0242] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.

[0243] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here. As an option but not a necessity, when necessary, the event notification device 1500 provided in the embodiment of the present application may also include a processing module or a control module for supporting the above receiving unit 1501 and / or sending unit 1502 to complete the corresponding functions.

[0244] Fig.16 A schematic diagram of the composition of a policy control function entity 1600 is shown. The policy control function entity 1600 may include: a processor 1601 and a memory 1602. The memory 1602 is used to store computer-executable instructions. Exemplarily, in some embodiments, when the processor 1601 executes the instructions stored in the memory 1602, the policy control function entity 1600 may perform the operations that the PCF needs to perform in the above example.

[0245] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0246] Fig.17 A schematic diagram of the composition of a chip system 1700 is shown. The chip system 1700 may include: a processor 1701 and a communication interface 1702, which are used to support the PCF to implement the functions involved in the above embodiments. In a possible design, the chip system 1700 also includes a memory for storing program instructions and data necessary for the PCF. The chip system 1700 may be composed of chips, or may include chips and other discrete devices.

[0247] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0248] Please refer to Fig.18 , is a schematic block diagram of an event notification device 1800 provided in an embodiment of the present application. The event notification device 1800 can be arranged in Figure 2 or Figure 3 or Figure 4 or Figure 5 The SMF shown is used to implement any event notification method provided in the embodiments of the present application.

[0249] like Fig.18As shown, the event notification device 1800 may include: a receiving unit 1801 and a sending unit 1802. The receiving unit 1801 is used to receive first information and second information, the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the destination address for receiving the event notification information, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function AF. The second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. A first user plane network element is selected for the terminal device, the first user plane network element corresponds to the first data network access identifier, and the at least one data network access identifier includes the first data network access identifier. The sending unit 1802 is used to send third information and the first event notification address. The third information is determined according to the second information and is used to subscribe to the first event. The first event notification address is determined according to the first data network access identifier, the at least one data network access identifier, and the event notification address corresponding to the at least one data network access identifier.

[0250] In a possible design, the sending unit 1802 is also used to send a second event notification address, where the second event notification address is the address of the local capability exposure network element corresponding to the first user plane network element.

[0251] In one possible design, the second information also includes: a notification association identifier, the notification association identifier is used to associate the event notification information of the first event with the first information, and the third information also includes the notification association identifier.

[0252] In one possible design, the device also includes a configuration unit 1803, which is used to select a corresponding second user plane network element for a terminal device of an application server accessing an application, the second user plane network element corresponds to a second data network access identifier, and at least one data network access identifier includes the second data network access identifier. Send fourth information and a third event notification address. The fourth information is determined based on the second information and is used to subscribe to the first event. The third event notification address is determined based on the second data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.

[0253] In a possible design, the sending unit 1802 is further used to send a fourth event notification address, where the fourth event notification address is the address of the local capability exposure network element corresponding to the second user plane network element.

[0254] In one possible design, the second information also includes: a notification association identifier, the notification association identifier is used to associate the event notification information of the first event with the first information, and the fourth information also includes the notification association identifier.

[0255] In one possible design, the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.

[0256] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here. As an option but not a necessity, when necessary, the event notification device 1800 provided in the embodiment of the present application may also include a processing module or a control module for supporting the above-mentioned receiving unit 1801 and / or sending unit 1802 and / or configuration unit 1803 to complete the corresponding functions.

[0257] Fig.19 A schematic diagram of the composition of a session management function entity 1900 is shown. The session management function entity 1900 may include: a processor 1901 and a memory 1902. The memory 1902 is used to store computer-executable instructions. Exemplarily, in some embodiments, when the processor 1901 executes the instructions stored in the memory 1902, the session management function entity 1900 may perform the operations that the SMF needs to perform in the above example.

[0258] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0259] Fig. 20 A schematic diagram of the composition of a chip system 2000 is shown. The chip system 2000 may include: a processor 2001 and a communication interface 2002, which are used to support the SMF to implement the functions involved in the above embodiments. In a possible design, the chip system 2000 also includes a memory for storing program instructions and data necessary for the SMF. The chip system 2000 may be composed of a chip, or may include a chip and other discrete devices.

[0260] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0261] Please refer to Fig.21 , is a schematic block diagram of an event notification device 2100 provided in an embodiment of the present application. The event notification device 2100 can be arranged in Figure 2 or Figure 3 or Figure 4 or Figure 5 The UPF shown is used to implement any event notification method provided in the embodiments of the present application.

[0262] like Fig.21As shown, the event notification device 2100 may include: a receiving unit 2101 and a sending unit 2102 .

[0263] The receiving unit 2101 is used to receive first information, a first event notification address and a second event notification address, wherein the first information is used to subscribe to a first event of a terminal device, and the terminal device is a device that accesses an application server of an application. The first event notification address is a destination address for receiving event notification information of a first event, and the destination address is an address of an application function AF corresponding to the application. The second event notification address is an address of a local capability exposure network element corresponding to a first user plane network element. The sending unit 2102 is used to send second information to the first event notification address via the second event notification address, wherein the second information includes event notification information of the first event.

[0264] In one possible design, the first information also includes: a notification association identifier, where the notification association identifier is used to associate the event notification information of the first event with the event notification address, and the second information also includes the notification association identifier.

[0265] In one possible design, the first information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

[0266] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here. As an option but not a necessity, when necessary, the event notification device 2100 provided in the embodiment of the present application may also include a processing module or a control module for supporting the above receiving unit 2101 and the sending unit 2102 to complete the corresponding functions.

[0267] Fig. 22 A schematic diagram of the composition of a user plane function entity 2200 is shown. The application function entity 2200 may include: a processor 2201 and a memory 2202. The memory 2202 is used to store computer-executable instructions. Exemplarily, in some embodiments, when the processor 2201 executes the instructions stored in the memory 2202, the user plane function entity 2200 may perform the operations that the UPF needs to perform in the above example.

[0268] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0269] Fig.23A schematic diagram of the composition of a chip system 2300 is shown. The chip system 2300 may include: a processor 2301 and a communication interface 2302, which are used to support the UPF to implement the functions involved in the above embodiments. In a possible design, the chip system 2300 also includes a memory for storing the necessary program instructions and data of the UPF. The chip system 2300 may be composed of a chip, or may include a chip and other discrete devices.

[0270] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0271] The functions or actions or operations or steps in the above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. 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 a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or may include one or more servers, data centers and other data storage devices that can be integrated with the medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0272] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. An event notification method, characterized in that: The method comprises: receiving first information and third information, wherein the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of an application server of an application, and the event notification address is a destination address for receiving event notification information, and the destination address is an address of a local capability exposure network element corresponding to the application or an address of an application function AF; The third information is used to subscribe to a first event of a terminal device, where the terminal device is a device that accesses an application server of the application; Selecting a first user plane network element for the terminal device, the first user plane network element corresponds to a first data network access identifier, and the at least one data network access identifier includes the first data network access identifier; Sending fourth information and a first event notification address, where the first event notification address is a destination address for receiving event notification information of the first event; Among them, the fourth information is determined according to the third information and is used to subscribe to the first event; the first event notification address is determined according to the first data network access identifier, the at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier.

2. The method according to claim 1, characterized in that The method further comprises: A second event notification address is sent, where the second event notification address is an address of a local capability exposure network element corresponding to the first user plane network element.

3. The method according to claim 1 or 2, characterized in that: The third information also includes: a notification association identifier, and the notification association identifier is used to associate the event notification information of the first event with the first information. The fourth information also includes the notification association identifier.

4. The method according to claim 1 or 2, characterized in that: The third information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

5. An event notification device, characterized in that: The device comprises a receiving unit and a sending unit, The receiving unit is configured to receive first information and third information, wherein the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of an application server of an application, and the event notification address is a destination address for receiving event notification information, and the destination address is an address of a local capability exposure network element corresponding to the application or an address of an application function AF; The third information is used to subscribe to a first event of a terminal device, where the terminal device is a device that accesses an application server of the application; Selecting a first user plane network element for the terminal device, the first user plane network element corresponds to a first data network access identifier, and the at least one data network access identifier includes the first data network access identifier; The sending unit is used to send fourth information and a first event notification address, where the first event notification address is a destination address for receiving event notification information of the first event; The fourth information is determined according to the third information and is used to subscribe to the first event; The first event notification address is determined according to the first data network access identifier, the at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier.

6. The device according to claim 5, characterized in that The sending unit is further used to send a second event notification address, where the second event notification address is an address of a local capability exposure network element corresponding to the first user plane network element.

7. The device according to claim 5 or 6, characterized in that The third information also includes: a notification association identifier, and the notification association identifier is used to associate the event notification information of the first event with the first information. The fourth information also includes the notification association identifier.

8. The device according to claim 5 or 6, characterized in that The third information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

9. A session management function SMF entity, characterized in that: The SMF entity includes one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions; When the one or more processors execute the computer instructions, the SMF entity executes the event notification method according to any one of claims 1 to 4.

10. An event notification method, characterized in that: The method comprises: Sending first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, where the network access identifier is used to indicate the location of an application server of an application, and the event notification address is a destination address for receiving event notification information, and the destination address is an address of a local capability exposure network element corresponding to the application or an address of an application function AF; The second information is used to subscribe to a first event of a terminal device, where the terminal device is a device that accesses an application server of the application; The at least one data network access identifier includes a first data network access identifier, the first data network access identifier corresponds to a first user plane network element, the first user plane network element is selected by the session management function SMF entity for the terminal device, the first data network access identifier, the at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier are used to determine a first event notification address, and the first event notification address is a destination address for receiving event notification information of the first event.

11. The method according to claim 10, characterized in that The second information also includes: a notification association identifier, and the notification association identifier is used to associate the event notification information of the first event with the first information.

12. The method according to claim 10 or 11, characterized in that: The second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

13. An event notification device, characterized in that: The device comprises: a determining unit and a sending unit; The determining unit is used to determine first information and second information, wherein the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of an application server of an application, and the event notification address is a destination address for receiving event notification information, and the destination address is an address of a local capability exposure network element corresponding to the application or an address of an application function AF; the second information is used to subscribe to a first event of a terminal device, and the terminal device is a device that accesses the application server of the application; the at least one data network access identifier includes a first data network access identifier, the first data network access identifier corresponds to a first user plane network element, and the first user plane network element is selected by a session management function SMF entity for the terminal device, the first data network access identifier, the at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier are used to determine a first event notification address, and the first event notification address is a destination address for receiving event notification information of the first event; The sending unit is used to send the first information and the second information.

14. The device according to claim 13, characterized in that The second information also includes: a notification association identifier, and the notification association identifier is used to associate the event notification information of the first event with the first information.

15. The device according to claim 13 or 14, characterized in that The second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

16. An application function AF entity, characterized in that: The AF entity includes one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions; When the one or more processors execute the computer instructions, the AF entity is caused to perform the event notification method according to any one of claims 10 to 12.

17. An event notification method, characterized in that: The method comprises: receiving first information and second information, wherein the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of an application server of an application, and the event notification address is a destination address for receiving event notification information, and the destination address is an address of a local capability exposure network element corresponding to the application or an address of an application function AF; The second information is used to subscribe to a first event of a terminal device, where the terminal device is a device that accesses an application server of the application; Sending third information and the first information, wherein the third information is determined according to the second information and is used to subscribe to the first event; The at least one data network access identifier includes a first data network access identifier, the first data network access identifier corresponds to a first user plane network element, the first user plane network element is selected by the session management function SMF entity for the terminal device, the first data network access identifier, the at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier are used to determine a first event notification address, and the first event notification address is a destination address for receiving event notification information of the first event.

18. The method according to claim 17, characterized in that The second information also includes: a notification association identifier, and the notification association identifier is used to associate the event notification information of the first event with the first information. The third information also includes the notification association identifier.

19. The method according to claim 17 or 18, characterized in that The second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

20. An event notification device, characterized in that: The device comprises: a receiving unit and a sending unit; The receiving unit is configured to receive first information and second information, wherein the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of an application server of an application, and the event notification address is a destination address for receiving event notification information, and the destination address is an address of a local capability exposure network element corresponding to the application or an address of an application function AF; the second information is used to subscribe to a first event of a terminal device, and the terminal device is a device for accessing the application server of the application; The sending unit is used to send third information and the first information, wherein the third information is determined according to the second information and is used to subscribe to the first event; The at least one data network access identifier includes a first data network access identifier, the first data network access identifier corresponds to a first user plane network element, the first user plane network element is selected by the session management function SMF entity for the terminal device, the first data network access identifier, the at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier are used to determine a first event notification address, and the first event notification address is a destination address for receiving event notification information of the first event.

21. The device according to claim 20, characterized in that The second information also includes: a notification association identifier, and the notification association identifier is used to associate the event notification information of the first event with the first information. The third information also includes the notification association identifier.

22. The device according to claim 20 or 21, characterized in that The second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

23. A policy control function PCF entity, characterized in that: The PCF entity includes one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions; When the one or more processors execute the computer instructions, the PCF entity is caused to perform the event notification method according to any one of claims 17 to 19.

24. An event notification method, characterized in that: The method comprises: Receive fourth information, a first event notification address and a second event notification address, the fourth information is used to subscribe to a first event of a terminal device, the terminal device is a device for accessing an application server of an application; the first event notification address is a destination address for receiving event notification information of the first event, and the destination address is an address of an application function AF corresponding to the application; the second event notification address is an address of a local capability exposure network element corresponding to a first user plane network element; the first user plane network element is selected by a session management function SMF entity for the terminal device, the first user plane network element corresponds to a first data network access identifier, the first event notification address is determined by the first data network access identifier, at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the at least one data network access identifier includes the first data network access identifier; Fifth information is sent to the first event notification address through the local capability opening network element corresponding to the second event notification address, where the fifth information includes event notification information of the first event.

25. The method according to claim 24, characterized in that The fourth information also includes: a notification association identifier, where the notification association identifier is used to associate the event notification information of the first event with the first event notification address, and the fifth information also includes the notification association identifier.

26. The method according to claim 24 or 25, characterized in that The fourth information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

27. An event notification device, characterized in that: The device comprises a receiving unit and a sending unit, The receiving unit is used to receive fourth information, a first event notification address and a second event notification address, wherein the fourth information is used to subscribe to a first event of a terminal device, and the terminal device is a device for accessing an application server of an application; The first event notification address is a destination address for receiving event notification information of the first event, and the destination address is an address of an application function AF corresponding to the application; The second event notification address is an address of a local capability exposure network element corresponding to the first event notification device; The first event notification device is selected by the session management function SMF entity for the terminal device, the first event notification device corresponds to a first data network access identifier, the first event notification address is determined by the first data network access identifier, at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the at least one data network access identifier includes the first data network access identifier; The sending unit is configured to send fifth information to the first event notification address through the local capability opening network element corresponding to the second event notification address, where the fifth information includes event notification information of the first event.

28. The device according to claim 27, characterized in that The fourth information also includes: a notification association identifier, where the notification association identifier is used to associate the event notification information of the first event with the first event notification address, and the fifth information also includes the notification association identifier.

29. The device according to claim 27 or 28, characterized in that The fourth information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information, and location request information.

30. A user plane function UPF entity, characterized in that: The UPF entity includes one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions; When the one or more processors execute the computer instructions, the UPF entity executes the event notification method as described in any one of claims 24-26.

31. A communication system, characterized in that: The system comprises: a first network element, a second network element, a third network element and a fourth network element; The first network element is used to send first information and second information, the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, the network access identifier is used to indicate the location of an application server of an application, the event notification address is a destination address for receiving event notification information, and the destination address is an address of a local capability exposure network element corresponding to the application or an address of an application function AF; the second information is used to subscribe to a first event of a terminal device, and the terminal device is a device that accesses the application server of the application; The second network element is configured to receive the first information and the second information; and send third information and the first information, wherein the third information is determined according to the second information and is used to subscribe to the first event; The third network element is used to receive the first information and the third information; select a first user plane network element for the terminal device, the first user plane network element corresponds to a first data network access identifier, and the at least one data network access identifier includes the first data network access identifier; send fourth information and a first event notification address; wherein the fourth information is determined according to the third information and is used to subscribe to the first event; the first event notification address is determined according to the first data network access identifier, the at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier; The fourth network element is used to receive the fourth information and the first event notification address; send fifth information to the first event notification address, and the fifth information includes event notification information of the first event.

32. The communication system according to claim 31, characterized in that The first network element is an AF network element, the second network element is a policy control function PCF network element, the third network element is a session management function SMF network element, and the fourth network element is a user plane function UPF network element.

Images