A method, apparatus and system for sending event reports

Abstract

The present application provides a method, apparatus, and system for sending an event report. The method includes: a session management network element receives an event notification request from a policy control network element, the event notification request includes an event identifier and a first notification address, the first notification address is the address of an event report receiving network element for receiving an event report, and the event report receiving network element is an application function network element or a network exposure function network element; the session management network element sends a first message to a user plane network element, the first message includes the event identifier and the notification address, and the first message is used to instruct the user plane network element to send a first event report corresponding to the event identifier to the first notification address. In this solution, the user plane network element sends the first event report to the first notification address. When the first notification address is the address of the network exposure function network element for receiving an event report, the network exposure function network element can send the received first event report to the application function network element, so that the application function network element can obtain the event report.

Description

[0001] This application claims the priority of a Chinese patent application with an application number of 201910695285.8 and an invention title of "A Method, Apparatus and System for Sending Event Reports" filed with the State Intellectual Property Office of the People's Republic of China on July 30, 2019, the entire content of which is incorporated herein by reference. Technical Field

[0002] This application relates to the field of mobile communication technologies, and in particular, to a method, apparatus and system for sending event reports. Background Art

[0003] In the 5th generation (5G) system, after a terminal device accesses the network, a session is established, and the terminal device accesses an external data network through the session to implement the interaction between the terminal device and an application function network element (also referred to as an application server) deployed in the data network. Generally, these application function network elements are deployed in a Mobile Edge Compute (MEC) environment. For an application function network element, it is necessary to obtain relevant event reports of the application in order to perform corresponding adjustments at the application layer.

[0004] There is currently no corresponding method for how an application function network element obtains an event report. Summary of the Invention

[0005] This application provides a method, apparatus and system for sending event reports, which can solve the above problems.

[0006] In a first aspect, this application provides a method for sending an event report. A session management network element receives an event notification request from a policy control network element. The event notification request includes event notification request information and a first notification address. The event notification request information includes an event identifier and / or event monitoring control information. The first notification address is the address of an event report receiving network element for receiving an event report. The event report receiving network element is an application function network element or a network exposure function network element. The session management network element sends a first message to a user plane network element. The first message includes the event notification request information and a second notification address. The second notification address is determined according to the first notification address. The first message is used to instruct the user plane network element to send a first event report corresponding to the event notification request information to the second notification address.

[0007] Among them, the second notification address is the address of the event report receiving network element for receiving an event report. The second notification address may be the same as the first notification address. In this case, the second notification address may also be referred to as the first notification address, or both the second notification address and the first notification address are referred to as notification addresses.

[0008] Based on this solution, the user plane network element can send a first event report to the second notification address. When the second notification address is the address of the network exposure function network element for receiving event reports, the network exposure function network element can send the received first event report to the application function network element, enabling the application function network element to obtain the event report. Moreover, since the user plane network element can directly report the event report to the application function network element or report the event report to the AF through the network exposure function network element, the path length of reporting the event report is greatly shortened. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing at the application layer.

[0009] In a possible implementation manner, the session management network element determines that the user plane network element sends the first event report to the second notification address.

[0010] In a possible implementation manner, the session management network element determines that the user plane network element sends the first event report to the second notification address, including: the session management network element determines that the user plane network element sends the first event report to the notification address according to the second notification address; or, the event notification request further includes the location information of the event report receiving network element; the session management network element determines that the user plane network element sends the first event report to the second notification address according to the location information of the event report receiving network element; or, the event notification request further includes first indication information, and the first indication information is used to indicate that the event notification request is a local event notification request; the session management network element determines that the user plane network element sends the first event report to the second notification address according to the first indication information.

[0011] In a possible implementation manner, the first message includes second indication information, and the first message is used to indicate that the user plane network element sends the first event report corresponding to the event notification request information to the second notification address, including: the second indication information is used to indicate that the user plane network element sends the first event report corresponding to the event notification request information to the second notification address.

[0012] In a possible implementation manner, the first message further includes third indication information, and the third indication information is used to indicate that the user plane network element sends the second event report corresponding to the event notification request information to the session management network element.

[0013] In a possible implementation, when the session management network element determines to send a third event report to the policy control network element, it sends fourth indication information to the user plane network element. The fourth indication information is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address, and to instruct the user plane network element to send the second event report corresponding to the event notification request information to the session management network element.

[0014] In a possible implementation, the session management network element's determination to send the third event report to the policy control network element includes: The event notification request further includes fifth indication information, which is used to instruct the session management network element to send the third event report to the policy control network element; The session management network element determines to send the third event report to the policy control network element according to the fifth indication information; or, the session management network element determines to send the third event report to the policy control network element according to the configuration information.

[0015] In a possible implementation, the event notification request further includes a notification association identifier, which is used for the event report receiving network element to associate the first event report with the event notification request; The session management network element sends the notification association identifier to the user plane network element.

[0016] In a possible implementation, the event identifier is a QoS detection event identifier, the event monitoring control information is QoS detection control information, and the QoS detection control information includes parameters for requesting QoS detection and a reporting frequency.

[0017] In a possible implementation, the event identifier is a quality of service (QoS) detection (QoS detection can also be referred to as a QoS detection event identifier), and the event notification request further includes QoS parameters to be detected. Among them, the QoS parameters to be detected can be understood as event monitoring control information.

[0018] In a possible implementation, the session management network element sends sixth indication information to the access network device, and the sixth indication information is used to instruct the execution of QoS detection.

[0019] In a possible implementation, the event notification request information includes the event identifier and the event monitoring control information. The event identifier is a usage monitoring event identifier, and the event monitoring control information is usage monitoring control information. Optionally, the usage monitoring control information includes a usage threshold.

[0020] In a possible implementation, the event identifier is usage monitoring (usage monitoring may also be referred to as the usage monitoring event identifier), and the event notification request further includes a usage threshold. The usage threshold can be understood as event monitoring control information.

[0021] In a second aspect, the present application provides a method for sending an event report. The method includes: a user plane network element receives a first message from a session management network element. The first message includes event notification request information and a second notification address. The event notification request information includes an event identifier and / or event monitoring control information. The second notification address is the address of an event report receiving network element for receiving a first event report. The event report receiving network element is an application function network element or a network exposure function network element. The first message is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address; the user plane network element sends the first event report to the second notification address.

[0022] Among them, the notification address received by the session management network element from other network elements (such as a policy control network element) is called the first notification address, and the notification address sent by the session management network element to the user plane network element is called the second notification address. Both the first notification address and the second notification address are the addresses of the event report receiving network element for receiving event reports. The second notification address is obtained based on the first notification address. The second notification address may be the same as the first notification address. In this case, the second notification address may also be referred to as the first notification address, or both the second notification address and the first notification address are referred to as the notification address.

[0023] Based on this solution, the user plane network element can send the first event report to the second notification address. When the second notification address is the address of the network exposure function network element for receiving event reports, the network exposure function network element can send the received first event report to the application function network element, realizing that the application function network element obtains the event report. Moreover, since the user plane network element can directly report the event report to the application function network element, or report the event report to the AF through the network exposure function network element, the path length of reporting the event report is greatly shortened. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing of the application layer.

[0024] In a possible implementation, the first message includes second indication information. The first message is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address, including: the second indication information is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address.

[0025] In a possible implementation, the user plane network element sends a second event report corresponding to the event notification request information to the session management network element.

[0026] In a possible implementation, the first message further includes third indication information, where the third indication information is used to indicate sending the second event report corresponding to the event notification request information to the session management network element.

[0027] In a possible implementation, the first message further includes fourth indication information, where the fourth indication information is used to indicate that the user plane network element sends the first event report corresponding to the event notification request information to the second notification address, and to indicate that the user plane network element sends the second event report corresponding to the event notification request information to the session management network element.

[0028] In a possible implementation, the first message further includes a notification association identifier, where the notification association identifier is used for the event report receiving network element to associate the first event report with the event notification request; the first event report includes the notification association identifier.

[0029] In a possible implementation, when the user plane network element detects an event corresponding to the event notification request information, it generates the first event report.

[0030] In a third aspect, the present application provides a method for sending an event report. The method includes: an application function network element sends an event notification request to a network exposure function network element. The event notification request includes event notification request information and a first notification address. The event notification request information includes an event identifier and / or event monitoring control information. The first notification address is an address of the application function network element for receiving the first event report. The event notification request is used to request the user plane network element to send the first event report corresponding to the event notification request information to the first notification address; the application function network element receives the first event report from the user plane network element or the network exposure function network element. Based on this solution, the user plane network element can send the first event report to the first notification address, achieving that the application function network element can obtain the event report. Moreover, since the user plane network element can directly report the event report to the application function network element, or report the event report to the AF through the network exposure function network element, the path length of reporting the event report is greatly shortened. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing of the application layer.

[0031] In a possible implementation, the event notification request further includes seventh indication information, where the seventh indication information is used to indicate that the event notification request is a local event notification request; or, the event notification request further includes location information of the application function network element.

[0032] In a possible implementation, the event notification request further includes a notification association identifier, where the notification association identifier is used by the application function network element to associate the first event report with the event notification request.

[0033] In a possible implementation, the application function network element receives the notification association identifier from the user plane network element or the network exposure function network element.

[0034] Fourthly, this application provides a method for sending an event report. The method includes: The policy control network element receives a first event notification request from the network exposure function network element. The first event notification request includes event notification request information and a first notification address. The first notification address is the address of the event report receiving network element for receiving the first event report. The event report receiving network element is the application function network element or the network exposure function network element; The policy control network element sends a second event notification request to the session management network element. The second event notification request includes the event notification request information and the first notification address. The event notification request information includes an event identifier and / or event monitoring control information. The second event notification request is used to request the user plane network element to send the first event report corresponding to the event notification request information to the first notification address. Based on this solution, the user plane network element can send the first event report to the first notification address. When the first notification address is the address of the network exposure function network element for receiving the event report, the network exposure function network element can send the received first event report to the application function network element, realizing that the application function network element obtains the event report. And, since the user plane network element can directly report the event report to the application function network element, or report the event report to the AF through the network exposure function network element, the path length of reporting the event report is greatly shortened. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing of the application layer.

[0035] In a possible implementation, the second event notification request further includes first indication information, where the first indication information is used to indicate that the second event notification request is a local event notification request.

[0036] In a possible implementation, the first event notification request further includes eighth indication information, where the eighth indication information is used to indicate that the first event notification request is a local event notification request; or, the first event notification request further includes location information of the event report receiving network element. The eighth indication information may also be referred to as indication information for indicating that the event notification request is a local event notification request.

[0037] In a possible implementation, if the policy control network element determines that it is necessary to obtain a third event report corresponding to the event notification request information, the policy control network element determines to send indication information to the session management network element for instructing the session management network element to send the third event report to the policy control network element. This indication information may also be referred to as fifth indication information.

[0038] In a possible implementation, the second event notification request further includes fifth indication information, where the fifth indication information is used to instruct the session management network element to send a third event report corresponding to the event notification request information to the policy control network element.

[0039] In a possible implementation, the first event notification request further includes a notification association identifier, where the notification association identifier is used for the event report receiving network element to associate the first event report with the second event notification request, and the second event notification request further includes the notification association identifier.

[0040] In a fifth aspect, the present application provides a method for sending an event report. The method includes: The session management network element receives an event notification request from the policy control network element. The event notification request includes event notification request information and a first notification address. The event notification request information includes an event identifier and / or event monitoring control information. The first notification address is the address of the event report receiving network element for receiving event reports, and the event report receiving network element is an application function network element or a network exposure function network element; The session management network element determines that the user plane network element sends a first event report corresponding to the event notification request information to a second notification address, and the second notification address is determined according to the first notification address.

[0041] In a possible implementation, the event notification request further includes first indication information, where the first indication information is used to indicate that the event notification request is a local event notification request. The session management network element determines that the user plane network element sends a first event report corresponding to the event notification request information to a second notification address, including: The session management network element determines, according to the first indication information, that the user plane network element sends the first event report to the second notification address.

[0042] In a possible implementation, the event notification request further includes indication information for indicating that the event notification request is a repeated event notification request. The session management network element determines that the user plane network element sends a first event report corresponding to the event notification request information to a second notification address, including: the session management network element determines, according to the indication information for indicating that the event notification request is a repeated event notification request, that the user plane network element sends the first event report to the second notification address.

[0043] In a possible implementation, the session management network element sends third indication information to the user plane network element according to the indication information for indicating that the event notification request is a repeated event notification request. The third indication information is used to indicate that the user plane network element sends a second event report corresponding to the event notification request information to the session management network element.

[0044] In a possible implementation, the session management network element sends second indication information to the user plane network element. The second indication information is used to indicate that the user plane network element sends the first event report to the second notification address.

[0045] In a possible implementation, the session management network element sends the event notification request information and the second notification address to the user plane network element, for indicating that the user plane network element sends the first event report to the second notification address.

[0046] In a possible implementation, the event notification request further includes a notification association identifier, which is used for the event report receiving network element to associate the first event report with the event notification request; the session management network element sends the notification association identifier to the user plane network element.

[0047] In a sixth aspect, the present application provides a communication device, which may be a session management network element or a chip for a session management network element. The device has functions of implementing the first aspect, the fifth aspect, the embodiments of the first aspect, or the embodiments of the fifth aspect. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0048] In a seventh aspect, the present application provides a communication device, which may be a user plane network element or a chip for a user plane network element. The device has functions of implementing the second aspect or the embodiments of the second aspect. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0049] In an eighth aspect, the present application provides a communication device, which may be an application function network element or a chip for an application function network element. The device has the functions of implementing the third aspect or each embodiment of the third aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0050] In a ninth aspect, the present application provides a communication device, which may be a policy control network element or a chip for a policy control network element. The device has the functions of implementing the fourth aspect or each embodiment of the fourth aspect. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0051] In a tenth aspect, the present application provides a communication device, including a processor and a memory; the memory is used to store computer execution instructions, and when the device runs, the processor executes the computer execution instructions stored in the memory, so that the device executes the methods of the above aspects or each embodiment of the aspects.

[0052] In an eleventh aspect, the present application provides a communication device, including units or means for performing the above aspects or each step of the aspects.

[0053] In a twelfth aspect, the present application provides a communication device, including a processor and an interface circuit, and the processor is used to communicate with other devices through the interface circuit and execute the methods of the above aspects or each embodiment of the aspects. The processor includes one or more.

[0054] In a thirteenth aspect, the present application provides a communication device, including a processor, which is used to be connected to a memory and call a program stored in the memory to execute the methods of the above aspects or each embodiment of the aspects. The memory may be inside or outside the device. And the processor includes one or more.

[0055] In a fourteenth aspect, the present application further provides a computer-readable storage medium, in which instructions are stored, and when they run on a computer, the processor is caused to execute the methods described in the above aspects or each embodiment of the aspects.

[0056] In a fifteenth aspect, the present application further provides a computer program product including instructions, and when it runs on a computer, the computer is caused to execute the methods described in the above aspects or each embodiment of the aspects.

[0057] In a sixteenth aspect, the present application further provides a chip system, including: a processor for executing the methods described in the above aspects or each embodiment of the aspects.

[0058] In the seventeenth aspect, the present application provides a communication system, including: a session management network element, configured to receive an event notification request from a policy control network element, where the event notification request includes event notification request information and a first notification address, the event notification request information includes an event identifier and / or event monitoring control information, the first notification address is an address of an event reporting receiving network element for receiving an event report, and the event reporting receiving network element is an application function network element or a network exposure function network element; and, configured to send a first message to a user plane network element, where the first message includes the event notification request information and a second notification address, and the first message is used to instruct the user plane network element to send a first event report corresponding to the event notification request information to the second notification address, and the second notification address is determined according to the first notification address. A user plane network element, configured to receive the first message from the session management network element; and, configured to send the first event report to the second notification address.

[0059] In the seventeenth aspect, the present application provides a method for sending an event report, including: a session management network element receives an event notification request from a policy control network element, where the event notification request includes event notification request information and a first notification address, the event notification request information includes an event identifier and / or event monitoring control information, the first notification address is an address of an event reporting receiving network element for receiving an event report, and the event reporting receiving network element is an application function network element or a network exposure function network element; the session management network element sends a first message to a user plane network element, where the first message includes the event notification request information and a second notification address, and the first message is used to instruct the user plane network element to send a first event report corresponding to the event notification request information to the second notification address, and the second notification address is determined according to the first notification address; the user plane network element sends the first event report to the second notification address. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 It is a schematic diagram of a communication system provided by the present application;

[0061] Figure 2A It is a schematic diagram of a 5G network architecture based on a service-based architecture;

[0062] Figure 2B It is a schematic diagram of a 5G network architecture based on a peer-to-peer interface;

[0063] Figure 3A It is a schematic diagram of a network architecture applicable to the present application;

[0064] Figure 3B It is another schematic diagram of a network architecture applicable to the present application;

[0065] Figure 3C Another schematic diagram of a network architecture applicable to this application;

[0066] Figure 3D Another schematic diagram of a network architecture applicable to this application;

[0067] Figure 3E Another schematic diagram of a network architecture applicable to this application;

[0068] Figure 4 Schematic diagram of a method flow for sending an event report provided by this application;

[0069] Figure 5 Another schematic diagram of a method flow for sending an event report provided by this application;

[0070] Figure 6 Another schematic diagram of a method flow for sending an event report provided by this application;

[0071] Figure 7 Another schematic diagram of a method flow for sending an event report provided by this application;

[0072] Figure 8 Schematic diagram of a communication device provided by this application;

[0073] Figure 9 Another schematic diagram of a communication device provided by this application. Detailed implementation manners

[0074] In order to make the objectives, technical solutions, and advantages of this application clearer, the following will further describe this application in detail with reference to the accompanying drawings. The specific operation methods in the method embodiments can also be applied to the device embodiments or system embodiments. Among them, in the description of this application, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0075] To solve the problems mentioned in the background art, as Figure 1 shown, this application provides a communication system, which includes a session management network element and a user plane network element. Optionally, the system may further include an application function network element. Optionally, the system may further include a network openness function network element. Optionally, the system may further include a policy control network element.

[0076] The session management network element is configured to receive a second event notification request from a policy control network element. The second event notification request includes event notification request information and a first notification address. The event notification request information includes an event identifier and / or event monitoring control information. The first notification address is the address of an event reporting receiving network element for receiving event reports, and the event reporting receiving network element is an application function network element or a network exposure function network element. Further, the session management network element is configured to send a first message to a user plane network element. The first message includes the event notification request information and a second notification address, and the first message is used to instruct the user plane network element to send a first event report corresponding to the event notification request information to the second notification address. The second notification address is determined based on the first notification address. The user plane network element is configured to receive the first message from the session management network element. Further, the user plane network element is configured to send the first event report to the second notification address.

[0077] In a possible implementation method, the session management network element is further configured to determine that the user plane network element sends the first event report to the second notification address.

[0078] In a possible implementation method, the session management network element is configured to determine that the user plane network element sends the first event report to the second notification address, including: being configured to determine, based on the second notification address, that the user plane network element sends the first event report to the second notification address; or, the second event notification request further includes location information of the event reporting receiving network element, and being configured to determine, based on the location information of the event reporting receiving network element, that the user plane network element sends the first event report to the second notification address; or, the second event notification request further includes first indication information, and the first indication information is used to indicate that the second event notification request is a local second event notification request, and being configured to determine, based on the first indication information, that the user plane network element sends the first event report to the second notification address.

[0079] In a possible implementation method, the first message includes second indication information, and the first message is used to instruct the user plane network element to send a first event report corresponding to the event notification request information to the second notification address, including: the second indication information is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address.

[0080] In a possible implementation method, the first message further includes third indication information, and the third indication information is used to instruct the user plane network element to send a second event report corresponding to the event notification request information to the session management network element. The user plane network element is further configured to send the second event report to the session management network element.

[0081] In a possible implementation method, the session management network element is further configured to determine to send a third event report to the policy control network element, and then send fourth indication information to the user plane network element. The fourth indication information is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address, and to instruct the user plane network element to send the second event report corresponding to the event notification request information to the session management network element.

[0082] In a possible implementation method, the session management network element is configured to determine to send the third event report to the policy control network element, including: the second event notification request further includes fifth indication information, and the fifth indication information is used to instruct the session management network element to send the third event report to the policy control network element; being configured to determine to send the third event report to the policy control network element according to the fifth indication information; or being configured to determine to send the third event report to the policy control network element according to configuration information.

[0083] In a possible implementation method, the second event notification request further includes a notification association identifier, and the notification association identifier is used for the event report receiving network element to associate the first event report with the second event notification request; the session management network element is further configured to send the notification association identifier to the user plane network element.

[0084] In a possible implementation method, the event notification request information includes the event identifier and the event monitoring control information. The event identifier is a QoS detection event identifier, and the event monitoring control information is QoS detection control information. The QoS detection control information includes parameters for requesting QoS detection and a reporting frequency.

[0085] In a possible implementation method, the event identifier is a Quality of Service (QoS) detection (QoS detection can also be referred to as a QoS detection event identifier), and the second event notification request further includes QoS parameters to be detected. Among them, the QoS parameters to be detected can be understood as event monitoring control information.

[0086] In a possible implementation method, the session management network element is further configured to send sixth indication information to the access network device, and the sixth indication information is used to instruct to perform QoS detection.

[0087] In a possible implementation manner, the event notification request information includes the event identifier and the event monitoring control information. The event identifier is a usage monitoring event identifier, and the event monitoring control information is usage monitoring control information. Optionally, the usage monitoring control information includes a usage threshold.

[0088] In a possible implementation method, the event identifier is usage monitoring (usage monitoring can also be referred to as the usage monitoring event identifier), and the second event notification request further includes a usage threshold. Among them, the usage threshold can be understood as event monitoring control information.

[0089] In a possible implementation method, the user plane network element is further configured to generate the first event report when detecting the event corresponding to the event notification request information.

[0090] In a possible implementation method, the network exposure function network element is configured to send a first event notification request to the policy control network element, and the first event notification request includes the event notification request information and the first notification address. The policy control network element is configured to receive the first event notification request.

[0091] In a possible implementation method, the application function network element is configured to send a third event notification request to the network exposure function network element, the third notification request includes the event notification request information and the first notification address, and the event report receiving network element is the application function network element.

[0092] As Figure 2A shown, it is a schematic diagram of a 5G network architecture based on a service-based architecture. Figure 2A The 5G network architecture shown may include three parts, namely the terminal device part, the data network (DN), and the operator network part. The functions of some network elements among them are briefly introduced below.

[0093] Among them, the operator network may include one or more of the following network elements: Network Exposure Function (NEF) network element, Policy Control Function (PCF) network element, Unified Data Management (UDM) network element, Network Repository Function (NRF) network element, Application Function (AF) network element, Access and Mobility Management Function (AMF) network element, Session Management Function (SMF) network element, (Radio) Access Network ((R)AN), and User Plane Function (UPF) network element, etc. In the above operator network, the part except the (radio) access network part can be called the core network part. For the convenience of description, hereinafter, (R)AN is taken as an example and referred to as RAN for description.

[0094] The terminal device, which can also be called User Equipment (UE), is a device with wireless transceiver functions. It can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, satellites, etc.). The terminal device can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0095] The above-mentioned terminal device can establish a connection with the operator network through an interface provided by the operator network (such as N1, etc.), and use services such as data and / or voice provided by the operator network. The terminal device can also access the DN through the operator network, use the operator services deployed on the DN, and / or services provided by a third party. Among them, the above-mentioned third party can be a service provider other than the operator network and the terminal device, and can provide other data and / or voice services to the terminal device. Among them, the specific manifestation form of the above-mentioned third party can be determined according to the actual application scenario and is not limited here.

[0096] The RAN is a sub-network of the operator network and is an implementation system between the service nodes and the terminal device in the operator network. For a terminal device to access the operator network, it first passes through the RAN and then can be connected to the service nodes of the operator network through the RAN. The RAN device in this application is a device that provides wireless communication functions for the terminal device, and the RAN device is also called an access network device. The RAN devices in this application include but are not limited to: the next-generation base station (g nodeB, gNB) in 5G, evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, etc.

[0097] The AMF network element is a control-plane network element provided by the operator network and is responsible for access control and mobility management for the terminal device to access the operator network. For example, it includes functions such as mobile status management, allocation of user temporary identity identifiers, authentication and authorization of users, etc.

[0098] The SMF network element is a control plane network element provided by the operator's network and is responsible for managing the PDU sessions of terminal devices. A PDU session is a channel for transmitting PDUs, and terminal devices need to use PDU sessions to transmit PDUs to and from the DN. The SMF network element is responsible for establishing, maintaining, and deleting PDU sessions, etc. The SMF network element includes session management (such as session establishment, modification, and release, including the tunnel maintenance between the UPF and the AN), the selection and control of UPF network elements, the selection of the Service and Session Continuity (SSC) mode, roaming, and other session-related functions.

[0099] The UPF network element is a gateway provided by the operator and is the gateway for communication between the operator's network and the DN. The UPF network element includes user plane-related functions such as packet routing and transmission, packet detection, service usage reporting, QoS processing, lawful interception, uplink packet detection, and downlink packet storage.

[0100] The DN is a network outside the operator's network. The operator's network can access multiple DNs, and various services can be deployed on the DN, which can provide services such as data and / or voice for terminal devices. For example, the DN is a private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminal devices. A control server for the sensors is deployed in the DN, and the control server can provide services for the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. Another example is that the DN is the internal office network of a company. The mobile phones or computers of the company's employees can be terminal devices, and the mobile phones or computers of the employees can access information, data resources, etc. on the company's internal office network.

[0101] The UDM network element is a control plane network element provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI), credentials, security context, and subscribed data of subscribed users in the operator's network. The information stored in the UDM network element can be used for the authentication and authorization of terminal devices to access the operator's network. Among them, the subscribed users of the above operator network can specifically be users who use the services provided by the operator network, such as users who use the mobile phone SIM card of China Telecom, or users who use the mobile phone SIM card of China Mobile, etc. The SUPI of the above subscribed users can be the number of the mobile phone SIM card, etc. The credentials and security context of the above subscribed users can be small files such as the encryption key of the mobile phone SIM card or information related to the encryption of the mobile phone SIM card, which are used for authentication and / or authorization. The above security context can be data (cookie) or token stored on the user's local terminal (such as a mobile phone), etc. The subscribed data of the above subscribed users can be the supporting services of the mobile phone SIM card, such as the data traffic package of the mobile phone SIM card or the use of the network, etc. It should be noted that information related to authentication and authorization, such as permanent identifiers, credentials, security contexts, authentication data (cookie), and tokens, are not distinguished or restricted in this application document of the present invention for the sake of convenience of description. Without special instructions, the embodiments of this application will be described by taking the security context as an example, but the embodiments of this application are equally applicable to authentication and / or authorization information in other expression forms.

[0102] The NEF network element is a control plane network element provided by the operator. The NEF network element opens the external interface of the operator's network to the third party in a secure manner. When the SMF network element needs to communicate with the network element of the third party, the NEF network element can act as a relay for the SMF network element to communicate with the network element of the third party. When acting as a relay, the NEF network element can act as the translation of the identification information of the subscribed user and the identification information of the network element of the third party. For example, when the NEF sends the SUPI of the subscribed user from the operator's network to the third party, it can translate the SUPI into its corresponding external identity (ID). Conversely, when the NEF network element sends the external ID (the network element ID of the third party) to the operator's network, it can translate it into SUPI.

[0103] The Application Function (AF) network element mainly provides application layer services and also supports interacting with the 5G core network to provide services, such as influencing data routing decisions, policy control functions, or providing some services of the third party to the network side. In this application, the AF network element includes an application server, and this application server refers to a third-party server.

[0104] The PCF network element is a control plane function provided by the operator and is used to provide policies to network elements. As an implementation method, the policies may include access control policies, mobility management policies, charging-related policies, QoS-related policies, authorization-related policies, etc.

[0105] The NRF network element can be used to provide a network element discovery function and provide network element information corresponding to the network element type based on the requests of other network elements. The NRF also provides network element management services, such as network element registration, update, deregistration, and network element status subscription and push, etc.

[0106] Figure 2A Among them, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be referred to the meanings defined in the standard protocol of the 3rd generation partnership project (3GPP), and are not restricted here.

[0107] Such as Figure 2B shown, it is a schematic diagram of the 5G network architecture based on point-to-point interfaces. The introduction of the functions of the network elements therein can be referred to Figure 2A the introduction of the functions of the corresponding network elements in, and will not be elaborated here. Figure 2B Compared with Figure 2A the main difference is that: Figure 2B the interfaces between the various network elements in are point-to-point interfaces, rather than service-based interfaces.

[0108] In Figure 2B the shown architecture, among them, the interface between the UE and the AMF network element is called the N1 interface, the interface between the AMF network element and the RAN device is called the N2 interface, the interface between the RAN device and the UPF network element can be called the N3 interface, the interface between the SMF network element and the UPF network element is called the N4 interface, the interface between the PCF network element and the AF network element is called the N5 interface, the interface between the UPF network element and the DN is called the N6 interface, the interface between the SMF network element and the PCF network element is called the N7 interface, the interface between the AMF network element and the UDM network element is called the N8 interface, the interface between different UPF network elements is called the N9 interface, the interface between the UDM network element and the SMF network element is called the N10 interface, the interface between the AMF network element and the SMF network element is called the N11 interface, the interface between different AMF network elements is called the N14 interface, and the interface between the AMF network element and the PCF network element is called the N15 interface.

[0109] It is understandable that the above network element or function can be either a network element in a hardware device, or a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above network element or function can be implemented by one device, or jointly implemented by multiple devices, or can also be a functional module within a device. The embodiments of the present application do not make specific limitations in this regard.

[0110] The mobility management network element, session management network element, policy control network element, application function network element, access network device, network exposure function network element, and user plane network element in this application can respectively be Figure 2A or Figure 2B the AMF, SMF, PCF, AF, RAN, NEF, UPF in

[0111] For example, Figures 3A to 3D As shown, there are four schematic diagrams of network architectures provided by this application, corresponding to four different solutions for solving the problems in the background art.

[0112] It should be noted that both the UPF and the AF are located in the local data center. Therefore, the UPF can also be referred to as the local UPF, and the AF can also be referred to as the local AF. Optionally, the local data center also includes a local NEF (such as the architecture shown in Figure 3C and Figure 3D ).

[0113] The central data center includes network elements such as the AMF, SMF, and PCF. Optionally, the central data center also includes a NEF, which can be referred to as the central NEF.

[0114] Referring to Figure 3A , the transmission path between the AF and the UPF (i.e., the local UPF shown in Figure 3A ) is:

[0115] AF - NEF - PCF - SMF - UPF.

[0116] Among them, in the downlink direction, AF notifies the UPF to perform event detection and report event reports through the NEF, PCF, and SMF respectively; in the uplink direction, the UPF sends the event report to the AF through the SMF, PCF, and NEF respectively.

[0117] The problem with this solution is that the path for the UPF to send event reports to the AF is too long and needs to pass through multiple network elements. Therefore, for services with high time sensitivity, the timeliness of event reports will be reduced, which is not conducive to the processing at the application layer.

[0118] For this reason, this application uses the following Figures 3B - 3E solution corresponding to the network architecture shown to solve the above Figure 3A problem of the long path in the architecture shown.

[0119] Refer to Figure 3B , the transmission path between the AF and the UPF (i.e., the local UPF shown in Figure 3B ) is as follows:

[0120] Downlink direction: AF -> NEF -> PCF -> SMF -> UPF. That is, AF notifies the UPF to perform event detection and report event reports through the NEF, PCF, and SMF respectively.

[0121] Uplink direction: UPF -> AF. That is, the UPF directly sends the event report to the AF through the interface between the UPF and the AF.

[0122] This solution shortens the path length for reporting event reports. Therefore, for services with high time sensitivity, the timeliness of event reports can be improved, which is beneficial to the processing at the application layer.

[0123] As an implementation method, if the UPF supports a service-based interface, the UPF can send event reports to the AF through the service-based interface between the UPF and the AF (which can be called the N4a interface).

[0124] Refer to Figure 3C , the transmission path between the AF and the UPF (i.e., the local UPF shown in Figure 3C ) is as follows:

[0125] Downlink direction: AF -> NEF (i.e., the local NEF shown in Figure 3C ) -> PCF -> SMF -> UPF. That is, AF notifies the UPF to perform event detection and report event reports through the NEF, PCF, and SMF respectively.

[0126] Uplink direction: UPF -> NEF (i.e., Figure 3CThe local NEF shown in -> AF. That is, the UPF directly sends the event report to the NEF through the interface between the UPF and the NEF, and then the NEF sends the event report to the AF.

[0127] This solution shortens the path length of reporting the event report. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing of the application layer.

[0128] As an implementation method, the UPF can send the event report to the NEF through the interface between the UPF and the NEF (which can be called the N4a interface), and then the NEF sends the event report to the AF through the N33 interface between the NEF and the AF. Among them, the interface between the UPF and the NEF can be the service-based interface of the UPF, or an interface obtained by enhancing the existing N4 interface of the UPF.

[0129] Reference Figure 3D , the transmission path between the AF and the UPF (i.e., Figure 3D the local UPF shown in) is as follows:

[0130] Downlink direction: AF -> local NEF -> NEF (which can also be called the central NEF) -> PCF -> SMF -> UPF. That is, the AF notifies the UPF to perform event detection and report the event report through the local NEF, NEF, PCF, and SMF respectively;

[0131] Uplink direction: UPF -> local NEF -> AF. That is, the UPF directly sends the event report to the local NEF through the interface between the UPF and the local NEF, and then the local NEF sends the event report to the AF.

[0132] This solution shortens the path length of reporting the event report. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing of the application layer.

[0133] As an implementation method, the UPF can send the event report to the local NEF through the interface between the UPF and the local NEF (which can be called the N4a interface), and then the local NEF sends the event report to the AF through the N33 interface between the local NEF and the AF. Among them, the interface between the UPF and the local NEF can be the service-based interface of the UPF, or an interface obtained by enhancing the existing N4 interface of the UPF.

[0134] Figure 3D The architecture shown and Figure 3C The main difference between the architecture shown is that: Figure 3D A central NEF is added in, and this architecture is applicable to scenarios where the local NEF in the local data center cannot communicate with the PCF in the central data center, or the communication is difficult.

[0135] In the uplink direction, the path for the UPF to send event reports in the Figure 3D shown architecture is the same as the path for sending event reports in the Figure 3C shown architecture. In the downlink direction, the path for the AF to notify the UPF to send event reports in the Figure 3D shown architecture is different from the path for notifying the UPF to send event reports in the Figure 3C shown architecture.

[0136] Refer to Figure 3E , the transmission path between the AF and the UPF (i.e., the local UPF shown in Figure 3E ) is as follows:

[0137] Downlink direction: AF -> NEF (which can also be called the central NEF) -> PCF -> SMF -> UPF. That is, the AF notifies the UPF to perform event detection and report event reports through the NEF, PCF, and SMF respectively;

[0138] Uplink direction: UPF -> local NEF -> AF. That is, the UPF directly sends the event report to the local NEF through the interface between the UPF and the local NEF, and then the local NEF sends the event report to the AF.

[0139] This solution shortens the path length for reporting event reports. Therefore, for services with high time sensitivity, the timeliness of event reports can be improved, which is beneficial to the processing at the application layer.

[0140] As an implementation method, the UPF can send event reports to the NEF through the interface between the UPF and the local NEF (which can be called the N4a interface), and then the local NEF sends the event reports to the AF through the N33 interface between the local NEF and the AF. Among them, the interface between the UPF and the local NEF can be the service-based interface of the UPF or an interface obtained by enhancing the existing N4 interface of the UPF.

[0141] In the uplink direction, the path for the UPF to send event reports in the Figure 3E shown architecture is the same as the path for sending event reports in the Figure 3D shown architecture. In the downlink direction, the path for the AF to notify the UPF to send event reports in the Figure 3E shown architecture is different from the path for notifying the UPF to send event reports in the Figure 3C shown architecture.

[0142] Based on the above Figures 3B to 3E shown architecture, the method for sending event reports is introduced below. As Figure 4As shown in the figure, it is a schematic flow diagram of a method for sending an event report provided by this application. The method includes the following steps:

[0143] Step 401, the AF sends an event notification request to the NEF. The event notification request includes event notification request information and a first notification address. The first notification address is the address of the AF for receiving the first event report. The event notification request is used to request the UPF to send the first event report corresponding to the event notification request information to the first notification address. Accordingly, the NEF can receive the event notification request. The event notification request is also referred to as an event notification subscription or an event subscription. The event report is also referred to as an event notification.

[0144] Among them, the event notification request information includes an event identifier and / or event monitoring control information. Among them, the event identifier is used to identify an event. The event monitoring control information is used to trigger the corresponding network element to generate an event report. For example, when the UPF receives the event monitoring control information, the UPF can generate an event report according to the event monitoring control information and report it to the SMF.

[0145] As an example, for a QoS monitoring event, the event notification request information carried in the event notification request message may include a QoS Monitoring event identifier, or may include a QoS Monitoring event identifier and QoS Monitoring control information, or may include QoS Monitoring control information. Among them, the QoS Monitoring event identifier is used to identify the QoS Monitoring event. The QoS Monitoring control information includes parameters for requesting QoS Monitoring (such as at least one of the parameters for indicating detection of uplink packet delay, the parameters for indicating detection of downlink packet delay, or the parameters for indicating detection of round-trip packet delay) and a reporting frequency (such as at least one of event-triggered reporting, periodic reporting, or reporting when a PDU session is released). Exemplarily, if the reporting frequency is event-triggered reporting, the QoS Monitoring control information may further include at least one of a downlink packet delay threshold, an uplink packet delay threshold, or a round-trip packet delay threshold, and may further include a minimum waiting time (i.e., the minimum time interval between two event reports). Optionally, when the detected uplink packet delay is greater than the uplink packet delay threshold, the detected uplink packet delay is triggered for reporting. When the detected downlink packet delay is greater than the downlink packet delay threshold, the detected downlink packet delay is triggered for reporting. When the detected round-trip packet delay is greater than the round-trip packet delay threshold, the detected round-trip packet delay is triggered for reporting. Exemplarily, if the reporting frequency is periodic reporting, the QoS Monitoring control information may further include a periodic reporting period.

[0146] As an example, for a usage monitoring event, the event notification request information carried in the event notification request message may include a usage monitoring event identifier, or may include a usage monitoring event identifier and usage monitoring control information (such as a usage threshold), or may include usage monitoring control information.

[0147] Among them, the first notification address includes at least one of the Internet Protocol (IP) address of the AF, the Fully Qualified Domain Name (FQDN), or the Uniform Resource Identifier (URI).

[0148] In this application, the event notification request in step 401 is also referred to as the third event notification request.

[0149] Among them, when based on Figure 3BThe described architecture Figure 4 In it, the NEF is the central NEF, and step 401 is: The AF sends an event notification request to the central NEF.

[0150] When based on Figure 3C the described architecture Figure 4 In it, the NEF is the local NEF, and step 401 is: The AF sends an event notification request to the local NEF.

[0151] When based on Figure 3D the shown architecture Figure 4 in which the NEF is Figure 3D the central NEF in it, step 401 is: The AF sends an event notification request to the local NEF, and the local NEF further sends an event notification request to the central NEF. The event notification request sent by the local NEF to the central NEF carries the first notification address assigned by the local NEF. The first notification address of the local NEF includes at least one of the IP address, FQDN, or URI of the local NEF.

[0152] When based on Figure 3E the shown architecture Figure 4 in which the NEF is Figure 3E the central NEF in it, step 401 is: The AF sends an event notification request to the central NEF.

[0153] As an implementation, the event notification request in this step may also carry the location information of the AF, so that the PCF or SMF determines, based on the location information of the AF, that the AF requesting the event notification is a local AF (i.e., the AF in the local data center). Alternatively, the event notification request in this step carries an indication information (also referred to as the seventh indication information in this application), and this indication information is used to indicate that the event notification request is a local event notification request, that is, to notify the UPF to directly send an event report to the local NEF or AF.

[0154] Based on Figure 3D the shown architecture, the local NEF may further carry the location information of the local NEF in the event notification request sent to the central NEF, so that the PCF or SMF determines, based on the location information of the local NEF, that the NEF requesting the event notification is a local NEF (i.e., the NEF in the local data center). Alternatively, the local NEF further carries an indication information (also referred to as the seventh indication information in this application) in the event notification request sent to the central NEF, and this indication information is used to indicate that the event notification request is a local event notification request, that is, to notify the UPF to directly send an event report to the local NEF.

[0155] As an implementation, a notification association identifier may also be carried in the event notification request in step 401, and the notification association identifier is used by the AF to associate the first event report with the event notification request.

[0156] Based on Figure 3D the architecture shown, the event notification request sent by the local NEF to the central NEF may carry a notification association identifier assigned by the local NEF.

[0157] Step 402, the NEF sends an event notification request to the PCF. The event notification request includes event notification request information and a first notification address. The first notification address is the address of the event report receiving network element for receiving the first event report, and the event report receiving network element is the AF or the NEF. Correspondingly, the PCF can receive the event notification request.

[0158] The event notification request information is the same as the event notification request information in step 401 above.

[0159] In this application, the event notification request in this step is also referred to as the first event notification request.

[0160] For this step 402, three implementation methods are given below:

[0161] Implementation method 1: For Figure 3B the architecture shown, Figure 4 if the NEF in

[0162] is the central NEF, then the first notification address in the event notification request is the address of the AF for receiving the first event report, that is, the first notification address is the same as the first notification address in step 401.

[0163] Combined with the above Implementation Method 1, if the event notification request in step 401 carries the seventh indication information or the location information of the AF, the NEF can obtain the location information of the AF or the seventh indication information, and then can carry the location information of the AF or an indication information (this application refers to this indication information as the eighth indication information, and the eighth indication information is the above-mentioned seventh indication information or is generated according to the seventh indication information) in the event notification request in step 402. Or, if the event notification request in step 401 does not carry the above-mentioned seventh indication information and does not carry the location information of the AF, the NEF can determine the location information of the AF according to the first notification address in the event notification request in step 401, so as to carry the location information of the AF or the eighth indication information in the event notification request in this step 402. The eighth indication information is used to indicate that this event notification request is a local event notification request (that is, to notify the UPF to directly send an event report to the AF) or is used to indicate that the AF is a local AF.

[0164] Implementation Method 2: For Figure 3C , Figure 4 the NEF in is a local NEF, and the first notification address in the event notification request in this step 402 is the address of the NEF for receiving the first event report, that is, the first notification address allocated by the local NEF.

[0165] Based on this Implementation Method 2, the UPF will send the first event report corresponding to the event notification request information to the local NEF through the interface between the UPF and the local NEF, and then the local NEF will send the first event report to the AF.

[0166] Combined with the above Implementation Method 2, the location information of the NEF can also be carried in the event notification request of this step, so that the PCF or the SMF can determine according to the location information of the NEF that the address for receiving the event report is a local NEF (that is, the NEF in the local data center). Or, an indication information is carried in the event notification request of this step, and the indication information is used to indicate that this event notification request is a local event notification request (that is, to notify the UPF to directly send an event report to the local NEF).

[0167] Implementation Method 3: For Figure 3D the architecture shown, Figure 4 the NEF in is a central NEF, and the first notification address in the event notification request in this step 402 is the address of the local NEF for receiving the first event report, that is, the notification address in this step 402 is the address of the local NEF for receiving the first event report sent by the local NEF to the central NEF in step 401.

[0168] Based on the third implementation method, the UPF will send the first event report corresponding to the event notification request information to the local NEF through the interface between the UPF and the local NEF, and then the local NEF will send the first event report to the AF.

[0169] Combined with the above third implementation method, the event notification request in this step may also carry the location information of the local NEF, so that the PCF or the SMF can determine based on the location information of the local NEF that the one receiving the event report is a local NEF (i.e., the NEF of the local data center). Alternatively, an indication information is carried in the event notification request in this step, and this indication information is used to indicate that the event notification request is a local event notification request.

[0170] Implementation method four, for Figure 3E the architecture shown, Figure 4 if the NEF in

[0171] is the central NEF, then the first notification address in the event notification request is the address of the AF for receiving the first event report, that is, the first notification address is the same as the first notification address in step 401. Optionally, the NEF determines the address of the local NEF corresponding to the first notification address and sends the address of the local NEF to the PCF.

[0172] Through the above implementation method one, the UPF can directly send the first event report to the AF, or through the above implementation methods two, three, and four, the UPF sends the first event report to the local NEF, and then the local NEF sends the first event report to the AF, thereby shortening the path for reporting the event report.

[0173] As an implementation method, if the event notification request in step 401 above carries a notification association identifier, the event notification request in step 402 may also carry a notification association identifier. Among them, for Figure 3C 、 Figure 3D the architecture, the event notification request in this step 402 carries the notification association identifier assigned by the local NEF, and for Figure 3B ,the event notification request in this step 402 carries the notification association identifier received in step 401.

[0174] Step 403: The PCF sends an event notification request to the SMF. The event notification request includes event notification request information and a first notification address. This event notification request is used to request the UPF to send a first event report corresponding to the event notification request information to the first notification address. Accordingly, the SMF can receive this event notification request. The event notification request information is the same as the event notification request information in step 402 above.

[0175] In this application, the event notification request in this step is also referred to as the second event notification request.

[0176] In the first scenario (for implementation method 1 of step 402), that is, the first notification address in the event notification request of step 402 above is the address of the AF for receiving the first event report, then the first notification address in the event notification request of step 403 is also the address of the AF for receiving the first event report.

[0177] For this first scenario, if the event notification request of step 402 carries the eighth indication information or the location information of the AF, then the PCF can obtain the location information of the AF or the eighth indication information, and then can carry the location information of the AF or an indication information (this indication information is also referred to as the first indication information in this application, and the first indication information can be the same as the eighth indication information, or is generated based on the eighth indication information) in the event notification request of step 403. This first indication information is used to indicate that the event notification request of step 403 is a local event notification request. Or, if the event notification request of step 402 does not carry the above-mentioned eighth indication information and does not carry the location information of the AF, then the PCF can determine the location information of the AF based on the first notification address in the event notification request of step 402, so as to carry the location information of the AF or the above-mentioned first indication information in the event notification request of this step 403.

[0178] In the second scenario (for implementation methods 2 and 3 of step 402), that is, the first notification address in the event notification request of step 402 above is the address of the local NEF for receiving the first event report, then the first notification address in the event notification request of step 403 is also the address of the local NEF for receiving the first event report.

[0179] For the second case, if the event notification request in step 402 carries indication information or the location information of the NEF, the PCF can obtain the location information of the NEF or the indication information, and then can carry the location information of the NEF or an indication information (this application also refers to this indication information as the first indication information) in the event notification request in step 403. The eighth indication information is used to indicate that the event notification request in step 403 is a local event notification request. Alternatively, if the event notification request in step 402 does not carry the above indication information and does not carry the location information of the NEF, the PCF can determine the location information of the NEF according to the first notification address in the event notification request in step 402, so as to carry the location information of the NEF or the above first indication information in the event notification request in this step 403.

[0180] In the third case (for implementation method 4 of step 402), that is, the first notification address in the event notification request in the above step 402 is the address of the AF for receiving the first event report, then the first notification address in the event notification request in step 403 is the address of the AF for receiving the first event report. Optionally, the event notification request in step 402 further includes the address of the local NEF. The address of the local NEF can be determined by the NEF according to the first notification address.

[0181] As an implementation method, if the event notification request in step 402 carries a notification association identifier, the event notification request in step 403 can also carry the notification association identifier.

[0182] It should be noted that the UPF detects an event according to the event notification request information, and after generating an event report, it can either report only to the AF or report to the AF and the SMF at the same time. Among them, the one reported to the AF is called the first event report corresponding to the event notification request information, and the one reported to the SMF is called the second event report. Further, the SMF generates a third event report according to the second event report and reports the third event report to the PCF.

[0183] The above first event report and second event report can be the same event report or different event reports. For example, for the same event notification request information, the conditions for generating an event are different. For example, for the QoS Monitoring event, the types of detection delays may be different.

[0184] Next, the method for determining whether the UPF needs to report a second event report to the SMF will be described.

[0185] The first implementation method is: determine whether the UPF needs to report a second event report corresponding to the event notification request information through protocol pre - definition or through pre - configuration.

[0186] The second implementation method is as follows: The PCF decides whether the UPF needs to report a second event report corresponding to the event notification request information to the SMF and indicates it through indication information.

[0187] For this second implementation method, if the PCF decides that the UPF needs to report a second event report corresponding to the event notification request information to the SMF, then the fifth indication information can be carried in step 403, which is used to indicate the SMF to send a third event report corresponding to the event notification request information to the PCF. After receiving the fifth indication information, the SMF determines that it needs to report the third event report to the PCF. Thus, the SMF can instruct the UPF to report the second event report corresponding to the event notification request information to the SMF. Subsequently, the SMF generates a third event report based on the second event report and sends the third event report to the PCF.

[0188] Step 404, the SMF determines that the UPF needs to send a first event report to a second notification address.

[0189] Before this step 404, the SMF first determines the second notification address according to the first notification address.

[0190] As an implementation method, the second notification address is the same as the first notification address. In this case, the second notification address can also be referred to as the first notification address. Or both the second notification address and the first notification address are referred to as the notification address.

[0191] As another implementation method, the second notification address is different from the first notification address. For example, the first notification address is at least two of an IP address, an FQDN, or a URI, and the second notification address is one or two of the first notification address. For another example, the first notification address is a URI, and the second notification address is an IP address determined according to the URI (for example, the SMF determines the IP address according to the server address attribute item in the URI, or the SMF determines the IP address according to the local configuration and the URI, or the SMF determines the IP address by performing a DNS query on the URI). For another example, the first notification address is an FQDN, and the second notification address is an IP address determined according to the FQDN (such as the SMF determines the IP address according to the local configuration and the FQDN, or the SMF determines the IP address by performing a DNS query on the FQDN).

[0192] This step is optional. When this step is not executed, it can be predefined by the protocol that the UPF needs to send a first event report to the second notification address.

[0193] The ways for the SMF to determine that the UPF needs to send a first event report to the second notification address include but are not limited to:

[0194] Method 1: The SMF determines, based on the first notification address in the event notification request in step 403, that the UPF needs to send a first event report to the second notification address.

[0195] For example, the SMF is pre-configured with the attribute information of the second notification address, and this attribute information is used to indicate whether the second notification address is a local address. When the SMF determines that the second notification address is a local address, it determines that the UPF needs to send a first event report to the second notification address.

[0196] Method 2: If the SMF, based on the location information of the event report receiving network element (AF or NEF) included in the event notification request in step 403, then the SMF determines, according to the location information of the event report receiving network element, that the UPF sends a first event report to the second notification address.

[0197] For example, if the location information of the AF is carried in the event notification request in step 403, the SMF determines, based on the location information of the AF, that the AF is a local AF, and then determines that the UPF needs to send a first event report to the second notification address (i.e., the address of the AF).

[0198] For another example, if the location information of the NEF is carried in the event notification request in step 403, the SMF determines, based on the location information of the NEF, that the NEF is a local NEF, and then determines that the UPF needs to send a first event report to the second notification address (i.e., the address of the NEF).

[0199] Method 3: If the first indication information is carried in the event notification request in step 403, and the first indication information is used to indicate that the event notification request is a local event notification request, then the SMF determines, based on the first indication information, that the UPF sends a first event report to the second notification address.

[0200] Method 4: If the indication information for indicating that the event notification request is a repeated event notification request is carried in the event notification request in step 403, then the SMF determines, based on this indication information, that the UPF sends a first event report to the second notification address.

[0201] Step 405: The SMF determines whether it is necessary to send a third event report to the PCF.

[0202] This step is optional. When this step is not executed, it can be predefined or pre-configured by the protocol that the SMF needs to send a third event report to the PCF, or it is not necessary to send a third event report to the PCF.

[0203] When this step 405 is executed, that is, when the SMF determines whether it is necessary to send a third event report to the PCF, the methods for the SMF to determine whether it is necessary to send a third event report to the PCF include but are not limited to:

[0204] The SMF receives indication information from the PCF, which indicates whether the SMF needs to send a third event report to the PCF. For example, when the event notification request in step 403 carries the fifth indication information described above, the SMF determines that it needs to send a third event report to the PCF according to the fifth indication information. For another example, when the event notification request in step 403 carries other indication information, which is used to indicate that the SMF does not need to send a third event report to the PCF, the SMF determines that it needs to send a third event report to the PCF according to the other indication information.

[0205] Step 406, the SMF sends a first message to the UPF. Correspondingly, the UPF can receive this first message.

[0206] As an implementation, this first message can be an event notification request, or it can also be a notification message.

[0207] This first message includes event notification request information and a second notification address, and this first message is used to instruct the UPF to send a first event report corresponding to the event notification request information to the second notification address. Or it can be understood that the event notification request information and the second notification address are used to instruct the UPF to send a first event report corresponding to the event notification request information to the second notification address.

[0208] In the first case (for implementation method 1 of step 402), when the first notification address in the event notification request in step 403 above is the address of the AF for receiving the first event report, then the second notification address in the first message in step 406 is also the address of the AF for receiving the first event report.

[0209] In the second case (for implementation methods 2 and 3 of step 402), when the first notification address in the event notification request in step 403 above is the address of the local NEF for receiving the first event report, then the second notification address in the first message in step 406 is also the address of the local NEF for receiving the first event report. In the third case (for implementation method 4 of step 402), when the first notification address in the event notification request in step 403 above is the address of the AF for receiving the first event report, then the second notification address in the first message in step 406 is also the address of the AF for receiving the first event report. In addition, the SMF carries the address of the corresponding local NEF in the first message. The address of the local NEF is received by the SMF from the PCF or determined by the SMF according to the first notification address.

[0210] As an implementation, if the event notification request in step 403 carries a notification association identifier, then the event notification request in step 406 can also carry this notification association identifier.

[0211] The following describes the specific implementation method for the SMF to instruct the UPF to send the first event report corresponding to the event notification request message to the second notification address.

[0212] Implementation method 1: If it is determined in step 405 that the SMF does not need to send the third event report to the PCF, then the second indication information can be carried in the first message in step 406. This second indication information is used to instruct the UPF to send the first event report corresponding to the event notification request message to the second notification address.

[0213] For this implementation method 1, if the SMF determines that the UPF needs to send the first event report to the second notification address and determines that the SMF does not need to send the third event report to the PCF, then the SMF only needs to instruct the UPF to send the first event report corresponding to the event notification request message to the second notification address through the second indication information.

[0214] Implementation method 2: If it is determined in step 405 that the SMF needs to send the third event report to the PCF, then the second indication information and the third indication information can be carried in the first message in step 406. This second indication information is used to instruct the UPF to send the first event report corresponding to the event notification request message to the second notification address, and the third indication information is used to instruct the UPF to send the second event report corresponding to the event notification request message to the SMF.

[0215] For this implementation method 2, if the SMF determines that the UPF needs to send the first event report to the second notification address and determines that the SMF needs to send the third event report to the PCF, then on the one hand, the SMF instructs the UPF to send the first event report corresponding to the event notification request message to the second notification address through the second indication information; on the other hand, the SMF instructs the UPF to send the second event report corresponding to the event notification request message to the SMF through the third indication information. Thus, the SMF generates the third event report based on the second event report and sends the third event report to the PCF.

[0216] As an alternative solution to this implementation method 2, if it is determined in step 405 that the SMF needs to send the third event report to the PCF, then the first message in step 406 does not carry the second indication information and the third indication information, but carries the fourth indication information. This fourth indication information is used to instruct the UPF to send the first event report corresponding to the event notification request message to the second notification address and to instruct the UPF to send the second event report corresponding to the event notification request message to the SMF. That is, this fourth indication information has the functions of the above-mentioned second indication information and third indication information.

[0217] Step 407, the UPF sends the first event report to the second notification address of the event report receiving network element. Correspondingly, the event report receiving network element can receive this first event report.

[0218] That is, when the UPF detects the event corresponding to the event notification request information, it generates a first event report and then sends the first event report to the second notification address.

[0219] When the second notification address is the address of the AF for receiving the first event report, the UPF sends the first event report to the AF. Among them, for implementation method four of step 402, the way for the UPF to send the first event report to the AF can be: the UPF sends the first event report and the second notification address to the local NEF, and then the local NEF sends the first event report to the second notification address.

[0220] When the second notification address is the address of the local NEF for receiving the first event report, the UPF sends the first event report to the local NEF, and then the local NEF sends the first event report to the AF.

[0221] Optionally, when the notification association identifier is carried in the first message of step 406 above, in this step 407 or through other steps, the UPF sends the notification association identifier to the second notification address, and this notification association identifier is used for the event report receiving network element to associate the first event report with the event notification request.

[0222] In one implementation, the event identifier in the first message of step 406 is QoS detection (QoS Monitoring), then the first message may further include the QoS parameters to be detected (the QoS parameters to be detected are the event monitoring control information), and the QoS parameters to be detected are from the AF and can be sent to the UPF through steps 401 to 403 and step 406. That is, the event monitoring control information carried in the event notification request of the above steps 401 to 403 includes the event identifier and the event monitoring control information. Among them, the event identifier is QoS detection (also called the QoS detection event identifier), and the event monitoring control information includes the QoS parameters to be detected. The QoS parameters to be detected can be, for example, one or more of the uplink packet delay report threshold, the downlink packet delay report threshold, the round-trip packet delay report threshold, and the reporting frequency. Based on this implementation, optionally, after or before step 406, the SMF may further send a sixth indication information to the RAN, and this sixth indication information may also be called the indication of QoS Monitoring, which is used to instruct the RAN to perform QoS detection. The RAN measures the delay of the Uu interface between the RAN and the UE according to the sixth indication information, and the UPF and the RAN interact to measure the delay between the UPF and the RAN. Thus, the UPF can carry the delay between the UPF and the RAN and the delay of the Uu interface between the RAN and the UE in the first event report.

[0223] In yet another implementation, if the event identifier in the first message of step 406 is usage monitoring, the first message may further include a usage threshold, which is sourced from the AF and can be sent to the UPF via steps 401 to 403 and step 406.

[0224] As an example, if the UPF supports the service-based interface, the UPF sends an HTTP POST message to the local NEF or AF. The request URI in the HTTP POST message is the second notification address (such as a URI), and the HTTP POST message body includes the detected event report (i.e., the first event report). If a notification association identifier is also received in step 406, the received notification association identifier may also be included in the HTTP POST message body.

[0225] As an example, if the UPF supports the Packet Forwarding Control Protocol (PFCP), the UPF sends a PFCP message to the local NEF or AF. The destination address of the PFCP message is the second notification address (such as an IP address), and the port number is 8805. The Session Endpoint Identifier (SEID) field is not included in the PFCP header, or the SEID field is set to 0, and the PFCP message body includes the event report (i.e., the first event report). If a notification association identifier is also received in step 406, the received notification association identifier is also included in the PFCP message body.

[0226] Step 408, the UPF sends a second event report to the SMF. Correspondingly, the SMF may receive the second event report.

[0227] This step 408 is optional. This step 408 is executed when the UPF determines that it is necessary to send a second event report to the SMF. For example, if the first message in the above step 406 carries the above third indication information or fourth indication information, the UPF may determine that it is necessary to send a second event report to the SMF.

[0228] Step 409, the SMF sends a third event report to the PCF. Correspondingly, the PCF may receive the third event report.

[0229] This step 409 is optional. This step 409 is executed when the SMF determines in the above step 405 that it is necessary to send a third event report to the PCF.

[0230] Based on the above solution, since the UPF can directly report event reports to the AF, or report event reports to the AF through the local NEF, the path length of reporting event reports is greatly shortened. Therefore, for services with high time sensitivity, the timeliness of event reports can be improved, which is beneficial to the processing at the application layer.

[0231] The following combines Figures 5 to 7 , and specifically describes Figure 4 the different methods for sending event reports introduced in Figure 5 Among them, Figure 3B corresponds to the network architecture shown in Figure 6 Among them, Figure 3C corresponds to the network architecture shown in Figure 7 Among them, Figure 3D corresponds to the network architecture shown in

[0232] As Figure 5 shown, the present application provides a schematic diagram of a method for sending event reports. This embodiment is based on Figure 3B the architecture. The AF requests event detection through the NEF, and the UPF can directly send event reports to the AF. In addition, the UPF can also send event reports to the SMF at the same time.

[0233] It should be noted that the following steps 502 to step 505 and the following steps 506 to step 510 are alternatives. Specifically, Figure 5 in the embodiment shown in

[0234] In the first implementation manner, steps 501 to step 505 and steps 511 to step 522 are executed. This implementation manner is for an established and ongoing PDU session; in the second implementation manner, steps 501, steps 506 - step 522 are executed. This implementation manner is for an established and ongoing PDU session or a future-established PDU session.

[0235] The method includes the following steps:

[0236] Step 501, the UE requests to establish a PDU session, and the UE and the network side complete the establishment of the PDU session.

[0237] An N4 session is established between the SMF and the UPF. The SMF sends a notification address to the UPF, and this notification address is the address of the SMF (such as the IP address of the SMF). Optionally, the SMF can also send the notification association identifier (Sequence Id) of the SMF to the UPF. This notification association identifier is used by the SMF to associate the event report received from the UPF (i.e., Figure 4 the second event report of the embodiment) with the event notification request sent by the SMF to the UPF.

[0238] Optionally, the UPF notifies the SMF of its ability to support local event notification, and the SMF further notifies the PCF of the UPF's ability to support local event notification.

[0239] A user plane channel is established between the UE, the RAN, and the UPF, and the UE accesses services with the AF.

[0240] Step 502, the AF sends an event notification request to the NEF. Correspondingly, the NEF can receive this event notification request.

[0241] This NEF is the Figure 3B central NEF in

[0242] This event notification request can be, for example, an Npcf_PolicyAuthorization_Create request or an Nnef_AFsessionWithQoS_Create Request.

[0243] This event notification request includes the address of the UE, event notification request information, and a first notification address. The address of the UE is the address of the UE associated with the PDU session established in step 501 (such as the IP address of the UE). The event identifier is the identifier of the event to be subscribed to. The first notification address is the address of the AF for receiving the first event report (such as an IP address). This event notification request is used to request the UPF to send the first event report corresponding to this event notification request information to the first notification address.

[0244] Among them, for the description of the event notification request information, reference can be made to the relevant description in the Figure 4 corresponding embodiment and will not be elaborated here.

[0245] Optionally, this event notification request can also include flow description information.

[0246] Optionally, this event notification request also includes a notification association identifier. This notification association identifier is used by the AF to associate the above first event report with this event notification request. When multiple event notification requests of the AF have the same notification address, different event notification requests can be distinguished by different notification association identifiers.

[0247] Optionally, the event notification request may include the location information of the AF, such as a data network access identifier (DNAI). Alternatively, the event notification request may include indication information (i.e., Figure 4 the seventh indication information of the embodiment), which is used to indicate that the event notification request is a local event notification request, or which is used to indicate that the AF is a local AF.

[0248] Optionally, if the event identifier carried in the event notification request is QoS Monitoring, the event notification request may further carry QoS parameters to be detected (the QoS parameters to be detected are the event monitoring control information), and the QoS parameters may be, for example, one or more of an uplink packet delay reporting threshold, a downlink packet delay reporting threshold, a round-trip packet delay reporting threshold, and a reporting frequency.

[0249] Optionally, if the event identifier carried in the event notification request is usage monitoring, the event notification request may further carry a usage threshold.

[0250] Step 503: After obtaining the address of the PCF by interacting with a Binding Support Function (BSF) network element (not shown in the figure), the NEF sends an event notification request to the PCF. Correspondingly, the PCF may receive the event notification request from the NEF.

[0251] The event notification request includes a first notification address and event notification request information obtained from the event notification request in step 502 above.

[0252] The event notification request may be, for example, an Npcf_PolicyAuthorization_Create request.

[0253] Optionally, if the event notification request in step 502 above does not carry the location information of the AF and does not carry the above seventh indication information, the NEF may determine the location information of the AF based on the first notification address in the event notification request in step 502, and thus carry the location information or indication information of the AF in the event notification request in this step 503 (i.e., Figure 4 the eighth indication information of the embodiment), which is used to indicate that the event notification request is a local event notification request or is used to indicate that the AF is a local AF.

[0254] Step 504: The PCF sends an event notification request response to the NEF. Correspondingly, the NEF may receive the event notification request response.

[0255] The event notification request response can be, for example, Npcf_Policy Authorization_CreateResponse.

[0256] Step 505, the NEF sends an event notification request response to the AF. Correspondingly, the AF can receive this event notification request response.

[0257] The event notification request response can be, for example, Npcf_Policy Authorization_CreateResponse.

[0258] As another implementation method, the above steps 502 - 505 can also be replaced by the following steps 506 - 509.

[0259] Step 506, the AF sends an event notification request to the NEF. Correspondingly, the NEF can receive this event notification request.

[0260] This NEF is Figure 3B the central NEF in

[0261] The event notification request can be, for example, Nnef_EventExposure_Subscribe request.

[0262] The content carried in this event notification request is basically the same as that carried in the event notification request in step 502 above. The main difference is that the event notification request in step 502 above carries the identifier of the UE, while the event notification request in this step 506 carries an external group identifier or indication information for indicating all UEs. This external group identifier is used to indicate that this event notification request applies to the UEs corresponding to this external group identifier (which can be one or more UEs), and this indication information for indicating all UEs is used to indicate that this event notification request applies to all UEs.

[0263] Step 507, the NEF sends the event notification request to all PCFs. Correspondingly, the PCF can receive the event notification request from the NEF.

[0264] The event notification request in this step 507 carries the first notification address and event notification request information obtained from step 506. However, it should be noted that if the external group identifier is carried in the event notification request in step 506, the NEF needs to map this external group identifier to an internal group identifier, and the event notification request in this step 507 carries this internal group identifier instead of the external group identifier. If the above indication information for indicating all UEs is carried in the event notification request in step 506, the event notification request in this step 507 can also carry this indication information for indicating all UEs.

[0265] The event notification request can be, for example, an Npcf_EventExposure_Subscribe Request.

[0266] Optionally, if the event notification request in step 506 does not carry the location information of the AF and does not carry the seventh indication information, the NEF can determine the location information of the AF based on the first notification address in the event notification request in step 506, so as to carry the location information or indication information of the AF in the event notification request in this step 507 (i.e., Figure 4 the eighth indication information of the embodiment), and the eighth indication information is used to indicate that the event notification request is a local event notification request or to indicate that the AF is a local AF.

[0267] Step 508, the PCF sends an event notification request response to the NEF. Correspondingly, the NEF can receive the event notification request response.

[0268] The event notification request response can be, for example, an Npcf_EventExposure_Subscribe Response.

[0269] Step 509, the NEF sends an event notification request response to the AF. Correspondingly, the AF can receive the event notification request response.

[0270] The event notification request response can be, for example, an Nnef_EventExposure_Subscribe Response.

[0271] Step 510, for the scenario of establishing a PDU session in the future, the UE establishes a PDU session.

[0272] This PDU session is a different session from the PDU session in step 501.

[0273] This step 510 is optional.

[0274] It should be noted that when performing the above steps 502 to 505, this step 510 is not executed. When performing the above steps 506 to 509, this step 510 can be executed or not executed.

[0275] Step 511, the PCF performs policy decision-making.

[0276] If the above steps 502 - 505 are executed, the PCF can perform session binding in step 511, and then formulate a Policy and Charging Control (PCC) rule for the PDU session established in step 501.

[0277] If the above steps 506 - 509 are executed, when the internal group identifier is carried in the event notification request in step 507, the PCF formulates PCC rules for all PDU sessions belonging to this internal group identifier; when the indication information for indicating all UEs is carried in the event notification request in step 507, the PCF formulates PCC rules for the PDU sessions of all UEs.

[0278] Among them, the PCC rules include event notification request information and a first notification address. Optionally, a notification association identifier may also be included. If the event identifier is QoS Monitoring, the PCC rules also include the QoS parameters to be measured as described above (the QoS parameters to be measured are the event monitoring control information).

[0279] The event notification request information includes an event identifier and / or event monitoring control information.

[0280] Optionally, when the event is QoS Monitoring and the event notification request information carried in the PCC rules only includes QoS Monitoring control information and does not include the QoS Monitoring event identifier, the PCF may decide to provide a policy control request trigger (PCRT) for QoS Monitoring to the SMF. If the PCF has previously provided a policy control request trigger for QoS Monitoring to the SMF, then the PCF may not provide a policy control request trigger for QoS Monitoring in this step.

[0281] Optionally, if the location information of the AF or the eighth indication information is also carried in step 503 or step 507, the PCC rules may also carry the location information of the AF or an indication information (i.e., Figure 4 the first indication information in the embodiment).

[0282] Optionally, the PCF determines to carry the location information of the AF or an indication information (i.e., Figure 4 the first indication information in the embodiment) in the PCC rules according to the first notification address.

[0283] Optionally, the PCF determines to carry the location information of the AF or the first indication information in the PCC rules according to the ability of the UPF obtained in step 501 or step 510 to support local event notification.

[0284] Optionally, if the PCF decision event report needs to be reported locally to the AF and also to the SMF, the PCC rule can also carry an indication of duplicate reporting (duplicating Report). This indication of duplicate reporting causes the UPF to send a first event report to the AF and the SMF to send a third event report to the PCF. Alternatively, instead of carrying this indication of duplicate reporting, the PCC rule carries a Figure 4 fifth indication information in the embodiment, which can also achieve the purpose of indicating duplicate reporting. For details, refer to Figure 4 the description of the embodiment.

[0285] Optionally, the PCF determines whether to carry an indication of duplicate reporting or the fifth indication information in the PCC rule based on the UPF's ability to support local event notification obtained in step 501 or step 510.

[0286] Optionally, it can also be predefined or preconfigured by the protocol whether the UPF needs to report events locally to the AF and also to the SMF. In step 512, the PCF sends an event notification request to the SMF corresponding to the PDU session. This event notification request includes the PCC rule in step 511. Correspondingly, the SMF can receive this event notification request.

[0287] Optionally, this event notification request also includes the QoS Monitoring PCRT described above.

[0288] This event notification request can be, for example, an Npcf_SMPolicyControl_UpdatNotify request.

[0289] In step 513, after installing the PCC rule, the SMF returns an event notification request response to the PCF. Correspondingly, the PCF can receive this event notification request response.

[0290] This event notification request response can be, for example, an Npcf_SMPolicyControl_UpdatNotifyresponse.

[0291] In step 514, the SMF determines based on the PCC rule that event detection requires the assistance of the RAN to complete. If the event identifier is a QoSMonitoring event identifier and / or the event monitoring control information is QoS Monitoring control information, the SMF sends a request message to the AMF. This request message carries an indication of QoS Monitoring. Correspondingly, the AMF can receive this request message.

[0292] This indication of QoS Monitoring is Figure 4 the sixth indication information in the embodiment.

[0293] The request message can be, for example, a Namf_Communication_N1N2MessageTransfer Request message.

[0294] Step 515, the AMF sends an N2 request message to the RAN. The N2 request message includes an indication of QoS Monitoring. Accordingly, the RAN can receive the N2 request message. Also, the RAN sends an N2 response message to the AMF, and accordingly the AMF can receive the N2 response message.

[0295] Step 516, the AMF sends a response message to the SMF. Accordingly, the SMF can receive the response message.

[0296] The response message can be, for example, a Namf_Communication_N1N2MessageTransfer Response message.

[0297] The above steps 514 - step 516 are optional steps.

[0298] Step 517, the SMF sends an N4 session modification request to the UPF. The N4 session modification request includes a second notification address and event notification request information. Accordingly, the UPF can receive the N4 session modification request.

[0299] Among them, the SMF can determine the second notification address according to the first notification address. As an implementation manner, the second notification address is the same as the first notification address. In this case, the second notification address can also be referred to as the first notification address. Or both the second notification address and the first notification address are referred to as the notification address.

[0300] As another implementation method, the second notification address is different from the first notification address. For example, the first notification address is at least two of an IP address, an FQDN, or a URI, and the second notification address is one or two of the first notification addresses. For another example, the first notification address is a URI, and the second notification address is an IP address determined according to the URI (for example, the SMF determines the IP address according to the server address attribute item in the URI, or the SMF determines the IP address according to the local configuration and the URI, or the SMF determines the IP address by performing a DNS query on the URI). For another example, the first notification address is an FQDN, and the second notification address is an IP address determined according to the FQDN (such as the SMF determines the IP address according to the local configuration and the FQDN, or the SMF determines the IP address by performing a DNS query on the FQDN).

[0301] The N4 session modification request is Figure 4 A specific example of the first message in the embodiment.

[0302] Before executing step 517, the SMF may also determine whether the UPF needs to send a first event report to the second notification address of the AF. One method is as follows: If the PCC rule does not include the location information of the AF and does not include the above-mentioned first indication information, the SMF may determine that the AF is a local AF according to the protocol predefined or preconfigured, and then the SMF determines that the UPF needs to send a first event report to the AF. Another method is as follows: If the PCC rule includes the location information of the AF or the above-mentioned first indication information, the SMF determines that the UPF needs to send a first event report to the AF according to the location information of the AF or the above-mentioned first indication information.

[0303] Optionally, for Figure 3E the architecture, the second notification address is the address of the AF, and the SMF also carries the address of the local NEF in the above N4 session modification request, so that the UPF can report the first event report to the second notification address of the AF through the local NEF.

[0304] Furthermore, the SMF may also determine whether it is necessary to report a third event report corresponding to the event notification request information to the PCF.

[0305] The implementation method of the content carried in the session modification request in step 517 may refer to Figure 4 the various implementation methods of the first message in step 406 of the embodiment, which will not be elaborated here.

[0306] Step 518, the UPF sends an N4 session modification response to the SMF. Correspondingly, the SMF may receive this N4 session modification response.

[0307] Step 519, the UPF performs event detection according to the event notification request information.

[0308] After performing event detection, an event report may be generated.

[0309] Step 520, the UPF sends a first event report to the AF. Correspondingly, the AF may receive this first event report.

[0310] Specifically, the UPF sends a first event report to the second notification address of the AF. Optionally, a notification association identifier may also be sent to the second notification address of the AF.

[0311] Optionally, for Figure 3E the architecture, the method for the UPF to send a first event report to the AF may be: the UPF sends a first event report to the local NEF, and then the local NEF sends a first event report to the second notification address of the AF.

[0312] Step 521, the UPF sends a second event report to the SMF. Correspondingly, the SMF can receive this second event report.

[0313] Specifically, the UPF sends the second event report to the notification address of the SMF. Optionally, the notification association identifier of the SMF can also be sent to the notification address of the SMF. The notification address and the notification association identifier of the SMF here are sent by the SMF to the UPF in the above step 501 or step 510.

[0314] Step 522, the SMF sends a third event report to the PCF. Correspondingly, the PCF can receive this third event report.

[0315] The above steps 521 to 522 are optional steps. Steps 521 and 522 are only executed when it is necessary to report an event report to the PCF.

[0316] Based on the above solution, since the UPF can directly report an event report to the AF or report an event report to the AF through the local NEF, the path length of reporting the event report is greatly shortened. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing of the application layer.

[0317] As Figure 6 shown, the present application provides a schematic diagram of a method flow for sending an event report. This embodiment is based on Figure 3C the architecture. The AF requests event detection through the local NEF. The UPF directly sends the detected event report to the local NEF. In addition, the UPF can also report the detected event to the SMF at the same time.

[0318] It should be noted that the following steps 602 to 605 and the following steps 606 to 610 are alternative. Specifically, Figure 6 in the embodiment shown, in the first implementation manner, execute: steps 601 to 605, and steps 611 to 623. This implementation manner is for an established and ongoing PDU session; in the second implementation manner, execute: step 601, steps 606 - 623. This implementation manner is for an established and ongoing PDU session or a future-established PDU session.

[0319] The method includes the following steps:

[0320] Step 601 is the same as Figure 5 step 501 of the embodiment and can be referred to the foregoing description.

[0321] Step 602, the AF sends an event notification request to the local NEF. Correspondingly, the local NEF can receive this event notification request.

[0322] This local NEF is the Figure 3C local NEF in

[0323] The specific content and implementation method in this event notification request are the same as those in the event notification request in step 502 of the Figure 5 same embodiment, and reference can be made to the foregoing description.

[0324] Step 603: After the local NEF obtains the address of the PCF through interaction with the BSF network element (not shown in the figure), it sends an event notification request to the PCF. Correspondingly, the PCF can receive the event notification request from the local NEF.

[0325] This event notification request includes the event notification request information obtained from the event notification request in the above step 602, and also includes the first notification address of the local NEF. It can also be understood that in this step 603, the local NEF replaces the first notification address of the AF in the event notification request in step 602 with the first notification address of the local NEF. Further, the local NEF can also save the correspondence between the first notification address of the AF and the first notification address of the local NEF.

[0326] This event notification request can be, for example, Npcf_PolicyAuthorization_Create request.

[0327] Optionally, if the event notification request in the above step 602 does not carry the location information of the AF and does not carry the seventh indication information, the local NEF can determine the location information of the AF according to the first notification address in the event notification request in step 602, so as to carry the location information or indication information of the AF in the event notification request in this step 603 (i.e., Figure 4 the eighth indication information in the embodiment), and this indication information is used to indicate that this event notification request is a local event notification request or to indicate that the AF is a local AF. Alternatively, the local NEF carries the location information of the local NEF in the event notification request in this step 603.

[0328] Step 604: The PCF sends an event notification request response to the local NEF. Correspondingly, the local NEF can receive this event notification request response.

[0329] This event notification request response can be, for example, Npcf_Policy Authorization_CreateResponse.

[0330] Step 605: The local NEF sends an event notification request response to the AF. Correspondingly, the AF can receive this event notification request response.

[0331] The event notification request response can be, for example, Npcf_Policy Authorization_Create RequestResponse or Nnef_AFsessionWithQoS_Create Response.

[0332] As another implementation method, the above steps 602 - 605 can also be replaced by the following steps 606 - 609.

[0333] Step 606, the AF sends an event notification request to the local NEF. Correspondingly, the local NEF can receive this event notification request.

[0334] This local NEF is Figure 3C the local NEF in

[0335] The specific content and implementation method in this event notification request are the same as the event notification request in Figure 5 step 506 of the embodiment, and reference can be made to the foregoing description.

[0336] Step 607, the local NEF sends an event notification request to all PCFs. Correspondingly, the PCF can receive the event notification request from the local NEF.

[0337] The event notification request in step 607 carries the event notification request information obtained from step 606 and the first notification address of the local NEF. However, it should be noted that if the external group identifier is carried in the event notification request of 606, the local NEF needs to map this external group identifier to an internal group identifier, and the event notification request in this step 607 carries this internal group identifier instead of the external group identifier. If the above indication information for indicating all UEs is carried in the event notification request of 606, the event notification request in this step 607 can also carry this indication information for indicating all UEs.

[0338] This event notification request can be, for example, Npcf_EventExposure_Subscribe Request or Nnef_EventExposure_Subscribe.

[0339] Optionally, if the event notification request in the above step 606 does not carry the location information of the AF and does not carry the seventh indication information, the NEF can determine the location information of the AF according to the first notification address in the event notification request of step 606, so as to carry the location information or indication information of the AF in the event notification request of this step 607 (i.e., Figure 4(8th indication information of the embodiment), the indication information is used to indicate that the event notification request is a local event notification request or to indicate that the AF is a local AF. Alternatively, the local NEF carries the location information of the NEF in the event notification request in step 607.

[0340] Steps 608 to 610 are the same as Figure 5 Steps 508 to 510 of the embodiment, which can be referred to the foregoing description.

[0341] Step 611, the PCF performs policy decision-making.

[0342] If the above steps 602 - 605 are executed, the PCF can perform session binding in step 611, and then formulate PCC rules for the PDU session established in step 601.

[0343] If the above steps 606 - 609 are executed, when the event notification request in step 607 carries an internal group identifier, the PCF formulates PCC rules for all PDU sessions belonging to this internal group identifier; when the event notification request in step 507 carries indication information for indicating all UEs, the PCF formulates PCC rules for the PDU sessions of all UEs.

[0344] Among them, the PCC rules include event notification request information and a first notification address, and the first notification address is the notification address of the local NEF. Optionally, a notification association identifier can also be included, and the notification association identifier is the notification association identifier of the local NEF. If the event identifier is QoS Monitoring (also known as QoS detection event identifier, or QoS Monitoring event identifier), the PCC rules also include the QoS parameters to be measured as described above (the QoS parameters to be measured are the event monitoring control information).

[0345] The event notification request information includes an event identifier and / or event monitoring control information.

[0346] Optionally, when the event is QoS Monitoring, and the event notification request information carried in the PCC rules only includes QoS Monitoring control information and does not include the QoS Monitoring event identifier, the PCF can decide to provide a policy control request trigger (PCRT) for QoS Monitoring to the SMF. If the PCF has previously provided a policy control request trigger for QoS Monitoring to the SMF, then the PCF may not provide a policy control request trigger for QoS Monitoring in this step.

[0347] Optionally, if the location information of the AF, or the location information of the local NEF, or the eighth indication information is also carried in step 603 or step 607, the PCC rule may also carry the location information of the AF, or the location information of the local NEF, or an indication information (i.e., Figure 4 the first indication information in the embodiment).

[0348] Optionally, the PCF determines to carry the location information of the AF, or the location information of the local NEF, or an indication information (i.e., Figure 4 the first indication information in the embodiment) in the PCC rule according to the first notification address.

[0349] Optionally, the PCF determines to carry the location information of the AF or the first indication information in the PCC rule according to the ability of the UPF to support local event notification obtained in step 601 or step 610.

[0350] Optionally, if the PCF decides that the event report needs to be reported locally to the AF and also to the SMF, the PCC rule may also carry an indication of duplicate reporting, and this indication of duplicate reporting causes the UPF to send a first event report to the local NEF, and indicates that the SMF sends a third event report to the PCF. Alternatively, the PCC rule does not carry this indication of duplicate reporting, but carries a Figure 4 fifth indication information in the embodiment, and the purpose of indicating duplicate reporting can also be achieved. For specific reference, see Figure 4 the description of the embodiment.

[0351] Optionally, the PCF determines whether to carry an indication of duplicate reporting or the fifth indication information in the PCC rule according to the ability of the UPF to support local event notification obtained in step 601 or step 610.

[0352] Optionally, it can also be predefined or preconfigured by the protocol whether the UPF needs to report the event locally to the AF and also send the event report to the SMF.

[0353] Steps 612 to 616 are the same as Figure 5 steps 512 to 516 in the embodiment, and reference can be made to the foregoing description.

[0354] In step 617, the SMF sends an N4 session modification request to the UPF, and the N4 session modification request includes the second notification address of the local NEF and event notification request information. Accordingly, the UPF can receive the N4 session modification request.

[0355] This N4 session modification request is Figure 4 a specific example of the first message in the embodiment.

[0356] As an implementation, the second notification address is the same as the first notification address.

[0357] As another implementation method, the second notification address is different from the first notification address. For example, the first notification address is at least two of an IP address, an FQDN, or a URI, and the second notification address is one or two of the first notification addresses. For another example, the first notification address is a URI, and the second notification address is an IP address determined according to the URI (for example, the SMF determines the IP address according to the server address attribute item in the URI, or the SMF determines the IP address according to the local configuration and the URI, or the SMF performs a DNS query according to the URI to determine the IP address). For another example, the first notification address is an FQDN, and the second notification address is an IP address determined according to the FQDN (for example, the SMF determines the IP address according to the local configuration and the FQDN, or the SMF performs a DNS query according to the FQDN to determine the IP address). Before performing step 617, the SMF can also determine whether the UPF needs to send a first event report to the second notification address of the local NEF. One method is: if the PCC rule does not include the location information of the local NEF, does not include the location information of the AF, and does not include the above first indication information, the SMF can determine that the NEF is the local NEF according to the protocol predefined or preconfigured, and then the SMF determines that the UPF needs to send a first event report to the local NEF. Another method is: if the PCC rule includes the location information of the AF, or the location information of the local NEF, or the above first indication information, the SMF determines that the UPF needs to send a first event report to the local NEF according to the location information of the AF, or the location information of the local NEF, or the above first indication information.

[0358] Furthermore, the SMF can also determine whether it is necessary to report a third event report corresponding to the event notification request information to the PCF.

[0359] The implementation method of the content carried in the session modification request in this step 617 can refer to Figure 4 The various implementation methods of the first message in step 406 of the embodiment, which will not be elaborated here.

[0360] Steps 618 to step 619 are the same as Figure 5 Steps 518 to step 519 of the embodiment, which can be referred to the foregoing description.

[0361] In step 620, the UPF sends a first event report to the local NEF. Correspondingly, the local NEF can receive the first event report.

[0362] Specifically, the UPF sends a first event report to the second notification address of the local NEF. Optionally, it can also send a notification association identifier of the local NEF to the second notification address of the local NEF.

[0363] Step 621: The local NEF sends a first event report to the AF. Correspondingly, the AF can receive this first event report.

[0364] Specifically, the local NEF sends the first event report to the second notification address of the AF. Optionally, the notification association identifier of the AF can also be sent to the second notification address of the AF.

[0365] Steps 622 to 623 are the same as Figure 5 Steps 521 to 522 in the embodiment, and reference can be made to the foregoing description.

[0366] Based on the above solution, since the UPF can directly report the event report to the AF, the path length of reporting the event report is greatly shortened. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing of the application layer.

[0367] As Figure 7 shown, the present application provides a schematic flowchart of a method for sending an event report. This embodiment is based on Figure 3D the architecture. The AF requests event detection through the local NEF, and the local NEF further requests event detection from the NEF. The UPF directly sends the detected event report to the local NEF. In addition, the UPF can also report the detected event to the SMF at the same time.

[0368] It should be noted that the following steps 702 to 705 and the following steps 706 to 710 are alternatives. Specifically, Figure 7 in the embodiment shown, in the first implementation manner, the following are executed: steps 701 to 705, and steps 711 to 723. This implementation manner is for an established and ongoing PDU session; in the second implementation manner, the following are executed: step 701, steps 706 - 723. This implementation manner is for an established and ongoing PDU session or a future-established PDU session.

[0369] The method includes the following steps:

[0370] Step 701 is the same as Figure 5 Step 501 in the embodiment, and reference can be made to the foregoing description.

[0371] Step 702: The AF sends an event notification request to the local NEF. Correspondingly, the local NEF can receive this event notification request.

[0372] This local NEF is the Figure 3D local NEF in

[0373] The specific content and implementation manner in this event notification request are the same as those in Figure 5The event notification request in step 502 of the embodiment is the same, and reference may be made to the foregoing description.

[0374] Step 702a, the local NEF sends an event notification request to the central NEF (i.e., the NEF in Figure 3D ). Accordingly, the central NEF can receive the event notification request from the local NEF.

[0375] This event notification request includes the event notification request information obtained from the event notification request in step 702 above, and also includes the first notification address of the local NEF. It can also be understood that in this step 702a, the local NEF replaces the first notification address of the AF in the event notification request in step 702 with the first notification address of the local NEF. Further, the local NEF can also save the correspondence between the first notification address of the AF and the first notification address of the local NEF.

[0376] Optionally, if the event notification request in step 702 above does not carry the location information of the AF and does not carry the seventh indication information, the local NEF can determine the location information of the AF according to the first notification address in the event notification request in step 702, so as to carry the location information or indication information of the AF in the event notification request in this step 702a (i.e., Figure 4 the eighth indication information in the embodiment), and this indication information is used to indicate that this event notification request is a local event notification request or to indicate that the local AF receives the event report. Or, the local NEF carries the location information of the local NEF in the event notification request in this step 702a.

[0377] The event notification request in this step 702a can be, for example, Npcf_Policy Authorization_CreateRequest or Nnef_AFsessionWithQoS_Create Request.

[0378] Step 703, after obtaining the address of the PCF through interaction with the BSF network element (not shown in the figure), the central NEF sends an event notification request to the PCF. Accordingly, the PCF can receive the event notification request from the central NEF.

[0379] Optionally, if the event notification request in step 702a above does not carry the location information of the AF, does not carry the location information of the local NEF, and does not carry the seventh indication information, the central NEF can determine the location information of the AF according to the first notification address in the event notification request in step 702a, so as to carry the location information or indication information of the AF in the event notification request in this step 703 (i.e., Figure 4(the eighth indication information of the embodiment), the indication information is used to indicate that the event notification request is a local event notification request or to indicate that the AF is a local AF. Alternatively, the central NEF carries the location information of the local NEF or the above-mentioned eighth indication information in the event notification request in step 703 according to the determined location information of the local NEF.

[0380] The event notification request can be, for example, an Npcf_PolicyAuthorization_Create request.

[0381] Step 704, the PCF sends an event notification request response to the central NEF. Correspondingly, the central NEF can receive the event notification request response.

[0382] The event notification request response can be, for example, an Npcf_Policy Authorization_CreateResponse.

[0383] Step 704a, the central NEF sends an event notification request response to the local NEF. Correspondingly, the local NEF can receive the event notification request response.

[0384] The event notification request in step 704a can be, for example, an Npcf_Policy Authorization_CreateResponse or an Nnef_AFsessionWithQoS_Create Response.

[0385] Step 705, the local NEF sends an event notification request response to the AF. Correspondingly, the AF can receive the event notification request response.

[0386] The event notification request response can be, for example, an Npcf_Policy Authorization_Create RequestResponse or an Nnef_AFsessionWithQoS_Create Response.

[0387] As another implementation method, the above steps 702 - step 705 can also be replaced by the following steps 706 - step 709.

[0388] Step 706, the AF sends an event notification request to the local NEF. Correspondingly, the local NEF can receive the event notification request.

[0389] The local NEF is the Figure 3D local NEF in

[0390] The specific content and implementation method in the event notification request are the same as those inFigure 5 The event notification request in step 506 of the embodiment is the same, and reference can be made to the foregoing description.

[0391] In step 706a, the local NEF sends an event notification request to the central NEF. Correspondingly, the central NEF can receive the event notification request.

[0392] The event notification request includes the event notification request information obtained from the event notification request in step 706 above, and also includes the first notification address of the local NEF. It can also be understood that in this step 706a, the local NEF replaces the notification address of the AF in the event notification request in step 706 with the notification address of the local NEF. Further, the local NEF can also save the correspondence between the first notification address of the AF and the first notification address of the local NEF.

[0393] Optionally, if the event notification request in step 706 above does not carry the location information of the AF and does not carry the seventh indication information, the local NEF can determine the location information of the AF according to the first notification address in the event notification request in step 706, so as to carry the location information or indication information of the AF in the event notification request in this step 706a (i.e., Figure 4 the eighth indication information in the embodiment), and this indication information is used to indicate that this event notification request is a local event notification request or to indicate that the AF is a local AF. Or, the local NEF carries the location information of the local NEF or the above eighth indication information in the event notification request in this step 706a.

[0394] It should be noted that if the external group identifier is carried in the event notification request in 706, the local NEF needs to map this external group identifier to an internal group identifier, and the internal group identifier is carried in the event notification request in this step 706a, rather than the external group identifier. If the indication information for indicating all UEs is carried in the event notification request in 706, the event notification request in this step 706a can also carry this indication information for indicating all UEs.

[0395] The event notification request in this step 706a can be, for example, Nnef_EventExposure_SubscribeRequest.

[0396] In step 707, the central NEF sends an event notification request to all PCFs. Correspondingly, the PCF can receive the event notification request from the central NEF.

[0397] The content in this event notification request is the same as the content in the event notification request in step 706a.

[0398] The event notification request can be, for example, an Npcf_EventExposure_Subscribe Request.

[0399] Optionally, if the location information of the AF, the location information of the local NEF, and the seventh indication information are not carried in the event notification request in step 706a, the central NEF can determine the location information of the AF based on the first notification address in the event notification request in step 706a, so as to carry the location information or indication information of the AF in the event notification request in this step 707 (i.e., Figure 4 the eighth indication information of the embodiment), and this indication information is used to indicate that the event notification request is a local event notification request or to indicate that the local AF receives the event report. Alternatively, the central NEF carries the location information of the local NEF in the event notification request in this step 707 according to the determined location information of the local NEF.

[0400] Step 708, the PCF sends an event notification request response to the central NEF. Correspondingly, the central NEF can receive this event notification request response.

[0401] The event notification request response can be, for example, an Npcf_EventExposure_Subscribe Response.

[0402] Step 708a, the central NEF sends an event notification request response to the local NEF. Correspondingly, the local NEF can receive the event notification request response.

[0403] The event notification request response can be, for example, an Nnef_EventExposure_Subscribe Response.

[0404] Step 709, the local NEF sends an event notification request response to the AF. Correspondingly, the AF can receive this event notification request response.

[0405] The event notification request response can be, for example, an Nnef_EventExposure_Subscribe Response.

[0406] Steps 710 - Step 723 are the same as Figure 6 Steps 610 to 623 of the embodiment, and reference can be made to the foregoing description.

[0407] Based on the above solution, since the UPF can report the event report to the local NEF, and then the local NEF reports the event report to the AF, the path length of reporting the event report is greatly shortened. Therefore, for services with high time sensitivity, the timeliness of the event report can be improved, which is beneficial to the processing of the application layer.

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

[0409] As Figure 8 shown, it is a possible exemplary block diagram of a communication device involved in the present application. The device 800 can exist in the form of software or hardware. The device 800 may include: a sending unit 801, a receiving unit 802, and a processing unit 803. As an implementation manner, the receiving unit 802 and the sending unit 801 can be implemented through a communication unit. The processing unit 803 is used to control and manage the actions of the device 800. The sending unit 801 and the receiving unit 802 are used to support the communication between the device 800 and other network entities.

[0410] Among them, the processing unit 803 can be a processor or a controller. For example, it can be a general central processing unit (CPU), a general processor, a digital signal processing (DSP), an application specific integrated circuits (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in combination with the disclosed content of the present application. The processor can also be a combination for implementing computing functions, such as including a combination of one or more microprocessors, a combination of DSP and microprocessors, and so on. The receiving unit 802 is the interface circuit of the device, used to receive signals from other devices. The sending unit 801 is the interface circuit of the device, used to send signals to other devices. For example, when the device is implemented in the form of a chip, the receiving unit 802 is the interface circuit of the chip for receiving signals from other chips or devices, and the sending unit 801 is the interface circuit of the chip for sending signals to other chips or devices.

[0411] The device 800 may be a session management network element, a user plane network element, an application function network element, or a policy control network element in the above embodiments, or may be a chip for a session management network element, a user plane network element, an application function network element, or a policy control network element. For example, when the device 800 is a session management network element, a user plane network element, an application function network element, or a policy control network element, the processing unit 803 may be a processor, for example, and the sending unit 801 may be a transmitter, for example, and the receiving unit 802 may be a receiver. Optionally, the transmitter and the receiver may include a radio frequency circuit, and the storage unit may be a memory, for example. For example, when the device 800 is a chip for a session management network element, a user plane network element, an application function network element, or a policy control network element, the processing unit 803 may be a processor, for example, and the sending unit 801 may be an output interface, a pin, or a circuit, etc., and the receiving unit 802 may be an input interface, a pin, or a circuit, etc. The processing unit 803 may execute computer-executable instructions stored in the storage unit. Optionally, the storage unit is a storage unit inside the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit outside the chip in the session management network element, the user plane network element, the application function network element, or the policy control network element, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.

[0412] In the first embodiment, the device is the session management network element in the above embodiments. The receiving unit 802 is configured to receive an event notification request from a policy control network element. The event notification request includes event notification request information and a first notification address. The first notification address is an address of an event reporting receiving network element for receiving an event report. The event reporting receiving network element is an application function network element or a network exposure function network element. The sending unit 801 is configured to send a first message to a user plane network element. The first message includes the event notification request information and a second notification address. The first message is used to instruct the user plane network element to send a first event report corresponding to the event notification request information to the notification address. The second notification address is determined according to the first notification address.

[0413] In a possible implementation, the processing unit 803 is configured to determine that the user plane network element sends the first event report to the second notification address.

[0414] In a possible implementation, the processing unit 803 is configured to determine, according to the second notification address, that the user plane network element sends the first event report to the second notification address; or, the event notification request further includes the location information of the event report receiving network element, and is configured to determine, according to the location information of the event report receiving network element, that the user plane network element sends the first event report to the second notification address; or, the event notification request further includes first indication information, where the first indication information is used to indicate that the event notification request is a local event notification request, and is configured to determine, according to the first indication information, that the user plane network element sends the first event report to the second notification address.

[0415] In a possible implementation, the first message includes second indication information, and the first message is used to indicate that the user plane network element sends the first event report corresponding to the event notification request information to the second notification address, including: the second indication information is used to indicate that the user plane network element sends the first event report corresponding to the event notification request information to the second notification address.

[0416] In a possible implementation, the first message further includes third indication information, and the third indication information is used to indicate that the user plane network element sends the second event report corresponding to the event notification request information to the session management network element.

[0417] In a possible implementation, the processing unit 803 is configured to determine to send a third event report to the policy control network element; the sending unit 801 is further configured to send fourth indication information to the user plane network element, where the fourth indication information is used to indicate that the user plane network element sends the first event report corresponding to the event notification request information to the second notification address, and to indicate that the user plane network element sends the second event report corresponding to the event notification request information to the session management network element.

[0418] In a possible implementation, the processing unit 803 is configured to determine to send the third event report to the policy control network element, specifically including: the event notification request further includes fifth indication information, where the fifth indication information is used to indicate that the session management network element sends the third event report to the policy control network element; and is configured to determine to send the third event report to the policy control network element according to the fifth indication information; or, is configured to determine to send the third event report to the policy control network element according to configuration information.

[0419] In a possible implementation manner, the event notification request further includes a notification association identifier, which is used for the event reporting receiving network element to associate the first event report with the event notification request; the sending unit 801 is further configured to send the notification association identifier to the user plane network element.

[0420] In a possible implementation method, the event notification request information includes the event identifier and the event monitoring control information. The event identifier is a QoS detection event identifier, and the event monitoring control information is QoS detection control information. The QoS detection control information includes parameters for requesting QoS detection and a reporting frequency.

[0421] In a possible implementation manner, the event identifier is a quality of service (QoS) detection (QoS detection can also be referred to as a QoS detection event identifier), and the event notification request further includes QoS parameters to be detected. Among them, the QoS parameters to be detected can be understood as event monitoring control information.

[0422] In a possible implementation manner, the sending unit 801 is further configured to send sixth indication information to the access network device, and the sixth indication information is used to indicate the execution of QoS detection.

[0423] In a possible implementation manner, the event notification request information includes the event identifier and the event monitoring control information. The event identifier is a usage monitoring event identifier, and the event monitoring control information is usage monitoring control information. Optionally, the usage monitoring control information includes a usage threshold.

[0424] In a possible implementation manner, the event identifier is usage monitoring (usage monitoring can also be referred to as a usage monitoring event identifier), and the event notification request further includes a usage threshold. Among them, the usage threshold can be understood as event monitoring control information.

[0425] In the second embodiment, the device is the user plane network element in the above embodiment. The receiving unit 802 is configured to receive a first message from the session management network element. The first message includes event notification request information and a second notification address. The second notification address is the address of the event reporting receiving network element for receiving the first event report. The event reporting receiving network element is an application function network element or a network exposure function network element. The first message is used to instruct the device to send the first event report corresponding to the event notification request information to the second notification address; the sending unit 801 is configured to send the first event report to the second notification address.

[0426] In a possible implementation, the first message includes second indication information, and the first message is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address, including: the second indication information is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address.

[0427] In a possible implementation, the sending unit 801 is further configured to send a second event report corresponding to the event notification request information to the session management network element.

[0428] In a possible implementation, the first message further includes third indication information, and the third indication information is used to instruct to send the second event report corresponding to the event notification request information to the session management network element.

[0429] In a possible implementation, the first message further includes fourth indication information, and the fourth indication information is used to instruct the user plane network element to send the first event report corresponding to the event notification request information to the second notification address, and to instruct the user plane network element to send the second event report corresponding to the event notification request information to the session management network element.

[0430] In a possible implementation, the first message further includes a notification association identifier, and the notification association identifier is used for the event report receiving network element to associate the first event report with the event notification request; the first event report includes the notification association identifier.

[0431] In a possible implementation, the processing unit 803 is configured to generate the first event report when detecting an event corresponding to the event notification request information.

[0432] In the third embodiment, the device is the application function network element in the above embodiment. The sending unit 801 is configured to send an event notification request to the network exposure function network element. The event notification request includes event notification request information and a first notification address. The first notification address is the address of the device for receiving the first event report. The event notification request information includes an event identifier and / or event monitoring control information. The event notification request is used to request the user plane network element to send the first event report corresponding to the event notification request information to the first notification address. The receiving unit 802 is configured to receive the first event report from the user plane network element or the network exposure function network element.

[0433] In a possible implementation, the event notification request further includes seventh indication information, where the seventh indication information is used to indicate that the event notification request is a local event notification request; or, the event notification request further includes the location information of the device.

[0434] In a possible implementation, the event notification request further includes a notification association identifier, where the notification association identifier is used by the device to associate the first event report with the event notification request.

[0435] In a possible implementation, the receiving unit 802 is further configured to receive the notification association identifier from the user plane network element or the network exposure function network element.

[0436] In the fourth embodiment, the device is the policy control network element in the foregoing embodiment. The receiving unit 802 is configured to receive a first event notification request from a network exposure function network element. The first event notification request includes event notification request information and a first notification address. The event notification request information includes an event identifier and / or event monitoring control information. The first notification address is the address of the event report receiving network element for receiving the first event report. The event report receiving network element is an application function network element or the network exposure function network element. The sending unit 801 is configured to send a second event notification request to the session management network element. The second event notification request includes the event notification request information and the first notification address. The second event notification request is used to request the user plane network element to send the first event report corresponding to the event notification request information to the first notification address.

[0437] In a possible implementation, the second event notification request further includes first indication information, where the first indication information is used to indicate that the second event notification request is a local event notification request.

[0438] In a possible implementation, the first event notification request further includes eighth indication information, where the eighth indication information is used to indicate that the first event notification request is a local event notification request; or, the first event notification request further includes the location information of the event report receiving network element. Herein, the eighth indication information may also be referred to as the indication information for indicating that the event notification request is a local event notification request.

[0439] In a possible implementation, when the processing unit 803 determines that it is necessary to obtain a third event report corresponding to the event notification request information, the sending unit 801 is configured to send indication information to the session management network element, where the indication information is used to instruct the session management network element to send the third event report to the policy control network element. This indication information may also be referred to as fifth indication information.

[0440] In a possible implementation, the second event notification request further includes fifth indication information, where the fifth indication information is used to instruct the session management network element to send a third event report corresponding to the event notification request information to the device.

[0441] It can be understood that for the specific implementation process and corresponding beneficial effects of the device when used in the above event reporting method, reference can be made to the relevant descriptions in the foregoing method embodiments, and details are not elaborated herein.

[0442] If the device 800 is a session management network element, a user plane network element, an application function network element, or a policy control network element, then the session management network element, the user plane network element, the application function network element, or the policy control network element is presented in the form of dividing each functional module in an integrated manner. Here, a "module" may refer to a specific ASIC, a circuit, a processor and a memory that execute one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can conceive that the session management network element, the user plane network element, the application function network element, or the policy control network element can adopt Figure 9 the form shown.

[0443] For example, Figure 9 the processor 902 in

[0444] Specifically, Figure 8 the functions / implementation processes of the sending unit 801, the receiving unit 802, and the processing unit 803 in Figure 9 can be implemented by the processor 902 in Figure 8 calling computer-executable instructions stored in the memory 901. Alternatively, Figure 9 the function / implementation process of the processing unit 803 in Figure 8 can be implemented by the processor 902 in Figure 9 calling computer-executable instructions stored in the memory 901, and

[0445] the functions / implementation processes of the sending unit 801 and the receiving unit 802 in

[0446] can be implemented by the communication interface 903 in Figure 9As shown in the figure, it is another schematic diagram of a communication device provided by this application. This device can be a session management network element, a user plane network element, an application function network element, or a policy control network element in the above embodiments. The device 900 includes: a processor 902 and a communication interface 903. Optionally, the device 900 may further include a memory 901. Optionally, the device 900 may further include a communication line 904. Among them, the communication interface 903, the processor 902, and the memory 901 can be interconnected through the communication line 904; the communication line 904 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication line 904 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 9 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0447] The processor 902 can be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of this application solution.

[0448] The communication interface 903 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, a radio access network (RAN), a wireless local area network (WLAN), a wired access network, etc.

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

[0450] Among them, the memory 901 is used to store computer execution instructions for implementing the solution of this application, and is controlled by the processor 902 for execution. The processor 902 is used to execute the computer execution instructions stored in the memory 901, so as to implement the method for sending an event report provided in the above embodiments of this application.

[0451] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not make specific limitations thereon.

[0452] Those of ordinary skill in the art can understand that the various digital numbers such as the first and the second involved in this application are only for the convenience of description and are not used to limit the scope of the embodiments of this application, nor do they represent the order. "And / or" describes the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after. "At least one" means one or more. At least two means two or more. "At least one", "any one" or their similar expressions refer to any combination of these items, including any combination of single item (s) or plural item (s). For example, at least one (item, kind) of a, b, or c may represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, c may be single or multiple. "Multiple" means two or more, and other quantifiers are similar. In addition, for elements where the singular forms "a", "an", and "the" appear, unless the context clearly stipulates otherwise, they do not mean "one or only one", but mean "one or more than one". For example, "a device" means one or more such devices.

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

[0454] In the embodiments of the present application, the various illustrative logical units and circuits described can be implemented or operate the described functions through a design of a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above. The general-purpose processor can be a microprocessor. Optionally, the general-purpose processor can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0455] The steps of the methods or algorithms described in the embodiments of the present application can be directly embedded in hardware, software units executed by a processor, or a combination of the two. The software units can be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and the storage medium can be provided in an ASIC.

[0456] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus, causing a series of operational steps to be performed on the computer or other programmable apparatus to generate a computer-implemented process, so that the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions specified in one process or a plurality of processes and / or blocks Figure 1 one process or a plurality of processes and / or blocks Figure 1 or steps for implementing the functions specified in one block or a plurality of blocks.

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

Claims

1. A method for sending an event report, characterized in that, including: A session management network element receives a second event notification request from a policy control network element. The second event notification request includes event monitoring control information, a first notification address, and first indication information. The first notification address is the address of an event reporting receiving network element for receiving event reports. The event reporting receiving network element is an application function network element or a network exposure function network element. The first indication information is used to indicate that the second event notification request is a local event notification request; The session management network element determines, according to the first indication information, that a user plane network element sends a first event report corresponding to the event monitoring control information to a second notification address, and the second notification address is determined according to the first notification address; The session management network element sends a first message to the user plane network element. The first message includes the event monitoring control information and the second notification address. The first message is used to instruct the user plane network element to send the first event report to the second notification address.

2. The method according to claim 1, wherein, The first message includes second indication information. The first message is used to instruct the user plane network element to send a first event report corresponding to the event monitoring control information to the second notification address, including: The second indication information is used to instruct the user plane network element to send the first event report corresponding to the event monitoring control information to the second notification address.

3. The method according to claim 2, wherein The first message further includes third indication information. The third indication information is used to instruct the user plane network element to send a second event report corresponding to the event monitoring control information to the session management network element.

4. The method according to claim 1, characterized in that, also including: When the session management network element determines to send a third event report to the policy control network element, it sends fourth indication information to the user plane network element. The fourth indication information is used to instruct the user plane network element to send the first event report corresponding to the event monitoring control information to the second notification address, and to instruct the user plane network element to send a second event report corresponding to the event monitoring control information to the session management network element.

5. The method according to claim 4, wherein The session management network element determines to send the third event report to the policy control network element, including: The event notification request further includes fifth indication information. The fifth indication information is used to instruct the session management network element to send the third event report to the policy control network element. The session management network element determines to send the third event report to the policy control network element according to the fifth indication information; or, The session management network element determines to send the third event report to the policy control network element according to configuration information.

6. The method according to any one of claims 1-5, characterized in that, also including: The event notification request further includes a notification association identifier. The notification association identifier is used for the event reporting receiving network element to associate the first event report with the second event notification request; The session management network element sends the notification association identifier to the user plane network element.

7. The method according to any one of claims 1-5, characterized in that, The event monitoring control information is QoS detection control information. The QoS detection control information includes parameters for requesting QoS detection and a reporting frequency.

8. The method according to claim 6, wherein The event monitoring control information is QoS detection control information, and the QoS detection control information includes parameters for requesting QoS detection and a reporting frequency.

9. The method according to claim 7, wherein It further includes: The session management network element sends sixth indication information to the access network device, and the sixth indication information is used to indicate the execution of QoS detection.

10. The method according to claim 8, wherein It further includes: The session management network element sends sixth indication information to the access network device, and the sixth indication information is used to indicate the execution of QoS detection.

11. A method for sending an event report, characterized in that, It includes: The user plane network element receives a first message from the session management network element. The first message includes event monitoring control information, a second notification address, and fourth indication information. The second notification address is the address of the event reporting receiving network element for receiving event reports. The event reporting receiving network element is an application function network element or a network exposure function network element. The fourth indication information is used to instruct the user plane network element to send a first event report corresponding to the event monitoring control information to the second notification address, and to instruct the user plane network element to send a second event report corresponding to the event monitoring control information to the session management network element; The user plane network element sends the first event report to the second notification address and sends the second event report to the session management network element.

12. The method according to claim 11, wherein The first message further includes a notification association identifier, and the notification association identifier is used for the event reporting receiving network element to associate the first event report with an event notification request; the first event report includes the notification association identifier.

13. A method for sending an event report, characterized in that, It includes: The policy control network element receives a first event notification request from the network exposure function network element. The first event notification request includes event monitoring control information and a first notification address. The first notification address is the address of the event reporting receiving network element for receiving event reports. The event reporting receiving network element is an application function network element or a network exposure function network element; The policy control network element sends a second event notification request to the session management network element. The second event notification request includes the event monitoring control information, the first notification address, and first indication information. The first indication information is used to indicate that the second event notification request is a local event notification request.

14. The method according to claim 13, wherein The first event notification request further includes eighth indication information, and the eighth indication information is used to indicate that the first event notification request is a local event notification request; or, the first event notification request further includes the location information of the event reporting receiving network element.

15. The method according to claim 13 or 14, characterized in that It further includes: If the policy control network element determines that it is necessary to obtain a third event report corresponding to the event monitoring control information, it determines to send fifth indication information to the session management network element, and the fifth indication information is used to instruct the session management network element to send the third event report to the policy control network element.

16. The method according to claim 15, wherein The second event notification request further includes the fifth indication information.

17. The method according to any one of claims 13, 14, and 16, characterized in that The first event notification request further includes a notification association identifier, and the notification association identifier is used for the event reporting receiving network element to associate the first event report with the first event notification request. The second event notification request further includes the notification association identifier.

18. The method according to claim 15, characterized in that The first event notification request further includes a notification association identifier, which is used for the event report receiving network element to associate the first event report with the first event notification request, and the second event notification request further includes the notification association identifier.

19. A method for sending an event report, characterized in that, Comprising: The network exposure function network element receives a first event notification request from the application function network element. The first event notification request includes event monitoring control information, a first notification address, and an eighth indication information. The first notification address is the address of the event report receiving network element for receiving event reports. The event report receiving network element is the application function network element or the network exposure function network element. The eighth indication information is used to indicate that the first event notification request is a local event notification request. The network exposure function network element sends the first event notification request to the policy control network element.

20. The method according to claim 19, wherein The first event notification request further includes a notification association identifier, which is used for the event report receiving network element to associate the first event report with the first event notification request.

21. A session management network element, characterized in that, Comprising: A processor and a memory; The memory is used to store computer-executable instructions. When the session management network element runs, the processor executes the computer-executable instructions stored in the memory to implement the method for sending an event report according to any one of claims 1-10.

22. A user plane network element, characterized in that, Comprising: A processor and a memory; The memory is used to store computer-executable instructions. When the user plane network element runs, the processor executes the computer-executable instructions stored in the memory to implement the method for sending an event report according to claim 11 or 12.

23. A policy control network element, characterized in that, Comprising: A processor and a memory; The memory is used to store computer-executable instructions. When the policy control network element runs, the processor executes the computer-executable instructions stored in the memory to implement the method for sending an event report according to any one of claims 13-18.

24. A network open function network element, characterized in that, Comprising: A processor and a memory; The memory is used to store computer-executable instructions. When the network exposure function network element runs, the processor executes the computer-executable instructions stored in the memory to implement the method for sending an event report according to claim 19 or 20.

25. A communication system, characterized in that, Comprising a session management network element and a user plane network element; The session management network element is used to receive a second event notification request from the policy control network element. The second event notification request includes event monitoring control information, a first notification address, and a first indication information. The first notification address is the address of the event report receiving network element for receiving event reports. The event report receiving network element is the application function network element or the network exposure function network element. The first indication information is used to indicate that the second event notification request is a local event notification request. According to the first indication information, it is determined that the user plane network element sends a first event report corresponding to the event monitoring control information to a second notification address, and the second notification address is determined according to the first notification address. Further, send a first message to the user plane network element, where the first message includes the event monitoring control information and the second notification address, and the first message is used to instruct the user plane network element to send the first event report to the second notification address; The user plane network element is configured to receive the first message from the session management network element; Further, it is configured to send the first event report to the second notification address.

26. A computer-readable storage medium, characterized in that, Instructions are stored in the computer-readable storage medium, and when the instructions run, the method according to any one of claims 1-10 is implemented, or the method according to claim 11 or 12 is implemented, or the method according to any one of claims 13-18 is implemented, or the method according to claim 19 or 20 is implemented.

27. A computer program product, characterized in that, It includes instructions, and when the instructions run, the method according to any one of claims 1-10 is implemented, or the method according to claim 11 or 12 is implemented, or the method according to any one of claims 13-18 is implemented, or the method according to claim 19 or 20 is implemented.

Images