WO2021197773A1 - Collecte de données améliorée au niveau d'une fonction analytique de données de réseau (nwdaf) - Google Patents

Collecte de données améliorée au niveau d'une fonction analytique de données de réseau (nwdaf) Download PDF

Info

Publication number
WO2021197773A1
WO2021197773A1 PCT/EP2021/055878 EP2021055878W WO2021197773A1 WO 2021197773 A1 WO2021197773 A1 WO 2021197773A1 EP 2021055878 W EP2021055878 W EP 2021055878W WO 2021197773 A1 WO2021197773 A1 WO 2021197773A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
function
message
subscription
data
Prior art date
Application number
PCT/EP2021/055878
Other languages
English (en)
Inventor
Saurabh Khare
Original Assignee
Nokia Solutions And Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Publication of WO2021197773A1 publication Critical patent/WO2021197773A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management

Definitions

  • 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, 5G system (5GS) technology, new radio (NR) access technology, or other communications systems.
  • LTE Long Term Evolution
  • 5G fifth generation
  • 5GS 5G system
  • NR new radio
  • certain embodiments may relate to systems and/or methods for enhanced data collection at a network data analytics function (NWDAF).
  • NWDAAF network data analytics function
  • Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, and/or fifth generation (5G) radio access technology or 5GS access technology.
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Long Term Evolution
  • E-UTRAN Long Term Evolution Evolved UTRAN
  • LTE-A LTE-Advanced
  • MulteFire LTE-A Pro
  • 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G is mostly built on a 5GS, but a 5G (or NG) network can also build on E-UTRA radio.
  • 5GS may provide bitrates on the order of 10-20 Gbit/s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC) as well as massive machine type communication (mMTC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency-communication
  • mMTC massive machine type communication
  • 5GS is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT).
  • IoT Internet of Things
  • M2M machine- to-machine
  • the nodes that can provide radio access functionality to a user equipment may be named gNB when built on 5GS radio and may be named NG-eNB when built on E-UTRA radio.
  • Fig. 1 illustrates an example of enhanced data collection at a NWDAF, according to some embodiments
  • Fig. 2 illustrates a signal diagram of an example of enhanced data collection at a NWDAF, according to some embodiments
  • Fig. 3 illustrates a signal diagram of another example of enhanced data collection at a NWDAF, according to some embodiments
  • FIG. 4 illustrates an example flow diagram of a method, according to some embodiments.
  • FIG. 5 illustrates an example flow diagram of a method, according to some embodiments.
  • FIG. 6 illustrates an example flow diagram of a method, according to some embodiments.
  • FIG. 7a illustrates an example block diagram of an apparatus, according to an embodiment
  • Fig. 7b illustrates an example block diagram of an apparatus, according to another embodiment.
  • NWDAF network data analytics function
  • NWDAF network data analytics function
  • 5GS has evaluated ways to reduce the load on tracking serving entities (i.e., of collecting data on 5G entities association information), to avoid forcing a NWDAF to subscribe to all events from all network functions (NFs) (e.g., a unified data management (UDM) function, or a network repository function (NRF)), so that the NWDAF may be able to determine the serving entities at any period in time.
  • NFs network functions
  • UDM unified data management
  • NRF network repository function
  • an event associated with an NF may be of interest to multiple NWDAFs that are supporting different analytics identifiers.
  • the NWDAFs may have to make explicit subscription with the NF.
  • the NF may have to send multiple notifications to NWDAFs, such as one for each subscriber.
  • certain mechanisms may be needed to achieve communication efficiencies in large networks comprised of many NF instances and NWDAF instances, to reduce dependency on managing subscriptions because of lifecycle events on aNF and/or a NWDAF, to reduce dependency on managing subscriptions because of a change in serving entities for a UE, and/or to reduce complexity at a NWDAF in determining entities serving a UE or a group of UEs and entities serving an area at a particular time window.
  • an operator may have deployed more than 500 access and mobility management functions (AMFs) and around a similar number of session management functions (SMFs). If one NWDAF is interested in performance data from all the AMFs and SMFs, then the NWDAF may have to send a large quantity of subscribe requests to these AMFs and SMFs. Whenever any of these NFs are down, the NWDAF may have to renew the subscription. If there are multiple NWDAFs, supporting multiple events for data collection from these NFs, this problem of maintaining the subscription may increase significantly. [0018] Some embodiments described herein may provide for enhanced data collection at a NWDAF. For example, certain embodiments may provide a way to make implicit subscriptions at different NFs for a NWDAF.
  • certain embodiments may offload the NWDAF from maintaining multiple subscriptions and their association with different NFs and may create a framework in a service-based architecture (SBA) where NFs may have subscription information to send data to a NWDAF.
  • SBA service-based architecture
  • This may conserve memory resources of the NWDAF and/or computing or processing resources of the NWDAF that would otherwise be consumed as a result of the NWDAF having to maintain the multiple subscriptions and their associations.
  • Fig. 1 illustrates an example of enhanced data collection at a NWDAF, according to some embodiments.
  • Fig. 1 illustrates a NWDAF, aNRF, and aNF in communication.
  • NF profde information which may be used in NRF registration, may be updated with new NWDAF data (nwdafData), as described elsewhere herein.
  • a NF e.g., an AMF, a SMF, an UDM, an unified data repository (UDR), and/or the like
  • NWDAF data may include a default NWDAF configuration identifying where the NF may send notifications (e.g., the configuration may identify an event type (EventType), a notification uniform resource indicator (URI) (NotificationURI), such as a NWDAF URI (nwdaf URI), and/or the like).
  • EventType an event type
  • URI notification uniform resource indicator
  • NWDAF URI nwdaf URI
  • the NWDAF data may be empty while the NF is registering with the NRF.
  • a NF registers with a NRF, and if the NRF already received a subscription request from the NWDAF that is relevant to the NF, then the NRF may return the NWDAF data back to the newly registered NF as part of the response to registration.
  • the NWDAF may send, and the NRF may receive, a message associated with creating a subscription to a NF (e.g., the message may comprise information that identifies the NF and filter criteria for a notification associated with the subscription).
  • the NWDAF may send a service-based interface (SBI) message to the NRF requesting the NRF to create an implicit subscription for one or more requested NFs.
  • a subscription framework e.g., a subscribe/notify framework
  • This SBI message (e.g., Nnrf_UpdateNWDAF_Subscribe, illustrated in, and described with respect to, Fig 2) may comprise information that identifies a target NF (TargetNF), such as an AMF, and filter criteria applicable for the notification.
  • TargetNF target NF
  • Filter criteria may include identification of a target UE (FilterTargetUE), such as criteria to filter based on any UE (AnyUE), a subscription permanent identifier (SUPI) list, a permanent equipment identifier (PEI) list, and/or the like, to filter based on target NF type (FilterTargetNFType), such as AMF, SMF, or UDM types, to filter based on a data network name (DNN) list (FilterDNNList), a filter expiry time (FilterExpiryTime), a filter event type (FilterEventType), and/or the like.
  • a target UE such as criteria to filter based on any UE (AnyUE), a subscription permanent identifier (SUPI) list, a permanent equipment identifier (PEI) list, and/or the like
  • target NFType such as AMF, SMF, or UDM types
  • DNN data network name
  • FilterExpiryTime filter expiry time
  • FilterEventType
  • the NRF may process one or more filter criteria to determine the NF associated with the subscription. For example, the NRF may determine or identify the NFs registered with the NRF where one or more filter criteria are matched. As illustrated at 104, the NRF may send, to the NFs via a message, NWDAF data associated with the subscription (e.g., based on the filter criteria and based on the NFs being registered with the NRF). For example, the NRF may push the NWDAF data with an implicit subscription to the NFs. The NFs can be informed of the implicit subscription via an update response (e.g., a heartbeat response) or an information (INFO) message.
  • an update response e.g., a heartbeat response
  • INFO information
  • the NF may send, to the NWDAF, a notification associated with the subscription (e.g., based on filter criteria associated with the subscription). For example, when the NFs receive implicit subscription details from the NRF having NWDAF details, the NF may process the filter criteria and may start sending a notification to NWDAF directly. When the NWDAF wants to stop collecting data from NFs, it may unsubscribe from the NRF. Based on the unsubscribe, the NRF may update different NFs with the updated implicit subscription information.
  • Fig. 1 is provided as an example. Other examples are possible, according to some embodiments.
  • Fig. 2 illustrates an example signal diagram of an example of enhanced data collection at a NWDAF, according to some embodiments.
  • Fig. 2 illustrates two NFs (AMF1 and AMF2), a NRF, and a NWDAF in communication.
  • the NFs may register with the NRF and may send a heartbeat message (e.g., a periodic message, a scheduled message, and/or the like) to keep registration of the NFs active in the NRF repository.
  • a heartbeat message e.g., a periodic message, a scheduled message, and/or the like
  • the AMF1 and/or the AMF2 may update the NFprofile information to the NRF, where the NFprofile information comprises NF-related information.
  • the NFprofile information for a AMF may include parameters such as nwdafData (e.g., in an nwdafData array): NotificationURI (e.g., that comprises a default notification URI configured in the NF for a NWDAF notification), an application identifier (application ID) (e.g., used by the NWDAF to identify the application service provider and application for the quality of service (QoS) flow), EventType (e.g., load and/or performance event types), DNN, single network slice selection assistance information (SNSSAI), QoS flow identifier (QFI), Internet protocol (IP) filter information (e.g., applicable to a SMF), and/or the like.
  • NotificationURI e.g., that comprises a default notification URI configured in the NF for a NWDAF notification
  • application ID application identifier
  • EventType e.g., load and/or performance event types
  • DNN single network slice selection assistance information
  • SNSSAI single network slice selection
  • NwdafData configured in the NF may provide the default configuration. Additionally, or alternatively, the configuration may be based on network operator policy. If there is no default configuration, then the NF/AMF may send empty data in the nwdafData object in the NFprofile. For a deployment where, for example, there is one NWDAF in a public land mobile network (PLMN), then the network operator may configure an AMF with NWDAF data with slicing key performance indicators (KPIs) or overload situations. The NF may determine and/or provide its own configuration while registering with the NRF. The NRF may override the data or instruct the NF to remove the NWDAF data.
  • KPIs key performance indicators
  • the NRF may respond with a 201 accepted message (e.g., a registration accepted message).
  • a proposed configuration from the NF in the NFprofile may be overwritten by the NRF while providing the response. If the NRF does not suppress this configuration in the registration reply, then the AMF (or an SMF in other scenarios) may start sending notifications to the NWDAF based on the default configuration. As illustrated in the example of Fig. 2, because there is no default configuration, the AMF may send nwdafData as NULL in the NFprofile and the NRF may return the same data back in a registration response. If the NRF has previous NWDAF data (as described with respect to operation 204 below), then the NRF response may be updated with updated nwdafData parameters in the NFprofile.
  • the NWDAF may send a new message to the NRF requesting that the NRF update the NFs with an implicit NWDAF subscription.
  • the message to the NRF may be implemented via a new service in the NRF or a new message in an existing service.
  • a new message may include a posting (POST) message (e.g., a Nnrf_Updatenwdaf_Subscribe message).
  • the message may comprise the following parameters listed in Table 1 below (other parameters not listed in Table 1 are possible):
  • the NRF may return with a 201 accepted message.
  • the NRF may identify the registered NFs applicable for implicit NWDAF subscription (e.g., AMF supported TAI list, event type, etc.). If the fdter criteria are specific to the UE/SUPI, then the information may not be available to the NRF (e.g., a NRF and NF association).
  • the NRF may provide the filter criteria for specific UE/set of UEs to the relevant NFs. A relevant NF may apply the filter criteria and then send the notification to the NWDAF.
  • the NWDAF may send a subscription request to the NRF, and the NRF may send an implicit subscription message to the AMFs registered in a PLMN.
  • the AMF may have the NWDAF subscription data beforehand. More optimization can be applied to narrow down the AMF/NF selections at the NRF for a specific UE/group of UEs. For example, the NWDAF or the NRF may retrieve the serving NF details from a UDM and a request may be sent to the specific NFs.
  • one or more of the NFs may provide notifications (for a previously created subscription) to the NWDAF. Therefore, relevant NFs may have NWDAF data (for an implicit subscription) for the NWDAF. Adding SUPI/set of SUPIs may involve updating NWDAF data to the AMFs.
  • the NRF may send a 200 OK message with updated nwdafData having implicit subscription information.
  • Nfprofile information for AMF1
  • nwdafData that includes call-back information (NotificationCallBack:abc@nqdaf) and/or filter criteria (FilterCriteria)
  • EventType Load, Performance
  • TAI as an area of
  • the NRF may not only forward the subscription parameters but may apply some filtering or adaption for the event exposure parameters, such as adapting the TAIs from the TAI list to those that an AMF supports, adapting the SUPI list to the SUPIs that the AMF supports, adapting the monitoring period based on the time when the subscription was initially received from NWDAF, and/or the like.
  • the AMF may create an implicit subscription with the provided details in association with starting monitoring the resources.
  • the AMF may send a notification directly to the NWDAF.
  • a new NF e.g., an AMF or a SMF
  • the NRF may send the nwdafData back to the NF in a registration response, so that the new NF may create an implicit subscription.
  • the NWDAF may send an unsubscribe request to the NRF.
  • the NRF may update the subscriptions in all the NFs where the implicit subscription was created.
  • the NWDAF call-back URI is changed, the NRF may update the call-back URI to the implicit subscribed NFs in an update message (e.g., a heartbeat response).
  • a heartbeat timer for a heartbeat response may be kept under 10 seconds, or some other amount of time.
  • the NF may be updated with the updated NWDAF notification URI.
  • the NRF may need to monitor some subscriptions when, for example, the reporting mode is for a maximum duration for reporting, in which case the subscription may need to be deleted by the NRF or it can be deleted by NFs and NRF both implicitly when the subscription expires.
  • certain embodiments may not have to maintain subscription and NF associations in a NWDAF and in NFs. Additionally, or alternatively, certain embodiments may not have to renew the subscription when the NF is down or renew due to lifecycle change in the NFs. Additionally, or alternatively, a new NF joining a SBA may use implicit subscription data. Additionally, or alternatively, data collection in a NWDAF may be more accurate as a new NF, which may be registering in the NRF, may also be able to provide data directly to the NWDAF (via implicit subscription).
  • Fig. 2 is provided as an example. Other examples are possible, according to some embodiments.
  • Fig. 3 illustrates a signal diagram of another example of enhanced data collection at a NWDAF, according to some embodiments.
  • Fig. 3 illustrates NFs, an NRF, and a NWDAF similar to that illustrated in Fig. 2
  • Fig. 3 illustrates an example where an INFO message is implemented between the NFs and the NRF, where the NRF may update the NFs when there is a change in the NWDAF data.
  • Operation 300 may be similar to operation 200 described above.
  • Operation 302 may be similar to operation 202 described above.
  • Operation 304 may be similar to operation 204 described above, except that the event type in the filter criteria may be performance data.
  • Operation 306 may be similar to operation 206 described above.
  • Operation 308 may be similar to operation 208 described above except that an INFO message, rather than a 200 OK message, is used.
  • the event type in the filter criteria may be performance data at 308
  • Fig. 2 and Fig. 3 propose to use heartbeat response or INFO message, respectively, to transport NWDAF subscriptions, another existing service operation or a new service operation dedicated to the NWDAF subscriptions could be used.
  • Operation 310 may be similar to operation 212 described above.
  • Operation 312 may be similar to operation 214 described above.
  • Fig. 3 is provided as an example. Other examples are possible, according to some embodiments.
  • Fig. 4 illustrates an example flow diagram of a method, according to some embodiments.
  • Fig. 4 shows example operations of a network entity (e.g., hosted on apparatus 10 discussed below), such as a NWDAF.
  • NWDAF a network entity
  • Some of the operations illustrated in Fig. 4 may be similar to some operations shown in, and described with respect to, Figs. 1-3.
  • the method may include, at 400, sending, to at least one NRF, at least one message associated with creating at least one subscription to at least one NF.
  • the at least one message may comprise information that identifies the at least one NF and at least one filter criterion for at least one notification associated with the at least one subscription.
  • the method may include, at 402, receiving, from the at least one NF, the at least one notification based on the at least one filter criterion.
  • the at least one message may comprise at least one service-based interface (SBI) message.
  • the at least one subscription may be at least one implicit subscription which is to be created to the at least one network function.
  • the at least one filter criterion may comprise information identifying at least one target UE, at least one NF type, at least one DNN list, at least one SNSSAI, at least one filter expiry time, and/or at least one filter event type.
  • the method may further include sending, to the at least one NRF, at least one other message.
  • the at least one other message may be associated with stopping further notifications or unsubscribing from the at least one NF.
  • the at least one other message may be associated with updating the at least one subscription at the at least one NF to modify the at least one subscription from the at least one NF.
  • Fig. 4 is provided as an example. Other examples are possible according to some embodiments.
  • Fig. 5 illustrates an example flow diagram of a method, according to some embodiments.
  • Fig. 5 shows example operations of a network entity (e.g., hosted on apparatus 10 discussed below), such as a NRF.
  • a network entity e.g., hosted on apparatus 10 discussed below
  • Some of the operations illustrated in Fig. 5 may be similar to some operations shown in, and described with respect to, Figs. 1-3.
  • the method may include, at 500, receiving at least one first message associated with creating at least one subscription to at least one NF.
  • the at least one message may comprise information that identifies the at least one NF and at least one filter criterion for at least one notification associated with the at least one subscription.
  • the method may include, at 502, sending, to the NF via at least one second message, NWDAF data associated with the at least one subscription based on the at least one filter criterion and based on the at least one NF being registered with the network entity.
  • the method may further comprise processing the at least one filter criterion to determine the at least one network function associated with the at least one subscription.
  • the NWDAF data may comprise at least one default configuration identifying at least one NWDAF to which the at least one NF is to send the at least one notification, or is empty during registration of the at least one NF with the network entity.
  • the NWDAF data may identify at least one event type and at least one notification URL
  • the at least one first message may comprise at least one SBI message.
  • the at least one subscription may comprise at least one implicit subscription.
  • the at least one filter criterion may comprise information identifying at least one target UE, at least one NF type, at least one DNN list, at least one SNSSAI, at least one filter expiry time, and/or at least one filter event type.
  • the at least one second message may comprise at least one heartbeat response message, at least one registration response message, at least one update response message, and/or at least one INFO message.
  • the method may further comprise receiving, from at least one NWDAF, at least one third message.
  • the at least one third message may be associated with stopping at least one further notification or unsubscribing from the at least one NF.
  • the at least one third message may be associated with updating the at least one subscription from the at least one NF.
  • the method may further comprise sending, to the at least one NF, at least one fourth message.
  • the at least one fourth message may be associated with updating the at least one subscription at the at least one network function to stop the at least one further notification or to unsubscribe from the at least one NF.
  • the at least one fourth message may be associated with updating the at least one subscription at the at least one NF to modify the at least one subscription from the at least one NF.
  • the method may further comprise receiving at least one registration of the at least one NF, determining that the at least one first message has already been received for the at least one subscription to the at least one NF, and sending the network data analytics function (NWDAF) data may further comprise sending returned NWDAF data included in at least one response message associated with registration of the at least one NF to the network entity.
  • the method may further comprise receiving at least one registration of the at least one NF, and receiving at least one update of profile information associated with the at least one NF in association with the registration.
  • the profile information may comprise information that identifies at least one of: at least one URI for the notification, at least one application identifier, at least one event type, at least one DNN, SNSSAI, at least one quality of service (QoS) flow identifier (QFI), and/or IP filter information.
  • the method may further comprise providing at least one indication that the profile information was accepted, or providing at least one indication that the profile information was overridden.
  • Fig. 5 is provided as an example. Other examples are possible according to some embodiments.
  • Fig. 6 illustrates an example flow diagram of a method, according to some embodiments.
  • Fig. 6 shows example operations of a network node (e.g., hosted on apparatus 10 discussed below), such as a NF.
  • a network node e.g., hosted on apparatus 10 discussed below
  • Some of the operations illustrated in Fig. 6 may be similar to some operations shown in, and described with respect to, Figs. 1-3.
  • the method may include, at 600, receiving, in at least one message, NWDAF data associated with at least one subscription to the network entity.
  • the method may include, at 602, sending at least one notification associated with the at least one subscription to at least one NWDAF based on at least one filter criterion associated with the at least one subscription.
  • the at least one NWDAF data may comprise at least one default configuration identifying the at least one NWDAF to which the network entity is to send the at least one notification, or is empty during registration of the network entity with at least one NRF.
  • the at least one NWDAF data may identify at least one event type and at least one notification URI.
  • the at least one filter criterion may comprise information identifying at least one target UE, at least one NF type, at least one DNN list, at least one filter expiry time, and/or at least one filter event type.
  • the at least one message may comprise at least one heartbeat response message, at least one registration response message, at least one update response message, and/or at least one INFO message.
  • the method may comprise receiving, from the at least one NRF, at least one other message.
  • the at least one other message may be associated with updating the at least one subscription at the network entity or stopping at least one further notification.
  • the method may further comprise registering with at least one NRF, and receiving the NWDAF data may further comprise receiving returned NWDAF data included in at least one response message associated with registration of the network entity to at least one NRF.
  • the method may further comprise registering with at least one NRF, and updating profile information associated with the network entity in association with registering with the at least one NRF.
  • the profile information may comprise information that identifies at least one of: at least one URI for the notification, at least one application identifier, at least one event type, at least one DNN, SNSSAI, at least one QFI, or IP filter information.
  • the method may further comprise receiving at least one indication that the profile information was accepted, or receiving at least one indication that the profile information was overridden.
  • Fig. 6 is provided as an example. Other examples are possible according to some embodiments.
  • apparatus 10 may be a node, host, or server in a communications network or serving such a network.
  • apparatus 10 may be a network node, satellite, base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), and/or a WLAN access point, associated with a radio access network, such as a LTE network, 5G or NR or 5GS.
  • apparatus 10 may be an eNB in LTE or gNB in 5G.
  • a network node may host one or more network entities, such as a NWDAF, a NRF, and/or a NF.
  • apparatus 10 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection.
  • apparatus 10 represents a gNB
  • it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality.
  • the CU may be a logical node that includes gNB functions such as transfer of user data, mobility control, radio access network sharing, positioning, and/or session management, etc.
  • the CU may control the operation of DU(s) over a front-haul interface.
  • the DU may be a logical node that includes a subset of the gNB functions, depending on the functional split option. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in Fig. 7a.
  • apparatus 10 may include a processor 12 for processing information and executing instructions or operations.
  • processor 12 may be any type of general or specific purpose processor.
  • processor 12 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field- programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi -core processor architecture, as examples. While a single processor 12 is shown in Fig. 7a, multiple processors may be utilized according to other embodiments.
  • apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing.
  • processor 12 may represent a multiprocessor
  • the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
  • Processor 12 may perform functions associated with the operation of apparatus 10, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.
  • Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12.
  • Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory.
  • a semiconductor-based memory device such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory.
  • RAM random access memory
  • ROM read only memory
  • HDD hard disk drive
  • the instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.
  • apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium.
  • an external computer readable storage medium such as an optical disc, USB drive, flash drive, or any other storage medium.
  • the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.
  • apparatus 10 may also include or be coupled to one or more antennas
  • Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information.
  • the transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15.
  • the radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like.
  • the radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink).
  • transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10.
  • transceiver 18 may be capable of transmitting and receiving signals or data directly.
  • apparatus 10 may include an input and/or output device (I/O device).
  • memory 14 may store software modules that provide functionality when executed by processor 12.
  • the modules may include, for example, an operating system that provides operating system functionality for apparatus 10.
  • the memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10.
  • the components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.
  • processor 12 and memory 14 may be included in or may form a part of processing circuitry or control circuitry.
  • transceiver 18 may be included in or may form a part of transceiver circuitry.
  • circuitry may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to case an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation.
  • hardware-only circuitry implementations e.g., analog and/or digital circuitry
  • combinations of hardware circuits and software e.g., combinations of analog and/or digital hardware circuits with software/firmware
  • any portions of hardware processor(s) with software including digital signal processors
  • circuitry may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or 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.
  • apparatus 10 may be a network node or RAN node, such as a base station, access point, Node B, eNB, gNB, WLAN access point, or the like.
  • a network node or RAN node such as a base station, access point, Node B, eNB, gNB, WLAN access point, or the like.
  • apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the embodiments described herein, such as some operations of flow or signaling diagrams illustrated in Figs. 1-6.
  • apparatus 10 may be controlled by memory 14 and processor 12 to send, to at least one NRF, at least one message associated with creating at least one subscription to at least one NF.
  • the at least one message may comprise information that identifies the at least one NF and at least one filter criterion for at least one notification associated with the at least one subscription.
  • apparatus 10 may be controlled by memory 14 and processor 12 to receive, from the at least one NF, the at least one notification based on the at least one filter criterion.
  • apparatus 10 may be controlled by memory 14 and processor 12 to receive at least one first message associated with creating at least one subscription to at least one NF.
  • the at least one message may comprise information that identifies the at least one NF and at least one filter criterion for at least one notification associated with the at least one subscription.
  • apparatus 10 may be controlled by memory 14 and processor 12 to send, to the NF via at least one second message, NWDAF data associated with the at least one subscription based on the at least one filter criterion and based on the at least one NF being registered with the apparatus.
  • apparatus 10 may be controlled by memory 14 and processor 12 to receive, in at least one message, NWDAF data associated with at least one subscription to the apparatus.
  • apparatus 10 may be controlled by memory 14 and processor 12 to send at least one notification associated with the at least one subscription to at least one NWDAF based on at least one filter criterion associated with the at least one subscription.
  • Fig. 7b illustrates an example of an apparatus 20 according to another embodiment.
  • apparatus 20 may be a node or element in a communications network or associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device.
  • a UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, IoT device, sensor or NB-IoT device, or the like.
  • apparatus 20 may be implemented in, for instance, a wireless handheld device, a wireless plug-in accessory, or the like.
  • apparatus 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface.
  • apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, 5GS, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 7b.
  • apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations.
  • processor 22 may be any type of general or specific purpose processor.
  • processor 22 may include one or more of general- purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in Fig. 7b, multiple processors may be utilized according to other embodiments.
  • apparatus 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing.
  • processor 22 may represent a multiprocessor
  • the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
  • Processor 22 may perform functions associated with the operation of apparatus 20 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.
  • Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22.
  • Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory.
  • a semiconductor-based memory device such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory.
  • RAM random access memory
  • ROM read only memory
  • HDD hard disk drive
  • the instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.
  • apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium.
  • an external computer readable storage medium such as an optical disc, USB drive, flash drive, or any other storage medium.
  • the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20.
  • apparatus 20 may also include or be coupled to one or more antennas
  • Apparatus 20 may further 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 plurality of radio access technologies including one or more of GSM, LTE, LTE- A, 5G, NR, 5GS, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like.
  • the radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.
  • filters for example, digital-to-analog converters and the like
  • symbol demappers for example, digital-to-analog converters and the like
  • signal shaping components for example, an Inverse Fast Fourier Transform (IFFT) module, and the like
  • IFFT Inverse Fast Fourier Transform
  • transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20.
  • transceiver 28 may be capable of transmitting and receiving signals or data directly.
  • apparatus 20 may include an input and/or output device (I/O device).
  • apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen.
  • memory 24 stores software modules that provide functionality when executed by processor 22.
  • the modules may include, for example, an operating system that provides operating system functionality for apparatus 20.
  • the memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20.
  • the components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software.
  • apparatus 20 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 70 according to any radio access technology, such as 5GS.
  • processor 22 and memory 24 may be included in or may form a part of processing circuitry or control circuitry.
  • transceiver 28 may be included in or may form a part of transceiving circuitry.
  • apparatus 20 may be a UE, mobile device, mobile station, ME, IoT device and/or NB-IoT device, for example.
  • apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with example embodiments described herein.
  • apparatus 20 may be configured to perform one or more of processes described herein.
  • certain example embodiments provide several technological improvements, enhancements, and/or advantages over existing technological processes.
  • one benefit of some example embodiments is conservation of memory resources of the NWDAF and/or computing or processing resources of the NWDAF that would otherwise be consumed as a result of the NWDAF having to maintain multiple subscriptions and their associations. Accordingly, the use of some example embodiments results in improved functioning of communications networks and their nodes and, therefore constitute an improvement at least to the technological field of data collection at a NWDAF, among others.
  • certain embodiments propose to use heartbeat response or INFO message, respectively, to transport NWDAF subscriptions, another existing service operation or a new service operation dedicated to the NWDAF subscriptions could be used for certain embodiments.
  • any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.
  • an apparatus may be included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor.
  • Programs also called 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 to perform particular tasks.
  • a computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments.
  • the one or more computer-executable components may be at least one software code or portions of code. Modifications and configurations required for implementing functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). In one example, software routine(s) may be downloaded into the apparatus.
  • software or a computer program code or portions of code may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • the computer readable medium or computer readable storage medium may be a non- transitory medium.
  • the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20), for example through the use of 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.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • the functionality may be implemented as a signal, such as a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.
  • an apparatus such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity used for arithmetic operation(s) and/or an operation processor for executing the arithmetic operation(s).
  • Example embodiments described herein apply equally to both singular and plural implementations, regardless of whether singular or plural language is used in connection with describing certain embodiments. For example, an embodiment that describes operations of a single network node equally applies to embodiments that include multiple instances of the network node, and vice versa.
  • a method may include sending, to at least one NRF, at least one message associated with creating at least one subscription to at least one NF.
  • the at least one message may comprise information that identifies the at least one NF and at least one filter criterion for at least one notification associated with the at least one subscription.
  • the method may include receiving, from the at least one NF, the at least one notification based on the at least one filter criterion.
  • the at least one message may comprise at least one service-based interface (SBI) message.
  • the at least one subscription may be at least one implicit subscription, which is to be created to the at least one network function.
  • the at least one filter criterion may comprise information identifying at least one target UE, at least one NF type, at least one DNN list, at least one SNSSAI, at least one filter expiry time, or at least one filter event type.
  • the method may further include sending, to the at least one NRF, at least one other message.
  • the at least one other message may be associated with stopping further notifications or unsubscribing from the at least one NF.
  • a method may include receiving at least one first message associated with creating at least one subscription to at least one NF.
  • the at least one message may comprise information that identifies the at least one NF and at least one filter criterion for at least one notification associated with the at least one subscription.
  • the method may include sending, to the NF via at least one second message, NWDAF data associated with the at least one subscription based on the at least one filter criterion and based on the at least one NF being registered with a network entity.
  • the method may further comprise processing the at least one filter criterion to determine the at least one NF associated with the at least one subscription.
  • the NWDAF data may comprise at least one default configuration identifying a NWDAF to which the at least one NF is to send the at least one notification, or is empty during registration of the at least one NF with the network entity.
  • the NWDAF data may identify at least one event type and at least one notification URI.
  • the at least one first message may comprise at least one SBI message.
  • the at least one subscription may comprise at least one implicit subscription.
  • the at least one filter criterion may comprise information identifying at least one target UE, at least one NF type, at least one DNN list, at least one SNSSAI, at least one filter expiry time, or at least one filter event type.
  • the at least one second message may comprise at least one heartbeat response message, at least one registration response message, at least one update response message, or at least one INFO message.
  • the method may further comprise receiving, from at least one NWDAF, at least one third message.
  • the at least one third message may be associated with stopping at least one further notification or unsubscribing from the at least one NF.
  • the at least one third message may be associated with updating the at least one subscription from the at least one NF.
  • the method may further comprise sending, to the at least one NF, at least one fourth message.
  • the at least one fourth message may be associated with updating the at least one subscription at the at least one network function to stop the at least one further notification or to unsubscribe from the at least one NF. In a variant, the at least one fourth message may be associated with updating the at least one subscription at the at least one NF to modify the at least one subscription from the at least one NF.
  • the method may further comprise receiving at least one registration of the at least one NF, determining that the at least one first message has already been received for the at least one subscription to the at least one NF, and sending the network data analytics function (NWDAF) data may further comprise sending returned NWDAF data included in at least one response message associated with registration of the at least one NF to the network entity.
  • the method may further comprise receiving at least one registration of the at least one NF, and receiving at least one update of profde information associated with the at least one NF in association with the registration.
  • the profde information may comprise information that identifies at least one of: at least one URI for the notification, at least one application identifier, at least one event type, at least one DNN, SNSSAI, at least one quality of service (QoS) flow identifier (QFI), or IP filter information.
  • the method may further comprise providing at least one indication that the profile information was accepted, or providing at least one indication that the profile information was overridden.
  • a method may include receiving, in at least one message, NWDAF data associated with at least one subscription to the network entity.
  • the method may include sending at least one notification associated with the at least one subscription to at least one NWDAF based on at least one filter criterion associated with the at least one subscription.
  • the at least one NWDAF data may comprise at least one default configuration identifying the at least one NWDAF to which a network entity is to send the at least one notification, or is empty during registration of the network entity with at least one NRF.
  • the at least one NWDAF data identifies at least one event type and at least one notification URI.
  • the at least one filter criterion may comprise information identifying at least one target UE, at least one NF type, at least one DNN list, at least one filter expiry time, or at least one filter event type.
  • the at least one message may comprise at least one heartbeat response message, at least one registration response message, at least one update response message, or at least one INFO message.
  • the method may comprise receiving, from the at least one NRF, at least one other message.
  • the at least one other message may be associated with updating the at least one subscription at the network entity or stopping at least one further notification.
  • the method may further comprise registering with at least one NRF, and receiving the NWDAF data may further comprise receiving returned NWDAF data included in at least one response message associated with registration of the network entity to at least one NRF.
  • the method may further comprise registering with at least one NRF, and updating profile information associated with the network entity in association with registering with the at least one NRF.
  • the profile information may comprise information that identifies at least one of: at least one URI for the notification, at least one application identifier, at least one event type, at least one DNN, SNSSAI, at least one QFI, or IP filter information.
  • a fourth embodiment may be directed to an apparatus including at least one processor and at least one memory comprising computer program code.
  • the at least one memory and computer program code may be configured, with the at least one processor, to cause the apparatus at least to perform the method according to the first embodiment, the second embodiment, or the third embodiment, or any of the variants discussed above.
  • a fifth embodiment may be directed to an apparatus that may include circuitry configured to perform the method according to the first embodiment, the second embodiment, or the third embodiment, or any of the variants discussed above.
  • a sixth embodiment may be directed to an apparatus that may include means for performing the method according to the first embodiment, the second embodiment, or the third embodiment, or any of the variants discussed above.
  • a seventh embodiment may be directed to a computer readable medium comprising program instructions stored thereon for performing at least the method according to the first embodiment, the second embodiment, or the third embodiment, or any of the variants discussed above.
  • An eighth embodiment may be directed to a computer program product encoding instructions for performing at least the method according to the first embodiment, the second embodiment, or the third embodiment, or any of the variants discussed above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Des systèmes, des procédés, des appareils et des produits programmes d'ordinateur pour une collecte de données améliorée au niveau d'une fonction analytique de données de réseau (NWDAF). Par exemple, certains modes de réalisation peuvent fournir une manière de réaliser des abonnements implicites à différentes fonctions de réseau (NF) pour une NWDAF. De cette manière, certains modes de réalisation peuvent délester la NWDAF de la responsabilité de maintenir de multiples abonnements et leur association avec des NF différents et peuvent créer un cadre dans une architecture à base de service (SBA) selon laquelle des NF peuvent avoir des informations d'abonnement pour envoyer des données à une NWDAF.
PCT/EP2021/055878 2020-03-30 2021-03-09 Collecte de données améliorée au niveau d'une fonction analytique de données de réseau (nwdaf) WO2021197773A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063001756P 2020-03-30 2020-03-30
US63/001,756 2020-03-30

Publications (1)

Publication Number Publication Date
WO2021197773A1 true WO2021197773A1 (fr) 2021-10-07

Family

ID=74871386

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/055878 WO2021197773A1 (fr) 2020-03-30 2021-03-09 Collecte de données améliorée au niveau d'une fonction analytique de données de réseau (nwdaf)

Country Status (1)

Country Link
WO (1) WO2021197773A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230188445A1 (en) * 2020-08-13 2023-06-15 Huawei Technologies Co., Ltd. Communication Method, and Communication Apparatus and System
US11765064B1 (en) 2022-05-27 2023-09-19 Cisco Technology, Inc. Network repository function overload protection
US12034621B2 (en) * 2020-08-13 2024-07-09 Huawei Technologies Co., Ltd. Communication method, and communication apparatus and system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019032968A1 (fr) * 2017-08-11 2019-02-14 Convida Wireless, Llc Analyse de données de réseau dans un réseau de communication
CN110798360A (zh) * 2019-11-06 2020-02-14 腾讯科技（深圳）有限公司 Nwdaf网元的选择方法、装置、电子设备及可读存储介质

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019032968A1 (fr) * 2017-08-11 2019-02-14 Convida Wireless, Llc Analyse de données de réseau dans un réseau de communication
CN110798360A (zh) * 2019-11-06 2020-02-14 腾讯科技（深圳）有限公司 Nwdaf网元的选择方法、装置、电子设备及可读存储介质

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for 5G System (5GS) to support network data analytics services (Release 16)", vol. SA WG2, no. V16.3.0, 27 March 2020 (2020-03-27), pages 1 - 62, XP051861086, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/23_series/23.288/23288-g30.zip 23288-g30.docx> [retrieved on 20200327] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16)", vol. SA WG2, no. V16.4.0, 27 March 2020 (2020-03-27), pages 1 - 430, XP051861090, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/23_series/23.501/23501-g40.zip 23501-g40.docx> [retrieved on 20200327] *
HUAWEI ET AL: "New KI for minimization of the load generated by NWDAF in Data Collection and Storage", vol. SA WG2, no. Incheon, South Korea; 20200113 - 20200117, 17 January 2020 (2020-01-17), XP051844295, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_136AH_Incheon/Docs/S2-2001562.zip S2-2001562_1298_1231_1209_0421_0632_0920 - pCR TR 23.700-91 New KI Minimization - v2.0.doc> [retrieved on 20200117] *
NOKIA ET AL: "OAM based solution for minimizing the load of real-time data collection", vol. SA WG2, no. Incheon, Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), XP051842978, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_136AH_Incheon/Docs/S2-2000925.zip S2-2000925-OAM-based-data-collection.docx> [retrieved on 20200107] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230188445A1 (en) * 2020-08-13 2023-06-15 Huawei Technologies Co., Ltd. Communication Method, and Communication Apparatus and System
US12034621B2 (en) * 2020-08-13 2024-07-09 Huawei Technologies Co., Ltd. Communication method, and communication apparatus and system
US11765064B1 (en) 2022-05-27 2023-09-19 Cisco Technology, Inc. Network repository function overload protection

Similar Documents

Publication Publication Date Title
US11509728B2 (en) Methods and apparatuses for discovering a network function acting as network function service consumer
US20240015044A1 (en) Separate session start request indication
US11930394B2 (en) Overload control information from a network function service consumer in 5G core network (5GC) service based architecture (SBA)
US20220046410A1 (en) Systems and methods to enable representative user equipment sampling for user equipment-related analytics services
WO2020257265A1 (fr) Notification de souscription à un événement
US11190928B2 (en) Data storage function selection
US20200351704A1 (en) Buffer status report for sidelink resource allocation
US20230297717A1 (en) Enhanced method of control or management of user related data subject to user consent
EP3979680A1 (fr) Services de localisation améliorés en 5g
WO2022148627A1 (fr) Procédés et appareils d&#39;activation et de désactivation d&#39;un service de diffusion-multidiffusion (mbs)
WO2021197773A1 (fr) Collecte de données améliorée au niveau d&#39;une fonction analytique de données de réseau (nwdaf)
WO2021138558A1 (fr) Sélection d&#39;une fonction de gestion de session apte à stocker une multidiffusion par protocole internet
US11895524B2 (en) Distinction of minimization drive test logging through different radio resource controller states
US20220377528A1 (en) Dynamically unsubscribing from a plmn/npn service
EP3790347B1 (fr) Gestion des notifications pour la surveillance de la communication
US11985050B2 (en) Unified data repository selection and parameters therefor
EP4255002A1 (fr) Profilage analytique de données de réseau
US11985045B2 (en) Method and apparatus for subscribing change notification of network function
WO2023143385A1 (fr) Procédé et appareil de formation de groupe fondé sur la localisation
US20230147094A1 (en) Data collection coordination and persistent storage control for analytics
WO2022175779A1 (fr) Poussée de descriptions de flux de paquets sur la base d&#39;attributs fournis et configurés
WO2023285224A1 (fr) Procédés et appareils destinés à permettre à un équipement utilisateur de s&#39;enregistrer auprès de multiples réseaux mobiles terrestres publics et réseaux non publics à l&#39;aide du même type d&#39;accès

Legal Events

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

Ref document number: 21711520

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21711520

Country of ref document: EP

Kind code of ref document: A1