WO2021187948A1 - Method and apparatus for data analytics in telecommunication network - Google Patents

Method and apparatus for data analytics in telecommunication network Download PDF

Info

Publication number
WO2021187948A1
WO2021187948A1 PCT/KR2021/003437 KR2021003437W WO2021187948A1 WO 2021187948 A1 WO2021187948 A1 WO 2021187948A1 KR 2021003437 W KR2021003437 W KR 2021003437W WO 2021187948 A1 WO2021187948 A1 WO 2021187948A1
Authority
WO
WIPO (PCT)
Prior art keywords
nwdaf
analytics
nwdafs
nrf
network
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/KR2021/003437
Other languages
English (en)
French (fr)
Inventor
Mehrdad Shariat
Jungshin Park
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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
Priority claimed from GB2004073.9A external-priority patent/GB2593217A/en
Priority claimed from GBGB2013265.0A external-priority patent/GB202013265D0/en
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to JP2022556607A priority Critical patent/JP7730832B2/ja
Priority to CN202180022588.9A priority patent/CN115316044B/zh
Publication of WO2021187948A1 publication Critical patent/WO2021187948A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5058—Service discovery by the service manager

Definitions

  • the disclosure relates to the acquisition, processing and use of data analytics in a telecommunication network. More particularly, the disclosure relates to Fifth Generation networks, although this is exemplary and other networks may benefit similarly.
  • the 5G or pre-5G communication system is also called a ‘Beyond 4G Network’ or a ‘Post LTE System’.
  • the 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates.
  • mmWave e.g., 60GHz bands
  • MIMO massive multiple-input multiple-output
  • FD-MIMO Full Dimensional MIMO
  • array antenna an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
  • RANs Cloud Radio Access Networks
  • D2D device-to-device
  • CoMP Coordinated Multi-Points
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC sliding window superposition coding
  • ACM advanced coding modulation
  • FBMC filter bank multi carrier
  • NOMA non-orthogonal multiple access
  • SCMA sparse code multiple access
  • 5G communication systems to IoT networks.
  • technologies such as a sensor network, Machine Type Communication (MTC), and Machine-to-Machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas.
  • MTC Machine Type Communication
  • M2M Machine-to-Machine
  • Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology.
  • RAN Radio Access Network
  • NWDAF Network Data Analytics Function
  • SBA Service Based Architecture
  • each network function comprises a set of services that interfaces it (as the producer of such services) to other NFs (as the consumer of those services) over a common bus known as service-based interface (SBI).
  • SBI service-based interface
  • FIG. 1 illustrates a general schematic overview illustrating various element in a 5G network automation scheme according to the related art. Only those parts relevant of the automation are shown, for clarity.
  • This shows that activity data and analytics are provided from a first group of NFs 50 or Application Functions (AFs) 10 to NWDAF 40.
  • NWDAF 40 also interfaces to OAM 30 and data repositories 20. NWDAF 40 analyses the data from these sources and delivers analytics data to a second group of NFs 50 or AFs 10.
  • the second group of NFs 50 may include some or all of the first group of NFs 50 or AFs 10.
  • eNA Network Automation
  • an aspect of the disclosure is to provide a method of managing analytics data in a telecommunication network, wherein a consumer Network Function (NF), determining how analytics data from a plurality of individual sources is collected and analyzing the analytics data in one of a distributed manner from a plurality of Network Data Analytics Functions (NWDAF), a centralized manner by aggregating analytics data from the plurality of NWDAFs, before analyzing the analytic data at an Aggregator NWDAF, or at least one of each of the distributed manner from the plurality of NWDAFs and the centralized manner by the aggregating of the analytics data from the plurality of NWDAFs, before the analyzing the analytics data at an Aggregator NWDAF.
  • NF consumer Network Function
  • NWDAF Network Data Analytics Function
  • At least one in the case of a plurality of NWDAFs being provided in the telecommunication network, at least one has a specialized function and at least one has a general function.
  • the specialized function is to aggregate analytics from plurality of areas of interest or plurality of target users, and the general function is to notify analytics per area of interest or per set of target users.
  • capability information of any particular one of the plurality of NWDAFs having the specialized function is stored in a Network Repository Function (NRF).
  • NEF Network Repository Function
  • the capability information relates to analytics aggregation capability
  • a consumer Network Function determines one or more NWDAFs from which to collect data, based on NWDAF capability information as part of its implemented internal selection criteria.
  • implemented selection criteria comprises one or more of newly registered capabilities in NRF, determined based on the level of load per NWDAF, number of analytics Identifiers (IDs) directly supported per NWDAF and other Key Performance Indicators (KPIs) pre-configured by the network Operator.
  • IDs number of analytics Identifiers
  • KPIs Key Performance Indicators
  • an identifier such as aggregation point identifier, AP ID
  • AP ID is defined per Aggregator NWDAF, as an assistance information registered in NRF wherein the identifier indicates which amongst NWDAFs are able to act as an aggregation point.
  • the consumer NF autonomously determines how a plurality of NWDAFs operate together.
  • the determination is based on selection criteria, whereby the consumer NF considers all NWDAFs identified by the NRF and based on the implemented selection criteria decides how to collect data from a combination of them.
  • each of the plurality of NWDAFs pre-negotiates with one or more other Aggregator NWDAFs how many analytics IDs it supports and the Aggregator NWDAF advertises such extended set of supported analytics IDs within the NRF.
  • a network function service consumer sends a discovery request to a Network Repository Function, NRF, including all required Analytics ID(s) and an area of interest, the NRF responding with one or more of a set of NWDAF instance IDs, each covering a set of Analytics ID(s), and at least part of the area of interest supported and AP ID, or other identifier, per Aggregator NWDAF instance(s) indicating possible aggregation point(s), the network function service consumer, based on its internal selection criteria, considering registered NWDAF capabilities and information from NRF, selects at least one NWDAF as Aggregator NWDAF, the network function service consumer sends a subscription request to Aggregator NWDAF to designate as an aggregation point, including Analytics IDs and area of interest per NWDAF to aggregate from, and either a) Aggregator NWDAF identifies its designation as aggregation point, or b) Aggregator NWDAF based on configuration, implementation or queries to NRF decides on mapping to
  • a network function service consumer sends a discovery request to a Network Repository Function, NRF, including all required Analytics ID(s) and an area of interest, the NRF responding with one or more of at least one NWDAF instance ID, at least one NWDAF instance ID to be aggregated into at least one Aggregator NWDAF instance ID as registered in NRF, the network function service consumer subscribing to all NWDAFs, including aggregation points acting as central NWDAFs and receiving individual notifications, and per analytics ID, the network function service consumer aggregating analytics data from both distributed and (semi-)centralized NWDAF instances for corresponding points of interest.
  • NRF Network Repository Function
  • NWDAF 40 may be deployed in a Public land mobile network (PLMN).
  • PLMN Public land mobile network
  • embodiments of the disclosure support deploying the NWDAF 40 as a central NF, as a collection of distributed NFs, or as a combination of both (i.e. some centralized and some distributed).
  • Embodiments of the disclosure define an Analytics ID information element, which is used to identify the type of supported analytics that a particular NWDAF can generate.
  • some of the NWDAFs in one network may be providing the same type of analytics, and so may assist each other for e.g. specific analytics for specific target User Equipment (UEs) or specific analytics for specific area of interest.
  • UEs User Equipment
  • NWDAF Network Repository Function
  • Embodiments of the disclosure provide a data collection mechanism in an environment comprising multiple NWDAFs to thereby flexibly support different deployment options.
  • NWDAF NWDAF instance
  • a consumer NF decides on the set of NWDAFs (or NWDAF instances) from which to collect data, based on its implemented selection criteria (e.g. the level of load per NWDAF, number of analytics IDs directly supported per NWDAF or other Key Performance Indicators (KPIs) pre-configured by the network Operator).
  • NWDAFs or NWDAF instances
  • KPIs Key Performance Indicators
  • a novel aggregation point identifier is defined per NWDAF indicating which other NWDAF can be a potential aggregation point for it.
  • the identifier can be set, taking into account multiple factors including the level of load per NWDAF (or NWDAF instance), number of analytics IDs directly supported per NWDAF or other KPIs set by the network operator. NWDAF information maintained in NRF or any other designated Data Repository structures may hold this identifier per NWDAF.
  • the consumer NF utilizes the AP ID as assistance information in addition to its other implemented selection criteria to decide on how multiple NWDAF instances collaborate.
  • a consumer NF intelligently decides how multiple NWDAF instances collaborate without any other entities’ intervention.
  • the consumer NF considers all NWDAF instances (e.g. as discovered via NRF) and based on implemented selection criteria, similar to distributed data collection, decides how to collect data from a combination of them.
  • NWDAF information maintained in NRF or any other designated Data Repository structures can be agnostic to aggregation information.
  • each NWDAF instance pre-negotiates the number of analytics IDs it may support (either directly or indirectly) with other NWDAF instances (e.g. via NRF discovery) and it advertises such extended set of supporting analytics IDs (direct plus indirect ones) within NRF.
  • NWDAF information maintained in NRF or any other designated Data Repository structures may explicitly differentiate directly supported analytics IDs from indirect ones.
  • the consumer NF utilizes the direct versus indirect supporting analytics IDs as assistance information in addition to its other implemented selection criteria to decide how multiple NWDAF instances collaborate.
  • the disclosure is to provide a method of effectively managing analytics data in a telecommunication network.
  • FIG. 2 illustrates a message exchange and method according to an embodiment of the disclosure
  • FIG. 3 illustrates a message exchange and method according to an embodiment of the disclosure
  • FIG. 4 illustrates a message exchange and method according to an embodiment of the disclosure.
  • FIG. 2 illustrates a scenario where there is a consumer NF, NRF, NWDAF(k) forming at least part of a system according to an embodiment of the disclosure. This also shows the various processes and messaging between respective elements.
  • index (k) shows the NWDAF instance ID in a multi-instance deployment.
  • NWDAF(k) 120 is specialized in a set of data analytics types, identified by AnalyticsIDs(k); some overlapping across different instances and some are mutually exclusive. Instances with overlapping analytic IDs may help each other e.g. to cover different sets of UEs as the target of analytics reporting or to cover different set of Tracking Areas within the area of interest. Tracking Area Indicators - TAI(k) refers to such areas of interest that could be covered by NWDAF(k).
  • the Consumer NF 100 may decide to consume different NWDAFs’ services in a distributed manner.
  • implemented selection criteria e.g. network configuration or pre-configured network operator’s preference
  • NWDAF service consumer 100 sends NF discovery request (1a) to NRF 110 including all required Analytics ID(s) and the area of interest (e.g. in form of TAIs).
  • the request may also include extra information, e.g. Network Slice Selection Assistance Information (i.e. Single-NSSAI or S-NSSAI).
  • the NRF 110 response (1b) may include multiple NWDAF instance IDs, NWDAF(k), each covering a set of Analytics ID(s), AnalyticsIDs(k), and (part of) the area of interest supported by instance (k), identified as TAI(k).
  • NWDAF service consumer 100 sends a subscription request (2a) to each NWDAF(k) 120 including AnalyticsIDs(k) and TAI(k) (e.g. as Analytics Filter).
  • NWDAF(k) 120 notifies with analytics specific parameters per analytics ID as shown in operation 2b.
  • the service consumer NF 100 may aggregate the target of analytics reporting across NWDAF(k)s for AnalyticsIDs(k) for corresponding areas of interest TAI(k).
  • FIG. 3 illustrates a scenario where there is a consumer NF, NRF, NWDAF(j) and NWDAF(i) forming at least part of a system according to an embodiment of the disclosure.
  • the Consumer NF 200 based on AP ID as assistance information in addition to its implemented selection criteria decides to consume different NWDAFs’ services in a (semi-)centralized manner, designating one (set of) NWDAF(s) as aggregation point(s).
  • the AP ID is also configured equivalent to NWDAF(j) 220 ID. This also identifies NWDAF(j) 220 as an aggregation point.
  • the AP ID is also configured equivalent to one of NWDAF(j)s 220 already registered as aggregation points.
  • the mapping between NWDAF(j)s 220 and NWDAF(i)s 230 in AP IDs can take into account multiple factors including the level of load per NWDAF, analytics IDs supported per NWDAF, area of interest supported per NWDAF, any predefined hierarchy for mapping or other KPIs set by the network operator.
  • NWDAF information maintained in NRF 210 or any other designated Data Repository structures may hold this mapping between NWDAFs based on AP IDs.
  • both NRF 210 and NWDAF service consumer 200 become aware of the mapping between central and distributed NWDAFs based on AP IDs.
  • FIG. 3 illustrates a scenario where there is a consumer NF, NRF, NWDAF(j) and NWDAF(i) forming at least part of a system according to an embodiment of the disclosure.
  • the details of each operation shown in FIG 3 are as follows:
  • the NRF 210 response may include both distributed NWDAF(i)s and central NWDAF(j)s.
  • the NRF 210 response also includes the AP ID per NWDAF(i) 230 instance indicating possible aggregation point(s) NWDAF(j) 220 for different values of (j) i.e. the mapping between central and distributed NWDAFs.
  • NWDAF service consumer 200 determines central aggregation points based on the mapping received from NRF 210 as AP IDs.
  • NWDAF service consumer 200 sends a subscription request to NWDAF(j) 220 (to designate it as an aggregation point) including AnalyticsIDs(i), TAI(i) (as analytics filter) for NWDAF(i) 230.
  • NWDAF(j) 220 identifies its designation as aggregation point being the addressee of service consumer request.
  • another explicit flag or parameter can be set as an input parameter by NWDAF service consumer 200 to explicitly designate an aggregation point, NWDAF(j) 220.
  • NWDAF(j) 220 subscribes to all NWDAF(i)s 230 in a similar procedure as case A (single instance subscription procedure). All NWDAF(i)s notify with analytics specific parameters per analytics ID in the set of AnalyticsIDs(i).
  • NWDAF(j) 220 may aggregate the target of analytics reporting across different NWDAF(i)s 230 for AnalyticsIDs(i) for corresponding area of interest, TAI(i).
  • NWDAF(j) 220 notifies with analytics specific parameters per analytics ID for all aggregated analytics IDs per NWDAF(i) 230.
  • operation 1 is exactly similar to case A (distributed deployment) where the data kept in NRF 210 or any other data repository structure stays agnostic to deployment information (i.e. aggregation point identifiers).
  • deployment information i.e. aggregation point identifiers.
  • NRF 210 response may include both distributed NWDAF (i)s 230 and NWDAF (j)s 220 identified as aggregation points.
  • NWDAF service consumer 200 determines central aggregation point(s) based on its configuration or implemented selection criteria.
  • operation 1 is similar to case A (distributed deployment) except in respect of the data kept within NRF 210 or any other data repository structure, the AnalyticsIDs(j) advertised by NWDAF(j) 220 is an extended set of analytics IDs from different NWDAF(i)s 230 that can be pre-negotiated for instance j, e.g. based on some configurations or a pre-defined hierarchy when each NWDAF registers within NRF 210.
  • no explicit identifier is defined per NWDAF within NRF 210, unlike case B and no mapping is indicated between central and distributed NWDAFs at NRF 210.
  • the extended set of analytics IDs supported can be differentiated from analytics IDs directly supported per NWDAF. Some central NWDAFs may only aggregate analytics so the extended list may not have directly supported analytics in such a situation. Consequently, the NWDAF service consumer 200 may utilize this information in addition to its implemented selection criteria to decide on how multiple NWDAFs collaborate (e.g. the NWDAF(s) supporting more analytics IDs directly can be preferred to extend their list to avoid extra signaling overhead or network latency).
  • NWDAF service consumer sends subscription request to NWDAF(j) 220 (to designate as aggregation point) including all Analytics IDs, TAIs needed without indicating any mapping per NWDAF (i)s 230.
  • NWDAF (j) 220 based on extended set of supporting analytics IDs and also configuration, implementation or queries to NRF 210, decides on mapping to specific distributed NWDAFs to aggregate analytics from and subscribes to them.
  • NWDAF(j) 220 may aggregate the target of analytics reporting across different NWDAF(i)s 230 for Analytics IDs(i) for corresponding area of interest.
  • NWDAF (j) 220 notifies with analytics specific parameters per analytics ID for all aggregated analytics IDs without indicating any mapping per NWDAF(i)s 230.
  • case D1 In another case of centralized aggregation (referred to here as case D1, as a sub-case of Case D), no mapping is indicated between central and distributed NWDAFs at NRF 210 similar to case D.
  • no AP ID configured and only aggregation points are differentiated when registering in NRF 210 either implicitly (again similar to case D) or explicitly e.g. by configuring an identifier.
  • NWDAF service consumer 200 also becomes agnostic to the mapping between central and distributed NWDAFs. Instead, each central NWDAF 220 based on configuration, implementation or queries to NRF 210 or a pre-defined hierarchy (when registers to NRF) decides on mapping to specific distributed NWDAFs.
  • NRF 210 response may include both distributed NWDAF (i)s 230 and NWDAF (j)s 220 identified as aggregation points. NWDAF service consumer 200 chooses central aggregation points.
  • NWDAF service consumer sends subscription request to NWDAF(j) 220 (to designate as aggregation point) including all Analytics IDs, TAIs needed without indicating any mapping of analytics IDs or TAIs per NWDAF (i) 230.
  • NWDAF (j) 220 based on configuration, implementation or queries to NRF 210 decides on mapping to specific distributed NWDAFs 230 to aggregate analytics from and accordingly subscribes to them.
  • NWDAF(j) 220 may aggregate the target of analytics reporting across different NWDAF(i)s 230 for Analytics IDs(i) for corresponding areas of interest.
  • NWDAF (j) 220 notifies with analytics specific parameters per analytics ID for all aggregated analytics IDs without indicating any mapping of analytics IDs or TAIs per NWDAF (i) 230.
  • a mixture of distributed and (semi-)centralized modes of deployment can be used.
  • FIG. 4 illustrates a scenario where there is a consumer NF, NRF, NWDAF(k), NWDAF(j) and NWDAF(i) forming at least part of a system according to an embodiment of the disclosure.
  • NWDAF service consumer 300 sends NF discovery request (1a) to NRF 310 including all required Analytics ID(s) and the area of interest (e.g. in form of TAIs).
  • the request may also include extra information, e.g. Network Slice Selection Assistance Information (i.e. Single-NSSAI or S-NSSAI).
  • NRF response may include (1b) a (set of) NWDAF instance ID(s), i.e. NWDAF(k) 320, deployed in distributed manner.
  • NRF 310 response may also include (1c) a (set of) NWDAF instance ID(s) (i.e. NWDAF(i) 340) to be aggregated in a (set of) NWDAF instance IDs (i.e. NWDAF(j) 330).
  • NWDAF service consumer 300 subscribes to all NWDAF(k)s 320 similar to the distributed deployment procedure in case A and receives individual notifications.
  • NWDAF service consumer 300 also subscribes to NWDAF(j) 330.
  • NWDAF(j) 330 subscribes to all relevant NWDAF(i)s 340 to be aggregated similar to the (semi-)centralized deployment procedure in cases B or C or D or D1 and provides aggregate notification to the NWDAF service consumer 300.
  • the NWDAF service consumer 300 aggregates analytics data from both distributed and (semi-)centralized NWDAF instances.
  • FIG. 5 is a block diagram of a network entity according to an embodiment of the disclosure.
  • the network entity may correspond to each of the network entities shown in FIGS. 1-4.
  • the network entity may refer to each of the network functions (e.g. NRF, NWDAF) shown in FIG. 1-4.
  • the network entity may include a transceiver 510, a controller 520, and storage 530.
  • the controller 520 may include a circuit, an ASIC, or at least one processor.
  • the transceiver 510 may transmit and receive signals to and from a terminal or another network entity.
  • the controller 520 may control the overall operation of the network entity according to an embodiment. For example, the controller 520 may control the signal flow to perform the operations in FIGS. 1-4 described above. For example, the control unit 520 may determining how analytics data from a plurality of individual sources is collected and analyzed.
  • the storage 530 may store at least one of information exchanged through the transceiver 510 and information generated by the controller 530.
  • At least some of the example embodiments described herein may be constructed, partially or wholly, using dedicated special-purpose hardware.
  • Terms such as ‘component’, ‘module’ or ‘unit’ used herein may include, but are not limited to, a hardware device, such as circuitry in the form of discrete or integrated components, a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs certain tasks or provides the associated functionality.
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • the described elements may be configured to reside on a tangible, persistent, addressable storage medium and may be configured to execute on one or more processors.
  • These functional elements may in some embodiments include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
  • components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
  • components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/KR2021/003437 2020-03-20 2021-03-19 Method and apparatus for data analytics in telecommunication network Ceased WO2021187948A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022556607A JP7730832B2 (ja) 2020-03-20 2021-03-19 電気通信ネットワークにおけるデータ分析のための方法及び装置
CN202180022588.9A CN115316044B (zh) 2020-03-20 2021-03-19 电信网络中用于数据分析的方法和装置

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
GB2004073.9 2020-03-20
GB2004073.9A GB2593217A (en) 2020-03-20 2020-03-20 Improvements in and relating to data analytics in a telecommunication network
GBGB2013265.0A GB202013265D0 (en) 2020-08-25 2020-08-25 Improvements in and relating to data analytics in a telecommunication network
GB2013265.0 2020-08-25
GB2103460.8 2021-03-12
GB2103460.8A GB2593979B (en) 2020-03-20 2021-03-12 Improvements in and relating to data analytics in a telecommunication network

Publications (1)

Publication Number Publication Date
WO2021187948A1 true WO2021187948A1 (en) 2021-09-23

Family

ID=75623251

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/003437 Ceased WO2021187948A1 (en) 2020-03-20 2021-03-19 Method and apparatus for data analytics in telecommunication network

Country Status (6)

Country Link
US (3) US11632667B2 (cg-RX-API-DMAC7.html)
EP (1) EP3883189A1 (cg-RX-API-DMAC7.html)
JP (1) JP7730832B2 (cg-RX-API-DMAC7.html)
CN (1) CN115316044B (cg-RX-API-DMAC7.html)
GB (1) GB2593979B (cg-RX-API-DMAC7.html)
WO (1) WO2021187948A1 (cg-RX-API-DMAC7.html)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023163269A (ja) * 2022-04-28 2023-11-10 トヨタ自動車株式会社 情報処理装置、及び、情報処理方法
JP2024543875A (ja) * 2021-12-03 2024-11-26 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ５ｇコアネットワークにおける機械学習モデルの管理発明の背景

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113169897B (zh) * 2018-10-05 2024-07-05 瑞典爱立信有限公司 用于分析功能发现的方法和设备
EP4140099A4 (en) * 2020-04-21 2024-05-01 Qualcomm Incorporated Network data analytics function selection
US20220053348A1 (en) * 2020-08-12 2022-02-17 Nokia Technologies Oy Method, apparatus, and computer program product for enhanced data analytics in multiple nwdaf deployments
JP7717700B2 (ja) * 2021-04-06 2025-08-04 オッポ広東移動通信有限公司 ネットワーク機能登録方法、発見方法、装置、デバイス及び媒体
CN116546519A (zh) * 2022-01-26 2023-08-04 中国移动通信有限公司研究院 一种网络数据分析功能的选择方法、装置及设备
CN114760209B (zh) * 2022-03-29 2022-11-18 广州爱浦路网络技术有限公司 数据处理方法、系统、装置及存储介质
KR20240021056A (ko) * 2022-08-09 2024-02-16 삼성전자주식회사 무선 통신 시스템에서 네트워크 데이터 분석을 위한 데이터 수집 방법 및 장치
CN117768937A (zh) * 2022-09-26 2024-03-26 中国电信股份有限公司 信息获取方法、装置和存储介质
KR20240060336A (ko) * 2022-10-28 2024-05-08 삼성전자주식회사 무선 통신 시스템에서 로밍 단말에 대한 데이터 수집 방법 및 장치
KR20240121606A (ko) * 2023-02-02 2024-08-09 고려대학교 산학협력단 계층적 네트워크 데이터 분석 장치 및 방법
US20250024401A1 (en) * 2023-07-13 2025-01-16 Verizon Patent And Licensing Inc. Systems and methods for supporting a network data analytics function based on inputs from an anchor user plane function
WO2025041155A1 (en) * 2023-08-18 2025-02-27 Jio Platforms Limited System and method for reporting load information to network function

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190394713A1 (en) * 2018-06-22 2019-12-26 Huawei Technologies Co., Ltd. Systems and methods for reduced network signalling based on mapping
KR20200018343A (ko) * 2018-08-09 2020-02-19 한국전자통신연구원 Nwdaf를 이용한 페이징 실패 예측 방법 및 페이징 실패 예측 방법을 실행하는 페이징 실패 예측 장치

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020530703A (ja) * 2017-08-11 2020-10-22 コンヴィーダ ワイヤレス， エルエルシー 通信ネットワークにおけるネットワークデータ分析
US11140047B2 (en) * 2018-04-09 2021-10-05 Intel Corporation Network data analytics function (NWDAF) influencing fifth generation (5G) quality of service (QoS) configuration and adjustment
US10917800B2 (en) * 2018-06-22 2021-02-09 Huawei Technologies Co., Ltd. Data analytics management (DAM), configuration specification and procedures, provisioning, and service based architecture (SBA)
CN113169897B (zh) * 2018-10-05 2024-07-05 瑞典爱立信有限公司 用于分析功能发现的方法和设备
US10750371B2 (en) * 2018-12-12 2020-08-18 Verizon Patent And Licensing, Inc. Utilizing machine learning to provide closed-loop network management of a fifth generation (5G) network
US11140048B2 (en) * 2019-01-11 2021-10-05 Huawei Technologies Co., Ltd. Sharable storage method and system for network data analytics
CN113475123A (zh) * 2019-03-01 2021-10-01 瑞典爱立信有限公司 用于基于动态网络状况的局域数据网络（ladn）选择的方法和系统
US10785634B1 (en) * 2019-03-08 2020-09-22 Telefonaktiebolaget Lm Ericsson (Publ) Method for end-to-end (E2E) user equipment (UE) trajectory network automation based on future UE location
US10904739B2 (en) * 2019-04-02 2021-01-26 Electronics And Telecommunications Research Institute Network data collection method from network function device for network data analytic function
CN111901367B (zh) * 2019-05-06 2022-04-29 华为技术有限公司 一种网络数据分析方法及装置
CN112311564B (zh) * 2019-07-23 2022-04-22 华为技术有限公司 应用mos模型的训练方法、设备及系统
CN112312418A (zh) * 2019-07-26 2021-02-02 华为技术有限公司 一种用户面数据的获取方法、装置及存储介质
US10791507B1 (en) * 2019-08-05 2020-09-29 Cisco Technology, Inc. Facilitating reservation and use of remote radio units (RRUs) of radio providers for mobile service providers in virtualized radio access network (vRAN) environments
WO2021032495A1 (en) * 2019-08-16 2021-02-25 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatus and machine-readable media relating to machine-learning in a communication network
CN110677299B (zh) * 2019-09-30 2024-06-28 中兴通讯股份有限公司 网络数据采集方法、装置和系统
CN115022176B (zh) * 2019-11-06 2023-08-22 腾讯科技（深圳）有限公司 Nwdaf网元的选择方法、装置、电子设备及可读存储介质
US11188785B2 (en) * 2019-11-08 2021-11-30 Electronics And Telecommunications Research Institute Optimization of network data analysis device
US11412412B2 (en) * 2020-01-14 2022-08-09 Cisco Technology, Inc. User plane function (UPF) selection based on predicted load information
US20210367854A1 (en) * 2020-05-22 2021-11-25 Electronics And Telecommunications Research Institute Method for data collection using multiple network data analytics functions device
US20220053348A1 (en) * 2020-08-12 2022-02-17 Nokia Technologies Oy Method, apparatus, and computer program product for enhanced data analytics in multiple nwdaf deployments
EP3979101A3 (en) * 2020-10-01 2022-07-06 Nokia Technologies Oy Historical data support enhancement for network entities

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190394713A1 (en) * 2018-06-22 2019-12-26 Huawei Technologies Co., Ltd. Systems and methods for reduced network signalling based on mapping
KR20200018343A (ko) * 2018-08-09 2020-02-19 한국전자통신연구원 Nwdaf를 이용한 페이징 실패 예측 방법 및 페이징 실패 예측 방법을 실행하는 페이징 실패 예측 장치

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE, CHINA TELECOM, TENCENT, CATT, ZTE, OPPO, NEC: "New Use Case: NWDAF-assisted Smart City", 3GPP DRAFT; S2-1912302, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, NV, USA; 20191118 - 20191122, 22 November 2019 (2019-11-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051828332 *
ERICSSON, AT&T: "SCP selection of another SCP", 3GPP DRAFT; S2-2001850, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Electronic Meeting ;20200224 - 20200227, 18 February 2020 (2020-02-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051855264 *
HUAWEI: "TS 23.288 editor’s note handling", 3GPP DRAFT; S2-2002170, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20200224 - 20200227, 18 February 2020 (2020-02-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051855554 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2024543875A (ja) * 2021-12-03 2024-11-26 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ５ｇコアネットワークにおける機械学習モデルの管理発明の背景
JP7745764B2 (ja) 2021-12-03 2025-09-29 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ５ｇコアネットワークにおける機械学習モデルの管理
US12592862B2 (en) * 2021-12-03 2026-03-31 Telefonaktiebolaget Lm Ericsson (Publ) Machine learning (ML) model management in 5G core network
JP2023163269A (ja) * 2022-04-28 2023-11-10 トヨタ自動車株式会社 情報処理装置、及び、情報処理方法
JP7732390B2 (ja) 2022-04-28 2025-09-02 トヨタ自動車株式会社 情報処理装置、方法、および、プログラム

Also Published As

Publication number Publication date
JP2023518957A (ja) 2023-05-09
CN115316044B (zh) 2025-07-04
CN115316044A (zh) 2022-11-08
US11632667B2 (en) 2023-04-18
GB2593979B (en) 2022-09-14
GB202103460D0 (en) 2021-04-28
EP3883189A1 (en) 2021-09-22
JP7730832B2 (ja) 2025-08-28
US20230247411A1 (en) 2023-08-03
GB2593979A (en) 2021-10-13
US12022563B2 (en) 2024-06-25
US20210297843A1 (en) 2021-09-23
US20240349028A1 (en) 2024-10-17

Similar Documents

Publication Publication Date Title
WO2021187948A1 (en) Method and apparatus for data analytics in telecommunication network
WO2022071751A1 (en) Method and apparatus for renewing subscription for network data analysis in wireless communication system
WO2019225929A1 (en) Method and apparatus for utilizing data collection and analysis function in wireless communication system
WO2022080962A1 (en) Method and apparatus for improvements in application discovery and event exposure
WO2019160379A1 (en) Configuration of reference signals in a multi-transmission point telecommunication system
WO2020251289A1 (en) Improvements in and relating to the provision of data analytics in a telecommunication network
WO2021235902A1 (ko) 무선 통신 네트워크에서 네트워크 데이터 수집 및 분석을 위한 이동성 지원 방법 및 장치
WO2021141348A1 (ko) 이동통신 네트워크에서 단일 응용에 복수의 가상 네트워크를 제공하는 방법 및 장치
WO2020036364A1 (ko) 단말이 사설 셀룰러 네트워크를 발견하고 선택하기 위한 방법 및 장치
WO2021141265A1 (en) Improvements in and relating to dynamic path selection
WO2021091266A1 (ko) 이동통신 네트워크에서 rfsp 인덱스 선택을 위한 네트워크 분석 정보 제공하는 방법 및 장치
EP3782395A1 (en) Method and apparatus for utilizing data collection and analysis function in wireless communication system
WO2020017886A1 (en) Method and system for providing simultaneous voice and data services in en-dc capable user equipment
WO2019103552A1 (en) Resource element offsetting in a telecommunication system
WO2020231078A1 (en) Improvements in and relating to data analytics in a telecommunication network
WO2021020855A1 (en) Method and apparatus for assignment of service id
WO2021177736A1 (en) Improvements in and relating to power saving in a telecommunication network
WO2021235901A1 (ko) 무선 통신 네트워크에서 네트워크 데이터 수집 및 분석을 위한 이동성 지원 방법 및 장치
WO2022075811A1 (en) Systems and methods for managing paging collision and paging filters in a user equipment
WO2016064230A1 (en) Method and apparatus for interworking wireless lan according to camping cell
WO2021025486A1 (en) Method and apparatus for paging multi-usim ue
WO2020209694A1 (en) A method and an apparatus for determining a local frequency in wireless communication system
WO2022035266A1 (en) A method for sharing a recording status inside a mission critical video group call
WO2018143657A1 (ko) 단말의 네트워크 정보 저장 서비스 제공 방법 및 장치
WO2021235872A1 (en) Improvements in and relating to telecommunication systems

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: 21772631

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022556607

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202237059484

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21772631

Country of ref document: EP

Kind code of ref document: A1

WWG Wipo information: grant in national office

Ref document number: 202180022588.9

Country of ref document: CN