Methods, apparatuses and computer programs

Abstract

There is provided a device, method and computer program for causing an apparatus to perform: obtaining first signaling from a network node, the first signaling comprising information indicating that latency information is to be determined in relation to at least one radio resource control procedure when the apparatus is in a reduced energy mode; and determining the latency information based on the first signaling.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure relate to methods, apparatus, systems, and computer programs, and specifically, but not exclusively, to obtaining delay information regarding at least one radio resource control process. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] Such communication networks operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of these standards are the so-called 5G (fifth generation) and 6G (sixth generation) standards provided by 3GPP. Summary of the Invention

[0004] Some exemplary embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of embodiments of this disclosure, nor are they intended to limit its scope. Other features, aspects, and elements will be apparent to those skilled in the art in light of this disclosure.

[0005] According to a first aspect, an apparatus is provided, comprising: at least one processor; and at least one memory including code that, when executed by the at least one processor, causes the apparatus to perform: obtaining first signaling from a network node, the first signaling including information indicating that delay information will be determined with respect to at least one radio resource control procedure when the apparatus is in a reduced power mode; and determining the delay information based on the first signaling.

[0006] According to a second aspect, an apparatus is provided, comprising components for: obtaining first signaling from a network node, the first signaling including information indicating that first delay information will be determined with respect to at least one radio resource control process when the apparatus is in a reduced power mode; and determining the delay information based on the first signaling.

[0007] According to a third aspect, a method for an apparatus is provided, the method comprising: obtaining first signaling from a network node, the first signaling including information indicating that delay information will be determined with respect to at least one radio resource control procedure when the apparatus is in a reduced power mode; and determining the delay information based on the first signaling.

[0008] According to a fourth aspect, an apparatus is provided, comprising: an acquisition circuit system for acquiring first signaling from a network node, the first signaling including information indicating that delay information will be determined with respect to at least one radio resource control procedure when the apparatus is in a reduced power mode; and a determination circuit system for determining the delay information based on the first signaling.

[0009] The following can be applied to any of the first to fourth aspects mentioned above (e.g., including one or more of all aspects).

[0010] The apparatus may also be made to perform: providing a second signaling to a network node, the second signaling including information indicating that the first delay information is available regarding at least one radio resource control procedure; obtaining a third signaling from the network node including a request for the first delay information; and providing the first delay information to the network node.

[0011] The device can be made to perform: obtain a fourth signaling from a network node, the fourth signaling including information indicating that second delay information will be determined with respect to at least one radio resource control procedure when the device is in connected mode; and determine the second delay information based on the fourth signaling.

[0012] The apparatus can be caused to perform: providing a fifth signaling to a network node, the fifth signaling including information indicating at least one of a first delay information and a second delay information regarding the availability of at least one radio resource control procedure; obtaining a sixth signaling from the network node including a request for the first delay information and the second delay information; and providing the first delay information and the second delay information to the network node.

[0013] The apparatus can be made to perform: providing a seventh signaling to a network node prior to obtaining a first signaling, the seventh signaling including information instructing the apparatus for determining delay information regarding one or more radio resource control procedures, wherein the first signaling is based on the seventh signaling.

[0014] When the device is in connected mode, the first signaling can be obtained, and when the device switches from de-energized mode to connected mode, the delay information can be subsequently determined.

[0015] According to a fifth aspect, an apparatus is provided, comprising: at least one processor; and at least one memory, the at least one memory including code that, when executed by the at least one processor, causes the apparatus to perform: providing a first signaling to a user equipment, the first signaling including information indicating that first delay information will be determined regarding at least one radio resource control procedure when the user equipment is in a reduced power mode.

[0016] According to a sixth aspect, an apparatus is provided, comprising components for: providing a first signaling to a user equipment, the first signaling including information indicating that first delay information will be determined regarding at least one radio resource control procedure when the user equipment is in a reduced power mode.

[0017] According to a seventh aspect, a method for an apparatus is provided, the method comprising: providing a first signaling to a user equipment, the first signaling including information indicating that first delay information will be determined regarding at least one radio resource control procedure when the user equipment is in a reduced power mode.

[0018] According to an eighth aspect, an apparatus is provided, comprising: a circuit system for providing a first signaling to a user equipment, the first signaling including information indicating that first delay information will be determined regarding at least one radio resource control procedure when the user equipment is in a reduced power mode.

[0019] The following can be applied to any of the aspects from the fifth to the eighth aspects above (e.g., including one or more of all aspects).

[0020] The apparatus can be made to perform: obtaining a second signaling from a user equipment, the second signaling including information indicating that first delay information is available regarding at least one radio resource control procedure; providing a third signaling to the user equipment, the third signaling including a request for the first delay information; and obtaining the first delay information from the user equipment.

[0021] The device can be made to perform: providing a fourth signaling to the user equipment, the fourth signaling including information indicating that when the device is in connected mode, second delay information will be determined with respect to at least one radio resource control procedure.

[0022] The apparatus can be caused to perform: obtaining a fifth signaling from a user equipment, the fifth signaling including information indicating at least one of a first delay information and a second delay information regarding the availability of at least one radio resource control procedure; providing a sixth signaling to the user equipment, the sixth signaling including a request for the first delay information and the second delay information; and obtaining the first delay information and the second delay information from the user equipment.

[0023] The apparatus may be made to perform: prior to providing the first signaling, obtaining a seventh signaling from the user equipment, the seventh signaling including information instructing the user equipment for determining delay information regarding one or more radio resource control procedures, wherein the first signaling is based on the seventh signaling.

[0024] The apparatus can be made to perform: obtaining an eighth signaling from a core network node for minimizing drive tests, the eighth signaling including information requesting delay information about one or more radio resource control procedures that will be performed at the user equipment when the user equipment is in connected mode; and providing a ninth signaling to the core network node based on the eighth signaling.

[0025] The apparatus can be made to: determine, based on obtaining the eighth signaling, the user equipment's capability to determine the first delay information; and provide the first signaling based on the determined user equipment's capability.

[0026] When the device is in connection mode with the user equipment, the first signaling can be provided to the user equipment.

[0027] The following can be applied to any of the first to eighth aspects mentioned above (e.g., including one or more of all aspects).

[0028] The information indicating which delay information will be determined may include information identifying which delay information will be determined by the device with respect to at least one radio resource control procedure.

[0029] The information indicating the delay information to be determined may include information for identifying radio resource control procedures, which will be determined during the de-energy mode.

[0030] During the reduced energy mode, the delay information will be applied to at least one of the radio resource control procedures in which it is determined, including the radio resource control establishment request procedure and the radio resource control recovery request procedure.

[0031] The first signaling can be included in the process of minimizing drive test signaling.

[0032] The first signaling may include the recorded measurement configuration message.

[0033] According to a ninth aspect, an apparatus is provided, comprising: at least one processor; and at least one memory including code that, when executed by the at least one processor, causes the apparatus to perform: providing an eighth signaling to a network node for minimizing drive tests, the eighth signaling including information requesting first delay information regarding one or more radio resource control procedures that will be performed at the user equipment when the user equipment is in a reduced power mode; and obtaining a ninth signaling from the network node based on the eighth signaling.

[0034] According to a tenth aspect, an apparatus is provided, comprising components for: providing an eighth signaling to a network node for minimizing drive testing, the eighth signaling including information requesting first delay information regarding one or more radio resource control procedures that will be performed at the user equipment when the user equipment is in a reduced power mode; and obtaining a ninth signaling from the network node based on the eighth signaling.

[0035] According to the eleventh aspect, a method for an apparatus is provided, the method comprising: providing an eighth signaling to a network node for minimizing drive testing, the eighth signaling including information requesting first delay information regarding one or more radio resource control procedures that will be performed at the user equipment when the user equipment is in a reduced power mode; and obtaining a ninth signaling from the network node based on the eighth signaling.

[0036] According to a twelfth aspect, an apparatus is provided, comprising: a providing circuit system for providing an eighth signaling to a network node for minimizing drive tests, the eighth signaling including information requesting first delay information regarding one or more radio resource control procedures to be performed at the user equipment when the user equipment is in a reduced power mode; and an obtaining circuit system for obtaining a ninth signaling from the network node based on the eighth signaling.

[0037] The following can be applied with respect to any of the first to twelfth aspects (e.g., including one or more of all aspects).

[0038] The energy reduction mode can include at least one of the idle mode and the inactive mode.

[0039] The first delay information may include information indicating the time taken to perform at least a portion of the radio resource control process.

[0040] According to one aspect, a non-transient computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the method according to any of the foregoing aspects.

[0041] Many different embodiments have been described above. It should be understood that other embodiments can be provided by any combination of two or more of the above embodiments. Attached Figure Description

[0042] Some exemplary embodiments will now be described by way of non-limiting and illustrative examples only, with reference to the accompanying drawings, in which: Figure 1A and Figure 1BA diagram of the communication system is shown; Figure 2 The illustration shows a method for using some example embodiments. Figure 1A and Figure 1B A diagram of a communication system device; Figure 3 Illustrations of an apparatus according to some example embodiments are shown; Figure 4A Example signaling that can be executed for successful Radio Resource Control (RRC) connection establishment is shown; Figure 4B An example delay source for establishing an RRC connection is shown; Figures 5 to 6 Example delay sources for different RRC processes are shown; Figure 7 Example signaling is shown for configuring a user equipment (UE) to provide latency measurement information associated with a connection-mode RRC procedure; Figure 8 An example signal is shown for obtaining delay measurement information from the UE; Figures 9 to 10 Example signaling is shown for configuring a user equipment (UE) to provide delay measurement information associated with a connection-mode RRC procedure; Figures 11 to 13 Example signaling is shown for configuring a user equipment (UE) to provide latency measurement information associated with an idle mode RRC procedure; Figure 14 and Figure 15 An example method is shown for obtaining capability information related to latency measurement information provision from the UE; and Figures 16 to 21 Example methods that can be performed by the apparatus described herein are shown. Detailed Implementation

[0043] Generally speaking, the following refers to measurement information (also referred to as “delay measurement” and / or “delay measurement information”) corresponding to one or more delays of one or more RRC protocol procedures (also referred to as RRC procedures in this document).

[0044] The RRC protocol is a Layer 3 (network layer) protocol used between the UE and the base station. RRC functions may include, for example, connection establishment and release, broadcasting system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release, and outer loop power control. RRC procedures can be used to configure the user plane and control plane based on network conditions and allow for the implementation of radio resource management policies.

[0045] Each RRC procedure can be associated with a maximum delay value that defines the time limit within which the RRC procedure should be completed (e.g., having a maximum delay value). However, the actual delay associated with a particular RRC procedure performed by the UE can vary significantly based on the UE architecture, network architecture, and network configuration. Furthermore, current methods for determining the delay associated with an RRC procedure typically use a test UE configured with special software. This means that determining the UE-specific delay of an RRC procedure for better resource allocation and mobility decisions can be difficult and resource-intensive.

[0046] Although these concepts will be explained in more detail below, examples of communication environments in which the technologies currently described can be deployed are provided. It should be understood that these communication environments are not restrictive and are merely intended to provide at least one example of where such technologies can be deployed.

[0047] In other words, the following explanation will refer to communication devices capable of communicating with a communication system to illustrate various exemplary embodiments. Before explaining in detail embodiments of the methods and apparatus of this disclosure, refer to... Figure 1A , 1B Briefly explain the fifth-generation communication system (5GS), the access network and its core network (5GC), and communication equipment in sections 2 and 3.

[0048] Figure 1A The diagram illustrates a 5G communication system (5GS). 5GS can include user equipment (UE), an access network (such as a 5G radio access network (5G-RAN) or a next-generation radio access network (NG-RAN)), a 5G core network (5GC), and one or more application functions. Application functions can be deployed as trusted application functions within the 5GS, or they can be deployed or hosted on one or more application servers in the data network. Such application functions are untrusted application functions. 5GS connects the UE to the data network, the access network, and the 5GC (e.g., the 5GC's UPF).

[0049] 5G-RAN may include one or more radio access nodes, such as gNodeBs (gNBs). A gNB may include one or more gNodeB distributed units connected to one or more gNodeB centralized units. 5G-RAN can be as follows: Figure 1B As shown.

[0050] 5GC can include the following network functions: Network Slice Selection Function (NSSF); Network Exposure Function; Network Repository Function (NRF); Policy Control Function (PCF); Unified Data Management (UDM); Application Function (AF); Authentication Server Function (AUSF); Access and Mobility Management Function (AMF); Session Management Function (SMF); and User Plane Function (UPF). Figure 1A Various interfaces (N1, N2, etc.) that can be implemented between various components of the system are also shown.

[0051] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), user station (SS), portable user station, mobile device, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), machine-type communication (MTC) devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), data consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Terminal devices may also correspond to the mobile terminal (MT) portion of an integrated access and backhaul (IAB) node (e.g., a relay node). In the following description, the terms “terminal equipment”, “communication equipment”, “terminal”, “user device”, “user equipment” and “UE” are used interchangeably.

[0052] As used herein, the terms "network device" and "network access node" are used interchangeably and refer to a node in a communication network through which terminal devices access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), repeater, integrated access and backhaul node, low-power node (such as femtosecond, picosecond), non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites and geostationary Earth orbit (GEO) satellites), spacecraft network equipment, etc., depending on the terminology and technology applied. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes the mobile terminal (IAB-MT) portion, which behaves similarly to a UE moving toward a parent node, and the DU portion of the IAB node, which behaves similarly to a base station moving toward the next-hop IAB node.

[0053] In some example embodiments, the link from network device 120 to user equipment 110 or 115 is referred to as a DL, while the link from user equipment 110 or 115 to network device 120 is referred to as a UL. The link is also referred to herein as a “channel.” In the DL, network device 120 is a Tx device (or transmitter), and user equipment 110 or 115 is an Rx device (or receiver). In the UL, user equipment 110 or 115 is a Tx device (or transmitter), and network device 120 is an Rx device (or receiver). The link between user equipment 110 and another user equipment (not shown) is referred to as a side link (SL). In the SL, one of the user equipments is a Tx device (or transmitter), and the other is an Rx device (or receiver).

[0054] Communication in communication environment 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G), wireless local area network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0055] Figure 2 It shows the control Figure 1A and 1B The access network shown above (e.g., Figure 1A and 1B An example of a control device 200 for 5G-RAN or NG-RAN functions is shown. The control device 200 may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and a network interface 214. At least one processor 212, 213 may be coupled to RAM 211a and ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. Execution of the software code 215 may, for example, cause the device to perform operations for controlling access network functions. The software code 215 may be stored in ROM 211b. The control device 200 may interconnect with another control device 200 for controlling another function of the 5G-RAN or NG-RAN. In some embodiments, each function of the 5G-RAN or NG-RAN is deployed or hosted on the control device 200. In alternative embodiments, two or more functions of the 5G-RAN or NG-RAN may share the control device.

[0056] Figure 3 A communication device 300 (such as) is shown. Figure 1A and 1BThe example shown above is a UE. Communication device 300 can be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples of communication device 300 include user equipment, mobile station (MS) or mobile device (such as a mobile phone or so-called 'smartphone'), computer provided with a wireless interface card or other wireless interface facility (e.g., a USB dongle), personal data assistant (PDA) or tablet computer provided with wireless communication capabilities, machine-type communication (MTC) device, Internet of Things (IoT) type communication device, or any combination of these devices. Communication device 300 may include a transceiver for transmitting and / or receiving wireless signals, such as those carrying communications (e.g., radio signals). Communication can be one or more of voice, email, text messages, multimedia data, machine data, etc.

[0057] Communication device 300 can receive wireless signals (e.g., radio signals) over the air or on radio interface 307 via suitable means for receiving, and can transmit wireless signals via suitable means for transmitting. Figure 3 In this diagram, the transceiver is schematically designated by block 306. Transceiver 306 may include, for example, a radio section and an associated antenna arrangement. The antenna arrangement may be located inside or outside the mobile device and may include one or more antenna elements. The antenna arrangement may be a multiple-input multiple-output (MIMO) antenna.

[0058] The communication device 300 may provide at least one processor 301, a memory 302 including at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for use in the software and hardware-assisted execution of the tasks it is designed to perform, including access to the network (e.g., Figure 1A and Figure 1B The control of access and communication with 5G-RAN (or NG-RAN) and other communication devices shown is provided. At least one processor 301 is coupled to RAM 302b and ROM 302a. At least one processor 301 can be configured to execute appropriate software code 308. The software code 308 can, for example, allow the execution of one or more operations of the communication device. The software code 308 can be stored in ROM 302a.

[0059] Processors, ROM, and RAM, transceivers, and other circuitry (e.g., modems) for the communication device may be provided on a circuit board, in a chipset, or in a system-on-a-chip. Circuit boards, chipsets, or systems-on-a-chip are indicated by reference numeral 304. The communication device 300 may optionally have a user interface, such as a keyboard 305, a touchscreen or keyboard, or combinations thereof. Optionally, depending on the type of communication device, one or more of a display, speaker, and microphone may be provided.

[0060] UE (such as those mentioned above, see Figure 1 to...) Figure 3 The described access point can be connected to the network via the Radio Resource Control (RRC) protocol.

[0061] In the above-mentioned Figures 1A to 3 In the systems described, it is useful for the radio management device to obtain information about how the UE is currently performing. This information can then be used by the radio management device to make resource allocation decisions, scheduling decisions, and / or mobility decisions.

[0062] One method for obtaining this information is called "minimum drive test" or MDT. According to this method, any UE with predetermined attributes to be tested (e.g., UE location, UE speed, UE chipset, etc.) can be configured to perform measurements to obtain measurement information. Such a UE can also be configured to provide this measurement information to a radio management device.

[0063] Currently, 3GPP describes two types of MDT mechanisms for configuring UEs to obtain measurement data: recorded MDT (denoted as “loggdMDT” in this document) and immediate MDT (denoted as “immediateMDT” in this document) (see, for example, 3GPP TS 37.320).

[0064] When the UE is in RRC idle and / or RRC inactive mode, the loggedMDT method obtains the measurement results performed by the UE for measurement. For clarity and brevity, the following reference to RRC idle mode will be understood to also refer to RRC inactive mode. When the UE is in RRC connected mode, the UE can be configured with information defining how to perform measurements in RRC idle mode by receiving the "LoggedMeasurementConfiguration" RRC message.

[0065] Conversely, when the UE is in RRC connected mode, the immediateMDT method obtains the measurement results of the measurements performed by the UE. As part of this, the network uses measurement identifiers (measurement IDs) that can be used to define which measurements to obtain. Table 1 below indicates the current correspondence between measurement IDs used in 3GPP TS 37.320 and the measurements the UE wants to obtain.

[0066]

[0067] Table 1. Correspondence between Measurement ID and Measured Quantity The measurement information obtained by the UE according to this MDT configuration can be provided to the access node in any of a variety of different ways. One method for providing this information is to use the “UEInformation” procedure defined in section 3GPP TS 38.331 to obtain a RadioLinkFailure report that includes delay measurements.

[0068] However, these existing measurements do not cover the time delay aspect of different RRC processes.

[0069] This may present a problem due to the following: i) Different types of RRC procedures can involve different types of signaling, and therefore different types of RRC procedures can be associated with corresponding delays for execution; ii) Different types of UEs may have latency associated with their hardware and / or software (e.g., different processing speeds, different available resources, etc.); and iii) Different types of RRC procedures can be associated with different maximum delays for execution.

[0070] Regarding i), please refer to the following: Figures 4A to 6 Examples of different time delays associated with different types of RRC processes are shown.

[0071] Figure 4A and Figure 4B An example latency that can be associated with a successful RRC connection process is shown.

[0072] Figure 4A This illustrates the signaling that can be executed between UE 401 and access node 402 when the RRC connection establishment procedure is successfully performed. This procedure can be as shown in 3GPP 38.331.

[0073] During period 4001, UE 401 signals to access node 402. This signaling may include a request to establish an RRC connection. For example, this signaling may include an RRCSetupRequest message.

[0074] During period 4002, access node 402 signals to UE 401. This signaling may include the requested RRC connection configuration for establishing 4001. For example, the signaling may include an RRCSetup message.

[0075] During period 4003, UE 401 signals to access node 402. This signaling may include information indicating to the access node that the RRC configuration of 4002 has been successfully applied by UE 401. For example, this signaling may include an RRCSetupComplete message.

[0076] Figure 4B It shows Figure 4A Examples of delays involved in the signaling are shown in Table 2 below, which describes where these different delays originate. Generally, it should be understood that handover execution delay is typically measured on the UE side from the start of the RRC reconfiguration message carrying the HO command from the source cell until the completion of the transmission of the RRC reconfiguration to the target cell.

[0077]

[0078] Table 2 and Figure 4A Signaling-related delay Figure 5 Example latency can be associated with a non-hands-free RRC reconfiguration process. These example latency are also shown in Table 3 below.

[0079] More specifically, in the case of RRC reconfiguration for adding a Dedicated Resource Block (DRB) or a Secondary Cell (Scell) or completing measurement configuration, the process begins with the reception of the RRC reconfiguration and ends with the transmission of the RRC reconfiguration completion message.

[0080]

[0081] Table 3 Example latency for RRC reconfiguration (non-handover case) Figure 6 Example delays associated with the RRC procedure during handover are shown. These example delays are also shown in Table 4 below.

[0082] Typically, the handover execution delay is measured on the UE side from the start of the RRC reconfiguration message of the bearer handover command from the source cell until the transmission of the RRC reconfiguration to the target cell is completed.

[0083]

[0084] Table 4 shows example latency for RRC reconfiguration (switchover) scenarios. Regarding ii), it is understood that the processing time for the RRC procedure may vary depending on the UE chipset. Currently, there is no standard mechanism to determine how different configurations are executed on different UE chipsets (e.g., across different UEs).

[0085] Regarding iii), 3GPP TS 38.331 provides examples of the maximum latency associated with different types of RRC level procedures. Examples include the RRC procedures mentioned in Table 5 below. It can be seen that some procedures involve multiple RRC messages.

[0086]

[0087] Table 5 shows the maximum delay for different RRC procedures. As mentioned above, the RRC procedure can depend on both the current resource configuration and the UE architecture (e.g., carrier aggregation, multiple-input multiple-output, etc.). Therefore, the size and complexity of the expected RRC message may increase with the number of different configuration options for the combination of network resources and UE hardware.

[0088] Therefore, it can be seen that Table 5 above is insufficient to calculate the latency associated with the entire RRC process (which may include one or more RRC messages), because the process may include multiple message exchanges, may include steps not defined in Table 5 above, and / or may be affected by the specific UE performing the test.

[0089] Therefore, it is evident that obtaining a holistic view of UE performance and understanding how introducing new features into the network impacts performance is currently challenging for operators. This can make network-related decisions, such as resource allocation, scheduling, and / or mobility decisions, difficult.

[0090] To address at least one of the aforementioned aspects, a method for providing a first signaling to a UE is disclosed below, the first signaling including information indicating that first delay information will be determined with respect to at least one radio resource control procedure, and information for causing the first delay information to be determined based on the first signaling. The UE may be in a connected RRC mode. The UE may be in an idle RRC mode.

[0091] This information may include at least one of several different types of information.

[0092] For example, this information can indicate one or more RRC procedures, and the first delay information will be obtained for those one or more RRC procedures.

[0093] In cases where more than one RRC process is indicated, the information may indicate whether information relating to multiple processes should be reported in a consolidated report (e.g., first delay information relating to multiple RRC processes) or in an individual report (e.g., first delay information relating to a single RRC process).

[0094] This information can indicate the granularity of the first delay information to be provided. For example, this information can indicate whether the first delay information corresponds to a single RRC message, a pair of exchanged RRC messages, and / or three or more RRC messages (e.g., when an RRC message corresponds to more than one RRC message exchange).

[0095] It should be understood that these are merely examples, and other types of information may be provided to the UE to indicate that the first delay information will be determined with respect to at least one radio resource control procedure.

[0096] Specifically, the following aims to provide a flexible framework for performing RRC process delay measurements to enable improved network configuration decisions.

[0097] The framework described in this paper can leverage and extend some existing features of the MDT process.

[0098] For example, the following can be introduced as an RRC process-agnostic delay measurement framework, which introduces new MDT RRC process delay measurements (Mx) for access nodes (such as centralized units) to collect them and report them to requesting entities (e.g., Access and Mobility Functions (AMF), Operations and Management (OAM) entities, or some other core network function).

[0099] As described above, the requested latency measurement to be performed by the UE can be measured at a variable granularity level based on how the requesting entity intends to use the latency measurement.

[0100] For example, the delay can be measured at at least one of the following: (a) RRC procedure-level latency: At this granularity, the UE can be configured to report all contributing components of the latency used for the execution of the RRC procedure. For example, consider Figure 4B It will report all components from t1 to t8 (and / or the sum of components from t1 to t8).

[0101] (b) Message-level latency: At this granularity, the UE can be configured to report the latency of all contributing components involved in the successful processing and transmission of a given message. For example, consider... Figure 4B The report will include components t5, t6, t7, and t8 (and / or the sum of these components); or (c) RRC processing level latency: At this granularity, the UE can be configured to report RRC level latency individually for a given successful message exchange. For example, considering Figure 4, t6 can be reported.

[0102] The following will also consider the difference in configuring the UE to perform latency measurements when the UE is in RRC idle mode versus when the UE is in RRC connected mode.

[0103] For example, for a UE in RRC connected mode, the immediateMDT mechanism can be used to configure and / or collect latency measurements for processes occurring in RRC connected mode.

[0104] In this example, the UE can be configured to report latency measurements in any of a variety of different ways. For example, the UE can be configured to provide latency measurements associated with multiple RRC procedures (“connectivity level ranges”). As another example, the UE can be configured to provide latency measurements associated with a single RRC procedure (“per procedure level range”).

[0105] In more detail: Connection level range: This mechanism can be used when it is desired that the UE track the latency of all RRC procedures that occur during RRC connected mode. In this case, the UE continuously tracks all latency and transmits the information to the access node before the UE moves to RRC idle mode.

[0106] Per-process level range: This mechanism can be used when only the latency aspect of a specific process is of interest. When a core network node configures an access node to provide RRC process latency measurement MDT reports, the configured access node can select specific (multiple) UEs and configure the UEs to measure and report latency measurements.

[0107] For UEs configured to perform delay measurements during RRC procedures in RRC idle mode, the LoggedMDT mechanism can be used to configure the set of delay measurement information. For example, the LoggedMDT mechanism can be used to configure tracking of RRC connection establishment and RRC recovery procedures.

[0108] It should be understood that the configuration of these MDT methods can be performed using either signaling-based MDT or management-based MDT.

[0109] Signaling-based MDT can be considered as a request from the core network to the access network node to collect MDT information for a specific UE. This can be performed via next-generation application protocol signaling. The access network node can then configure and collect MDT information from the UE based on this core network request.

[0110] Conversely, management-based MDT can be considered as when Operations and Management (OAM) functions are configured to collect information in a specific area. In this case, OAM requests the access network node to perform the collection. The access network node then selects one or more UEs from which it collects messages (e.g., based on the configured number and / or percentage of the UEs to be requested) and requests MDT measurements from the selected UEs(s).

[0111] Regarding Figures 7 to 21 The examples illustrate these and other aspects.

[0112] For clarity and brevity, at least some of the examples below will consider the RRC connected mode and RRC idle mode procedures separately. However, it should be understood that when the same terminology is used in different procedures, the term can be understood in the same way. Furthermore, it should be understood that the term "RRC idle mode" is used interchangeably with "RRC inactive mode" in this document.

[0113] Figure 7 and Figures 9 to 10 The RRC connection mode signaling is shown.

[0114] Figure 7 Example signaling that can be executed as part of an RRC connection mode procedure is shown.

[0115] Figure 7 The signaling that can be executed between UE 701 and access node 702 is shown.

[0116] During period 7001, access node 702 sends a signal to UE 701. This signaling may include RRC connection mode messages. For example, the signaling may include at least one of the following: an RRC establishment message, an RRC reconfiguration request message, and an RRC recovery process.

[0117] The signaling of 7001 may include information instructing the UE to perform at least one measurement corresponding to the delay (also referred to herein as a "delay measurement"). For example, the signaling of 7001 may include information that triggers the UE to perform at least one delay measurement.

[0118] Although the UE may be pre-configured with information indicating what delay information should be provided, in this example, the signaling of 7001 may include at least a portion of the information indicating what delay information should be provided.

[0119] Several different types of such information exist that can be provided in the 7001 signaling. These are discussed below as "delay measurement range" information and "delay granularity configuration" information.

[0120] The latency measurement range information may include at least one value that instructs the UE to measure processing latency. The latency measurement range information may include an enumerated value of a process range information element (IE) and / or a connection range IE. When the IE value is set to process range, or if the process range IE is not included in the 7001 signaling, latency measurement applies only to a single specific RRC process. Conversely, when the IE value is set to connection range, latency measurement can be performed with respect to multiple (e.g., two or more) subsequent RRC processes exchanged while the UE is in the RRC-Connected state.

[0121] The "Latency Granularity Configuration" IE can indicate the granularity of the set of measurements used to perform latency measurements. For example, when the value for this IE is set to "RRC Layer Level," latency measurements are obtained only with respect to the RRC layer (e.g., the time from receiving an incoming procedure at the UE's RRC layer to sending a response procedure from the RRC layer). Conversely, when this IE is set to a value indicating "RRC Message Level," the latency between a request triggered by the access node and a response sent by the UE is measured. If this IE is set to "RRC Procedure Level," the latency of multiple RRC messages across RRC procedures is measured.

[0122] During this period, UE 701 performs multiple delay measurements as indicated by signaling from 7001.

[0123] Although not shown, in the example, UE 701 can signal access node 702 to indicate that delay measurement information is available. Regarding Figure 8 Let's discuss this example further.

[0124] Figure 8 This illustrates a method by which an access node can obtain one or more delay measurements.

[0125] Figure 8 The signaling that can be executed by UE 801 and access node 802 is shown.

[0126] During period 8001, network access node 802 sends a signal to UE 801. This signaling may include a request for at least one latency measurement. This signaling may be included in a UE information request. The request for at least one latency measurement may be labeled LatencyMeasurementInfoReq.

[0127] The signaling for 8001 can be executed based on information previously received by network access node 802 from UE 801 indicating that at least one delay measurement is available. In other words, the execution of signaling for 8001 can be triggered based on receiving information from UE 801 indicating that at least one delay measurement is available. The information indicating that at least one delay measurement is available can involve a single delay measurement and / or multiple delay measurements. However, it should be understood that the signaling for 8001 can be executed based on some other criteria (e.g., timer timeout since the signal for 7001 was sent). In other words, the signaling for 8001 can be executed even if there is no information indicating that at least one delay measurement has been received from UE 801.

[0128] The 8001 signaling may include information identifying at least one delay measurement to be obtained.

[0129] During signaling 8002, UE 801 sends a signal to access node 802. This signaling may include at least one latency measurement requested in 8001. The signaling may include at least a portion of the at least one latency measurement requested in 8001. The latency measurement information provided in the signaling of 8002 may be tagged as LatencyMeasurementInfoResult.

[0130] Figure 8 The process can be used to obtain at least one latency measurement when the UE is in idle mode and / or connected mode.

[0131] Regarding this, for (multiple) RRC-Connected UEs, after latency measurement is activated, the UE performs latency measurement and creates a LatencyResult according to this configuration. Before releasing the RRC connection, the access node can obtain the merged latency measurement results by sending an enhanced UE information request procedure, as mentioned above. Figure 8 As described.

[0132] Similarly, for an RRC-Idle mode UE that performs at least one delay measurement in idle mode, when the UE re-enters RRC connected mode, the access node can perform... Figure 8 The method is to obtain at least one latency measurement from the UE. This will be further illustrated in the RRC idle mode example below.

[0133] Figure 9 and Figure 10 It shows Figure 7 and Figure 8 The principle shown can be implemented by a UE in RRC connection mode. Although Figure 9 and Figure 10 All of these involve using the RRC reconfiguration request message to configure latency measurement, but it should be understood that this is just an example and other types of RRC messages can be used to configure latency measurement.

[0134] Figure 9 The diagram illustrates the signaling that can be executed by UE 901, access node 902, and core network node 903. The core network node can be, for example, an access and mobility function. Figure 9 The signaling can involve situations where the UE is instructed to use an RRC reconfiguration request message to perform latency measurements.

[0135] During 9001, core network node 903 signals to access node 902. This signaling may include instructions for access node 902 to configure latency measurement configuration (such as signaling via 7001) to UE 901. This signaling may include messages initiating MDT procedures, such as a trace start message.

[0136] The signaling may include a UE identifier to indicate to the access node 902 which UE will be configured to provide latency measurement. The signaling may include corresponding identifiers (and / or group identifiers of multiple UEs) for indicating to the access node 902 which UE will be configured to provide latency measurement.

[0137] The signaling may include the identifier of the RRC procedure for which delay measurement is to be performed. The signaling may include the corresponding identifiers of multiple RRC procedures for which delay measurement is to be performed.

[0138] During period 9002, access node 902 sends a signal to UE 901. This signaling may include an RRC reconfiguration request. This signaling may include at least one of the aforementioned delay measurement range configuration and delay granularity configuration.

[0139] During 9003, UE 901 performs at least one latency measurement configured during 9002.

[0140] During period 9004, UE 901 signals to access node 902. This signaling may indicate that RRC reconfiguration of 9002 has been completed. For example, the signaling may include an RRC reconfiguration completion message. Optionally, the signaling may include an indication that at least one latency measurement has been performed. For example, the signaling may include the LatencyMeasurementAvailable information element described above.

[0141] During period 9005, access node 902 sends a signal to UE 901. This signaling may include a request for at least one delay measurement obtained during period 9002. This signaling may be as described above with respect to period 8001.

[0142] During period 9006, UE 901 sends a signal to access node 902. This signaling may include at least one delay measurement. This signaling may be as described above with respect to 8002. This signaling may also (in some examples) include delay measurement information related to the duration between 9004 and 9005.

[0143] During 9007, access node 902 signals to core network node 903. This signaling may include one or more MDT records based on at least one delay information received from 9006 and / or include at least one delay measurement from 9006. This signaling may be sent to the core network node using any appropriate signaling (e.g., cell tracking message).

[0144] Figure 10 This illustrates the process for implementing a reconfiguration request for RRC. Figure 7 and Figure 8Another example of the above principle is a signaling diagram.

[0145] Figure 10 The diagram illustrates signaling that can be executed by UE 1001, access node 1002, and core network node 1003. The core network node can be, for example, an access and mobility function. Figure 10 The signaling can involve situations where the UE is instructed to use an RRC reconfiguration request message to perform latency measurements.

[0146] During 10001, core network node 1003 sends a signal to access node 1002. This signaling may include instructions for access node 1002 to configure latency measurement configuration (such as signaling via 7001) to UE 1001. This signaling may include a trace start message.

[0147] The signaling may include a UE identifier to indicate to access node 1002 which UE will be configured to provide latency measurement. The signaling may include corresponding identifiers (and / or group identifiers of multiple UEs) for indicating to access node 1002 which UE will be configured to provide latency measurement.

[0148] The signaling may include the identifier of the RRC procedure for which delay measurement is to be performed. The signaling may include the corresponding identifiers of multiple RRC procedures for which delay measurement is to be performed.

[0149] During period 10002, access node 1002 sends a signal to UE 1001. This signaling may include an RRC reconfiguration request. This signaling may include at least one of the aforementioned delay measurement range configuration and delay granularity configuration.

[0150] During period 10003, UE 1001 sends a signal to access node 1002. This signaling can indicate that the RRC reconfiguration of 10002 has been completed. For example, this signaling can include an RRC reconfiguration completion message.

[0151] During period 10004, access node 1002 sends a signal to UE 1001. This signaling may include an RRC reconfiguration request. In this example, the signaling at 10004 does not include the aforementioned delay measurement range and / or delay granularity configuration.

[0152] During period 10005, UE 1001 performs at least one delay measurement configured during period 10002.

[0153] During period 10006, UE 1001 sends a signal to access node 1002. This signaling may indicate that the RRC reconfiguration of 10004 has been completed. For example, the signaling may include an RRC reconfiguration completion message. Optionally, the signaling may include an indication that at least one latency measurement has been performed. For example, the signaling may include the LatencyMeasurementAvailable information element described above.

[0154] During period 10007, access node 1002 sends a signal to UE 1001. This signaling may include an RRC reconfiguration request. In this example, the signaling for 10007 does not include the aforementioned delay measurement range and / or delay granularity configuration.

[0155] During period 10008, UE 1001 performs at least one latency measurement configured during period 10002.

[0156] During period 10009, UE 1001 sends a signal to access node 1002. This signaling may indicate that the RRC reconfiguration of 10006 has been completed. For example, the signaling may include an RRC reconfiguration completion message. Optionally, the signaling may include an indication that at least one latency measurement has been performed. For example, the signaling may include the LatencyMeasurementAvailable information element described above.

[0157] During period 10010, access node 1002 sends a signal to UE 1001. This signaling may include a request for at least one delay measurement obtained during at least one of periods 10005 and 10008. This signaling may be as described above with respect to 8001.

[0158] During period 10011, UE 1001 sends a signal to access node 1002. This signaling may include at least one delay measurement requested during period 10010. This signaling may be as described above with respect to 8002.

[0159] During period 10012, access node 1002 sends a signal to core network node 1003. This signaling may include one or more MDT records based on at least one delay information received from 10011 and / or include at least one delay measurement of 10011. This signaling may be sent to the core network node using, for example, a cell tracking message.

[0160] Figures 11 to 13 The following example will show how the principles described here can be performed when the UE is in RRC idle mode.

[0161] Figure 11This illustrates how a UE can be configured to perform at least one latency measurement when the UE is in RRC idle mode.

[0162] Figure 11 The signaling that can be executed between UE 1101 and access node 1102 is shown.

[0163] During period 11001, access node 1102 sends a signal to UE 1101. This signaling can be performed when the UE is in RRC connected mode. The signaling may include configurations for enabling the UE to perform latency measurement when the UE is in RRC idle mode. The signaling may include a LoggedMeasurementConfiguration message. The RRC procedure involved in the latency measurement may be, for example, an RRC establishment request and / or an RRC recovery request. The signaling may include a new event type information element (labeled "latency measurement" herein). When the UE receives this message when the latency measurement IE is set to true, the UE can perform latency measurement for subsequent RRC procedures and report measurement availability to the access network node.

[0164] In the example, the latency measurement IE does not include identifiers for one or more RRC procedures involved in the latency measurement. In this case, the UE can perform latency measurements on the default RRC procedures when entering RRC idle mode. For example, the UE can perform latency measurements on the first RRC procedure executed by the UE when entering RRC idle mode. As another example, the UE can perform latency measurements on the last RRC procedure executed by the UE before entering RRC connected mode.

[0165] In the example, the signaling of 11001 may include at least one of the above-mentioned delay measurement range and delay granularity configuration.

[0166] Although not shown, after the UE is configured according to 11001, the UE can enter RRC idle mode and perform at least one latency measurement according to the configuration of 11001.

[0167] Figure 12 An example is shown whereby the UE notifies the access node that at least one latency measurement is available after performing at least one latency measurement configured by 1101.

[0168] Figure 12 The signaling that can be executed between UE 1201 and access node 1202 is shown.

[0169] During 12001, UE 1201 signals to access node 1202. This signaling may include an indication that at least one latency measurement configured by 1101 has been performed. This indication may be labeled herein as a LatencyMeasurementAvailable information element. This signaling may be included in an RRC message. For example, the signaling may include an RRC establishment complete message and / or an RRC recovery complete message. The signaling for 12001 may be sent based on (e.g., in response to and / or triggered by and / or after) UE 1201 returning to RRC connection mode.

[0170] Figure 13 Example signaling that can be executed when the UE is configured to perform at least one delay measurement while the UE is in RRC idle mode is shown.

[0171] Figure 13 The signaling that can be executed between UE 1301, access node 1302 and core network node 1303 is shown.

[0172] During period 13001, the UE and the access node are in an RRC connection state.

[0173] During period 13002, core network node 1303 sends a signal to access node 1302. This signaling may include information instructing the UE to be configured to perform and / or report at least one delay measurement. This signaling may be the same as the signaling described above with respect to 9001.

[0174] During 13003, access node 1302 determines that the signaling of 13002 indicates that the UE should be configured to perform at least one delay measurement for an RRC procedure that is performed at least in part when the UE is in RRC idle mode.

[0175] Based on the determination at 13003, during 13004, access node 1302 sends a signal to UE 1301. The signaling at 13004 can correspond to the signaling at 1101.

[0176] During period 13005, access node 1302 sends a signal to UE 1301. This signaling may include information to trigger the UE to enter RRC idle mode. For example, the signaling at 13005 may include an RRC release message.

[0177] During period 13006, the UE was in RRC idle mode.

[0178] During 13007, UE 1301 determined that the UE would be moved to RRC connection mode.

[0179] Based on the determination of 13007 and / or the configuration of 13004, during 13008, UE 1301 initiates the execution of at least one delay measurement according to the configuration of 13004.

[0180] During period 13009, UE 1301 sends a signal to access node 1302. This signaling may include a request to enter RRC connection mode. For example, the signaling may include an RRC establishment request.

[0181] During period 13010, access node 1302 sends a signal to UE 1301. This signaling may include configuration for configuring UE 1301 to enter an RRC connection mode with access node 1302. For example, the signaling may include an RRC establishment message.

[0182] During 13011, UE 1301 can determine whether to perform additional latency measurements based on the configuration of 13004. For example, additional latency measurements after sending the RRC setup completion message (e.g., during 13012).

[0183] During period 13012, UE 1301 sends a signal to access node 1302. This signaling may include an indication that at least one delay measurement is available at UE 1301. For example, this signaling may be as described above regarding... Figure 7 As described. For example, the signaling may include an RRC setup complete message. The signaling may include a LatencyMeasurementAvailable IE (as described above).

[0184] During period 13013, access node 1302 signals to UE 1301. This signaling may include a request for at least one delay measurement. This may be as described above with respect to 8001. For example, the signaling may include a UEInformationRequest element.

[0185] During period 13014, UE 1301 sends a signal to access node 1302. This signaling may include at least one delay measurement. This signaling may be as described above with respect to 8002.

[0186] During 13015, access node 1302 sends a signal to core network node 1303. This signaling can be as described above regarding 9007.

[0187] exist Figures 7 to 13In all the examples above, it is assumed that the RRC procedure, which is the subject of at least one latency measurement, is successfully executed. However, even if the UE encounters a failure for that RRC procedure, the method described above can still be executed. In this case, the UE can store and report at least one latency measurement even for a failed procedure. For the idle mode case, at least one stored latency can be reported after a successful RRC connection to the access node.

[0188] Furthermore, information indicating that at least one delay is associated with a failed process can be used to report at least one reported delay. This can be useful, for example, when the reported at least one delay measurement involves an end-to-end RRC process or some other granularity affected by the failure. When at least one delay measurement is not involved in a part of an RRC process affected by the failure, at least one delay measurement can be reported to the access node without any information indicating that at least one delay measurement is associated with the failed process.

[0189] As should be understood above, different combinations of measurement granularity and measurement range can have their own individual measurement identifiers (Mx). The core network can use these individual measurement identifiers to trigger relevant delay measurements toward the UE.

[0190] In some examples, the access node may determine whether to execute the principles described herein based on the UE's ability to perform at least one latency measurement.

[0191] For example, the UE can notify the access node of its ability to perform latency measurements via the "UE-BasedPerfMeas-Parameters" IE in the UE-NR-capabilities.

[0192] The capability information provided by the UE may include information about the UE's ability to report latency information in connected mode (labeled as latencyMeasLog-rX in this document).

[0193] The capability information provided by the UE can include information about the number of RRC procedures for which it can store latency information when using the "RRC Connection Range" configuration. This can be useful because the capability can vary for UEs with normal and reduced capabilities. There are at least two ways to specify this configuration aspect. For example, the UE can report the number as a capability (e.g., using a new information element labeled maxRRCP proceduresTraked herein). As another example, the capability can be a hard-coded configuration in terms of memory size (e.g., in kB), which can be reported to the access node. In either of these options, once the buffer is full, the UE can rewrite the old information with the latency information of the latest procedure.

[0194] The capability information provided by the UE may include information indicating the UE's ability to measure latency in RRC idle mode and / or report such information via recorded measurements (as described above with respect to LatencyMeasLogViaLoggedMDT).

[0195] The following provides at least one signaling procedure for each example in the connected and idle mode examples to illustrate how the UE provides this capability information to the access node. It should be understood that these are merely examples, and the access node may obtain the UE's capability information in some other way. For example, the UE's capabilities may be stored by the core network node, and the access node may be configured to obtain such information from the core network node. As another example, the UE's capabilities may be provided to the access node by another access node, such as during a handover process and / or as part of a two-component carrier procedure.

[0196] Figures 14 to 15 The following examples and Figures 7 to 13 Examples of any of the items are compatible, where Figure 14 and Figures 7 to 10 Related to the RRC connection mode example, and Figure 15 and Figures 11 to 12 This relates to the RRC idle mode example. In other words, the following example can be performed before the UE is configured to provide latency measurement information obtained during RRC idle mode or RRC connected mode.

[0197] Figure 14 An example method is shown for how an access node can determine whether a UE is able (e.g., capable) to perform at least one delay measurement of an RRC procedure when the UE is in RRC connection mode.

[0198] It should be understood that this is merely an example, and other methods are possible. Furthermore, the access node can simply attempt to configure the UE without attempting to obtain prior knowledge of the UE's latency measurement capabilities (e.g., without performing [specific actions]). Figure 14 (or similar methods).

[0199] Figure 14 The diagram illustrates the signaling that can be executed between UE 1401, access node 1402, AMF 1403, and Operation and Management Function (OAM) 1404 when UE 1401 is configured to obtain at least one latency measurement while UE 1401 is in RRC connection mode.

[0200] During 14001, OAM 1404 signals to access node 1402. This signaling can configure access node 1402 with an MDT measurement configuration for measuring delays for one or more different RRC procedures. The MDT configuration can include information identifying which types of RRC procedures will be considered for delay measurement and the level at which they need to be measured (e.g., RRC procedure level or end-to-end). In other words, the signaling at 14001 can configure the access node with information to determine the aforementioned "delay measurement range" and "delay granularity configuration" information.

[0201] 14002 to 14007 can correspond to the procedures performed when the UE establishes an RRC connection with the access node.

[0202] During 14002, UE 1401 switches between RRC idle mode and RRC connected mode. This can be performed, for example, using the RRC establishment procedure for registering UE 1401 with access node 1402.

[0203] During 14003, access node 1402 signals to AMF 1403. The signaling in 14003 can be used to establish a context for the UE. For example, the signaling in 14003 may include Next Generation Application Protocol (NGAP) messages (such as NGAP: InitialUEMessage) to create a next generation context for the UE.

[0204] During period 14004, AMF 1403 identifies that UE 1401 is not registered with the AMF (e.g., no UE context for UE 1401 is available to AMF 1403). AMF 1403 determines to register UE 1401 with AMF 1403. AMF 1403 can register the UE with the AMF by, for example, performing a Non-Access Stratum (NAS) message exchange for registration, authentication, and NAS security activation.

[0205] Assuming UE 1401 is successfully registered at AMF 1403, AMF 1403 will continue to build the UE context for UE 1401 by proceeding to 14005.

[0206] During period 14005, AMF 1403 signals to access node 1402. This signaling may include an InitialContextSetupRequest message.

[0207] During 14006, access node 1402 configures a security mode for UE 1401 at the RRC protocol level. This can be performed, for example, using the RRC: SecurityMode procedure.

[0208] During 14007, assuming the access stratum was successfully enabled during 14006, access node 1402 signals to UE 1401. This signaling may include a request for UE capability information. For example, this signaling may include a UECapbilityEnquiry message. This signaling can be executed at the RRC tag.

[0209] During 14008, UE 1401 signals to Access Node 1402. This signaling may include information about the UE's capabilities. For example, the signaling may include information about the UE's ability to perform latency measurements as described herein. For example, the signaling at 14008 may include information about its latency measurement capabilities using the UE-NR-Capability field (e.g., the latencyMeasReport-rX information element in the UE-BasedPerfMeas-Parameters field of the UE-NR-Capability field). The UE's capability information may indicate the granularity of the latency measurements that can be performed by the UE (e.g., at the RRC message level, end-to-end level, etc.). The UE's capability information may indicate that the UE is capable of performing one or more procedures for at least one latency measurement. For example, the UE may be able to perform latency measurements for a connected mode RRC procedure but not for an idle mode RRC procedure.

[0210] During period 14009, access node 1402 stores information about the latency capabilities of the UEs received during period 14008. This storage can be performed locally on access node 1402, but it should be understood that this is not required.

[0211] During period 14010, the access node provides UE capability information to AMF 1403. This can be done using the NGAP:UECapabilityInfoIndication message.

[0212] During 14011, access node 1402 signals to AMF 1403. This signaling indicates that the initial setup configuration notified during 14005 has been successfully applied. This signaling can be provided using, for example, the NGAP: InitialContextSetup message.

[0213] Pages 14012 to 14013 illustrate example signaling that can be executed when an access node attempts to measure latency in RRC connection mode.

[0214] During 14012, access node 1402 determines whether UE 1401 is capable of performing at least one latency measurement in RRC connection mode. This determination in 14012 can be performed using (e.g., based on) information stored during 14009. The determination in 14012 may additionally determine whether UE 1401 is capable of performing at least one latency measurement at a specific granularity (e.g., RRC procedure level and / or end-to-end level).

[0215] Although not shown, 14012 can be executed based on (e.g., depending on) a request received from the AMF and / or OAM to enable UE 1401 to perform at least one delay measurement. In this case, when determining whether UE 1401 is able to perform at least one delay measurement at a specific granularity, the specific granularity can be based on the request from the AMF and / or OAM.

[0216] If it is determined during 14012 that UE 1401 is unable to perform at least one delay measurement, access node 1402 may refrain from signaling delay measurement configuration to UE 1401.

[0217] When it is determined during 14012 that the UE is able to perform at least one delay measurement, the method proceeds to 14013.

[0218] During 14013, access node 1402 configures UE 1401 to perform at least one latency measurement, such as those mentioned above. Figures 7 to 10 As described in any of the items in [the document / concept].

[0219] Figure 15 An example method is shown for how an access node can determine whether a UE is able (e.g., capable) to perform at least one delay measurement of an RRC procedure when the UE is in RRC idle mode.

[0220] It should be understood that this is merely an example, and other methods are possible. Furthermore, the access node can simply attempt to configure the UE without attempting to obtain prior knowledge of the UE's latency measurement capabilities (e.g., without performing [specific actions]). Figure 15 (or similar methods).

[0221] Figure 15 The diagram illustrates the signaling that can be executed between UE 1501, access node 1502, AMF 1503, and Operation and Management Function (OAM) 1504 when UE 1501 is configured to obtain at least one latency measurement while UE 1501 is in RRC idle mode.

[0222] During 15001, OAM 1504 signals to access node 1502. This signaling can configure the MDT measurement configuration for access node 1502 to measure the delay for one or more different RRC procedures. The MDT configuration can include information identifying which types of RRC procedures will be considered for delay measurement and the level at which they need to be measured (e.g., RRC procedure level or end-to-end). In other words, the signaling of 15001 can configure the access node with information to determine the aforementioned "delay measurement range" and "delay granularity configuration" information.

[0223] 15002 to 15007 can correspond to the procedures performed when the UE establishes an RRC connection with the access node.

[0224] During 15002, UE 1501 switches between RRC idle mode and RRC connected mode. This can be performed using, for example, the RRC establishment procedure used to register UE 1501 with access node 1502.

[0225] During 15003, access node 1502 signals to AMF 1503. The signaling of 15003 can be used to establish a context for the UE. For example, the signaling of 15003 may include Next Generation Application Protocol (NGAP) messages (such as NGAP: InitialUEMessage) to create a next generation context for the UE.

[0226] During period 15004, AMF 1503 identifies that UE 1501 is not registered with the AMF (e.g., no UE context of UE 1501 is available to AMF 1503). AMF 1503 determines to register UE 1501 with AMF 1503. AMF 1503 can register the UE with the AMF by, for example, performing a Non-Access Stratum (NAS) message exchange for registration, authentication, and NAS security activation.

[0227] Assuming UE 1501 is successfully registered at AMF 1503, AMF 1503 will continue to establish a UE context for UE 1501 by proceeding to 15005.

[0228] During period 15005, AMF 1503 signals to access node 1502. This signaling may include an InitialContextSetupRequest message.

[0229] During 15006, access node 1502 configures a security mode for UE 1501 at the RRC protocol level. This can be performed, for example, using the RRC: SecurityMode procedure.

[0230] During 15007, assuming the access stratum was successfully enabled during 15006, access node 1502 signals to UE 1501. This signaling may include a request for UE capability information. For example, this signaling may include a UECapbilityEnquiry message. This signaling can be executed at the RRC tag.

[0231] During 15008, UE 1501 signals to Access Node 1502. This signaling may include information about the UE's capabilities. For example, the signaling may include information about the UE's ability to perform latency measurements as described herein. For example, the signaling at 15008 may include information about its latency measurement capabilities using the UE-NR-Capability field (e.g., the latencyMeasReport-rX information element in the UE-BasedPerfMeas-Parameters field of the UE-NR-Capability field). The UE's capability information may indicate the granularity of the latency measurements that can be performed by the UE (e.g., at the RRC message level, end-to-end level, etc.). The UE's capability information may indicate that the UE is capable of performing one or more procedures for at least one latency measurement. For example, the UE may be capable of performing latency measurements for an idle mode RRC procedure but not for a connected mode RRC procedure.

[0232] During period 15009, access node 1502 stores information about the latency capabilities of the UEs received during period 15008. This storage can be performed locally on access node 1502, but it should be understood that this is not required.

[0233] During period 15010, the access node provides UE capability information to AMF 1503. This can be done using the NGAP:UECapabilityInfoIndication message.

[0234] During 15011, access node 1502 signals to AMF 1503. This signaling indicates that the initial setup configuration notified during 15005 has been successfully applied. This signaling can be provided using, for example, the NGAP: InitialContextSetup message.

[0235] Pages 15012 to 15013 illustrate example signaling that can be executed when an access node attempts to measure latency in RRC idle mode.

[0236] During 15012, access node 1502 determines whether UE 1501 is capable of performing at least one latency measurement in RRC idle mode. This determination of 15012 can be performed using (e.g., based on) information stored during 15009. The determination of 15012 may additionally determine whether UE 1501 is capable of performing at least one latency measurement at a specific granularity (e.g., RRC procedure level and / or end-to-end level).

[0237] Although not shown, 15012 can be performed based on (e.g., depending on) a request received from the AMF and / or OAM to enable UE 1501 to perform at least one delay measurement. In this case, when determining whether UE 1501 is able to perform at least one delay measurement at a specific granularity, the specific granularity can be based on the request from the AMF and / or OAM.

[0238] If it is determined during 15012 that UE 1501 is unable to perform at least one delay measurement, access node 1502 may refrain from signaling delay measurement configuration to UE 1501.

[0239] When it is determined during step 15012 that the UE is able to perform at least one delay measurement, the method proceeds to step 15013.

[0240] During 15013, access node 1502 configures UE 1501 to perform at least one latency measurement, such as those mentioned above. Figures 11 to 13 As described in any of the items in [the document / concept].

[0241] The example above illustrates how capability information is provided from the UE to the access node. The following shows how to mark this capability information in the relevant 3GPP specification: UE-BasedPerfMeas-Parameters-r16: latencyMeasReport-rX LatencyMeasurementCapability OPTIONAL LatencyMeasurementCapability ::= SEQUENCE { latencyMeasLog-rX ENUMERATED {supported} OPTIONAL maxRRCProceduresTracked INTEGER (1..16) OPTIONAL -- COND MAX-TRACKED-RRC-PROCS latencyMeasLogViaLoggedMDT ENUMERATED {supported} OPTIONAL -- COND LOGGED-LATENCY-MEAS }

[0242] The following is for reference. Figures 16 to 21 Highlight at least some of the features mentioned above in the example. Figures 16 to 18 The features that can be executed when delay information corresponding to the RRC connection mode RRC procedure is expected are shown, and Figures 19 to 21 The features that can be executed when delay information corresponding to the RRC idle mode RRC procedure is expected are shown.

[0243] Figure 16 A method that can be performed by a device is shown. The device may include a UE, such as those described above. Figure 3 As described.

[0244] During 1601, the device receives first signaling from a network node, the first signaling including information indicating that first delay information will be determined regarding at least one radio resource control procedure when the device is in connected mode. For example, during 1601, the device receives first signaling including information indicating that first delay information will be determined, wherein the first delay information corresponds to at least one radio resource control procedure performed when the device is in RRC connected mode.

[0245] Network nodes can include access nodes (e.g., gNBs, base stations, etc., as mentioned above regarding Figure 1 and...) Figure 2 (As described). Network nodes can correspond to Figure 17 The device. Network nodes may include core network nodes, such as AMF, OAM, etc.

[0246] During 1602, the device determines the first delay information based on the first signaling. For example, the device determines the first delay based on information indicating that the first delay information will be determined.

[0247] As mentioned above, in the example, Figure 16 The device can receive a corresponding trigger for providing first delay information to network nodes. Although not strictly necessary, Figure 16 The device can also signal to the network node when the first delay information is available. This latter feature can be used to reduce redundant communication because the network node can refrain from signaling the device to provide the first delay information if it has not yet received the information indicating that the first delay information is available.

[0248] For example, the device may provide a second signaling to a network node, the second signaling including information indicating that the first delay information is available regarding at least one radio resource control procedure, obtaining a third signaling from the network node including a request for the first delay information, and providing the first delay information to the network node (e.g., based on the second signaling).

[0249] As mentioned above, Figure 16 The device can receive a trigger for providing both first and second delay information to network nodes.

[0250] For example, consider a situation similar to the previous example. Figure 16 The device can obtain a fourth signaling from the network node, the fourth signaling including information indicating that second delay information will be determined regarding at least one radio resource control procedure when the device is in connected mode, and determine the second delay information based on the fourth signaling. Subsequently, the device can provide a fifth signaling to the network node, the fifth signaling including information indicating that at least one of the first and second delay information is available regarding at least one radio resource control procedure, obtain a sixth signaling from the network node including a request for the first and second delay information, and provide the first and second delay information to the network node.

[0251] It should be understood that these examples are network nodes from Figure 16 An example of a device pulling data, and Figure 16 The device can alternatively push latency information directly to network nodes without first receiving a trigger (e.g., a request) for such information.

[0252] The device can also provide a seventh signaling to the network node before receiving the first signaling. The seventh signaling includes information instructing the device on its ability to determine delay information regarding one or more radio resource control procedures, wherein the first signaling is based on the seventh signaling.

[0253] Figure 17 A method that can be performed by an apparatus is illustrated. The apparatus may include network nodes. For example, the apparatus may include access nodes (such as those discussed in the examples above). As another example, the apparatus may include core network nodes, such as AMF and / or OAM.

[0254] During 1701, the device provides the user equipment with first signaling, which includes information indicating that when the user equipment is in connected mode, first delay information will be determined regarding at least one radio resource control procedure.

[0255] Similar to Figure 16 The above example, Figure 17The device can provide a corresponding trigger for the first delay information, and / or provide triggers for both the first delay information and the second delay information. In other words, Figure 17 The apparatus can be used to extract data from a single RRC process and / or from multiple RRC processes. Figure 16 The device obtains latency information.

[0256] For example, the device can obtain a second signaling from the user equipment, the second signaling including information indicating that the first delay information is available regarding at least one radio resource control procedure, provide the user equipment with a third signaling including a request for the first delay information, and obtain the first delay information from the user equipment.

[0257] As another example, the device may provide a fourth signaling to the user equipment, the fourth signaling including information indicating that second delay information will be determined regarding at least one radio resource control procedure when the device is in connected mode. Subsequently, the device may obtain a fifth signaling from the user equipment, the fifth signaling including information indicating that the first delay information is available regarding the availability of at least one radio resource control procedure, provide the user equipment with a sixth signaling including a request for the first delay information and the second delay information, and obtain the first delay information and the second delay information from the user equipment.

[0258] It should be understood that these examples are network nodes from Figure 16 An example of a device pulling data, and Figure 16 The device can alternatively push latency information directly to network nodes without first receiving a trigger (e.g., a request) for such information. In this case, the network node may also not receive any prior information indicating that the first latency information is available (e.g., the latency information can arrive directly).

[0259] The device can obtain a seventh signaling from the user equipment before providing the first signaling, the seventh signaling including information instructing the user equipment on its ability to determine delay information regarding one or more radio resource control procedures, wherein the first signaling is based on the seventh signaling.

[0260] Figure 17 The device can also be used with the following: Figure 18 Interact with the described device.

[0261] For example, the device can obtain an eighth signaling message from the core network node for minimizing drive tests. This eighth signaling message includes information requesting delay information regarding one or more radio resource control procedures that will be performed at the user equipment when it is in connected mode. Based on this eighth signaling message, the device provides a ninth signaling message to the core network node. The ninth signaling message may include first and / or second delay information, and / or information based on the first and / or second delay information.

[0262] The device can also determine the user equipment's capability to determine the first delay information based on the obtained eighth signaling, and provide the first signaling based on the determined user equipment capability.

[0263] The first signaling may include at least one of a radio resource control reconfiguration message, a radio resource control recovery message, and a radio resource control establishment message.

[0264] It can also provide information such as... Figure 18 The device described. Figure 18 The devices may include core network devices, such as the core network devices described in the preceding paragraphs.

[0265] During 1801, Figure 18 The device provides network nodes with an eighth signaling message for minimizing drive tests. This eighth signaling message includes information requesting first delay information regarding one or more radio resource control procedures that will be executed at the user equipment when the user equipment is in connected mode. The network node can, as described above, provide... Figure 17 As described. User equipment can correspond to Figure 16 The device.

[0266] During 1802, the device obtains the ninth signaling from the network node based on the eighth signaling.

[0267] Figures 19 to 21 Features of the above-described example of RRC reduced energy mode are illustrated. For example, when the device is in an idle mode (e.g., RRC idle mode) and / or an inactive mode (e.g., RRC inactive mode), Figures 19 to 21 Examples can be performed at least partially by the device.

[0268] Figure 19 A method that can be performed by a device is shown. The device may include a UE, such as those described above. Figure 3 As described.

[0269] During 1901, the device receives first signaling from a network node. This first signaling includes information indicating that, when the device is in idle mode, first delay information will be determined regarding at least one radio resource control (RRC) procedure. For example, during 1901, the device receives first signaling including information indicating that, when the device is in de-energized mode, first delay information will be determined regarding at least one RRC procedure. The first delay information corresponds to at least one radio resource control procedure that is at least partially executed when the device is in RRC idle mode and / or RRC inactive mode. For example, the first delay information may correspond to at least one RRC procedure initiated during RRC idle mode (such as an RRC recovery procedure and / or an RRC establishment procedure).

[0270] Network nodes can include access nodes (e.g., gNBs, base stations, etc., as mentioned above regarding Figure 1 and...) Figure 2 (As described). Network nodes can correspond to Figure 20 The device. Network nodes may include core network nodes, such as AMF, OAM, etc.

[0271] During 1902, the device determines the first delay information based on the first signaling. For example, the device determines the first delay based on information indicating that the first delay information will be determined.

[0272] As mentioned above, in the example, Figure 19 The device can receive a corresponding trigger for providing first delay information to network nodes. Although not strictly necessary, Figure 19 The device can also signal to network nodes to notify them when the first delay information is available. This latter feature can reduce redundant communication because if a network node has not yet received information indicating that the first delay information is available, it can refrain from signaling the device to trigger the provision of the first delay information to the network node.

[0273] For example, the device may provide a second signaling to a network node, the second signaling including information indicating that the first delay information is available regarding at least one radio resource control procedure, obtaining a third signaling from the network node including a request for the first delay information, and providing the first delay information to the network node (e.g., based on the second signaling).

[0274] As mentioned above, Figure 19 The device can receive a trigger for providing both first and second delay information to network nodes.

[0275] For example, consider a situation similar to the previous example. Figure 19The device can obtain a fourth signaling from the network node, the fourth signaling including information indicating that second delay information will be determined regarding at least one radio resource control procedure when the device is in idle mode, and determine the second delay information based on the fourth signaling. Subsequently, the device can provide a fifth signaling to the network node, the fifth signaling including information indicating that at least one of the first and second delay information is available regarding at least one radio resource control procedure, obtain a sixth signaling from the network node including a request for the first and second delay information, and provide the first and second delay information to the network node.

[0276] It should be understood that these examples are network nodes from Figure 19 An example of a device pulling data, and Figure 19 The device can alternatively push latency information directly to network nodes without first receiving a trigger (e.g., a request) for such information.

[0277] The device can also provide a seventh signaling to the network node before receiving the first signaling. The seventh signaling includes information instructing the device on its ability to determine delay information regarding one or more radio resource control procedures, wherein the first signaling is based on the seventh signaling.

[0278] When the device is in connected mode, the first signaling can be obtained, and when the device switches from de-energized mode to connected mode, the delay information is subsequently determined.

[0279] Figure 20 A method that can be performed by an apparatus is illustrated. The apparatus may include network nodes. For example, the apparatus may include access nodes (such as those discussed in the examples above). As another example, the apparatus may include core network nodes, such as AMF and / or OAM.

[0280] During 2001, the device provides first signaling to the user equipment, the first signaling including information indicating that when the user equipment is in a reduced power mode, first delay information will be determined regarding at least one radio resource control procedure.

[0281] Similar to Figure 19 The above example, Figure 20 The device can provide a corresponding trigger for the first delay information, and / or provide triggers for both the first delay information and the second delay information. In other words, Figure 20 The apparatus can be used to extract data from a single RRC process and / or from multiple RRC processes. Figure 19 The device obtains latency information.

[0282] For example, the device can obtain a second signaling from the user equipment, the second signaling including information indicating that the first delay information is available regarding at least one radio resource control procedure, provide the user equipment with a third signaling including a request for the first delay information, and obtain the first delay information from the user equipment.

[0283] As another example, the device may provide a fourth signaling to the user equipment, the fourth signaling including information indicating that second delay information will be determined regarding at least one radio resource control procedure when the device is in idle mode. Subsequently, the device may obtain a fifth signaling from the user equipment, the fifth signaling including information indicating that at least one of the first and second delay information is available regarding the availability of at least one radio resource control procedure, provide the user equipment with a sixth signaling including a request for the first and second delay information, and obtain the first and second delay information from the user equipment.

[0284] It should be understood that these examples are network nodes from Figure 19 An example of a device pulling data, and Figure 19 The device can alternatively push latency information directly to network nodes without first receiving a trigger (e.g., a request) for such information. In this case, the network node may also not receive any prior information indicating that the first latency information is available (e.g., the latency information can arrive directly).

[0285] The device may obtain a seventh signaling from the user equipment before providing the first signaling. The seventh signaling includes information instructing the user equipment of its ability to determine delay information regarding one or more radio resource control procedures, wherein the first signaling is based on the seventh signaling.

[0286] Figure 20 The device can also be used with the following: Figure 21 Interact with the described device.

[0287] For example, the device can obtain an eighth signaling message from the core network node for minimizing drive tests. This eighth signaling message includes information requesting delay information regarding one or more radio resource control procedures that will be executed at the user equipment when it is in idle mode. Based on this eighth signaling message, the device provides a ninth signaling message to the core network node. The ninth signaling message may include first and / or second delay information, and / or information based on the first and / or second delay information.

[0288] The device can also determine the user equipment's capability to determine the first delay information based on the obtained eighth signaling, and provide the first signaling based on the determined user equipment capability.

[0289] The first signaling may include the recorded measurement configuration message.

[0290] when Figure 19 When the device enters RRC connection mode, it can provide network nodes with Figure 19 and Figure 20 The first delay information of the device. In other words, when Figure 19 When the device enters RRC connection mode, it can provide network nodes with the RRC idle mode procedure (e.g., in...). Figure 16 The first delay information corresponding to the RRC idle mode process initiated when the device is in RRC idle mode.

[0291] When the device is in connection mode with the user equipment, it can provide the first signaling to the user equipment.

[0292] It can also provide information such as... Figure 21 The device described. Figure 21 The devices may include core network devices, such as the core network devices described in the preceding paragraphs.

[0293] During 2101, Figure 21 The device provides network nodes with an eighth signaling message for minimizing drive tests. This eighth signaling message includes information requesting first delay information regarding one or more radio resource control procedures that will be executed at the user equipment when the user equipment is in idle mode. The network node can, as described above, provide... Figure 20 As described. User equipment can correspond to Figure 19 The device.

[0294] During 2102, the device obtains the ninth signaling from the network node based on the eighth signaling.

[0295] The following can be applied to Figures 16 to 21 Any one of them.

[0296] The information indicating which delay information will be determined includes information identifying which delay information will be determined by the device with respect to at least one radio resource control procedure. The information identifying which delay information will be determined can be, for example, the delay granularity configuration described above. For example, the information identifying which delay information will be determined can indicate whether delay information is to be provided with respect to a single RRC message, two or more RRC messages, and / or an RRC procedure. For example, the information identifying which delay information will be determined can specify (or otherwise identify) one or more RRC messages for which delay information is to be provided.

[0297] The information indicating the delay information to be determined may include information identifying a Radio Resource Control (RRC) procedure, for which the delay information will be determined during a reduced power mode. This information identifying one or more RRC procedures may correspond to the aforementioned delay measurement range. For example, this information may identify whether the first delay information corresponds to a single RRC procedure or multiple RRC procedures.

[0298] The radio resource control process for determining delay information during reduced energy modes may include at least one of a radio resource control establishment request process and a radio resource control recovery request process.

[0299] The first signaling can be included in the process of minimizing drive test signaling.

[0300] exist Figures 16 to 21 In all of the above examples, the first delay information may include information indicating the time taken to perform at least a portion of the radio resource control process.

[0301] It should be understood that the foregoing references to various network functions (e.g., AMF, OAM, etc.) may include means for performing at least some of the functions associated with these network functions. Furthermore, means including a network function may include a virtual network function instance of that network function.

[0302] It should be understood that the device may include or be coupled to other units or modules used in or for transmission and / or reception, such as a radio section or radio head. Although the device has been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0303] Note that while some embodiments have been described with respect to 5G networks, similar principles can be applied to other networks and communication systems. Therefore, although some embodiments have been described above by way of example with reference to certain example architectures for wireless networks, technologies, and standards, these embodiments can be applied to any other suitable form of communication system compared to those shown and described herein.

[0304] It should also be noted that although exemplary embodiments have been described above, several changes and modifications can be made to the disclosed solutions without departing from the scope of the invention.

[0305] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0306] Generally, various embodiments can be implemented in hardware or special-purpose circuitry systems, software, logic, or any combination thereof. Some aspects of this disclosure may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but this disclosure is not limited thereto. Although various aspects of this disclosure may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that these blocks, apparatuses, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware, or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0307] As used herein, the term "circuit system" may refer to one or more, or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor (including multiple digital signal processors, software, and multiple memories, which work together to enable a device (such as a mobile phone or server) to perform various functions), and (c) The hardware circuitry and / or processors (such as microprocessors or a portion thereof) that require software (e.g., firmware) for operation, but which may not be present when not required for operation.

[0308] This definition of circuit system applies to all uses of the term herein, including in any claim. As another example, as used herein, the term circuit system also covers only hardware circuitry or a processor (or processors) or a portion thereof and its accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0309] Embodiments of this disclosure can be implemented by computer software, which can be executed by a data processor of a mobile device (such as in a processor entity), by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets, and / or macros) can be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer-executable components that, when the program is run, are configured to execute the embodiments. The one or more computer-executable components may be at least one piece of software code or a portion thereof.

[0310] Furthermore, it should be noted that any box in the logical flow diagram may represent a program step, or an interconnected logic circuit, a box and function, or a combination of program steps and logic circuits, boxes and functions. Software may be stored on such physical media as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants CDs. The physical media is a non-transient medium.

[0311] As used herein, the term “non-transient” refers to the limitation of the medium itself (i.e., tangible, not signal-based), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0312] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, gate-level circuits, and processors based on multi-core processor architectures.

[0313] The various exemplary embodiments of this disclosure can be practiced in a variety of components, such as integrated circuit modules. The design of integrated circuits is a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready to be etched and formed on a semiconductor substrate.

[0314] The scope of protection sought by the various exemplary embodiments of this disclosure is set forth in the independent claims. Exemplary embodiments and features thereof (if any) described in this disclosure that are not within the scope of the independent claims are to be construed as examples useful for understanding the various exemplary embodiments of this disclosure.

[0315] The foregoing description has provided a complete and informative description of various exemplary embodiments of the present disclosure by way of non-limiting and illustrative examples. However, various modifications and adaptations may become apparent to those skilled in the art when read in conjunction with the accompanying drawings and claims, given the foregoing description. Nevertheless, all such and similar modifications to the present teachings will still fall within the various exemplary embodiments of the present disclosure as set forth in the claims. As a non-limiting and illustrative example, there are other exemplary embodiments that include combinations of one or more exemplary embodiments with any other exemplary embodiments discussed above.

Claims

1. A device for communication, comprising: At least one processor; as well as At least one memory, including code, which causes the device to execute when executed by the at least one processor: A first signaling is obtained from a network node, the first signaling including information indicating that when the device is in a reduced power mode, delay information will be determined with respect to at least one radio resource control process; as well as The delay information is determined based on the first signaling.

2. The apparatus of claim 1, wherein the apparatus is further configured to perform: A second signaling is provided to the network node, the second signaling including information indicating that the first delay information is available regarding at least one radio resource control procedure; Obtain third signaling from the network node, the third signaling including a request for the first delay information; and The first latency information is provided to the network node.

3. The apparatus according to any one of the preceding claims, wherein the apparatus is further caused to perform: A fourth signaling is obtained from the network node, the fourth signaling including information indicating that second delay information will be determined regarding at least one radio resource control procedure when the device is in connected mode; and The second delay information is determined based on the fourth signaling.

4. The apparatus of claim 3, wherein the apparatus is further caused to perform: The network node is provided with a fifth signaling message, the fifth signaling message including information indicating at least one of the first delay information and the second delay information regarding the availability of at least one radio resource control procedure; A sixth signaling is obtained from the network node, the sixth signaling including a request for the first delay information and the second delay information; as well as The first delay information and the second delay information are provided to the network node.

5. The apparatus according to claim 1 or 2, wherein the apparatus is further caused to perform: Before receiving the first signaling, a seventh signaling is provided to the network node, the seventh signaling including information indicative of the device’s ability to determine delay information regarding one or more radio resource control procedures, wherein the first signaling is based on the seventh signaling.

6. The apparatus of claim 1 or 2, wherein the first signaling is obtained when the apparatus is in a connected mode, and the delay information is subsequently determined when the apparatus switches from the reduced-power mode to the connected mode.

7. A communication apparatus, comprising: At least one processor; as well as At least one memory, including code, which causes the device to execute when executed by the at least one processor: Provide first signaling to the user equipment, the first signaling including information indicating that when the user equipment is in a reduced power mode, first delay information will be determined regarding at least one radio resource control procedure.

8. The apparatus of claim 7, wherein the apparatus is further caused to perform: A second signaling is obtained from the user equipment, the second signaling including information indicating that the first delay information is available with respect to at least one radio resource control procedure; Provide the user equipment with third signaling, the third signaling including a request for the first delay information; as well as The first delay information is obtained from the user equipment.

9. The apparatus according to any one of claims 7 to 8, wherein the apparatus is further caused to perform: A fourth signaling is provided to the user equipment, the fourth signaling including information indicating that second delay information will be determined regarding at least one radio resource control procedure when the device is in connected mode.

10. The apparatus of claim 9, wherein the apparatus is further caused to perform: A fifth signaling is obtained from the user equipment, the fifth signaling including information indicating at least one of the first delay information and the second delay information regarding the availability of at least one radio resource control procedure; The user equipment is provided with a sixth signaling message, the sixth signaling message including a request for the first delay information and the second delay information; and The first latency information and the second latency information are obtained from the user equipment.

11. The apparatus according to any one of claims 7 to 8, wherein the apparatus is further caused to perform: Before providing the first signaling, a seventh signaling is obtained from the user equipment, the seventh signaling including information instructing the user equipment for determining delay information regarding one or more radio resource control procedures, wherein the first signaling is based on the seventh signaling.

12. The apparatus of claim 11, wherein the apparatus is further caused to perform: Obtain an eighth signaling message from the core network node for minimizing drive tests. This eighth signaling message includes information requesting delay information regarding one or more radio resource control procedures that will be executed at the user equipment when the user equipment is in connected mode; and The ninth signaling is provided to the core network node based on the eighth signaling.

13. The apparatus of claim 12, wherein the apparatus is further caused to perform: Based on obtaining the eighth signaling, determine the user equipment's capability for determining the first delay information; and The first signaling is provided based on the determined capabilities of the user equipment.

14. The apparatus according to any one of claims 7 to 8, wherein the first signaling is provided to the user equipment when the apparatus is in a connection mode with the user equipment.

15. The apparatus of claim 1 or 7, wherein the information indicating which delay information will be determined includes information identifying which delay information will be determined by the apparatus with respect to at least one radio resource control procedure.

16. The apparatus of claim 1 or 7, wherein the information indicating the delay information to be determined includes information for identifying a radio resource control process, wherein the delay information is determined for the radio resource control process during the reduced power mode.

17. The apparatus of claim 16, wherein the delay information during the reduced power mode will be determined for at least one of the radio resource control process including a radio resource control establishment request process and a radio resource control recovery request process.

18. The apparatus of claim 1 or 7, wherein the first signaling is included in the process of minimizing drive test signaling.

19. The apparatus of claim 1 or 7, wherein the first signaling includes a recorded measurement configuration message.

20. A means for communication, comprising: At least one processor; as well as At least one memory, including code, which causes the device to execute when executed by the at least one processor: The network node is provided with an eighth signaling message for minimizing drive tests. The eighth signaling message includes information requesting first delay information about one or more radio resource control procedures that will be performed at the user equipment when the user equipment is in a reduced power mode. as well as The ninth signaling is obtained from the network node based on the eighth signaling.

21. The apparatus according to any one of claims 1, 7 and 20, wherein the reduced energy mode comprises at least one of an idle mode and an inactive mode.

22. The apparatus of any one of claims 1, 7, and 20, wherein the first delay information includes information indicating the time taken to perform at least a portion of the radio resource control process.

23. A method for communication, the method comprising: A first signaling is obtained from a network node, the first signaling including information indicating that when the device is in a reduced power mode, delay information will be determined with respect to at least one radio resource control process; as well as The delay information is determined based on the first signaling.

24. A method for communication, the method comprising: Provide first signaling to the user equipment, the first signaling including information indicating that when the user equipment is in a reduced power mode, first delay information will be determined regarding at least one radio resource control procedure.

25. A method for communication, the method comprising: The network node is provided with an eighth signaling message for minimizing drive tests. The eighth signaling message includes information requesting first delay information about one or more radio resource control procedures that will be performed at the user equipment when the user equipment is in a reduced power mode. as well as The ninth signaling is obtained from the network node based on the eighth signaling.

26. A computer program product comprising instructions that, when executed by a device, cause the device to perform: Obtain first signaling from a network node, the first signaling including information indicating that when the device is in a low-power mode, delay information will be determined with respect to at least one radio resource control procedure; and The delay information is determined based on the first signaling.

27. A computer program product comprising instructions that, when executed by a device, cause the device to perform: Provide first signaling to the user equipment, the first signaling including information indicating that when the user equipment is in a reduced power mode, first delay information will be determined regarding at least one radio resource control procedure.

28. A computer program product comprising instructions that, when executed by a device, cause the device to perform: The network node is provided with an eighth signaling message for minimizing drive tests. This eighth signaling message includes information requesting first delay information regarding one or more radio resource control procedures that will be executed at the user equipment when the user equipment is in a reduced-power mode; and The ninth signaling is obtained from the network node based on the eighth signaling.

Images