WO2022022345A1 - Procédé, appareil et système de notification d'événement - Google Patents

Procédé, appareil et système de notification d'événement Download PDF

Info

Publication number
WO2022022345A1
WO2022022345A1 PCT/CN2021/107477 CN2021107477W WO2022022345A1 WO 2022022345 A1 WO2022022345 A1 WO 2022022345A1 CN 2021107477 W CN2021107477 W CN 2021107477W WO 2022022345 A1 WO2022022345 A1 WO 2022022345A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
event
address
event notification
notification
Prior art date
Application number
PCT/CN2021/107477
Other languages
English (en)
Chinese (zh)
Inventor
周晓云
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022022345A1 publication Critical patent/WO2022022345A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to an event notification method, apparatus, and system.
  • the terminal device can interact with the application server after accessing the network.
  • the application server may send event subscription information to the access network device (such as a user plane function (UPF)) that establishes a connection with the terminal device, so as to collect information on the communication between the terminal device and the corresponding application server.
  • the access network device such as a user plane function (UPF)
  • UPF user plane function
  • the terminal device is user equipment (UE), and the events subscribed by the application server can be quality of service (QoS) monitoring information.
  • the application server can send the QoS monitoring request information for the UE to the UPF through the application function (AF), policy control function (PCF), session management function (session management function, SMF).
  • the UPF can acquire the QoS monitoring event report in the process of communicating with the UE according to the QoS monitoring request information, and feed back the QoS monitoring event report to the AF.
  • the UPF may return the QoS monitoring event report through the path of receiving the QoS monitoring request information, that is, the UPF sends the QoS monitoring event report to the corresponding application server through the SMF, the PCF and the AF.
  • the UPF may also directly send the QoS monitoring event report to the AF through the dashed arrow as shown in FIG. 1 .
  • the corresponding UE is the UE that establishes a protocol data unit (protocol data unit, PDU) session with the UPF.
  • protocol data unit protocol data unit
  • the UE is often in a moving state, and as the UE moves, UPF reselection may occur.
  • the application server needs to obtain the event report corresponding to the event subscription in the communication process between the UPF and the UE, it needs to re-deliver the event subscription information to the reselected UPF through the AF, PCF and SMF.
  • the application server cannot quickly obtain the event report corresponding to the monitoring information.
  • the present application provides an event notification method, device and system, which can obtain a corresponding event report without the need for an application server to re-issue event subscription information when a UPF (PSA) reselection occurs due to a terminal device moving or other reasons.
  • PSA UPF
  • a first aspect provides an event notification method, the method comprising: sending first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier,
  • the network access identifier is used to indicate the location of the application server of the application
  • the event notification address is the destination address for receiving event notification information
  • the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function (AF).
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. Based on this solution, the application server can issue the correspondence including the data network access identifier and the corresponding event notification address through the AF.
  • the application server can also send event subscription information through AF.
  • other network elements such as SMF
  • SMF network management function
  • the event subscription information is sent, thereby the delay can be significantly reduced, and the signaling overhead of the system in the process of repeatedly sending the event subscription information can be reduced.
  • the application server may deliver the above correspondence and event subscription information through the same AF, or may deliver the above correspondence and event subscription information through different AFs.
  • the second information further includes: a notification association identifier, where the notification association identifier is used to associate the event notification information of the first event with the first information.
  • the AF can also send related information (such as the first notification related information) corresponding to the event subscription information, so that when the UPF reports the event report, the notification related information can be fed back to the application server at the same time. So that the application server can determine the association between the event report and the sent event subscription information according to the association information.
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • the second information may be information for making a QoS monitoring request, or information for a QoS notification control request, or information for a location request of a terminal device.
  • the QoS-related information is service-related information
  • the location request information is non-service-related information. Therefore, for other service information and non-service information, the solutions in the above-mentioned first aspect and its possible designs can be adopted. It realizes the reporting of events and obtains corresponding beneficial effects, so it should also be included in the protection scope of this application.
  • an event notification device comprising: a determining unit and a sending unit.
  • the determining unit is configured to determine first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the network access identifier is used to indicate the application's
  • the location of the application server the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability open network element corresponding to the application or the address of the application function (AF).
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • the sending unit is used for sending the first information and the second information.
  • the determining unit may specifically determine the specific content of the first information and the second information according to the instruction of the application server.
  • the second information further includes: a notification association identifier, where the notification association identifier is used to associate the event notification information of the first event with the first information.
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • an application function (AF) entity including one or more processors and one or more memories.
  • One or more memories are coupled to the one or more processors, and the one or more memories store computer instructions.
  • the computer instructions when executed by one or more processors, cause the AF entity to perform the event notification method as in any of the first aspect and possible designs thereof.
  • a computer-readable storage medium includes computer instructions.
  • the event notification according to any one of the first aspect and its possible implementations is executed. method.
  • a chip system in a fifth aspect, includes a processing circuit and an interface.
  • the processing circuit is configured to call and run the computer program stored in the storage medium from the storage medium, so as to execute the event notification method according to any one of the first aspect and its possible implementation manners.
  • a sixth aspect provides an event notification method, the method comprising: receiving first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the network
  • the access identifier is used to indicate the location of the application server of the application
  • the event notification address is the destination address for receiving event notification information
  • the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • the core network element can receive the first information and the second information from the AF, and perform response processing on them, so that other network elements can perform response processing.
  • the core network element may be a PCF, and the PCF may generate a corresponding PCC rule according to the first information and the second information, and deliver the PCC rule to other network elements (eg, SMF).
  • the PCC rule may include at least one data network access identifier, an event notification address (eg, first information) corresponding to the at least one data network access identifier, and third information for subscribing to the first event.
  • the third information may be the same as the second information, or may be determined by the PCF according to the second information (eg, the PCF performs a process such as transcoding the content of the second information to obtain the third information). It should be noted that, for some events corresponding to the time subscription information, the events correspond to the terminal equipment, therefore, the identification information of the target terminal equipment may also be included in the PCC rule.
  • the identification information can be used to indicate a terminal device, and can also be used to indicate a terminal device group.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the third information further includes a notification association identifier.
  • the AF can also send related information (such as the first notification related information) corresponding to the event subscription information, so that when the UPF reports the event report, the notification related information can be fed back to the application server at the same time. So that the application server can determine the association between the event report and the sent event subscription information according to the association information.
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • the second information may be information for making a QoS monitoring request, or information for a QoS notification control request, or information for a location request of a terminal device.
  • the QoS-related information is service-related information
  • the location request information is non-service-related information. Therefore, for other service information and non-service information, the solutions in the above-mentioned first aspect and its possible designs can be adopted. It realizes the reporting of events and obtains corresponding beneficial effects, so it should also be included in the protection scope of this application.
  • an event notification device comprising: a receiving unit and a sending unit.
  • the receiving unit is configured to receive first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the network access identifier is used to indicate the application
  • the location of the application server, the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the second information is used to subscribe to the first event of the terminal device, which is the device accessing the application server of the application.
  • the sending unit is configured to send third information and first information, wherein the third information is determined according to the second information and is used for subscribing to the first event.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the third information further includes a notification association identifier
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • a Policy Control Function (PCF) entity includes one or more processors and one or more memories.
  • One or more memories are coupled to the one or more processors, and the one or more memories store computer instructions.
  • the computer instructions when executed by one or more processors, cause a PCF entity to perform the event notification method as in any of the sixth aspect and possible designs thereof.
  • a computer-readable storage medium includes computer instructions, when the computer instructions are executed, execute the event notification as described in any one of the sixth aspect and its possible implementation manners method.
  • a chip system in a tenth aspect, includes a processing circuit and an interface.
  • the processing circuit is configured to call and run the computer program stored in the storage medium from the storage medium, so as to execute the event notification method according to any one of the sixth aspect and its possible implementation manners.
  • An eleventh aspect provides an event notification method, the method comprising: receiving first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier , the network access identifier is used to indicate the location of the application server of the application, the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • a first user plane network element is selected for the terminal device, the first user plane network element corresponds to the first data network access identifier, and at least one data network access identifier includes the first data network access identifier.
  • the third information is determined according to the second information and is used to subscribe to the first event.
  • the first event notification address is determined according to the first data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.
  • the network element can receive information from other network elements and process the response.
  • the network element may be an SMF.
  • the SMF may receive the PCC rule from the PCF, and the PCC rule may include the first information and the second information.
  • the SMF may select the corresponding UPF as the PSA for the terminal device according to the DNAI in the first information. Since the SMF knows the corresponding relationship between the DNAI and the event notification address, the SMF can also know the feedback address of the report corresponding to the event to which the second information is subscribed.
  • the SMF may deliver the third information corresponding to the event subscription information and the corresponding event notification address to the UPF, so that the UPF can obtain and feedback the event report accordingly.
  • the third information may be determined according to the second information. In different embodiments, the third information may be the same as the second information, or may be different from the second information.
  • the second event notification address is sent, where the second event notification address is the address of the local capability opening network element corresponding to the first user plane network element.
  • the SMF can also deliver the address of the NEF corresponding to the currently selected PSA to the UPF.
  • the NEF may correspond to the local AF.
  • the event report may need to be reported to other NEFs (such as the NEF in the central DC) first. Therefore, the SMF can send the address of the NEF to the UPF, so that the UPF can report the event report to the correct the address of.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the third information further includes a notification association identifier.
  • the AF can also send related information (such as the first notification related information) corresponding to the event subscription information, so that when the UPF reports the event report, the notification related information can be fed back to the application server at the same time. So that the application server can determine the association between the event report and the sent event subscription information according to the association information.
  • the method further includes: selecting a corresponding second user plane network element for the terminal device accessing the application server of the application, the second user plane network element corresponding to the second data network access identifier, at least one data network element
  • the access identifier includes the second data network access identifier.
  • the fourth information is determined according to the second information, and is used to subscribe to the first event.
  • the third event notification address is determined according to the second data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.
  • the SMF can select a new UPF as the PSA for the terminal equipment according to the DNAI in the PCC rule.
  • the DNAI corresponding to the updated PSA has an updated event notification address, so the SMF can send the updated event notification address to the UPF after reselection of the PSA, so that the UPF can report the event correctly according to the address.
  • the method further includes: sending a fourth event notification address, where the fourth event notification address is an address of a local capability opening network element corresponding to the second user plane network element.
  • a treatment scheme when PSA reselection occurs is provided.
  • the SMF may determine, according to the DNAI corresponding to the reselected PSA, the reporting address of the event report (eg, the fourth event notification address) after the PSA reselection is performed.
  • the SMF can deliver the updated reporting address to the corresponding updated UPF, so that the UPF can obtain the corresponding event report according to the event subscription information, and report the event report to the updated address.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the fourth information further includes a notification association identifier.
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • the second information may be information for making a QoS monitoring request, or information for a QoS notification control request, or information for a location request of a terminal device.
  • the QoS-related information is service-related information
  • the location request information is non-service-related information. Therefore, for other service information and non-service information, the solutions in the above-mentioned first aspect and its possible designs can be adopted. It realizes the reporting of events and obtains corresponding beneficial effects, so it should also be included in the protection scope of this application.
  • a twelfth aspect provides an event notification device, the device comprising: a receiving unit and a sending unit.
  • a receiving unit configured to receive first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the network access identifier is used to indicate the application of the application
  • the location of the server the event notification address is the destination address for receiving event notification information
  • the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the second information is used to subscribe to the first event of the terminal device, which is the device accessing the application server of the application.
  • a first user plane network element is selected for the terminal device, the first user plane network element corresponds to the first data network access identifier, and at least one data network access identifier includes the first data network access identifier.
  • a sending unit configured to send the third information and the first event notification address.
  • the third information is determined according to the second information and is used to subscribe to the first event.
  • the first event notification address is determined according to the first data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.
  • the sending unit is further configured to send a second event notification address, where the second event notification address is an address of a local capability opening network element corresponding to the first user plane network element.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the third information further includes a notification association identifier
  • the apparatus further includes a configuration unit for selecting a corresponding second user plane network element for the terminal device accessing the application server of the application, and the second user plane network element corresponds to the second data network access identifier , at least one data network access identifier includes a second data network access identifier.
  • the fourth information is determined according to the second information, and is used to subscribe to the first event.
  • the third event notification address is determined according to the second data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.
  • the sending unit is further configured to send a fourth event notification address, where the fourth event notification address is an address of a local capability opening network element corresponding to the second user plane network element.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the fourth information further includes a notification association identifier
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • a thirteenth aspect provides a session management function (SMF) entity, the SMF entity comprising one or more processors and one or more memories.
  • SMF session management function
  • One or more memories are coupled to the one or more processors, and the one or more memories store computer instructions.
  • the computer instructions when executed by one or more processors, cause the SMF entity to perform the event notification method of any one of the eleventh aspect and possible designs thereof.
  • a fourteenth aspect provides a computer-readable storage medium, the computer-readable storage medium includes computer instructions, when the computer instructions are executed, executes any one of the eleventh aspect and its possible implementation manners. Event notification method.
  • a fifteenth aspect provides a chip system, the chip includes a processing circuit and an interface.
  • the processing circuit is configured to call and run the computer program stored in the storage medium from the storage medium, so as to execute the event notification method according to any one of the eleventh aspect and its possible implementation manners.
  • a sixteenth aspect provides an event notification method, the method comprising: receiving first information, a first event notification address and a second event notification address, where the first information is used to subscribe to a first event of a terminal device, and the terminal device is an access application application server device.
  • the first event notification address is a destination address for receiving event notification information of the first event, and the destination address is an address of the application corresponding to the application function AF.
  • the second event notification address is the address of the local capability opening network element corresponding to the first user plane network element. Send second information to the first event notification address through the local capability opening network element corresponding to the second event notification address, where the second information includes event notification information of the first event.
  • the UPF can receive the first information from the SMF, obtain the event report according to the first information, and then report the event report to the address indicated in the first information. It should be understood that, since the first event notification address and the second event notification address obtained by the UPF from the first information are the latest addresses determined by the SMF, the UPF can On the premise that the event subscription information is not repeatedly issued, the correct event notification address is obtained, so that the UPF can successfully report the event report on the premise that the AF does not repeatedly issue the event subscription information.
  • the first information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the event notification address
  • the second information further includes a notification association identifier.
  • the AF can also send related information (such as the first notification related information) corresponding to the event subscription information, so that when the UPF reports the event report, the notification related information can be fed back to the application server at the same time. So that the application server can determine the association between the event report and the sent event subscription information according to the association information.
  • the first information includes at least one of the following information: service quality QoS monitoring request information, QoS notification control request information, and location request information.
  • the second information may be information for making a QoS monitoring request, or information for a QoS notification control request, or information for a location request of a terminal device.
  • the QoS-related information is service-related information
  • the location request information is non-service-related information. Therefore, for other service information and non-service information, the solutions in the above-mentioned first aspect and its possible designs can be adopted. It realizes the reporting of events and obtains corresponding beneficial effects, so it should also be included in the protection scope of this application.
  • a seventeenth aspect provides an event notification apparatus, which may include a receiving unit and a sending unit.
  • the receiving unit is configured to receive first information, a first event notification address and a second event notification address, where the first information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses an application server of an application.
  • the first event notification address is a destination address for receiving event notification information of the first event, and the destination address is an address of the application corresponding to the application function AF.
  • the second event notification address is the address of the local capability opening network element corresponding to the first user plane network element.
  • the sending unit is configured to send second information to the first event notification address through the local capability opening network element corresponding to the second event notification address, where the second information includes event notification information of the first event.
  • the first information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the event notification address
  • the second information further includes a notification association identifier
  • the first information includes at least one of the following information: service quality QoS monitoring request information, QoS notification control request information, and location request information.
  • An eighteenth aspect provides a user plane function UPF entity, where the UPF entity includes one or more processors and one or more memories. One or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. The computer instructions, when executed by one or more processors, cause a UPF entity to perform the event notification method of any one of the sixteenth aspect and its possible worlds.
  • a nineteenth aspect provides a computer-readable storage medium, the computer-readable storage medium includes computer instructions, when the computer instructions are executed, execute the sixteenth aspect and any one of its possible implementations. Event notification method.
  • a chip system in a twentieth aspect, includes a processing circuit and an interface.
  • the processing circuit is configured to call and run the computer program stored in the storage medium from the storage medium, so as to execute the event notification method according to any one of the sixteenth aspect and its possible implementation manners.
  • a twenty-first aspect provides a communication system, where the system includes: a first network element, a second network element, a third network element, and a fourth network element.
  • the first network element is used to send first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the network access identifier is used to indicate an application
  • the location of the application server, the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • the second network element is configured to receive the first information and the second information.
  • the third network element is configured to receive the first information and the third information.
  • a first user plane network element is selected for the terminal device, the first user plane network element corresponds to the first data network access identifier, and at least one data network access identifier includes the first data network access identifier.
  • the fourth information is determined according to the third information and is used to subscribe to the first event.
  • the first event notification address is determined according to the first data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.
  • the fourth network element is configured to receive the fourth information and the first event notification address. Send fifth information to the first event notification address, where the fifth information includes event notification information of the first event.
  • the first network element is an AF network element
  • the second network element is a policy control function PCF network element
  • the third network element is a session management function SMF network element
  • the fourth network element is a user plane function UPF network element.
  • FIG. 1 is a schematic diagram of a network architecture
  • FIG. 2 is a schematic logical diagram of a communication architecture provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of deployment of a communication architecture provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of deployment of another communication architecture provided by an embodiment of the present application.
  • 5A is a schematic diagram of deployment of another communication architecture provided by an embodiment of the present application.
  • 5B is a schematic flowchart of an event notification method provided by an embodiment of the application.
  • FIG. 6 is a schematic flowchart of another event notification method provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another event notification method provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another event notification method provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another event notification method provided by an embodiment of the present application.
  • Figure 10 is a schematic diagram of a PSA reselection provided in the embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another event notification method provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of the composition of an event notification device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of the composition of an application functional entity according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of the composition of a chip system according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of the composition of another event notification apparatus provided by an embodiment of the present application.
  • FIG. 16 is a schematic diagram of the composition of a policy control functional entity according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of the composition of another chip system provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of the composition of another event notification apparatus provided by an embodiment of the present application.
  • FIG. 19 is a schematic diagram of the composition of a session management functional entity provided by an embodiment of the present application.
  • FIG. 20 is a schematic diagram of the composition of another chip system provided by an embodiment of the present application.
  • FIG. 21 is a schematic diagram of the composition of another event notification apparatus provided by an embodiment of the present application.
  • FIG. 22 is a schematic diagram of the composition of a user plane functional entity according to an embodiment of the present application.
  • FIG. 23 is a schematic diagram of the composition of another chip system provided by an embodiment of the present application.
  • the terminal device can reselect the locally deployed UPF and the application server. If the application server still needs to get the event report, it needs to re-subscribe to the event. This can cause delays in UPF getting and feeding back incident reports.
  • the embodiment of the present application provides an event notification method, which can enable the core network element (such as the session management function) to be able to configure the new UPF according to the new UPF configured by the application server when the UPF changes due to the movement of the terminal device.
  • the corresponding event notification address instructing the UPF to report the acquired event report to the corresponding address.
  • the application server does not need to re-issue the event subscription information through AF, PCF, and SMF again, which can significantly save the number of communications between different network elements, save signaling overhead, and ensure fast feedback of event reports.
  • FIG. 2 is a schematic diagram of a communication architecture provided by an embodiment of the present application.
  • the communication architecture may include terminal equipment, RAN, UPF, AMF, SMF, PCF and AF.
  • the AF may be a corresponding functional entity of the application server.
  • one application server may correspond to one or more AFs.
  • the application server may issue event subscription information through the AF, which is used to subscribe the corresponding UPF to acquire and report the corresponding event report.
  • the application server may further issue address correspondence information including at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier through the AF. It should be noted that, in this application, the application server may deliver the above-mentioned event subscription information through the same AF, and the information corresponding to the address.
  • the application server may also deliver the above-mentioned event subscription information through different AFs, and the information corresponding to the address.
  • the AF for receiving the event report by the application server may be the same as or different from the AF for sending the event subscription information and/or address correspondence information. This embodiment of the present application does not limit this.
  • PCF Policy control function
  • the PCF can be used to customize corresponding policy and charging control (policy and charging control, PCC) rules according to the message from the AF.
  • the PCC rule is issued to other network elements, so that other network elements can execute corresponding events according to the PCC rule.
  • the PCF may be used to customize a PCC rule including an address correspondence according to the address correspondence information from the AF, and issue the PCC rule to other network elements, so that other network elements can
  • the PCC rule learns the correspondence between the event report notification address and the data network access identifier.
  • the PCF can also be used to customize the corresponding PCC rules according to the event subscription information from AF (or network exposure function (NEF)), or update existing PCC rules, and deliver the PCC rules to other network elements, so that other network elements can execute the corresponding event according to the PCC rule and feed back the event report to the corresponding address.
  • AF network exposure function
  • NEF network exposure function
  • Session management function session management function
  • SMF Session management function
  • the SMF is primarily responsible for interacting with the separate data plane, creating, updating and deleting PDU sessions, and managing the session context with the UPF.
  • the SMF may be configured to receive a PCC rule of the PCF, and execute a corresponding event according to the PCC rule.
  • the SMF may be used to select the corresponding UPF for the terminal device according to the data network access identifier included in the PCC rule.
  • the SMF may use the UPF closest to the terminal device as a protocol data unit anchor (PDU Session Anchor, PSA) for establishing a PDU session with the terminal device.
  • PDU Session Anchor protocol data unit anchor
  • the SMF can also configure the PSA for the terminal device according to other rules, for example, the SMF can configure the PSA for the terminal device according to the historical communication quality. This embodiment of the present application does not limit this. SMF can also be used to receive PCC rules including address correspondence information and event subscription information, determine the corresponding event report notification address according to the PSA currently selected for the terminal device, and send the address and event subscription information to the corresponding PSA, so that PSA performs corresponding operations.
  • Core network access and mobility management function Core access and mobility management function
  • AMF Core network access and mobility management function
  • the AMF is mainly responsible for the access authentication of terminal equipment, mobility management, and signaling interaction between various functional network elements, such as the registration status of the user, the connection status of the user, the user registration and access to the network, and the tracking area. Update, cell handover user authentication and key security are managed.
  • the UPF may establish a PDU session with a corresponding terminal device according to the information sent by the SMF, so as to implement functions such as packet routing and forwarding, data packet inspection, and implementation of some policy rules on the user plane.
  • the UPF may execute the corresponding event according to the event subscription information from the SMF, and obtain the corresponding event report.
  • the UPF can also feed back the event report through the event report notification address sent by the SMF, so that when the UPF reselection occurs after the UE moves, the AF does not need to re-issue the event subscription information, and the application server can also obtain the corresponding event report.
  • the terminal equipment may include a user equipment (user equipment, UE) or a mobile station (mobile station, MS) or a mobile terminal device (mobile terminal, MT) and the like.
  • the terminal device may be a mobile phone (mobile phone), a tablet computer, or a computer with a wireless transceiver function, and may also be a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal device , wireless terminal equipment in industrial control, wireless terminal equipment in unmanned driving, wireless terminal equipment in telemedicine, wireless terminal equipment in smart grid, wireless terminal equipment in smart city, smart home, vehicle Terminal Equipment.
  • the terminal device can communicate with a data network (data net, DN) by establishing a PDU session with the UPF.
  • DN data network
  • a radio access network is an access network element that provides wireless access services.
  • this network element may be called NR-RAN.
  • the RAN may be implemented by a base station.
  • the RAN can be a node that provides a new radio (NR) user plane and control plane protocol terminals to terminal equipment, and is connected to the 5G core network via an NG interface.
  • the RAN can also be a node that provides terminal equipment with Evolved Universal Terrestrial Radio Access Network (E-UTRAN) user plane and control plane protocol terminals, and is connected to the 5G core network via the NG interface.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the network architecture may also include the NEF.
  • the NEF is an example of a capability opening network element, and in other implementation manners, the NEF can also be replaced by other capability opening network elements.
  • the NEF may be set at the front end of the AF to perform secondary processing on the information sent/received by the AF, so as to ensure the AF communication function and at the same time perform address protection for the AF and the like.
  • the NEF may be set in the local network, each NEF may be configured with an address (for example, called an NEF address), and the NEF may receive the event report reported by the UPF through the corresponding NEF address.
  • the NEF can also be used to send the received event report to the AF corresponding to the local NEF.
  • To implement event reporting is feedback to the application server.
  • NEFs may also be set up in the central network to perform similar functions to local NEFs. It should be understood that, in some implementation manners, different NEFs may be set in the central network and the local network at the same time, so as to realize network function expansion at multiple levels.
  • FIGS. 3-5B show a specific deployment method based on the schematic diagram shown in FIG. 2 .
  • the hierarchical management of data can be realized by setting up multiple data centers (data centers, DCs) on the layer side.
  • DCs data centers
  • a central DC (central DC) covering a larger area may be set, and one or more local DCs (local DC) may also be included in the coverage area of the central DC.
  • AMF, SMF, PCF and NEF can be set up in the central DC.
  • one or more local DCs may also be deployed in different locations.
  • the embodiment of the present application uses a central DC and a local DC as an example.
  • the UPF, as well as the AF, can be set in this local DC.
  • the UPF set in the local DC may be referred to as a local UPF (local UPF)
  • the AF set in the local DC may be referred to as a local AF (local AF).
  • the data interaction of each network element is exemplarily described by taking the AF delivering the QoS monitoring request information as an example.
  • the AF can deliver a message including the QoS monitoring request information to the NEF through the N33 interface, and the NEF can send the message to the PCF through the N6 interface.
  • the PCF can customize the corresponding PCC rules and deliver them to the SMF through the N7 interface.
  • the SMF can deliver the relevant signaling to the AMF through the N11 interface, so that the AMF can perform corresponding signaling interaction with the terminal device through the N1 interface, and/or perform corresponding signaling interaction with the RAN through the N2 interface.
  • the SMF may also send the QoS monitoring request information and the event report notification address (such as the address of the AF) corresponding to the QoS monitoring request information to the UPF through the N4 interface.
  • the UPF performs corresponding monitoring according to the QoS monitoring request information to obtain an event report. Then, the UPF can feed back the event report to the AF with the corresponding event report notification address through the N4a interface.
  • the UPF when sending the event report, the UPF selects the corresponding transmission channel according to the event notification address sent by the SMF.
  • the event notification address delivered by the SMF is the same as the AF that sends the QoS monitoring request information, so the UPF can feed back the event report to the AF.
  • the UPF when the event notification address delivered by the SMF is different from the AF that sent the QoS monitoring request information, the UPF sends the corresponding event report to the corresponding network element according to the event notification address.
  • the NEF can also be set in the local DC. In this way, after the UPF obtains the event report, it can send the event report to the NEF in the local DC through the N4a interface, so that the NEF can send the event report to the corresponding AF.
  • NEFs can be deployed simultaneously to achieve multi-level expansion of network functions.
  • 5A is an example of setting one NEF in the local DC and the central DC respectively (eg, setting NEF1 in the local DC and setting NEF2 in the central DC).
  • event subscription information such as QoS monitoring request information
  • it can send the information to NEF1 through the N33 interface, and NEF1 can forward the information (or send it after transcoding it) through the N33a interface.
  • NEF2 so that NEF2 can pass this information on until it is released to the UPF.
  • the UPF can send the event report to NEF1 through the N4a interface. So that NEF1 sends the event report to the corresponding application server.
  • the event notification method provided in the embodiment of this application can be applied to a network architecture of 4G/5G service capability interworking, and can also be applied to a future 6th generation (6G) communication system or other communication systems, which is not limited in this application. .
  • the method can be applied to a communication network having the logical schematic shown in FIG. 2 , and can also be applied to a deployed communication network as shown in FIG. 3 or FIG. 4 or FIG. 5A .
  • FIG. 5B is a schematic flowchart of an event notification method provided by an embodiment of the present application.
  • the method may be applied to the communication network as shown in FIG. 3 or FIG. 4 or FIG. 5A , or the method may also be applied to other communication networks having the logic shown in FIG. 2 .
  • the following description will be given by taking the method applied to the communication network as shown in FIG. 4 as an example.
  • the method may include S501-S508.
  • the AF sends the first information and the second information.
  • the first information may include at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, where the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the receiving event
  • the destination address of the notification information where the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the data network access identifier may be a data network access identifier (data network access identifier, DNAI).
  • DNAI data network access identifier
  • the DNAI can be used to indicate the location of the application server of the application.
  • the application server at each location may correspond to a DNAI.
  • event reports generally need to be reported to the AF or NEF that subscribes to the corresponding event.
  • the AF and NEF applied in the local DC are generally set correspondingly, and there may also be a corresponding relationship between the application server and the AF. Therefore, a DNAI corresponding to an application server has a corresponding relationship with AF (and/or NEF).
  • a corresponding relationship between the DNAI and the address (eg, the destination address) at which the AF or NEF receives the event report (or event notification information) can be established, that is, the above-mentioned at least one data network access identifier and at least one data network access identifier can be established.
  • the event notification address corresponding to the network access identifier It is carried in the first information and sent to other core network elements, such as PCF.
  • the correspondence between the data network access identifier and the corresponding event notification address may be referred to as address correspondence information.
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application. It should be noted that the second information can be used to subscribe to service-related events. Exemplarily, in some implementations, the second information may include quality of service QoS monitoring request information, and/or QoS notification control request information. In other embodiments, the second information may also be used to subscribe to events not related to services. Exemplarily, the second information may include location request information.
  • the delivery of the first information and the second information may be delivered by the application server controlling the same AF in one message stream, or by the application server controlling the same AF to deliver in different message streams, or It is sent by the application server to control different AFs in different message streams.
  • This embodiment of the present application does not limit this.
  • the second information may further include a notification association identifier, where the notification association identifier is used to associate the event notification information of the first event with the first information.
  • the notification association identifier is used to associate the event notification information of the first event with the first information.
  • the PCF receives the first information and the second information.
  • the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, where the network access identifier is used to indicate the location of the application server of the application, and the event notification address is the one that receives the event notification information.
  • Destination address where the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • the PCF sends the third information and the first information.
  • the third information is determined according to the second information and is used to subscribe to the first event. It should be understood that, in some implementation manners, after receiving the second information, the PCF may perform certain processing on the second information before sending it to other network elements (eg, SMF). As an example, the PCF may encapsulate the address correspondence information included in the first information and the corresponding information for subscribing to the first event indicated in the second information into a PCC rule, and deliver the PCC rule to the SMF.
  • the information in the PCC rule for indicating subscription to the first event may be the same as the second information, that is, the third information is the same as the second information.
  • the information used to indicate that the first event is scheduled in the PCC rule may also be different from the second information, that is, the third information is different from the second information. This embodiment of the present application does not limit the specific form of the third information.
  • the PCF may deliver the first association identifier to the SMF together.
  • the PCF may carry the first association identifier in the PCC rule and deliver it to the SMF.
  • the above description is described by taking the PCF encapsulating the first information, the third information and the first association identifier in the PCC rule as an example for delivery.
  • the first information, the third information and the first association identifier are delivered to other network elements (eg SMF).
  • the PCF may send the first information, the third information and the first association identifier in the same message flow, and the PCF may also send the first information, the third information and the first association identifier respectively in different message flows.
  • This embodiment of the present application does not limit the manner in which the PCF delivers the first information, the third information, and the first association identifier.
  • the SMF receives the first information and the third information.
  • the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, where the network access identifier is used to indicate the location of the application server of the application, and the event notification address is for the purpose of receiving event notification information address, and the destination address is the address of the local capability exposure network element corresponding to the application or the address of the application function AF.
  • the third information is used to subscribe to the first event of the terminal device, which is a device accessing the application server of the application.
  • the SMF may receive the first information and the third information by receiving the PCC rule sent by the PCF.
  • the SMF selects the first user plane network element for the terminal device.
  • the first user plane network element corresponds to the first data network access identifier, and at least one data network access identifier includes the first data network access identifier.
  • the SMF may, according to the DNAI included in the PCC rule, select a corresponding UPF as the PSA for the terminal device to establish a PDU session so that the terminal device can access the data network.
  • the SMF may determine the corresponding event notification address according to the first information in the PCC rule (which may include address correspondence information) in combination with the DNAI corresponding to the current PSA.
  • the SMF can reselect the corresponding UPF as the PSA for the terminal device according to the DNAI included in the PCC rule.
  • the SMF may determine the corresponding event notification address according to the first information in the PCC rule (which may include address correspondence information) and in combination with the DNAI corresponding to the current PSA. It can be seen that when PSA reselection occurs, since SMF can know the correspondence between different DNAIs and event notification addresses, SMF can pass the correspondence (ie address correspondence information) after reselection of PSA for the terminal device.
  • the event notification address corresponding to the new PSA is determined without the need for the AF to re-issue the event subscription information. In this way, the reporting delay of the corresponding event can be greatly reduced.
  • the event notification address corresponding to the PSA may be referred to as the first event notification address.
  • the SMF may also obtain the address of the forwarding NEF (such as the second event notification address), so as to deliver the second event notification address to the UPF, so that the UPF can pass the second event notification address Realize the reporting of the event report to the first event notification address.
  • the forwarding NEF such as the second event notification address
  • the SMF sends the fourth information and the first event notification address.
  • the first event notification address is a destination address for receiving event notification information of the first event.
  • the fourth information may be determined according to the third information and used for subscribing to the first event.
  • the first event notification address may be the SMF according to the first data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier (such as the above address correspondence information) Sure.
  • the fourth information may further include a notification association identifier for associating the event notification information of the first event with the event notification address.
  • the SMF may deliver the second event notification address to the UPF.
  • the fourth information, the first event notification address and the second event notification address may be delivered in the same message, or may be delivered in different messages. This embodiment of the present application does not limit the manner in which the relevant information is distributed.
  • the UPF receives the fourth information and the first event notification address.
  • the UPF may be the first user plane network element selected by the SMF for the terminal device.
  • the first information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • the first event notification address is a destination address for receiving event notification information of the first event, and the destination address is an address of the application corresponding to the application function AF.
  • the UPF may also receive a second event notification address, where the second event notification address may be an address of a local capability opening network element corresponding to the first user plane network element.
  • the first user plane network element may report the event report to the first event notification address through the second event notification address.
  • the second event notification address may be the address of the NEF for forwarding the event report.
  • the second event notification address may also be the address of other network elements capable of implementing the forwarding function of the event report to the network element having the first event notification address. This embodiment of the present application does not limit this.
  • the UPF may receive the address of the NEF with the forwarding function (eg, the second event notification address). So that after obtaining the event report, the event report and the corresponding destination address (such as the first event notification address) can be sent to the NEF corresponding to the second event notification address, so that the NEF can send the event report to the first event notification address.
  • the NE corresponding to the event notification address.
  • the UPF sends fifth information.
  • the fifth information may include event notification information of the first event.
  • the fifth information may include an event report corresponding to the QoS monitoring request.
  • the fifth information may include an event report corresponding to the QoS notification control request.
  • the fifth information may include an event report corresponding to the location request information.
  • the fifth information may be sent to the second event notification address.
  • the UPF may also send the first event notification address to a network element (eg, NEF) corresponding to the second event notification address, so that the NEF can send the event report included in the fifth information to the first event notification address.
  • NEF network element
  • the UPF may directly send the fifth information to the network element (eg, AF or NEF) corresponding to the first event notification address.
  • the network element eg, AF or NEF
  • the fifth information may further include a notification association identifier, so that the network element receiving the event report can specify the association between the event notification information of the first event and the event notification address according to the notification association identifier .
  • the SMF can determine the event notification address of the event report of the event subscription information according to the DNAI corresponding to the current PSA and the address corresponding information. Therefore, when PSA reselection occurs, since SMF knows the correspondence between all DNAIs and event notification addresses, there is no need for AF to re-issue event subscription information. SMF can determine the event notification address corresponding to the new PSA and deliver it to UPF. So that UPF can report accurately. Thereby, the delay of event report reporting can be significantly reduced, and at the same time, signaling interaction between core network elements can be saved.
  • FIG. 6 shows a specific implementation manner in which the AF performs address correspondence information delivery.
  • FIG. 7 is an example of a method for realizing PSA selection on the basis of FIG. 6 .
  • FIG. 8 is an example of the issue of event subscription information and the reporting of the corresponding event report.
  • FIG. 9 shows an example of event reporting in a PSA reselection scenario.
  • FIG. 11 shows an example of sending and reporting event subscription information in a scenario where the subscription event is a non-service-related event.
  • the above methods shown in FIG. 6 , FIG. 7 , FIG. 8 , FIG. 9 , and FIG. 11 can be applied to the logical architecture shown in FIG. 2 , and of course can also be applied to those shown in FIG. 3 or FIG. 4 or FIG. 5A in deployment.
  • the terminal device is used as the UE, and the application server sends the data network access identifier and the corresponding event notification address (such as address correspondence information), event subscription information and receiving events through the same AF. Report, the method is applied to the network architecture shown in Figure 4 as an example.
  • the AF may implement the configuration of the address correspondence information according to the method shown in FIG. 6 .
  • the method may include S601-S603.
  • the AF sends information 6-1 to the NEF.
  • the information 6-1 may include address correspondence information.
  • the address correspondence information may include at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier.
  • a data network access identifier may correspond to an event notification address.
  • one data network access identifier may also correspond to multiple event notification addresses. The following description is given by taking as an example that one data network access identifier may correspond to one event notification address.
  • the information 6-1 can be sent through the Nnef_TrafficInfluence_Create Request message.
  • the data network access identifier may be DNAI.
  • the event notification address may be the receiving address of the event report corresponding to the DNAI. It should be noted that the event notification address may be the NEF address corresponding to the application server of the application, or the AF address corresponding to the application server of the application.
  • the DNAI represents the location information of the application, that is, the location information of the application server of the application.
  • An application can have multiple different application servers under different local DCs. If the application server wants to interact with the PCF, the application server needs to interact with the AF deployed in the local DC, and then the AF interacts with the PCF. Therefore, an application server can generally correspond to an AF address, and thus DNAI can also correspond to an AF. If a local NEF is deployed in the local DC, DNAI can also correspond to an NEF.
  • the address correspondence information in the example may include the correspondence between the DNAI corresponding to each AF in different local DCs and the AF receiving event notification address. So that other network elements (such as SMF) can determine the address of the AF or NEF that can receive the event report according to the DNAI corresponding to the selected local UPF.
  • the information 6-1 may also include Traffic Steering Info, which may include an application service provider (application service provider, ASP) identifier, service description information, and an identifier of the corresponding UE.
  • an application service provider application service provider, ASP
  • the information 6-1 may also include an ASP identifier capable of identifying an application, service description information, and identification information of the target UE (such as the IP address of the UE, the indication information of any UE, the external identifier of the UE or the external identifier of the target UE). group ID).
  • the NEF sends information 6-2 to the PCF.
  • the NEF may process it, such as transcoding, so as to hide the information 6-1 and achieve the purpose of protecting the AF.
  • the NEF can achieve the above purpose by mapping the external group identifier in the Nnef_TrafficInfluence_Create Request to the internal group identifier and the UE's external identifier to the internal identifier.
  • the NEF may send the information 6-2 obtained according to the information 6-1 to the PCF.
  • the NEF can directly send the information 6-2 to the PCF or the NEF can send the information 6-2 to the PCF through a unified data repository (Unified Data Repository, UDR) that provides data storage services.
  • UDR Unified Data Repository
  • the NEF sends it to the PCF through the Npcf_PolicyAuthorization Request.
  • the information 6-2 includes relevant information for indicating address correspondence information, ASP identifiers, and service description information. The function is similar to the relevant information in S601, and will not be repeated here.
  • the NEF can send the information 6-2 to the UDR through Nudr_DM_Update Request.
  • the UDR can store the Nudr_DM_Update Request after receiving it.
  • the PCF For the PCF that needs to obtain this information, it generally subscribes the corresponding Traffic Steering Info to the UDR, and the UDR can send the Nudr_DM_Update Request to the PCF that has subscribed to the corresponding Traffic Steering Info. The transmission of the information 6-2 to the PCF is thereby achieved.
  • the information 6-2 when the NEF is set between the AF and the PCF, the information 6-2 may correspond to the first information in the solution shown in FIG. 5B .
  • the above-mentioned information 6-1 when the NEF is not set between the AF and the PCF, the above-mentioned information 6-1 may correspond to the first information in the scheme shown in FIG. 5B .
  • the PCF generates a first PCC rule according to the information 6-2.
  • the PCF After receiving the information 6-2, the PCF can generate a corresponding PCC rule according to the information 6-2, so that other network elements can perform corresponding operations according to the PCC rule.
  • the PCF can customize the corresponding PCC rule (for example, referred to as PCC rule 1).
  • PCC rule 1 only the DNAI or the corresponding relationship between the DNAI and the event notification address may be included.
  • the Nudr_DM_Update Request includes the correspondence between multiple DNAIs corresponding to application 1 and the event notification address.
  • PCC rule 1 it may include multiple DNAIs corresponding to the application 1 or the corresponding relationship between multiple DNAIs and event notification addresses.
  • the address correspondence information included in the first PCC rule may be the same as the address correspondence information in the first information in the solution shown in FIG. 5B .
  • the address correspondence information corresponding to the application is embodied in the PCC rule.
  • the SMF may select a corresponding UPF as the PSA for the UE according to the PCC rule.
  • the PCF may send the first PCC rule to the SMF (ie, perform S701).
  • the SMF may select the UPF as the PSA for the UE according to the first PCC rule (ie, DNAI) (ie, perform S702).
  • the SMF may determine the application server corresponding to the application 1 according to the first PCC rule. Since there is a corresponding relationship between the application server and the UPF in different local DCs, the SMF can obtain the list of UPFs that can access the application 1 accordingly.
  • the SMF can select the corresponding UPF as the PSA for the UE according to a preset rule. For example, according to the current position of the UE, the SMF can select the UPF that is closest to the UE, and the UPF in the above-mentioned UPF list is used as the PSA to establish a PDU session with the UE. Of course, the SMF can also select the PSA for the UE according to other rules, which will not be repeated here. It should be understood that, in the solution shown in FIG. 7 , the PSA determined by the SMF for the UE according to the first PCC rule may correspond to the first user plane network element in the solution shown in FIG. 5B .
  • the UE can access the DN through the PDU session, for example, the UE can access the application server corresponding to the application 1 through the PDU session.
  • the UE can interact with the application server through application layer signaling, and the application server can deliver event subscription information to the UPF through the AF.
  • the event subscription information may be service-related information, such as QoS monitoring information.
  • the event subscription information may also be information not related to services.
  • the event subscription information may be used to subscribe to the location information of the UE. This embodiment of the present application does not limit this. In the following, the event subscription information is used for the scheduled QoS monitoring information as an example.
  • FIG. 8 a schematic flowchart of an event notification method provided by an embodiment of the present application is shown. It can be understood that this method can be applied in the scenario where the UE performs relevant detection on the communication process after the UE establishes a PDU session in the UPF. For example, the method can be applied after the UE establishes the PDU session as shown in FIG. 7 .
  • the method may include S801-S808. This method can be applied after the PDU session is established as shown in FIG. 7 . It should be noted that, in other implementation manners, the method shown in FIG. 8 may also be performed simultaneously with the method shown in FIG. 7 . This embodiment of the present application does not limit the execution sequence of the method shown in FIG. 7 and the method shown in FIG. 8 . The following takes the establishment of the PDU session shown in FIG. 7 as an example before executing the method shown in FIG. 8 .
  • the AF sends information 8-1 to the NEF.
  • the information 8-1 may include event subscription information.
  • the event subscription information being used to request service-related communication data (eg, QoS-related data) as an example.
  • the event subscription information may include description information of the service data flow, an ASP identifier, and the like.
  • the event subscription information when used for quality of service monitoring (QoS Monitoring), the event subscription information may further include QoS Monitoring information or QoS Monitoring information and a QoS Monitoring event identifier.
  • the QoS Monitoring information may include, but is not limited to, the requested QoS Monitoring Parameter (that is, the measured delay type, which may include uplink data, downlink data, or round-trip data), reporting frequency (periodicity, event trigger) and other information.
  • the event subscription information when used to request a QoS Notification Control (QoS Notification Control) event notification, the event subscription information may also include an indication of the QoS Notification Control (such as a QoS Notification Control event identifier) and the like.
  • the information 8-1 may be sent to the NEF through the Nnef_AFsessionWithQoS_Create request message, and the message may include the notification association identifier.
  • the UPF may carry the notification association identifier in the corresponding event report, so that the AF or NEF receiving the event report can know that the event report is associated with the event subscription.
  • the NEF sends information 8-2 to the PCF.
  • the NEF can perform similar processing on the information 8-1, acquire the information 8-2 and send it to the PCF. The processing process is similar, and will not be repeated here.
  • the NEF can also transmit the information 8-2 through the UDR, which is not limited in this example.
  • the information 8-2 sent by the NEF may be Npcf_PolicyAuthorization Request.
  • the information 8-2 when the NEF is set between the AF and the PCF, the information 8-2 may correspond to the second information in the scheme shown in FIG. 5B .
  • the above-mentioned information 8-1 may correspond to the second information in the scheme shown in FIG. 5B .
  • the PCF acquires the second PCC rule according to the information 8-2 and the first PCC rule.
  • the PCF stores the first PCC rule.
  • the first PCC rule may include address correspondence information corresponding to the application.
  • the PCF can update the first PCC rule to obtain the updated PCC rule (ie, the second PCC rule).
  • the second PCC rule may include event subscription information and address correspondence information of an application corresponding to the event subscription information.
  • the second PCC rule in this example may include event subscription information corresponding to the third information in the scheme shown in FIG. 5B , and address correspondence information of the first information in the scheme shown in FIG. 5B .
  • the PCF can associate the above-mentioned application address correspondence information with the information 8-2 according to the ASP identifier in the information 8-2.
  • the PCF may determine the address correspondence information of the corresponding application in the first PCC rule according to the ASP identifier corresponding to the event subscription information included in the information 8-2. For example, if the ASP identifier corresponding to the event subscription information indicates that the event subscription information corresponds to application 1, the PCF can carry the address correspondence information 6-1 corresponding to application 1 in the second PCC rule according to the ASP identifier.
  • the second PCC rule may further include other information, for example, the second PCC rule may include the notification association identifier in the information 8-2.
  • the PCF sends the second PCC rule to the SMF.
  • the SMF determines the event notification address 1 according to the second PCC rule.
  • the SMF Since the SMF selects the PSA for the UE according to the first PCC rule, when the SMF receives the second PCC rule (that is, the event subscription information), the SMF further determines the event notification address 1 according to the DNAI used to select the PSA and the address correspondence information of the application .
  • the event notification address 1 may correspond to the first event notification address in the solution shown in FIG. 5B .
  • the SMF sends information 8-3 to the UPF.
  • the SMF may send information 8-3 including event subscription information (the fourth information in the scheme shown in FIG. 5B ), the event notification address 1, and the notification association identifier to the UPF corresponding to the event.
  • the UPF obtains an event report.
  • the UPF can perform corresponding monitoring according to the acquired event subscription information.
  • the UPF acquisition event report may also be referred to as a PSA acquisition event report.
  • the PSA can measure the packet transmission delay between the UE and the PSA.
  • the event corresponding to QoS Monitoring is detected.
  • the event subscription information is QoS Notification Control
  • the PSA receives a notification from the RAN that the bandwidth cannot be guaranteed or that the bandwidth can be guaranteed again, it detects the QoS Notification Control event.
  • the UPF sends information 8-4 to the AF.
  • the UPF After the UPF obtains the event report corresponding to the event subscription information, it can execute the feedback of the event report. Exemplarily, the UPF may feed back the event report to the network element with the event notification address 1 .
  • the network element may be AF or NEF.
  • the network element corresponding to the event notification address 1 is AF as an example for description.
  • the UPF can transmit data with the NEF in the local DC through the N4a interface. Further NEFs can transmit corresponding data to AFs in the local DC.
  • the event notification address 1 may be the address of the local NEF.
  • the UPF may send the information 8-4 including the event report, notification association identification to the NEF. In this way, the UPF completes the reporting of the event report to the event notification address 1.
  • the information 8-4 may correspond to the fifth information in the scheme shown in FIG. 5B.
  • the event notification address may be an address corresponding to an AF in the local DC, an address corresponding to an AF located in other local DCs, or an address corresponding to an AF located in the central DC.
  • the information 8-3 sent by the SMF to the UPF may include, in addition to the event notification address 1, the address of the NEF (eg, the event notification address 2) corresponding to the event notification address.
  • the UPF can report the event report and the event notification address 1 to the network element corresponding to the event notification address 2 .
  • the NEF may further transmit the event report to the network element (eg AF) having the event notification address 1.
  • the event notification address 2 may correspond to the second event notification address in the scheme shown in Fig. 5B.
  • the SMF determines the event notification address corresponding to the new PSA according to the saved event subscription information, and delivers the new event notification address together with the event subscription information to the UPF. This can avoid the problem that after PSA reselection occurs, the AF must re-issue the event subscription information to ensure that the UPF transmits the event report to the correct address.
  • FIG. 9 shows a schematic flowchart of a method for reporting events after PSA reselection.
  • the UE pair usage leads to PSA reselection as an example.
  • the method may include S901-S905.
  • the SMF reallocates the PSA for the moving UE.
  • the SMF can adjust the PSA for the UE to access the DN as the UE moves.
  • this reallocated PSA may be referred to as the second user plane network element, ie the second UPF.
  • the SMF may also switch the PSA for the PDU session with the UE from UPF1 in local DC1 to UPF2 in local DC2.
  • UPF1 and UPF are the same, when the UE is in position 2, UPF2 can provide a better communication service for the UE.
  • the SMF can know the correspondence between all DNAIs corresponding to the application and the event notification addresses (such as the above address correspondence information), after the PSA is updated, the SMF can also determine the corresponding updated event notification address.
  • the application server in DC1 will also send the event subscription information to the application server in DC2 through the application layer (such as a notification association identifier), after which DC2 can interact with the corresponding AF, and notify the AF to notify the corresponding event sent to the application server.
  • the application layer such as a notification association identifier
  • the SMF determines the event notification address 3 according to the second PCC rule.
  • the event notification address 3 corresponding to the DNAI corresponding to the new PSA may be determined according to the second PCC rule.
  • the determination method is similar to S805 shown in FIG. 8 and will not be repeated here.
  • the SMF sends information 9-1 to the UPF.
  • the UPF sends information 9-2 to the AF.
  • the SMF can continue to execute S903-S905. Their respective execution modes can correspond to S806-S808 shown in FIG. 8 . It will not be repeated here.
  • the information 9-1 may include the fourth information and the first event notification address in the scheme shown in FIG. 5B .
  • the information 9-2 may include the fifth information in the scheme shown in FIG. 5B.
  • a UPF in a network can be selected as a branching point or an uplink classifier. This enables the uplink data sent by the UE to access the application to be forwarded to the reselected PSA through the UPF. In this way, smooth uplink communication of the UE after reselection of the PSA is realized.
  • the AF can configure the information corresponding to different addresses into the PCF by the method shown in FIG. 6 .
  • the AF can also deliver event subscription information through the method shown in FIG. 8 . So that the SMF can determine the event notification address corresponding to the selected PSA based on the interaction with the PCF, and instruct the UPF to report the event report corresponding to the event subscription information through the event notification address.
  • the application server may control the same or different AFs,
  • the event subscription information and information including information corresponding to different addresses are delivered to other network elements through the same signaling.
  • the application server may also control the same or different AFs, and deliver event subscription information and information including information corresponding to different addresses to other network elements through different signaling.
  • the application server may control the same or different AFs , the event subscription information and information including information corresponding to different addresses are delivered to other network elements through the same signaling.
  • FIG. 11 is a schematic flowchart of another event reporting method provided by an embodiment of the present application.
  • the AF that sends the event subscription information and the address information is the same as the AF that receives the event report, for example.
  • the method may include S1101-S1107.
  • the AF sends information 11-1 to the PCF.
  • this information 11-1 can be sent via Nnef_TrafficInfluence_Create Request.
  • the information 11-1 may include at least the corresponding relationship between the DNAI and the event notification address (that is, the address correspondence information), the event identifier corresponding to the event subscription information, and the optional identifier allocated by the AF for the event subscription information (such as Notification Correlation Id).
  • the information 11-1 may include the first information and the second information in the scheme shown in FIG. 5B .
  • the AF can send the information 11-1 to the PCF through the NEF, the AF can also send the information 11-1 to the PCF through the NEF and UDR, and the AF can also This information 11-1 is sent directly to the PCF.
  • the specific implementation manner is similar to the method in S601-S602, which will not be repeated here.
  • the PCF customizes the corresponding PCC rule according to the information 11-1.
  • the PCF can customize the corresponding PCC rules according to the new 11-1 received.
  • the PCC rule may carry the Traffic Steering Policy, and the Traffic Steering Policy may include a list of DNAIs for the SMF to select the PSA according to the Traffic Steering Policy. If the identity information of the target UE indicated by the information 11-1 is the indication information of any UE or the internal group identity, the PCC rule also includes an indication of sending the UE identity.
  • the Traffic Steering Policy may also include address correspondence information, an event identifier, and a Notification Correlation Id. It should be understood that, in this example, the PCC rule may include the third information and the fourth information in the scheme shown in FIG. 5B .
  • the PCF sends the PCC rule to the SMF.
  • the SMF determines the event notification address according to the PCC rule.
  • the SMF can determine the event notification address corresponding to the event subscription information according to the address corresponding information in the PCC rule, that is, the currently selected PSA (such as the first user plane network element above).
  • the event notification address may be the first event notification address in the solution shown in FIG. 5B .
  • the SMF sends information 11-2 to the UPF.
  • the information 11-2 may include event subscription information and a corresponding event notification address. If the PCC rule includes an instruction to send the UE identity, the information 11-2 also includes the external identity of the UE. In some implementations, the information 11-2 may include the fourth information in the scheme shown in FIG. 5B and the first event notification address.
  • the UPF obtains an event report.
  • the UPF sends an event report to the AF.
  • the UPF can report the acquired event report through the event notification address indicated by the SMF.
  • the event report may be the fifth information in the scheme shown in FIG. 5B .
  • the AF when the AF issues the information 11-1, it can also issue a notification associated identifier, so that when the UPF reports an event, the notification associated identifier can be uploaded together, so that the application server can know the acquired event report and the next one.
  • the event subscription information is corresponding to some terminal devices. Therefore, when the UE reports the event report, it can report the Notification Correlation Id configured by the AF for it together, so that the application server can report the event. associated with the UE. If the information 11-2 includes the external identity of the UE, the external identity of the UE is also reported in the event report.
  • the SMF can determine the event notification address of the event report corresponding to the event subscription information according to the selected PSA.
  • the corresponding event reporting mechanism may be implemented according to the method shown in FIG. 9 . This avoids the problem of excessive delay caused by the need for AF to re-deliver event subscription information when the PSA changes.
  • the SMF can also obtain the event subscription information and the corresponding event notification address (such as address 1) to the UPF (that is, execute S1105). And send the address of the NEF (eg address 2).
  • the UPF can then obtain the event subscription information, address 1 and address 2, from the SMF. After the UPF acquires the corresponding event report, it can send the event report to the address 2, and simultaneously send the address 1 to the NEF corresponding to the address 2. So that the NEF can send the event report to the corresponding AF according to the address 1, so as to realize the smooth sending of the event report.
  • the above network elements can be divided into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 12 is a schematic block diagram of an event notification apparatus 1200 according to an embodiment of the present application.
  • the event notification apparatus 1200 may be set in the AF as shown in FIG. 2 or FIG. 3 or FIG. 4 or FIG. 5A, and is used to implement any one of the event notification methods provided in the embodiments of the present application.
  • the event notification apparatus 1200 may include: a determining unit 1201 and a sending unit 1202 .
  • the determining unit 1201 is configured to determine first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the network access identifier is used to indicate an application
  • the location of the application server, the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability open network element corresponding to the application or the address of the application function (AF).
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • the sending unit 1202 is configured to send the first information and the second information.
  • the determining unit 1201 may specifically determine the specific content of the first information and the second information according to the instruction of the application server.
  • the second information further includes: a notification association identifier, where the notification association identifier is used to associate the event notification information of the first event with the first information.
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • the event notification apparatus 1200 may further include a processing module or a control module for supporting the foregoing determining unit 1201 and/or sending unit 1202 to complete corresponding functions.
  • FIG. 13 shows a schematic composition diagram of an application function entity 1300 .
  • the application function entity 1300 may include: a processor 1301 and a memory 1302 .
  • the memory 1302 is used to store computer-implemented instructions. Exemplarily, in some embodiments, when the processor 1301 executes the instructions stored in the memory 1302, the application function entity 1300 can be caused to perform the operations that the AF needs to perform in the above examples.
  • FIG. 14 shows a schematic diagram of the composition of a chip system 1400 .
  • the chip system 1400 may include: a processor 1401 and a communication interface 1402 for supporting the AF to implement the functions involved in the above embodiments.
  • the system-on-a-chip 1400 further includes a memory for storing program instructions and data necessary for AF.
  • the chip system 1400 may be composed of chips, or may include chips and other discrete devices.
  • FIG. 15 is a schematic block diagram of yet another event notification apparatus 1500 provided by an embodiment of the present application.
  • the event notification apparatus 1500 may be set in the PCF as shown in FIG. 2 or FIG. 3 or FIG. 4 or FIG. 5A, and is used to implement any event notification method provided by the embodiments of the present application.
  • the event notification apparatus 1500 may include: a receiving unit 1501 and a sending unit 1502 .
  • the receiving unit 1501 is configured to receive first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the network access identifier is used to indicate an application
  • the location of the application server, the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • the sending unit 1502 is configured to send third information and first information, wherein the third information is determined according to the second information and is used for subscribing to the first event.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the third information further includes a notification association identifier
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • the event notification apparatus 1500 may further include a processing module or a control module for supporting the above-mentioned receiving unit 1501 and/or sending unit 1502 to complete corresponding functions.
  • FIG. 16 shows a schematic composition diagram of a policy control functional entity 1600 .
  • the policy control functional entity 1600 may include: a processor 1601 and a memory 1602 .
  • the memory 1602 is used to store computer-implemented instructions. Exemplarily, in some embodiments, when the processor 1601 executes the instructions stored in the memory 1602, the policy control functional entity 1600 can be made to perform the operations that the PCF needs to perform in the above examples.
  • FIG. 17 shows a schematic diagram of the composition of a chip system 1700 .
  • the chip system 1700 may include: a processor 1701 and a communication interface 1702 for supporting the PCF to implement the functions involved in the above embodiments.
  • the system-on-a-chip 1700 further includes a memory for storing necessary program instructions and data of the PCF.
  • the chip system 1700 may be composed of chips, or may include chips and other discrete devices.
  • FIG. 18 is a schematic block diagram of an event notification apparatus 1800 according to an embodiment of the present application.
  • the event notification apparatus 1800 may be set in the SMF as shown in FIG. 2 or FIG. 3 or FIG. 4 or FIG. 5A, and is used to implement any one of the event notification methods provided by the embodiments of the present application.
  • the event notification apparatus 1800 may include: a receiving unit 1801 and a sending unit 1802 .
  • the receiving unit 1801 is configured to receive first information and second information, where the first information includes at least one data network access identifier and an event notification address corresponding to the at least one data network access identifier, and the network access identifier is used to indicate an application's
  • the location of the application server the event notification address is the destination address for receiving event notification information, and the destination address is the address of the local capability open network element corresponding to the application or the address of the application function AF.
  • the second information is used to subscribe to the first event of the terminal device, and the terminal device is a device that accesses the application server of the application.
  • a first user plane network element is selected for the terminal device, the first user plane network element corresponds to the first data network access identifier, and at least one data network access identifier includes the first data network access identifier.
  • the sending unit 1802 is configured to send the third information and the first event notification address.
  • the third information is determined according to the second information and is used to subscribe to the first event.
  • the first event notification address is determined according to the first data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.
  • the sending unit 1802 is further configured to send a second event notification address, where the second event notification address is an address of a local capability openness network element corresponding to the first user plane network element.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the third information further includes a notification association identifier
  • the apparatus further includes a configuration unit 1803 for selecting a corresponding second user plane network element for the terminal device accessing the application server of the application, and the second user plane network element corresponds to the second data network access identifier, at least one data network access identifier includes a second data network access identifier.
  • the fourth information is determined according to the second information, and is used to subscribe to the first event.
  • the third event notification address is determined according to the second data network access identifier, at least one data network access identifier, and an event notification address corresponding to the at least one data network access identifier.
  • the sending unit 1802 is further configured to send a fourth event notification address, where the fourth event notification address is the address of the local capability opening network element corresponding to the second user plane network element.
  • the second information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the first information
  • the fourth information further includes a notification association identifier
  • the second information includes at least one of the following information: quality of service QoS monitoring request information, QoS notification control request information and location request information.
  • the event notification apparatus 1800 may further include a processing module or control for supporting the above-mentioned receiving unit 1801 and/or sending unit 1802 and/or configuring unit 1803 to complete corresponding functions module.
  • Fig. 19 shows a schematic diagram of the composition of a session management functional entity 1900.
  • the session management functional entity 1900 may include: a processor 1901 and a memory 1902 .
  • the memory 1902 is used to store computer-implemented instructions.
  • the session management function entity 1900 can be made to perform the operations that the SMF needs to perform in the above examples.
  • FIG. 20 shows a schematic diagram of the composition of a chip system 2000 .
  • the chip system 2000 may include: a processor 2001 and a communication interface 2002 for supporting the SMF to implement the functions involved in the above embodiments.
  • the system-on-a-chip 2000 further includes a memory for storing necessary program instructions and data for the SMF.
  • the chip system 2000 may be composed of chips, or may include chips and other discrete devices.
  • FIG. 21 is a schematic block diagram of an event notification apparatus 2100 according to an embodiment of the present application.
  • the event notification apparatus 2100 may be set in the UPF as shown in FIG. 2 or FIG. 3 or FIG. 4 or FIG. 5A , and is used to implement any one of the event notification methods provided in the embodiments of the present application.
  • the event notification apparatus 2100 may include: a receiving unit 2101 and a sending unit 2102 .
  • the receiving unit 2101 is configured to receive first information, a first event notification address and a second event notification address, where the first information is used to subscribe to a first event of a terminal device, which is a device accessing an application server of an application.
  • the first event notification address is a destination address for receiving event notification information of the first event, and the destination address is an address of the application corresponding to the application function AF.
  • the second event notification address is the address of the local capability opening network element corresponding to the first user plane network element.
  • the sending unit 2102 is configured to send second information to the first event notification address through the second event notification address, where the second information includes event notification information of the first event.
  • the first information further includes a notification association identifier
  • the notification association identifier is used to associate the event notification information of the first event with the event notification address
  • the second information further includes a notification association identifier
  • the first information includes at least one of the following information: service quality QoS monitoring request information, QoS notification control request information, and location request information.
  • the event notification apparatus 2100 may further include a processing module or a control module for supporting the above-mentioned receiving unit 2101 and sending unit 2102 to complete corresponding functions.
  • FIG. 22 shows a schematic composition diagram of a user plane functional entity 2200.
  • the application function entity 2200 may include: a processor 2201 and a memory 2202 .
  • the memory 2202 is used to store computer-implemented instructions.
  • the processor 2201 executes the instructions stored in the memory 2202, the user plane functional entity 2200 can be made to perform the operations that the UPF needs to perform in the above examples.
  • FIG. 23 shows a schematic diagram of the composition of a chip system 2300 .
  • the chip system 2300 may include: a processor 2301 and a communication interface 2302 for supporting the UPF to implement the functions involved in the above embodiments.
  • the system-on-a-chip 2300 further includes a memory for storing necessary program instructions and data for the UPF.
  • the chip system 2300 may be composed of chips, or may include chips and other discrete devices.
  • the functions or actions or operations or steps in the above embodiments may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer, or data storage devices including one or more servers, data centers, etc. that can be integrated with the medium.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Abstract

Les modes de réalisation de la présente demande, qui appartient au domaine des techniques de communication, concernent un procédé, un appareil et un système de notification d'événement. Lorsqu'une resélection d'une UPF (PSA) survient, un rapport d'événement correspondant peut être acquis sans qu'il soit nécessaire qu'un serveur d'application réémette des informations de souscription à un événement, ce qui réduit le retard d'acquisition du rapport d'événement. La solution spécifique est la suivante : la réception de premières informations et de deuxièmes informations, les premières informations comprenant au moins un identifiant d'accès au réseau de données et une adresse de notification d'événement correspondant au ou aux identifiants d'accès au réseau de données, l'identifiant d'accès au réseau étant utilisé pour indiquer l'emplacement d'un serveur d'application d'une application, l'adresse de notification d'événement étant une adresse de destination pour recevoir des informations de notification d'événement, et les deuxièmes informations étant utilisées pour souscrire à un premier événement d'un dispositif de terminal, le dispositif de terminal étant un dispositif accédant au serveur d'application de l'application ; la sélection, pour le dispositif de terminal, d'un premier élément de réseau de plan d'utilisateur correspondant à un premier identifiant d'accès au réseau de données ; et l'envoi de troisièmes informations et d'une première adresse de notification d'événement, les troisièmes informations étant déterminées selon les deuxièmes informations.
PCT/CN2021/107477 2020-07-31 2021-07-20 Procédé, appareil et système de notification d'événement WO2022022345A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010763473.2 2020-07-31
CN202010763473.2A CN114071554A (zh) 2020-07-31 2020-07-31 一种事件通知方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2022022345A1 true WO2022022345A1 (fr) 2022-02-03

Family

ID=80037579

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/107477 WO2022022345A1 (fr) 2020-07-31 2021-07-20 Procédé, appareil et système de notification d'événement

Country Status (2)

Country Link
CN (1) CN114071554A (fr)
WO (1) WO2022022345A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108353033A (zh) * 2015-11-30 2018-07-31 英特尔公司 移动终接分组发送
CN109951824A (zh) * 2018-04-09 2019-06-28 华为技术有限公司 通信方法及装置
CN110049070A (zh) * 2018-01-15 2019-07-23 华为技术有限公司 事件通知方法及相关设备
US20190349744A1 (en) * 2018-05-11 2019-11-14 Huawei Technologies Co., Ltd. Subscription Update Method, Device, and System
CN112312466A (zh) * 2019-07-30 2021-02-02 华为技术有限公司 一种事件报告的发送方法、装置及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108353033A (zh) * 2015-11-30 2018-07-31 英特尔公司 移动终接分组发送
CN110049070A (zh) * 2018-01-15 2019-07-23 华为技术有限公司 事件通知方法及相关设备
CN109951824A (zh) * 2018-04-09 2019-06-28 华为技术有限公司 通信方法及装置
US20190349744A1 (en) * 2018-05-11 2019-11-14 Huawei Technologies Co., Ltd. Subscription Update Method, Device, and System
CN112312466A (zh) * 2019-07-30 2021-02-02 华为技术有限公司 一种事件报告的发送方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Address editor’s notes for 5GS Bridge management and QoS mapping", 3GPP DRAFT; S2-1906616 WAS 5676 TS23.501 CR1425 ADDRESS EDITOR'S NOTES FOR 5GS BRIDGE MANAGEMENT AND QOS MAPPING - V1, vol. SA WG2, 17 May 2019 (2019-05-17), RENO, NEVADA, USA;, pages 1 - 8, XP051737141 *

Also Published As

Publication number Publication date
CN114071554A (zh) 2022-02-18

Similar Documents

Publication Publication Date Title
JP7047113B2 (ja) アプリケーションのサービスレベル合意を保証するための方法、デバイスおよびシステム
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
EP3732846B1 (fr) Contrôle de qualité de service (qos) dans l'informatique de périphérie mobile (mec)
AU2019251152B2 (en) Method and device for subscribing to service
US20210344590A1 (en) Application Function In A Network And Control Thereof
KR102387239B1 (ko) 모바일 네트워크 상호 작용 프록시
CN113841432A (zh) 用于提供与终端的连接以便使用边缘计算服务的方法和设备
US10924518B2 (en) UPF programming over enhanced N9 interface
CN115039391A (zh) 用于提供边缘计算服务的方法和装置
JP2021504991A (ja) アプリケーションのためのトラフィックをハンドリングするための方法および機能
US11477690B2 (en) Method for influencing data traffic routing in core networks by service applications
JP2022116193A (ja) 通信方法、通信装置、および通信システム
KR102233894B1 (ko) 네트워크 기능 장치 및 이를 이용한 요청 처리 방법
WO2018233451A1 (fr) Procédé, appareil et système de communication
WO2022022345A1 (fr) Procédé, appareil et système de notification d'événement
US20220217005A1 (en) Network Slice Charging Method and Apparatus
CN113993147B (zh) 信息处理方法、网元、存储介质及程序产品
WO2022099484A1 (fr) Procédé d'envoi d'identifiant et appareil de communication
JP2023510410A (ja) マルチアクセス関連情報を伴うプロビジョニングトラフィック操向
US20240121309A1 (en) Managing content provider multi-path policies
RU2783811C2 (ru) Способ подписки на услуги и устройство
WO2024098937A1 (fr) Procédé de communication, appareil de communication et support de stockage
KR20220055993A (ko) 호처리 가속화 장치 및 호처리 가속화 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21850001

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21850001

Country of ref document: EP

Kind code of ref document: A1