Event subscription notification
By providing event-exposed subscription policy control requests and PCC rule updates in 5G radio systems, the subscription and processing complexity of downlink data delivery status under high-latency communication is solved, and the efficiency and latency performance of the network is improved.
Patent Information
- Application Number
- CN202080058159.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-06-18
- Filing Date
- 2020-06-17
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2040-06-17
AI Technical Summary
In the high-latency communication scenarios, the application complexity and notification mechanism of the existing 5G radio system and the incomplete application of policy and billing control (PCC) rules have led to defects in subscription and processing of downlink data delivery status, which affects the network. efficiency and delay performance.
Ensure accurate subscription and processing of downlink data delivery status, including at SMF and UPF, by providing event-exposed subscription policy control request triggering between network entities and installing or updating PCC rules based on received notification information, ensuring accurate subscription and processing of downlink data delivery status, including at SMF and UPF Notification mechanism for buffering and discarding packets.
It improves the detection and processing capabilities of downlink data delivery status, supports PCC's optionality and flexibility, optimizes the network's support for high-latency communication, and improves the network's efficiency and delay performance.
Smart Images

Figure CN114270886B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 863,049, filed on June 18, 2019. The contents of that prior-filed application are incorporated herein by reference in their entirety. Technical Field
[0003] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology or other communication systems. For example, certain embodiments may relate to systems and / or methods for event subscription notifications in such communication systems. Background Art
[0004] Examples of mobile or wireless telecommunication systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), Advanced LTE (LTE-A), MulteFire, LTE-A Pro and / or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to next generation (NG) radio systems and network architectures. 5G is primarily built on new radio (NR), but 5G (or NG) networks may also be built on E-UTRA radio. It is estimated that NR provides bit rates of 10-20Gbit / s or higher, and can support at least enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC). NR is expected to deliver ultra-wideband and ultra-robust, low latency connectivity and large-scale networking to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more and more common, the demand for networks that meet the requirements of low power consumption, low data rates and long battery life will increase. It is worth noting that in 5G, a node that can provide radio access functionality to user equipment (i.e., similar to Node B in UTRAN or eNB in LTE) can be named gNB when established on NR radio, and can be named NG-eNB when established on E-UTRA radio. Summary of the invention
[0005] One embodiment may relate to a method comprising: providing a policy control request trigger regarding a subscription for event exposure from a first network entity to a second network entity, receiving a notification regarding the policy control request trigger from the second network entity; and installing or updating at least one policy and charging control (PCC) rule based on information received in the notification from the second network entity.
[0006] Another embodiment relates to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured with the at least one processor to cause the apparatus to at least: provide a policy control request trigger for a subscription for event exposure to a second network entity; receive a notification about the policy control request trigger from the second network entity; and install or update at least one policy and charging control (PCC) rule based on information received in the notification from the second network entity.
[0007] Another embodiment relates to an apparatus which may include: a component for providing a policy control request trigger regarding a subscription for event exposure to a second network entity, a component for receiving a notification regarding the policy control request trigger from the second network entity, and a component for installing or updating at least one policy and charging control (PCC) rule based on information received in the notification from the second network entity.
[0008] Another embodiment relates to a method at a first network entity, which may include: receiving a new policy control request trigger regarding a subscription for event exposure from a second network entity, receiving a subscription request for notifications regarding one or several events from a third network entity, and providing notifications regarding the subscription to the second network entity.
[0009] Another embodiment relates to an apparatus, the apparatus comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code can be configured with the at least one processor to cause the apparatus to at least: receive a new policy control request trigger for a subscription for event exposure from a second network entity, receive a subscription request for notifications about one or several events from a third network entity, and provide notifications about the subscription to the second network entity.
[0010] Another embodiment relates to an apparatus comprising components for receiving a new policy control request trigger regarding a subscription for event exposure from a second network entity, receiving a subscription request for notifications regarding one or several events from a third network entity, and providing notifications regarding the subscription to the second network entity. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:
[0012] Figure 1 illustrates an example signaling diagram according to an embodiment;
[0013] Figure 2 illustrates an example signaling diagram according to an embodiment;
[0014] Figure 3 illustrates an example signaling diagram according to an embodiment;
[0015] Figure 4a An example flow chart of a method according to one embodiment is shown;
[0016] Figure 4b illustrates an example flow chart of a method according to another embodiment;
[0017] Figure 5a An example block diagram of an apparatus according to an embodiment is shown;
[0018] Figure 5b illustrates an example block diagram of an apparatus according to an embodiment; and
[0019] Figure 5c An example block diagram of an apparatus according to an embodiment is illustrated. DETAILED DESCRIPTION
[0020] It will be readily appreciated that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for (multiple) event subscription notifications is not intended to limit the scope of certain embodiments, but is representative of selected example embodiments.
[0021] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, throughout this specification, the use of the phrases "certain embodiments," "some embodiments," or other similar language refers to the fact that a particular feature, structure, or characteristic described in conjunction with an embodiment may be included in at least one embodiment. Thus, throughout this specification, the appearance of the phrases "in certain embodiments," "in some embodiments," "in other embodiments," or other similar language does not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.
[0022] In addition, if desired, the different functions or processes discussed below may be performed in different orders and / or performed simultaneously with each other. In addition, if desired, one or more of the functions or processes described may be optional or may be combined. Thus, the following description should be considered as merely illustrating the principles and teachings of certain example embodiments, rather than limiting them.
[0023] The 3rd Generation Partnership Project (3GPP) TR 23.724 studies improvements to support for Cellular Internet of Things (CIoT) and the evolution to the 5G System (5GS). A key issue is support for high-latency communications. As part of this key issue, "downlink data delivery status" notifications (e.g., buffered, transmitted, dropped) provided by the Session Management Function (SMF) and related subscriptions are introduced. In order to support scenarios where multiple application functions (AFs) send data to the same UE, a subscription can contain a packet filter that describes a specific application function as the source of downlink packets; then only notifications related to these packets should be sent to that AF.
[0024] For UEs with high latency communications, whether Policy and Charging Control (PCC) is used may depend on operator policy. If PCC is used, the Policy Control Function (PCF) may need to be aware of the subscription to downlink data delivery status events, because the PCF should install appropriate PCC rules with packet filters matching those received in the subscription and instructions to apply extended buffering. Note that the PCF is not aware of whether the buffering is done in the Session Management Function (SMF) or in the User Plane Function (UPF).
[0025] If buffering is done at the UPF, the SMF configures the UPF with specific packet detection rules that match traffic from a specific AF to enable notifications from the UPF to the SMF about buffered and dropped packets from that AF. The SMF then requires PCC rules supplied from the PCF with these packet filters and appropriate detection priorities as input. The PCF considers the installed PCC rules and assigns appropriate priorities to the PCC rules relative to other PCC rules.
[0026] The Network Exposure Function (NEF) when subscribing to "downlink data delivery status" notifications on behalf of an application function may not be aware of whether the PCC is applied to a given UE, although the signaling path for the subscription may depend on this.
[0027] Several signaling paths for event subscriptions from NEF to SMF are described in 3GPP TR23.724. In particular, these signaling paths may include NEF to PCF using Npcf_EventExposure_Subscribe, and PCF to SMF using Nsmf_EventExposure_Subscribe (Solution 25). In addition, the signaling path may include NEF to Universal Data Management (UDM) using Nudm_EventExposure_Subscribe, and PCF to SMF using Nudm_EventExposure_Subscribe (Solution 39). Both solutions have been transferred to 3GPPTS23.502, subscribing to "Downlink Data Delivery Status" events via PCF, and subscribing to "DDN Failure Post-Availability" events via User Data Repository (UDR). However, the differences between the events do not justify different subscription paths.
[0028] The signaling path via PCF requires PCC to be applied and is not suitable if the operator wishes to avoid using PCC for UEs with high latency communications. The signaling path via UDM appears to exclude applying PCC to affected UEs; however the NEF may not know whether PCC is applied to a given UE and select the signaling path based on this.
[0029] According to one embodiment, the PCF may provide a new policy control request trigger for subscription to an event exposure received by the SMF. Then, when the SMF receives a subscription request for notification of one or more events from another network function, such as subscribing to a "downlink data delivery status" event from the UDM using the Nsmf_EventExposure service, the SMF notifies the PCF about the subscription, such as by requesting a new policy using the Npcf_SMPolicyControl_UpdateNotify service operation. In some embodiments, the SMF may also provide the PCF with possible parameters that the SMF received as part of the subscription request within the notification. For example, the received parameters may include a packet filter and a target address for notification of a "downlink data delivery status" event.
[0030] In one embodiment, the PCF may then install or update the PCC rules based on the information received from the SMF. For example, in one embodiment, for a "downlink data delivery status" event, the PCF may install a PCC rule with: a packet filter, an indication of application extension buffering, and a new "AF subscribes to downlink data delivery status event IE" and / or the received notification target address.
[0031] Figure 1 An example information flow or signaling diagram for downlink data delivery status is illustrated. In particular, Figure 1 Includes an example process that an application function can use to subscribe to data delivery status notifications and explicitly cancel a previous subscription. In one embodiment, cancellation can be accomplished by sending a Namf_EventExposure_UnSubscribe request that identifies a subscription correlation ID.
[0032] like Figure 1 As illustrated in the example of , at 0, the SMF (e.g., H-SMF in a non-roaming case or V-SMF in a roaming case) may configure the relevant UPF to forward packets subject to extended buffering to the SMF. At 1, the AF may send an Nnef_EventExposure_Subscribe request to the NEF to request the data delivery status of the UE or UE group. Traffic filter information may be included in the message to identify the source of the downlink IP or Ethernet traffic. The downlink delivery status event may include: (multiple) downlink packets in an extended buffer event, (multiple) downlink packets discarded, and / or (multiple) downlink packets sent. In one example, (multiple) downlink packets in an extended buffer event may be triggered each time a new downlink packet is buffered using an extended buffer that matches the traffic filter information. In the notification of this downlink delivery status, the SMF may provide an extended buffer time, as determined in Section 4.2.3.3 of TS 23.501. When the extended buffering time determined by the SMF expires or exceeds the amount of downlink data to be buffered, a (multiple) downlink packet discarded event may occur. When the UE of the PDU session becomes ACTIVE, a (multiple) downlink packet transmitted event occurs and the buffered data can be delivered to the UE according to Section 4.2.3.3 of TS 23.501.
[0033] continue Figure 1In the example of, at 2, the NEF may send a Nudm_EventExposure_Subscribe request to the UDM. The identifier of the UE or UE group, the traffic filter information, the monitoring events received from the AF at step 1, and the NEF notification endpoint may be included in the message. At 3, the UDM may send a Nsmf_EventExposure_Subscribe request message to the SMF, and may include the identifier of the UE or UE group, the traffic filter information, the monitoring events, and the notification endpoint of the NEF received at step 2. At 4, the SMF may send a Nsmf_EventExposure_Subscribe response message to the UDM. In one example, notification steps 3 and 4 may not be applicable in a cancellation situation. At 5, the UDM may send a Npcf_EventExposure_Subscribe response message to the NEF, and at 6, the NEF may send a Nsmf_EventExposure_Subscribe response to the AF.
[0034] Optionally, at 7, if PCC is used for the UE, the SMF may send an Npcf_SMPolicyControl_UpdateNotify message to the PCF, indicating that the SMF has received a subscription for the downlink delivery status, and may include traffic filtering information, monitoring events, and the notification endpoint received at step 3. If the step 3 subscription is for a UE group, step 7 may be performed separately for each UE within the group controlled using the PCC. Optionally, at 8, the PCF may send PCC rule information to the SMF via an Npcf_SMPolicyControl_UpdateNotify reply message, which includes the received traffic filter and a request for notification about the downlink delivery status, and may include the notification endpoint of the NEF (an implicit subscription to notifications of the Nsmf_EventExposure service) and an indicator of the application extension buffer. According to another optional step, in the case of home-routed roaming, the H-SMF may create a QoS flow corresponding to the PCC rule information received from the PCF and exchange relevant signaling with the V-SMF.
[0035] Optionally, at 9, the SMF (e.g., H-SMF in non-roaming case, V-SMF in roaming case) may configure the relevant UPF to forward the packet to the SMF according to the updated information in step 8.
[0036] At 10, the SMF or UPF detects a change in downlink delivery status event, as described in clause 4.2.3 of TS 23.501. When attempting to send a packet to the AMF via the Namf_Communication_N1N2MessageTransfer service operation and obtaining a corresponding response, the SMF becomes aware that (multiple) downlink packets require extended buffering. If the buffering is in the UPF, the SMF may configure the UPF to buffer the corresponding downlink packets and provide a notification when the UPF subsequently discards such packets (as per clause 5.8.3.2 in TS 23.501 [2]). If the UPF reports the discarded packets or the SMF decides to discard the packets, a "(multiple) downlink packet discarded event" is detected. The SMF detects that the previously buffered packets can be transmitted due to the fact that the associated PDU session has become ACTIVE. At 11, the SMF may send a Nsmf_EventExposure_Notify with a downlink delivery status event message to the NEF, and at 12, the NEF sends a Nnef_EventExposure_Notify with a downlink delivery status event message to the AF.
[0037] Figure 2 An example of a process that can be used by an AF to subscribe to notifications and explicitly cancel a previous subscription is illustrated. More specifically, Figure 2 An example information flow or signaling flow diagram of Nnef_EventExposure_Subscribe, Unsubscribe, and Notify operations according to an embodiment is illustrated. In one example, cancellation can be accomplished by sending a Nnef_EventExposure_Unsubscribe request that utilizes a subscription correlation ID to identify the subscription to be canceled.
[0038] like Figure 2As illustrated in the example of , at 1, the AF can subscribe to one or more events (identified by event IDs) and can provide the associated notification endpoint of the AF by sending a Nnef_EventExposure_Subscribe request. The event reporting information defines the type of report requested (e.g., a one-time report, a periodic report, or an event-based report for monitoring the event). If the reporting event subscription is authorized by the NEF, the NEF records the association of the event trigger with the requester identity. The subscription may also include a maximum number of reports and / or a maximum duration of a reporting information element (IE). At 2, conditionally depending on the authorization in step 1, the NEF can subscribe to the received (multiple) events (identified by event IDs) and provide the associated notification endpoint of the NEF to the UDM by sending a Nudm_EventExposure_Subscribe request. If the reporting event subscription is authorized by the UDM, the UDM can record the association of the event trigger with the requester identity. Otherwise, the UDM can continue to indicate a failure in step 4.
[0039] Optionally, at 3a, if the requested event (e.g., monitoring for connectivity loss) requires AMF assistance, the UDM may send a Namf_EventExposure_Subscribe to the AMF serving the requested user. The UDM may send a Namf_EventExposure_Subscribe request to the serving AMF(s) (if the subscription applies to one UE or a group of(s) UEs), or to all AMFs in the same PLMN as the UDM (if the subscription applies to any UE). Since the UDM itself is not an event receiving NF, the UDM may provide its own notification endpoint in addition to that of the NEF. Each notification endpoint may be associated with an associated(group of)(multiple) event IDs. This is to ensure that the UDM can receive notifications of subscription change related events. If the subscription applies to a group(s) of UEs, the UDM may include its own same notification endpoint, i.e., notification target address (+ notification related Id), in the subscription to the serving AMF(s) of all UEs. Note that the same notification endpoint of the UDM is to help the AMF identify whether the subscription to the requested group event is the same when a new group member UE registers.
[0040] Optionally, at 3b, AMF may confirm the execution of Namf_EventExposure_Subscribe. Also optionally, at 3c, if the requested event requires SMF assistance, then for an existing (multiple) PDU session or during the PDU session establishment process, UDM may select SMF based on slice information, DNN and / or AF service ID and send Nsmf_EventExposure_Subscribe to (multiple) SMFs serving the requested user. Since UDM itself is not an event receiving NF, UDM can provide notification endpoint information of AMF, i.e., notification target address (+ notification related Id). Each notification endpoint may be associated with a related (group) (multiple) event IDs. Note that in the case of home routing, UDM sends a subscription to V-SMF via H-SMF. Optionally, at 3d, SMF may confirm the execution of Nsmf_EventExposure_Subscribe.
[0041] Optionally, at 4, the UDM may confirm the execution of Nudm_EventExposure_Subscribe. If the subscription applies to a group (multiple) of UEs and the maximum reporting number is included in the event reporting information in step 1, the number of UEs may be included in the confirmation. At 5, the NEF confirms the execution of Nnef_EventExposure_Subscribe to the requester that initiated the request. Optionally, at 6a, the event-dependent UDM may detect the event occurrence and may send the event report together with a timestamp to the associated notification endpoint of the NEF, for example by means of a Nudm_EventExposure_Notify message. Optionally, at 6b, the event-dependent AMF may detect the event occurrence and may send the event report together with a timestamp to the associated notification endpoint of the NEF, for example by means of a Namf_EventExposure_Notify message. If the AMF has a maximum reporting number stored for a UE or individual member UE, the AMF may decrement its value by one for the reported event.
[0042] For both step 6a and step 6b, when the maximum number of reports is reached and if the subscription is applied to the UE, the NEF may unsubscribe the monitoring event(s) from the UDM and the UDM may unsubscribe the monitoring event(s) from the AMF serving the UE. Also for both step 6a and step 6b, when the maximum number of reports for an individual group member UE is reached, the NEF may use the number of UEs received in step 4 to determine whether the reporting for the group is complete. If the NEF determines that the reporting for the group is complete, the NEF may unsubscribe the monitoring event(s) from the UDM and the UDM may unsubscribe the monitoring event(s) from all AMFs serving the UEs belonging to the group. When the maximum duration of the reports in the NEF, UDM and AMF expires, then each of these nodes may locally unsubscribe from the monitoring event. Optionally, at 6c, depending on the event, the SMF may detect that the event has occurred and may send the event report together with a timestamp to the associated notification endpoint of the NEF, for example by means of an Nsmf_EventExposure_Notify message. Optionally, at 6d, the NEF may store the information received in steps 6a, 6b or 6c in the UDR together with a timestamp using the Nudr_DM_Create or Nudr_DM_Update service operations as appropriate.
[0043] Optionally, at 7, depending on the events in steps 6a-6f, the NEF may forward the report events received by Nudm_EventExposure_Notify and / or Namf_EventExposure_Notify to the AF. Optionally, at 8, depending on the events, the AMF may detect that a subscription change related event has occurred, such as a subscription correlation ID change due to AMF reallocation or the addition of a new subscription correlation ID due to a new group UE registration, it may send an event report to the associated notification endpoint of the UDM, for example by means of a Namf_EventExposure_Notify message. Note that in one embodiment, the notification steps 6 to 8 may not be applicable in the cancellation case.
[0044] Figure 3 An example information flow or signaling flow diagram for downlink data delivery status according to an embodiment is illustrated. In one example, Figure 3 The procedure can be used by application functions to subscribe to notifications about availability after a downlink data delivery notification failure. The NEF service operation information flow in clause 4.15.3.2.3 of TS23.501 can be used according to Figure 3 The detailed process is applied.
[0045] like Figure 3As illustrated in the example of , at 0, the SMF (e.g., H-SMF in non-roaming case or V-SMF in roaming case) may configure the relevant UPF to forward packets subject to extended buffering to the SMF. At 1, the AF may send a Nnef_EventExposure_Subscribe request to the NEF to request notification of "availability after DDN failure" for the UE or UE group. Traffic filter information may be included in the message to identify the source of the downlink IP or Ethernet traffic. At 2, the NEF may send a Nudm_EventExposure_Subscribe request to the UDM. The identifier of the UE or UE group, the traffic filter information, the monitoring events received from the AF in step 1, and the NEF notification endpoint may be included in the message.
[0046] At 3, the UDM may send a Namf_EventExposure_Subscribe to the AMF serving the UE identified in step 2 to subscribe to "Availability after DDN failure". Each UE may use a separate subscription. The NEF notification endpoint received in step 2 may be included in the message.
[0047] At 4, the AMF may confirm the execution of Namf_EventExposure_Subscribe and may provide a notification target address and a unique reference ID for a subsequent Nsmf_EventExposure_Notify message with the downlink delivery status event "(multiple) downlink packets are dropped" (see step 13). At 5, the UDM may send a Nsmf_EventExposure_Subscribe request to the PCF to request notification of the downlink delivery status "(multiple) downlink packets are dropped". A separate subscription may be used for each UE. The identifier and traffic filter information of the UE received in step 2 and the AMF notification endpoint received in step 4 may be included in the message.
[0048] At 6, the SMF may send a Npcf_SMPolicyControl_Update response message to the UDM. At 7, the UDM may send a Nudm_EventExposure_Subscribe response to the NEF. At 8, the NEF may send a Nsmf_EventExposure_Subscribe response to the AF. Optionally, at 9, if the PCC is used for the UE, the SMF may send a Npcf_SMPolicyControl_UpdateNotify message to the PCF to indicate that the SMF has received a subscription to the downlink delivery status, and may include traffic filter information, monitoring events, and the notification endpoint received in step 3.
[0049] Optionally, at 10, the PCF may send PCC rule information to (multiple) SMFs via a Npcf_SMPolicyControl_UpdateNotify reply message, which includes the received traffic filter and a request for notification about the downlink delivery status, and may include the notification endpoint of the NEF (an implicit subscription to notifications of the Nsmf_EventExposure service) and an indicator of the application extension buffer. Also optionally, in the case of home route roaming, the H-SMF may create a QoS flow corresponding to the PCC rule information received from the PCF, and may exchange related signaling with the V-SMF.
[0050] Optionally, at 11, the SMF (e.g., H-SMF in the non-roaming case or V-SMF in the roaming case) may configure the relevant UPF to forward the packet to the SMF based on the updated information in step 10. At 12, the SMF may detect that the first packet is being discarded as follows (see also clause 4.2.3): When attempting to send a packet to the AMF via the Namf_Communication_N1N2MessageTransfer service operation and obtaining a corresponding response, the SMF becomes aware that (multiple) downlink packets require extended buffering. If buffered in the UPF, the SMF may configure the UPF to buffer the corresponding downlink packets and provide a notification when the UPF subsequently discards such packets (according to clause 5.8.3.2 in TS 23.501 [2]). If the UPF reports the discarded packets or the SMF decides to discard the packets, a "downlink packet(s) discarded event" is detected.
[0051] At 13, the SMF may send a Nsmf_EventExposure_Notify message with the downlink delivery status event "(multiple) downlink packets dropped" to the AMF. If the UE is unreachable after the AMF receives the notification from the SMF, the AMF may set the Notify-on-available-after-DDN-failure flag for the subscription identified by the notification reference id (see step 4). At 14, the AMF may detect that the UE is reachable again and may check the Notify-on-available-after-DDN-failure flag for each subscription associated with the UE to determine whether any notification is required. At 15, the AMF may send (multiple) Namf_EventExposure_Notify messages with "availability after DDN failure" for the NEF identified via the corresponding subscription in step 14. At 16, the NEF may send a Nnef_EventExposure_Notify message with the "availability after DDN failure" event to the AF.
[0052] According to certain embodiments, the Nudm_EventExposure_Subscribe service operation is an operation by which a NF Consumer (NEF) subscribes to receive events, or updates the subscription if a subscription has already been defined in the UDM. The inputs to the Nudm_EventExposure_Subscribe service operation include the target of the subscription: UE ID (SUPI or GPSI, internal group identifier or external group identifier, or any indication that the UE is targeted), an event filter containing (multiple) event IDs (see Section 4.15.3.1), and the event reporting information defined in Table 4.15.1-1. Optional inputs may include an expiration time, traffic filters (for downlink data delivery failure and downlink data delivery status events). The outputs of the Nudm_EventExposure_Subscribe service operation include an operation execution result indication, when the subscription is accepted: subscription correlation ID, expiration time (required if the subscription can expire based on the operator's policy). The optional output may include the first corresponding event report - if the corresponding information is available (see clause 4.15.1), and / or the optional output may include the number of UE(s) - if the external group identifier and the maximum number of reports are included in the input. The number of UEs indicates the number of UEs within the group identified by the external group identifier. The NEF may use this value to determine whether the monitoring event has been reported for all group member UEs.
[0053] In some embodiments, buffering may be supported at the UPF and / or SMF. The UPF may forward incoming packets to the SMF. The SMF may then forward them to the AMF using the Namf_Communication_N1N2MessageTransfer service. If the UE is in a power saving state and is temporarily unreachable, the Namf_Communication_N1N2MessageTransfer reply requests downlink buffering. The SMF may then buffer the packets itself or configure the UPF accordingly. The SMF may become aware of the first buffered packets in this way. If buffering in the UPF is used, the SMF may configure the UPF to buffer the packets (instead of forwarding them to the SMF). If buffering at the SMF is used, the UPF does not need to be reconfigured, and the SMF may continue to receive and buffer all downlink packets.
[0054] As outlined above, the SMF can decide to apply buffering, and since the SMF receives all incoming downlink packets while buffering, it can easily detect whether any packet from a given source is buffered.
[0055] For low latency communications, the SMF can directly become aware of the need for buffering, and if source-specific reporting is required, notifications can be used. However, with existing functionality, the SMF cannot detect whether a packet from a given source is buffered at the UPF unless separate packet detection rules are configured for each source; if packets from multiple sources are combined in one packet detection rule via a wildcard filter, only the first buffered packet of any source is reported without identifying the source.
[0056] The SMF can configure the UPF to send a notification about the first buffered packet of a packet flow, as identified by the packet detection rule. The SMF identifies the packet flow via the packet detection rule and associates the forwarding action rule with the action "buffer" with a request for notification of the first buffered packet. The notification identifies the packet flow via the packet detection rule identifier. Therefore, the packet filter can be provided in the packet detection rule as part of the configuration from the SMF. The packet detection rules are evaluated in priority order to resolve overlapping filters. This information can typically be derived from the PCC rules. In this example, there is only one notification about the first buffered packet. The notification does not contain the packet filter describing the packet, but contains a reference to the packet detection rule.
[0057] Regarding the detection of dropped packets at the SMF, if buffering is done at the SMF, no UPF interaction is required and the SMF can identify the source(s) of the dropped packets.
[0058] Regarding the detection of dropped packets at the UPF, the SMF can inform the UPF to drop buffered (and subsequently incoming) packets. But the UPF can also automatically start dropping buffered and incoming packets based on a timer or the amount of buffered downlink data. However, for this case, there is no existing mechanism for notifying of dropped packets, and the N4 interface may need to be extended.
[0059] Thus, in one embodiment, the SMF may identify the packet flow via the packet detection rule and associate a forwarding action rule with the action "buffer" and a request for a new notification of the first dropped packet. The notification may identify the packet flow via the packet detection rule identifier.
[0060] For availability after a DDN failure, when the SMF is notified that the UE is unreachable, the SMF interacts with the UPF to remove the buffered packets and requests the UPF to report the traffic information (e.g., source IP address, source port number) of the discarded packets. This assumes that the SMF has not configured the UPF to buffer but to discard packets immediately. The existing N4 functionality is to associate the action "discard" (instead of "buffer") with the packet detection rule. However, in this case, there is no notification of discarded packets due to the "discard" action. It does not seem to be necessary because the traffic filter is configured by the SMF in the packet detection rule. If a wildcard filter is assumed in the packet detection rule, more detailed notifications about discarded packets may be introduced. In one embodiment, a notification about each discarded packet may be provided. In another embodiment, the UPF may analyze the discarded packets to detect flows with the same source and destination, and notify when a new flow is detected.
[0061] For the detection of transmission packets, if the UE is in CM-CONNECTED state, the SMF can be notified via the Namf_EventExposure_Notify service operation. The SMF can then transmit the packets it buffered, or configure the UPF to do so.
[0062] For high latency communications and related event detection, the SMF can configure the UPF to forward incoming packets before high latency communications can begin (i.e., when a PDP session is established). It may be inappropriate to perform such configuration only when a subscription for relevant event notifications is received, because the basic functionality of buffering packets can be applied independently of any such subscription. On the other hand, event subscriptions can provide packet filters for downlink packets from a specific AF. Configuring information that matches these packet filters before the AF transmits the information seems very complex, so a more general configuration with wildcard packet filters applied at the UPF when the PDP session is established should be assumed. The SMF can be triggered to perform this configuration based on PCC control or user profiles.
[0063] Some solutions assume PCC control, where the PCC provides policy information for extended buffering to the SMF during session management policy establishment / modification. Other solutions do not consider this aspect and may assume that whether to use PCC control for UEs with high latency communications depends on operator policy.
[0064] For configuration of event detection without using PCC, in one embodiment, when a subscription for downlink delivery status is received, the SMF acts as follows: If buffering is performed at the SMF, the SMF can analyze each downlink packet and if packet filters are supplied in the subscription, the detected subscription events can also be easily reported. Under the assumption that wildcard packet detection rules for forwarding downlink packets have been installed, no corresponding UPF configuration is required. If buffering is performed at the UPF and packet filters are supplied as part of the subscription, specific packet detection rules that match these packet filters can be installed. The corresponding logic in the SMF can also take into account other installed packet detection rules and their priorities, and thus replicate the policy control functionality that is usually assigned to the PCF.
[0065] For configuration of event detection in case of using PCC, in one embodiment, the PCF should be aware of the subscription to the "downlink data delivery status" event, because the PCF may need to install appropriate PCC rules with packet filters matching those received in the subscription and instructions to apply extended buffering. Note that the PCF is not aware of whether the buffering is done in the SMF or UPF.
[0066] As discussed above, different signaling paths are available for signaling of event subscriptions from NEF to PCF. These signaling paths may include NEF to PCF using Npcf_EventExposure_Subscribe, and PCF to SMF using Nsmf_EventExposure_Subscribe (Solution 25), and / or the signaling path may include NEF to Universal Data Management (UDM) using Nudm_EventExposure_Subscribe and PCF to SMF using Nudm_EventExposure_Subscribe (Solution 39).
[0067] According to one embodiment, the UDM signaling path may be used. If PCC is used, the SMF informs the PCF about the subscription to the "downlink data delivery status" event via a new policy control request trigger. The PCF then installs or updates the appropriate PCC rule with a matching packet filter and a new "AF subscribes to downlink data delivery status event IE".
[0068] Therefore, according to certain embodiments, for high-latency communications, buffering at both the UPF and / or SMF may be supported. In one embodiment, in order to support buffering at the UPF, a new notification from the UPF to the SMF about discarded packets may be provided. According to some embodiments, the use of PCC may be optional for high-latency communications. In one embodiment, the PCC rules for high-latency communications may include a new "Extended Buffer" IE. According to some embodiments, a UDM signaling path may be used. In one embodiment, if PCC is used, the SMF triggers notification of the PCF about the subscription to the "Downlink Data Delivery Status" event via a new policy control request. The PCF then installs or updates the appropriate PCC rules with a matching packet filter and a new "AF Subscribes to Downlink Data Delivery Status Event IE".
[0069] In view of the above, certain embodiments may at least solve the following problem: With respect to the "information flow for downlink data delivery status", how does the SMF detect the downlink delivery status. There are several related problems with the current information flow: (1) Solution 25 in TR 23.724 requires PCC control of extended buffering, but such PCC control is still lacking; (2) PCC control should be optional; and (3) The packet filter related to the downlink data delivery status implies UPF interaction (N4 impact) to configure the UPF to provide notification about the downlink data delivery status when the first packet is being buffered and then discarded.
[0070] According to certain embodiments, the traffic filter in the UPF has a priority that can be coordinated with other installed traffic filters. In one embodiment, this can be controlled by the PCF via PCC rules. Subscriptions for downlink data delivery status can also be integrated in the PCC rules. Subscriptions to Nsmf_EventExposure notifications can be made indirectly via the Npcf_SMPolicyControl service.
[0071] In one embodiment, the subscription to the Nsmf_EventExposure notification can be done indirectly via the PCC rule information of the Npcf_SMPolicyControl service. To this end, in one embodiment, the AF subscription to the downlink data delivery status event IE can be added to the PCC rules. If PCC is used, the PCF can be informed about the subscription to the downlink data delivery status at the SMF to allow the PCF to provide policies as described above.
[0072] Table 1 below describes forwarding action rules (FARs) that define how packets may be buffered, dropped, or forwarded, including packet encapsulation / decapsulation and forwarding destination, according to certain embodiments.
[0073]
[0074]
[0075] In some embodiments, the SMF may provide instructions to the UPF for at least the following actions: buffering downlink packets, with the additional option of reporting arrival of a first downlink packet and / or reporting a first discarded downlink packet or a discarded packet.
[0076] When the UP connection of a PDU session is deactivated and the SMF decides to activate buffering in the UPF for the session, the SMF can notify the UPF to start buffering packets for the PDU session. The buffering in the UPF can be configured based on a timer or the amount of downlink data to be buffered. The SMF can decide whether the buffering timer or the amount of downlink data is handled by the UPF or the SMF.
[0077] After starting buffering, when the first downlink packet arrives, the UPF can notify the SMF whether it is set to report. Unless otherwise specified, the UPF can send a downlink data notification message to the SMF via N4 and indicate the packet detection rule (PDR) for the received downlink packet.
[0078] After starting caching, when the first downlink packet that has been buffered within the configured time period is discarded by the UPF because it exceeds the configured buffering time or the amount of downlink data to be buffered, the UPF can notify the SMF: whether it is set to report. The UPF can send a discarded downlink data notification message to the SMF via N4 and indicate the PDR of the received downlink packet. If the buffered downlink packet is discarded after the configured time period, a new report can be sent.
[0079] When the UP connection of a PDU session is activated, the SMF can update the buffer status changes of the UPF. The buffered packets (if any) are then forwarded by the UPF to the (R)AN. If the UP connection of a PDU session has been deactivated for a long time, the SMF can instruct the UPF to stop buffering for the PDU session.
[0080] Figure 4a An example flow chart of one or more methods for notifications of event subscriptions according to an example embodiment is illustrated. In some example embodiments, Figure 4a The flowchart may be executed by a network entity or a network node in a 3GPP system, such as LTE or 5G NR. For example, in some example embodiments, Figure 4a The method can be executed by PCF, such as Figure 1-Figure 3 Thus, in some embodiments, the method may include Figure 1-Figure 3 Any process performed at a PCF in .
[0081] like Figure 4a As illustrated in the example of , the method may include, at 400, providing a new policy control request trigger for a subscription for event exposure received by the SMF. The method may also include, at 410, receiving a notification from the SMF regarding the subscription. For example, receiving 410 may include: receiving a notification when the SMF receives a subscription request for notifications about one or more events from another network function. For example, the subscription may include a subscription for a "downlink data delivery status" event from the UDM using the Nsmf_EventExposure service. In one embodiment, receiving 410 may also include: receiving a request for a new policy using the Npcf_SMPolicyControl_UpdateNotify service operation. In some embodiments, receiving 410 may also include: receiving feasible parameters received by the SMF as part of the subscription request within the notification. For example, the received parameters may include a packet filter and a target address for notifying the "downlink data delivery status" event.
[0082] In one embodiment, Figure 4a The method may also include, at 420, installing or updating the PCC rule based on the information received in the notification from the SMF. For example, in one embodiment, for a "downlink data delivery status" event, installing 420 may include installing a PCC rule with a receive packet filter, an indication of an application extension buffer, a "new AF subscription to downlink data delivery status event IE", and / or a received notification target address.
[0083] Figure 4bAn example flow chart of a method for notification of (multiple) event subscriptions according to an example embodiment is illustrated. In some example embodiments, Figure 4b The flowchart may be executed by a network entity or a network node in a 3GPP system, such as LTE or 5GNR. For example, in some example embodiments, Figure 4b The method can be executed by SMF, such as Figure 1-Figure 3 Thus, in some embodiments, the method may include Figure 1-Figure 3 Any process executed at the SMF in .
[0084] like Figure 4b As illustrated in the example of , the method may include, at 450, receiving from the PCF a new policy control request trigger received by the SMF regarding a subscription for event exposure. The method may also include, at 460, providing a notification about the subscription to the PCF when the SMF receives a subscription request for notifications about one or several events from another network function. For example, providing 460 may include: providing a notification when the SMF receives a subscription request for notifications about one or more events from another network function. For example, the subscription may include a subscription from the UDM for a "downlink data delivery status" event using the Nsmf_EventExposure service. In one embodiment, providing 460 may also include: transmitting a request for a new policy using the Npcf_SMPolicyControl_UpdateNotify service operation. In some embodiments, providing 460 may also include: providing the PCF with possible parameters received by the SMF as part of the subscription request within the notification. For example, the parameters may include a packet filter and a target address for notifying the "downlink data delivery status" event.
[0085] Figure 5a An example of an apparatus 10 according to an embodiment is illustrated. In one embodiment, the apparatus 10 may be a node, a host, or a server in a communication network or serving such a network. For example, the apparatus 10 may be an AF, a UPF, a SMF, a PCF, a UDM, a NEF, a UDR, an AMF, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB), a CU of a gNB, a WLAN access point, a serving gateway (SGW), a mobility management entity (MME), a data management entity (e.g., UDM), and / or other entities associated with a radio access network (such as 5G or NR). In one example, the apparatus 10 may represent a PCF, such as Figure 1 , Figure 2 or Figure 3 As depicted in .
[0086] like Figure 5a As shown in the example of , the device 10 may include a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general or special purpose processor. In fact, the processor 12 may include, for example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 5a A single processor 12 is shown in the figure, but multiple processors may be utilized according to other embodiments. For example, it should be understood that in some embodiments, the device 10 may include two or more processors, which may form a multi-processor system that can support multi-processing (e.g., in this case, the processor 12 may represent a multi-processor). In some embodiments, the multi-processor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
[0087] Processor 12 may perform functions associated with the operation of device 10, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 10, including processes associated with management of communication resources.
[0088] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that may be executed by the processor 12. The memory 14 may be one or more memories and any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may include any combination of random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic disks or optical disks, hard disk drives (HDDs), or any other type of non-transitory machine or computer readable media. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enable the device 10 to perform the tasks described herein.
[0089] In one embodiment, the device 10 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 12 and / or the device 10.
[0090] In some embodiments, the device 10 may also include or be coupled to one or more antennas 15 for transmitting signals and / or data to the device 10 and receiving signals and / or data from the device 10. The device 10 may also include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, multiple radio interfaces that may be coupled to (multiple) antennas 15. The radio interfaces may correspond to a variety of radio access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, Radio Frequency Identifier (RFID), Ultra-Wideband (UWB), MulteFire, etc. The radio interface may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, Fast Fourier Transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and receive symbols (e.g., via uplinks).
[0091] As such, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15 and to demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the apparatus 10 may include input and / or output devices (I / O devices).
[0092] In one embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. These modules may include, for example, an operating system that provides operating system functionality for device 10. Memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to device 10. The components of device 10 may be implemented in hardware, or as any suitable combination of hardware and software.
[0093] According to some embodiments, processor 12 and memory 14 may be included in or may form part of a processing circuit system or a control circuit system. In addition, in some embodiments, transceiver 18 may be included in or may form part of a transceiver circuit system.
[0094] As used herein, the term "circuitry" may refer to: a pure hardware circuitry implementation (e.g., analog and / or digital circuitry); a combination of hardware circuitry and software; a combination of analog and / or digital hardware circuitry and software / firmware; any portion of a hardware processor(s) with software (including a digital signal processor) that work together to enable a device (e.g., device 10) to perform various functions, and / or hardware circuit(s) and / or processor(s) or portions thereof that operate using software, which may not be present when the operation does not require it. As a further example, as used herein, the term "circuitry" may also cover an implementation of only a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, and its accompanying software and / or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.
[0095] As described above, in some embodiments, the apparatus 10 may be a network node or entity, such as a PCF or an AF. According to some embodiments, the apparatus 10 may be controlled by the memory 14 and the processor 12 to perform functions associated with any of the embodiments described herein. For example, in some embodiments, the apparatus 10 may be configured to execute any of the flow charts or signaling diagrams described herein (such as Figure 1-Figure 3 The signaling diagram shown in Figure 4a or Figure 4b For example, in some examples, the device 10 may correspond to or represent Figure 1-Figure 3 In some embodiments, the apparatus 10 may be configured to perform the process of event subscription notification as described in the example embodiments discussed herein.
[0096] Figure 5b An example of an apparatus 20 according to another example embodiment is illustrated. In an example embodiment, the apparatus 20 may be a node or server associated with a radio access network such as an LTE network, 5G or NR, or other radio systems that may benefit from equivalent procedures. For example, the apparatus 20 may be an AF, UPF, SMF, PCF, UDM, NEF, UDR, AMF, base station, Node B, evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), and / or a DU or CU of a gNB associated with a radio access network such as 5G or NR. It should be noted that a person of ordinary skill in the art will understand that the apparatus 20 may include Figure 5b Components or features not shown.
[0097] In some example embodiments, the apparatus 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some example embodiments, the apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, MulteFire, and / or any other radio access technology. It should be noted that persons of ordinary skill in the art will understand that the apparatus 20 may include Figure 5b Components or features not shown.
[0098] like Figure 5b As shown in the example of , the device 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general or special purpose processor. In fact, the processor 22 may include, for example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 4b A single processor 22 is shown in FIG. 1 , but multiple processors may be used according to other example embodiments. For example, it should be understood that in some example embodiments, the apparatus 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 22 may represent a multiprocessor). In some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
[0099] Processor 22 may perform functions associated with the operation of device 20, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 20, including processes associated with communication resource management.
[0100] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories and any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may include any combination of random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic disks or optical disks, hard disk drives (HDDs), or any other type of non-transitory machine or computer readable media. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, enables the device 20 to perform tasks as described herein.
[0101] In an example embodiment, the device 20 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 22 and / or the device 20.
[0102] In an example embodiment, the device 20 may also include or be coupled to one or more antennas 25 for receiving downlink signals and for transmitting from the device 20 via an uplink. The device 20 may also include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a variety of radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, BT-LE, RFID, UWB, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDMA symbols.
[0103] For example, in one example embodiment, the transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via other component antennas 25 for further processing by other elements of the device 20. In other example embodiments, the transceiver 28 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some example embodiments, the device 10 may include input and / or output devices (I / O devices). In some examples, the device 20 may also include a user interface, such as a graphical user interface or a touch screen.
[0104] In an example embodiment, the memory 24 stores software modules that provide functionality when executed by the processor 22. These modules may include, for example, an operating system that provides operating system functionality for the device 20. The memory may also store one or more functional modules such as applications or programs to provide additional functionality for the device 20. The components of the device 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, the device 20 may optionally be configured to communicate with the device 10 via a wireless or wired communication link 70 according to any radio access technology such as NR. For example, in an example embodiment, the link 70 may represent an Xn interface.
[0105] According to some example embodiments, the processor 22 and the memory 24 may be included in the processing circuit system or the control circuit system or may form a part of the processing circuit system or the control circuit system. In addition, in some example embodiments, the transceiver 28 may be included in the transceiver circuit system or may form a part of the transceiver circuit system.
[0106] As discussed above, according to example embodiments, the apparatus 20 may be a network node or function, such as an AF, AMF, SMF, NEF, UDR, and / or UDM. According to some examples, the apparatus 20 may be controlled by the memory 24 and the processor 22 to perform functions associated with the example embodiments described herein. For example, in some example embodiments, the apparatus 20 may be configured to perform any of the diagrams or signaling flow diagrams described herein (such as Figure 1-Figure 3 as well as Figure 4a or Figure 4b For example, the apparatus 20 may correspond to one or more of the processes described in Figure 1-Figure 3 In an example embodiment, the apparatus 20 may be configured to perform the process of event subscription notification as described in the example embodiments discussed herein.
[0107] Figure 5cAn example of an apparatus 30 according to another example embodiment is illustrated. In an example embodiment, the apparatus 30 may be a node or element in a communication network or associated with such a network, such as a UE, a mobile equipment (ME), a mobile station, a mobile device, a fixed device, an IoT device, or other device. As described herein, a UE may alternatively be referred to as, for example, a mobile station, a mobile equipment, a mobile unit, a mobile device, a user device, a subscriber station, a wireless terminal, a tablet computer, a smart phone, an IoT device or a NB-IoT device, a connected car, etc. As an example, the apparatus 30 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, etc.
[0108] In some example embodiments, the apparatus 30 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some example embodiments, the apparatus 30 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, MulteFire, and / or any other radio access technology. It should be noted that persons of ordinary skill in the art will understand that the apparatus 30 may include Figure 5c Components or features not shown.
[0109] like Figure 5c As shown in the example of , the device 30 may include or be coupled to a processor 32 for processing information and executing instructions or operations. The processor 32 may be any type of general or special purpose processor. In fact, the processor 32 may include, for example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 5c A single processor 32 is shown in FIG. 1 , but multiple processors may be used according to other example embodiments. For example, it should be understood that in some example embodiments, the apparatus 30 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 32 may represent a multiprocessor). In some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
[0110] Processor 32 may perform functions associated with the operation of device 30, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 30, including processes associated with communication resource management.
[0111] The device 30 may also include or be coupled to a memory 34 (internal or external), which may be coupled to the processor 32 for storing information and instructions that may be executed by the processor 32. The memory 34 may be one or more memories and any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 34 may include any combination of random access memory (RAM), read-only memory (ROM), static memory such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium. The instructions stored in the memory 34 may include program instructions or computer program code that, when executed by the processor 32, enables the device 30 to perform tasks as described herein.
[0112] In an example embodiment, the device 30 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 32 and / or the device 30.
[0113] In some example embodiments, the apparatus 30 may also include or be coupled to one or more antennas 35 for receiving downlink signals and for transmitting from the apparatus 30 via an uplink. The apparatus 30 may also include a transceiver 38 configured to transmit and receive information. The transceiver 38 may also include a radio interface (e.g., a modem) coupled to the antenna 35. The radio interface may correspond to a variety of radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, BT-LE, RFID, UWB, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDMA symbols.
[0114] For example, the transceiver 38 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 35 and to demodulate information received via the antenna(s) 35 for further processing by other elements of the apparatus 30. In other example embodiments, the transceiver 38 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some example embodiments, the apparatus 30 may include input and / or output devices (I / O devices). In certain example embodiments, the apparatus 30 may also include a user interface, such as a graphical user interface or a touch screen.
[0115] In an example embodiment, the memory 34 stores software modules that provide functionality when executed by the processor 32. These modules may include, for example, an operating system that provides operating system functionality for the device 30. The memory may also store one or more functional modules such as applications or programs to provide additional functionality for the device 30. The components of the device 30 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, the device 30 may optionally be configured to communicate with the device 10 via a wireless or wired communication link 71 according to any radio access technology such as NR and / or communicate with the device 20 via a wireless or wired communication link 72.
[0116] According to some example embodiments, the processor 32 and the memory 34 may be included in the processing circuit system or the control circuit system or may form a part of the processing circuit system or the control circuit system. In addition, in some example embodiments, the transceiver 38 may be included in the transceiver circuit system or may form a part of the transceiver circuit system.
[0117] As discussed above, according to some example embodiments, the apparatus 30 may be, for example, a UE, a mobile device, a mobile station, a ME, an IoT device, and / or a NB-IoT device. According to some example embodiments, the apparatus 30 may be controlled by a memory 34 and a processor 32 to perform functions associated with the example embodiments described herein.
[0118] Thus, certain example embodiments provide several technical improvements, enhancements and / or advantages over prior art processes and constitute improvements in at least the technical field of wireless network control and management. As a result, example embodiments may improve at least the throughput, latency and / or processing speed of network nodes and / or UEs. Thus, use of certain example embodiments results in improved functionality of communication networks and their nodes (such as base stations, eNBs, gNBs and / or UEs or mobile stations).
[0119] In some example embodiments, the functionality of any method, process, signaling diagram, algorithm, or flow chart described herein may be implemented by software and / or computer program code or code portions stored in a memory or other computer readable or tangible medium and executed by a processor.
[0120] In some example embodiments, the apparatus may include or be associated with at least one software application, module, unit or entity configured as (multiple) arithmetic operations, or as a program or part thereof (including added or updated software routines), executed by at least one operating processor. Programs, also referred to as program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and may include program instructions for performing specific tasks.
[0121] The computer program product may include one or more computer executable components that are configured to perform some example embodiments when the program is run. The one or more computer executable components may be at least one software code or code portion. Modifications and configurations required to implement the functionality of the example embodiments may be performed as (multiple) routines that may be implemented as added or updated (multiple) software routines. In one example, (multiple) software routines may be downloaded to the device.
[0122] As an example, software or computer program code or code portions may be in source code form, object code form or some intermediate form, and it may be stored in some carrier, distribution medium or computer readable medium which may be any entity or device capable of carrying the program. For example, such carriers may include recording media, computer memory, read-only memory, optoelectronic and / or electrical carrier signals, telecommunication signals and / or software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer, or it may be distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.
[0123] In other example embodiments, the functionality may be performed by hardware or circuitry included in a device (e.g., device 10 or device 20), such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, such as an intangible means, which may be carried by an electromagnetic signal downloaded from the Internet or other network.
[0124] According to example embodiments, an apparatus such as a node, a device or a corresponding component may be configured as a circuit system, a computer or a microprocessor, such as a single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity used for (multiple) arithmetic operations and / or an operation processor for performing (multiple) arithmetic operations.
[0125] Those of ordinary skill in the art will readily appreciate that the example embodiments discussed above may be practiced with processes in a different order and / or with hardware elements in a configuration different from that disclosed. Therefore, although some embodiments have been described based on these example embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be apparent while remaining within the spirit and scope of the example embodiments.
Claims
1. A method for a policy control function of a communication network, the method comprising: providing a policy control request trigger to a session management function, the policy control request trigger requesting notification of a subscription request for notifications received by the session management function from other network entities of the communications network regarding downlink data delivery status events; receiving, based on the policy control request trigger, a notification from the session management function of a subscription request for notifications received by the session management function from another network entity of the communications network regarding downlink data delivery status events, the notifications including identification of a source of downlink Internet Protocol or Ethernet traffic associated with the downlink; as well as At least one policy and charging control rule is installed or updated based on the traffic filter information included in the notification received from the session management function. 2 . The method of claim 1 , wherein the another network entity comprises a general data management entity.
3. The method of claim 1, wherein the receiving comprises receiving a notification from the session management function using an Npcf_SMPolicyControl_UpdateNotify service operation. The method of claim 1 , wherein the notification includes parameters related to the subscription.
5. The method of claim 4, wherein the parameters include at least one of: at least one packet filter and a target address for notification regarding the downlink data delivery status event.
6. The method of claim 5, wherein installing or updating the at least one policy and charging control rule comprises installing a policy and charging control rule comprising at least one packet filter.
7. The method of claim 6, wherein the policy and charging control rules further include at least one of: an indication of applying extended buffering to data packets received from a source of downlink Internet Protocol or Ethernet traffic, an information element indicating an application function subscription to receive notifications about downlink data delivery status events, or the target address.
8. An apparatus for communication, comprising: at least one processor; as well as at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, when the computer program code is executed, cause, with the at least one processor, the apparatus to at least: providing a policy control request trigger to a session management function, the policy control request trigger requesting notification of a subscription request for notifications received by the session management function from other network entities of a communications network regarding downlink data delivery status events; receiving a notification from the session management function of a subscription request for notifications received by the session management function from another network entity regarding downlink data delivery status events, the notifications including identifying a source of downlink Internet Protocol or Ethernet traffic associated with the downlink; as well as At least one policy and charging control rule is installed or updated based on the traffic filter information included in the notification received from the session management function.
9. The apparatus of claim 8, wherein a notification of the subscription request for notifications regarding the downlink data delivery status event is received from the session management function when the session management function receives the subscription request from a general data management.
10. The apparatus of claim 8, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus, when the computer program code is executed, to at least: receive the notification using an Npcf_SMPolicyControl_UpdateNotify service operation. The apparatus according to claim 8 , wherein the notification includes parameters related to the subscription.
12. The apparatus of claim 11, wherein the parameters include at least one of: at least one packet filter and a target address for notification regarding the downlink data delivery status event.
13. The apparatus of claim 12, wherein installing or updating at least one policy and charging control rule comprises installing a policy and charging control rule that includes the at least one packet filter.
14. The apparatus of claim 13, wherein the policy and charging control (PCC) rule further comprises at least one of: an indication of applying extended buffering to data packets received from a source of downlink Internet Protocol or Ethernet traffic, an information element indicating an application function subscription to receive notifications about downlink data delivery status events, or the target address.
15. An apparatus for communication, the apparatus comprising: Policy control functions, including: means for providing a policy control request trigger to a session management function, the policy control request trigger requesting notification of a subscription request for notification of downlink data delivery status events received by the session management function from another network entity of a communications network; means for receiving, from the session management function, a notification of a subscription request for notifications of downlink data delivery status events received by the session management function from the other network entity, the notifications including identification of a source of downlink Internet Protocol or Ethernet traffic associated with the downlink data delivery status events; and Means for installing or updating at least one policy and charging control rule based on traffic filter information included in said notification received from said session management function.
16. A method for session management functionality of a communication network, the method comprising: receiving a policy control request trigger from a policy control function, the policy control request trigger requesting notification regarding a subscription request regarding a downlink data link delivery status event received by the session management function from another network entity of the communications network; as well as receiving a subscription request for notifications regarding downlink data link delivery status events from another network entity of the communications network; as well as Providing a notification to the policy control function regarding a subscription request for notifications received from the other network entity regarding downlink data delivery status events, the notifications including identifying a source of downlink Internet Protocol or Ethernet traffic associated with the downlink data delivery status event.
17. The method of claim 16, wherein the another network entity comprises a Universal Data Management (UDM).
18. The method of claim 16, wherein the providing comprises sending the notification using an Npcf_SMPolicyControl_UpdateNotify service operation. The method of claim 16 , wherein the notification includes parameters received in the subscription request.
20. The method of claim 19, wherein the parameters include at least one of: at least one packet filter and a target address for notifications regarding downlink data delivery status events.
21. The method according to claim 20, further comprising: receiving, from the policy control function, policy and charging control rules including the at least one packet filter; as well as User plane functions of the communication network are configured using the policy and charging control rules.
22. The method of claim 21, wherein the policy and charging control rules further include at least one of: an indication of applying extended buffering to data packets received from a source of downlink Internet Protocol or Ethernet traffic, an information element indicating an application function subscription to receive notifications about downlink data delivery status events, or the target address.
23. An apparatus for a communication network, comprising: at least one processor; as well as at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, when the computer program code is executed, cause the apparatus to at least perform, using the at least one processor: receiving a policy control request trigger from a policy control function, the policy control request trigger requesting notification of a subscription request for notifications of downlink data link delivery status events received by a session management function from other network entities of the communications network; as well as receiving a subscription request for notifications regarding downlink data link delivery status events from another network entity; as well as Providing a notification to the policy control function regarding a subscription request for notifications received from the other network entity regarding downlink data delivery status events, wherein the notification includes identifying a source of downlink Internet Protocol or Ethernet traffic associated with the downlink data delivery status event.
24. The apparatus of claim 23, wherein the another network entity comprises a Universal Data Management (UDM).
25. The apparatus of claim 23, wherein the providing comprises sending the notification using an Npcf_SMPolicyControl_UpdateNotify service operation.
26. The apparatus of claim 23, wherein the notification comprises parameters included in the subscription request.
27. The apparatus of claim 26, wherein the parameters include at least one of: at least one packet filter and a target address for notification regarding the downlink data delivery status event.
28. The apparatus of claim 27, wherein the at least one memory and the computer program code are configured to, when the computer program code is executed, cause the apparatus to at least perform, with the at least one processor: receiving, from the policy control function, policy and charging control rules including the at least one packet filter; and User plane functions of the communication network are configured using the policy and charging control rules.
29. The apparatus of claim 28, wherein the policy and charging control rules further include at least one of: an indication of applying extended buffering to data packets received from a source of downlink Internet Protocol or Ethernet traffic, an information element indicating an application function subscription to receive notifications about downlink data delivery status events, or the target address.
30. An apparatus for a communication network, the apparatus comprising: Session management features, including: means for receiving from a policy control function a new policy control request trigger for subscription to notifications of subscription requests received by the session management function from other network entities of the communications network regarding downlink data link delivery status events; and means for receiving a subscription request for notifications regarding downlink data link delivery status events from another network entity; and Means for providing notification to the policy control function regarding the subscription regarding downlink data delivery status events received from the other network entity, wherein the notification includes identifying a source of downlink Internet Protocol or Ethernet traffic associated with the downlink data delivery status events.
31. A computer readable medium comprising program instructions stored thereon, the program instructions being used to execute the method according to any one of claims 1-7 or 16-22.
