Configuration of minimization of drive test measurement refinement

Abstract

A method performed by a user equipment (UE) is provided. The method includes sending, to a core network via a radio access network (RAN), information indicating that the UE supports a plurality of refinements of minimization of drive test (MDT) measurements. The method includes receiving, from the RAN, information indicating that the UE is to perform an MDT measurement and information indicating a refinement of the plurality of refinements according to which the MDT measurement is to be reported. The method includes performing the MDT measurement. And the method includes reporting the MDT measurement to the RAN according to the refinement.

Description

Technical Field

[0001] This disclosure relates generally to telecommunications, and more particularly to subscriber and device tracking in telecommunications systems. Background Technology

[0002] A telecommunications system can be viewed as a facility that enables communication between two or more entities, such as between two user equipments (UEs), between a UE and a base station, between two base stations, between a UE and network functions of a communication network, and / or between a base station and other nodes. A telecommunications system may include a communication network and one or more UEs. Communication sessions may include, for example, data communications used to carry communications (such as voice, video, email, SMS, multimedia, and / or content data). Non-limiting examples of services provided include two-way or multi-way calling, data communication or multimedia services, and access to data network systems such as the Internet.

[0003] In telecommunications systems that include wireless communication networks, at least a portion of a communication session between at least two stations occurs over a wireless link. Examples of wireless communication networks include Public Land Mobile Networks (PLMNs), satellite-based communication networks, and various wireless local networks, such as Wireless Local Area Networks (WLANs). Some wireless communication networks can be divided into cells and are therefore often referred to as cellular networks.

[0004] Users can access telecommunications systems using appropriate communication equipment or terminals. A user's communication equipment may be referred to as user equipment (UE) or user device. The communication equipment is provided with appropriate signal receiving and transmitting means to enable communication, such as enabling access to a communication network or direct communication with other users. The communication equipment can access, for example, a carrier provided by a base station in a cell, and transmit and / or receive communication on that carrier.

[0005] Telecommunications systems have evolved through multiple generations, each bringing advancements in speed, capacity, and functionality. Evolved Packet System (EPS) represents the 4G architecture, encompassing Long Term Evolution (LTE) and LTE-Advanced (LTE-A) as its radio access technologies. 5G systems (5GS) are built on top of EPS, introducing 5G New Radio (5G NR) for enhanced mobile broadband, massive machine-type communications, and ultra-reliable low-latency communications. Future 6G systems (6GS) are expected to further revolutionize the telecommunications field with even more advanced capabilities. These systems are interconnected, and 5GS is designed to interoperate with EPS for seamless service continuity. The 3rd Generation Partnership Project (3GPP) plays a crucial role in developing and maintaining standards for these telecommunications systems, ensuring global interoperability and evolution from Universal Mobile Telecommunications System (UMTS) (3G) to the continuously evolving 6G technology. Summary of the Invention

[0006] The example implementations of this disclosure are intended for the telecommunications field, and in particular for subscriber and device tracking in telecommunications systems. This disclosure includes, but is not limited to, the following example implementations.

[0007] The first example implementation provides a method performed by a user equipment (UE), the method comprising: sending information to a core network via a radio access network (RAN) indicating that the UE supports multiple granularities of minimized drive test (MDT) measurements; receiving from the RAN information indicating that the UE will perform MDT measurements, and information indicating the granularity among the multiple granularities, according to which the MDT will be reported; performing the MDT measurements; and reporting the MDT measurements to the RAN according to the granularity.

[0008] In the first example implementation, sending includes sending a message that includes information indicating that the UE supports multiple levels of granularity in MDT measurements.

[0009] In the first example implementation, the message includes a registration request, which is carried to the RAN in the access network message.

[0010] In the first example implementation, the granularity includes the quantization level, wherein performing an MDT measurement includes: acquiring a sample of the MDT measurement; and quantizing the sample to generate a quantized value of the MDT measurement based on the quantization level, and wherein reporting the MDT measurement to the RAN includes: reporting the quantized value of the MDT measurement.

[0011] In the first example implementation, the granularity includes a quantization level, wherein performing an MDT measurement includes: acquiring a sample of the MDT measurement; quantizing the sample to generate a first quantized value of the MDT measurement based on a quantization level higher than the quantization level; and requantizing the first quantized value to generate a second quantized value of the MDT measurement based on the quantization level; and wherein reporting the MDT measurement to the RAN includes: reporting the second quantized value of the MDT measurement.

[0012] In the first example implementation, the method further includes storing the first quantization value of the MDT measurement.

[0013] In the first example implementation, the UE will perform an MDT measurement for a tracking session, and the method further includes: receiving a second message from the RAN indicating that the UE will perform an MDT measurement for a second tracking session, wherein the second message indicates a higher quantization level; and reporting a first quantization value of the MDT measurement to the RAN.

[0014] The second example implementation provides a method comprising: receiving a configuration for performing a minimized drive test (MDT) measurement, the configuration including information indicating the required granularity for the MDT measurement; determining one or more user equipments (UEs) having the capability to meet the required granularity for the MDT measurement; and instructing the one or more UEs to: perform the MDT measurement and report the MDT measurement according to the required granularity.

[0015] In the second example implementation, receiving the configuration for performing MDT measurements includes: receiving a request from the management system to activate a tracking session, wherein the request to activate the tracking session includes the configuration for performing MDT measurements for the tracking session.

[0016] In a second example implementation, the method further includes: receiving context information from the core network for a plurality of UEs, wherein for each of the plurality of UEs, the context information indicates the capability of the corresponding UE to support a plurality of granularities of MDT measurement, and wherein one or more UEs having the capability to meet the required granularity are determined based on the context information.

[0017] In the second example implementation, receiving the configuration for performing MDT measurements includes: receiving a message from the core network to start a tracing session, wherein the message to start a tracing session includes the configuration for performing MDT measurements for the tracing session.

[0018] In the second example implementation, the required level of precision is either the minimum precision required for MDT measurements or the exact precision required for MDT measurements.

[0019] In the second example implementation, the configuration for performing MDT measurements further includes: information indicating the required number of UEs to be used to perform MDT measurements, and wherein determining one or more UEs having the capability to meet the required granularity for MDT measurements includes: determining that one or more UEs meet the required number of UEs to be used to perform MDT measurements.

[0020] In the second example implementation, the required number of UEs is either the minimum number E of UEs to be used to perform MDT measurements or the exact number of UEs to be used to perform MDT measurements.

[0021] A third example implementation provides a method comprising: receiving a request to activate a tracking session, the request including a configuration for performing a minimized drive test (MDT) measurement, the configuration including information indicating the required granularity for the MDT measurement; determining one or more user equipments (UEs) capable of meeting the required granularity for the MDT measurement; and sending the configuration for performing the MDT measurement to a mobility management network function serving the one or more UEs, so that the mobility management network function can initiate a tracking session based on the configuration for the MDT measurement.

[0022] In the third example implementation, receiving the request includes: receiving a request including a configuration for MDT measurements performed by one or more UEs, and wherein determining one or more UEs includes: determining one or more UEs having the capability to meet the required granularity for MDT measurements.

[0023] In the third example implementation, receiving the request includes: receiving a request including a configuration for performing MDT measurements in one or more cells of the radio access network, and wherein determining one or more UEs includes: determining one or more UEs served by one or more cells that have the capability to meet the required granularity for MDT measurements.

[0024] In the third example implementation, the required level of precision is either the minimum precision required for MDT measurements or the exact precision required for MDT measurements.

[0025] In the third example implementation, the configuration for MDT measurement further includes: information indicating the required number of UEs to be used to perform the MDT measurement, and wherein determining one or more UEs having the capability to meet the required granularity for the MDT measurement includes: determining that one or more UEs meet the required number of UEs to be used to perform the MDT measurement.

[0026] In the third example implementation, the required number of UEs is either the minimum number of UEs that will be used to perform MDT measurements or the exact number of UEs that will be used to perform MDT measurements.

[0027] A fourth example implementation provides a method comprising: receiving, from a Session Management Network Function (SM NF), a charging data request for a Protocol Data Unit (PDU) session for a User Equipment (UE), wherein the charging data request includes information instructing the UE to support multiple granularities of Minimized Drive Test (MDT) measurements; based on the charging data request, initiating a Charging Data Record (CDR) for the PDU session for the UE; receiving, from the SM NF, charging information associated with the PDU session, wherein the charging information is categorized into one or more categories corresponding to one or more granularities of multiple granularities of MDT measurements reported by the UE; and updating the CDR according to the charging information, wherein the CDR includes one or more counters updated by categories of the one or more categories, and wherein each of the one or more counters is associated with a corresponding charging policy.

[0028] In the fourth example implementation, the method further includes sending a billing report to the SM NF, the billing report including information indicating one or more values ​​of the one or more counters.

[0029] A fifth example implementation provides an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform a method of any one of the first to fourth example implementations.

[0030] A sixth example implementation provides an apparatus including components for performing a method of any one of the first to fourth example implementations.

[0031] A seventh example implementation provides a computer-readable medium including instructions that, in response to execution by at least one processor, cause a device to perform a method of any one of the first to fourth example implementations.

[0032] The eighth example implementation provides a computer-readable storage medium including instructions that, in response to execution by at least one processor, cause a device to perform a method of any one of the first to fourth example implementations.

[0033] The ninth example implementation provides a computer program including instructions that, in response to execution by at least one processor, cause a device to perform the method of any one of the first to fourth example implementations.

[0034] These and other features, aspects, and advantages of this disclosure will become apparent upon reading the following detailed description and the accompanying drawings (which will be briefly described below). This disclosure includes any combination of two, three, four, or more features or elements set forth in this disclosure, whether such features or elements are explicitly combined or otherwise referenced in the specific example implementations described herein. This disclosure is intended to be interpreted holistically such that, unless the context of this disclosure explicitly specifies otherwise, any separable feature or element of this disclosure (whether in any aspect of this disclosure or in example implementations) should be considered composable.

[0035] Therefore, it should be understood that the content of this invention is provided only for the purpose of summarizing some exemplary implementations in order to provide a basic understanding of some aspects of this disclosure. Consequently, it should be understood that the above exemplary implementations are merely examples and should not be construed as limiting the scope or spirit of this disclosure in any way. Other exemplary implementations, aspects, and advantages will become apparent from the following detailed description taken in conjunction with the accompanying drawings (which illustrate by way of example the principles of some of the described exemplary implementations). Attached Figure Description

[0036] Therefore, an exemplary implementation of this disclosure has been described in general terms. Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0037] Figure 1 The illustration shows a telecommunications system implemented according to some examples of this disclosure, including one or more public land mobile networks (PLMNs) coupled to one or more external data networks;

[0038] Figure 2 The diagram illustrates a PLMN implementation based on some examples;

[0039] Figure 3 A more detailed description is given based on some examples. Figure 2 The core network of the PLMN;

[0040] Figure 4A and 4B The diagram illustrates a process for managing MDT granularity, implemented according to various examples, including granularity requirements for Minimum Reporting Drive Test (MDT) measurements.

[0041] Figure 5A and 5B The diagram illustrates the granularity process for signaling-based MDTs implemented according to various examples, including granularity requirements for reported MDT measurements.

[0042] Figure 6 This is a diagram illustrating the process for performing MDT measurements, implemented based on some examples;

[0043] Figure 7 It is a diagram of the process for establishing a Protocol Data Unit (PDU) session, implemented based on some examples, where the billing information associated with the PDU session is categorized into categories corresponding to the granularity of the reported MDT measurements.

[0044] Figure 8A , 8B 8C and 8D are flowcharts illustrating the steps in a method executed by a user equipment (UE) according to various examples;

[0045] Figure 9 , 10 And 11 are flowcharts illustrating the steps in a method implemented according to various examples; and

[0046] Figure 12 The diagram illustrates a device implemented based on some examples. Detailed Implementation

[0047] Some implementations of this disclosure will now be described in more detail below with reference to the accompanying drawings, in which some, but not all, implementations of this disclosure are shown. In fact, various implementations of this disclosure may be embodied in many different forms and should not be construed as limited to the implementations transmitted herein; rather, these exemplary implementations are provided so that the content of this disclosure will be exhaustive and complete, and will fully convey the scope of this disclosure to those skilled in the art. The same reference numerals refer to the same elements throughout the drawings.

[0048] Unless otherwise specified or the context clearly indicates otherwise, references to first, second, etc., should not be interpreted as implying a particular order.

[0049] As used herein, unless otherwise specified or the context clearly indicates otherwise, "OR" in the operand set is "inclusive OR," meaning it is true if and only if one or more of the operands are true, rather than "exclusive OR," which is false if all operands are true. Thus, for example, "[A] OR [B]" is true if [A] is true, or if [B] is true, or if both [A] and [B] are true. Furthermore, unless otherwise specified or the context clearly indicates otherwise for the singular form, the articles "a" and "an" both mean "one or more." Additionally, it should be understood that, unless otherwise specified, the terms "data," "content," "digital content," "information," and similar terms are sometimes used interchangeably. The term "network" can refer to a set of interconnected computers including clients and servers; and within a network, these computers may be directly interconnected or indirectly interconnected through various components, including via one or more switches, routers, gateways, access points, etc.

[0050] This disclosure discusses telecommunications systems and mobile or cellular networks and their user equipment, and while specific terms may be used, these terms are broadly applicable across a variety of technologies. For example, while this disclosure may refer to radio access technologies such as 5G NR and 5G Advanced, it also relates to next-generation radio access technologies such as 6G. The example implementations of this disclosure described herein also refer to Public Land Mobile Networks (PLMNs) and Mobile Network Operators (MNOs), but the example implementations are equally applicable to Standalone Non-Public Networks (SNPNs).

[0051] While some examples and figures focus on radio access networks (RANs), particularly those operating according to 3GPP standards for 5G NR (often referred to as 3GPP access or 3GPP access network), the example implementations are applicable to any type of access network. This includes not only 3GPP access networks but also non-3GPP access networks, such as wired access, untrusted non-3GPP access networks, and trusted non-3GPP access networks using Radio Access Gateway Functions (W-AGF), Non-3GPP Interoperability Functions (N3IWF), or Trusted Non-3GPP Gateway Functions (TNGF) to connect to the core network of a mobile or cellular network (e.g., a 5G core network (5GC) or a 6G core network (6GC)).

[0052] Furthermore, as used in this application, the term "circuit system" may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation in an analog and / or digital circuit system only) and (b) a combination of hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuits with software / firmware and (ii) any portion of (multiple) hardware processors (including (multiple) digital signal processors) having software, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or a server) to perform various functions; or (c) (multiple) hardware circuits and / or (multiple) processors (such as (multiple) microprocessors or portions of (multiple) microprocessors) that require software (e.g., firmware) to operate, but where operation does not require software, the software may be absent.

[0053] The above definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit system" also covers only hardware circuitry or a processor (or multiple processors), or portions of hardware circuitry or a processor and / or their accompanying software and / or firmware implementations. The term "circuit system" also covers, for example, and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0054] Figure 1 A telecommunications system 100 implemented according to various examples of this disclosure is illustrated. Examples of suitable telecommunications systems include UMTS, EPS, and 5GS, as well as future 6GS. A telecommunications system (also referred to as a system) typically includes one or more mobile or cellular networks that can interoperate between different telecommunications systems. As shown, for example, the system includes one or more PLMNs 102 coupled to one or more other external data networks 104, particularly wide area networks (WANs) such as the Internet. It should be understood that a PLMN can be a standalone PLMN including a 5GC, or a non-standalone PLMN including both an evolved packet core (EPC) and a 5GC connected to a RAN.

[0055] Each PLMN in PLMN 102 includes a core network (CN) 106, such as EPC, 5GC, or 6GC; and each CN is coupled to one or more RANs 108, which implement one or more radio access technologies (RATs). Examples of these RANs include the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) for 4G LTE, the Next Generation Radio Access Network (NG-RAN) for 5G NR, and the 6G RAN. As used herein, “network equipment” refers to any suitable equipment in the RAN or core network of a telecommunications system. Examples of suitable network equipment will be described in detail below.

[0056] Examples of RATs include 3GPP radio access technologies such as GSM, CDMA2000 1xEV-DO (HRPD), CDMA2000 1x (1xRTT), UTRA, E-UTRA, 5G NR, 5G Advanced, and 6G. Other examples of RATs include IEEE 802 technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.15 (including 802.15.1 (WPAN / Bluetooth), 802.15.4 (Zigbee), and 802.15.6 (WBAN)), Bluetooth, Bluetooth Low Energy (BLE), Ultra Wideband (UWB), etc. Generally, RAT can refer to any 2G, 3G, 4G, 5G, 6G, or higher generation RAT and its different versions, as well as any other RAT that can be arranged to communicate with such a RAT to provide CN 106 access to the MNO.

[0057] Telecommunication system 100 also includes one or more communication devices, which may be referred to differently as User Equipment (UE) 110, terminal equipment, terminal device, mobile station, etc. A UE is typically configured to communicate with network equipment (e.g., access nodes, such as the RAN node of RAN 108) or with other UEs within the telecommunications system. A UE may be a portable computer (e.g., a laptop, notebook computer, tablet computer), a mobile phone (e.g., a mobile phone, smartphone), a wearable computer (e.g., a smartwatch), etc. In other examples, a UE may be an Internet of Things (IoT) device, an Industrial IoT (IIoT) device, a vehicle equipped with Vehicle-to-Everything (V2X) communication technology, etc. In some examples, such as those referenced by 3GPP, a UE may be a Narrowband IoT (NB-IoT) device, an enhanced machine-type communication (eMTC) device, a RedCap device, an environmental IoT device, etc.

[0058] In operation, these UEs 110 can connect to one or more RAN nodes of RAN 108 according to their specific RAT, thereby accessing a specific CN 106 of PLMN 102, or accessing one or more of external data networks 104 (e.g., the Internet) or services provided by the PLMN. External data networks can provide Internet access or third-party services. For example, the International Telecommunication Union (ITU) has classified 5G mobile network services (e.g., services provided by 5G mobile networks) into three categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC) or massive Internet of Things (MIoT).

[0059] In various examples, RAN 108 can be configured to provide one or more macro cells, micro cells, pico cells, femto cells, etc. RAN typically includes one or more RAN nodes that interact with UE 110. In various examples, RAN nodes can be referred to as base stations (BS), access points (AP), base transceiver stations (BTS). Examples of RAN nodes include node B (NB), evolved NB (eNB), macro BS, NB (MNB) or eNB (MeNB), home BS, NB (HNB) or eNB (HeNB), next-generation NB (gNB), enhanced gNB (en-gNB), next-generation eNB (ng-eNB), 6G NB (6gNB), etc. The term “gNB” in 5G NR can correspond to eNB in ​​4G LTE. Additionally, NG-RAN nodes can refer to gNB or ng-eNB. And unless otherwise specified, gNB in ​​5G NR or 6gNB in ​​6G can sometimes be more commonly referred to as (6) gNB or simply gNB.

[0060] RAN 108 may include several types of network control / management entities responsible for controlling the RAN nodes. The network control / management entities and RAN nodes may be separate or integrated into a single device. The network control / management entities may include processing circuitry configured to perform various management functions for controlling the RAN nodes. This processing circuitry may be associated with a memory, computer-readable storage medium, or data storage device that includes a database for maintaining the information required for the various management functions.

[0061] Figure 2 An example of a PLMN 102 communicating with a UE 110 of a telecommunications system 100 and an external data network 104, such as a 4G LTE, 5G NR, or 6G PLMN, is illustrated. As shown, a RAN 108 (e.g., E-UTRAN, NG-RAN, 6G RAN) includes one or more RAN nodes 202 configured to connect one or more UEs to the RAN for access to a CN 106 (e.g., EPC, 5GC, 6GC). In 4G LTE, the UE, E-UTRAN, and EPC constitute the EPS. Similarly, in 5G NR, the UE, NG-RAN, and 5GC constitute the 5GS. And in 6G, the UE, 6G RAN, and 6GC constitute the 6GS.

[0062] In some implementations, the operation of a gNB or other RAN node can be distributed or functionally broken down into components, including one or more Remote Radio Heads (RRHs) or Radio Units (RUs) and Baseband Units (BBUs); and in some implementations, the BBU can be split into a Central Unit (CU) (central node) and a Distributed Unit (DU) (distributed node). A CU can be, for example, a server, host, or node. In some implementations, RRHs / RUs and DUs can be co-located at a network device. It is also possible for the operation of a gNB or RAN node to be distributed among multiple servers, hosts, or nodes.

[0063] It should also be understood that the allocation of work between core network operations and RAN node operations may vary depending on the implementation. For example, 5G or 6G network architectures may be based on so-called CU-DU splitting. One gNB-CU (CU) can control one or more gNB-DU (DU). A gNB-CU can control multiple spatially separated gNB-DUs that at least act as transmit / receive (Tx / Rx) nodes. However, in some example implementations, a gNB-DU may include, for example, the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and the Physical (PHY) layer, while the gNB-CU may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, the Radio Resource Control (RRC) layer, and the Internet Protocol (IP) layer. Other functional splitting is also possible. Those skilled in the art are believed to be familiar with the Open Systems Interconnection (OSI) model and the functions within each layer.

[0064] In some example implementations, the server or CU can generate a virtual network through which the server communicates with radio nodes. Typically, a virtual network can involve the process of combining hardware and software network resources and network functions into a single software-based management entity virtual network. Such virtual networks can provide flexible operational allocation between the server and radio headers / nodes. In fact, any digital signal processing task can be performed in the CU or DU, and the boundaries of responsibility transferred between the CU and DU can be chosen depending on the implementation.

[0065] Figure 3 A more specific description is given of aspects of CN 106 in an example of a PLMN 102 implemented according to some examples. The CN may include multiple network functions (NFs) divided between the control plane (CP) and the user plane (UP). Specifically, for example, the CN may include, for example, NFs for access and mobility management (MM) functions (sometimes referred to as MMF or MM NF) and session management (SM) functions (sometimes referred to as SMF or SM NF). An MM NF may be, for example, a Mobility Management Entity (MME) in EPS, a 5G MM or Access and Mobility Management Function (AMF) 302 in 5GS, or a 6G MM in 6GS. Similarly, an SM NF may be, for example, a Serving Gateway (SGW) Control Plane Function (SGW-C) and / or a Packet Data Network Gateway (PGW) Control Plane Function (PGW-C) in EPS, a 5G SM or Session Management Function (SMF) 304 in 5GS, or a 6G SM in 6GS.

[0066] For example, as also shown in the figure, CN 106 may include NFs for the reception and transmission of traffic (e.g., data), which may be or include SGW User Plane Functions (SGW-U) and / or PGW User Plane Functions (PGW-U) in EPS, or User Plane Functions (UPF) 306 in 5GS. Other examples of suitable NFs for CN 106 include Policy Control Functions (PCF) 308, Charging Functions (CHF) 310, Unified Data Management (UDM) 312, Network Exposure Functions (NEF) 314, and / or Application Functions (AF) 316.

[0067] In Release 15, 3GPP introduced a Service-Based Management Architecture (SBMA), in which Management Services (MnS) are exposed by MnS producers for consumption by MnS consumers. The resource model exposed by the MnS producers can be accessed by MnS consumers using Create, Read, Update, and Delete (CRUD) operations.

[0068] The resource model exposed by the MnS producer is a management representation of network functions (e.g., RAN node 202, AMF 302), management functions, jobs, and activities, all of which can be managed by the MnS producer. Therefore, management objects can represent network functions and specific management tasks. A Management Object Instance (MOI) is a specific instantiation of a management object, and the structure of an MOI is described by its Management Object Class (MOC), also known as an Information Object Class (IOC). Management objects representing management tasks can include, for example, data collection jobs such as "PerfMetricJob," "QMCJob," and "TraceJob."

[0069] Therefore, the number of automated functions and MnS consumers is increasing, especially in the context of artificial intelligence (AI) / machine learning (ML). These MnS consumers may need to collect measurement data from network functions. Subscriber and device tracking (initially introduced as a troubleshooting feature) is now widely used as a data source for detailed (and automated) analysis, debugging, and optimization of network functions or features. Resource models also allow MnS consumers to receive detailed information about individual network functions or UEs 110.

[0070] When information is requested from UE 110, the concept of Minimized Drive Test (MDT) measurements applies, and the collection of MDT data utilizes tracking features and their reporting mechanisms. In 3GPP, the MDT framework is a feature widely used by MNOs that want feedback on coverage areas in specific regions of their network (managed MDT) or feedback on radio conditions experienced by some specific UEs in a given coverage area of ​​PLMN 102 (signaling-based MDT). For example, as... Figure 2 As shown, the MDT framework may include a management system 204 and a trace collection entity (TCE) 206. The management system and TCE may be components of Operations, Administration and Maintenance (OAM).

[0071] There are two types of MDTs: logging MDTs and instantaneous MDTs. Logging MDTs are applicable to the RRCIDLE and RRC INACTIVE states. For logging MDTs, when the UE is in the RRC_CONNECTED state, UE 110 receives the logging MDT configuration from RAN 108 (e.g., RAN node 202). This logging MDT configuration is stored in the UE. During the logging duration of the logging MDT configuration (e.g., a maximum of two hours), when the UE is in the RRCIDLE state, the logging MDT measurement configured for the logging MDT is activated and executed, and the measurement results (e.g., measurement results, measurement samples) are cached in the UE.

[0072] When UE 110 reconnects to the network and transitions to the RRC CONNECTED state, a log of cached measurement availability is signaled to the network, which can then forward this log to TCE 206. In the RRC CONNECTED state, the logged MDT configuration is simply retained, but the measurements are not executed. However, RAN 108 can be configured with on-the-spot MDT configurations. On-the-spot MDT configuration can result in UE 110 being configured with RRC measurements to be activated and executed in the RRC CONNECTED state, but the UE is unaware that the purpose of these RRC measurements is Radio Resource Management (RRM) or MDT.

[0073] Since immediate MDT is applied to the RRC CONNECTED state, the configuration for immediate MDT UE measurements reuses existing RRC measurement procedures and reporting. Specifically, the following measurements are supported for immediate MDT execution: M1: Reference signal received power (RSRP), reference signal received quality (RSRQ), and signal-to-interference plus noise ratio (SINR) performed by UE 110. M2: Power margin measurement performed by the UE. M3: Received interference power measurement performed by the eNB (RAN node 202), which is a cell measurement. M4: Data capacity measurement performed by the eNB for each UE per Quality of Service Class Identifier (QCI) for both downlink (DL) and uplink (UL). M5: IP throughput scheduled by the eNB for DL ​​and UL, per UE per Radio Access Bearer (RAB), and per DL per UE, and per UL per UE. M6: Packet delay measurement performed by the UE individually for DL ​​and UL, per QCI per UE, with reference to UL PDCP delay; and packet delay measured by the eNB in ​​DL per QCI. M7: Packet loss rate measurement performed individually by the eNB for DL ​​and UL, per QCI per UE. M8: RSSI measurement performed by the UE. M9: RTT measurement performed by the UE.

[0074] For example, after performing an M1 measurement to obtain samples of the MDT measurement, the UE 110 can quantize these samples to generate quantized values ​​for the MDT measurement. In this respect, quantization is the process of mapping continuous values ​​to discrete values. The UE can then report the quantized values ​​of the MDT measurement samples (e.g., MDT measurement samples) to the RAN node 202. In 3GPP, this quantization is performed based on Table 1 from 3GPP TS 38.133, in which if the maximum number of reported reference signals (RS) (nrofReportedRS) is configured to 1, the UE reports a 7-bit RSRP value with a 1 dB step size, or quantization fineness. If the maximum number of RS is configured to be greater than 1, or if group-based beam reporting is enabled, the UE uses a 4-bit differential report, which implies a 2 dB step size or quantization fineness. Then, in some examples, the fineness of the reported MDT measurement can refer to the quantization level, according to which the MDT measurement can be quantized. For example, 7 bits means that 128 discrete quantization levels are allowed.

[0075] UE 110 can report MDT measurements at a fixed level of granularity (e.g., quantization level). However, there is currently no mechanism for defining different levels of granularity for various parameters or other measurements via MDT (such as based on MDT job type requirements). Furthermore, training AI / ML models typically requires numerous data samples. Therefore, the problem arises when reporting these numerous data samples, quantized at the high granularity of current specifications, places a significant burden on the data-carrying interface, radio resources, and UE battery consumption. More importantly, depending on the use cases associated with MDT jobs and the network conditions imposed on individual UEs, UEs may have less interest in participating in MDT jobs and may choose not to participate due to battery consumption and / or other considerations.

[0076] In view of the foregoing, the example implementations of this disclosure provide solutions(s) that enable the over-the-top (OTT) server of the OAM or management system 204 to use MDT to collect measurements reported by the UE 110 according to a configurable granularity (e.g., quantization level) among multiple granularities supported by the UE. In some examples, granularity may refer to a quantization level, according to which samples of MDT measurements for one or more data types (e.g., M1, M2) can be quantized. These MDT measurements may include, for example, SINR, RSRQ, etc. In some examples, this same configuration may allow measurement granularity (e.g., SINR) on all or some subcarriers (lower frequency granularity).

[0077] Alternatively or concurrently, some of the solutions described in the examples herein may allow billing based on the granularity of the reported MDT measurements; variations in the fees charged for the granularity of the reported MDT measurements can be used to incentivize the management system to select lower-granularity MDT measurement reports. In some cases, higher-granularity data may be required for shorter time periods, while lower-granularity data can be used for longer traces to analyze the long-term behavior of time series. In these cases, some of the example implementations may enable and provide RAN-side optimizations to avoid long bursts of high-granularity / high-throughput data collection.

[0078] Some example implementations introduce multi-finesity MDT (MR-MDT), where UE 110 supports multiple granularities of finesse MDT measurement, such as MDT for logging and / or immediate MDT. During registration, the UE can send a message via RAN 108 to CN106 indicating that the UE supports MR-MDT (multiple granularities of finesse MDT measurement). For example, the UE can indicate its capability for MR-MDT, which can indicate multiple granularities of MDT measurement for one or more data types (e.g., M1, M2). In some examples, a message can be added to the registration request, indicating the UE's capability for MR-MDT. The UE's capability for MR-MDT can then be configured in UDM 312 in CN.

[0079] The example implementations (multiple) of solutions can be implemented for either management-based MDT or signaling-based MDT, or both. For an MDT operation, the management system 204 can provide information indicating the required granularity among multiple granularities, based on which MDT measurements will be reported for the MDT operation granularity, which can be signaled upon activation of the MDT operation. In various examples, the required granularity can be the minimum granularity for MDT measurements or the precise (strict) granularity for MDT measurements. The information can indicate the required granularity in a variety of different ways, for example, by including a vector containing the location (channel state, location) corresponding to the data type to be collected (e.g., M1, M2). And in some examples, the CHF 310 can receive a charging data request that includes information indicating that the UE 110 supports MR-MDT, which the CHF can use to classify charging information into one or more categories corresponding to one or more granularities.

[0080] The MR-MDT provided by the example implementation offers several advantages. In this regard, the provided MR-MDT can allow for higher radio efficiency for RAN108, especially when higher-granularity data (in the current configuration) is not required, such as in cases where the AI / ML model does not need higher-granularity data and can instead use larger, lower-granularity data. However, in other cases, the AI / ML model may require higher-granularity data, such as for positioning applications. The provided MR-MDT can also reduce the demands on UE 110 battery life due to shorter communication durations, reduce the complexity of data processing on the UE, and reduce memory usage, all of which can vary with data granularity. In some cases, MR-MDT can also be used to implement low-latency applications (e.g., URLLC) by using smaller datasets, making it easier to ensure a certain level of latency during the upload of datasets applicable to URLLC.

[0081] According to some example implementations, UE 110 can send information to CN 106 via RAN 108, indicating that the UE supports multiple levels of granularity for MDT measurements. In some examples, the UE can send a message including information; and in some of these examples, the message can be a registration request carried to the RAN in an Access Network (AN) message. The UE can receive from the RAN information indicating that the UE will perform MDT measurements, as well as information indicating the granularity among multiple levels, according to which the MDT measurements will be reported. The UE can perform MDT measurements and report the MDT measurements to the RAN according to the granularity.

[0082] In an example where the granularity includes a quantization level, UE 110 can acquire samples of MDT measurements and quantize these samples to generate quantized values ​​of the MDT measurements based on the quantization level. The UE can then report the quantized values ​​of the MDT measurements. In some examples, the UE can sample the MDT measurements at a higher rate than required to achieve the desired granularity, and then average the samples to achieve the desired granularity.

[0083] In some other examples, UE 110 can quantize the sample to generate a first quantized value for the MDT measurement based on a quantization level higher than the quantization level. The UE can then requantize the first quantized value to generate a second quantized value for the MDT measurement based on a quantization level that can be reported.

[0084] In some examples, UE 110 can store a first quantized value of the MDT measurement (quantized according to a higher quantization level), which allows the first quantized value to be used later. In this regard, when an MDT measurement is performed for a tracking session, the UE can receive a second message from RAN 108 instructing the UE to perform an MDT measurement for a second tracking session, and this second message may indicate a higher quantization level for the MDT measurement. The UE can then report the stored first quantized value of the MDT measurement to the RAN without having to retrieve and quantize samples of the MDT measurement again.

[0085] According to some example implementations, the RAN side of the MDT operation can be implemented at RAN node 202. In some example implementations of these example implementations, the RAN node can receive configuration for the execution of MDT measurements, which includes information indicating the required granularity for the MDT measurements, such as minimum granularity or exact granularity for the MDT measurements. In some examples involving management-based MDT, the RAN node can receive a request from management system 204 to activate a tracing session, and this request can include configuration for performing MDT measurements for the tracing session. In some other examples involving signaling-based MDT, the RAN node can receive a message from CN 106 (e.g., AMF 302) to start a tracing session, and this message can include configuration for performing MDT measurements for the tracing session.

[0086] RAN node 202 can identify one or more UEs 110 that have the capability to meet the required granularity for MDT measurements, and instruct the UE(s) to: perform MDT measurements and report the MDT measurements according to the required granularity. In some examples, the RAN node can receive context information for multiple UEs from CN 106. The context information for each corresponding UE among the multiple UEs can indicate the capability of that corresponding UE to support multiple granularities (MR-MDT) of granular MDT measurements, and the RAN node can determine the UE(s) with the capability to meet the required granularity based on the context information.

[0087] In some examples, the configuration for performing MDT measurements may include information indicating the required number of UEs 110 that will be used to perform the MDT measurements. The required number may be indicated as a minimum number of UEs to be used to perform the MDT measurements, or as a precise number of UEs to be used to perform the MDT measurements. In some of these examples, RAN node 202 may determine (multiple) UEs(s) with the capability to meet the required granularity for MDT measurements, and also in number, meet the required number of UEs to be used to perform the MDT measurements.

[0088] According to some example implementations specifically relating to signaling-based MDT, the UDM 312 in CN 106 can receive a request to activate a tracking session, and this request may include configuration for performing MDT measurements. This configuration may include information indicating the required granularity (e.g., minimal, precise) for the MDT measurements, and the UDM can determine the UE(s)(s) capable of meeting the required granularity for the MDT measurements. The UDM can then send the configuration for performing the MDT measurements to the AMF 302 (or other MM NF) serving the UE(s), for the AMF to initiate a tracking session based on the configuration for the MDT measurements, such as by sending a message to RAN node 202 to initiate a tracking session.

[0089] In some examples, the request received by UDM 312 to activate a tracking session may include configuration for MDT measurements performed by one or more UEs 110, and the UDM may identify those UEs with the capability to meet the required granularity. In some other examples, the request may include configuration for performing MDT measurements in one or more cells of RAN 108, and the UDM may identify (multiple) UEs served by (multiple) cells and with the capability to meet the required granularity.

[0090] As previously described, in some examples, the configuration for performing MDT measurements may include information indicating the required number of UEs 110 that will be used to perform the MDT measurements. The required number may be indicated as a minimum number of UEs that will be used to perform the MDT measurements, or a precise number of UEs that will be used to perform the MDT measurements. In some of these examples, UDM312 may determine that the number (e.g., quantity) of (multiple) UEs with the capability to meet the required granularity for MDT measurements also meets the required number of UEs that will be used to perform the MDT measurements.

[0091] As described above, CHF 310 can utilize the UE's support for MR-MDT to classify billing information into one or more categories corresponding to one or more granularities. According to some example implementations, CHF can then receive a billing data request for a Protocol Data Unit (PDU) session for UE 110 from SMF 304 (or other SM NF), and this billing data request can include information indicating that the UE supports multiple granularities of MDT measurement. CHF can then initiate a Billing Data Record (CDR) for the UE's PDU session based on this billing data request.

[0092] CHF 310 can receive charging information associated with a PDU session from SMF 304. The charging information can be categorized into one or more categories corresponding to one or more granularities of MDT measurements reported by UE 110. CHF can update CDR based on the charging information. In this regard, CDR includes one or more counters updated by categories, and each of the one or more counters can be associated with a corresponding charging policy. Then, in some examples, CHF can send a charging report to SMF, which includes information indicating one or more values ​​of one or more counters.

[0093] To further illustrate various example implementations, Figure 4A and 4B The diagram illustrates the level of granularity used in a management-based MDT process that includes granularity requirements for reporting MDT measurements. For example... Figure 4A As shown, UE 110 can send a registration request message to AMF 302 of CN 106 at steps 401 and 402, and the registration request can include information indicating that the UE supports multiple granularities (MultiRes capabilities) of granular MDT measurements. The registration request message can be carried from the UE to the RAN in an AN message and from the RAN to the AMF in an N2 message. The AMF can register with UDM 312 using Nudm_UECM_Registration at steps 403 and 404 for the access to be registered, and the AMF can retrieve the access and mobility subscription data for the UE from the UDM using Nudm_UECM_Ge at steps 405 and 406. During AMF registration, the AMF can indicate the UE's MultiRes capabilities to the UDM, which can be stored in the UDM and included in the access and mobility subscription data for the UE.

[0094] The management system 204 may send a request to the RAN node 202 at step 407 to activate the tracking session, and this request may include a configuration for performing MDT measurements for the tracking session. The configuration may include multiple MDT parameters. The MDT parameters (and thus the configuration) may include information indicating the data types to be performed for the MDT measurements, and the required granularity (minimum or exact granularity) for each data type. In some examples, the configuration may also include information indicating the required number of UEs 110 to be used to perform the MDT measurements. In some of these examples, the required number of UEs may be indicated as a minimum number of UEs to be used to perform the MDT measurements (e.g., the number of UE thresholds (Thr)) or an exact number of UEs to be used to perform the MDT measurements. Alternatively, in some examples, the required number of UEs may be indicated as a minimum number of data points for the MDT measurements. The RAN node may start the tracking session at step 408 and store the configuration including the MDT parameters.

[0095] RAN node 202 may receive an initial context establishment request or handover request message at step 409, which may include information indicating that managed MDT is permitted for the UE and that the UE supports multiple granularities of granular MDT measurements. This information may be received from AMF 302, such as access and mobility subscription data for the UE, which the AMF receives from UDM 312. Figure 4B As shown, the RAN node can store information in the context information for the UE at step 410, which indicates multiple levels of granularity for the UE based on the managed MDT and the UE's support for granular MDT measurements.

[0096] RAN node 202 may determine at step 411 whether the configuration for performing MDT measurements for the tracking session can be satisfied. For example, the RAN node may determine whether there are (multiple) UEs 110 with the capability to satisfy the required granularity for MDT measurements, and (if provided) a sufficient number of UEs 110 that will be used to perform the MDT measurements. If the configuration cannot be satisfied, the RAN node may report to management system 204 at step 412 that there are not enough UEs (e.g., “MR-MDT UE Insufficiency”).

[0097] If the configuration can be satisfied, RAN node 202 can, at step 413, select, based on context information for the multiple UEs 110, those UE(s) that have the capability to meet the required granularity for MDT measurements and also meet the required number of UEs to be used to perform MDT measurements. Then, at step 414, the RAN node can activate the MDT function for the selected UE(s), such as via RRC configuration, for logged MDT or on-the-fly MDT. In this regard, the RAN node can instruct the UE(s)(s) to perform MDT measurements and report the MDT measurements according to the required granularity.

[0098] Figure 5A and Figure 5B The diagram illustrates graphical granularity of processes for signaling-based MDT implementations, including granularity requirements for reported MDT measurements, based on various examples. For example... Figure 5A and Figure 5B As shown, the process may include steps 401 to 406 as described above. The management system 204 may send a request to the UDM 312 at step 507 to activate the tracking session, and this request may include configuration for performing MDT measurements for the tracking session.

[0099] The configuration for performing MDT measurements for a tracking session may include multiple tracking control and configuration parameters. The tracking control and configuration parameters (and thus the configuration) may include information indicating the required granularity (minimum or exact granularity) for each data type of the data to be performed in the MDT measurements. In some examples, the configuration may also include information indicating the required number of UEs 110 to be used to perform the MDT measurements. In some examples, the required number of UEs may be indicated as a minimum number of UEs to be used to perform the MDT measurements (e.g., the number of UE thresholds (Thr)) or an exact number of UEs to be used to perform the MDT measurements. Alternatively, in some examples, the required number of UEs may be indicated as a minimum number of data points for the MDT measurements. The UDM 312 may begin the tracking session at step 508 and store the configuration including the tracking control and configuration parameters.

[0100] UDM 312 can, at step 509, search for access and mobility subscription data for multiple UEs 110 (subscribers) based on the configuration used to perform MDT measurements. In this regard, the UDM can search the access and mobility subscription data to locate a sufficient number of UEs that have the capability to meet the granularity required for MDT measurements and, if provided by the configuration, also meet the required number of UEs to be used to perform the MDT measurements. Figure 5BAs shown, the UDM can then send the configuration (including tracking control and configuration parameters) for performing MDT measurements to the AMF 302 (or other MM NFs) serving the UEs at step 510, and can also instruct the UEs (e.g., via subscriber ID).

[0101] Each AMF 302 may store a configuration including tracking control and configuration parameters at step 511, and send a message to RAN node 202 to start a tracking session according to the configuration for MDT measurements. Similar to the above description, the RAN node may determine at step 512 whether the configuration for performing MDT measurements for the tracking session can be satisfied. For example, the RAN node may determine whether there is a sufficient number of UE(s) that have the capability to satisfy the required granularity for MDT measurements, are served by the RAN node, and (if provided by the configuration) also meet the required number of UEs to be used to perform the MDT measurements. If the configuration cannot be satisfied, the RAN node may report to management system 204 at step 513 that there is not a sufficient number of UE(s) (e.g., “MR-MDT UE Insufficiency”).

[0102] If the configuration can be satisfied, RAN node 202 can store information in the UE's context information at step 514, indicating multiple levels of granularity for the UE based on managed MDT and the UE's support for granular MDT measurements. At step 515, the RAN node can select, based on the context information for multiple UEs 110, those UE(s) that have the capability to meet the required granularity for MDT measurements and also meet the required number of UEs to be used to perform MDT measurements. The RAN node can also select UE(s) based on RRM considerations, which can influence how MDT is configured for UE(s), such as by delaying MDT in instances where the RAN node's cell is fully loaded. Then, at step 516, the RAN node can activate the MDT functionality for the selected UE(s), such as via RRC configuration, for logged MDT or on-demand MDT. In this regard, the RAN node can instruct the UE(s) to perform MDT measurements and report the MDT measurements according to the required granularity.

[0103] Figure 6This is a diagram illustrating a process for performing MDT measurements by UE 110, implemented according to some examples. As shown, the process may include step 401 as described above, and step 414 (for managed MDT) or step 515 (for signaling-based MDT). When instructed at step 414 / 515, the UE may perform MDT measurements and report the MDT measurements according to the configured required granularity. When the required granularity is indicated by a quantization level, the UE may acquire samples of the MDT measurements and quantize these samples to generate quantized values ​​of the MDT measurements according to the quantization level.

[0104] As shown at step 603, in some examples, UE 110 may quantize the sample to generate a first quantized value for the MDT measurement based on a quantization level higher than the desired quantization level. The UE may then requantize the first quantized value at step 604 to generate a second quantized value for the MDT measurement based on a quantization level that can be reported.

[0105] UE 110 may store a first quantized value (quantized according to a higher quantization level) of the MDT measurement at step 604. If the UE receives a second message from RAN 108 instructing the UE to perform MDT measurements for a second tracking session requiring a higher quantization level for the MDT measurements, the UE may report the stored first quantized value without needing to retrieve and quantize samples of the MDT measurements again. The UE may report a second quantized value for the tracking session at step 605, and in the case of a second tracking session, report the first quantized value.

[0106] Figure 7 This diagram illustrates the process for establishing a PDU session, implemented using several examples. During PDU session establishment, billing information associated with the PDU session is categorized into classes corresponding to the granularity of the reported MDT measurements. CHF 310 is responsible for managing and processing the billing information, enabling operators to charge users for their services. In 3GPP, billing can take various forms, such as online or offline billing, session-based or event-based billing, etc. In the illustrated diagram, the process involves session-based billing of the UE 110 for multiple granularities of the MDT measurements.

[0107] Session-based billing can be used for continuous services, such as voice or data sessions. The CHF 310 can interact with various CN network functions, such as SMF 304 (or other SM NFs) and PCF 308, to collect and process billing information. In this regard, the CHF can interact with the SMF to collect session-related information for PDU sessions, such as data usage, quality of service (QoS), etc., and the CHF can interact with the PCF primarily to collect billing rules and policy decisions.

[0108] As indicated above, during registration, UE 110 can indicate to AMF 302 that the UE supports multiple levels of granularity (MultiRes capability) for granular MDT measurements. AMF can indicate the UE's MultiRes capability to UDM 312, and the indication of the UE's MultiRes capability can be stored in the UDM and included in the access and mobility subscription data used for the UE. The UE's MultiRes capability can also be indicated to the AMF and SMF and stored in the context information used for the UE.

[0109] like Figure 7 As shown, the process for establishing a PDU session may include: at step 701, UE 110 sends a PDU session establishment request to AMF 302 via RAN node 202. AMF may select SMF at step 702 to handle PDU session establishment and user plane aspects (e.g., UPF selection). AMF may send a request to SMF 304 at step 703 to create an SM context for the PDU session. SMF may retrieve subscription data for the UE from UDM at steps 704 and 705, which may include an indication of the UE's MultiRes capability. The MultiRes capability may instruct the SMF to perform UE-specific charging requests based on the granularity of MDT measurements to be reported by the UE. SMF may send a response to AMF at step 706.

[0110] At step 707, PDU session authentication / authorization can be performed for the PDU session. At step 708, SMF 304 can select PCF 308, responsible for authorizing QoS rules and charging policies for the PDU session, and perform SM policy creation / modification to establish policy rules for QoS, charging, and traffic management. Then, at step 709, SMF can select UPF 306 for routing user plane traffic for the PDU session.

[0111] SMF 304 may send a charging data request to CHF 310 at step 710 to set up and manage charging for the PDU session. As indicated, the indication of the UE's MultiRes capability may instruct the SMF to perform a UE-specific charging request based on the granularity of the MDT measurements to be reported by UE 110. Therefore, the charging data request may include information indicating that the UE supports multiple granularities of MDT measurements. When the UE first registers with PLMN 102, CHF may, at step 711, initiate a Charging Data Record (CDR) for the UE's PDU session based on the charging data request. If the UE has previously (e.g., earlier) registered with the PLMN, CHF may already have a CDR for the UE. CHF may send a charging data response to SMF at step 712.

[0112] During a PDU session, steps 710 to 712 can be repeated periodically. The SMF 304 can collect charging information associated with the PDU session, and the SMF can send a charging data request, including the charging information, to the CHF at step 710. The charging information can be categorized into one or more categories corresponding to one or more granularities of the MDT measurements reported by the UE 110. The CHF can update the CDR based on the charging information at step 711. The CDR can include one or more counters updated by categories from the one or more categories, and each of these counters can be associated with a corresponding charging policy. The CHF can then send a charging data response to the SMF at step 712 to indicate that the CDR has been updated. In at least one charging data response, the charging data response can include a charging report that includes information indicating one or more values ​​of one or more counters.

[0113] Figures 8A to 8D This is a flowchart illustrating the various steps of method 800 performed by a user equipment (UE) according to various examples. The method includes: transmitting information to the core network via the radio access network (RAN), the information instructing the UE to support multiple levels of granularity in minimizing drive test (MDT) measurements, such as... Figure 8A As shown in box 802. The method includes: receiving from the RAN information indicating that the UE will perform an MDT measurement, and information indicating a granularity among a plurality of granularities, according to which the MDT measurement will be reported, as shown in box 804. The method includes: performing the MDT measurement, as shown in box 806. And the method includes: reporting the MDT measurement to the RAN according to the granularity, as shown in box 808.

[0114] In some examples, the transmission at box 802 includes: transmitting a message that includes information indicating that the UE supports multiple levels of granularity in MDT measurements.

[0115] In some examples, the message includes a registration request, which is carried to the RAN in the access network message.

[0116] In some examples, fineness includes quantization level, and performing MDT measurements at box 806 includes: obtaining samples of the MDT measurements, such as... Figure 8B As shown in box 810. In some of these examples, performing an MDT measurement further includes quantizing the sample to generate a quantized value for the MDT measurement based on the quantization level, as shown in box 812. Additionally, in some of these examples, reporting the MDT measurement to the RAN at box 808 includes reporting the quantized value of the MDT measurement, as shown in box 814.

[0117] In some examples, fineness includes quantization level, and performing MDT measurements at box 806 includes: obtaining samples of the MDT measurements, such as... Figure 8C As shown in box 816. In some of these examples, performing an MDT measurement further includes: quantizing the sample to generate a first quantized value for the MDT measurement based on a quantization level higher than the quantization level, as shown in box 818. Performing an MDT measurement also includes a method that includes: requantizing the first quantized value to generate a second quantized value for the MDT measurement based on the quantization level, as shown in box 820. Additionally, in some of these examples, reporting the MDT measurement to the RAN at box 808 includes: reporting the second quantized value for the MDT measurement, as shown in box 822.

[0118] In some examples, the method 800 also includes storing the first quantization value of the MDT measurement.

[0119] In some examples, the UE will perform an MDT measurement for a tracking session, and in some of these examples, the method 800 further includes: receiving from the RAN a second message indicating that the UE will perform an MDT measurement for a second tracking session, such as... Figure 8D As shown in box 824. Additionally, in some of these examples, the second message indicates a higher quantization level. And the method includes: reporting the first quantization value of the MDT measurement to the RAN, as shown in box 826.

[0120] Figure 9This is a flowchart illustrating the various steps of method 900 implemented according to various examples. The method includes: receiving a configuration for performing minimized drive test (MDT) measurements, the configuration including information indicating the required granularity for the MDT measurements, as shown in box 902. The method includes: determining one or more user equipments (UEs) that have the capability to meet the required granularity for the MDT measurements, as shown in box 904. And the method includes: instructing the one or more UEs to: perform the MDT measurements and report the MDT measurements according to the required granularity, as shown in box 906.

[0121] In some examples, receiving the configuration for performing MDT measurements at box 902 includes receiving a request from the management system to activate the tracing session. In some of these examples, the request to activate the tracing session includes configuration for performing MDT measurements for the tracing session.

[0122] In some examples, the method 900 further includes receiving context information from the core network for multiple UEs. In some of these examples, for each corresponding UE among the multiple UEs, the context information indicates the capability of the corresponding UE to support multiple levels of granularity for MDT measurement. Additionally, in some of these examples, one or more UEs with the capability to meet the required granularity are determined based on the context information.

[0123] In some examples, receiving the configuration for performing MDT measurements at box 902 includes receiving a message from the core network to start a tracing session. In some of these examples, the message to start a tracing session includes configuration for performing MDT measurements for the tracing session.

[0124] In some examples, the required precision is either the minimum precision required for MDT measurements or the exact precision required for MDT measurements.

[0125] In some examples, the configuration for performing MDT measurements also includes information indicating the required number of UEs to be used to perform the MDT measurements. In some of these examples, determining one or more UEs with the capability to meet the required granularity for MDT measurements at box 904 includes determining the required number of UEs to be used to perform the MDT measurements.

[0126] In some examples, the required number of UEs is either the minimum number of UEs that will be used to perform MDT measurements or the exact number of UEs that will be used to perform MDT measurements.

[0127] Figure 10This is a flowchart illustrating the various steps of method 1000 implemented according to various examples. The method includes: receiving a request to activate a tracking session, the request including a configuration for performing minimized drive test (MDT) measurements, the configuration including information indicating the required granularity for the MDT measurements, as shown in box 1002. The method includes: determining one or more user equipments (UEs) capable of meeting the required granularity for the MDT measurements, as shown in box 1004. And the method includes: sending the configuration for performing the MDT measurements to a mobility management network function serving the one or more UEs, so that the mobility management network function can initiate a tracking session based on the configuration for the MDT measurements, as shown in box 1006.

[0128] In some examples, the receiving request at block 1002 includes receiving a request including a configuration for MDT measurements performed by one or more UEs. In some of these examples, determining one or more UEs includes, at block 1004, determining one or more UEs that have the capability to meet the required granularity for MDT measurements.

[0129] In some examples, the receive request at box 1002 includes receiving a request including a configuration for performing MDT measurements in one or more cells of the radio access network. In some of these examples, determining one or more UEs at box 1004 includes determining one or more UEs served by one or more cells that have the capability to meet the required granularity for MDT measurements.

[0130] In some examples, the required precision is either the minimum precision required for MDT measurements or the exact precision required for MDT measurements.

[0131] In some examples, the configuration for MDT measurement also includes information indicating the required number of UEs to be used to perform the MDT measurement. In some of these examples, determining one or more UEs with the capability to meet the required granularity for MDT measurement at box 1004 includes determining the required number of UEs to be used to perform the MDT measurement.

[0132] In some examples, the required number of UEs is either the minimum number of UEs that will be used to perform MDT measurements or the exact number of UEs that will be used to perform MDT measurements.

[0133] Figure 11This is a flowchart illustrating the various steps of method 1100 implemented according to various examples. The method includes: receiving a charging data request for a Protocol Data Unit (PDU) session for a User Equipment (UE) from a Session Management Network Function (SM NF), as shown in box 1102. The charging data request includes information instructing the UE to support multiple granularities of Minimized Drive Test (MDT) measurements. The method includes: initiating a Charging Data Record (CDR) for the PDU session for the UE based on the charging data request, as shown in box 1104. The method includes receiving charging information associated with the PDU session from the SM NF, as shown in box 1106. The charging information is categorized into one or more categories corresponding to one or more granularities of MDT measurements reported by the UE. The method further includes: updating the CDR based on the charging information, as shown in box 1108. The CDR includes one or more counters updated by categories from the one or more categories, and in some of these examples, each of the one or more counters is associated with a corresponding charging policy.

[0134] In some examples, method 1100 further includes sending a billing report to the SM NF, the billing report including information indicating one or more values ​​of one or more counters.

[0135] According to exemplary embodiments of this disclosure, telecommunications system 100 or PLMN 102 and its components (such as UE 110, CN 106, RAN 108, RAN node 202, management system 204, TCE 206, AMF 302, SMF 304, UPF 306, PCF 308, CHF 310, UDM 312, NEF 314 and / or AF 316) can be implemented by various parts. Parts used to implement the system and its components can include hardware, firmware, software, or combinations thereof. In some examples, one or more devices can be configured to implement the system and its components shown and described herein, or otherwise. In examples involving more than one device, the respective devices can be interconnected or otherwise communicate in a variety of different ways, such as directly or indirectly via wired or wireless networks.

[0136] According to some example embodiments, relative to Figures 8A to 8D At least some of the methods 800 described herein can be performed by means including components that function to perform corresponding steps of the method. Similarly, relative to Figure 9 At least some of the described method 900 can be performed by means including components that function to perform corresponding steps of the method. Similarly, relative to... Figure 10 At least some of the described method 1000 can be performed by means including components that function to perform corresponding steps of the method, and relative to Figure 11 At least some of the described methods 1100 can be performed by means including components that perform the corresponding steps of the method. Examples of suitable means may include user equipment, user devices, user terminals, etc. Other examples of suitable means may include RAN nodes (e.g., ng-eNB, gNB, gNB-DU, gNB-CU) or any suitable means such as a server, host, or node. Further examples of suitable means may include: a standalone computer (such as a server, host, or node) including a UDM and / or CHF, a distributed computing system including a UDM and / or CHF, or a cloud computing system including a UDM and / or CHF. The UDM and / or CHF may be implemented as virtual machines or containers by the distributed computing system or cloud computing system.

[0137] Figure 12 The illustration shows an apparatus 1200 implemented according to some examples of the present disclosure, wherein components for performing various operations include hardware, which is independent or directed by one or more computer programs derived from a computer-readable storage medium or other memory (such as computer memory). The apparatus may include one or more of each of a plurality of components, such as, for example, a processing circuitry system 1202 connected to a computer-readable storage medium or other memory 1204.

[0138] The processing circuitry system 1202 may consist independently of one or more processors or in combination with one or more computer-readable storage media. The processing circuitry system is typically any computer hardware capable of processing information, such as, for example, data, computer programs, computer code, and / or other suitable electronic information. The processing circuitry system comprises a set of electronic circuits, some of which may be packaged as integrated circuits or multiple interconnected integrated circuits (integrated circuits are sometimes more commonly referred to as “chips”). The processing circuitry system may be configured to execute computer programs, which may be stored on the processing circuitry system board or otherwise stored in memory 1204 (of the same device or another device).

[0139] Depending on the specific implementation, the processing circuitry system 1202 may include multiple processors, multi-core processors, or some other type of processor, such as a central processing unit, graphics processing unit, tensor processing unit, or accelerator. Furthermore, the processing circuitry system may be implemented using multiple heterogeneous processor systems, where the main processor resides on a single chip along with one or more auxiliary processors. As another illustrative example, the processing circuitry system may be a symmetric multiprocessor system containing multiple processors of the same type. In yet another example, the processing circuitry system may be embodied as or otherwise include one or more application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc. Therefore, while the processing circuitry system is capable of executing a computer program to perform one or more functions, the various examples of processing circuitry systems are also capable of performing one or more functions without the assistance of a computer program. In any case, the processing circuitry system can be appropriately programmed to perform functions or operations implemented according to the examples of this disclosure.

[0140] Memory 1204 is typically any computer hardware capable of temporarily or permanently storing information such as, for example, data, computer programs, instructions 1206 (e.g., computer-readable program code), and / or other suitable information. Memory may include volatile and / or non-volatile memory and may be fixed or removable. Examples of suitable memory include recording media, random access memory (RAM), read-only memory (ROM), hard disk drives, flash memory, USB flash drives, removable computer disks, optical disks, or combinations thereof.

[0141] Memory 1204 is a non-transitory device capable of storing information. An example of a suitable memory is a computer-readable storage medium, which differs from a computer-readable transport medium capable of carrying information from one location to another. Examples of suitable computer-readable transport media include electronic carrier signals, telecommunication signals, or combinations thereof. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not signaling), not a limitation on the persistence of data storage (e.g., RAM and ROM). Computer-readable media as described herein generally refers to either computer-readable storage media or computer-readable transport media. A computer-readable medium is any entity or device in which information, such as one or more computer programs or portions thereof, can be stored and carried.

[0142] In addition to memory 1204 (e.g., a computer-readable storage medium), processing circuitry 1202 may also be connected to one or more interfaces for displaying, sending, and / or receiving information. Interfaces may include communication interface 1208 and / or one or more user interfaces. Communication interfaces may be configured to send and / or receive information, such as to and / or from (multiple) other devices, (multiple) networks, etc. Communication interfaces may be configured to send and / or receive information via physical (wired) and / or wireless communication links. Examples of suitable communication interfaces include network interface controllers (NICs), wireless NICs (WNICs), etc.

[0143] The user interface may include a display 1210 and / or one or more user input interfaces 1212. The display may be configured to present or otherwise display information to a user; suitable examples of such a display include liquid crystal displays (LCDs), light-emitting diode (LED) displays, organic LED (OLED) displays, active-matrix OLEDs (AMOLEDs), and the like. The user input interface may be wireless or wired and may be configured to receive information from a user into the device, such as for processing, storage, and / or display. Suitable examples of user input interfaces include microphones, image or video capture devices, keyboards or keypads, joysticks, touch-sensitive surfaces (separate from or integrated into the touchscreen), biometric sensors, and the like. The user interface may also include one or more interfaces for communicating with peripheral devices, such as printers, scanners, etc.

[0144] The execution of instructions 1206 by processing circuitry system 1202, or the storage of instructions in memory 1204, supports a combination of operations for implementing the exemplary implementations of this disclosure. In this way, apparatus 1200 may include at least one processing circuitry system and at least one memory coupled to the at least one processing circuitry system, wherein the at least one processing circuitry system is configured to execute instructions stored in the at least one memory. It should also be understood that one or more functions and combinations of functions may be implemented by a dedicated hardware-based computer system and / or processing circuitry system performing a specific function, or by a combination of dedicated hardware and program code instructions.

[0145] Some example implementations of this disclosure can also be executed as a computer process defined by one or more computer programs or portions thereof. Example implementations of this disclosure can be executed by executing at least a portion of a computer program including instructions. The computer program can be in the form of source code, object code, or some intermediate form. The computer program can be stored on a computer-readable medium that can be read by a computer, processing circuitry system, or other suitable means. As indicated above, for example, the computer program can be stored in memory, such as a computer-readable storage medium. Additionally or alternatively, for example, the computer program can be stored on a computer-readable transmission medium. The coding of software used to perform example implementations of this disclosure is entirely within the knowledge of those skilled in the art.

[0146] It should be understood that any suitable instructions can be loaded from memory or a computer-readable medium (e.g., a computer-readable storage medium, a computer-readable transmission medium) onto a computer, processing circuitry, or other programmable means to produce a particular machine, such that particular machine becomes a component for implementing the functions specified herein. Instructions can also be stored in a computer-readable medium that can instruct a computer, processing circuitry, or other programmable means to operate in a particular manner to produce a particular machine or a particular article of manufacture. In some examples, instructions stored in a computer-readable medium can produce an article of manufacture, wherein the article of manufacture becomes a component for implementing the functions described herein. Instructions can be retrieved from a computer-readable medium and loaded onto a computer, processing circuitry, or other programmable means to configure the computer, processing circuitry, or other programmable means to perform operations that will be performed on or by the computer, processing circuitry, or other programmable means.

[0147] The retrieval, loading, and execution of instructions, including program code instructions, can be performed sequentially, such that one instruction is retrieved, loaded, and executed at a time. In some example implementations, retrieval, loading, and / or execution can be performed in parallel, such that multiple instructions are retrieved, loaded, and / or executed together. The execution of program code instructions can produce computer-implemented processes, such that the instructions, executed by a computer, processing circuitry system, or other programmable device, provide operations for implementing the functions described herein.

[0148] Benefiting from the teachings presented in the foregoing description and associated drawings, those skilled in the art will conceive of various modifications and other implementations of the disclosure set forth herein. Therefore, it should be understood that the disclosure is not limited to the specific implementations disclosed, and that modifications and other implementations are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and associated drawings describe exemplary implementations in the context of certain example combinations of elements and / or functions, it should be understood that different combinations of elements and / or functions may be provided by alternative implementations without departing from the scope of the appended claims. In this regard, for example, combinations of elements and / or functions different from those expressly described above may also be considered, as may be set forth in some of the appended claims. Although specific terminology is used herein, it is used only in a general and descriptive sense and not for limiting purposes.

Claims

1. A method performed by a user equipment (UE), the method comprising: The UE sends information to the core network via the radio access network (RAN), indicating that the UE supports multiple levels of granularity in minimizing drive test MDT measurements. The RAN receives information instructing the UE to perform the MDT measurement, as well as information instructing the granularity among the plurality of granularities, the MDT measurement being reported according to the granularity; Perform the MDT measurement; as well as The MDT measurements are reported to the RAN with varying degrees of precision.

2. The method of claim 1, wherein the transmission includes sending a message, the message including information indicating that the UE supports the plurality of granularities of the MDT measurement.

3. The method of claim 2, wherein the message includes a registration request, and the registration request is carried to the RAN in an access network message.

4. The method according to any one of claims 1 to 3, The level of precision mentioned above includes the quantization level. Performing the MDT measurement includes: Obtain the sample measured by the MDT; as well as The sample is quantized to generate a quantized value for the MDT measurement based on the quantization level. The reporting of the MDT measurement to the RAN includes: Report the quantized value of the MDT measurement; or The level of precision mentioned above includes the quantization level. Performing the MDT measurement includes: Obtain the sample measured by the MDT; The sample is quantized to generate a first quantized value for the MDT measurement based on a quantization level higher than the stated quantization level; and The first quantized value is requantized to generate a second quantized value for the MDT measurement based on the quantization level. The reporting of the MDT measurement to the RAN includes: Report the second quantization value of the MDT measurement.

5. The method according to claim 4, wherein the method further comprises: Store the first quantization value measured by the MDT.

6. The method of claim 5, wherein the UE performs the MDT measurement for a tracking session, and wherein the method further comprises: Receive a second message from the RAN, the second message instructing the UE to perform the MDT measurement for a second tracking session, wherein the second message indicates the higher quantization level; and The first quantization value of the MDT measurement is reported to the RAN.

7. A method for communication, the method comprising: Receive a configuration for performing a minimized road test MDT measurement, the configuration including information indicating the required granularity for the MDT measurement; Identify one or more user equipment (UEs) that have the capability to meet the required granularity for the MDT measurements; as well as The instruction to one or more UEs is to perform the MDT measurement and report the MDT measurement according to the required granularity.

8. A method for communication, the method comprising: Receive a request to activate a tracking session, the request including a configuration for performing minimized road test MDT measurements, the configuration including information indicating the required granularity for the MDT measurements; Identify one or more user equipment (UEs) that have the capability to meet the required granularity for the MDT measurements; as well as The configuration for performing the MDT measurement is sent to the mobility management network function serving the one or more UEs, so that the mobility management network function can start the tracking session according to the configuration for the MDT measurement.

9. A method for communication, the method comprising: The Session Management Network Function (SM NF) receives a charging data request for a Protocol Data Unit (PDU) session for a User Equipment (UE), wherein the charging data request includes information indicating that the UE supports multiple levels of granularity for minimizing drive test MDT measurements; Based on the charging data request, start the charging data recording (CDR) for the PDU session of the UE; Receive billing information associated with the PDU session from the SM NF, wherein the billing information is classified into one or more categories corresponding to one or more of the plurality of granularities of the MDT measurement reported by the UE; as well as The CDR is updated based on the billing information, wherein the CDR includes one or more counters updated by one or more categories, and wherein each of the one or more counters is associated with a corresponding billing policy.

10. An apparatus for communication, the apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform the method according to any one of claims 1 to 9.

Images