Network function monitoring and data collection
By receiving notification of data source change in the first network function operated in the core network of the wireless communication system, and sending data analysis or data acquisition requests to the new data source, the problem of data analysis and acquisition breakage during network function switching of mobile devices is solved. Seamless conversion and maintenance are achieved.
Patent Information
- Application Number
- CN202080100787.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-05-11
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-05-11
AI Technical Summary
Prior art is difficult to effectively provide and maintain data analysis and data acquisition when mobile devices are disconnected from one network function and connected to another network function.
Receive notification of data source change by a first network function operating in the core network of the wireless communication system, determine the second network function associated with the new data source, and send it a data analysis or data acquisition request to ensure data analysis and Continuity of collection.
It realizes seamless conversion and maintenance of data analysis and data acquisition when switching network functions of mobile devices, improving system flexibility and data acquisition accuracy.
Smart Images

Figure CN115606163B_ABST
Abstract
Description
Technical Field
[0001] This patent application is generally directed to wireless communications. Background Art
[0002] Mobile communication technologies are driving the world towards an increasingly connected and networked society. The rapid growth of mobile communications and technological advances have led to greater demands for capacity and connectivity. Other aspects such as data analysis, energy consumption, device cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Various technologies are being discussed, including new methods for providing higher quality of service, longer battery life, and improved performance. Summary of the invention
[0003] Among other things, this patent application describes techniques for providing and maintaining data analysis and data collection when a mobile device is disconnected from one network function and connected to another network function.
[0004] In one aspect, a wireless communication method is disclosed. The method includes: receiving, by a first network function operating in a core network of a wireless communication system in which data analysis information or data collection is provided, a notification that a data source has changed from a first data source to a second data source. The method also includes: determining, by a first network element, a second network function associated with the second data source, and sending, by the first network function, a request for data analysis information or data collection to the second network function. The method includes: receiving the data analysis information or data collection from the second network function.
[0005] In another aspect, another wireless communication method is disclosed. The method includes: receiving, by a first network function operating in a core network of a wireless communication system in which data analysis information or data collection is provided, a notification from a second network function that a data source has changed from a first data source to a second data source. The method also includes: determining, by the first network function, a third network function associated with the second data source based on the received notification, and sending, by the first network function, a request for data analysis information or data collection to the third network function. The method includes: receiving, by the first network function, data analysis information or data collection from the third network function.
[0006] In another aspect, another wireless communication method is disclosed. The method includes: determining, by a first network function operating in a core network of a wireless communication system in which data analysis information or data collection is provided, a second network function associated with a second data source. The method also includes: passing a request for data analysis information or data collection received from a third network function associated with a mobile device from the first network function to the second network function. The method includes: sending a notification of the passing to the third network function by the first network function, and receiving the data analysis information or collection data from the second network function.
[0007] These and other aspects are described throughout this application. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 Depicts examples of reference network architectures such as non-roaming 5G architectures;
[0009] Figure 2 depicts an example of a message process for a single network data analysis function (NWDAF) according to some example embodiments;
[0010] Figure 3 depicts an example architecture with multiple NWDAFs according to some example embodiments;
[0011] Figure 4 An example architecture having a NWDAF and multiple data collection coordination functions (DCCFs) according to some example embodiments is described;
[0012] Figure 5 depicts an example of changing application functionality (AF) when a mobile device moves from one service area to another service area according to some example embodiments;
[0013] Figure 6 depicts a subscription process according to some example embodiments;
[0014] Figure 7 Depicting a process for a NWDAF to collect data from a lower-level NWDAF according to some example embodiments;
[0015] Figure 8 depicts a NWDAF collecting data from a DCCF according to some example embodiments;
[0016] Fig. 9 Depicted are some examples of embodiments of the Figure 7 A similar example process where the top NWDAF has information indicating that one or more data sources have changed;
[0017] Fig.10 Depicted are some examples of embodiments of the Figure 8 A similar example process where the top NWDAF has information indicating that one or more data sources have changed;
[0018] Fig.11 Depicted are some examples of embodiments of the Fig. 9 A similar example process where the old low-level NWDAF determines which NWDAF serves the new data source;
[0019] Fig.12 Depicted are some examples of embodiments of the Fig.10 A similar example process where the old DCCF determines which DCCF serves the new data source;
[0020] Fig.13 An example of a method according to some example embodiments is depicted;
[0021] Fig.14 Another example of a method according to some example embodiments is depicted;
[0022] Fig.15 yet another example of a method according to some example embodiments is depicted;
[0023] Fig.16 An example of a wireless communication system is depicted in accordance with some example embodiments; and
[0024] Fig.17 An example block diagram of a portion of a wireless system is depicted in accordance with some example embodiments. DETAILED DESCRIPTION
[0025] Certain features are described using the example of a fifth generation (5G) wireless protocol. However, the applicability of the disclosed technology is not limited to only 5G wireless systems.
[0026] Techniques for providing and maintaining data analytics and data collection related to data analytics when a mobile device is disconnected from one network function and connected to another network function are disclosed. Data analytics is an important aspect of the ongoing operation of wireless networks for wireless networks because it enables the collection of information used by various hardware and software functions implemented by network operators and user devices to achieve efficient operation.
[0027] To support network data analysis services in the core network, the network data analysis function (NWDAF) collects data from network functions (NFs) such as access and mobility management function (AMF), session management function (SMF), etc. However, for each type of NF, there may be multiple NF instances deployed in different service areas. When the UE moves to a different service area, the NF serving the UE may also change. In order to collect data from the NF serving the UE, the NWDAF needs to know which NFs are serving the UE. Technologies for obtaining information about which NFs are serving the UE and for collecting data from the NFs are disclosed.
[0028] Figure 1 An example of a reference network architecture (such as a non-roaming 5G architecture) is depicted. A service-based interface is used within the control plane.
[0029] The 5G system architecture consists of the following network functions (NFs).
[0030] The 5G system architecture consists of the following network functions (NFs).
[0031] -Authentication Server Function (AUSF)
[0032] - Access and Mobility Management Function (AMF)
[0033] -Data Network (DN), such as carrier services, Internet access, or third-party services
[0034] - Unstructured Data Storage Function (UDSF)
[0035] -Network Open Function (NEF)
[0036] -Intermediate NEF (I-NEF)
[0037] -Network Repository Function (NRF)
[0038] - Network Slice Selection Function (NSSF)
[0039] -Policy Control Function (PCF)
[0040] -Session Management Function (SMF)
[0041] -Unified Data Management (UDM)
[0042] - Unified Data Repository (UDR)
[0043] -User Plane Function (UPF)
[0044] -UE Radio Capability Management Function (UCMF)
[0045] - Application Function (AF)
[0046] - User Equipment (UE) includes devices such as mobile phones, tablets or other mobile devices.
[0047] - A (Radio) Access Network ((R)AN) comprises base stations.
[0048] -5G Equipment Identity Register (5G-EIR)
[0049] -Network Data Analysis Function (NWDAF)
[0050] -Charging function (CHF)
[0051] The 5G system architecture also consists of the following network entities:
[0052] -Service Communication Proxy (SCP)
[0053] -Security Edge Protection Proxy (SEPP)
[0054] -Non-3GPP Interworking Function (N3IWF)
[0055] -Trusted Non-3GPP Gateway Function (TNGF)
[0056] -Wired Access Gateway Function (W-AGF)
[0057] -Data Collection Coordination Function (DCCF): coordinates data collection.
[0058] For more details on the definition of each network function, please refer to TS 23.501, the entire contents of which are incorporated herein by reference.
[0059] The UE shall register with the network to receive services that require registration. As a result of the registration process, the identifier of the AMF serving the UE will be registered at the UDM.
[0060] The 5G Core Network (5GC) supports PDU connectivity services (such as services that provide PDU exchange between the UE and the data network identified by the DNN). The PDU connectivity service is supported by PDU sessions established based on requests from the UE. The SMF is responsible for checking whether the UE PDU session establishment request complies with the user subscription. To this end, the SMF retrieves and requests to receive update notifications about SMF-level subscription data from the UDM. The UE can simultaneously establish multiple PDU sessions to the same data network or to different data networks via access networks including 3GPP access networks and non-3GPP access networks. A UE with multiple established PDU sessions can be served by different SMFs. The SMF should register and deregister in the UDM at a per-PDU session granularity.
[0061] In various wireless communication systems including 5G systems, a single instance or multiple instances of NWDAF can be deployed in the PLMN. NWDAF interacts with different entities for different purposes, including:
[0062] - Data collection based on event subscriptions provided by AMF, SMF, PCF, UDM, AF (directly or via NEF) and / or OAM;
[0063] - Retrieving information from a data repository, such as, for example, retrieving information from a UDR via the UDM for user-related information;
[0064] - Retrieve information about 3GPP NFs, such as, for example, retrieving NF related information from an NRF;
[0065] - retrieve information from the UE; and / or
[0066] - Provide analytical information (e.g. statistics or forecasts or both) to consumers (e.g. 3GPP NF, AF or OAM) on demand;
[0067] Figure 2 An example of a message process 200 is shown which may be applied to all types of analysis of a single NWDAF. As used herein, data sources may include 3GPP NF, AF, OAM and / or UE, whose own data or owned data may be collected and utilized.
[0068] At 201, an NWDAF service consumer (e.g., including NF / OAM) 220 sends a request for analysis information to the NWDAF 222, the analysis information including the type of analysis requested (e.g., UE mobility analysis, UE communication analysis, expected UE behavior parameters related to network data analysis, etc.) and / or other input parameters (e.g., the object or area for which the analysis information is requested, etc.).
[0069] At 202, a request for analytical information is received at the NWDAF 222. The NWDAF 222 retrieves from the UDM and / or NRF 224 which data sources are serving the requested object or area of interest.
[0070] At 203 , the NWDAF 222 retrieves data from various data sources 226 .
[0071] At 204 , NWDAF 222 exports the requested analysis.
[0072] At 205, the NWDAF 222 responds to the NWDAF service consumer 220 with analytical information.
[0073] Figure 3 An example architecture with multiple NWDAFs is shown. Figure 3 In the example of , NWDAF 310 (e.g., at a slice level) requests an analysis report or data collection from one of the NWDAFs, such as NWDAF 312 and / or NWDAF 314, but NWDAF 310 may be connected to a different number of NWDAFs. Figure 3In the example of FIG. 3 , NWDAF 312 requests data from one or more data sources 316A to 316N, each of which serves multiple UEs, and NWDAF 314 requests data from lower NWDAFs 318 and 320, which are connected to one or more data sources such as data sources 322 and 324, respectively. NWDAF 310 may be referred to as a higher-level NWDAF above NWDAF1 312 and NWDAF2 314, and NWDAF1 312 and NWDAF2 314 may be referred to as lower-level NWDAFs below NWDAF 310. NWDAF2 314 is a higher-level NWDAF above NWDAF21 318 and NWDAF22 320, and NWDAF21 318 or NWDAF22 320 is a lower-level NWDAF below NWDAF2 314.
[0074] Figure 4 An example architecture 400 is shown with a NWDAF and multiple DCCFs. Figure 4 4 shows NWDAF 410 and DCCF 412 and DCCF 414, but NWDAF 410 may be connected to a different number of DCCFs. Figure 4 In the example of FIG. 4 , NWDAF 410 (e.g., at a slice level) requests data from one of a plurality of DCCFs, such as DCCF 412 and / or DCCF 414, but NWDAF 410 may be connected to a different number of DCCFs. Each DCCF may provide services to a different data source based on policies such as operator configuration. DCCF 412 may receive data from one or more data sources, such as data sources 416A-416N, and DCCF 414 may receive data from one or more data sources, such as data sources 418A-418N.
[0075] Figure 5 A mobile device is shown moving from one service area to another. Figure 5 As shown, UE 530 is connected to AMF 532. As UE 530 moves, it will next connect to AMF 534 and then to AMF 536. AMF 532 and AMF 534 are in a service area 510 served by an NWDAF such as NWDAF 312 or a DCCF such as DCCF 412. AMF 536 is in a service area 520 served by an NWDAF such as NWDAF 314 or a DCCF such as DCCF 414. Apparatus and techniques for determining that a data source has changed and for acquiring data from a new data source are disclosed.
[0076] Case 1: Figure 6 shown. Figure 6 6. The subscription process according to some example embodiments is depicted. A data consumer 610 subscribes to an application function 620 for service changes related to a UE. Figure 6 As shown, data consumer 610 includes a UDM service consumer, and application function 620 includes a UDM.
[0077] For example, at 601, the UDM service consumer 610 subscribes to the UDM 620, requests one or more notifications of "UE associated NF" events (identified by event ID) for a UE or UE group, and includes the identifier of the UE and / or other filter parameters (i.e., one or more NF types, DNN, S-NSSAI). The UDM 620 detects UE associated NF events. When the UDM detects that one or more NFs serving the UE or the PDU session serving the UE (according to one or more request parameters NF type) are changed, the UDM may notify the UDM service consumer of information related to one or more NF identifiers.
[0078] At 602, the UDM 620 acknowledges and responds to the subscription request.
[0079] At 603 , based on the event, the UDM 620 detects that one or more NFs requested at 601 have changed, and sends an event report to the UDM service consumer 610 .
[0080] exist Figure 7 In case 2 depicted in FIG, the UE moves from an old data source service area to a new data source service area. One or more old data sources are served by the old lower level NWDAF, while one or more new data sources are served by the new NWDAF. The top NWDAF receives notifications of changes in the NF serving the UE via subscription events in the UDM.
[0081] When the NWDAF receives a data analysis request or a data collection request, the NWDAF determines one or more NFs serving the UE and subscribes to the "UE-associated NF events" in the UDM. The NWDAF may request data collection from one or more data sources (according to the UDM indication) via the old lower-level NWDAF, or request analysis to be generated by the old lower-level NWDAF. When the NWDAF receives a notification of "UE-associated NF events" including one or more new data source information, the NWDAF determines that the one or more new data sources are not in the service area of the old lower-level NWDAF, and determines which NWDAF provides services for the one or more new data sources (such as the new lower-level NWDAF). The NWDAF then sends a request for analysis information to the new lower-level NWDAF.
[0082] At 701a, the NWDAF service consumer 720 may send a request to the NWDAF 722 to obtain analysis information including the requested analysis type.
[0083] At 701b, the NWDAF service consumer 820 may also send a request to the NWDAF 722 for data collection.
[0084] At 702, the NWDAF 722 determines which data source(s) are serving the UE based on information retrieved from the UDM 724. In this case, the old data source 730 is serving the UE by providing data.
[0085] At 703, the NWDAF subscribes to "UE-associated NF events" in the UDM including identifiers of one or more UEs and / or one or more NF types.
[0086] At 704 , the NWDAF 722 sends a request to the old lower-level NWDAF 726 to request analysis information or data collection including the old data source information received at 702 .
[0087] The NWDAF 722 queries the NRF and / or UDM to determine which lower-level NWDAF is servicing the one or more data sources retrieved from the UDM 724 at 702. In this case, the old lower-level NWDAF 726 is servicing the old data source 730.
[0088] The old lower level NWDAF 726 receives the request 704a and collects data from the old data source. If the request is for analytical information, the old lower level NWDAF 726 should export the requested analysis. The old lower level NWDAF 726 then responds to the NWDAF 722 with analytical information or data collection according to the request.
[0089] At 705, the NWDAF 722 exports the requested analysis or aggregates the received data according to the request in 701a / b.
[0090] At 706, the NWDAF 722 responds to the NWDAF service consumer 720 according to the request in 701a / b.
[0091] At 707 , the NWDAF 722 receives the event notification subscribed at 703 , which includes new data source information.
[0092] At 708 , the NWDAF 722 determines which NWDAF services the one or more new data sources 732 (ie, queries the NRF and / or UDM that includes the one or more new data source information). In this case, the new lower-level NWDAF 728 services the new data source 732 .
[0093] At 709 a , the NWDAF may send a request to the new lower-level NWDAF 728 to request analysis information or data collection including the data source information received at 707 .
[0094] At 709b, the new lower-level NWDAF 728 collects data from the new data source 732. If the request is for analytical information, the new lower-level NWDAF 728 should export the requested analysis. The new lower-level NWDAF 728 then responds to the NWDAF 722 with analytical information or data collection according to the request.
[0095] At 710, the NWDAF 722 exports the requested analysis or aggregates the requested data based on the request 701a / b.
[0096] At 711, NWDAF 722 responds to the NWDAF service consumer according to the request at 701a / b.
[0097] exist Figure 8 In the depicted scenario 3, one or more DCCFs are deployed, and the NWDAF can collect data via one or more DCCFs. The UE can move from an old data source service area to a new data source service area. One or more old data sources are served by the old DCCF, and one or more new data sources are served by the new DCCF. The NWDAF receives information from the UDM about the NF serving the UE that changes via subscription events.
[0098] At 801a, the NWDAF service consumer 820 may send a request to the NWDAF 822 to obtain analysis information including the requested analysis type.
[0099] At 801b, the NWDAF service consumer 820 may also send a request to the NWDAF 822 for data collection.
[0100] At 802, the NWDAF 822 determines which data source(s) are serving the UE based on information retrieved from the UDM 824. In this case, the old data source 830 is providing data to the UE.
[0101] At 803, the NWDAF 822 subscribes at the UDM 824 to NF events associated with the UE including one or more UE identifiers and / or one or more NF types.
[0102] At 804a / b, the NWDAF may query the NRF for which the DCCF serves one or more old data sources 830. In this case, the old DCCF 826 serves the old data source 830.
[0103] At 804a, the NWDAF sends a request to the old DCCF 826 for data collection.
[0104] At 804b, the old DCCF 826 collects data from one or more old data sources 830 and responds to the NWDAF 822 including the collected data according to the request.
[0105] At 805, the NWDAF 822 exports the requested analysis or aggregates the requested data collection according to the request at 801a / b.
[0106] At 806, the NWDAF 822 responds to the NWDAF service consumer 820 according to the request at 801a / b.
[0107] At 807 , the NWDAF 822 receives the event notification subscribed at 803 , which includes new data source information.
[0108] At 808 , the NWDAF 822 determines which DCCF serves the one or more new data sources 832 (ie, queries the NRF and / or UDM including the one or more new data source information). In this case, the new DCCF 828 serves the one or more new data sources 832 .
[0109] At 809a, the NWDAF 822 sends a request to the new DCCF 832 for data collection.
[0110] At 809b, the new DCCF 828 collects data from the new data source 832 and responds to the NWDAF 822 with the collected data according to the request.
[0111] At 810, the NWDAF 822 derives the requested analysis or aggregates the requested data collection according to the request at 801a / b.
[0112] At 811, the NWDAF 822 responds to the NWDAF service consumer 820 according to the request at 801a / b.
[0113] Fig. 9The situation described in 4 is similar to Figure 7 2, but the top NWDAF has an indication that one or more data sources have changed, and according to a message from the old lower-level NWDAF, the one or more new data sources are not associated with the old lower-level NWDAF service area.
[0114] Components 901-905 are similar to Figure 7 The top NWDAF 922 does not need to subscribe to the UDM 924.
[0115] At 901a, the NWDAF service consumer 920 may send a request to the NWDAF 922 to obtain analysis information including the requested analysis type.
[0116] At 901b, the NWDAF service consumer 920 may also send a request to the NWDAF 922 for data collection.
[0117] At 902, the NWDAF 922 determines which data source(s) are serving the UE based on information retrieved from the UDM 924. In this case, the old data source is serving the UE by providing data.
[0118] At 903 , the NWDAF 922 sends a request to the old lower-level NWDAF 926 to request analysis information or data collection including one or more data source information received in 902 .
[0119] The NWDAF 922 may query the NRF and / or UDM for information about which lower-level NWDAF is serving one or more legacy data sources 928. In this case, the legacy lower-level NWDAF 926 is serving the legacy data source 928.
[0120] The old lower level NWDAF 926 receives the request and collects data from the old data source 928 via the data collection subscription event. If the request is for analysis information, the old lower level NWDAF 926 should export the requested analysis. Then, the old lower level NWDAF 926 sends the analysis information or collects data to the NWDAF 922 according to the request.
[0121] At 904, the NWDAF 922 exports the requested analysis or aggregates the requested collected data according to the request at 901a / b.
[0122] At 905, the NWDAF 922 responds to the NWDAF service consumer 920 according to the request at 901a / b.
[0123] At 906, when the UE moves from one or more old data source 928 service areas to one or more new data source service areas, the UE's context including subscribed events in the old data sources is transferred to the new data sources.
[0124] At 907 , one or more new data sources send UE-related data to the old lower-level NWDAF 926 according to the subscription event request.
[0125] At 908, the old lower level NWDAF 926 determines that one or more new data sources 930 are not in its service area and sends a message to the NWDAF 922 according to the request at 903a including the one or more new data source information.
[0126] At 909 , the NWDAF 922 determines which NWDAF services the one or more new data sources 930 (ie, queries the NRF and / or UDM that includes the one or more new data source information). In this case, the new data source 930 is served by a new lower-level NWDAF 927 .
[0127] At 910, the NWDAF sends a request to a new lower-level NWDAF 927 to request analysis information or data collection including one or more new data source information.
[0128] The new lower level NWDAF 927 receives the request and collects data from one or more new data sources. If the request is for analytical information, the new lower level NWDAF 927 should export the requested analysis. The new lower level NWDAF 927 then responds to the NWDAF 922 with analytical information or collected data, depending on the request.
[0129] At 911, NWDAF 922 exports the requested analysis or aggregates the requested collected data according to the request at 901a / b.
[0130] At 912, the NWDAF 922 responds to the NWDAF service consumer 920 according to the request at 901a / b.
[0131] Fig.10 Case 5 described in is similar to Case 3, where the top NWDAF has information indicating that one or more data sources have changed, and according to a message from the old lower-level DCCF, the one or more new data sources are not in the service area of the old lower-level DCCF. Elements 1001-1005 are similar to Figure 8 Elements 801, 802, 804-806 are shown in case 3. The top NWDAF does not need to subscribe to the UDM.
[0132] At 1001a, the NWDAF service consumer 1020 may send a request to the NWDAF 1022 to obtain analysis information including the requested analysis type.
[0133] At 1001b, the NWDAF service consumer 1020 may send a request to the NWDAF 1022 for data collection.
[0134] At 1002, the NWDAF 1022 determines which data source(s) are serving the UE based on information retrieved from the UDM 1024. In this case, the old data source 1030 is serving the UE by providing data.
[0135] At 1003a / b, the NWDAF 1022 may query the NRF for which the DCCF serves one or more legacy data sources 1030. In this case, the legacy DCCF 1026 serves one or more legacy data sources 1030.
[0136] At 1003a, the NWDAF 1022 sends a request to the old DCCF 1026 for data collection.
[0137] At 1003 b , the old DCCF 1026 collects data from one or more old data sources 1030 via a data collection subscription event, and feeds the collected data back to the NWDAF 1022 according to the request.
[0138] At 1005, the NWDAF 1022 exports the requested analysis or aggregates the requested collected data according to the request at 1001a / b.
[0139] At 1006, when the UE moves from one or more old data sources 1030 in the old service area to one or more new data sources in the new service area, the UE's context including subscribed events in the old data sources is transferred to the new data sources.
[0140] At 1007 , one or more new data sources 1032 send UE-related data to the old DCCF 1026 according to the subscription event received at 1006 .
[0141] At 1008, the old DCCF 1026 determines that the one or more new data sources 1032 are not in the service area of the old DCCF 1026, and sends a message including the one or more new data source information to the NWDAF 1022 according to the request at 1003a.
[0142] At 1009 , the NWDAF 1022 determines which DCCF services the one or more new data sources 1032 (ie, queries the NRF and / or UDM including the one or more new data source information). In this case, the new data source is served by the new DCCF 1028 .
[0143] At 1010, the NWDAF 1022 sends a request to the new DCCF 1028 for data collection.
[0144] The new DCCF 1028 collects data from one or more new data sources 1032 and feeds the collected data back to the NWDAF 1022 according to the request.
[0145] At 1011 , the NWDAF 1022 exports data analytics or aggregates the requested collected data requested by the NWDAF service consumer 1020 according to the request at 1001a / b.
[0146] At 1012, the NWDAF responds to the NWDAF service consumer 1020 according to the request at 1001a / b.
[0147] Fig.11 Case 6 depicted in is similar to Case 4, but the old lower-level NWDAF determines which NWDAF serves the new data source and passes the request received from the top NWDAF to the new lower-level NWDAF. Elements 1101-1107 are similar to elements 901-907 in Case 4.
[0148] At 1108, the old lower-level NWDAF 1126 determines that the one or more new data sources 1132 are not in the service area of the NWDAF 1126, and determines which NWDAF is serving (i.e., querying from the NRF or UDM) the one or more new data sources 1132. In this case, the new lower-level NWDAF 1128 serves the one or more new data sources 1132.
[0149] At 1109, the old lower level NWDAF 1126 will be Fig.10 The request received from the top NWDAF 1122 at 1003a in is passed to the new lower level NWDAF 1128.
[0150] The old lower level NWDAF 1126 may also transfer UE-related information previously received from one or more old data sources 1130 , data analysis information derived therefrom prior to the transfer, to the new lower level NWDAF 1128 .
[0151] At 1110 , the old lower-level NWDAF 1126 may notify the top NWDAF 1122 of the request to be passed to the new lower-level NWDAF 1128 .
[0152] At 1111 , the new lower-level NWDAF 1128 sends a request to one or more new data sources 1132 for data collection.
[0153] At 1112 , one or more new data sources 1132 feed data to the new lower level NWDAF 1128 based on the request at 1111 .
[0154] If the request at 1109 is for analytical information, the new lower-level NWDAF 1128 should derive the requested analysis based on the collected data from the one or more new data sources 1132. The new lower-level NWDAF 1128 then feeds the analytical information or collected data back to the top NWDAF 1122 based on the request at 1109.
[0155] At 1113, NWDAF 1122 Fig. 9 The request at 901a / b shown exports the requested analysis or aggregates the requested collected data.
[0156] At 1114, NWDAF 1122 Fig. 9 The request at 901a / b in the above example responds to the NWDAF service consumer 1120.
[0157] Fig.12 Case 7 depicted in FIG. 5 is similar to case 5, but the old DCCF determines which DCCF serves the new data source and passes the request received from the top NWDAF to the new DCCF.
[0158] Components 1201-1207 are similar to Fig.10 Elements 1001-1007 in case 5 are shown.
[0159] At 1208, the old DCCF 1226 determines that one or more new data sources 1232 are not in the service area of the old DCCF 1226, and determines which DCCF is serving the one or more new data sources (i.e., querying from NRF or UDM). In this case, the new DCCF 1228 serves the one or more new data sources 1232.
[0160] At 1209, the old DCCF 1226 will be Fig.10 The request received from the top NWDAF at 1003a is passed to the new DCCF 1228 .
[0161] The old DCCF 1226 may also transfer UE-related information previously received from the old data source 1230 to the new DCCF 1228 .
[0162] At 1210 , the old DCCF 1226 may notify the top NWDAF 1222 of the request to be passed to the new DCCF 1228 .
[0163] At 1211, the new DCCF 1228 sends a request to one or more new data sources 1232 for data collection.
[0164] At 1212 , one or more new data sources feed data to the new DCCF 1228 based on the request at 1211 .
[0165] The new DCCF 1228 feeds the acquisition data to the top NWDAF 1222 based on the request at 1209 .
[0166] At 1213, NWDAF 1222 Fig.10 The request at 1110a / b shown exports the requested analysis or aggregates the requested collected data.
[0167] At 1214, NWDAF Fig.10 The request at 1110a / b is shown to be responded to by the NWDAF service consumer 1220.
[0168] In some example embodiments related to the above situations 1-3, one or more of the following features are included.
[0169] 1) For UDM, a new monitoring event "UE associated NF" is introduced to UDM. UDM detects the event that the NF providing service for UE or UE's PDU session is changed, and notifies the consumer according to the subscription request.
[0170] 2) For NWDAF, when NWDAF receives an analysis information request or a data collection request, NWDAF subscribes to UDM to monitor one or more UE-associated NFs, where the UE-associated NFs include an event ID (ie, "UE-associated NF") and one or more UE identifiers.
[0171] The NWDAF receives a notification that one or more NFs associated with one or more UEs are changed by new data source information. The NWDAF performs operations such as:
[0172] a) Request a new lower-level NWDAF to obtain data analysis information or data collection. Before sending the request message, the NWDAF determines which NWDAF serves one or more new data sources (i.e., queries the NRF and / or UDM including one or more new data source information); or
[0173] b) Requesting DCCF to collect data Before sending the request message, the NWDAF may query the NRF and / or UDM which DCCF is serving one or more NFs associated with one or more new UEs.
[0174] In some example embodiments related to the above-mentioned situations 4 and 5, the following features are included.
[0175] 1) The lower-level NWDAF or DCCF determines that one or more data sources providing the collected data are not in its service area, and then notifies the top NWDAF that one or more data sources have been changed, including one or more new data source information,
[0176] 2) For the top NWDAF:
[0177] a) Upon receiving a message that one or more data sources have been changed, the NWDAF queries the NRF or UDM which NWDAF or DCCF is serving the one or more new data sources; (the NRF feeds back new NWDAF information, i.e., a new lower-level NWDAF or a new DCCF);
[0178] b) Send a request for data collection or analysis information to a new lower-level NWDAF or DCCF; and / or
[0179] c) receiving collected data or analysis information from a new lower-level NWDAF or a new DCCF; in some example embodiments related to the above-mentioned situations 6 and 7, the following features are included.
[0180] 1) Lower level NWDAF or DCCF:
[0181] a) Determine that one or more data sources providing collected data are not in its service area, and then query the NRF or UDM which NWDAF or DCCF is serving one or more new data sources; the NRF feeds back new NWDAF information, i.e., a new lower-level NWDAF or a new DCCF;
[0182] b) passing the request received from the top NWDAF to a new lower-level NWDAF or a new DCCF;
[0183] c) passing previously acquired data or analysis information to a new lower level NWDAF or new DCCF; and / or
[0184] d) Notify the top NWDAF, which requests to be changed to a new lower-level NWDAF or a new DCCF.
[0185] Fig.13 An example of a method according to some example embodiments is depicted. At 1310, the method includes: receiving, by a first network function operating in a core network of a wireless communication system in which data analysis information or data collection is provided, a notification from a second network function that a data source has changed from a first data source to a second data source. At 1320, the method includes: determining, by a first network element, a second network function associated with the second data source. At 1330, the method includes: sending, by the first network function, a request for data analysis information or data collection to the second network function. At 1340, the method includes: receiving data analysis information or data collection from the second network function. In some example embodiments, the first network function is a NWDAF such as a top NWDAF, and the second network function is an old lower NWDAF or an old DCCF.
[0186] Fig.14 An example of a method according to some example embodiments is depicted. At 1410, the method includes: receiving, by a first network function operating in a core network of a wireless communication system in which data analysis information or data collection is provided, a notification that a data source has changed from a first data source to a second data source. At 1420, the method includes: determining, by the first network function, a third network function associated with the second data source based on the received notification. At 1430, the method includes: sending, by the first network function, a request for data analysis information or data collection to the third network function. At 1440, the method includes: receiving, by the first network function, the data analysis information or data collection from the third network function. In some example embodiments, the first network function is a NWDAF such as a top NWDAF, the second network function is an old lower NWDAF or an old DCCF, and the third network function is a new lower NWDAF or a new DCCF.
[0187] Fig.15An example of a method according to some example embodiments is depicted. At 1510, the method includes: determining, by a first network function operating in a core network of a wireless communication system in which data analysis information or data collection is provided, a second network function associated with a second data source. At 1520, the method includes: passing a request for data analysis information or data collection received from a third network function associated with a mobile device, from the first network function to the second network function. At 1530, the method includes: sending a notification of the passing by the first network function to the third network function. At 1540, the method includes: receiving data analysis information or collection data from the second network function. In some example embodiments, the first network function is an old lower NWDAF or an old DCCF, the second network function is a new lower NWDAF or a new DCCF, and the third network function is a NWDAF, such as a top NWDAF.
[0188] Fig.16 An example of a wireless communication system 1600 in which the technology according to one or more embodiments of the present technology can be applied is shown. The wireless communication system 1600 may include one or more base stations (BSs) 1605a, 1605b, one or more wireless devices 1610a, 1610b, 1610c, 1610d, and a core network 1625. The base stations 1605a, 1605b may provide wireless services to the wireless devices 1610a, 1610b, 1610c, and 1610d in one or more wireless sectors. In some embodiments, the base stations 1605a, 1605b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.
[0189] The core network 1625 can communicate with one or more base stations 1605a, 1605b. The core network 1625 provides connections with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to subscribed wireless devices 1610a, 1610b, 1610c, and 1610d. The first base station 1605a can provide wireless services based on a first wireless access technology, and the second base station 1605b can provide wireless services based on a second wireless access technology. Depending on the deployment scenario, base stations 1605a and 1605b can be quasi-co-located or can be installed separately on site. Wireless devices 1610a, 1610b, 1610c, and 1610d can support a variety of different wireless access technologies. The techniques and embodiments described in this application can be implemented by base stations, other network entities, and / or by a combination of wireless devices or base stations and mobile device devices described in this application.
[0190] Fig.171705 is a block diagram representation of a portion of a wireless site according to one or more embodiments of the present technology in which it can be applied. A wireless site 1705 such as a base station, other network entity, or wireless device (or UE) may include a processor electronic device 1710 such as a microprocessor that implements one or more wireless technologies presented in this application. The wireless site 1705 may include a transceiver electronic device 1715 for sending and / or receiving wireless signals through one or more communication interfaces (e.g., antenna 1720). The wireless site 1705 may include other communication interfaces for sending and receiving data. The wireless site 1705 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, the processor electronic device 1710 may include at least a portion of the transceiver electronic device 1715. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the wireless site 1705. In some embodiments, the wireless site 1705 may be configured to perform the methods described herein.
[0191] It should be understood that the present application discloses techniques that can be implemented in various embodiments to establish and manage multicast sessions in various scenarios. The disclosed embodiments and other embodiments, modules, and functional operations described in the present application can be implemented in digital electronic circuits, or in computer software, firmware, or hardware (including the structures disclosed in the present application and their equivalent structures), or in a combination of one or more of them. The disclosed embodiments and other embodiments can be implemented as one or more computer program products (i.e., one or more modules of computer program instructions encoded on a computer-readable medium) for execution by a data processing device or control of the operation of the data processing device. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a storage device, a composition that affects a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" covers all devices, equipment, and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, for example, code that constitutes a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, eg, a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
[0192] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program under consideration, or in multiple collaborative files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program may be deployed to be executed on one computer or multiple computers, or to be executed on multiple computers distributed in multiple locations and interconnected by a communications network.
[0193] The processes and logic flows described in this application can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by special purpose logic circuits, and the apparatus can also be implemented as special purpose logic circuits, for example, FPGAs (field programmable gate arrays) or ASICs (application specific integrated circuits).
[0194] For example, processors suitable for executing computer programs include general-purpose microprocessors and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include or be operably coupled to one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data to receive data from the mass storage device or to transfer data to it, or both. However, a computer need not have such a device. Computer-readable media suitable for storing computer program instructions and data include various forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM optical disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit.
[0195] Although this patent application contains many details, these should not be interpreted as limitations on the scope of any invention or the scope of what may be claimed, but rather as descriptions of features that may be specific to a particular embodiment of a particular invention. Certain features described in this patent application in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although the above-mentioned features may be described as working in certain combinations and even initially claimed as such, in some cases, one or more features from the combination may be deleted from the combination, and the combination may involve sub-combinations or variations of sub-combinations.
[0196] Similarly, although operations are described in a particular order in the drawings, this should not be understood as requiring that the operations be performed in the particular order or sequence shown, or that all of the operations shown be performed, in order to achieve the desired results. In addition, the separation of various system components in the embodiments described in this patent application should not be understood as requiring such separation in all embodiments.
[0197] Only a few implementations and examples are described, and other implementations, enhancements, and changes may be made based on what is described and illustrated in this patent application.
Claims
1. A wireless communication method, comprising: receiving, by a first network function operating in a core network of a wireless communication system, data related to a user equipment from a second data source; determining, by the first network function, that a second data source is not within a service area of the first network function and that the second network function is associated with the second data source; communicating, from the first network function to the second network function, a request for obtaining data analysis information or data collection, wherein the request is received from a third network function associated with the user equipment; A notification is sent by the first network function to the third network function that the request is passed to the second network function.
2. The method according to claim 1, wherein: The third network function is a network data analysis function NWDAF, the first network function is an old lower-level NWDAF, wherein the old lower-level NWDAF is lower than the NWDAF in the logical hierarchy, and wherein the second network function is a new lower-level NWDAF at the same logical hierarchy as the old lower-level NWDAF.
3. The method according to claim 1, wherein: The third network function is a network data analysis function NWDAF, the first network function is an old lower-level data acquisition coordination function DCCF, wherein the old lower-level DCCF is lower than the NWDAF in the logical hierarchy, and wherein the second network function is a new lower-level DCCF at the same logical hierarchy as the old lower-level DCCF.
4. The method according to claim 1, wherein: The determination comprises requesting an indication from a network repository function, NRF, or a unified data management, UDM, of a new lower level NWDAF or a new lower level DCCF serving the second data source.
5. The method according to claim 1, further comprising: Previously received user equipment related information and previously received data analysis information are communicated from the first network function to the second network function, wherein the previously received data analysis information is received from the first data source.
6. A communication device comprising a processor configured to implement the method according to any one or more of claims 1 to 5.
7. A computer program product having stored thereon a code which, when executed by a processor, causes the processor to carry out the method according to any one or more of claims 1 to 5.
