A method, apparatus and device for state subscription notification

Abstract

The application provides a method, device and equipment for state subscription notification, the method comprising: a first network function (NF) triggering detection on a service flow according to policy information, the first NF being related to session management; the first NF notifying service flow initiation and termination to a second NF; and the second NF being related to access management. The scheme of the application avoids the process of the second NF accessing a session binding support function (BSF) and the first NF, and reduces signaling overhead.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method, apparatus, and device for status subscription notifications. Background Technology

[0002] Currently, considering the introduction of access management policies (AM Policies) for dynamic control of 5G networks, and the dynamic distribution of access technology / frequency selection priority parameters to achieve capacity management, enhanced coverage, etc., it is necessary to consider scenarios where AM policies are dynamically changed based on third-party or application detection.

[0003] Existing technical solutions require addressing the BSF (User Session Binding Function) responsible for session binding via user code, which leads to redundant BSF deployment. Furthermore, existing session binding BSFs are deployed at the visited location, either independently or jointly with the SMF (Session Management Function), serving different IP address ranges. For each PDU (Protocol Data Unit) session, they store session binding information such as user identifier, DNN (Content Management System), UE address (IP address or MAC address, etc.), and the address of the PCF (Policy Control Function) selected by the SMF. This ensures that when the AF (Access Controller) identifies the UE's service transmission policy based on the UE address, it provides a PCF address lookup service to the AF or NEF (Network Open Function), enabling the N5 / Rx interface to address the PCF corresponding to the UE's PDU session.

[0004] Using user-number-based session binding BSFs requires the BSF to register user number ranges with the NRF (NR Storage Function), and these user number ranges cannot be duplicated. This makes it unsuitable for BSFs deployed together with SMFs at the visited location. There is a need to deploy BSFs by user number range and synchronize session binding information from BSFs serving IP address ranges to those deployed by user number ranges. This introduces redundant BSF deployments and data consistency issues related to the real-time synchronization of large amounts of session binding information between visited and home locations, and between many-to-many BSFs.

[0005] Furthermore, AM PCF (Access Management Policy Control Function) discovers a large number of BSFs (BSFs) via NRF based on DNN and S-NSSAI (Network Slice Selection Auxiliary Information) when SMF / BSF are co-located (hundreds). The BSF profiles (documents) maintained by AM PCF and the subscription resource addresses for subscribing to BSFs are huge, but only one BSF can match the subscription, and other subscriptions and BSF processing are invalid. Summary of the Invention

[0006] The technical problem this invention aims to solve is how to provide a method for state subscription notifications. This avoids the processes of access management PCF to access BSF and session management PCF, reducing signaling overhead.

[0007] To solve the above-mentioned technical problems, the technical solution of the present invention is as follows:

[0008] A method for state subscription notifications includes:

[0009] The first network function (NF) triggers the detection of service flows based on policy information;

[0010] The first NF notifies the second NF of the start and end of the service flow.

[0011] Optionally, the first NF triggers detection of the service flow based on policy information, including:

[0012] The first NF subscribes to policy information from the Unified Data Warehouse Function UDR. After receiving the policy information from the UDR, it detects the service flow of the user's Protocol Data Unit (PDU) session.

[0013] Optionally, after a user's Protocol Data Unit (PDU) session is established, the first NF subscribes to policy information from the UDR. Upon receiving the policy information from the UDR, the first NF detects the service flow of the user's PDU session. Optionally, the first PCF triggers the detection of the service flow based on the policy information, including:

[0014] The first NF receives a subscription request sent by the second NF, the subscription request being used to establish a PDU session for the subscribing user;

[0015] The first NF obtains policy information based on the subscription request and detects the service flow of the user's Protocol Data Unit (PDU) session based on the policy information.

[0016] Optionally, the first NF triggers the detection of the service flow based on the policy information, including:

[0017] The first NF receives a second subscription request sent by the second NF, the second subscription request being used to subscribe to the business flow state;

[0018] Upon receiving the second subscription request, the first NF triggers an inspection of the business flow;

[0019] The second subscription request is sent after the second NF confirms the establishment of the user's PDU session.

[0020] Optionally, the user's PDU session establishment is confirmed when the second NF receives a notification of the establishment of the user's PDU session or when the second NF receives relevant information from the first NF;

[0021] The relevant information of the first NF includes at least one of the following: the identifier of the first NF, its address, and session binding information.

[0022] Optionally, the notification of the establishment of the user's PDU session received by the second NF is sent to either the first NF or the third NF.

[0023] Optionally, the second NF receives relevant information from the first NF and sends it to either the first NF or the third NF.

[0024] Optionally, the first NF triggers detection of the service flow based on policy information, including:

[0025] The first NF receives a first subscription request sent by the second NF, the first subscription request being used to establish a PDU session for the subscribing user;

[0026] Alternatively, the first NF receives a first indication sent by the second NF, the first indication being used to request or indicate that: the first NF notifies the second NF user of the PDU session establishment after the PDU session is established;

[0027] When a user's PDU session is established, the first NF notifies the second NF, which then sends a second subscription request to the first NF. The second subscription request is used to subscribe to the service flow status of the PDU session. The first NF then detects the service flow of the user's PDU session based on the second subscription request.

[0028] Optionally, the first subscription request or the first indication carries a DNN and / or slice identifier.

[0029] Optionally, the first subscription request carries information related to the second NF;

[0030] or

[0031] The first instruction carries information related to the second NF;

[0032] The relevant information of the second NF includes at least one of the following: the second NF identifier and the second NF address.

[0033] Optionally, the method further includes:

[0034] After the user's PDU session is established, the first NF subscribes to policy information from the UDR;

[0035] After the user's PDU session is established, the first NF notifies the second NF, including:

[0036] After receiving the policy information from the UDR notification, a notification message is sent to the second NF. The notification message is used to notify the second NF user of the establishment of a PDU session.

[0037] Optionally, after receiving the policy information from the UDR notification but before sending the notification message to the second NF, the method further includes:

[0038] Determine the second NF.

[0039] Optionally, determining the second NF includes:

[0040] The first NF queries the binding support function BSF with relevant information of the second NF based on the user's information or identifier to determine the second NF;

[0041] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0042] Optionally, determining the second NF includes:

[0043] The first NF obtains relevant information about the second NF from the UDR based on the user's information or identifier, and determines the second NF;

[0044] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0045] Optionally, determining the second NF includes:

[0046] The second NF is determined by receiving the relevant information of the second NF carried in the UDR notification policy information;

[0047] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0048] Optionally, if the notification of the establishment of a user's PDU session received by the second NF is sent by the third NF, then the notification of the establishment of the user's PDU session is that the second NF subscribes to the third NF.

[0049] Optionally, the first NF notifies the second NF of the start and end of the service flow, including:

[0050] The first NF queries the Session Binding Support Function (BSF) that has the second NF's information / identifier based on the user's information / identifier, and determines the second NF.

[0051] The first NF notifies the second NF of the start and end of the service flow.

[0052] Optionally, the first NF notifies the second NF of the start and end of the service flow, including:

[0053] The first NF queries the storage function NRF containing the second NF's information / identifier based on the user's information / identifier to determine the second NF;

[0054] The first NF notifies the second NF of the start and end of the service flow.

[0055] Optionally, the first NF notifies the second NF of the start and end of the service flow, including:

[0056] The first NF determines the second NF based on the subscription request of the second NF;

[0057] The first NF notifies the second NF of the start and end of the service flow.

[0058] Optionally, the first NF notifies the second NF of the start and end of the service flow, including:

[0059] The first NF determines the second NF based on the second subscription request;

[0060] The first NF notifies the second NF of the start and end of the service flow.

[0061] Optionally, all policy information for a preset application is created in batches by AF in UDR as application data, and the preset application is associated with a specified DNN and slice identifier;

[0062] The first NF subscribes to policy information from the UDR for all users of the preset application;

[0063] The service flow of the session of the application associated with the specified DNN and slice identifier is detected based on the policy information.

[0064] Optionally, all policy information for a preset application is created in batches by AF in UDR as application data, and the preset application is associated with a specified DNN and slice identifier;

[0065] The service flow status of the first PDU session is that the second NF subscribes to the first NF in batches according to the policy information, and the first NF detects the service flow of the session of the application associated with the specified DNN and slice identifier according to the policy information.

[0066] The policy information refers to the policy information that the second NF subscribes to from the UDR for all users of the preset application.

[0067] Optionally, both the first NF and the second NF are policy control functions (PCFs), with the first NF related to session management and the second NF related to access management.

[0068] Embodiments of the present invention also provide a method for status subscription notifications, comprising:

[0069] The second NF receives notifications from the first NF regarding the start and end of the service flow; the first NF triggers the detection of the service flow based on the policy information.

[0070] Optionally, the method further includes:

[0071] The second NF subscribes to the UDR's policy information;

[0072] After receiving the policy information from the UDR notification, the relevant information of the second NF is written into the UDR;

[0073] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0074] Optionally, the method further includes:

[0075] Send a subscription request to the first NF, the subscription request being used to establish a PDU session for the subscribing user.

[0076] Optionally, the method further includes:

[0077] After confirming the establishment of the user's PDU session, the second NF sends a second subscription request to the first NF. The second subscription request is used to subscribe to the service flow state.

[0078] Optionally, the user's PDU session establishment is confirmed when the second NF receives a notification of the establishment of the user's PDU session, or when the second NF receives the identifier, address, or session binding information of the first NF.

[0079] Optionally, the notification of the establishment of the user's PDU session received by the second NF is sent to either the first NF or the third NF.

[0080] Optionally, the second NF receives relevant information from the first NF and sends it to either the first NF or the third NF;

[0081] The relevant information of the first NF includes at least one of the following: the identifier of the first NF, its address, and session binding information.

[0082] Optionally, the method further includes:

[0083] The second NF sends a first subscription request to the first NF, the first subscription request being used to subscribe to the establishment of a PDU session for the user; or, the second NF sends a first indication to the first NF, the first indication being used to request or indicate that: the first NF notifies the second NF of the establishment of the user's PDU session after the PDU session is established;

[0084] The second NF receives the notification from the first NF regarding the establishment of the user's PDU session;

[0085] After receiving notification of the user's PDU session establishment, the second NF sends a second subscription request to the first NF.

[0086] Optionally, the first subscription request or the first indication carries a DNN and / or slice identifier.

[0087] Optionally, the first subscription request carries information related to the second NF;

[0088] or

[0089] The first instruction carries information related to the second NF;

[0090] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0091] Optionally, if the notification of user PDU session establishment received by the second NF is sent by the third NF, the method further includes:

[0092] The second NF sends a third subscription request to the third NF, the third subscription request being used to establish a PDU session for the subscribing user;

[0093] The second NF receives the notification from the third NF regarding the establishment of the user's PDU session.

[0094] Optionally, all policy information for a preset application is created in batches by AF in UDR as application data, and the preset application is associated with a specified DNN and slice identifier;

[0095] The second NF subscribes to policy information from the UDR for all users of the preset application;

[0096] The second NF subscribes to the service flow status of the PDU session in batches from the first NF based on the policy information.

[0097] Embodiments of the present invention also provide an apparatus for state subscription notification, applied to a first network function (NF), comprising:

[0098] The processing module is used to trigger the detection of business flows based on policy information;

[0099] The transceiver module is used to notify the second NF of the start and end of the service flow.

[0100] Embodiments of the present invention also provide a network function (NF), including the apparatus described above.

[0101] Embodiments of the present invention also provide an apparatus for state subscription notification, applied to a second network function (NF), comprising:

[0102] The transceiver module is used to receive service flow start and end notifications sent by the first NF; the first NF triggers the detection of the service flow according to the policy information.

[0103] Embodiments of the present invention also provide a network function (NF), including the apparatus as described above.

[0104] Embodiments of the present invention also provide a communication device, including: a processor and a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method described above.

[0105] Embodiments of the present invention also provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described above.

[0106] The above-described solution of the present invention has at least the following beneficial effects:

[0107] The first NF (Network Function) triggers the detection of service flows based on policy information. This first NF is related to session management. The first NF notifies the second NF (Network Function) of the start and end of the service flow. The second NF is related to access management. By using a session management-related network function NF to trigger the detection of service flows based on policy information, the process of access management-related network function NFs accessing session binding function BSF (Network Function Foundation) and related network function NFs is avoided, reducing signaling overhead. Attached Figure Description

[0108] Figure 1 This is a flowchart illustrating the application data status subscription method according to an embodiment of the present invention;

[0109] Figure 2 This is a schematic diagram of the method for implementing application data state subscription based on Session Management SM PCF according to an embodiment of the present invention;

[0110] Figure 3 This is another flowchart illustrating the method for application data state subscription based on Session Management SM PCF according to an embodiment of the present invention;

[0111] Figure 4 This is a flowchart of an AM PCF subscription in an embodiment of the present invention;

[0112] Figure 5 This is another flowchart illustrating the method for application data state subscription based on Session Management SM PCF according to an embodiment of the present invention;

[0113] Figure 6 This is a flowchart of AM PCF subscription twice according to an embodiment of the present invention;

[0114] Figure 7 This is a flowchart illustrating the process of sending a first instruction to the first NF in the second NF item according to an embodiment of the present invention.

[0115] Figure 8 This is a schematic diagram of the process by which the AMF sends a notification of the establishment of a user's PDU session to the second NF according to an embodiment of the present invention;

[0116] Figure 9 This is a schematic diagram of SM PCF de-UDR bulk subscription according to an embodiment of the present invention;

[0117] Figure 10 This is a schematic diagram of the AM PCF subscribing to the SM PCF twice in an embodiment of the present invention. The first step is a batch subscription process.

[0118] Figure 11 This is a block diagram of the application data status subscription device according to an embodiment of the present invention. Detailed Implementation

[0119] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0120] like Figure 1 As shown, an embodiment of the present invention provides a method for application data status subscription, comprising:

[0121] Step 11: The first NF (Network Function) triggers the detection of service flow based on policy information. The first NF is related to session management and can be a policy control function (PCF).

[0122] Step 12: The first NF notifies the second NF of the start and end of the service flow; the second NF is related to access management and may be a policy control function (PCF).

[0123] In this embodiment, the first policy control function (PCF) triggers the detection of service flows based on policy information. The first PCF is related to session management. The first PCF notifies the second PCF of the start and end of the service flows. The second PCF is related to access management. Here, the policy information can be user policy information, which includes access management policy influence information or access management influence information (AM influence information). By using the session management PCF to trigger the detection of service flows based on policy information, the process of the access management PCF accessing the session binding function (BSF) and the session management PCF is avoided, reducing signaling overhead.

[0124] In embodiments of the present invention, before the first NF notifies the second NF of the start and end of the service flow, the first NF determines the second NF, and the first NF notifies the determined second NF of the start and end of the service flow; the first NF can determine the second NF before triggering the detection of the service flow, or when triggering the detection of the service flow, or after triggering the detection of the service flow.

[0125] In an optional embodiment of the present invention, taking NF as an example, step 11 may include:

[0126] Step 111: The first PCF subscribes to policy information from the Unified Data Warehouse Function UDR. After receiving the policy information from the UDR, it detects the service flow of the user's Protocol Data Unit (PDU) session.

[0127] In this embodiment, after the user's Protocol Data Unit (PDU) session is established, the first PCF subscribes to policy information from the UDR. Upon receiving the policy information from the UDR, the first PCF detects the service flow of the user's PDU session. It should be noted that in this embodiment, the establishment of the user's PDU session can also be replaced by the establishment of a Session Management Policy Association (SMAC). That is, the first PCF detects the service flow of the user's PDU session after the SMAC is established.

[0128] Specifically, subscribing to policy information from the UDR includes:

[0129] Policy information is created when the UDR is accessed by the AF. After the first PCF receives the notification from the UDR, it generates subscription information for subscribing to the policy information. Here, the subscription information subscribes to the start / end of the user's Protocol Data Unit (PDU) session in the user plane application traffic and / or the address of the second PCF.

[0130] In an optional embodiment of the present invention, after the user's Protocol Data Unit (PDU) session is established, the first PCF subscribes to policy information from the UDR. After receiving the policy information notified by the UDR, the first PCF detects the service flow of the user's PDU session.

[0131] In an optional embodiment of the present invention, taking NF as an example, step 12 may include:

[0132] Step 121: The first PCF queries the Session Binding Support Function (BSF) with the second PCF's information / identifier based on the user's information / identifier, and determines the second PCF; the first PCF then notifies the second PCF of the start and end of the service flow. It should be noted that the second PCF determined in step 121 is the second PCF whose status the first PCF needs to notify of the start and end of the service flow.

[0133] In an optional embodiment of the present invention, step 12 may also include:

[0134] Step 122: The first PCF queries the storage function NRF of the second PCF's information / identifier / address based on the user's information / identifier to determine the second PCF; the first PCF then notifies the second PCF of the start and end of the service flow. It should be noted that the second PCF determined in step 122 is the second PCF whose start and end status the first PCF needs to notify the second PCF of.

[0135] The specific implementation process is as follows: Figure 2 As shown, it includes:

[0136] 1. The session management related PCF (SM PCF, i.e. the first PCF) subscribes to this policy information from the UDR after a user's session is established (this policy information is created / modified / deleted by AF, and this policy information is the access management AM policy impact request information).

[0137] 2. After the UDR is created by the AF, the session management PCF will receive a notification of the UDR (a user's AM policy impact request information is created).

[0138] 3. Upon receiving the notification, the SM PCF generates subscription information based on this notification. The subscription information relates to the start / stop of the PDU session subscribed to for this user in the user-plane application traffic. The subscription information also includes the address of the notifying party, i.e., the address of the AM PCF that manages the user's access.

[0139] 4. The address of the notification provider for subscription information can be obtained by querying the BSF or NRF through the SM PCF. The AM PCF registers a default notification address during service registration.

[0140] 5. The PCF initiates the detection of the service flow, or instructs the SMF to detect it, or subscribes to the start / stop status of the service flow.

[0141] 6. When an event related to subscription information (the user's PDU session in the user plane application data start / stop state) is detected, the SM PCF notifies the AM PCF according to the address of the notification party for the subscription information.

[0142] Another specific implementation process is as follows: Figure 3 As shown, it includes:

[0143] 1. The session management related PCF (SM PCF, i.e. the first PCF) subscribes to this policy information from the UDR after a user's session is established (this policy information is created / modified / deleted by AF, and this policy information is the access management AM policy impact request information).

[0144] 2. After the UDR is created by the AF, the session management PCF will receive a notification of the UDR (a user's AM policy impact request information is created).

[0145] 3. Upon receiving the notification, the PCF initiates the detection of the service flow, or instructs the SMF to perform the detection, or subscribes to the start / stop status of the service flow.

[0146] 4. Upon detecting an event related to subscription information (the user's PDU session's application data start / stop status on the user plane), the SM PCF determines the AM PCF and notifies it. The SM PCF can determine the AM PCF by querying the Session Binding Support Function (BSF) with second PCF information / identifier / address or by querying the NRF.

[0147] In an optional embodiment of the present invention, taking the NF as an example, step 11 above may include:

[0148] Step 112: The first PCF receives a subscription request sent by the second PCF. The subscription request is used to establish a PDU session for the subscribing user (or to establish a session management policy association (SM policy association)).

[0149] Step 113: The first PCF obtains policy information based on the subscription request, and detects the service flow of the user's Protocol Data Unit (PDU) session based on the policy information.

[0150] The policy information here includes DNN and slice information related to the PDU session.

[0151] Accordingly, step 12 above may include:

[0152] The first PCF determines the second PCF based on the subscription request of the second PCF; the first PCF notifies the second PCF of the start and end of the service flow.

[0153] The specific process is as follows Figure 4 As shown in Figure 1, the session management related PCF (SM PCF, i.e., the first PCF) subscribes to this policy information from the UDR after a user's session is established (this policy information is created / modified / deleted by the AF, and this policy information is the access management AM policy impact request information).

[0154] 2. After the UDR is created by the AF, the session management PCF will receive a notification of the UDR (a user's AM policy impact request information is created).

[0155] 3. The first PCF receives the subscription request sent by the second PCF.

[0156] 4. The first PCF obtains policy information based on the subscription request and detects the service flow of the user's Protocol Data Unit (PDU) session based on the policy information.

[0157] As an optional embodiment, step 11 includes:

[0158] The first NF receives a second subscription request sent by the second NF, the second subscription request being used to subscribe to the service flow status; upon receiving the second subscription request, the first NF triggers the detection of the service flow; wherein, the second subscription request is sent by the second NF after confirming that the user's PDU session has been established.

[0159] In this embodiment, upon confirming the establishment of a user's PDU session, the second NF sends a second subscription request to the first NF to subscribe to the service flow status. Upon receiving the second subscription request, the first NF triggers the detection of the service flow. Specifically, the second NF confirms the establishment of the user's PDU session upon receiving notification of the establishment of the user's PDU session, or upon receiving relevant information from the first NF. The relevant information of the first NF includes at least one of the following: the identifier of the first NF, its address, and session binding information.

[0160] It should be noted that, in this embodiment, the establishment of the user's PDU session can also be replaced by the establishment of a session management policy association. That is, the second NF sends a second subscription request to the first NF after confirming the establishment of the session management policy association. Specifically, the second NF confirms the establishment of the session management policy association upon receiving a notification of the establishment of the session management policy association, or upon receiving relevant information from the first NF.

[0161] It should be noted that the notification received by the second NF regarding the establishment of a user's PDU session (or the establishment of a session management policy association) can be sent by either the first NF or the third NF. Similarly, the second NF receiving relevant information from the first NF can be sent by either the first NF or the third NF. The third NF can be any NF other than the first or second NF, such as the Access and Mobility Management Function (AMF).

[0162] The specific implementation process is as follows: Figure 5 As shown, taking NF as an example of PCF, it includes:

[0163] 1. The session management related PCF (SM PCF, i.e. the first PCF) subscribes to this policy information from the UDR after a user's session is established (this policy information is created / modified / deleted by AF, and this policy information is the access management AM policy impact request information).

[0164] 2. When a user's PDU session is established, the AM PCF (i.e., the second PCF) receives the user's PDU session notification. This session notification can be sent by either the SM PCF or the AMF.

[0165] 3. After receiving the user's PDU session establishment notification, the AM PCF (i.e., the second PCF) subscribes to the SM PCF (the first PCF) for the application traffic status of the user's PDU session (i.e., sends the second subscription request);

[0166] 4. SM PCF (First PCF) performs application traffic detection.

[0167] 5. The SM PCF sends a notification to the AM PCF (notifying that the application traffic status of the user's PDU session has been detected).

[0168] It should be noted that, in this embodiment, the establishment of the user's PDU session can also be replaced by the establishment of a session management policy association, and the specific implementation process is the same as... Figure 5Similarly, this will not be repeated here. The following uses the sending of the user's PDU session establishment notification in the second NF of the first NF item as an example to illustrate the state subscription notification method of this embodiment of the invention.

[0169] In an optional embodiment of the present invention, taking NF as an example, step 11 above may include:

[0170] Step 114: The first NF receives a first subscription request sent by the second NF, that is, the second PCF sends a first subscription request to the first PCF, the first subscription request being used to subscribe to the user's PDU session establishment; or, the first NF receives a first indication sent by the second NF, the first indication being used to request or indicate that: the first NF notifies the second NF of the PDU session establishment after the PDU session is established.

[0171] Step 115: When a user's PDU session is established, the first PCF notifies the second PCF, which then sends a second subscription request to the first PCF. The second subscription request is used to subscribe to the service flow status of the PDU session. The first PCF detects the service flow of the user's PDU session according to the second subscription request.

[0172] In this embodiment, the second NF can send a first subscription request or a first indication to the first NF. The first subscription request is used to subscribe to the establishment of a PDU session from the first NF. The first indication is used to request or indicate to the first NF to notify the second NF user of the PDU session establishment after the PDU session is established.

[0173] Optionally, in this embodiment, the first subscription request can also be used to establish a subscription session management policy association; the first indication can also be used to request or indicate the first NF. exist The second NF is notified after the session management policy association is established. The first indication is either a PDU session-related indication or a session management policy association-related indication.

[0174] Optionally, the first subscription request or the first indication carries a DNN and / or slice identifier. That is, when the second NF sends the first subscription request, it carries a DNN and / or slice identifier for establishing a PDU session with the specified DNN and / or slice identifier of the user subscribing to the first NF. Alternatively, when the second NF sends the first indication, it carries a DNN and / or slice identifier for instructing or requesting the first NF to establish a PDU session with the specified DNN and / or slice identifier of the user.

[0175] It should be noted that the user's PDU session information will be obtained in the first NF when the PDU session is established or when the session management policy associated with the PDU session is established.

[0176] Accordingly, step 12 above may include:

[0177] The first PCF determines the second PCF based on the second subscription request; the first PCF notifies the second PCF of the start and end of the service flow.

[0178] The specific implementation process is as follows: Figure 6 As shown, taking NF as an example of PCF, it includes:

[0179] 1. The AM PCF (i.e., the second PCF) subscribes to the SM PCF (i.e., the first PCF) for PDU session information (which can be for a group of users corresponding to a DNN and a slice, or for all users). The trigger condition for the AM PCF to send a subscription request is receiving a notification from the UDR, informing the AF which users have created application data for a DNN and a slice—AM policy influence request information; that is, the second NF establishes a PDU session for the subscribed users from the first NF (which can also be replaced by the establishment of a subscription session management policy association).

[0180] 2. When a user's PDU session is established (or a session management policy association is established), the SM PCF (i.e., the first PCF) notifies the AM PCF (i.e., the second PCF) of the user's PDU session information.

[0181] 3. Upon receiving the notification, the AM PCF sends a request to the SM PCF regarding the start / stop status of application data in the user plane for a PDU session.

[0182] 4. SM PCF detection (Application traffic detection).

[0183] 5. The SM PCF (i.e., the first PCF) sends a notification to the AM PCF (i.e., the second PCF) (notifying that the application traffic status of the user's PDU session has been detected).

[0184] Optionally, the first subscription request carries information related to the second NF;

[0185] Alternatively, the first instruction may carry information related to the second NF;

[0186] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0187] In this embodiment, when the second NF sends a first subscription request or a first instruction to the first NF, the relevant information of the second NF can be carried in the first subscription request or the first instruction. Then the first NF can obtain the address, identifier, binding information, etc. of the second NF according to the first subscription request; or, the first NF can obtain the address, identifier, binding information, etc. of the second NF at the same time as obtaining the first instruction.

[0188] The specific implementation process is as follows: Figure 7 As shown, taking the first instruction sent by the second NF to the first NF as an example, where the NF is a PCF, it includes:

[0189] 0. During the AM policy association establishment or modification process, the AM PCF (i.e., the second PCF) carries an instruction to request or instruct the PCF for the PDU session (the first PCF) to send a notification to the PCF for the UE (the second PCF) after the PDU session is established.

[0190] 1. During the PDU session establishment process, the AMF->SMF and SMF->PCF messages carry indication information (i.e., the first indication) requesting the user's PDU session information, which is used to request or instruct the PCF for the PDU session (first PCF) to send a notification to the PCF for the UE (second PCF) after the PDU session is established.

[0191] 2. The first PCF sends a notification to the second PCF regarding PDU session information.

[0192] 3. After the second PCF confirms the establishment of the PDU session, it subscribes to the first PCF for the application traffic status of the user's PDU session.

[0193] 4. SM PCF detection (Application traffic detection).

[0194] 5. The SM PCF (i.e., the first PCF) sends a notification to the AM PCF (i.e., the second PCF) (notifying that the application traffic status of the user's PDU session has been detected).

[0195] It should be noted that in this embodiment, the establishment of a user's PDU session can also be replaced by the establishment of a session management policy association; that is, the establishment of a PDU session for a subscribing user can be replaced by the establishment of a session management policy association; sending a notification after the user's PDU session is established can be replaced by sending a notification after the session management policy association is established; and confirming the establishment of the PDU session can be replaced by confirming the establishment of the session management policy association. The specific implementation process is the same as... Figure 7 Similarly, this will not be elaborated upon here. Optionally, the method further includes:

[0196] After the user's PDU session is established (or the session management policy association is established), the first NF subscribes to policy information from the UDR;

[0197] After the user's PDU session is established (or the session management policy association is established), the first NF notifies the second NF, including:

[0198] After receiving the policy information from the UDR notification, a notification message is sent to the second NF. The notification message is used to notify the second NF user of the establishment of a PDU session (or the establishment of a session management policy association).

[0199] In this embodiment, after the first NF detects the establishment of a user's PDU session (or the establishment of a session management policy association), it can subscribe to policy information from the UDR. Since it has received the first subscription request sent by the second NF, it can notify the second NF of the establishment of the user's PDU session (or the establishment of a session management policy association) after receiving the policy information from the UDR.

[0200] In this embodiment, the first NF can be a first PCF, and the second NF can be a second PCF. Taking a PCF as an example, the first PCF subscribes to policy information from the UDR. After the PDU session is established, the first PCF subscribes to the policy information from the UDR. After receiving the policy information notified by the UDR, the first PCF sends a notification message to the second PCF that the user's PDU session has been established, notifying the second PCF that the PDU session has been established. After receiving the notification message, the second PCF sends a first request message to the first PCF. The first request message is used to subscribe to the service flow status. When the first PCF receives the first request message, it detects the service flow according to the first request message and feeds back the service flow status, i.e., the start and end of the service flow, to the second PCF.

[0201] It should be noted that the first NF can also send a request message to the UDR to request policy information. The UDR then returns the policy information to the first NF based on the request message (for example, if the first NF queries the second NF for policy information, it can directly obtain the query result returned by the second NF). After receiving the policy information, the first NF sends a notification message to the second NF indicating the establishment of the user's PDU session. After receiving the notification message, the second NF sends a request message to the first NF to subscribe to the service flow status. The first NF detects the service flow based on the request message and notifies the second NF of the start and end of the service flow. In this embodiment, the first NF sends a request message to the UDR to request policy information after the user's PDU session is established.

[0202] It should be noted that in this embodiment, the establishment of a user's PDU session can also be replaced by the establishment of a session management policy association. For example, the establishment of a PDU session for a subscribing user can be replaced by the establishment of a subscription session management policy association, and the confirmation of PDU session establishment can be replaced by the confirmation of a session management policy association. The specific implementation process will not be elaborated here.

[0203] Optionally, before the first NF sends a notification message to the second NF after receiving the policy information from the UDR notification, the method further includes: determining the second NF. In this embodiment, determining the second NF means: determining the second NF that the first NF needs to notify the user of the establishment of a PDU session (or the establishment of a session management policy association). After determining the second NF, the first NF sends a notification message to the second NF.

[0204] Specifically, determining the second NF can include, but is not limited to, the following methods:

[0205] Method 1: The first NF queries the Session Binding Support Function (BSF) with relevant information about the second NF based on the user's information or identifier to determine the second NF; wherein, the relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0206] In this method, the first NF can query the BSF based on user information or identifier. The BSF has relevant information about the second NF, thereby determining the second NF. The first NF then sends a notification message to the determined second NF to notify the establishment of the PDU (or the establishment of a session management policy association).

[0207] Method 2: The first NF obtains relevant information about the second NF from the UDR based on the user's information or identifier, and determines the second NF; wherein, the relevant information about the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0208] In this second method, the first NF can obtain relevant information about the second NF from the UDR based on the user's information or identifier, thereby determining the second NF. The first NF then sends a notification message to the determined second NF to notify the PDU to be established (or the session management policy association to be established).

[0209] Method 3: When receiving the UDR notification policy information, the relevant information of the second NF is carried to determine the second NF; wherein, the relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0210] In this third method, the first NF subscribes to policy information from the UDR and can receive policy information and related information of the second NF from the UDR. That is, when the UDR notifies the policy information, it carries the related information of the second NF.

[0211] As an optional embodiment, after the first NF detects the service flow, the first NF can determine the second NF based on the subscription request of the second NF. The subscription request of the second NF is a subscription request for the service flow status (i.e., the start and end of the service flow). In this embodiment, determining the second NF means determining the second NF that needs to send the service flow status. After determining the second NF, the first NF notifies the second NF of the start and end of the service flow.

[0212] The above is an example of the first NF sending a notification of user PDU session establishment (or session management policy association establishment) to the second NF. The following specific example illustrates how the third NF sends a notification of user PDU session establishment (or session management policy association establishment) to the second NF.

[0213] Optionally, if the notification of user PDU session establishment received by the second NF is sent by the third NF, the notification of user PDU session establishment (or session management policy association establishment) is a subscription from the second NF to the third NF. The third NF can be any NF other than the first NF and the second NF, such as an AMF.

[0214] Specifically, the implementation process is as follows: Figure 8 As shown, taking the AMF sending a notification to the second NF to establish a user's PDU session as an example, it includes:

[0215] 1. The AM PCF (i.e., the second PCF) subscribes to the AMF for PDU session information (the PDU session information of the subscribing user).

[0216] 2. When a user's PDU session is established, the AMF notifies the AM PCF (i.e., the second PCF) of the user's PDU session information.

[0217] 3. Upon receiving the notification, the AM PCF sends a request to the SM PCF for the start / stop status of the application data in the user plane for a PDU session (i.e., the application traffic status of the PDU session of the subscribed user).

[0218] 4. SM PCF detection (Application traffic detection).

[0219] 5. The SM PCF (i.e., the first PCF) sends a notification to the AM PCF (i.e., the second PCF) (notifying that the application traffic status of the user's PDU session has been detected).

[0220] It should be noted that in this embodiment, the establishment of the user's PDU session can also be replaced by the establishment of a session management policy association. For example, the establishment of a PDU session for a subscribing user can be replaced by the establishment of a subscription session management policy association, and the confirmation of PDU session establishment can be replaced by the confirmation of session management policy association establishment. The specific implementation process is the same as... Figure 8 Similarly, this will not be elaborated upon here. In an optional embodiment of the present invention, the first PCF subscribes to policy information from the UDR, including:

[0221] All policy information for a preset application is created in batches by AF in UDR as application data. The preset application is associated with a specified DNN and slice identifier.

[0222] The first NF subscribes to policy information from the UDR for all users of the preset application;

[0223] The service flow of the session of the application associated with the specified DNN and slice identifier is detected based on the policy information.

[0224] Policy information is created in batches by AF in UDR, the first PCF is for the session information of the pre-defined DNN and slices, and the batch subscription of the start / end status of the business flow of all users or the start / end status of the business flow.

[0225] The specific implementation process is as follows: Figure 9 As shown, it includes:

[0226] AF creates application data in batches within UDR (for all users / a group of users targeting a specific DNN and a specific slice).

[0227] 1. After enabling the AM policy (access policy) control function, the AM PCF subscribes to the SM PCF in batches for application data of all users in a specific DNN and a specific slice.

[0228] 2. AM PCF receives a notification from UDR and receives application data (application policy impact request) from a batch of users.

[0229] 3. AM PCF subscribes to SM PCF in batches for users' PDU session information and application data start / stop status subscriptions for specific DNNs and slices (two-in-one event subscription) or application data start / stop status subscriptions (which can be capability open services).

[0230] 4. Once a user establishes a PDU session for a specified DNN and slice, and the SM PCF detects the start / stop status of the application data on the user plane, the SM PCF sends a notification to the AM PCF (a notification is sent for each user and each PDU session for a specific slice and a specific PDU session).

[0231] The above embodiments of the present invention use Session Management PCF to subscribe to user policy information from UDR, avoiding the process of Access Management PCF accessing BSF and Session Management PCF, thus reducing signaling overhead.

[0232] In an optional embodiment of the present invention, all policy information for a preset application is created in batches by AF as application data in UDR, wherein the preset application is associated with a specified DNN and slice identifier.

[0233] Wherein, the policy information is the policy information that the second NF subscribes to from the UDR for all users of the preset application, that is, the second NF subscribes to the UDR for all users of the preset application.

[0234] The service flow status of the PDU session is that the second NF subscribes to the first NF in batches according to the policy information, that is, the second NF subscribes to the service flow status of the PDU session in batches according to the policy information, and the first NF detects the service flow of the session of the application associated with the specified DNN and slice identifier according to the policy information.

[0235] like Figure 10 As shown, the AM PCF (i.e., the second PCF) subscribes to the SM PCF (i.e., the first PCF) twice, the first time being a bulk subscription. This includes:

[0236] 1. Batch subscribe to UE application data for all users of slices and DNN;

[0237] 2. The second PCF receives application data from a batch of users;

[0238] 3. The second PCF, based on the application data information of batch users notified by the UDR, batch subscribes to the application traffic status of users' PDU sessions or the application traffic and PDU session information of PDU sessions;

[0239] 4. After the PDU session is established, the SM PCF (i.e., the first PCF) performs application traffic detection.

[0240] The SM PCF (i.e., the first PCF) sends a notification independently to the AM PCF (i.e., the second PCF) regarding the application traffic status of a user's PDU session.

[0241] It should be noted that in this embodiment, the establishment of the user's PDU session can also be replaced by the establishment of a session management policy association. For example, the establishment of a PDU session for a subscribing user can be replaced by the establishment of a subscription session management policy association, and the confirmation of PDU session establishment can be replaced by the confirmation of a session management policy association establishment. The specific implementation process is the same as... Figure 10 Similarly, I will not elaborate further here.

[0242] Embodiments of the present invention also provide a method for status subscription notifications, comprising:

[0243] The second network function (NF) receives service flow start and end notifications from the first NF; the second NF is related to access management; wherein, the first NF triggers service flow detection based on policy information, and the first NF is related to session management. Here, the NF can be a policy control function (PCF).

[0244] Optionally, the method further includes: the second NF subscribing to policy information from the UDR;

[0245] After receiving the policy information from the UDR notification, the relevant information of the second NF is written into the UDR; wherein, the relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0246] In this embodiment, the second NF subscribes to policy information from the UDR. After receiving the policy information from the UDR, it writes its own relevant information (i.e., the relevant information of the second NF) into the UDR. The relevant information includes at least one of an identifier, an address, and information. When the second NF writes its relevant information into the UDR, the relevant information of the second NF (at least one of the identifier, address, and information) needs to be associated with the user's information / identifier. The identifier / address / information of the second NF can be written into the UDR's policy information or application data.

[0247] Optionally, the method further includes:

[0248] Send a subscription request to the first NF, the subscription request being used to establish a PDU session for the subscribing user.

[0249] Optionally, the method further includes:

[0250] After confirming the establishment of the user's PDU session, the second NF sends a second subscription request to the first NF. The second subscription request is used to subscribe to the service flow state.

[0251] Optionally, the user's PDU session establishment is confirmed when the second NF receives a notification of the establishment of the user's PDU session, or when the second NF receives the identifier, address, or session binding information of the first NF.

[0252] Optionally, the notification of the establishment of the user's PDU session received by the second NF is sent to either the first NF or the third NF.

[0253] Optionally, the second NF receives relevant information from the first NF and sends it to either the first NF or the third NF;

[0254] The relevant information of the first NF includes at least one of the following: the identifier of the first NF, its address, and session binding information.

[0255] Optionally, the method further includes:

[0256] The second NF sends a first subscription request to the first NF, the first subscription request being used to subscribe to the establishment of a PDU session for the user; or, the second NF sends a first indication to the first NF, the first indication being used to request or indicate that: the first NF notifies the second NF of the establishment of the user's PDU session after the PDU session is established;

[0257] The second NF receives the notification from the first NF regarding the establishment of the user's PDU session;

[0258] After receiving notification of the user's PDU session establishment, the second NF sends a second subscription request to the first NF.

[0259] Optionally, the first subscription request or the first indication carries a DNN and / or slice identifier.

[0260] Optionally, the first subscription request carries information related to the second NF;

[0261] or

[0262] The first instruction carries information related to the second NF;

[0263] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0264] Optionally, if the notification of user PDU session establishment received by the second NF is sent by the third NF, the method further includes:

[0265] The second NF sends a third subscription request to the third NF, the third subscription request being used to subscribe to the user's PDU session;

[0266] The second NF receives the notification from the third NF regarding the establishment of the user's PDU session.

[0267] Optionally, all policy information for a preset application is created in batches by AF in UDR as application data, and the preset application is associated with a specified DNN and slice identifier;

[0268] The second NF subscribes to policy information from the UDR for all users of the preset application;

[0269] The second NF subscribes to the service flow status of the PDU session in batches from the first NF based on the policy information.

[0270] It should be noted that, in the embodiments of the present invention, the establishment of the user's PDU session can also be replaced by the establishment of a session management policy association. For example, the establishment of a PDU session for a subscribing user can be replaced by the establishment of a subscription session management policy association, and the confirmation of PDU session establishment can be replaced by the confirmation of a session management policy association establishment. The specific implementation process will not be elaborated here.

[0271] It should be noted that the above Figures 1 to 10 All methods described herein are applicable to embodiments of this method and can achieve the same technical effect.

[0272] like Figure 11 As shown, embodiments of the present invention also provide a state subscription notification apparatus 110, applied to a first network function NF, comprising:

[0273] Processing module 111 is used to trigger the detection of business flow based on policy information;

[0274] The transceiver module 112 is used to notify the second NF of the start and end of the service flow; the second NF is related to access management.

[0275] Optionally, the first NF triggers detection of the service flow based on policy information, including:

[0276] The first NF subscribes to policy information from the Unified Data Warehouse Function UDR. After receiving the policy information from the UDR, it detects the service flow of the user's Protocol Data Unit (PDU) session.

[0277] Optionally, after the user's Protocol Data Unit (PDU) session is established, the first NF subscribes to policy information from the UDR. After receiving the policy information from the UDR, the first NF detects the service flow of the user's PDU session.

[0278] Optionally, the first NF triggers detection of the service flow based on policy information, including:

[0279] The first NF receives a subscription request sent by the second NF, the subscription request being used to establish a PDU session for the subscribing user;

[0280] The first NF obtains policy information based on the subscription request and detects the service flow of the user's Protocol Data Unit (PDU) session based on the policy information.

[0281] Optionally, the first NF triggers the detection of the service flow based on the policy information, including:

[0282] The first NF receives a second subscription request sent by the second NF, the second subscription request being used to subscribe to the business flow state;

[0283] Upon receiving the second subscription request, the first NF triggers an inspection of the business flow;

[0284] The second subscription request is sent after the second NF confirms the establishment of the user's PDU session.

[0285] Optionally, the user's PDU session establishment is confirmed when the second NF receives a notification of the establishment of the user's PDU session or when the second NF receives relevant information from the first NF;

[0286] The relevant information of the first NF includes at least one of the following: the identifier of the first NF, its address, and session binding information.

[0287] Optionally, the notification of the establishment of the user's PDU session received by the second NF is sent to either the first NF or the third NF.

[0288] Optionally, the second NF receives relevant information from the first NF and sends it to either the first NF or the third NF.

[0289] Optionally, the first NF triggers detection of the service flow based on policy information, including:

[0290] The first NF receives a first subscription request sent by the second NF, the first subscription request being used to establish a PDU session for the subscribing user;

[0291] Alternatively, the first NF receives a first indication sent by the second NF, the first indication being used to request or indicate that: the first NF notifies the second NF user of the PDU session establishment after the PDU session is established;

[0292] When a user's PDU session is established, the first NF notifies the second NF, which then sends a second subscription request to the first NF. The second subscription request is used to subscribe to the service flow status of the PDU session. The first NF then detects the service flow of the user's PDU session based on the second subscription request.

[0293] Optionally, the first subscription request or the first indication carries a DNN and / or slice identifier.

[0294] Optionally, the first subscription request carries information related to the second NF;

[0295] or

[0296] The first instruction carries information related to the second NF;

[0297] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0298] Optionally, the method further includes:

[0299] After the user's PDU session is established, the first NF subscribes to policy information from the UDR;

[0300] After the user's PDU session is established, the first NF notifies the second NF, including:

[0301] After receiving the policy information from the UDR notification, a notification message is sent to the second NF. The notification message is used to notify the second NF user of the establishment of a PDU session.

[0302] Optionally, after receiving the policy information from the UDR notification but before sending the notification message to the second NF, the method further includes:

[0303] Determine the second NF.

[0304] Optionally, determining the second NF includes:

[0305] The first NF queries the binding support function BSF with relevant information of the second NF based on the user's information or identifier to determine the second NF;

[0306] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0307] Optionally, determining the second NF includes:

[0308] The first NF obtains relevant information about the second NF from the UDR based on the user's information or identifier, and determines the second NF;

[0309] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0310] Optionally, determining the second NF includes:

[0311] The second NF is determined by receiving the relevant information of the second NF carried in the UDR notification policy information;

[0312] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0313] Optionally, if the notification of the establishment of a user's PDU session received by the second NF is sent by the third NF, then the notification of the establishment of the user's PDU session is that the second NF subscribes to the third NF.

[0314] Optionally, the first NF notifies the second NF of the start and end of the service flow, including:

[0315] The first NF queries the Session Binding Support Function (BSF) that stores the second NF's information / identifier based on the user's information / identifier, and determines the second NF.

[0316] The first NF notifies the second NF of the start and end of the service flow.

[0317] Optionally, the first NF notifies the second NF of the start and end of the service flow, including:

[0318] The first NF queries the storage function NRF that stores the information / identifier / address of the second NF based on the user's information / identifier, and determines the second NF;

[0319] The first NF notifies the second NF of the start and end of the service flow.

[0320] Optionally, the first NF notifies the second NF of the start and end of the service flow, including:

[0321] The first NF determines the second NF based on the subscription request of the second NF;

[0322] The first NF notifies the second NF of the start and end of the service flow.

[0323] Optionally, the first NF notifies the second NF of the start and end of the service flow, including:

[0324] The first NF determines the second NF based on the second subscription request;

[0325] The first NF notifies the second NF of the start and end of the service flow.

[0326] Optionally, all policy information for a preset application is created in batches by AF in UDR as application data, and the preset application is associated with a specified DNN and slice identifier;

[0327] The first NF subscribes to policy information from the UDR for all users of the preset application;

[0328] The service flow of the session of the application associated with the specified DNN and slice identifier is detected based on the policy information.

[0329] Optionally, all policy information for a preset application is created in batches by AF in UDR as application data, and the preset application is associated with a specified DNN and slice identifier;

[0330] The service flow status of the PDU session is that the second NF subscribes to the first NF in batches according to the policy information, and the first NF detects the service flow of the session of the application associated with the specified DNN and slice identifier according to the policy information.

[0331] The policy information refers to the policy information that the second NF subscribes to from the UDR for all users of the preset application.

[0332] Optionally, both the first NF and the second NF are policy control functions (PCFs), with the first NF related to session management and the second NF related to access management.

[0333] It should be noted that this device is the same as the method described above, and all implementations of the method described above are applicable to the embodiments of this device and can achieve the same technical effect.

[0334] Embodiments of the present invention also provide a network function (NF), including the apparatus described above.

[0335] Embodiments of the present invention also provide an apparatus for state subscription notification, applied to a second network function (NF), comprising:

[0336] The transceiver module is used to receive service flow start and end notifications sent by the first NF; the second NF is related to access management; wherein, the first NF triggers the detection of the service flow according to policy information, and the first NF is related to session management.

[0337] Optionally, the device further includes:

[0338] The subscription module is used by the second NF to subscribe to the UDR for policy information;

[0339] The information writing module is used to write the relevant information of the second NF into the UDR after receiving the policy information from the UDR notification;

[0340] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0341] Optionally, the device further includes:

[0342] The first sending module is used to send a subscription request to the first NF, the subscription request being used to establish a PDU session for the subscribing user.

[0343] Optionally, the device further includes:

[0344] The second sending module is used to send a second subscription request to the first NF after confirming the establishment of the user's PDU session. The second subscription request is used to subscribe to the service flow status.

[0345] Optionally, the user's PDU session establishment is confirmed when the second NF receives a notification of the establishment of the user's PDU session, or when the second NF receives the identifier, address, or session binding information of the first NF.

[0346] Optionally, the notification of the establishment of the user's PDU session received by the second NF is sent to either the first NF or the third NF.

[0347] Optionally, the second NF receives relevant information from the first NF and sends it to either the first NF or the third NF;

[0348] The relevant information of the first NF includes at least one of the following: the identifier of the first NF, its address, and session binding information.

[0349] Optionally, the device further includes:

[0350] The third sending module is used to send a first subscription request to the first NF, the first subscription request being used to subscribe for the establishment of a PDU session for the user; or, the second NF sends a first indication to the first NF, the first indication being used to request or indicate that the first NF notifies the second NF of the establishment of the user's PDU session after the PDU session is established;

[0351] The first receiving module is used to receive the notification of PDU session establishment of the user sent by the first NF;

[0352] The fourth sending module is used to send a second subscription request to the first NF after receiving the user's PDU session establishment notification.

[0353] Optionally, the first subscription request or the first indication carries a DNN and / or slice identifier.

[0354] Optionally, the first subscription request carries information related to the second NF;

[0355] or

[0356] The first instruction carries information related to the second NF;

[0357] The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

[0358] Optionally, if the notification of user PDU session establishment received by the second NF is sent by the third NF, the apparatus further includes:

[0359] The fifth sending module is used to send a third subscription request to the third NF, the third subscription request being used to subscribe to the user's PDU session;

[0360] The second receiving module is used to receive the notification of user PDU session establishment sent by the third NF.

[0361] Optionally, all policy information for a preset application is created in batches by AF in UDR as application data, and the preset application is associated with a specified DNN and slice identifier;

[0362] The second NF subscribes to policy information from the UDR for all users of the preset application;

[0363] The second NF subscribes to the service flow status of the PDU session in batches from the first NF based on the policy information.

[0364] It should be noted that this device is the same as the method described above, and all implementations of the method described above are applicable to the embodiments of this device and can achieve the same technical effect.

[0365] It should be noted that, in the embodiments of the present invention, the subscription to a user's PDU session can be initiated simultaneously with the release and modification of the PDU session. The notification can be sent after the user's PDU session is established, and it can also be sent after the user's PDU session is released and modified.

[0366] Subscribing users can subscribe to the release and modification of SM policy associations at the same time as establishing them. They can also instruct the sending of notifications after the SM policy association is established, released, or modified.

[0367] In the above embodiments of the present invention, both the user's AM PCF (Network Functions Related to Access Management, NF) and SM PCF (Network Functions Related to Session Management, NF) can access the UDR. The information subscribed by the AM PCF to the SM PCF comes from the AM policy influence request information (which belongs to application data stored in the UDR and is created / modified by the AF from the UDR) subscribed by the AM PCF to the UDR. The SM PCF can also subscribe to the AM policy influence request information from the UDR. After receiving the notification from the UDR, an implicit subscription from AM PCF to SM PCF is generated. The SM PCF sends a notification of PDU session establishment to the AM PCF, and then the AM PCF subscribes to the service flow status from the SM PCF. When the status of the application data flow is detected, the SM PCF sends a notification to the AM PCF. The notification address of the AM PCF can be a default notification address, which is registered by the AM PCF with the NRF and obtained by the SM PCF through NRF discovery; or the SM PCF can subscribe to the UDR (subscribe to the AM PCF subscription event). In addition, users' AM PCF (Network Functions Related to Access Management) and SM PCF (Network Functions Related to Session Management) can directly exchange PCF binding information or subscribe to PDU session establishment or instruct the SM PCF to send a notification after the PDU session is established.

[0368] By generating implicit subscriptions after subscribing to UDR policy data through SM PCF, or by avoiding the process of Access Management PCF accessing BSF and Session Management PCF through interaction between AM PCF and SM PCF, signaling overhead is reduced.

[0369] Embodiments of the present invention also provide a communication device, including: a processor and a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0370] Embodiments of the present invention also provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0371] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0372] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0373] In the embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0374] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0375] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0376] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0377] Furthermore, it should be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of the present invention. Moreover, the steps performing the above-described series of processes can naturally be executed in the order described, but are not necessarily required to be executed in chronological order; some steps can be executed in parallel or independently of each other. Those skilled in the art will understand that all or any step or component of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or a combination thereof. This is something that those skilled in the art can achieve by using their basic programming skills after reading the description of the present invention.

[0378] Therefore, the object of the present invention can also be achieved by running a program or a set of programs on any computing device. The computing device can be a known general-purpose device. Therefore, the object of the present invention can also be achieved simply by providing a program product containing program code implementing the method or apparatus. That is, such a program product also constitutes the present invention, and the storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium can be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent to the present invention. Furthermore, the steps performing the above series of processes can naturally be performed in the order described, but are not necessarily required to be performed in chronological order. Some steps can be performed in parallel or independently of each other.

[0379] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method of state subscription notification, the method comprising: include: The first network function (NF) determines the second NF and triggers the detection of service flows based on the policy information; wherein, the first NF is a policy control function (PCF), the first NF is related to session management, and the policy information is policy information related to access management; The first NF notifies the second NF of the start and end of the service flow; wherein, the second NF is a PCF, and the second NF is related to access management; Wherein, the first network function (NF) determines the second NF and triggers the detection of service flows according to policy information, including: After the user's Protocol Data Unit (PDU) session is established, or after the session management policy association is established, the first NF subscribes to policy information from the UDR. Upon receiving the policy information notified by the UDR, it queries the User Session Binding Function (BSF) to obtain relevant information about the second NF, queries the Network Storage Function (NRF) to obtain relevant information about the second NF, obtains relevant information about the second NF from the UDR, or obtains relevant information about the second NF from the policy information notified by the UDR. Based on the queried relevant information about the second NF, it determines the second NF and detects the service flow of the user's PDU session; or... The first NF receives a first subscription request sent by the second NF; the first subscription request is used to subscribe to the establishment of a user's PDU session; or, the first subscription request is used to subscribe to the establishment of a session management policy association; or, the first subscription request is used to subscribe to the establishment and release of a user's PDU session; or, the first subscription request is used to subscribe to the establishment and termination of a session management policy association; wherein, the first subscription request carries relevant information of the second NF, and the first NF determines the second NF based on the relevant information of the second NF; After a user's PDU session is established or a session management policy association is established, the first NF notifies the second NF, which then sends a second subscription request to the first NF. The second subscription request is used to subscribe to the service flow status of the PDU session. The first NF detects the service flow of the user's PDU session according to the second subscription request. or, The first NF receives a first indication sent by the second NF; the first indication is used to instruct the first NF to notify the second NF of the establishment of a user's PDU session; or, the first indication is used to instruct the first NF to notify the second NF of the establishment of a session management policy association; or, the first indication is used to instruct the first NF to notify the second NF of the establishment and release of a user's PDU session; or, the first indication is used to instruct the first NF to notify the second NF of the establishment and termination of a session management policy association; wherein, the first NF obtains relevant information about the second NF from the message carrying the first indication received by the first NF, and determines the second NF; After a user's PDU session is established or a session management policy association is established, the first NF notifies the second NF, which then sends a second subscription request to the first NF. The second subscription request is used to subscribe to the service flow status of the PDU session, and the first NF detects the service flow of the user's PDU session according to the second subscription request.

2. The method of state subscription notification of claim 1, wherein, The first NF triggers the detection of the business flow based on the policy information, including: The first NF obtains policy information based on the subscription request and detects the service flow of the user's Protocol Data Unit (PDU) session based on the policy information.

3. The method of state subscription notification of claim 1, wherein, When the second NF receives a notification of the establishment of the user's PDU session, or when the second NF receives relevant information from the first NF, the user's PDU session is confirmed to be established. The relevant information of the first NF includes at least one of the following: the identifier of the first NF, its address, and session binding information.

4. The method of state subscription notification of claim 3, wherein, The notification of the user's PDU session establishment received by the second NF is sent to either the first NF or the third NF.

5. The method of state subscription notification of claim 3, wherein, The second NF receives relevant information from the first NF and sends it to either the first NF or the third NF.

6. The method of state subscription notification of claim 1, wherein, The first subscription request or the first indication carries a DNN and / or slice identifier.

7. The method for status subscription notification according to claim 1, characterized in that, The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

8. The method of state subscription notification of claim 1, wherein, The method further includes: After receiving the policy information from the UDR notification, a notification message is sent to the second NF. The notification message is used to notify the second NF user of the establishment of a PDU session.

9. The method of state subscription notification of claim 4, wherein, If the notification of a user's PDU session establishment received by the second NF is sent by the third NF, then the notification of the user's PDU session establishment is that the second NF subscribes to the third NF.

10. The method for status subscription notification according to claim 1, characterized in that, All policy information for a preset application is created in batches by AF as application data in UDR. The preset application is used to specify the association between DNN and slice identifier. The first NF subscribes to policy information from the UDR for all users of the preset application; The service flow of the session of the application associated with the specified DNN and slice identifier is detected based on the policy information.

11. The method for status subscription notification according to claim 1, characterized in that, All policy information for a preset application is created in batches by AF as application data in UDR. The preset application is used to specify the association between DNN and slice identifier. The service flow status of the PDU session is that the second NF subscribes to the first NF in batches according to the policy information, and the first NF detects the service flow of the session of the application associated with the specified DNN and slice identifier according to the policy information. The policy information refers to the policy information that the second NF subscribes to from the UDR for all users of the preset application.

12. A method of state subscription notification, the method comprising: include: The second NF receives service flow start and end notifications sent by the first NF; wherein, both the first NF and the second NF are policy control functions (PCFs), the first NF is related to session management, and the second NF is related to access management; Before the second NF receives the service flow start and end notifications sent by the first NF, it includes: The second NF sends a first subscription request to the first NF; the first subscription request is used to subscribe to the establishment of a user's PDU session; or, the first subscription request is used to subscribe to the establishment of a session management policy association; or, the first subscription request is used to subscribe to the establishment and release of a user's PDU session; or, the first subscription request is used to subscribe to the establishment and termination of a session management policy association; wherein, the first subscription request carries relevant information of the second NF; or, The second NF sends a first instruction to the first NF; the first instruction is used to instruct the first NF to notify the second NF of the establishment of the user's PDU session; or, the first instruction is used to instruct the first NF to notify the second NF of the establishment of the session management policy association; or, the first instruction is used to instruct the first NF to notify the second NF of the establishment and release of the user's PDU session; or, the first instruction is used to instruct the first NF to notify the second NF of the establishment and termination of the session management policy association. The method further includes: the second NF receiving a notification from the first NF that a user's PDU session has been established; and the second NF sending a second subscription request to the first NF after receiving the notification, the second subscription request being used to subscribe to the service flow status.

13. The method of state subscription notification of claim 12, wherein, The method further includes: The second NF subscribes to the UDR's policy information; After receiving the policy information from the UDR notification, the relevant information of the second NF is written into the UDR; The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

14. The method for status subscription notification according to claim 12, characterized in that, When the second NF receives a notification of the establishment of the user's PDU session, or when the second NF receives the identifier, address, or session binding information of the first NF, it confirms the establishment of the user's PDU session.

15. The method of state subscription notification of claim 14, wherein, The notification of the user's PDU session establishment received by the second NF is sent to either the first NF or the third NF.

16. The method of state subscription notification of claim 14, wherein, The second NF receives relevant information from the first NF and sends it to either the first NF or the third NF; The relevant information of the first NF includes at least one of the following: the identifier of the first NF, its address, and session binding information.

17. The method of state subscription notification of claim 12, wherein, The first subscription request or the first indication carries a DNN and / or slice identifier.

18. The method of state subscription notification of claim 12, wherein, The relevant information of the second NF includes at least one of the following: second NF information, second NF identifier, and second NF address.

19. The method of state subscription notification of claim 15, wherein, When the notification of user PDU session establishment received by the second NF is sent by the third NF, the method further includes: The second NF sends a third subscription request to the third NF, the third subscription request being used to establish a PDU session for the subscribing user; The second NF receives the notification from the third NF regarding the establishment of the user's PDU session.

20. The method for status subscription notification according to claim 12, characterized in that, All policy information for a preset application is created in batches by AF as application data in UDR. The preset application is used to specify the association between DNN and slice identifier. The second NF subscribes to policy information from the UDR for all users of the preset application; The second NF subscribes to the service flow status of the PDU session in batches from the first NF based on the policy information.

21. An apparatus for status subscription notifications, characterized in that, Applied to the first network function (NF), including: The processing module is used to determine the second NF and trigger the detection of the service flow according to the policy information; wherein, the first NF is the policy control function PCF, the first NF is related to session management, and the policy information is policy information related to access management; The transceiver module is used to notify the second NF of the start and end of the service flow; wherein, the second NF is the PCF, and the second NF is related to access management; The processing module is further configured to: after the user's Protocol Data Unit (PDU) session is established, or after the session management policy association is established, query the user session binding function (BSF) to obtain relevant information of the second NF, query the network storage function (NRF) to obtain relevant information of the second NF, obtain relevant information of the second NF from the UDR, or obtain relevant information of the second NF from the UDR notification policy information, determine the second NF based on the queried relevant information of the second NF, subscribe to policy information from the UDR, and after receiving the UDR notification policy information, detect the service flow of the user's PDU session; or, The processing module is further configured to: The first subscription request is received from the second NF; the first subscription request is used to subscribe to the establishment of a user's PDU session; or, the first subscription request is used to subscribe to the establishment of a session management policy association; or, the first subscription request is used to subscribe to the establishment and release of a user's PDU session; or, the first subscription request is used to subscribe to the establishment and termination of a session management policy association; wherein, the first subscription request carries relevant information of the second NF, and the processing module determines the second NF based on the relevant information of the second NF; After a user's PDU session is established or a session management policy association is established, the second NF is notified, and the second NF sends a second subscription request to the first NF. The second subscription request is used to subscribe to the service flow status of the PDU session, and the service flow of the user's PDU session is detected according to the second subscription request. or, The processing module is further configured to: Receive a first indication sent by the second NF; the first indication is used to instruct the first NF to notify the second NF of the establishment of the user's PDU session; or, the first indication is used to instruct the first NF to notify the second NF of the establishment of a session management policy association; or, the first indication is used to instruct the first NF to notify the second NF of the establishment and release of the user's PDU session; or, the first indication is used to instruct the first NF to notify the second NF of the establishment and termination of a session management policy association; obtain relevant information about the second NF from the message carrying the first indication received by the first NF, and determine the second NF; After a user's PDU session is established or a session management policy association is established, the second NF is notified, and the second NF sends a second subscription request to the first NF. The second subscription request is used to subscribe to the service flow status of the PDU session, and the first NF detects the service flow of the user's PDU session according to the second subscription request.

22. A network function (NF), characterized in that, Includes the apparatus as described in claim 21.

23. An apparatus for status subscription notifications, characterized in that, Applied to the second network function (NF), including: The transceiver module is used to receive service flow start and end notifications sent by the first NF; wherein, both the first NF and the second NF are policy control functions (PCFs), the first NF is related to session management, and the second NF is related to access management; The transceiver module is also used for: Send a first subscription request to the first NF; the first subscription request is used to subscribe to the establishment of a user's PDU session; or, the first subscription request is used to subscribe to the establishment of a session management policy association; or, the first subscription request is used to subscribe to the establishment and release of a user's PDU session; or, the first subscription request is used to subscribe to the establishment and termination of a session management policy association; wherein, the first subscription request carries relevant information of the second NF; or, Send a first instruction to the first NF; the first instruction is used to instruct the first NF to notify the second NF of the establishment of the user's PDU session; or, the first instruction is used to instruct the first NF to notify the second NF of the establishment of the session management policy association; or, the first instruction is used to instruct the first NF to notify the second NF of the establishment and release of the user's PDU session; or, the first instruction is used to instruct the first NF to notify the second NF of the establishment and termination of the session management policy association. The transceiver module is further configured to: after confirming the establishment of the user's PDU session, send a second subscription request to the first NF, the second subscription request being used to subscribe to the service flow state.

24. A network function (NF), characterized in that, Includes the apparatus as described in claim 23.

25. A communication device, characterized in that, include: A processor, a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method as described in any one of claims 1 to 20.

26. A computer-readable storage medium, characterized in that, A storage instruction that, when executed on a computer, causes the computer to perform the method as described in any one of claims 1 to 20.

Images