Apparatus, method and system for handling events in mobile communication network

Abstract

The invention relates to the field of telecommunications. A control plane (CP) entity is disclosed, the CP entity being configured to generate a first list and a second list, and to transmit the first list and the second list to a user plane (UP) entity. The first list indicates a plurality of network events and a plurality of corresponding actions that are allowed to be performed by the UP entity. The second list indicates a plurality of network functions for notifying the UP entity of the plurality of network events. The UP entity sends one or more subscription requests for subscribing to one or more of the plurality of network events based on the first list and the second list. When a network event trigger is received, the UP entity may be used to take a corresponding action according to the first list. In this manner, decisions may be simplified or dynamically made, and quality of service (QoS) may be improved.

Description

Technical Field

[0001] This invention generally relates to the field of communication technology. For example, this invention provides an apparatus, method, and system for processing network events in a mobile communication network. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) standards, versions 15-18, introduced a Service Based Architecture (SBA) for fifth-generation (5G) mobile communication systems, supporting three main types of communication services: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (uRLLC), and massive machine-type communications (mMTC). Standardized network functions (NFs) with service-based interfaces (SBIs) were defined for message exchange between these NFs. In sixth-generation (6G) mobile communication systems, support for more advanced applications and services was proposed, such as holographic telepresence, immersive experiences, and digital twins. Technological advancements made 6G possible, with billions of sophisticated mobile devices connected through communication networks, placing stringent performance demands. In addition, applications and services such as autonomous driving, tactile internet, eXtreme Reality (XR), Internet of Things (IoT), and holographic communication will generate, collect, and process massive amounts of data. Besides facilitating real-time device-to-device communication, they will also require extremely low latency to operate and control devices such as sensors and actuators.

[0003] The aforementioned use cases impose many new and stringent requirements on the underlying communication networks, such as faster signal processing, higher data rates, ultra-low latency, and enhanced security, privacy, and reliability, in order to provide users with a seamless end-to-end (e2e) experience. These extreme requirements increase the need for high-data-rate, low-latency, and high-capacity communication networks to provide extreme coverage and performance guarantees.

[0004] 3GPP 5G networks provide PDU connection services that allow user equipment (UE) to exchange Protocol Data Units (PDUs) with the data network (DNN). To do this, the UE requests to establish a PDU session in order to exchange the necessary data packets with the DNN. A control plane (CP) entity called the Session Management Function (SMF) is responsible for verifying the UE's subscription information and approving the session establishment request. Upon receiving the session establishment request, the SMF retrieves the necessary UE subscription data from the Unified Data Management (UDM) and Quality of Service (QoS) and policy data from the Policy Control Function (PCF), and verifies the compliance of the UE's session establishment request. Once approved, the SMF generates Packet Detection Rule (PDR), Forwarding Action Rule (FAR), Quality of Service Enforcement Rule (QER), Usage Reporting Rule (URR), Buffering Action Rule (BAR), and PFCP session context for the PDU session. The User Plane Function (UPF) (as an example of a user plane (UP)NF) handles all user traffic in the mobile network. Therefore, once the PDU session rules are generated, the SMF selects the UPF and passes the PDU session rules and configuration via the designated N4 interface to add / update / delete rules. Upon receiving a PDU belonging to a configured session from the New Generation Radio Access Network (NG-RAN), the UPF processes the packet by applying the necessary pre-configured rules from the SMF and forwards it to the DNN based on the FAR.

[0005] 3GPP 5G SBA enriches NFs to provide services such as event exposure to interested CP NFs. Any CP NF can request / subscribe to receive information / notifications from NFs that generate information of interest. When a CP NF (e.g., SMF) receives a request for information via SBI, a response is returned almost immediately along with the requested information. However, for subscriptions, the subscribing NF sends a subscription request to a notifying NF (e.g., Network Data Analytics Function, NWDAF), which will notify the subscribing NF of any information of interest. Upon receiving the subscription request, the notifying NF adds the subscribing NF to its subscriber list and publishes a notification to all subscribed NFs when any event of interest occurs. Similar to CP NFs, UPFs also provide the "Nupf_EventExposure" service, which exposes UP-related information, such as events on a PDU session, to interested CP NFs. Summary of the Invention

[0006] Traditionally, uRLLC can be supported by providing redundant transmission for uRLLC sessions within the UP. To support uRLLC sessions, the UE can initiate dual connectivity with two redundant PDU sessions, either by utilizing redundancy supported by the transport layer or by sending data packets through two N3 and N9 tunnels between the NG-RAN and the Protocol Session Anchor (PSA) UPF. With dual connectivity, the mobile network establishes two independent PDU sessions to ensure higher reliability through different combinations of the DNN and Single-Network Slice Selection Assistance Information (S-NSSAI). In the case of transport layer-supported uRLLC, the SMF selects the UPF with redundant transmission capabilities. That is, the UPF can copy DL packets at the transport layer and forward them to the NG-RAN, which then eliminates duplicate packets before forwarding them to the UE. The NG-RAN copies UL packets and forwards them to the UPF, which then eliminates duplicate packets and forwards them to the designated DNN. In the dual N3 and N9 tunnel configuration, the SMF configures different routing information in the tunnels mapped to disjoint transport layer paths. During the dual-tunnel configuration, when the UPF receives DL packets, the PSA UPF duplicates these packets and assigns the same GTP-U sequence number to facilitate redundant transmission. The NG-RAN eliminates duplicate packets and then forwards them to the UE. For UL packets, the NG-RAN duplicates the packets, assigns the same GTP-U sequence number, and then forwards them to the UPF through the two N3 tunnels respectively. The UPF eliminates duplicate packets and then forwards them to the designated DNN.

[0007] Some CP NFs (e.g., NWDAFs and Application Functions (AFs)) are also interested in information generated in UP NFs. However, due to the CP-UP separation architecture principle in 5G (and above), UPFs are primarily able to access SMFs and can restrict access to other CP NFs to provide simple event exposure. However, UPFs cannot subscribe to events exposed by any CP NF.

[0008] In current mobile networks, uRLLC support is primarily based on redundant transmission. However, in 5G and 6G, billions of devices are expected to connect to mobile networks, so redundant transmission cannot scale well with billions of connections having stringent performance requirements.

[0009] CP NFs possess decision-making autonomy when events (e.g., network-related events) occur; UP NFs, on the other hand, wait to receive and execute these decisions. However, decision-making does not occur at runtime. Furthermore, any changes to an ongoing PDU session involve a series of decisions between CP NFs (e.g., long paths in the decision-making process: UPF-SMF-PCF-AF-PCF-SMF-UPF), which not only increases signaling traffic but also leads to increased latency in responding to any events in the UP. This unintentionally hinders any dynamic or emergency responses that UPs can make during changes in network behavior (e.g., changes in channel conditions, user density fluctuations, congestion, etc.).

[0010] Currently, SMFs are allowed to handle subscriptions from CP NFs to UPFs. However, UPFs cannot access any services that can identify events that may occur in the UP. CP NFs identify UP events or receive event notifications from NFs that generate such information, and then invoke a series of NFs to decide how to handle the identified events. Because the CP NFs responsible for user plane decisions are reactive, they introduce latency into the user's response to events, thus impacting the uRLLC and QoS requirements anticipated by many 5G and 6G applications.

[0011] For many applications, such as autonomous driving and holographic communication, timely arrival and reliable packet transmission are crucial for synchronizing data collected from multiple sources and making real-time decisions. Therefore, regardless of changes in network behavior, faster and more reliable packet transmission is needed between end users or between end users and service providers. This is particularly critical for some applications, as latency from mobile networks can have adverse effects such as collisions and injuries.

[0012] Currently, if the SMF fails or crashes, or if the UPF loses connection with the SMF, the PDU session is abandoned until a new SMF takes over. The PDU session is then restarted in the same / new UPF. This can impact reliability, which is critical for uRLLC applications.

[0013] In summary, current UP NFs cannot leverage CP decisions and event notifications to dynamically / in real-time adapt to traffic characteristics and / or network conditions.

[0014] In view of the above-mentioned problems and drawbacks, the present invention aims to enhance the UP and CP NFs used in mobile communication systems, thereby improving the response latency to various events in the network. The object of the present invention is to achieve dynamic and real-time response when the UP NF processes events.

[0015] These and other objectives are achieved by the invention, for example, as described in the independent claims. Advantageous implementations are further described in the dependent claims.

[0016] A first aspect of the present invention provides a CP entity for a telecommunications network. The CP entity is configured to generate a first list indicating multiple events and corresponding actions permitted to be performed by a UP entity; and to generate a second list indicating multiple NF entities for notifying the UP entity of the multiple events. The CP entity is further configured to send the first list and the second list to the UP entity.

[0017] It should be noted that the first list indicates the plurality of events and the plurality of corresponding actions (or includes information about the plurality of events and the plurality of corresponding actions). The second list indicates the plurality of NF entities used to notify the UP entity of the plurality of events (or includes information about the plurality of NF entities used to notify the UP entity of the plurality of events). In this invention, the CP entity may be referred to as CP NF, the UP entity may be referred to as UP NF, and the general NF entity may be abbreviated as NF. The event can be any event that may occur in the network. For example, the event may be related to the network, user behavior, or application / service. In this invention, the event may be referred to as a "network event". Optionally, the event can be identified by a corresponding event ID.

[0018] Optionally, the first list and the second list can be combined into a hybrid list. When sending the first list and the second list, the CP entity can be used to send the hybrid list to the UP entity.

[0019] Optionally, the plurality of NF entities used to notify the UP entity of the plurality of events can be simply referred to as "notification NF entities". The CP entity can be one of the notification NF entities.

[0020] Optionally, the CP entity may be an SMF, and the UP entity may be a UPF.

[0021] The CP NF pre-configures the plurality of events and the plurality of corresponding actions in the UP NF, making event processing in the user plane more efficient, as the user plane becomes autonomous by executing dynamic and real-time actions to process events in the network according to the first list. This improves the QoS delivered to the end user.

[0022] In one implementation of the first aspect, each action may include one or more instructions to be executed by the UP entity in response to a corresponding event in the network.

[0023] For example, the one or more instructions may include one or more PDU session rules (e.g., FAR, QER, BAR rules).

[0024] In another implementation of the first aspect, the CP entity can be used to generate the first list and the second list in the following manner:

[0025] - Determine the multiple events that are allowed to be notified to the UP entity based on network configuration information;

[0026] - Generate the multiple corresponding actions that the UP entity can perform in response to the determined multiple events;

[0027] - Based on the determined multiple events, obtain a list of NF entities to notify the UP entity.

[0028] Optionally, the network configuration information may include UE subscription information and / or policy information.

[0029] In another implementation of the first aspect, the CP entity may be used to send the first list and the second list to the UP entity via a dedicated interface (optionally via the N4 interface).

[0030] In another implementation of the first aspect, the CP entity can be used for:

[0031] - Receive one or more subscription requests from the UP entity for subscribing to one or more of the plurality of events;

[0032] - Send the one or more subscription requests to one or more corresponding NF entities.

[0033] In another implementation of the first aspect, the CP entity may be used to add and / or modify one or more parameters in the received subscription requests before sending the one or more subscription requests.

[0034] In another implementation of the first aspect, the CP entity may be used to send the first list and the second list to the UP entity during the lifetime of a session (e.g., a PDU session), the lifetime of service delivery, or the lifetime of the UP entity.

[0035] A second aspect of the invention provides a UP entity for a telecommunications network. The UP entity is configured to receive a first list and a second list from a CP entity, the first list indicating multiple events and corresponding actions permitted to be performed by the UP entity, and the second list indicating multiple NF entities for notifying the UP entity of the multiple events. The UP entity is further configured to send one or more subscription requests for subscribing to one or more of the multiple events based on the first list and / or the second list.

[0036] In this way, based on the first and second lists, the UP entity can become autonomous in performing dynamic and real-time actions to process events according to the first and / or second lists. Furthermore, since lengthy decision-making processes on the control plane can be avoided, processing latency when events occur can be reduced. Therefore, the QoS for end users can be improved.

[0037] Optionally, the UP entity can be used to receive a mixed list from the CP entity. The mixed list may include the first list and the second list.

[0038] Optionally, the CP entity may be an SMF, and the UP entity may be a UPF.

[0039] Optionally, the one or more subscription requests can be sent via a dedicated interface (e.g., the Nupf SBI interface).

[0040] In this way, Nupf SBI can be enhanced, not only providing user plane-related information to the control plane but also allowing the user plane to subscribe to and receive event notifications from the control plane. This reduces signaling traffic and latency between the control plane and the user plane when responding to events.

[0041] In one implementation of the second aspect, the UP entity can be used to send a corresponding subscription request to the CP entity.

[0042] In another implementation of the second aspect, the UP entity can be used to send a corresponding subscription request to the corresponding NF entity based on the second list.

[0043] In another implementation of the second aspect, the UP entity can also be used for events triggered by notifications from the corresponding NF entity or the CP entity.

[0044] In another implementation of the second aspect, the UP entity can also be used for:

[0045] - Determine whether the triggered event is in the first list and / or whether the triggered event originates from the corresponding NF entity in the second list;

[0046] - In response to determining that the triggered event is in the first list and / or the triggered event originates from the corresponding NF in the second list, perform the corresponding action according to the first list.

[0047] A third aspect of the present invention provides a system. The system includes one or more CP entities according to the first aspect or any implementation thereof, and one or more UP entities according to the second aspect or any implementation thereof.

[0048] The system may further include one or more notification NF entities. The one or more UP entities may send one or more subscription requests to the one or more CP entities and / or the one or more notification NF entities for subscribing to one or more of the plurality of events, based on the first list and / or the second list.

[0049] In other words, a UP entity can send a subscription request to a CP entity to subscribe to a specific event. This can occur in two scenarios: Scenario I: The CP entity is one of a plurality of notification NF entities used to notify the UP entity of the event; or Scenario II: The UP entity does not have the interface, permission, or access rights to all the information required in the subscription request and cannot directly communicate with the corresponding notification NF entity used to notify the UP entity of the event. In Scenario II, the CP entity can forward the subscription request to the corresponding notification NF entity (on behalf of the UP entity). Before forwarding the subscription request, the CP entity can modify the subscription request (e.g., add any missing information to the subscription request).

[0050] Alternatively or additionally, the UP entity may send a subscription request to the corresponding notification NF entity for subscribing to the corresponding event. This may occur when the UP entity has an interface to communicate with the corresponding notification NF entity.

[0051] A fourth aspect of the present invention provides a method for use in a telecommunications network. The method includes the following steps:

[0052] - The CP entity generates a first list, which indicates multiple events and corresponding actions that allow the user-plane (UP) entity to perform.

[0053] - The CP entity generates a second list, which indicates multiple network function (NF) entities for notifying the UP entity of the multiple events;

[0054] - The CP entity sends the first list and the second list to the UP entity.

[0055] In one implementation of the fourth aspect, each action may include one or more instructions to be executed by the UP entity in response to the corresponding event.

[0056] In another implementation of the fourth aspect, the step of generating the first list and the second list may include:

[0057] - Determine the multiple events that are allowed to be notified to the UP entity based on network configuration information;

[0058] - Generate the multiple corresponding actions that the UP entity can perform in response to the determined multiple events;

[0059] - Based on the determined multiple events, obtain a list of NF entities to notify the UP entity.

[0060] In another implementation of the fourth aspect, the first list and the second list may be sent by the CP entity to the UP entity via a dedicated interface (optionally via the N4 interface).

[0061] In another implementation of the fourth aspect, the method may further include:

[0062] - The CP entity receives from the UP entity one or more subscription requests for subscribing to one or more of the plurality of events;

[0063] - The CP entity sends the one or more subscription requests to one or more corresponding NF entities.

[0064] In another implementation of the fourth aspect, before sending the one or more subscription requests, the method may further include: the CP entity (as an authorizing entity) adding and / or modifying one or more parameters in the received one or more subscription requests.

[0065] In another implementation of the fourth aspect, the first list and the second list may be sent by the CP entity to the UP entity during the lifetime of the session (e.g., PDU session), the lifetime of the service delivery, or the lifetime of the UP entity.

[0066] The method described in the fourth aspect can have the same features and advantages as the CP entity described in the first aspect.

[0067] A fifth aspect of the present invention provides a method for use in a telecommunications network. The method includes the following steps:

[0068] - The UP entity receives a first list from the CP entity, the first list indicating multiple events and multiple corresponding actions that the UP entity is allowed to perform;

[0069] - The UP entity receives a second list from the CP entity, the second list indicating multiple NF entities;

[0070] - The UP entity sends one or more subscription requests for subscribing to one or more of the plurality of events based on the first list and / or the second list.

[0071] In one implementation of the fifth aspect, the UP entity may send a corresponding subscription request to the CP entity.

[0072] In another implementation of the fifth aspect, the UP entity may send a corresponding subscription request to the corresponding NF entity based on the second list.

[0073] In another implementation of the fifth aspect, the method may further include: the UP entity receiving a notification of a triggered event from the corresponding NF entity or the CP entity.

[0074] In another implementation of the fifth aspect, the method may further include: the UP entity determining whether the triggered event is in the first list and / or whether the triggered event originates from the corresponding NF entity in the second list. In response to determining that the triggered event is in the first list and / or that the triggered event originates from the corresponding NF in the second list, the method may further include: the UP entity performing a corresponding action based on the first list.

[0075] The method described in the fifth aspect can have the same features and advantages as the UP entity described in the second aspect.

[0076] A sixth aspect of the invention provides a computer program including program code for performing the method according to the fourth aspect or any implementation thereof.

[0077] A seventh aspect of the invention provides a computer program including program code for performing the method according to the fifth aspect or any implementation thereof.

[0078] The eighth aspect of the invention provides a non-transitory storage medium for storing executable program code, which, when executed by a processor, causes the method described according to the fourth aspect or any implementation thereof to be performed.

[0079] A ninth aspect of the invention provides a non-transitory storage medium for storing executable program code, which, when executed by a processor, causes the method described according to the fifth aspect or any implementation thereof to be performed.

[0080] The tenth aspect of the present invention provides a chipset for storing executable program code, which, when executed by the chipset, causes the method described in accordance with the fourth aspect or any implementation thereof to be performed.

[0081] The eleventh aspect of the present invention provides a chipset for storing executable program code, which, when executed by the chipset, causes the method described in accordance with the fifth aspect or any implementation thereof to be performed.

[0082] It should be noted that all entities, elements, units, functions, and modules described in this application can be implemented in software or hardware elements or any combination thereof. All steps performed by the various entities described in this application, and the functions described for performance by the various entities, are intended to indicate that the respective entities are suitable for or used to perform the corresponding steps and functions. Although specific functions or steps to be performed by external entities are not reflected in the detailed description of the specific elements of the entity performing those steps or functions in the following description of the invention, those skilled in the art will understand that these methods and functions can be implemented by the corresponding software or hardware elements or any combination thereof. Attached Figure Description

[0083] The following description, in conjunction with the accompanying figures, illustrates the above aspects and implementation methods.

[0084] Figure 1 An example of the association between network entities in a telecommunications network is shown;

[0085] Figure 2 The CP entity and UP entity according to the present invention are shown;

[0086] Figure 3 An exemplary signaling flow according to the present invention is shown in which the CP entity notifies the UP entity of the first list and the second list;

[0087] Figure 4 Exemplary signaling for UP entity subscription network events according to the present invention is shown;

[0088] Figure 5An example of event processing performed by a UP entity according to the present invention is shown;

[0089] Figure 6 This illustrates an application scenario of the present invention;

[0090] Figure 7 A diagram illustrating a method according to the present invention is shown;

[0091] Figure 8 A diagram illustrating another method according to the present invention is shown. Detailed Implementation

[0092] The key terms and their abbreviations used in this invention are listed below: 3GPP; Access and Mobility Management Function – AMF; Application Function – AF; Buffer Action Rule – BAR; Control Plane – CP; Data Network – DN; Edge Application Server – EAS; Forwarding Action Rule – FAR; Network Data Analysis Function – NWDAF; Network Exposure Function – NEF; Network Function – NF; Packet Inspection Rule – PDR; Management Plane – MP; Packet Forwarding Control Protocol – PFCP; Policy Control Function – PCF; Protocol Data Unit – PDU; PDU Session Anchor – PSA; Quality of Service – QoS; Quality of Service Enforcement Rule – QER; Reinforcement Learning – RL; Service-Based Architecture – SBA; Service-Based Interface – SBI; Session Management Function – SMF; Ultra-Reliable Low-Latency Communication – uRLLC; Unified Data Management – ​​UDM; Uplink Classifier – UL CL; Usage Reporting Rule – URR; User Equipment – ​​UE; User Plane – UP.

[0093] Figure 1 An example of the association between network entities in a telecommunications network is shown.

[0094] The telecommunications network can be a mobile communication network defined by 3GPP, and can be referred to as a 3GPP system. For example, a 3GPP system can be a 5G system, a 6G system, or any next-generation system (5G or above). It should be understood that this invention can be applied not only to 3GPP systems, but also to other communication systems with similar technical architectures to 3GPP systems. As shown in Figure 1, a 3GPP system includes multiple NFs, such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Exposure Function (NEF), Network Repository Function (NRF), Policy Control Function (PCF), Network Data Collection and Analysis Function (NWDAF), Application Function (AF), and Unified Data Management (UDM). These NFs are implemented through... Figure 1 The dedicated interface interconnects are shown. Due to the separation of the control plane and user plane in the 3GPP system, there are at least two possible network functions: control plane network function (CP NF) and user plane network function (UP NF). AMF, SMF, NEF, UDM, NRF, PCF, and NWDAF are examples of CP NF. UPF is an example of UP NF.

[0095] UPF is used to handle UE data sessions in the network. However, the CP (Consulate) is obligated to make decisions when it discovers events of interest in the UP (Uploader). Traditionally, when an event occurs in the network, the UP NF (e.g., UPF) simply waits for the CP's decision. In this invention, a scheme is proposed to provide the UP with a degree of autonomy in responding to certain events (potentially in real-time), responses to which may be pre-configured by the CP before the UE session begins. Thus, this invention allows the UP NF to be more dynamic and flexible in responding to events observed in the network. This also prevents any delays caused by runtime decisions in the CP.

[0096] Figure 2CP entity 210 and UP entity 220 according to the present invention are shown. As an example, another CP entity 230 is shown. For readability, in this invention, CP entity 210 may correspond to SMF 210, another CP entity 230 may correspond to NWDAF, and UP entity 220 may correspond to UPF 220. However, it should be understood that, where applicable, the present invention can be applied to any CP NF and UP NF. SMF 210 and UPF 220 can constitute system 200.

[0097] SMF 210 is used to generate a first list. The first list indicates multiple network events and multiple corresponding actions that the UPF 220 is allowed to perform. For example, the first list may include information such as {first event, first action; second event, second action; ...}. In one possible example, the possible list of network events and the list of actions may be predefined in technical specifications such as 3GPP. SMF 210 can be used to determine the actions that the UPF is allowed to perform for events in the network. The result of this determination can be reflected in the first list. Network events and corresponding actions can be associated with their corresponding type identifiers (IDs) in the first list. For example, an example of the first list could be {event ID#m, action ID#n; ...}, indicating that network event ID#m is allowed to perform action ID#n. The present invention does not limit the implementation of these lists, and the information may not even be limited to lists, but may include any type of data structure that can convey the association between events and corresponding actions.

[0098] SMF 210 is also used to generate a second list. The second list indicates multiple NF entities used to notify UPF 220 of multiple network events. For example, the second list may include information such as {first event, first source NF; second event, second source NF; ...}. In one possible example, the event and source NF may be identified by corresponding IDs. The association between IDs and actual events and source NFs can be predefined in technical specifications such as 3GPP.

[0099] Then, SMF 210 is used to send the first list and the second list to UPF 220. For example, the first list and the second list can be combined and sent via a single signaling 201. Optionally, the first list and the second list can be sent before and / or during the session (including modifications to these lists). For example, one example could be sending the first list and the second list via an N4 session establishment / modification request message.

[0100] After receiving the first list and the second list, UPF 220 is used to send one or more subscription requests 202 for subscribing to one or more network events among a plurality of network events based on the first list and / or the second list.

[0101] Optionally, UPF 220 can be used to send a subscription request 202 to SMF 210 for subscribing to network events. When the SMF is not responsible for notifying network events, SMF 210 can be used to forward subscription request 202 to the target NF 230 (e.g., NWDAF 230). Optionally, SMF 210 can be used to add or modify one or more parameters in subscription request 202 and forward the modified subscription request 202' to the target NF 230. Possible parameters that SMF 210 can add or modify may include, but are not limited to: S-NSSAI, service area, UE ID, application ID, UE location, UE subscription INFO, etc. When a network event occurs, UPF 220 can receive notification message 203. Notification message 203 may come from the corresponding NF 230 or from SMF 210. In the latter case, the corresponding NF 230 may send notification message 203 to SMF 210, and SMF 210 may forward notification message 203 to UPF 220.

[0102] It should be noted that UPF 220 can send a first subscription request to SMF 210 for subscribing to a first network event, and a second subscription request to target NF 230 for subscribing to a second network event. This is not a limitation in this invention.

[0103] Examples of the first and second lists can be shown in Table 1.

[0104]

[0105] The "Event" information in the first column and the "Action" information in the second column of Table 1 can constitute a first list. The "Source" information in the first column of Table 1 can constitute a second list. It should be noted that Table 1 only provides possible examples of network events, sources, and actions. It should be understood that other network events, sources, and actions may also be included, and any event, source, or action mentioned in Table 1 may be modified or deleted. Furthermore, the actions in Table 1 are for illustrative purposes only. It should be understood that other possible actions may be used instead of the actions defined in Table 1. Optionally, CP entity 210 may determine different actions for the same network event.

[0106] Figure 3 An exemplary signaling flow is shown in which a CP entity notifies a first list and a second list to an UP entity according to the present invention. Figure 3 Depicting what can correspond to Figure 2 The SMF of CP entity 210 in the middle, and can correspond to Figure 2 The UPF of UP entity 220 in the diagram. Corresponding components can have the same characteristics and can function in a similar way.

[0107] As shown in Figure 3, in order to generate the first and second lists, the SMF can be used to retrieve UE subscription information from the UDM. To do this, the SMF can send a UE subscription information request 303 to the UDM and receive a UE subscription information response 304 from the UDM.

[0108] The SMF can also be used to retrieve QoS and policy-based information (e.g., PCC rules) from the PCF. To do this, the SMF can send a policy information request 305 to the PCF and receive a policy information response 306 from the PCF.

[0109] Based on UE subscription information, policy information, and any other types of information obtained from the corresponding CP / MP entity configured by the network operator, the SMF can determine the events that allow the UPF to respond.

[0110] Optionally, when the UE sends a PDU session establishment / modification request, or when the SMF relocates the UPF for the UE, the event can trigger the retrieval of subscription information and policy information (S330).

[0111] Optionally, the SMF can query the NEF or a similar CP entity to identify the corresponding list of NFs that the UPF should subscribe to in order to receive previously determined necessary event notifications (or triggers). To this end, the SMF can send request 307 to the NEF to request information about the NFs notifying network events and the subscription configuration. In response, the SMF can receive corresponding information 308 from the NEF.

[0112] Then, the SMF can be used to generate a first list in step S310. Optionally, the SMF can be used to create PDU session rules. Then, the SMF can be used to generate a second list in step S320. For example, the SMF can be used to create a list of CP NFs and their associated specific instances, such that the UPF can subscribe to receive event triggers. This invention does not limit the order in which the lists and PDU session rules are generated and / or sent to the UP.

[0113] The SMF then sends the first and second lists to the UPF. Optionally, the first and second lists can be sent via an N4 session establishment / modification request. Alternatively, the first and second lists can be sent when the UPF is launched / deployed in the telecommunications network or during the session's lifetime. The CP NF (e.g., the SMF) can be used to update the first and / or second lists by sending updated first and / or updated second lists. The CP NF (e.g., the SMF) can be used to remove the first and / or second lists by sending corresponding instructions / configurations to the UP NF (e.g., the UPF), thereby deleting (or deactivating) the first and / or second lists.

[0114] Figure 4 An exemplary signaling for a UP entity to subscribe to network events according to the present invention is shown. Figure 4 Depicting what can correspond to Figure 2 The SMF of CP entity 210 in the middle, and can correspond to Figure 2 The UPF of UP entity 220 in the middle. Figures 1 to 4 The corresponding components in the model can have the same characteristics and can function in a similar way.

[0115] as follows Figure 3 As shown, UPF can be used to store a primary list of events for taking action. There are at least three possible ways to subscribe to network events.

[0116] In the first possible approach, UPF creates one or more subscription requests based on the received second list. UPF can then use the second list ( Figure 3 (Not shown in the image) Send a subscription request directly to the target NF.

[0117] In the second possible approach, the UPF can send a subscription request 401 to the SMF. For example, subscription request 401 could be called an "Nsmf_EventExposure_Subscribe_Request" message, which may include the event ID to be notified. When the SMF receives subscription request 401 from the UPF, it can forward it to a target NF, such as the NWDAF that publishes the event ID information contained in the subscription request message. The SMF can acknowledge the request by replying to the UPF via a so-called "Nsmf_EventExposure_Subscribe_Response" message 402. The forwarded subscription request 403 could be called an "Nnwdaf_AnalyticsSubscription_Subscribe" message 403 that includes the notification target address (e.g., which may be equal to the UPF). Optionally, the SMF can add or modify one or more parameters (e.g., filtering information) in subscription request 401. The NWDAF can acknowledge the forwarded subscription request 403 by replying to the SMF with a "Nnwdaf_AnalyticsSubscription_Response".

[0118] In the third possible approach, the SMF (on behalf of the UPF) can create a subscription request. In this case, the UPF does not necessarily send the subscription request 401 itself. The SMF can, for example, notify the UPF that a subscription request has been sent via the "Nsmf_EventExposure_Subscribe_Response" message 402.

[0119] In step S410, the NWDAF and other CP NFs can monitor and / or analyze information to locate subscription events and notify the UPF when such subscription events are triggered (or discovered). For example, the NWDAF can notify the UPF via the "Nnwdaf_AnalyticsSubscription_Notify" message 405. In step S420, the UPF can analyze the triggered events and perform corresponding actions if the triggered events match the first and second lists.

[0120] It should be noted that, Figure 4 The names of messages 401, 402, 403, 404, and 405 are for illustrative purposes only. It should be understood that other similar messages may also be used.

[0121] Figure 5 An example of event handling performed by the UP entity according to the present invention is shown. Figure 4 The UP entity in the middle is based on Figure 2 The UP entity 220 in the example is shown as UPF 220. Figures 1 to 5 The corresponding components in the model can have the same characteristics and can function in a similar way.

[0122] like Figure 5 As depicted, UPF 220 can receive event notifications. These notifications may include the triggered event and its source. The source may be, for example, an SMF, AMF, NWDAF, PCF, etc. Where possible, UPF 220 can internally trigger events (i.e., UPF events). Once an incoming event is received or identified, UPF 220 can attempt to match it with multiple network events in a first list. If the incoming event matches a network event in the first list, a corresponding action is applied according to the first list. This corresponding action may include one or more steps that UPF 220 can perform in response to the incoming event. UPF 220 can also be used to report the incoming event and the action taken to the SMF. Optionally, UPF 220 may not report the incoming event and action immediately. UPF 220 can be used to periodically report one or more incoming events, and one or more actions taken within a predefined time period. If an incoming event does not match any event in the first list, UPF 220 takes no action. Conversely, the UPF 220 can report incoming events to the SMF and await a decision from the control plane on how to respond to the event.

[0123] Figure 6The application scenario of this invention is illustrated. In telecommunications networks such as 3GPP systems, the UPF performs traffic classification and traffic redirection. For example, the UPF determines whether traffic should flow to the DN or the nearest Edge Application Server (EAS). According to this invention, the SMF generates a first list and a second list and sends them to the UPF. The UPF subscribes to necessary event triggers generated by the CP NF. For example, when a specified EAS fails, the SMF can create an action for the event. For example, the action might involve specifying a DNAI that can be used as a backup for forwarding user traffic. That is, the first list may include items such as {Event: Specified EAS fails -> Action: Change DNAI (e.g., associated with a backup EAS)}. Once the corresponding event trigger indicating that the current EAS has failed is received from the CP NF (e.g., via the NEF or via the PCF from the AF), the UPF can take a timely action, such as switching to a different DNAI (e.g., associated with a backup EAS).

[0124] Optionally, a 3GPP system may include multiple UPFs. Although Figure 6 The example depicts two UPFs, but hundreds of UPFs may be deployed in a 3GPP system to serve a large number of connected devices. For instance, a UPF called an uplink (UL) classifier (CL) can be used to divert uplink traffic based on filtering rules provided by the SMF. Another UPF called a PDU Session Anchor (PSA) can be used to terminate the N6 interface of a PDU session within the core network.

[0125] By applying this invention, UL CL UPF can manage event subscriptions and event trigger distribution on behalf of PSAUPF. In this way, signaling traffic in the core network due to UPF subscriptions and event notifications can be reduced.

[0126] Figure 7 A diagram illustrating a method 700 according to the present invention is shown. Method 700 is used in a telecommunications network and includes the following steps:

[0127] - Step 701: The CP entity generates a first list, which indicates multiple network events and multiple corresponding actions that the UP entity is allowed to perform;

[0128] - Step 702: The CP entity generates a second list indicating multiple NF entities used to notify the UP entity of the multiple network events;

[0129] - Step 703: The CP entity sends the first list and the second list to the UP entity.

[0130] Figure 8 A diagram illustrating another method 800 according to the present invention is shown. Method 800 is used in telecommunications networks and includes the following steps:

[0131] - Step 801: The UP entity receives a first list from the CP entity, which indicates multiple network events and multiple corresponding actions that the UP entity is allowed to perform;

[0132] - Step 802: The UP entity receives a second list from the CP entity, the second list indicating multiple NF entities used to notify the UP entity of the multiple network events;

[0133] - Step 803: The UP entity sends one or more subscription requests for subscribing to one or more network events among the plurality of network events based on the first list and / or the second list.

[0134] It should be noted that, from the above Figures 1 to 6 From this perspective, the steps of method 700 and method 800 can have the same functionality and details. Therefore, at this point, the corresponding method implementation will not be described in detail.

[0135] This invention can be applied to any telecommunications network, such as, but not limited to, 5G, 5G-Advanced, 6G communication networks, and any other next-generation mobile communication networks. Application scenarios of this invention include, but are not limited to: Vehicle-to-Everything (V2X) networks, Internet of Things (IoT) networks, and massive Machine-Type Communications (mMTC).

[0136] In summary, this invention provides a scheme for decoupling UP event processing and UP packet processing. This can be achieved, for example, by pre-configuring decisions / responses in the UP NF and directly notifying the UP NF of triggered events from the CP NF. This shortens the processing path for handling the triggered event. Furthermore, this invention can enhance the CP NF (e.g., SMF) and N4 interface to convey information about the relevant NFs and events that the UP NF (e.g., UPF) should subscribe to for the PDU session during PDU session establishment or modification. Additionally, this invention can enhance the CP NF to forward subscription requests from the UP NF to the target CP NF, thereby ensuring security. If necessary, the CP NF can add (or modify) any missing (or incorrect) parameters in the subscription request that are unavailable in the UP NF.

[0137] This invention can also proactively provide the UP NF with the ability to autonomously apply actions in the event of a triggered event. To this end, the CP NF can be enhanced to determine appropriate events that allow the UP NF to respond and to generate actions in advance regarding how the UP NF should respond to the determined events. The N4 interface can be enhanced to provide a first list and a second list to the UP NF during PDU session establishment or modification. The UP NF can be enhanced to receive the first and second lists and to use the Nupf interface to subscribe to network events defined according to the first and / or second lists. After receiving an event trigger through the Nupf interface, the UP NF can autonomously apply the corresponding action.

[0138] The CP and UP entities in this invention may include processing circuitry or chipsets (not shown) for performing, implementing, or initiating the various operations described herein, respectively. The processing circuitry may include hardware and software. The hardware may include analog or digital circuitry, or both. The digital circuitry may include components such as application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), digital signal processors (DSPs), or multi-purpose processors. Optionally, the processing circuitry includes one or more processors and non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code that, when executed by the one or more processors, causes the device to perform, implement, or initiate the operations or methods described herein.

[0139] This invention has been described in conjunction with various embodiments as examples and implementations. However, based on a study of the drawings, the invention, and the independent claims, those skilled in the art will be able to understand and implement other variations when carrying out the claimed invention. In the claims and the description, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" does not exclude a plurality. A single element or other unit may fulfill the function of several entities or items described in the claims. The enumeration of certain measures in dissimilar dependent claims does not imply that combinations of these measures cannot be used in advantageous implementations.

Claims

1. A control plane CP entity (210) for a telecommunications network, characterized in that, The CP entity (210) is used for: Generate a first list indicating multiple events and corresponding actions that allow the user-face UP entity (220) to perform; A second list is generated, which indicates multiple network function (NF) entities (230) for notifying the multiple events to the UP entity (220); Send the first list and the second list (201) to the UP entity (220).

2. The CP entity (210) according to claim 1, characterized in that, Each action includes one or more instructions to be executed by the UP entity (220) in response to the corresponding event.

3. The CP entity (210) according to claim 1 or 2, characterized in that, The CP entity (210) is used to generate the first list and the second list (201) in the following manner: The plurality of events that are permitted to be notified to the UP entity (220) are determined based on network configuration information; Generate the plurality of corresponding actions that allow the UP entity (220) to perform in response to the determined plurality of events; A list of NF entities (230) for notifying the UP entity (220) is obtained based on the determined multiple events.

4. The CP entity (210) according to any one of claims 1 to 3, characterized in that, The CP entity (210) is used to send the first list and the second list (201) to the UP entity (220) via a dedicated interface (optionally via the N4 interface).

5. The CP entity (210) according to any one of claims 1 to 4, characterized in that, The CP entity (210) is used for: Receive one or more subscription requests from the UP entity (220) for subscribing to one or more of the plurality of events; Send the one or more subscription requests to one or more corresponding NF entities (230).

6. The CP entity (210) according to claim 5, characterized in that, Before sending the one or more subscription requests, the CP entity (210) is used to add and / or modify one or more parameters in the one or more received subscription requests.

7. The CP entity (210) according to any one of claims 1 to 6, characterized in that, The CP entity (210) is used to send the first list and the second list (201) to the UP entity (220) during the lifetime of the session, the lifetime of the service delivery, or the lifetime of the UP entity (220).

8. A user plane UP entity for a telecommunications network, characterized in that, The UP entity (220) is used for: Receive a first list from the control plane CP entity (210), the first list indicating multiple events and multiple corresponding actions that the UP entity (220) is allowed to perform; Receive a second list from the CP entity (210), the second list indicating multiple network function (NF) entities (230) for notifying the multiple events to the UP entity (220); One or more subscription requests for subscribing to one or more of the plurality of events are sent based on the first list and / or the second list.

9. The UP entity (220) according to claim 8, characterized in that, The UP entity (220) is used to send a corresponding subscription request to the CP entity (210).

10. The UP entity (220) according to claim 8, characterized in that, The UP entity (220) is used to send a corresponding subscription request to the corresponding NF entity based on the second list (230).

11. The UP entity (220) according to any one of claims 8 to 10, characterized in that, The UP entity (220) is also used for events triggered by notifications from the corresponding NF entity (230) or the CP entity (210).

12. The UP entity (220) according to claim 11, characterized in that, The UP entity (220) is also used for: Determine whether the triggered event is in the first list and / or whether the triggered event originates from the corresponding NF entity in the second list (230); In response to determining that the triggered event is in the first list and / or that the triggered event originates from the corresponding NF (230) in the second list, the corresponding action is performed according to the first list.

13. A system (200), characterized in that, The system includes one or more control plane CP entities (210) according to any one of claims 1 to 7 and one or more user plane UP entities (220) according to any one of claims 8 to 12.

14. A method (700) for use in a telecommunications network, characterized in that, The method includes: The control plane CP entity generates (701) a first list, which indicates multiple events and multiple corresponding actions that the user-plane (UP) entity is allowed to perform; The CP entity generates (702) a second list, the second list indicating multiple network function (NF) entities for notifying the multiple events to the UP entity; The CP entity sends (703) the first list and the second list to the UP entity.

15. A method (800) for use in a telecommunications network, characterized in that, The method includes: The user plane UP entity receives (801) a first list from the control plane CP entity, the first list indicating multiple events and multiple corresponding actions that the UP entity is allowed to perform; The UP entity receives (802) a second list from the CP entity, the second list indicating multiple network function NF entities for notifying the UP entity of the multiple events; The UP entity sends (803) one or more subscription requests for subscribing to one or more of the plurality of events based on the first list and / or the second list.

16. A computer program comprising instructions, characterized in that, When the program is executed by a second computer, it causes the second computer to perform the method according to claim 14 or 15.

Images