QoE continuity in RAT handover processing within 5GC

Abstract

Embodiments of this disclosure relate to terminal devices, methods, apparatus and computer-readable storage media that realize QoE continuity in inter-RAT handover processing within a 5GC. In some embodiments, a first layer of the terminal device receives a mobility command from a source terminal device. The first layer can provide an AT command to a higher second layer of the terminal device instructing it to release at least one configured QoE measurement and associated RRC ID. The second layer then releases at least one configured QoE measurement and associated RRC ID. Thus, QoE continuity is maintained and communication between the terminal device and the target network device is guaranteed during inter-RAT handover from NR to LTE.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and in particular, to a terminal device, method, apparatus, and computer-readable storage medium for realizing the continuity of quality of experience (QoE) in intra-5th generation core (intra-5GC) radio access technology (RAT) inter-RAT handover processing.

Background Art

[0002] Work items related to QoE improvement are in progress in the 3rd Generation Partnership Project (3GPP (registered trademark)) Release 18 (Rel-18). One of the objectives of this work item includes "consideration of the continuity of conventional QoE measurement jobs in streaming for Internet Protocol Multimedia Subsystem (MTSI) services and multimedia telephone services in intra-5GC RAT-to-RAT handover processing".

[0003] However, QoE settings supported by various radio access technologies (RATs) are different. Therefore, further consideration is needed on how to support the adaptation of settings.

Summary of the Invention

[0004] Generally, embodiments of the present disclosure provide a solution for QoE continuity in intra-5GC RAT-to-RAT handover processing.

[0005] In a first embodiment, a terminal device is provided. The terminal device comprises at least one processor and at least one memory which stores instructions that, when executed by the at least one processor, cause the terminal device to perform at least: receive a mobility command from a first network device at a first layer of the terminal device; provide an attention (AT) command associated with the mobility command from the first layer of the terminal device to a second layer of the terminal device, the AT command notifying the second layer to release at least one configured quality-of-effect (QoE) measurement and associated radio resource control (RRC) identifier (ID), the second layer being a higher layer than the first layer; and, at the second layer of the terminal device, release at least one configured QoE measurement and associated RRC ID based on the AT command.

[0006] In a second embodiment, a method is provided that is performed by a terminal device. This method includes: receiving a mobility command from a first network device at the first layer of the terminal device; providing an AT command associated with the mobility command from the first layer of the terminal device to the second layer of the terminal device, wherein the AT command notifies the second layer to release at least one configured QoE measurement and associated RRC ID, and the second layer is a higher layer than the first layer; and releasing at least one configured QoE measurement and associated RRC ID at the second layer of the terminal device based on the AT command.

[0007] In a third embodiment, an apparatus is provided. The apparatus comprises, in the first layer of a terminal device, means for receiving a mobility command from a first network device; means for providing an AT command associated with the mobility command from the first layer of the terminal device to the second layer of the terminal device, wherein the AT command notifies the second layer to release at least one configured QoE measurement and associated RRC ID, and the second layer is a higher layer than the first layer; and means in the second layer of the terminal device to release at least one configured QoE measurement and associated RRC ID based on the AT command.

[0008] In a fourth embodiment, a terminal device is provided. The terminal device comprises: a receiving circuit configured to receive mobility commands from a first network device; a providing circuit configured to provide AT commands associated with mobility commands from a first layer of the terminal device to a second layer of the terminal device, the AT commands instructing the second layer to release at least one configured QoE measurement and associated RRC ID, the second layer being a higher layer than the first layer; and a release circuit configured in the second layer of the terminal device to release at least one configured QoE measurement and associated RRC ID based on the AT command.

[0009] In a fifth embodiment, a non-temporary computer-readable medium is provided that includes program instructions for performing at least the method of the second embodiment.

[0010] In a sixth embodiment, a computer program is provided that, when executed by the apparatus, includes instructions causing the apparatus to perform at least the method of the second embodiment.

[0011] It should be understood that this abstract does not identify any important or essential features of the embodiments described herein, nor is it intended to limit the scope of this specification. Other features of this specification will be readily apparent through the following description. [Brief explanation of the drawing]

[0012] Several embodiments will be described with reference to the attached drawings. [Figure 1] Figure 1 shows an example of a handover from NR to LTE. [Figure 2] Figure 2 shows an example of a network environment in which several embodiments of this disclosure may be implemented. [Figure 3] Figure 3 shows an example process flow according to some embodiments of this disclosure. [Figure 4] Figure 4 shows an example process flow of an NR to LTE handover according to some embodiments of this disclosure. [Figure 5] Figure 5 shows a flowchart of a method implemented in a terminal device according to some embodiments of the present disclosure. [Figure 6] Figure 6 shows a simplified block diagram of an apparatus suitable for implementing some embodiments of the present disclosure. [Figure 7] Figure 7 shows a block diagram of an example of a computer-readable medium according to some embodiments of the present disclosure. Throughout the drawings, the same or similar reference numerals indicate the same or similar components. [Modes for carrying out the invention]

[0013] The principles of this specification will be explained with reference to several examples. These examples are not intended to limit the scope of this specification, but are provided solely for illustrative purposes and to assist those skilled in the art in understanding and implementing this specification. The disclosures described herein can be implemented in various ways other than those described below.

[0014] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those normally understood by a person ordinary in the art to which this disclosure belongs.

[0015] In this specification, descriptions such as “one embodiment,” “embodiment,” and “exemplary embodiment” indicate that the described embodiment may include a particular function, structure, or feature, but not all embodiments are required to include such a particular function, structure, or feature. Furthermore, these expressions do not necessarily refer to the same embodiment. Also, if a particular function, structure, or characteristic is described in relation to an embodiment, it should be understood that any influence of that function, structure, or characteristic in relation to other embodiments, whether explicitly stated or not, is within the knowledge of those skilled in the art.

[0016] While terms such as "first" and "second" may be used to describe various elements, these elements are not limited by these terms. These terms are simply used to distinguish elements. For example, referring to the first element as the second element, or similarly referring to the second element as the first element, does not deviate from the scope of the examples. In this specification, the term "and / or" encompasses any combination of one or more of the terms described.

[0017] The terms used herein are intended solely to describe specific embodiments and are not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are intended to include the plural forms as well. Furthermore, it should be understood that the terms “equip,” “equip,” “have,” “possess,” “include,” and / or “include” in this specification identify the presence of the described features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. In this specification, where “at least one of the following: <list of two or more elements>” and “at least one of the following: <list of two or more elements>” and similar expressions, if the lists of two or more elements are connected by “and” or “or,” it means at least one of the elements, at least two or more elements, or at least all of the elements.

[0018] In this application, the term "circuit" is defined as follows: (a) Hardware-only circuit implementation (such as implementation using only analog and / or digital circuits), (b) A combination of hardware circuitry and software, for example (where applicable), (i) combinations of analog and / or digital hardware circuits and software / firmware, (ii) A system in which a part of the hardware processor and software (including a digital signal processor), software, and memory work together to enable a device such as a mobile phone or server to perform various functions. (c) Hardware circuits and / or processors (e.g., microprocessors or parts of microprocessors) that require software (e.g., firmware) for operation, where the software may not be present if it is not necessary for operation. This may refer to one or more of these, or all of them.

[0019] The definition of this circuit applies to all uses of this term in this application, i.e., its use in all claims. Further by way of example, the term "circuit" as used in this application includes merely a hardware circuit or a processor (or processors), or an implementation of a hardware circuit or part of a processor together with its accompanying software and / or firmware. The term "circuit" includes, for example, a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network, or other computing systems, when applicable to an element of a particular claim.

[0020] As used herein, the term "communication network" refers to an evolved universal terrestrial radio access network (E-UTRAN), long term evolution (LTE), LTE-Advanced (LTE-A), New Radio (NR), wideband code division multiple access (WCDMA (registered trademark)), high speed packet access (HSPA), narrowband Internet of Things (NB-IoT), etc. Further, communications in a communication network include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), sixth generation (6G) communication protocols, and / or other protocols known currently or developed in the future. Embodiments of the present disclosure are applicable to various communication systems. Considering the rapid development of communication technologies, there will naturally be future communication technologies and systems in which the present disclosure will be embodied. The scope of the present disclosure is not limited to only the aforementioned systems.

[0021] In this specification, the term "network device" refers to a node within a communication network, through which a terminal device accesses the network and receives services therefrom. The network device may refer to, for example, a base station (BS) or an access point (AP), Node B (NodeB or NB), evolved Node B (eNodeB or eNB), new radio (NR) NB (also referred to as gNB), remote radio unit (RRU), radio header (RH), remote radio head (RRH), integrated access backhaul (IAB) node, relay, low-power nodes such as femto and pico, etc., which may vary depending on the terms and technologies applied.

[0022] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example only, the terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), mobile subscriber station, mobile station (MS), access terminal (AT). Terminal devices include mobile phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminals, PDAs, portable computers, desktop computers, imaging terminals such as digital cameras, game terminals, music storage and playback devices, in-vehicle wireless terminals, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, machine-to-machine communication (MTC) devices, watches and other wearables, head-mounted displays (HMD), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", "UE" may be used interchangeably.

[0023] In this specification, the term "configured QoE measurement" may also be referred to as QoE configuration container, QoE configuration, configured QoE container, etc., but this specification is not limited to these terms.

[0024] As mentioned above, the continuity of QoE measurement during intra-5GC inter-RAT handover processing is being investigated. However, the QoE settings supported by E-UTRAN and NR are different. Therefore, in order to support the continuity of QoE measurement during intra-5GC inter-RAT handover, it is necessary to support configuration adaptation.

[0025] For example, the settings for application layer measurement in LTE are defined as follows: [Table 1]

[0026] LTE QoE settings can support two service types: "qoe" for streaming and "qoemtsi" for MTSI. The field "measConfigAppLayerContainer" may contain application layer measurement settings, but the UE can only support a maximum of one application layer measurement setting, regardless of the service type. In other words, only one QoE setting can be configured in LTE.

[0027] For example, the settings for application layer measurement in NR are defined as follows: [Table 2]

[0028] NR's QoE settings support three service types: "Streaming," "MTSI," and "VR," and NR allows you to configure up to 16 QoE settings.

[0029] In handovers (HO) between LTE / 5GC and NR, it has been agreed that QoE continuity is performed at the access stratum (AS) layer, not the application layer (AL). This means that the continuity of QoE measurement at the application layer may not be guaranteed. Two principles regarding QoE continuity have been agreed upon and will be further considered. In a HO transition from NR to LTE / 5GC, the UE can only maintain and continue measurements for one setting for the service types supported by LTE. In a HO from LTE / 5GC to NR, the UE can only maintain and continue measurements for the ongoing configuration of service types supported by NR.

[0030] LTE is based on the E-UTRAN RAT, and NR is based on the NR RAT. The following applies to RAT handover from NR to LTE. The source RAT sets up the measurement and reporting of the target RAT. The source RAT decides to begin preparation and provides the target RAT with the necessary information in the format requested by the target RAT. Before the handover, the target RAT prepares the radio resources. The RRC reconfiguration message from the target RAT is delivered to the source RAT via a transparent container and passed by the source RAT to the UE within a handover command. Sequential and lossless handovers are not supported. Security procedures for handover to E-UTRA / EPC must follow the E-UTRA handover procedures.

[0031] Figure 1 shows an example of process 100 illustrating an example of a handover from NR to LTE. In process 110, the source gNB can configure multiple QoE configuration containers and associated RRC IDs. For example, an RRC reconfiguration message is sent from the source gNB to the NR AS layer of the UE, and this message includes the QoE1 configuration container and associated RRC ID1, as well as the QoE2 configuration container and associated RRC ID2.

[0032] In step 120, each NR QoE configuration container and its associated short RRC ID (measConfigAppLayerId) are simultaneously sent from the UE NR AS layer to the UE AL layer.

[0033] In NR QoE reporting, each QoE report data and RRC ID (to identify each NR QoE configuration within the UE AS) are sent back from the UE AL to the UE AS and then further transmitted to the network.

[0034] At step 130, the measurement report is sent from the UE to the source gNB, triggering a RAT handover.

[0035] In step 140, the source gNB selects one of the configured QoE measurements and sends it to the 5GC along with LTE handover readiness information including the selected QoE setting. For example, the selection of one QoE measurement is performed down to the network implementation level.

[0036] At step 150, the 5GC sends a handover request to the target eNB, and at step 160, the target eNB sends a handover request acknowledgment (ACK) to the 5GC. This allows the selected QoE configuration (selected by the source gNB) to be sent to the target eNB.

[0037] In step 170, 5GC sends a handover command to the source gNB. This allows the source gNB to receive LTE RRC reconfiguration with QoE settings (selected by the source gNB) from the target eNB.

[0038] In step 180, the source gNB sends a MobilityFromNRCommand message to the UE, which includes an embedded container containing an LTE RRC connection reconfiguration.

[0039] However, LTE QoE does not have the concept of a short RRC ID, and the QoE configuration container received from the LTE network is sent only once by the UE LTE AS to the UE AL. Furthermore, the QoE configuration container is common to the UE AL whether it is received from the UE LTE AS or the UE NR AS.

[0040] The 180 MobilityFromNRCommand message delivers a targetRAT-Message container (LTE RRC connection reconfiguration) containing the LTE measConfigAppLayer to the UE, where measConfigAppLayer-r15 is "Need ON" and is defined as follows: [Table 3]

[0041] "Need ON" is used only in downlinks and indicates that this field is optional for the signal. If the UE receives the message and this field is not present, the UE takes no action and continues to use the existing value (and / or associated function) where applicable.

[0042] In a specific scenario involving an inter-RAT handover from NR to LTE, multiple QoE measurements (e.g., QoE1 and QoE2) are performed at the UE AL before the HO.

[0043] If the source gNB selects a QoE1 setting for the target eNB and the target eNB accepts that selection (see Figure 1), the target eNB can use the "Choice-setup" of LTE measConfigAppLayer-r15 to configure the QoE1 setting to the UE via the NR MobilityFromNRCommand message. The UE LTE AS decrypts the QoE1 measConfigAppLayerContainer, taking the serviceType into consideration, and forwards it to the UE AL. However, if the related service continues after the handover, the QoE2 measurement pre-configured in the NR will continue to be performed in the UE AL, and as a result, the UE AL may send the NR's QoE2 report data, along with the related QoE2 RRC ID, to the UE LTE AS (the related service may still be running on the LTE side), which could lead to undefined behavior for the UE in the LTE AS.

[0044] If a source gNB selects the QoE1 setting for a target eNB, and the target eNB rejects that selection (for example, if it is not the target eNB's preferred setting), the target eNB can use the "Choice-release" method of LTEmeasConfigAppLayer-r15 to notify the UE AL to clear the saved AL QoE measurement settings. However, the LTE specification has an ambiguity in that it is not clear which QoE measurements the UE AL should release.

[0045] If the source gNB selects the QoE1 setting for the target eNB, and the target eNB does not support the QoE1 setting (for example, does not understand part of the setting), the target eNB may not have measConfigAppLayer-r15 in the LTE RRC connectivity reconfiguration container to the UE. Based on the definition of "Need ON", the UE LTE AS does nothing to the UE AL. Because there is no notification from the UE LTE AS to the UE AL, both QoE1 and QoE2, which were pre-configured in NR, will continue to operate on the UE AL, especially if the relevant services continue after the handover.

[0046] Therefore, further investigation is needed regarding the behavior during RAT handover processing.

[0047] Embodiments of this disclosure provide a solution for QoE continuity in inter-RAT handover processing within a 5GC. In some embodiments, Layer 1 of a terminal device may receive a mobility command from a source terminal device. Layer 1 can provide an AT command to the upper Layer 2 of the terminal device instructing it to release at least one configured QoE measurement and associated RRC ID. This allows Layer 2 to release at least one configured QoE measurement and associated RRC ID. Thus, QoE continuity is maintained and communication between the terminal device and the target network device is guaranteed during inter-RAT handover from NR to LTE. The principles of this disclosure and some embodiments are described below in detail with reference to the accompanying drawings.

[0048] Figure 2 shows an example of a network environment 200 in which several embodiments of this disclosure may be implemented. The environment 200, which may be part of a communication network, includes terminal equipment 210, a first network device 220, a second network device 230, and a core network device 240. The network environment 200 may also be called a network system, communication environment, communication network, communication system, etc., but this disclosure is not limited to these terms.

[0049] The environment 200 may include any appropriate number of devices and cells. In the environment 200, the first network device 220 can provide services to the terminal device 210, and the first network device 220 and the terminal device 210 can communicate data and control information with each other. In some embodiments, the first network device 220 and the terminal device 210 can communicate via direct link / channel.

[0050] In environment 200, the link from the first network device 220 to the terminal device 210 is called a downlink (DL), and the link from the terminal device 210 to the first network device 220 is called an uplink (UL). In the downlink, the first network device 220 is a transmitting (TX) device (or transmitter), and the terminal device 210 is a receiving (RX) device (or receiver). In the uplink, the terminal device 210 is a transmitting (TX) device (or transmitter), and the first network device 220 is a receiving (RX) device (or receiver). It should be understood that the first network device 220 may provide one or more service cells. In some embodiments, the first network device 220 may provide multiple cells.

[0051] In the event of a handover, terminal device 210 may be handed over from first network device 220 to second network device 230. In some embodiments, the handover process may be triggered by the mobility of terminal device 210, but this disclosure is not limited to this.

[0052] The core network device 240 is implemented as an optional function within the core network, and for convenience of explanation, the core network device 240 may also be referred to as 5GC.

[0053] Communication in network environment 200 is implemented according to an appropriate communication protocol, which includes cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G). Furthermore, appropriate wireless communication technologies can be used for communication, which include, but are not limited to, code-division multiple access (CDMA), frequency-division multiple access (FDMA), time-division multiple access (TDMA), and frequency-division duplexing (FDD). In addition, any appropriate wireless communication technology can be used for communication, which includes, but are not limited to, code-division multiple access (CDMA), frequency-division multiple access (FDMA), time-division multiple access (TDMA), frequency-division duplexing (FDD), time-division duplexing (TDD), multiple-input multiple-output (MIMO), orthogonal frequency-division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and other technologies currently known or to be developed in the future.

[0054] In certain embodiments, the first network device 220 may be associated with NR or a future RAT, for example, the first network device 220 may be a gNB. In certain embodiments, the second network device 230 may be associated with LTE or an earlier RAT, for example, the second network device 230 may be an eNB. For convenience of explanation, some of the following embodiments will be described using examples of gNBs and eNBs. However, these embodiments are merely illustrative and not limiting, and the first network device 220 and the second network device 230 may take other forms.

[0055] The number, connectivity, and types of devices shown in Figure 2 (i.e., terminal device 210, first network device 220, second network device 230) are for illustrative purposes only and should not be interpreted as limiting in any way. For example, environment 200 may include any number of devices suitable for implementing embodiments of the present disclosure. For example, while terminal device 210 is shown as a mobile phone in Figure 2, terminal device 210 may be any type of user device.

[0056] Figure 3 shows an example of a process flow 300 according to some embodiments of this disclosure. For ease of explanation, the process flow 300 will be described with reference to Figure 2. The process flow 300 involves a terminal device 210 and a first network device 220. Although the process flow 300 is described in the network environment 200 of Figure 2, it should be understood that this process flow is similarly applicable to other communication scenarios.

[0057] As shown in Figure 3, the terminal device 210 may include a first layer 211 and a second layer 212, where the second layer 212 is a layer above the first layer 211. In some embodiments, the first layer 211 of the terminal device 210 is the access stratum (AS) layer, and the second layer 212 of the terminal device 210 is the application layer (AL). In other embodiments, the first layer 211 and the second layer 212 may be implemented as other layers, and this disclosure is not limited thereto.

[0058] In some embodiments, the first network device 220 may be a network device associated with an NR such as a gNB. In other embodiments, the first network device 220 may be associated with a future network, and is not limited herein.

[0059] The first network device 220 transmits a mobility command 312 to the terminal device 210. On the other side of the communication, the terminal device 210 receives the mobility command 312, specifically, the first layer 211 can receive the mobility command 312.

[0060] In some examples, mobility commands 312 are transmitted during a handover process, for example, from a first network device 220 to a second network device 230. For example, the first network device 220 may be called the source network device, and the second network device 230 may be called the target network device. In some embodiments, the second network device may be an LTE-associated network device such as an eNB.

[0061] In some embodiments, if the first network device 220 is associated with an NR such as a gNB, the mobility command 312 may be a MobilityFromNRCommand. In some examples, the mobility command 312 may include a QoE configuration container supported by a second network device, i.e., the target network device. In some examples, the mobility command 312 may include RRC connection reconfiguration information associated with the second network device, i.e., the target network device.

[0062] The first layer 211 of the terminal device 210 provides the AT command 322 to the second layer 212. Thus, the second layer 212 receives the AT command 322. In some examples, the AT command 322 may be associated with a mobility command 312.

[0063] In some examples, AT command 322 may be used to notify Layer 2 212 to release at least one configured QoE measurement and associated RRC ID. For example, if multiple QoE measurements and associated RRC IDs are configured by, for example, the first network device 220, AT command 322 can notify Layer 2 212 to release multiple QoE measurements and associated RRC IDs. In other examples, AT command 322 may notify Layer 2 to release all configured QoE measurements and associated RRC IDs. In other examples, AT command 322 may notify Layer 2 to release all RRC IDs and configured QoE measurements except for one QoE measurement, which is associated with one QoE container and / or one service type.

[0064] In some examples, each configured QoE measurement may have an associated RRC ID, while different configured QoE measurements may have different RRC IDs. In some examples, RRC IDs may be used to distinguish or identify multiple QoE measurements, i.e., multiple QoE configuration containers.

[0065] The second layer 212 of the terminal device 210 releases at least one configured QoE measurement and its associated RRC ID based on the AT command 322. In some embodiments, the at least one configured QoE measurement and its associated RRC ID may include all QoE measurements and their associated RRC IDs configured by the first network device 220. In some embodiments, the second layer 212 may cease providing reporting data to the first layer 211. In other examples, the second layer 212 of the terminal device 210 may release all RRC IDs and configured QoE measurements except for one QoE measurement, which is associated with one QoE container and / or one service type. In other words, the second layer 212 may retain one QoE measurement and release all other QoE measurements and all RRC IDs.

[0066] The first layer 211 may include a first portion associated with a first network device 220 (i.e., a source network device) and a second portion associated with a second network device (i.e., a target network device). In some embodiments, the first portion of the first layer may be represented as an NR AS layer, and the second portion of the first layer may be represented as an LTE AS layer.

[0067] In some embodiments, upon receiving a mobility command 312, the first part of the first layer can provide an AT command 322 to the second layer. Thus, when the first part of the first layer (e.g., the NR AS layer) receives a mobility command 312 from the first network device 220, it can trigger the release of the QoE setting in the second layer 212. For example, the AT command 322 may be a newly defined attention command, such as a release command.

[0068] In some cases, layer 212 may stop reporting QoE measurements to layer 1211, thereby releasing all QoE measurements currently running in layer 212 and associated RRC IDs.

[0069] In some embodiments, the terminal device 210 can further perform RAT handover processing from the first network device 220 to the second network device 230. For example, the terminal device 210 can connect to the second network device 230.

[0070] For example, if the handover is successful, the second part of the first layer 211 may further transfer the QoE configuration container associated with the second network device 230 to the second layer 212, which may further initiate a new QoE measurement according to the QoE configuration container associated with the second network device 230. If no QoE configuration container has been transferred by the second part of the first layer 211, no QoE measurement is performed at the second layer of the terminal device 210.

[0071] For example, if a handover fails, terminal device 210 may return to the first network device 220. Please understand that if a handover fails, the QoE settings will not remain on Layer 2 212.

[0072] In other embodiments, after successfully decoding the RRC connection reset information associated with the second network device 230, or after connecting to the second network device 230, the second part of the first layer can provide an AT command 322 to the second layer. For example, when the second part of the first layer (such as the LTE AS layer) receives the LTE RRC connection reset embedded in the mobility command, it can trigger the release of the QoE setting in the second layer 212. For example, the second part of the first layer can obtain the RRC connection reset information associated with the second network device 230 by decoding the mobility command 312.

[0073] In some examples, the first layer 211 (e.g., including the first and second parts) may discard the QoE reporting data obtained from the second layer 212. In addition, or alternatively, the first part of the first layer may notify the second layer to stop QoE measurement and / or QoE reporting, for example, upon receiving a mobility command 312. For example, a newly defined AT command may be used to notify the second layer to stop QoE measurement and / or QoE reporting. In some examples, the second layer 212 may cease providing QoE reporting data to the first part of the first layer. In some examples, at least one QoE measurement and its associated RRC ID may be retained by the second layer until an AT command 322 is received.

[0074] In some examples, the AT command 322 is provided by the second part of Layer 1 (e.g., LTE AS) after the decoding of the RRC connection reconfiguration or after the successful RACH access procedure to the second network device 230. In addition, or alternatively, the second part of Layer 1 211 may further forward the QoE configuration container associated with the second network device 230 to Layer 2 212.

[0075] In some examples, AT command 322 may be a newly defined attention command, such as a release command. In other examples, AT command 322 may be an existing AT command. Also in other examples, AT command 322 may be implicitly indicated by other messages. For example, if the handover is successful, the second part of Layer 1 may provide an existing command containing the QoE settings associated with the second network device 230, which notifies Layer 2 to release at least one configured QoE measurement and associated RRC ID. Thus, no new AT command is required for release, and the command to release at least one configured QoE measurement and associated RRC ID may be integrated with the QoE settings container associated with the second network device 230, for example, the second part of Layer 1 may be aware that the QoE settings container exists within the LTE RRC connection reconfiguration container received by “Selection Settings”.

[0076] Furthermore, the second layer 212 can initiate a new QoE measurement according to the QoE configuration container associated with the second network device 230. If there is no QoE configuration container transferred by the second part of the first layer 211, no QoE measurement is performed in the second layer of the terminal device 210.

[0077] In other examples, if the handover fails, the AT command 322 is not provided by the second part of Layer 1. The terminal device 210 can reconnect to the first network device 220. In some embodiments, the first part of Layer 1 may notify Layer 2 to recover a previously stopped QoE measurement or QoE report. In other words, if the handover fails, the second part of Layer 1 does not need to provide the AT command 322 to Layer 2, and at least one configured QoE measurement and associated RRC ID may be further used by Layer 2. In some examples, the command used to notify Layer 2 to recover a stopped QoE measurement or QoE report may be a newly defined recovery command.

[0078] In certain implementations, upon receiving a mobility command 312, the first layer 211 may send a first AT command to the second layer 212, which is used to notify the second layer 212 to stop QoE measurements and QoE reporting. If the handover is successful, the first layer 211 may send a second AT command to the second layer 212 after connecting to the target network device, which may notify the second layer 212 to release at least one (e.g., all) configured QoE measurements and associated RRC IDs. Furthermore, the first layer 211 may send a third AT command to the second layer 212, which contains the QoE configuration container associated with the target network device. In some examples, the second and third AT commands may be combined into a single AT command, for example, the third AT command may be used to notify Layer 2 212 to release at least one configured QoE measurement and associated RRC ID, the third AT command containing the QoE configuration container associated with the target network device, and the second AT command is absent. If the handover fails, Layer 1 211 may send a fourth AT command to Layer 2 212, which may notify Layer 2 212 to recover the previously stopped (stopped based on the first AT command) QoE measurement and QoE report.

[0079] Figure 4 shows an example of a process flow 400 for an NR to LTE handover according to some embodiments of this disclosure. The process flow 400 includes steps 110-180 shown in Figure 1, but will not be repeated for the sake of simplicity.

[0080] To release at least one configured QoE measurement running in UE AL and associated RRC ID, two different solutions are possible, as indicated by 410 and 420, respectively.

[0081] In Option 1, as shown in block 410, the UE NR AS (for example, upon receiving MobilityFromNRCommand) can provide an AT command to the UE AL, and in 411, all configured QoE measurements and associated RRC IDs can be released. Furthermore, the UE may perform a RACH procedure to obtain RACH access to the LTE cells of the target LTE eNB, for example, in 412. In 413, the UE LTE AS can provide other AT commands, including the QoE configuration container of the target LTE eNB.

[0082] The embodiments described herein may have some effect on the current specification. For example, based on the various embodiments described herein, the current specification may be updated as follows (underlined): Regarding the reception of MobilityFromNRCommand by the UE in section 5.4.3.3 of TS38.331, it may be updated as follows: [Table 4]

[0083] In Option 1, as shown in block 420, after receiving MobilityFromNRCommand, the UE may, at 421, perform a RACH procedure, for example, to perform RACH access to the LTE cell of the target LTE eNB. After receiving the LTE RRC connection reconfiguration message, the UE LTE AS may provide an AT command to the UE AL, releasing all configured QoE measurements and associated RRC IDs at 422. At 423, the UE LTE AS may provide other AT commands, including the QoE configuration container for the target LTE eNB. In some examples, steps 422 and 423 may be combined into a single step, i.e., a single AT command.

[0084] The embodiments described herein may have some effect on the current specification. For example, based on the various embodiments described herein, the current specification may be updated as follows (underlined): Regarding the reception of RRCConnectionReconfiguration by the UE in section 5.4.2.3 of TS36.331, it may be updated as follows: [Table 5]

[0085] Other settings in section 5.3.10.9 of TS36.331 may be updated as follows: [Table 6]

[0086] It should be understood that AT commands 411 or 422 are used to release all QoE configuration containers and associated RRC IDs. However, this is for illustrative purposes only and is not limiting in any way. For example, AT command 411 may be used to release only some of all QoE configuration containers and associated RRC IDs, or, for example, only one QoE configuration container and associated RRC ID, and this disclosure is not limited to this.

[0087] Process flow 400 includes operations 110-180, in which the QoE configuration container selected by the source gNB is accepted by the target eNB. However, in some other cases, the target eNB may reject or ignore the QoE configuration container selected by the source gNB, and this specification is not limited to this.

[0088] According to some of the embodiments described above, the continuity of QoE during RAT handover from NR to LTE can be maintained, and ambiguity in the current procedure can be eliminated by defining clear new UE behaviors.

[0089] Figure 5 shows a flowchart of Method 500 as implemented in a terminal device according to some embodiments of the present disclosure. For illustrative purposes, Method 500 will be described in terms of a terminal device 210 with reference to Figure 2.

[0090] In block 510, the first layer of the terminal device 210 receives a mobility command from the first network device. In 520, the first layer of the terminal device provides the second layer of the terminal device with an AT command associated with the mobility command, and the AT command notifies the second layer to release at least one configured QoE measurement and associated RRC ID, with the second layer being a higher layer than the first layer. In 530, the second layer of the terminal device releases at least one configured QoE measurement and associated RRC ID based on the AT command.

[0091] In some embodiments, the first part of the first layer of the terminal device, upon receiving a mobility command, provides an AT command to the second layer of the terminal device, and the first part of the first layer is associated with the first network device.

[0092] In some embodiments, the second part of the first layer of the terminal device provides AT commands to the second layer of the terminal device after successfully decoding RRC connection reconfiguration information associated with the second network device, or after connecting to the second network device, and the second part of the first layer is associated with the second network device.

[0093] In some embodiments, the first layer of the terminal device discards the QoE report data acquired from the second layer.

[0094] In some embodiments, the first part of the first layer of the terminal device, upon receiving a mobility command, notifies the second layer to stop at least one of either QoE measurement or QoE reporting.

[0095] In some embodiments, the AT command includes a QoE configuration container configured by the second network device.

[0096] In some embodiments, a terminal device, for example, a second part of the first layer of the terminal device, obtains RRC connection reconfiguration information associated with a second network device by decoding mobility commands.

[0097] In some embodiments, the second network device is a Long-Term Evolution (LTE) network device. In some embodiments, the first network device is a New Radio (NR) network device.

[0098] In some embodiments, the terminal device performs a wireless access technology (RAT) handover process from the first network device to the second network device.

[0099] In some embodiments, at least one configured QoE measurement and associated RRC ID includes all configured QoE measurements and associated RRC IDs configured by the first network device.

[0100] In some embodiments, the first layer of the terminal device is the access stratum (AS) layer, and the second layer of the terminal device is the application layer.

[0101] In some embodiments, an apparatus capable of performing Method 500 (e.g., a terminal device 210) may include means for performing each step of Method 500. These means can be implemented in any suitable form. For example, these means may be implemented as a circuit or a software module.

[0102] In some embodiments, the device comprises, at the first layer of the terminal device, means for receiving mobility commands from a first network device; means for providing attention (AT) commands associated with the mobility commands from the first layer of the terminal device to the second layer of the terminal device, wherein the AT command notifies the second layer to release at least one configured quality-of-effect (QoE) measurement and associated radio resource control (RRC) identifier (ID), and the second layer is a higher layer than the first layer; and means at the second layer of the terminal device to release at least one configured QoE measurement and associated RRC ID based on the AT command.

[0103] In some embodiments, the device comprises means for providing AT commands from a first portion of the first layer to a second layer upon receiving a mobility command, wherein the first portion of the first layer is associated with a first network device.

[0104] In some embodiments, the device includes means for providing AT commands from the second portion of the first layer to the second layer after successfully decoding RRC connection reconfiguration information associated with the second network device, or after connecting to the second network device, wherein the second portion of the first layer is associated with the second network device.

[0105] In some embodiments, the device includes means in the first layer of the terminal device for discarding QoE report data acquired from the second layer.

[0106] In some embodiments, the device includes means for notifying the second layer from a first portion of the first layer to stop at least one of QoE measurement or QoE reporting upon receiving a mobility command.

[0107] In some embodiments, the AT command includes a QoE configuration container configured by the second network device.

[0108] In some embodiments, the device includes means for obtaining RRC connection reconfiguration information associated with a second network device by decoding mobility commands.

[0109] In some embodiments, the second network device is an LTE network device such as an eNB. In some embodiments, the first network device is an NR network device such as a gNB.

[0110] In some embodiments, the device includes means for performing RAT handover processing from a first network device to a second network device.

[0111] In some embodiments, at least one configured QoE measurement and associated RRC ID includes all configured QoE measurements and associated RRC IDs configured by the first network device.

[0112] In some embodiments, the first layer of the terminal device is the access stratum (AS) layer, and the second layer of the terminal device is the application layer.

[0113] Figure 6 shows a simplified block diagram of a device 600 suitable for implementing some embodiments of the present disclosure. The device 600 is provided for implementing a communication device, for example, a terminal device 210 shown in Figure 2. As shown in the figure, the device 600 comprises one or more processors 610, one or more memories 620 connected to the processors 610, and one or more communication modules 640 connected to the processors 610.

[0114] The communication module 640 is for bidirectional communication. The communication module 640 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements.

[0115] The processor 610 is of any type suitable for a local technology network and may include, for example, a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), or a processor based on a multi-core processor architecture. The device 600 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent to a clock that synchronizes the main processor.

[0116] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically rewritable read-only memory (EPROM), flash® memory, hard disks, compact discs (CDs), digital video discs (DVDs), and other magnetic and / or optical memory devices. Examples of volatile memories include, but are not limited to, random-access memory (RAM) 622 and other volatile memories that cannot retain data during power-off periods.

[0117] The computer program 630 includes computer executable instructions that are executed by the associated processor 610. The program 630 may be stored in ROM 624. The processor 610 can perform any appropriate operations and processes by loading the program 630 into RAM 622.

[0118] Embodiments of the present disclosure are implemented by program 630, enabling the device 600 to perform any of the processes of the disclosure described with reference to Figures 3-5. Embodiments of the present disclosure may also be implemented by hardware, or by a combination of software and hardware.

[0119] In some embodiments, the program 630 may be tangibly stored in a computer-readable medium built into the device 600 (for example, in the memory 620) or in another storage device accessible to the device 600. The device 600 can load the program 630 from the computer-readable medium into the RAM 622 and execute it. The computer-readable medium can include any type of tangible non-volatile storage device, such as ROM, EPROM, flash® memory, hard disk, CD, DVD, etc.

[0120] Figure 7 is a block diagram showing an example of a computer-readable medium 700 according to some embodiments of the present disclosure. The computer-readable medium 700 stores a program 630. In Figure 7, the computer-readable medium 700 is shown in the form of a CD or DVD, but it should be noted that it may be in other forms suitable for transporting or holding the program 630.

[0121] In general, various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some features may be implemented in hardware, while others may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Various aspects of the embodiments of this disclosure are described using block diagrams, flowcharts, or other graphical representations, but it should be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or a combination thereof.

[0122] Furthermore, this disclosure provides at least one computer program product tangibly recorded on a non-temporary computer-readable storage medium. This computer program product includes computer-executable instructions, such as those contained in a program module, and is executed on a device on a target real or virtual processor to perform the methods described above with reference to one of Figure 5. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The functionality of program modules may be combined or divided among program modules as needed in various embodiments. Machine-executable instructions for program modules may be executed locally or within a distributed device. In a distributed device, program modules may reside on both local and remote storage media.

[0123] Program code for carrying out the methods described herein may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device. This ensures that, when executed by the processor or controller, the program code implements the functions / operations specified in the flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, as a standalone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0124] In the context of this disclosure, computer program code or related data may be carried by any suitable medium to enable a device, apparatus, or processor to perform various processes and operations as described above. Examples of such mediums include signals and computer-readable media.

[0125] Computer-readable media may be computer-readable signal media or computer-readable storage media. Computer-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, and semiconductor systems, apparatus, devices, or appropriate combinations thereof. More specific examples of computer-readable storage media include electrical connections with one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash® memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or appropriate combinations thereof. The term “non-temporary” as used herein refers to a limitation on the medium itself (i.e., a tangible medium rather than a signal) and not on the persistence of data storage (e.g., RAM vs. ROM).

[0126] Furthermore, even if operations are shown in a specific order, it should not be interpreted that the operations must be performed in a specific illustrated or sequential order, or that all illustrated operations must be performed, in order to obtain the desired result. In certain situations, multitasking or parallel processing may be advantageous. Similarly, although the above description includes some specific implementation details, these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features specific to a particular embodiment. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable partial combination in multiple embodiments.

[0127] While this disclosure is described in a language specific to structural features and / or methodological actions, the disclosure as defined in the attached claims is not necessarily limited to the specific functions or actions described above. Rather, the specific functions or actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A terminal device, At least one processor, When executed by the at least one processor, the terminal device receives at least, In the first layer of the terminal device, a mobility command is received from the first network device, The first layer of the terminal device provides an attention (AT) command associated with the mobility command to the second layer of the terminal device, wherein the AT command notifies the second layer to release at least one set quality-of-effect (QoE) measurement and associated radio resource control (RRC) identifier (ID), and the second layer is a higher layer than the first layer. In the second layer of the terminal device, based on the AT command, the at least one set QoE measurement and associated RRC ID are released, At least one memory to store instructions to execute, A terminal device equipped with the following features.

2. The aforementioned terminal device is The first portion of the first layer provides the AT command to the second layer upon receiving the mobility command, wherein the first portion of the first layer is associated with the first network device. The terminal device according to claim 1, which is configured to perform the following:

3. The aforementioned terminal device is The AT command is provided from the second portion of the first layer to the second layer after successfully decoding the RRC connection reset information associated with the second network device, or after connecting to the second network device, wherein the second portion of the first layer is associated with the second network device. The terminal device according to claim 1, which is configured to perform the following:

4. The aforementioned terminal device further, In the first layer of the terminal device, the QoE report data acquired from the second layer is discarded. The terminal device of claim 3, which is configured to perform the following.

5. The aforementioned terminal device further, The first portion of the first layer notifies the second layer to stop at least one of the QoE measurement or QoE reporting when the mobility command is received. The terminal device according to claim 3 or 4, which is configured to perform the following:

6. The terminal device according to any one of claims 3 to 5, wherein the AT command includes a QoE setting container set by the second network device.

7. The aforementioned terminal device further, By decoding the mobility command, the RRC connection reset information associated with the second network device is obtained. A terminal device according to any one of claims 3 to 6, which is configured to perform the following:

8. The terminal device according to any one of claims 3 to 7, wherein the second network device is a Long-Term Evolution (LTE) network device.

9. The terminal device according to any one of claims 3 to 8, wherein the first network device is a new wireless (NR) network device.

10. The aforementioned terminal device further, Performing a wireless access technology (RAT) handover process from the first network device to the second network device, A terminal device according to any one of claims 2 to 9, which is configured to perform the following:

11. The terminal device according to any one of claims 1 to 10, wherein the at least one configured QoE measurement and associated RRC ID includes all configured QoE measurements and associated RRC IDs configured by the first network device.

12. The terminal device according to any one of claims 1 to 11, wherein the first layer of the terminal device is an access stratum (AS) layer, and the second layer of the terminal device is an application layer.

13. In the first layer of the terminal device, it receives mobility commands from the first network device, The first layer of the terminal device provides an attention (AT) command associated with the mobility command to the second layer of the terminal device, wherein the AT command notifies the second layer to release at least one set quality-of-effect (QoE) measurement and associated radio resource control (RRC) identifier (ID), and the second layer is a higher layer than the first layer. In the second layer of the terminal device, based on the AT command, at least one set QoE measurement and associated RRC ID are released. Methods that include...

14. In the first layer of the terminal device, means for receiving mobility commands from the first network device, Means for providing an attention (AT) command associated with the mobility command from the first layer of the terminal device to the second layer of the terminal device, wherein the AT command notifies the second layer to release at least one set quality-of-effect (QoE) measurement and associated radio resource control (RRC) identifier (ID), and the second layer is a higher layer than the first layer. The second layer of the terminal device includes means for releasing at least one set QoE measurement and associated RRC ID based on the AT command, A device equipped with the following features.

15. A computer-readable medium containing program instructions for causing the device to carry out at least the method described in claim 13.

Images