CN114071554A

CN114071554A - Event notification method, device and system

Info

Publication number: CN114071554A
Application number: CN202010763473.2A
Authority: CN
Inventors: 周晓云
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2022-02-18
Also published as: WO2022022345A1

Abstract

The embodiment of the application discloses an event notification method, an event notification device and an event notification system, which relate to the technical field of communication and can acquire a corresponding event report without an application server issuing event subscription information again when UPF (PSA) reselection occurs, so that the acquisition delay of the event report is reduced. The specific scheme is as follows: receiving first information and second information, wherein the first information comprises 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 for indicating the position of an application server of an application, and the event notification address is a destination address for receiving event notification information. The second information is used for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. And selecting a first user plane network element corresponding to the first data network access identifier for the terminal equipment. And sending third information and the first event notification address, wherein the third information is determined according to the second information.

Description

Event notification method, device and system

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to an event notification method, device and system.

Background

In the current communication architecture (e.g., fourth generation mobile communication, or fifth generation mobile communication), the terminal device can interact with the application server after accessing the network. During the interaction, the application server may provide better communication service by sending event subscription information to an access network device (e.g., a User Plane Function (UPF)) that establishes a connection with the terminal device, so as to collect some data (including service-related data and service-unrelated data) of the terminal device during communication with the corresponding application server.

In the fifth generation mobile communication (5G), a terminal device is a User Equipment (UE), and an event subscribed by an application server may be quality of service (QoS) monitoring information. As shown in fig. 1, the application server may send the QoS monitoring request information for the UE to the UPF through an Application Function (AF), a Policy Control Function (PCF), and a Session Management Function (SMF). The UPF can acquire a QoS monitoring event report in the communication process with the UE according to the QoS monitoring request information and feed back the QoS monitoring event report to the AF. The UPF may return the QoS monitoring event report through a path that receives the QoS monitoring request information, that is, the UPF sends the QoS monitoring event report to the corresponding application server through the SMF, the PCF, and the AF. To save the delay for the UPF to return the QoS monitoring event report, the UPF may also directly send the QoS monitoring event report to the AF through a dashed arrow as shown in fig. 1. In general, when the UPF detects an event subscription such as QoS monitoring, the corresponding UE is a UE that establishes a Protocol Data Unit (PDU) session with the UPF.

The UE is often in a mobile state, and as the UE moves, a reselection of the UPF may occur. Thus, when the application server needs to acquire an event report corresponding to the event subscription in the communication process between the UPF and the UE, the application server needs to send the event subscription information to the reselected UPF through the AF, PCF, and SMF again. And the application server cannot quickly acquire the event report corresponding to the monitoring information.

Disclosure of Invention

The application provides an event notification method, an event notification device and an event notification system, when UPF (PSA) reselection occurs due to the movement of terminal equipment and the like, the corresponding event report can be obtained without an application server for issuing event subscription information again, so that the obtaining delay of the event report is reduced, and the signaling overhead of the system is reduced.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, an event notification method is provided, and the method includes: and sending first information and second information, wherein the first information comprises 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 for indicating the position of an application server of the application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an Application Function (AF) corresponding to the application. The second information is used for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. Based on the scheme, the application server can issue the corresponding relation comprising the data network access identification and the corresponding event notification address through the AF. The application server can also issue event subscription information through the AF. Therefore, 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 corresponding relation, so that the application server is not required to issue the event subscription information again through AF, the time delay can be obviously reduced, and the signaling overhead of the system in the process of repeatedly issuing the event subscription information can be reduced. It should be noted that, in different implementation manners, the application server may issue the correspondence and the event subscription information through the same AF, or issue the correspondence and the event subscription information through different AFs.

In one possible design, the second information further includes: and the notification association identifier is used for associating the event notification information of the first event with the first information. Based on the scheme, the AF may also issue association information (e.g., first notification association information) corresponding to the event subscription information, so that when the UPF reports the event, the notification association information may be fed back to the application server at the same time. So that the application server can determine the association of the event report with the transmitted event subscription information based on the association information.

In one possible design, the second information includes at least one of: quality of service, QoS, monitoring request information, QoS notification control request information, and location request information. Based on this scheme, a specific example of the second information is provided, that is, the second information may 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 the QoS-related information is service-related information, and the location request information is non-service-related information, so for other service information and non-service information, the above-mentioned scheme in the first aspect and possible design thereof may be adopted to implement reporting of an event and obtain corresponding beneficial effects, and therefore, the scope of protection of the present application should also be included.

In a second aspect, an event notification apparatus is provided, the apparatus comprising: a determining unit and a transmitting unit. The determining unit is configured to determine 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, the network access identifier is used to indicate a location of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an Application Function (AF) corresponding to the application. The second information is used for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. The sending unit is used for sending the first information and the second information. As an example, the determining unit may specifically determine the specific content of the first information and the second information according to an instruction of the application server.

In one possible design, the second information further includes: and the notification association identifier is used for associating the event notification information of the first event with the first information.

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

In a third aspect, an Application Function (AF) entity is provided, the AF entity comprising one or more processors and one or more memories. One or more memories are coupled to the one or more processors, the one or more memories storing computer instructions. The computer instructions, when executed by one or more processors, cause the AF entity to perform the event notification method as in any one of the first aspect and its possible designs.

In a fourth aspect, a computer-readable storage medium is provided, which comprises computer instructions that, when executed, perform the event notification method according to any one of the first aspect and its possible implementations.

In a fifth aspect, a chip system is provided, the chip comprising processing circuitry and an interface. The processing circuit is configured to invoke and run a computer program stored in a storage medium from the storage medium to execute the event notification method according to any one of the first aspect and its possible implementations.

It should be understood that the solutions provided in the second aspect, the third aspect, the fourth aspect and the fifth aspect all can correspond to the first aspect or possible designs thereof, and therefore beneficial effects that can be obtained are similar and will not be described herein again.

In a sixth aspect, there is provided an event notification method, the method comprising: receiving first information and second information, wherein the first information comprises 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 for indicating the position of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an Application Function (AF) corresponding to the application. The second information is used for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. And sending third information and the first information, wherein the third information is determined according to the second information and is used for subscribing 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 a responsive process on the first information and the second information, so as to facilitate a responsive process by other network elements. For example, the core network element may be a PCF, and the PCF may generate a corresponding PCC rule according to the first information and the second information, and issue the PCC rule to another network element (e.g., SMF). The PCC rule may include at least one data network access identifier, an event notification address (e.g., first information) corresponding to the at least one data network access identifier, 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 according to the second information (for example, the PCF performs transcoding or other processing on the content of the second information to obtain the third information). It should be noted that, for some events corresponding to the time subscription information, the events correspond to the terminal device, and therefore, the PCC rule may further include identification information of the target terminal device. The identification information may be used to indicate a terminal device or a group of terminal devices.

In one possible design, the second information further includes: and the notification association identifier is used for associating the event notification information of the first event with the first information, and the third information further comprises the notification association identifier. Based on the scheme, the AF may also issue association information (e.g., first notification association information) corresponding to the event subscription information, so that when the UPF reports the event, the notification association information may be fed back to the application server at the same time. So that the application server can determine the association of the event report with the transmitted event subscription information based on the association information.

In a seventh aspect, an event notification apparatus is provided, which includes: a receiving unit and a transmitting unit. The receiving unit is configured to receive 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, the network access identifier is used to indicate a location of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is 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 for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. The sending unit is configured to send third information and the first information, where the third information is determined according to the second information and is used to subscribe to the first event.

In one possible design, the second information further includes: and the notification association identifier is used for associating the event notification information of the first event with the first information, and the third information further comprises the notification association identifier.

In an eighth aspect, a Policy Control Function (PCF) entity is provided, the PCF entity comprising one or more processors and one or more memories. One or more memories are coupled to the one or more processors, the one or more memories storing computer instructions. The computer instructions, when executed by one or more processors, cause the PCF entity to perform the event notification method as in any one of the sixth aspect and its possible designs.

A ninth aspect provides a computer readable storage medium comprising computer instructions which, when executed, perform the event notification method of any of the sixth aspect and possible implementations thereof.

In a tenth aspect, a chip system is provided, the chip comprising processing circuitry and an interface. The processing circuit is configured to invoke and run a computer program stored in a storage medium from the storage medium to execute the event notification method according to any one of the sixth aspect and possible implementations thereof.

It should be understood that the solutions provided in the seventh aspect, the eighth aspect, the ninth aspect and the tenth aspect can all correspond to the sixth aspect or possible designs thereof, so that similar beneficial effects can be obtained, and further description thereof is omitted here.

In an eleventh aspect, there is provided an event notification method, including: receiving first information and second information, wherein the first information comprises 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 for indicating the position of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an Application Function (AF) corresponding to the application. The second information is used for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. And selecting a first user plane network element for the terminal equipment, wherein the first user plane network element corresponds to a first data network access identifier, and at least one data network access identifier comprises the first data network access identifier. Third information is sent, along with a first event notification address. And the third information is determined according to the second information and is used for subscribing 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. Based on the scheme, the network element can receive information from other network elements and perform response processing. Illustratively, the network element may be an SMF. The SMF may receive a PCC rule from the PCF, which may include the first information and the second information. The SMF may select a corresponding UPF for the terminal device as the PSA based on the DNAI in the first information. The SMF knows the correspondence between the DNAI and the event notification address, so the SMF can also know the feedback address of the report corresponding to the event subscribed by the second information. The SMF may send the third information corresponding to the event subscription information and the corresponding event notification address to the UPF, so that the UPF may obtain and feed back the event report accordingly. The third information may be determined according to the second information, and in different embodiments, the third information may be the same as the second information or different from the second information.

In one possible design, a second event notification address is sent, the second event notification address being an address of a local capability openness network element corresponding to the first user plane network element. Based on this scheme, the SMF may also issue to the UPF the address of the NEF corresponding to the currently selected PSA. Illustratively, in general, if a local NEF is provided in the system architecture, the NEF may be corresponding to a local AF. In some scenarios, the event report may need to be reported to other NEFs (e.g., NEFs in the central DC) first, and therefore, the SMF may send the address of the NEF to the UPF together, so that the UPF can report the event report to the correct address.

In one possible design, the method further includes: and selecting a corresponding second user plane network element for the terminal equipment of the application server accessing the application, wherein the second user plane network element corresponds to a second data network access identifier, and at least one data network access identifier comprises the second data network access identifier. And sending the fourth information and the third event notification address. And the fourth information is determined according to the second information and is used for subscribing the first event. The third event notification address is determined according to the second 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. Based on the scheme, when the PSA reselection is required (for example, the terminal device moves), the SMF may select a new UPF for the terminal device as the PSA according to the DNAI in the PCC rule. The DNAI corresponding to the updated PSA has an updated event notification address, so that the SMF can send the updated event notification address to the UPF after reselecting the PSA, so that the UPF can perform correct event reporting according to the address.

In one possible design, the method further includes: and sending a fourth event notification address, wherein 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 the scheme, a processing scheme when PSA reselection occurs is provided. For example, when the PSA is reselected, the SMF may determine, according to the DNAI corresponding to the reselected PSA, an address (e.g., a fourth event notification address) to report an event report after performing PSA reselection. The SMF may issue the updated reporting address to the corresponding updated UPF, so that the UPF may obtain the corresponding event report according to the event subscription information and report the event report to the updated address.

In one possible design, the second information further includes: and the notification association identifier is used for associating the event notification information of the first event with the first information, and the fourth information further comprises the notification association identifier. Based on the scheme, the SMF may send a corresponding notification association identifier when sending an updated event notification address, so that the application server can determine the association of the event report with the sent event subscription information according to the association information.

In a twelfth aspect, there is provided an event notification apparatus, comprising: a receiving unit and a transmitting unit. The receiving unit is used for receiving first information and second information, wherein the first information comprises 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 for indicating the position of an application server of the application, the event notification address is a destination address for receiving the event notification information, and the destination address is 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 for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. And selecting a first user plane network element for the terminal equipment, wherein the first user plane network element corresponds to a first data network access identifier, and at least one data network access identifier comprises the first data network access identifier. And a transmitting unit for transmitting the third information, and the first event notification address. And the third information is determined according to the second information and is used for subscribing 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.

In a possible design, the sending unit is further configured to send a second event notification address, where the second event notification address is an address of a local capability openness network element corresponding to the first user plane network element.

In a possible design, the apparatus further includes a configuration unit, configured to select a corresponding second user plane network element for a terminal device of an application server accessing the application, where 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. And sending the fourth information and the third event notification address. And the fourth information is determined according to the second information and is used for subscribing the first event. The third event notification address is determined according to the second 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.

In a possible design, the sending unit is further configured to send a fourth event notification address, where the fourth event notification address is an address of a local capability openness network element corresponding to the second user plane network element.

In one possible design, the second information further includes: and the notification association identifier is used for associating the event notification information of the first event with the first information, and the fourth information further comprises the notification association identifier.

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. One or more memories are coupled to the one or more processors, the one or more memories storing computer instructions. The computer instructions, when executed by one or more processors, cause the SMF entity to perform the event notification method of any one of the eleventh aspects and possible designs thereof.

In a fourteenth aspect, a computer-readable storage medium is provided, which comprises computer instructions that, when executed, perform the event notification method according to any one of the eleventh aspect and its possible implementations.

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

It should be understood that the solutions provided in the twelfth aspect, the thirteenth aspect, the fourteenth aspect and the fifteenth aspect can all correspond to the eleventh aspect or possible designs thereof, and therefore similar beneficial effects can be obtained, and are not described herein again.

In a sixteenth aspect, there is provided an event notification method, comprising: the method comprises the steps of receiving first information, a first event notification address and a second event notification address, wherein the first information is used for subscribing a first event of a terminal device, and the terminal device is a device of an application server accessing 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 corresponding to the application function AF. The second event notification address is an address of a local capability openness network element corresponding to the first user plane network element. And sending second information to the first event notification address through the local capability open network element corresponding to the second event notification address, wherein the second information comprises the event notification information of the first event. Based on the scheme, the UPF may receive the first information from the SMF, and obtain the event report according to 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 the UPF from the first information are the latest addresses determined by the SMF, the UPF can obtain the correct event notification address on the premise that the AF does not repeatedly issue the event subscription information regardless of whether the PSA is reselected, so that the UPF can smoothly report the event report on the premise that the AF does not repeatedly issue the event subscription information.

In one possible design, the first information further includes: and the notification association identifier is used for associating the event notification information of the first event with the event notification address, and the second information further comprises the notification association identifier. Based on the scheme, the AF may also issue association information (e.g., first notification association information) corresponding to the event subscription information, so that when the UPF reports the event, the notification association information may be fed back to the application server at the same time. So that the application server can determine the association of the event report with the transmitted event subscription information based on the association information.

In one possible design, the first information includes at least one of: quality of service, QoS, monitoring, request information, QoS notification control, request information, and location request information. Based on this scheme, a specific example of the second information is provided, that is, the second information may 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 the QoS-related information is service-related information, and the location request information is non-service-related information, so for other service information and non-service information, the above-mentioned scheme in the first aspect and possible design thereof may be adopted to implement reporting of an event and obtain corresponding beneficial effects, and therefore, the scope of protection of the present application should also be included.

In a seventeenth aspect, an event notification apparatus is provided, which may include a receiving unit and a transmitting unit. The terminal device comprises a receiving unit, a first event notification unit and a second event notification unit, wherein the receiving unit is used for receiving first information, a first event notification address and a second event notification address, the first information is used for subscribing a first event of the terminal device, and the terminal device is a device of an application server accessing 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 corresponding to the application function AF. The second event notification address is an address of a local capability openness network element corresponding to the first user plane network element. A sending unit, configured to send second information to the first event notification address through the local capability open network element corresponding to the second event notification address, where the second information includes event notification information of the first event.

In one possible design, the first information further includes: and the notification association identifier is used for associating the event notification information of the first event with the event notification address, and the second information further comprises the notification association identifier.

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

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. One or more memories are coupled to the one or more processors, the one or more memories storing computer instructions. The computer instructions, when executed by the one or more processors, cause the UPF entity to perform the event notification method as described in any one of the sixteenth aspect and its possible world.

A nineteenth aspect provides a computer-readable storage medium comprising computer instructions which, when executed, perform the event notification method of any of the sixteenth aspects and possible implementations thereof.

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

It should be understood that the solutions provided in the seventeenth aspect, the eighteenth aspect, the nineteenth aspect, and the twentieth aspect can all correspond to the sixteenth aspect or possible designs thereof, and therefore similar beneficial effects can be obtained, and are not described herein again.

In a twenty-first aspect, there is provided a communication 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 for sending first information and second information, the first information comprises 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 for indicating the position of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is 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 for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. And the second network element is used for receiving the first information and the second information. And sending third information and the first information, wherein the third information is determined according to the second information and is used for subscribing the first event. And the third network element is used for receiving the first information and the third information. And selecting a first user plane network element for the terminal equipment, wherein the first user plane network element corresponds to a first data network access identifier, and at least one data network access identifier comprises the first data network access identifier. The fourth information is sent, along with the first event notification address. And the fourth information is determined according to the third information and is used for subscribing 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. And the fourth network element is used for receiving the fourth information and the first event notification address. And sending fifth information to the first event notification address, wherein the fifth information comprises event notification information of the first event.

In a 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.

It is to be understood that the technical features of the communication system and its possible design provided by the twenty-first aspect described above can correspond to the method described in any one of the 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 therefore the same advantageous effects can be achieved.

Drawings

FIG. 1 is a schematic diagram of a network architecture;

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

fig. 3 is a deployment diagram of a communication architecture provided by an embodiment of the present application;

fig. 4 is a deployment diagram of another communication architecture provided by an embodiment of the present application;

fig. 5 is a deployment diagram of another communication architecture provided by an embodiment of the present application;

fig. 5A is a schematic flowchart of an event notification method according to an embodiment of the present application;

fig. 6 is a schematic flowchart of another event notification method according to an embodiment of the present application;

fig. 7 is a schematic flowchart of another event notification method according to an embodiment of the present application;

fig. 8 is a schematic flowchart of another event notification method according to an embodiment of the present application;

fig. 9 is a schematic flowchart of another event notification method according to an embodiment of the present application;

figure 10 is a schematic diagram of a PSA reselection provided by an embodiment of the present application;

fig. 11 is a schematic flowchart of another event notification method according to an embodiment of the present application;

fig. 12 is a schematic diagram illustrating an event notification apparatus according to an embodiment of the present application;

fig. 13 is a schematic composition diagram of an application function entity according to an embodiment of the present application;

fig. 14 is a schematic composition diagram of a chip system according to an embodiment of the present disclosure;

fig. 15 is a schematic diagram illustrating a composition of another event notification apparatus according to an embodiment of the present application;

fig. 16 is a schematic composition diagram of a policy control function entity according to an embodiment of the present application;

FIG. 17 is a schematic diagram illustrating a further system-on-chip according to an embodiment of the present disclosure;

fig. 18 is a schematic diagram illustrating a composition of another event notification apparatus according to an embodiment of the present application;

fig. 19 is a schematic diagram illustrating a session management function entity according to an embodiment of the present application;

FIG. 20 is a block diagram of another chip system provided in an embodiment of the present application;

fig. 21 is a schematic diagram illustrating a composition of another event notification apparatus according to an embodiment of the present application;

fig. 22 is a schematic composition diagram of a user plane functional entity according to an embodiment of the present application;

fig. 23 is a schematic composition diagram of another chip system provided in the embodiment of the present application.

Detailed Description

Currently, after the terminal device moves, in order to implement path optimization for service access, the terminal device may reselect a locally deployed UPF and an application server. If the application server still needs to obtain the event report, the event needs to be re-subscribed. This can result in delays in the UPF acquiring and feeding back the event reports.

In order to solve the above problem, an embodiment of the present invention provides an event notification method, which is capable of instructing a UPF to report an acquired event report to a corresponding address according to an event notification address corresponding to a new UPF configured for the core network element (e.g., a session management function) by an application server when a UPF changes due to a terminal device moving or the like. Therefore, the application server does not need to send the event subscription information again through AF, PCF and SMF, thereby remarkably saving the communication times among different network elements and ensuring the quick feedback of the event report while saving the signaling overhead.

The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

First, an environment in which the method is applied will be described.

Please refer to fig. 2, which is a logic diagram of a communication architecture according to an embodiment of the present application.

As shown in fig. 2, the communication architecture may include a terminal device, RAN, UPF, AMF, SMF, PCF, and AF.

Application Function (AF). The AF may be a corresponding one of the functional entities of the application server. In different implementations, one application server may correspond to one or more AFs. For example, in this embodiment of the present application, the application server may issue event subscription information through an AF, so as to subscribe to a corresponding UPF to obtain and report a corresponding event report. In some implementations, the application server may further issue, through the AF, 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. It should be noted that, in the present application, the application server may issue the event subscription information and the information corresponding to the address through the same AF. In other implementation manners, the application server may also issue the event subscription information through different AFs, where the event subscription information corresponds to the address. Of course, the AF that the application server receives the event report may be the same as or different from the AF that transmits the event subscription information and/or the address correspondence information. The embodiments of the present application do not limit this.

Policy Control Function (PCF). The PCF may be configured to customize a corresponding Policy and Charging Control (PCC) rule based on the message from the AF. And sending the PCC rule to other network elements so that the other network elements can execute corresponding events according to the PCC rule. For example, in this embodiment of the present application, the PCF may be configured to customize, according to the address correspondence information from the AF, a PCC rule including an address correspondence relationship, and send the PCC rule to another network element, so that the other network element can obtain, according to the PCC rule, a correspondence relationship between an event report notification address and a data network access identifier. The PCF may also be configured to customize a corresponding PCC rule according to event subscription information from an AF (or a Network Exposure Function (NEF)), or update an existing PCC rule, and send the PCC rule to another network element, so that the other network element may execute a corresponding event according to the PCC rule and feed back an event report to a corresponding address.

Session Management Function (SMF). The SMF is mainly responsible for interacting with a separate data plane, creating, updating, and deleting PDU sessions, and managing a session context (session context) with the UPF. For example, in this embodiment of the present application, the SMF may be configured to receive a PCC rule of the PCF, and execute a corresponding event according to the PCC rule. For example, the SMF may be configured to select a corresponding UPF for the terminal device according to the data network access identifier included in the PCC rule. In different embodiments, the SMF may use the UPF closest to the terminal device as a protocol data unit Anchor (PDU Session Anchor, PSA) for establishing a PDU Session with the terminal device. In other embodiments, the SMF may also configure the PSA for the terminal device according to other rules, e.g., the SMF may configure the PSA for the terminal device according to historical communication quality. The embodiments of the present application do not limit this. The SMF may be further configured to receive the PCC rule including address correspondence information and event subscription information, determine a corresponding event report notification address according to the currently selected PSA selection for the terminal device, and send the address and the event subscription information to the corresponding PSA, so that the PSA performs a corresponding operation.

Core network access and mobility management function (AMF). Illustratively, the AMF is mainly responsible for access authentication of the terminal device, mobility management, signaling interaction between functional network elements, and other operations, such as: and managing the registration state of the user, the connection state of the user, the user registration and network access, the tracking area updating, the cell switching user authentication, the key safety and the like.

User Plane Function (UPF). Illustratively, the UPF may establish a PDU session with a corresponding terminal device according to information sent by the SMF, so as to implement functions such as packet routing and forwarding, packet inspection, and user plane part policy rule implementation. In this embodiment of the present application, the UPF may execute a corresponding event according to the event subscription information from the SMF, and acquire a corresponding event report. The UPF can also feed back the event report through an event report notification address sent by the SMF, so that when the UPF reselects after the UE moves, the AF does not need to send the event subscription information again, and the application server can also obtain the corresponding event report.

The terminal equipment may include User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), or the like. As an example, the terminal device may be a mobile phone (mobile phone), a tablet computer or a computer with a wireless transceiving function, and may also be 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 a smart grid, a wireless terminal device in a smart city (smart city), a smart home, and a vehicle-mounted terminal device. In this example, the terminal device may communicate with a Data Network (DN) by establishing a PDU session with the UPF. The following description will be given taking a terminal device as a UE as an example.

A Radio Access Network (RAN), which is an access network element providing a radio access service. For example, in a 5G communication system, the network element may be referred to as an 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 (pg) terminal to the terminal device, and is connected to the 5G core network via an NG interface. The RAN may also be a node providing evolved universal terrestrial radio access network (E-UTRAN) user plane and control plane protocol terminals to the terminal devices and connected to the 5G core network via the NG interface.

To extend the network functionality of the AF, in some embodiments, the network architecture may also include a NEF. The NEF is an example of a capability openness network element, and in other implementations, the NEF may also be replaced by another capability openness network element. Illustratively, the NEF may be provided at the AF front end for performing secondary processing on information sent/received by the AF, so as to enable address protection and the like for the AF while ensuring the AF communication function. In this embodiment, the NEFs may be disposed in the local network, each NEF may be configured with an address (e.g., referred to as NEF address), and the NEF may receive the event report reported from the UPF through the corresponding NEF address. When the event subscription information corresponding to the event report is subscribed by the AF at the back end of the NEF, the NEF may further be configured to send the received event report to the AF corresponding to the local NEF. To enable the event report to be a feedback to the application server. In other embodiments, NEFs may also be provided in the central network, serving similar functions as local NEFs. It should be understood that in some implementations, different NEFs may be set in both the central network and the local network to achieve multiple levels of network functionality expansion.

Specifically, as a possible deployment manner, fig. 3 to 5 show a specific deployment method based on the logic diagram shown in fig. 2. Among them, hierarchical management of data can be realized by providing a Data Center (DC) on a plurality of layer sides. For example, a central DC (central DC) may be provided that covers a larger area, and one or more local DCs may also be included in the coverage area of the central DC.

In one possible deployment, as shown in fig. 3, AMF, SMF, PCF, and NEF may be located at the central DC. It should be noted that one or more local DCs may also be deployed at different locations. For convenience of explanation, the central DC and one local DC are taken as examples in the embodiment of the present application. UPF, as well as AF, may be set in the local DC. In the embodiment of the present application, the UPF set in the local DC may be referred to as local UPF (local UPF), and the AF set in the local DC may be referred to as local AF (local AF).

For example, in the deployment shown in fig. 3, data interaction of each network element is exemplarily illustrated by taking an example of sending QoS monitoring request information by an AF. The AF may issue a message including the QoS monitoring request information to the NEF through the N33 interface, and the NEF may transmit the message to the PCF through the N6 interface. The PCF can customize the corresponding PCC rules and send the PCC rules to the SMF through the N7 interface. The SMF may issue the related signaling to the AMF through an N11 interface, so that the AMF performs corresponding signaling interaction with the terminal device through an N1 interface and/or performs corresponding signaling interaction with the RAN through an N2 interface. The SMF may also send the QoS monitoring request information and an event report notification address (e.g., an address of an AF) corresponding to the QoS monitoring request information to the UPF through the N4 interface. And the UPF performs corresponding monitoring according to the QoS monitoring request information to acquire an event report. The UPF may then feed back the event report to the AF with the corresponding event report notification address via the N4a interface.

With reference to the above description, when the UPF sends an event report, the corresponding transmission channel is selected according to the event notification address issued by the SMF. In the deployment shown in fig. 3, it is exemplified that the event notification address issued by the SMF is the same as the AF that issued the QoS monitoring request message, so the UPF can feed back the event report to the AF. In other implementation manners, when the event notification address issued by the SMF is different from the AF that issued the QoS monitoring request information, the UPF sends the corresponding event report to the corresponding network element according to the event notification address.

In other deployments, as shown in fig. 4, the NEF may also be located in the local DC. Thus, after the event report is acquired by the UPF, it can 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.

In other deployments, as shown in fig. 5, multiple NEFs may be deployed simultaneously to achieve multi-level expansion of network functionality. Fig. 5 illustrates an example of setting one NEF in each of the local DC and the central DC (e.g., setting NEF1 in the local DC and NEF2 in the central DC). Thus, when the AF issues event subscription information (e.g., QoS monitoring request information), the information may be sent to NEF1 through an N33 interface, and NEF1 may forward (or send after transcoding) the information to NEF2 through an N33a interface. So that NEF2 can pass this information on until it is released to the UPF. The UPF may send the event report to NEF1 through the N4a interface after acquiring the corresponding event report. Such that NEF1 sends the event report to the corresponding application server.

The event notification method provided in the embodiment of the present application may be applied to a network architecture in which 4G/5G service capabilities are intercommunicated, and may also be applied to a future 6th generation (6G) communication system or other communication systems, which is not limited in this application. Illustratively, the method may be applied in a communication network having a logical schematic as shown in fig. 2, and may also be applied in a communication network deployed as shown in fig. 3 or fig. 4 or fig. 5.

The following describes in detail an event notification method provided in an embodiment of the present application.

Please refer to fig. 5A, which is a flowchart illustrating an event notification method according to an embodiment of the present disclosure. The method may be applied in a communication network as shown in fig. 3 or fig. 4 or fig. 5, or the method may be applied in other communication networks having the logic shown in fig. 2. The following description will be given taking as an example the application of this method to a communication network as shown in fig. 4.

As shown in fig. 5A, the method may include S501-S508.

S501, the AF sends the first information and the second information.

The first information may include 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 a location of an application server of the application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an application function AF corresponding to the application.

As an example, the data network access identifier may be a Data Network Access Identifier (DNAI). It should be appreciated that DNAI may be used to indicate the location of an application server for an application. When an application deploys multiple application servers, the application server at each location may correspond to one DNAI. It should be understood that an event report generally needs to be reported to an AF or NEF that subscribes to the corresponding event. Referring to fig. 4, the AF and NEF applied in the local DC are generally set correspondingly, and there may be a correspondence between the application server and the AF. Thus, the DNAI corresponding to one application server has a corresponding relationship with the AF (and/or NEF). In this example, a correspondence relationship between the DNAI and an address (e.g., referred to as a destination address) where the AF or NEF receives the event report (or referred to as event notification information), that is, the at least one data network access identifier and the event notification address corresponding to the at least one data network access identifier, may be established. And the first information is carried in the first information and is sent to other core network elements, such as PCF and the like. In this embodiment, a correspondence between a data network access identifier and a corresponding event notification address may be referred to as address correspondence information.

The second information is used for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. It should be noted that the second information may be used to subscribe to an event related to a service. For example, 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 may also be used to subscribe to events that are not related to the service. Illustratively, the second information may include location request information.

In addition, the first information and the second information may be issued by the same AF in one message flow controlled by the application server, or by different AFs controlled by the application server. The embodiments of the present application do not limit this.

In some embodiments of the present application, the second information may further include a notification association identifier, and the notification association identifier is used to associate event notification information of the first event with the first information. It should be understood that, since the first information and the second information may be issued in different message flows, it is necessary to enable other core network elements (e.g., PCF, SMF, etc.) to know the association between the address correspondence information in the first information and the first event subscribed in the second information through the above notification association identifier.

S502, the PCF receives the first information and the second information.

The first information comprises at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, wherein the network access identifier is used for indicating the position of an application server of the application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an Application Function (AF) corresponding to the application.

The second information is used for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application.

S503, the PCF sends the third information and the first information.

And the third information is determined according to the second information and is used for subscribing the first event. It should be appreciated that in some implementations, after receiving the second information, the PCF may process the second information for transmission to another network element (e.g., SMF). As an example, the PCF may encapsulate the address correspondence information included in the first information and the correspondence information for subscribing to the first event indicated in the second information in the PCC rule, and send the PCC rule to the SMF. Wherein, the information in the PCC rule for indicating subscription to the first event may be the same as the second information, i.e., the third information is the same as the second information. The information in the PCC rule indicating that it is specified for the first event may also be different from the second information, i.e. 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.

In some embodiments, when the second information received by the PCF further includes the first association identifier, the PCF may issue the first association identifier to the SMF together. Illustratively, the PCF may carry the first association identifier in the PCC rule and issue the PCC rule to the SMF.

It should be noted that, the above description is given by taking an example that the PCF encapsulates the first information, the third information, and the first association identifier in the PCC rule and issues the first information, the third information, and the first association identifier, in some other implementation manners, the PCF may also issue the first information, the third information, and the first association identifier to other network elements (such as SMF) in other manners. The PCF may send the first information, the third information and the first association identifier in the same message flow, or the PCF may send the first information, the third information and the first association identifier in different message flows, respectively. The method for the PCF to issue the first information, the third information and the first association identifier is not limited in the embodiment of the present application.

S504, the SMF receives the first information and the third information.

The first information comprises 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 for indicating the position of an application server of the application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an Application Function (AF) corresponding to the application.

The third information is used for subscribing to a first event of a terminal device, which is a device of an application server accessing the application.

With reference to the description in S503, the SMF may receive the first information and the third information by receiving the PCC rule sent by the PCF.

S505, the SMF selects a first user plane network element for the terminal equipment.

The first user plane network element corresponds to a first data network access identifier, and at least one data network access identifier comprises the first data network access identifier.

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

After choosing to determine the PSA, the SMF may determine the corresponding event notification address according to the first information (which may include address correspondence information) in the PCC rules, in combination with the DNAI corresponding to the current PSA.

And when the PSA is reselected due to the movement of the terminal device, the SMF may reselect the corresponding UPF for the terminal device as the PSA according to the DNAI included in the PCC rule. After determining the reselected PSA, the SMF may determine a corresponding event notification address in accordance with the first information in the PCC rules (which may include address correspondence information), in conjunction with the DNAI corresponding to the current PSA. It can be seen that when the PSA reselection occurs, since the SMF can know the correspondence between different DNAIs and event notification addresses, after the SMF reselects the PSA for the terminal device, the SMF can determine the event notification address corresponding to a new PSA through the correspondence (i.e., address correspondence information) without the AF having to re-issue the event subscription information. Therefore, the reporting time delay of the corresponding event can be greatly saved. In this example, the event notification address corresponding to the PSA may be referred to as a first event notification address.

It should be noted that in other embodiments, there may be situations where the event report needs to be forwarded through other NEFs before it can be sent to the first event notification address. In this example, the SMF may further obtain an address (for example, referred to as a second event notification address) of the forwarding NEF, so as to send the second event notification address to the UPF together, so that the UPF can report the event report to the first event notification address through the second event notification address.

S506, the SMF sends fourth information and a first event notification address.

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

The fourth information may be determined from the third information for subscribing to the first event. As an example, the first event notification address may be determined by the SMF according to the first data network access identifier, the at least one data network access identifier and an event notification address (such as the address correspondence information described above) corresponding to the at least one data network access identifier.

In addition, similar to the above description, a notification association flag may be further included in the fourth information, for associating the event notification information of the first event with the event notification address.

It should be appreciated that when the SMF determines the address (e.g., second event notification address) to forward the NEF, the SMF may issue 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 may be issued in the same message, or may be issued in different messages. The embodiment of the present application does not limit the issuing manner of the related information.

And S507, the UPF receives the fourth information and the first event notification address.

The UPF may be a first user plane network element selected by the SMF for the terminal device. The first information is used for subscribing a first event of a terminal device, and the terminal device is a device of an application server accessing the 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 corresponding to the application function AF.

In conjunction with S506, the UPF may further receive a second event notification address, where the second event notification address may be an address of a local capability openness network element corresponding to the first user plane network element. The first user plane network element can realize the report of the event report to the first event notification address through the second event notification address.

It should be noted that, in this example, the second event notification address may be an address of the NEF used for forwarding the event report. Of course, the second event notification address may also be an address of another network element that can implement the function of forwarding the event report to the network element having the first event notification address. The embodiments of the present application do not limit this.

Illustratively, the address of the NEF forwarding the event report is taken as the second event notification address. The UPF may receive an address (e.g., a second event notification address) of the NEF having the forwarding function. So that after acquiring the event report, the event report and the corresponding destination address (e.g. the first event notification address) can be sent together to the NEF corresponding to the second event notification address, and further the NEF can send the event report to the network element corresponding to the first event notification address.

And S508, the UPF sends fifth information.

Wherein the fifth information may include event notification information of the first event. For example, when the first event includes QoS monitoring request information, the fifth information may include an event report corresponding to the QoS monitoring request. When the first event includes the 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 the location request information, the fifth information may include an event report corresponding to the location request information.

It should be appreciated that when the UPF also receives the second event notification address, then the fifth information may be sent to the second event notification address. The UPF may further send the first event notification address to a network element (e.g., 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.

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 (e.g., AF or NEF) corresponding to the first event notification address.

In addition, in some embodiments, a notification association identifier may be further included in the fifth information, so that the network element receiving the event report can specify an association between the event notification information of the first event and the event notification address according to the notification association identifier.

Based on the above description regarding the method as shown in fig. 5A, the SMF may determine the event notification address of the event report of the event subscription information based on the current PSA corresponding DNAI and the address corresponding information. Therefore, when the PSA is reselected, the SMF knows the correspondence between all DNAIs and the event notification addresses, and thus does not need the AF to re-issue the event subscription information, and the SMF can determine the event notification address corresponding to the new PSA and issue the new event notification address to the UPF for the UPF to accurately report. Therefore, the time delay of reporting the event report can be obviously reduced, and meanwhile, the signaling interaction between the core network elements can be saved.

In order to enable those skilled in the art to more accurately understand the method shown in fig. 5A, the following description is further provided with reference to examples. Fig. 6 shows a specific implementation of sending address correspondence information by the AF. Fig. 7 is an example of a method for implementing PSA selection based on fig. 6. Fig. 8 shows an example of issuing event subscription information and reporting a corresponding event report. Fig. 9 shows an example of event reporting in a PSA reselection scenario. Fig. 11 shows an example of issuing and reporting event subscription information in a scenario where a subscription event is a non-service related event. The methods shown in fig. 6, fig. 7, fig. 8, fig. 9, and fig. 11 can be applied to the logical architecture shown in fig. 2, and can be applied to the deployment shown in fig. 3, fig. 4, or fig. 5.

It should be noted that, in the following example, the terminal device is taken as the UE, the application server issues the data network access identifier and the event notification address (for example, referred to as address corresponding information) corresponding to the data network access identifier through the same AF, the event subscription information, and receives the event report, and the method is applied to the network architecture shown in fig. 4 as an example.

Illustratively, the AF may implement the configuration of the address correspondence information according to the method shown in fig. 6.

As shown in fig. 6, the method may include S601-S603.

S601, AF sends information 6-1 to NEF.

Wherein the information 6-1 may include address correspondence information. In the address correspondence information, at least one data network access identification and an event notification address corresponding to the at least one data network access identification may be included. For example, in some embodiments, a data network access identifier may correspond to an event notification address. In other embodiments, one data network access identification may also correspond to multiple event notification addresses. The following description is given by way of example, in which a data network access identifier may correspond to an event notification address.

As a possible implementation, the information 6-1 may be transmitted through an Nnef _ trafficinfiluence _ Create Request message. The data network access identification may be a DNAI. The event notification address may be a reception address of an event report corresponding to the DNAI. The event notification address may be a NEF address corresponding to an application server of the application, or may be an AF address corresponding to an application server of the application.

It should be understood that DNAI represents location information of an application, i.e., location information of an application server of the application. One application may be provided with a plurality of different application servers respectively 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 interact with the PCF by the AF. Thus, an application server may generally correspond to an AF address, and thus the DNAI may also correspond to an AF. If a local NEF is deployed in the local DC, the DNAI may also correspond to one NEF. In the example, the address correspondence information may include a correspondence relationship between DNAI corresponding to each AF and the AF reception event notification address in different local DCs. So that other network elements (such as the SMF) can determine the address of the AF or NEF capable of receiving the event report according to the DNAI corresponding to the selected local UPF.

In some implementations, the information 6-1 may also include Traffic Steering Info, which may include Application Service Provider (ASP) identification, service description information, and identification of the corresponding UE. It should be understood that different applications may have multiple application servers located in different local DCs. Correspondingly, a plurality of application servers may be provided in the local DC for supporting respective services of different applications. Thus, in this example, the information 6-1 may further include ASP identification capable of identifying the application, service description information, and identification information of the target UE (such as an IP address of the UE, indication information of an arbitrary UE, external identification of the UE, or external group identification).

S602, NEF sends information 6-2 to PCF.

After the NEF acquires the information 6-1 from the AF, it may process it, for example, perform transcoding, so as to hide the information 6-1, thereby achieving the purpose of protecting the AF. For example, NEF may map the external group identifier in the nfo _ trafficlnfluency _ Create Request to the internal group identifier, and map the external identifier of the UE to the internal identifier. The NEF may then send information 6-2 obtained from information 6-1 to the PCF. The NEF may send information 6-2 directly to the PCF or the NEF may send information 6-2 to the PCF via a Unified Data Repository (UDR) that provides Data storage services.

As an example, if the identification information of the target UE is the IP address of the UE, the NEF sends the PCF via the Npcf _ PolicyAuthorization Request. The information 6-2 includes related information indicating address correspondence information, and ASP identification, service description information. The operation is similar to the related information in S601, and is not described in detail here.

As an example, if the identification information of the target UE is indication information of an arbitrary UE, an external identification of the UE, or an external group identification, the NEF may transmit the information 6-2 to the UDR through the nurr _ DM _ Update Request. The UDR may store this Nudr _ DM _ Update Request after it is received. For PCF needing to obtain the information, it generally subscribes to corresponding Traffic Steering Info from UDR, and UDR can send Nudr _ DM _ Update Request to PCF subscribing to corresponding Traffic Steering Info. Thereby enabling transmission of information 6-2 to the PCF.

It should be noted that, in the embodiment of the present application, when the NEF is set between the AF and the PCF, the information 6-2 may correspond to the first information in the scheme shown in fig. 5A. And when the NEF is not set between the AF and the PCF, the above-mentioned information 6-1 may correspond to the first information in the scheme shown in fig. 5A.

S603, PCF generates a first PCC rule according to the information 6-2.

After receiving the information 6-2, the PCF may generate a corresponding PCC rule according to the information 6-2, so that other network elements may perform corresponding operations according to the PCC rule.

Illustratively, the PCF may customize the corresponding PCC rule (e.g., referred to as PCC rule 1) upon receiving the nurr _ DM _ Update Request. In the PCC rule 1, DNAI may be included only or a correspondence relationship between DNAI and an event notification address may be included. For example, the Nudr _ DM _ Update Request includes the correspondence between a plurality of DNAIs corresponding to the application 1 and the event notification address. In the PCC rule 1, a plurality of DNAIs corresponding to the application 1 or a correspondence relationship between the DNAIs and the event notification address may be included.

It should be understood that, in this example, the address correspondence information included in the first PCC rule may be the same as the address correspondence information in the first information in the scheme shown in fig. 5A.

Therefore, the application of the corresponding address corresponding information is embodied in the PCC rule.

It should be understood that when the UE establishes the PDU session or the UE establishes the PDU session, the SMF may select a corresponding UPF for the UE as the PSA according to the PCC rule.

For example, referring to fig. 7, the PCF may send the first PCC rule to the SMF (i.e., perform S701). When or after the UE establishes the PDU session, the SMF may select a UPF for the UE as the PSA according to the first PCC rule (i.e., DNAI) (i.e., perform S702). As a possible implementation manner, when the UE establishes a PDU session for accessing application 1, the SMF may determine an application server corresponding to the application 1 according to the first PCC rule. Since there is a correspondence between the application server and the UPF in different local DCs, the SMF can accordingly obtain a list of UPFs that can access application 1. The SMF may select a corresponding UPF for the UE as the PSA according to a preset rule. For example, the SMF may select a UPF closest to the UE in the UPF list as the PSA to establish a PDU session with the UE according to the current location of the UE. Of course, the SMF may also select the PSA for the UE according to other rules, which are not described herein again. It should be understood that, in the scheme shown in fig. 7, the PSA determined by the SMF for the UE according to the first PCC rule may correspond to the first user plane network element in the scheme shown in fig. 5A.

Thus, a PDU session of the UE with the PSA is achieved. The UE may access the DN through the PDU session, e.g., the UE may access an application server corresponding to application 1 through the PDU session.

After the UE establishes the PDU session, the UE can interact with an application server through application layer signaling, and the application server can issue event subscription information to the UPF through AF. It should be noted that the event subscription information may be service-related information, such as QoS monitoring information. The event subscription information may also be information unrelated to the service, for example, the event subscription information may be used to subscribe to location information of the UE, which is not limited in this embodiment. In the following, the event subscription information is used for the QoS-specified monitoring information as an example.

Fig. 8 is a schematic flowchart illustrating an event notification method according to an embodiment of the present application. It can be understood that the method can be applied in a scenario where the UE performs a relevant detection on the communication procedure after establishing the PDU session in the UPF. For example, the method may be applied after the UE establishes the PDU session as shown in fig. 7.

As shown in fig. 8, the method may include S801-S808. The method can be applied after the PDU session is established as shown in fig. 7. It should be noted that, in other implementations, the method shown in fig. 8 may be performed simultaneously with the method shown in fig. 7. The embodiment of the present application does not limit the execution order of the method shown in fig. 7 and the method shown in fig. 8. In the following, the PDU session shown in fig. 7 is established before the method shown in fig. 8 is performed.

S801, AF sends information 8-1 to NEF.

The information 8-1 may include event subscription information.

For example, the event subscription information may be used to request service-related communication data (e.g., QoS-related data). The event subscription information may include description information of the service data stream, ASP identification, and the like.

As an example, when the event subscription information is used for quality of service Monitoring (QoS Monitoring), the event subscription information may further include QoS Monitoring information or QoS Monitoring information and a QoS Monitoring event identifier. The QoS Monitoring information may include, but is not limited to, a request QoS Monitoring Parameter (i.e., a type of delay measured, which may include uplink data, downlink data, or round trip data), a reporting frequency (periodicity, event trigger), and other information. The event subscription information is used for requesting a QoS Notification Control (QoS Notification Control) event Notification, and may further include an indication of the QoS Notification Control (such as a QoS Notification Control event identifier) and the like.

In addition, the information 8-1 may be sent to NEF through an Nnef _ AFsessionWithQoS _ Create request message, which may include a notification association identifier. The notification association identifier may be carried in the corresponding event report by the UPF after detecting the corresponding event, so that the AF or NEF receiving the event report can know that the event report is associated with the event subscription.

S802, NEF sends information 8-2 to PCF.

Like S602 shown in fig. 6 described above, the NEF may perform similar processing on information 8-1, obtain information 8-2 and send it to the PCF. The processing procedure is similar and will not be described herein. Of course, NEF may also transmit this information 8-2 via UDR, which is not limited by this example. For example, the information 8-2 sent by the NEF may be Npcf _ PolicyAuthorization Request.

In the embodiment of the present application, when the NEF is set between the AF and the PCF, the information 8-2 may correspond to the second information in the scheme shown in fig. 5A. And when the NEF is not set between the AF and the PCF, the above information 8-1 may correspond to the second information in the scheme shown in fig. 5A.

S803, the PCF acquires the second PCC rule according to the information 8-2 and the first PCC rule.

It will be appreciated that the PCF has stored therein a first PCC rule, as described with respect to fig. 6 and 7. The first PCC rule may include address correspondence information corresponding to the application.

The PCF, after receiving the information 8-2, may update the first PCC rule to obtain an updated PCC rule (i.e., the second PCC rule). In the second PCC rule, event subscription information and address correspondence information of an application corresponding to the event subscription information may be included. The second PCC rule in this example may include event subscription information corresponding to the third information in the scheme shown in fig. 5A, and address correspondence information of the first information in the scheme shown in fig. 5A.

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

In some implementations, after receiving the information 8-2, the PCF may determine, according to the ASP identifier corresponding to the event subscription information included in the information 8-2, address correspondence information corresponding to the application in the first PCC rule. For example, if the ASP identifier corresponding to the event subscription information indicates that the event subscription information corresponds to the application 1, the PCF may carry, according to the ASP identifier, the address correspondence information 6-1 corresponding to the application 1 in the second PCC rule. Still additionally, the second PCC rule may further include other information, for example, the second PCC rule may include the notification association identifier in information 8-2.

S804, the PCF sends the second PCC rule to the SMF.

S805, the SMF determines an event notification address 1 according to the second PCC rule.

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., the event subscription information), the SMF further determines an event notification address 1 according to the DNAI for selecting the PSA and the address correspondence information of the application. In this example, the event notification address 1 may correspond to the first event notification address in the scheme shown in fig. 5A.

S806, the SMF sends the information 8-3 to the UPF.

The SMF may send information 8-3 including event subscription information (fourth information in the scheme shown in fig. 5A), an event notification address 1, and a notification correlation identifier to the UPF corresponding to the event.

S807, UPF obtains the event report.

And the UPF can execute corresponding monitoring according to the acquired event subscription information. Illustratively, since the UPF is typically the PSA that establishes the PDU session with the UE, the UPF acquisition event report may also be referred to as the PSA acquisition event report. When the event subscription information is QoS Monitoring, the PSA may measure a packet transmission delay between the UE and the PSA, and when a condition indicated by the report frequency is satisfied, the PSA detects an event corresponding to QoS Monitoring. When the event subscription information is QoS Notification Control, when the PSA receives a Notification that the bandwidth cannot be guaranteed or the bandwidth can be guaranteed again, which is sent by the RAN, the PSA detects the QoS Notification Control event.

S808, the UPF sends information 8-4 to the AF.

And the UPF can execute the feedback of the event report after acquiring the event report corresponding to the event subscription information. Illustratively, the UPF may feed back the event report to the network element having event notification address 1. In different implementation scenarios, the network element may be an AF or a NEF. In this example, the network element corresponding to the event notification address 1 is described as an example, which is an AF.

In conjunction with the communications architecture shown in fig. 4, the UPF may communicate data with the NEF in the local DC via an N4a interface. A further NEF may transmit corresponding data to the AF in the local DC. In this example, event notification address 1 may be the address of the local NEF. The UPF may send information 8-4 including event reports, notification correlation identifications to the NEF. The UPF thus completes the reporting of the event report to the event notification address 1. In this example, this information 8-4 may correspond to the fifth information in the scheme shown in fig. 5A.

It should be noted that in other implementations, the event notification address may be an address corresponding to an AF in the local DC, or an address corresponding to an AF located in another local DC, or an address corresponding to an AF located 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, an address of the NEF (e.g., event notification address 2) corresponding to the event notification address. Thus, the UPF can report the event report and the event notification address 1 to the network element corresponding to the event notification address 2. The NEF, upon receiving the event notification address, may further transmit the event report to a network element (e.g., AF) having an event notification address of 1. Thereby a feedback of event reports to the network element having the event notification address 1 is achieved. In this example, the event notification address 2 may correspond to a second event notification address in the scheme shown in fig. 5A.

It can be understood that based on the above descriptions of the event reporting method in fig. 6, 7, and 8, since the SMF may obtain the correspondence between all possible DNAIs and event notification addresses, after PSA reselection occurs due to UE movement, the SMF determines an event notification address corresponding to a new PSA according to the stored event subscription information, and issues the new event notification address and the event subscription information to the UPF. This avoids the problem that the AF must re-issue the event subscription information to ensure that the UPF transmits the event report to the correct address after the PSA reselection has occurred.

As an example, fig. 9 is a flowchart illustrating an event reporting method after PSA reselection. Taking UE pair usage as an example to cause PSA reselection. As shown in fig. 9, the method may include S901-S905.

S901, the SMF reallocates PSA for the mobile UE.

It should be appreciated that when the UE moves, the SMF may adjust the PSA for the UE as it moves to access the DN in order to provide better communication services to the UE. In itself, this redistributed PSA may be referred to as a second user plane network element, i.e. a second UPF.

For example, please refer to fig. 10. When the UE moves from location 1 to location 2, the SMF may also switch the PSA in PDU session with the UE from UPF1 in local DC1 to UPF2 in local DC 2. It is apparent that, when the UE is in location 2, the UPF2 can provide better communication service to the UE, when the service quality that the UPF1 and the UPF can provide is the same.

However, when the UE moves, since the UPF with which the PDU session is established has changed, when the application server wants to acquire an event report corresponding to the current subscription event information of the UE, the event report acquired by the UPF2 in the local DC2 cannot be acquired through the AF in the local DC1 (the AF through which the application server acquires the event report before the UE moves). In the embodiment of the present application, since the SMF can know the correspondence between all DNAIs and event notification addresses corresponding to the applications (such as the address correspondence information described above), when the PSA is updated, the SMF can also determine the corresponding updated event notification address.

In this embodiment, the application server in DC1 also sends the event subscription information to the application server in DC2 (such as the notification association id) through the application layer, and DC2 may then interact with the corresponding AF, and the notification AF sends the corresponding event notification to the application server.

S902, the SMF determines an event notification address 3 according to the second PCC rule.

After the SMF assigns a new PSA to the UE, the event notification address 3 corresponding to the DNAI corresponding to the new PSA (UPF 2 shown in fig. 10) may be determined according to the second PCC rule. This determination method is similar to S805 shown in fig. 8, and is not described here again.

S903, the SMF sends information 9-1 to the UPF.

And S904, obtaining the event report by the UPF.

S905, the UPF sends information 9-2 to the AF.

After acquiring the new event notification address, the SMF may proceed to S903-S905. Their respective execution modes can correspond to S806-S808 as shown in fig. 8. And will not be described in detail herein. The information 9-1 may include the fourth information and the first event notification address in the scheme shown in fig. 5A. The information 9-2 may include fifth information in the scheme shown in fig. 5A.

It should be noted that, after the SMF reselects the PSA for the UE, a UPF in a network may be selected as a branch point (branching point) or an uplink data splitter (uplink splitter), and by configuring a splitting rule for the intermediate UPF, uplink data sent when the UE accesses the application can be forwarded to the reselected PSA through the UPF. Therefore, smooth uplink communication of the UE after PSA reselection is realized.

In conjunction with the above description, the AF may configure different address correspondence information into the PCF by the method shown in fig. 6. The AF may also issue event subscription information by the method shown in fig. 8. So that the SMF can determine an event notification address corresponding to the selected PSA based on the interaction with the PCF and instruct the UPF to report an event report corresponding to the event subscription information via the event notification address. As an example, when an event report that an AF (or an application server corresponding to the AF) wants to obtain is an event report related to a service (e.g., an event report related to QoS monitoring), the application server may control the same or different AFs, and send the event subscription information and the information including the information corresponding to different addresses to other network elements through the same signaling. In another implementation manner, the application server may also control the same or different AFs, and issue the event subscription information and the information including the information corresponding to different addresses to other network elements through different signaling. In other embodiments, when an event report that an AF (or an application server corresponding to the AF) wants to obtain is an event report that is not related to a service (e.g., an event report of a UE location), the application server may control the same or different AFs, and send the event subscription information and the information including information corresponding to 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 the scenario where the application server obtains the event report that is not related to the service, a specific implementation method in the scenario is exemplarily described below.

Please refer to fig. 11, which is a flowchart illustrating another event reporting method according to an embodiment of the present application. Note that, the AF that sends the event subscription information and the address information is the same as the AF that receives the event report, for example.

As shown in FIG. 11, the method may include S1101-S1107.

S1101, AF sends information 11-1 to PCF.

In this example, this information 11-1 may be sent through a Nnef _ TrapaCinfluence _ Create Request. The information 11-1 may at least include a correspondence between the DNAI and the event Notification address (i.e., address correspondence information), an event identifier corresponding to the event subscription information, and an identifier assigned by the optional AF to the event subscription information (e.g., Notification Correlation Id). The information 11-1 may include the first information and the second information in the scheme shown in fig. 5A.

With reference to the descriptions in S601-S602 above, in different network architectures, the AF may send the information 11-1 to the PCF through the NEF, or the AF may send the information 11-1 to the PCF through the NEF and the UDR, or the AF may directly send the information 11-1 to the PCF. The specific implementation is similar to the method in S601-S602, and is not described here again.

S1102, PCF customizes the corresponding PCC rule according to the information 11-1.

The PCF may customize the corresponding PCC rule based on receiving the new 11-1. Illustratively, the PCC rule may carry a Traffic Steering Policy, which may include a list of DNAIs for the SMF to select the PSA based on the Traffic Steering Policy. If the identification information of the target UE indicated by the information 11-1 is the indication information of any UE or the internal group identifier, the PCC rule further includes an indication of sending the UE identifier.

In this example, the Traffic Steering Policy may further include address correspondence information, event identifier, and Notification correction Id. It should be appreciated that, in this example, the PCC rule may include the third information and the fourth information in the scheme shown in fig. 5A.

S1103, the PCF sends the PCC rule to the SMF.

S1104, SMF determines an event notification address according to the PCC rule.

In conjunction with the descriptions in S804-S806 above, the SMF may determine the event notification address corresponding to the event subscription information according to the address correspondence information in the PCC rule, i.e. the currently selected PSA (e.g. the first user plane network element above). The event notification address may be the first event notification address in the scheme shown in fig. 5A.

S1105, the SMF sends information 11-2 to the UPF.

Event subscription information and corresponding event notification addresses may be included in this information 11-2. If the PCC rule includes an indication to send the UE identity, the information 11-2 further includes an external identity of the UE. In some implementations, this information 11-2 may include the fourth information and the first event notification address in the scheme shown in FIG. 5A.

S1106, the UPF acquires an event report.

S1107, the UPF sends an event report to the AF.

And the UPF can report the acquired event report through the event notification address indicated by the SMF. As an example, the event report may be the fifth information in the scheme shown in fig. 5A.

It should be noted that, when the AF issues the information 11-1, the AF may also issue a notification association identifier, so that when the UPF reports an event, the notification association identifier may be uploaded together, so that the application server can know the association between the obtained event report and the issued event subscription information. In addition, in some embodiments, the event subscription information corresponds to some terminal devices, and therefore, when the UE reports the event report, the UE may report the Notification correction Id configured for the UE together, so that the application server can associate the event report with the UE. If the information 11-2 includes the external identity of the UE, the external identity of the UE is also reported in the event report.

By way of illustration of the method shown in fig. 11, it should be understood that the SMF may determine an event notification address of an event report corresponding to the event subscription information according to the selected PSA, and thus, when a PSA (upf) reselection occurs due to UE movement or the like, a corresponding event reporting mechanism may be executed according to the method shown in fig. 9. Therefore, the problem of overlarge delay caused by the fact that the AF needs to issue the event subscription information again when the PSA is changed is avoided.

In addition, in some embodiments, when the event report needs to be fed back to the AF through another NEF, the SMF may further obtain and send the address (e.g., address 2) of the NEF when issuing the event subscription information and the corresponding event notification address (e.g., address 1) to the UPF (i.e., performing S1105). The UPF may obtain event subscription information, address 1 and address 2, from the SMF. After the UPF obtains the corresponding event report, it may send the event report to address 2, and simultaneously send address 1 to NEF corresponding to address 2. So that the NEF can transmit the event report to the corresponding AF according to the address 1, thereby realizing smooth transmission of the event report.

The above description mainly introduces the solutions provided in the embodiments of the present application from the perspective of each network element. To implement the above functions, it includes hardware structures and/or software modules for performing the respective functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the functional modules may be divided according to the method example, for example, the functional modules may be divided corresponding to the functions, or two or more functions may be integrated in one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

Referring to fig. 12, a schematic block diagram of an event notification apparatus 1200 according to an embodiment of the present application is shown. The event notification apparatus 1200 may be disposed in the AF shown in fig. 2, fig. 3, fig. 4, or fig. 5, and is configured to implement any one of the event notification methods provided in the embodiments of the present application.

As shown in fig. 12, the event notification apparatus 1200 may include: a determining unit 1201 and a transmitting unit 1202. The determining unit 1201 is configured to determine 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, the network access identifier is used to indicate a location of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is 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 for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. The sending unit 1202 is configured to send the first information and the second information. As an example, the determining unit 1201 may specifically determine the specific contents of the first information and the second information according to an instruction of the application server.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again. Optionally, but not necessarily, the event notification apparatus 1200 provided in the embodiment of the present application may further include a processing module or a control module for supporting the determining unit 1201 and/or the sending unit 1202 to complete corresponding functions, if necessary.

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

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Fig. 14 shows a schematic diagram of a chip system 1400. The chip system 1400 may include: a processor 1401 and a communication interface 1402 for supporting AF to implement the functions referred to in the above embodiments. In one possible design, the system-on-chip 1400 also includes memory for storing program instructions and data necessary for AF. The chip system 1400 may be formed by a chip, or may include a chip and other discrete devices.

Referring to fig. 15, a schematic block diagram of another event notification apparatus 1500 according to an embodiment of the present application is provided. The event notification apparatus 1500 may be disposed in a PCF as shown in fig. 2, fig. 3, fig. 4, or fig. 5, and is configured to implement any one of the event notification methods provided in the embodiments of the present application.

As shown in fig. 15, the event notification apparatus 1500 may include: a receiving unit 1501, a transmitting unit 1502. The receiving unit 1501 is configured to receive 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, the network access identifier is used to indicate a location of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is 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 for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. The sending unit 1502 is configured to send third information and the first information, where the third information is determined according to the second information and is used to subscribe to the first event.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again. Optionally, but not necessarily, the event notification apparatus 1500 provided in this embodiment of the application may further include a processing module or a control module for supporting the receiving unit 1501 and/or the sending unit 1502 to complete corresponding functions, if necessary.

Fig. 16 shows a schematic diagram of a policy control function 1600. The policy control function 1600 may include: a processor 1601, and a memory 1602. The memory 1602 is used to store computer-executable instructions. Illustratively, in some embodiments, the processor 1601, when executing the instructions stored by the memory 1602, may cause the policy control function 1600 to perform the operations that the PCF needs to perform in the above example.

Fig. 17 shows a schematic diagram of a chip system 1700. The chip system 1700 may include: a processor 1701 and a communication interface 1702 for supporting the PCF in implementing the functions referred to in the embodiments described above. In one possible design, chip system 1700 may also include a memory for storing program instructions and data necessary for the PCF. The chip system 1700 may be formed by a chip, and may also include a chip and other discrete devices.

Referring to fig. 18, a schematic block diagram of an event notification apparatus 1800 according to an embodiment of the present application is shown. The event notification apparatus 1800 may be disposed in the SMF shown in fig. 2, fig. 3, fig. 4, or fig. 5, and is used to implement any one of the event notification methods provided in the embodiments of the present application.

As shown in fig. 18, the event notification apparatus 1800 may include: a receiving unit 1801 and a transmitting unit 1802. A receiving unit 1801, configured to receive 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 a location of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is 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 for subscribing to a first event of a terminal device, the terminal device being a device of an application server accessing the application. And selecting a first user plane network element for the terminal equipment, wherein the first user plane network element corresponds to a first data network access identifier, and at least one data network access identifier comprises the first data network access identifier. A sending unit 1802 for sending the third information, and the first event notification address. And the third information is determined according to the second information and is used for subscribing 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.

In one possible design, the sending unit 1802 is further configured to send a second event notification address, where the second event notification address is an address of a local capability openness network element corresponding to the first user plane network element.

In a possible design, the apparatus further includes a configuring unit 1803, configured to select, for a terminal device of an application server accessing the application, a corresponding second user plane network element, where 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. And sending the fourth information and the third event notification address. And the fourth information is determined according to the second information and is used for subscribing the first event. The third event notification address is determined according to the second 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.

In a possible design, the sending unit 1802 is further configured to send a fourth event notification address, where the fourth event notification address is an address of a local capability openness network element corresponding to the second user plane network element.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again. Optionally, but not necessarily, the event notification apparatus 1800 according to the embodiment of the present application may further include a processing module or a control module for supporting the receiving unit 1801 and/or the sending unit 1802 and/or the configuring unit 1803 to complete corresponding functions, if necessary.

Fig. 19 is a schematic diagram illustrating a component of a session management function 1900. The session management function 1900 may include: a processor 1901 and a memory 1902. The memory 1902 is used to store computer-executable instructions. For example, in some embodiments, the processor 1901, when executing the instructions stored in the memory 1902, may cause the session management function 1900 to perform the operations that the SMF needs to perform in the above examples.

Fig. 20 shows a schematic diagram of a chip system 2000. The chip system 2000 may include: a processor 2001 and a communication interface 2002 for supporting SMF to implement the functions involved in the above embodiments. In one possible design, system-on-chip 2000 may further include a memory for storing the necessary program instructions and data for the SMF. The chip system 2000 may be formed by a chip, or may include a chip and other discrete devices.

Referring to fig. 21, a schematic block diagram of an event notification apparatus 2100 according to an embodiment of the present application is provided. The event notification apparatus 2100 may be disposed in a UPF shown in fig. 2, fig. 3, fig. 4, or fig. 5, and is configured to implement any one of the event notification methods provided in the embodiments of the present application.

As shown in fig. 21, the event notification apparatus 2100 may include: a receiving unit 2101 and a transmitting unit 2102.

The receiving unit 2101 is configured to receive first information, a first event notification address, and a second event notification address, where the first information is used to subscribe to a first event of a terminal device, and the terminal device is a device 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 corresponding to the application function AF. The second event notification address is an address of a local capability openness network element corresponding to the first user plane network element. A sending unit 2102 configured to send second information to the first event notification address through the second event notification address, where the second information includes event notification information of the first event.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again. As an option, but not necessarily, the event notification apparatus 2100 provided in the embodiment of the present application may further include a processing module or a control module for supporting the receiving unit 2101 and the sending unit 2102 to complete corresponding functions, if necessary.

Fig. 22 shows a schematic composition diagram of a user plane functional entity 2200. The application function entity 2200 may include: a processor 2201 and a memory 2202. The memory 2202 is used to store computer-executable instructions. For example, in some embodiments, the processor 2201, when executing the instructions stored in the memory 2202, may cause the user plane functional entity 2200 to perform the operations that the UPF needs to perform in the above example.

Fig. 23 shows a schematic diagram of a chip system 2300. The chip system 2300 may include: a processor 2301 and a communication interface 2302 to support UPF to implement the functions involved in the above embodiments. In one possible design, the chip system 2300 also includes memory for storing the necessary program instructions and data for the UPF. The chip system 2300 may be constituted by a chip, or may include a chip and other discrete devices.

The functions or actions or operations or steps, etc., in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such 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 such modifications and variations.

Claims

1. An event notification method, characterized in that the method comprises:

receiving first information and second information, wherein the first information comprises 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 for indicating the position of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an Application Function (AF) corresponding to the application;

the second information is used for subscribing a first event of a terminal device, and the terminal device is a device of an application server accessing the application;

selecting a first user plane network element for the terminal equipment, wherein the first user plane network element corresponds to a first data network access identifier, and the at least one data network access identifier comprises the first data network access identifier;

sending third information and a first event notification address, wherein the first event notification address is a destination address for receiving event notification information of the first event;

wherein the third information is determined according to the second information and is used for subscribing 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 an event notification address corresponding to the at least one data network access identifier.

2. The method of claim 1, further comprising:

and sending a second event notification address, wherein the second event notification address is an address of a local capability open network element corresponding to the first user plane network element.

3. The method of claim 1 or 2, wherein the second information further comprises: a notification association identifier, configured to associate event notification information of the first event with the first information, where the third information further includes the notification association identifier.

4. A method according to any of claims 1-3, wherein the second information comprises at least one of: QoS monitoring request information, QoS notification control request information, and position request information.

5. An event notification apparatus, characterized in that the apparatus is configured to perform the event notification method according to any of claims 1-4.

6. A session management function, SMF, entity, the SMF entity comprising one or more processors and one or more memories; the one or more memories coupled with the one or more processors, the one or more memories storing computer instructions;

the computer instructions, when executed by the one or more processors, cause the SMF entity to perform the event notification method of any of claims 1-4.

7. An event notification method, characterized in that the method comprises:

sending first information and second information, wherein the first information comprises 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 for indicating the position of an application server of an application, the event notification address is a destination address for receiving the event notification information, and the destination address is an address of a local capability open network element or an address of an Application Function (AF) corresponding to the application;

the second information is used for subscribing to a first event of a terminal device, and the terminal device is a device of an application server accessing the application.

8. The method of claim 7, wherein the second information further comprises: a notification association identifier for associating event notification information of the first event with the first information.

9. The method according to claim 7 or 8, wherein the second information comprises at least one of the following information: QoS monitoring request information, QoS notification control request information, and position request information.

10. An event notification apparatus, characterized in that the apparatus is adapted to perform the event notification method according to any of claims 7-9.

11. An application function, AF, entity, comprising one or more processors and one or more memories; the one or more memories coupled with the one or more processors, the one or more memories storing computer instructions;

the computer instructions, when executed by the one or more processors, cause the AF entity to perform the event notification method of any of claims 7-9.

12. An event notification method, characterized in that the method comprises:

and sending third information and the first information, wherein the third information is determined according to the second information and is used for subscribing the first event.

13. The method of claim 12, wherein the second information further comprises: a notification association identifier, configured to associate event notification information of the first event with the first information, where the third information further includes the notification association identifier.

14. The method according to claim 12 or 13, wherein the second information comprises at least one of: QoS monitoring request information, QoS notification control request information, and position request information.

15. An event notification apparatus, characterized in that the apparatus is adapted to perform the event notification method according to any of claims 12-14.

16. A policy control function, PCF, entity, comprising one or more processors and one or more memories; the one or more memories coupled with the one or more processors, the one or more memories storing computer instructions;

the computer instructions, when executed by the one or more processors, cause the PCF entity to perform the event notification method of any of claims 12-14.

17. An event notification method, characterized in that the method comprises:

receiving first information, a first event notification address and a second event notification address, wherein the first information is used for subscribing a first event of a terminal device, and the terminal device is a device of an application server accessing 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 open network element corresponding to the first user plane network element;

and sending second information to the first event notification address through the local capability open network element corresponding to the second event notification address, where the second information includes event notification information of the first event.

18. The method of claim 17, wherein the first information further comprises: a notification association identifier, configured to associate event notification information of the first event with the event notification address, where the second information further includes the notification association identifier.

19. The method according to claim 17 or 18, wherein the first information comprises at least one of: QoS monitoring request information, QoS notification control request information, and position request information.

20. An event notification apparatus, characterized in that the apparatus is adapted to perform the event notification method according to any of claims 17-19.

21. A user plane function, UPF, entity, the UPF entity comprising one or more processors and one or more memories; the one or more memories coupled with the one or more processors, the one or more memories storing computer instructions;

the computer instructions, when executed by the one or more processors, cause the UPF entity to perform the event notification method of any of claims 17-19.

22. A communication system, 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 configured to send 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 a 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 open network element or an address of an application function AF corresponding to the application; the second information is used for subscribing a first event of a terminal device, and the terminal device is a device of an application server accessing the application;

the second network element is configured to receive the first information and the second information; third information and the first information are sent, wherein the third information is determined according to the second information and is used for subscribing the first event;

the third network element is configured to receive the first information and the third information; selecting a first user plane network element for the terminal equipment, wherein the first user plane network element corresponds to a first data network access identifier, and the at least one data network access identifier comprises the first data network access identifier; sending fourth information and a first event notification address; wherein the fourth information is determined according to the third information and is used for subscribing 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 an event notification address corresponding to the at least one data network access identifier;

the fourth network element is configured to receive the fourth information and the first event notification address; and sending fifth information to the first event notification address, wherein the fifth information comprises event notification information of the first event.

23. The communication system of claim 22, wherein 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.