Switching user equipment type

Abstract

Embodiments of this disclosure relate to UE type switching. In one embodiment, a terminal device transmits capability information to a network device indicating support for multiple types of terminal devices. The network device then transmits an instruction to the terminal device to switch the type of terminal device. Furthermore, the terminal device performs the type switching based on the instruction and requirements regarding the interruption caused by the type switching. In this way, it is possible to avoid transmission failures due to interruptions caused by type switching, resulting in improved resource utilization and transmission flexibility.

Description

Technical Field

[0001] Various embodiments relate to the field of communications, and more particularly, to devices, methods, apparatuses, and computer-readable storage media for type switching of user equipment (UE).

Background Art

[0002] In the field of communication technology, continuous evolution has been ongoing to provide efficient and reliable solutions for leveraging wireless communication networks. Each new generation has its own specific technical challenges to address various situations and processes required to connect devices connected to the wireless network and provide services. Since the introduction of the fourth-generation (4G) communication system, efforts have been made to develop improved fifth-generation (5G), pre-5G, or 5G advanced communication systems to meet the increasing demand for wireless data traffic. These new communication systems can support various types of service applications for terminal devices.

[0003] According to the discussions of the Radio Access Network (RAN) Working Group 4 (RAN4), type 1 and type 2 UE architectures are distinguished by the number of receive (Rx) chains. A UE with a type 1 architecture receives from carriers within the same band via a single Rx chain (or a configuration assuming a single fast Fourier transform (FFT)). A type 2 UE receives from different bands, or from different carriers in the same or overlapping bands, via separate Rx chains (or separate FFTs, low-noise amplifiers (LNAs), antennas). Discussions have also been held regarding the type switching of UEs between type 1 and type 2. However, there are still some unresolved issues with such UE type switching and it is scheduled to be studied in the near future.

Summary of the Invention

[0004] Generally, embodiments of the present disclosure provide solutions related to type switching of UEs.

[0005] In a first embodiment, a terminal device is provided. The terminal device comprises at least one processor and at least one memory storing instructions that, when executed by at least one processor, cause the terminal device to transmit capability information indicating support for multiple types of the terminal device to a network device, receive instructions from the network device to switch the type of the terminal device, and perform the type switch based on the instructions and requirements regarding interruptions caused by the type switch.

[0006] In a second embodiment, a first network device is provided. The first network device comprises at least one processor and at least one memory which stores instructions that, when executed by at least one processor, cause the first network device to perform at least: receive capability information from a terminal device indicating support for multiple types of terminal devices; send instructions to a terminal device to switch the type of terminal device; and determine the scheduling of the terminal device based on the instructions and requirements regarding interruptions caused by the type switching in the terminal device.

[0007] In a third embodiment, a second network device is provided. The second network device includes at least one processor and at least one memory that stores instructions that, when executed by at least one processor, cause the second network device to perform at least: receive a terminal switching instruction from the first network device indicating a switch in the type of terminal device; and determine the scheduling of the terminal device based on requirements regarding the interruption caused by the type switching in the terminal device.

[0008] In a fourth embodiment, a method is provided. This method includes a terminal device transmitting capability information to a network device indicating support for multiple types of the terminal device; receiving instructions from the network device to switch the type of the terminal device; and performing the type switch based on the instructions and requirements regarding the interruption caused by the type switch.

[0009] A fifth embodiment provides a method, which includes a first network device receiving capability information from a terminal device indicating support for multiple types of terminal devices; transmitting instructions to the terminal device to switch the type of terminal device; and determining the scheduling of the terminal device based on the instructions and requirements regarding the interruption caused by the type switching in the terminal device.

[0010] In a sixth embodiment, a method is provided. This method includes a second network device receiving a terminal switching instruction from a first network device indicating a change in the type of terminal device, and determining the scheduling of the terminal device based on requirements regarding the interruption caused by the type switching in the terminal device.

[0011] In a seventh embodiment, an apparatus is provided. The apparatus comprises a terminal device, means for transmitting capability information to a network device indicating support for multiple types of the terminal device; means for receiving instructions from the network device indicating a type switch of the terminal device; and means for performing a type switch based on the instructions and requirements regarding interruptions caused by the type switch.

[0012] In an eighth embodiment, an apparatus is provided. The apparatus is a first network apparatus comprising: means for receiving capability information from terminal devices indicating support for multiple types of terminal devices; means for transmitting instructions to terminal devices for switching the type of terminal device; and means for determining the scheduling of terminal devices based on the instructions and requirements regarding interruptions caused by the type switching in the terminal devices.

[0013] In a ninth embodiment, an apparatus is provided. The apparatus includes, in a second network device, means for receiving a terminal switching instruction from a first network device indicating a switching of terminal device types, and means for determining the scheduling of terminal devices based on requirements regarding interruptions caused by the type switching in the terminal devices.

[0014] In a tenth embodiment, a non-temporary computer-readable medium is provided which includes program instructions for causing the device to perform at least one of the methods according to the fourth to sixth embodiments described above.

[0015] In the eleventh embodiment, a computer program is provided that, when executed by the device, includes instructions causing the device to perform at least one of the methods according to the fourth to sixth embodiments described above.

[0016] In a twelfth embodiment, a terminal device is provided. The terminal device comprises a transmitting circuit configured to transmit capability information indicating support for multiple types of terminal devices to a network device; a receiving circuit configured to receive instructions from the network device for switching the type of terminal device; and an executing circuit configured to perform a type switch based on the instructions and requirements regarding interruptions caused by the type switch.

[0017] In a thirteenth embodiment, a first network device is provided. The first network device comprises a receiving circuit configured to receive capability information from terminal devices indicating support for multiple types of terminal devices; a transmitting circuit configured to send instructions to terminal devices for switching the type of terminal device; and a decision circuit configured to determine the scheduling of terminal devices based on the instructions and requirements regarding interruptions caused by type switching in terminal devices.

[0018] In a fourteenth embodiment, a second network device is provided. The second network device comprises a receiving circuit configured to receive a terminal switching instruction from the first network device indicating a change in the type of terminal device, and a decision circuit configured to determine the scheduling of the terminal device based on requirements regarding the interruption caused by the type switching in the terminal device.

[0019] It should be noted that the summary section is not intended to identify any key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will be readily apparent through the following description. [Brief explanation of the drawing]

[0020] Several embodiments will be described below with reference to the attached drawings. [Figure 1A] Figure 1A shows an example of an environment in which some examples of embodiments of the present disclosure can be implemented. [Figure 1B] Figure 1B shows an exemplary Type 2 UE architecture related to several embodiments of the present disclosure. [Figure 1C] Figure 1C shows an example of UE type switching related to some embodiments of the present disclosure. [Figure 2] Figure 2 shows the signaling flow between a terminal device, a first network device, and a second network device according to some embodiments of the present disclosure. [Figure 3] Figure 3 shows an example of a UE type switching process according to some embodiments of the present disclosure. [Figure 4] Figure 4 shows a flowchart of a method executed in a terminal device according to some embodiments of the present disclosure. [Figure 5] Figure 5 shows a flowchart of a method executed in a first network device according to some embodiments of the present disclosure. [Figure 6] Figure 6 shows a flowchart of a method executed in a second network device according to some embodiments of the present disclosure. [Figure 7] Figure 7 shows a simplified block diagram of a device suitable for implementing some embodiments of the present disclosure. [Figure 8] Figure 8 is a block diagram showing 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.

Embodiments for Carrying out the Invention

[0021] The principles of the present disclosure will be described with reference to some embodiments. These embodiments are described for the purpose of exemplifying the present disclosure and are intended to assist those skilled in the art in understanding and implementing the present disclosure, and do not limit the scope of the present disclosure in any way. The disclosure described herein can be implemented in various manners without being limited to the aspects described below.

[0022] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which the present disclosure pertains.

[0023] In this specification, expressions such as “one embodiment,” “embodiment,” and “exemplary embodiment” indicate that the described embodiments may include certain features, structures, or characteristics, but not all embodiments are required to include such features, structures, or characteristics. 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 is considered within the scope of the knowledge of those skilled in the art to apply that function, structure, or characteristic in relation to other embodiments, whether or not it is explicitly stated.

[0024] In this specification, terms such as “first” and “second” may be used to describe various elements, but it should be understood that these elements are not limited by these terms. These terms are used solely to distinguish one element from another. For example, it is possible to refer to the first element as the second element, and similarly, the second element as the first element, without departing from the scope of the embodiments. In this specification, the term “and / or” includes any combination of one or more of the enumerated terms.

[0025] The terms used herein are intended to describe specific embodiments and are not intended to limit the embodiments. In this specification, the singular forms “a,” “an,” and “the” are to be interpreted as including the plural unless the context clearly indicates otherwise. Furthermore, in this specification, the terms “equip,” “equip,” “have,” “possess,” “include,” and / or “include,” 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, “at least one of the following: <list of two or more elements>” and “at least one of <list of two or more elements>” and similar expressions mean at least one of the elements, or at least two or more elements, or at least all of the elements, where the lists of two or more elements are joined by “and” or “or.”

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

[0027] The definition of the term “circuit” as used herein applies to all uses of the term in this application, including its use in the claims. For example, as used in this application, the term “circuit” includes not only a mere hardware circuit or processor (or more processors), but also a portion of a hardware circuit or processor and the associated software and / or firmware implementation. Furthermore, when applied to an element of a particular claim, the term “circuit” also includes, for example, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0028] As used herein, the term “communication network” refers to a network conforming to any appropriate communication standard, such as New Radio (NR), Long-Term Evolution (LTE), LTE-Advanced (LTE-A), Broadband Code Division Multiple Access (WCDMA®), High-Speed ​​Packet Access (HSPA), and Narrowband IoT (NB-IoT). Furthermore, communication between terminal devices and network devices in a communication network may be carried out in accordance with any appropriate generation of communication protocol, including but not limited to third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of the field of communications, it is clear that this disclosure may also be applicable to future types of communication technologies and systems. Therefore, the scope of this disclosure should not be construed as being limited only to the systems described above.

[0029] In this specification, the term “network device” refers to a node within a communication network that serves as a path for terminal devices to access the communication network and receive services from it. Network devices may also refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), Radio Access Network (RAN) nodes, Evolutionary Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), Infrastructure Devices for V2X (Vehicle-to-Everything) Communication, Transmitting / Receiving Points (TRP), Receiving Points (RP), Remote Radio Heads (RRH), Repeaters, Integrated Access Backhaul (IAB) nodes, and low-power nodes such as femtoBS and picoBS, which may vary depending on the terminology and technology applied.

[0030] The term "terminal equipment" refers to any end device capable of wireless communication. In more specific examples, terminal equipment may also be called communication equipment, user equipment (UE), subscriber station (SS), portable subscriber station, 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 devices, personal digital assistants (PDAs), portable computers, desktop computers, digital cameras and other image capture devices, gaming devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches and other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and their applications (e.g., remote surgery), industrial devices and their applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics, devices operating on commercial and / or industrial wireless networks, and similar devices. In the following description, the terms “terminal device,” “communication device,” “terminal,” “user device,” and “UE” may be used interchangeably.

[0031] The principles and embodiments of this disclosure will be described in detail below with reference to the attached drawings.

[0032] First, refer to Figure 1A. Figure 1A shows an example of an environment 100 in which embodiments of the present disclosure may be implemented. The environment 100, which may be part of a communication network, includes a terminal device 110, and network devices 120 and 130 (referred to as the first network device 120 and the third network device 130, respectively). Communication between the terminal device 110, the first network device 120, and the second network device 130 may be direct or indirect. For example, the terminal device 110, the first network device 120, and the second network device 130 may communicate with one or more further devices not shown in Figure 1A.

[0033] In some embodiments relating to a non-co-located NR-CA scenario within the same band, the first cell provided by the first network device 120 and the second cell provided by the second network device 130 are non-co-located. The first network device 120 provides a primary cell (PCell) to the terminal device 110, and the second network device 130 provides a secondary cell (SCell) for the terminal device 110 to operate in carrier aggregation (CA).

[0034] In some embodiments of interband EN-DC scenarios with overlapping bands, the first network device 120 may include a master node, and the second network device 130 may include a secondary node. The master node and secondary node may be provided to the terminal device 110 as dual connectivity. The first network device 120 may provide the terminal device 110 with a master cell group (MCG), and the second network device 130 may provide the terminal device 110 with a secondary cell group (SCG).

[0035] To transmit data and / or control information, the first device 110 may communicate with the first network device 120 and / or the second network device 130. The links from the first network device 120 and / or the second network device 130 to the terminal device 110 are called downlinks (DL), and the links from the terminal device 110 to the first network device 120 and / or the second network device 130 are called uplinks (UL).

[0036] In the communication environment 100 of Figure 1A, a terminal device 110, a first network device 120, and a second network device 130 are described, but embodiments of the present disclosure are equally applicable to any other suitable communication devices that communicate with each other. That is, embodiments of the present disclosure are not limited to the exemplary scenario of Figure 1A. In this regard, in Figure 1A, the terminal device is schematically shown as a mobile phone, and the first network device 120 and the second network device 130 are schematically shown as base stations, but these illustrations are illustrative and do not imply any limitation. In other embodiments, the first device 110, the first network device 120, and the second network device 130 may be any other communication devices, for example, any other wireless communication devices.

[0037] The specific numbers of various communication devices and communication links shown in Figure 1A are for illustrative purposes only and do not imply any limitation. The communication environment 100 may include any appropriate number of communication devices and any appropriate number of communication links to implement embodiments of this disclosure. Furthermore, it should be understood that wired communication, as well as wireless communication, may occur between all communication devices as needed.

[0038] Communication in communication environment 100 may conform to any existing or future-developed appropriate communication standards or protocols, such as Universal Mobile Communications System (UMTS), Long-Term Evolution (LTE), LTE-Advanced (LTE-A), 5th Generation (5G) New Radio (NR), Wireless Fidelity (Wi-Fi®), and Worldwide Interoperability Microwave Access (WiMAX®) standards. Furthermore, communication may utilize any appropriate communication technology, including but not limited to Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), Bluetooth®, ZigBee®, as well as Machine Type Communication (MTC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Ultra-High Reliability Low Latency Communication (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC), and New Radio Unlicensed (NR-U) technologies.

[0039] As mentioned above, according to the discussions in RAN4, Type 1 and Type 2 UE architectures are distinguished by the number of Rx chains. Type 1 is the baseline or legacy architecture used in intra-band new radio carrier aggregation (NR-CA) and intra-band evolved-universal terrestrial radio access network new radio dual connectivity (EN-DC) (where collocation deployment is always assumed). UEs with Type 1 receive from intra-band carriers via a single Rx chain (or a configuration assuming a single FFT). Type 2 is assumed to support interband operations, including interband NR-CA and interband EN-DC. Since Release 16, it has been further agreed that non-collocation scenarios within the intraband in frequency range 1 (FR1) can also be supported. Here, the non-co-located scenarios within the same band include non-co-located NR-CA within the same band and non-co-located EN-DC within the same band (also known as inter-band EN-DC when the bands overlap). A UE with type 2 receives from different bands in the case of inter-band scenarios, or from different carriers in the same band or overlapping bands in the case of non-co-located scenarios, via separate Rx chains (or separate FFT, LNA, antennas).

[0040] Until Release 17 (Rel-17), when defining RRM requirements for FR1 same-band NR-CA, only co-location scenarios were considered. However, from the operator's perspective, UE requirements supporting non-co-location configurations are essential to expand the usable area of ​​EN-DC / NR-CA. At the RAN#95e meeting of Release 18 (Rel-18), RAN4 work item (WI) RP-221004 was approved, defining UE requirements to support non-co-location EN-DC / NR-CA configurations within the same band. The WI description (WID) was further updated in RAN#96 as RP-221809, as follows, necessitating a re-examination or definition of RRM requirements to support FR1 same-band non-co-location scenarios. [Table 1]

[0041] Support for non-co-located EN-DC within the same band is indicated by the UE capability "interBandMRDC-WithOverlapDL-Bands-r16" as defined in Release 16 (Rel-16): [Table 2]

[0042] At RAN4#107 meeting, a similar UE capability [intraBandNonColocatedCA-r18] was introduced for non-colocated intraband NR-CA as follows: In either case, a UE exhibiting this capability is considered a Type 2 UE, and the network can configure band combinations that allow non-colocated placement in FR1 intraband CA / EN-DC, such as n42+n77 / 78. Otherwise, the network should not configure such band combinations. [Table 3]

[0043] Furthermore, the switching of UE types between Type 1 and Type 2 was also discussed. For example, at the RAN4#106bis-e meeting, it was proposed that UEs supporting Type 2 should support the ability to switch between Type 1 and Type 2 based on requests from base stations (BS).

[0044] At RAN4#107 meeting, the following was further discussed in R4-2310300: In previous discussions, there was agreement that the UE type can be switched between Type 1 and Type 2 based on network instructions. [Table 4]

[0045] Furthermore, at the RAN4#106bis-e meeting, it was proposed that UEs supporting Type 2 can operate as either Type 1 or Type 2 based on network signaling. It is understood that UEs demonstrating this capability can operate in their default UE type and switch to the other UE type based on instructions from the network.

[0046] Figure 1B shows an example of a UE architecture with Type 2 relating to some embodiments of the present disclosure, and Figure 1C shows an example of UE type switching between Type 1 and Type 2 relating to some embodiments of the present disclosure. When a UE switches between different types, it may need to turn on / off certain RF units, such as Rx chains. For example, when a UE switches from Type 1 to Type 2, it may need to turn on additional Rx chains and switch data transmission from a single Rx chain to multiple Rx chains. On the other hand, as shown in Figure 1C, when a UE switches from Type 2 to Type 1, some Rx chains are bypassed and all data passes through a single Rx chain.

[0047] Enabling a new type of architecture may require a certain period of time, such as a transition period, during which data transmission in at least some Rx chains may be affected. Currently, there is no effective way to support UE type switching. To minimize adverse effects on data transmission, it is expected that the network will recognize UE type switching and its potential impact and adjust UE scheduling accordingly. Optimizing UE type switching remains a significant challenge to address. This invention explores several enhancements to the interaction between UE and BS regarding UE type switching. For example, it is necessary to consider the radio resource management (RRM) requirements related to UE type switching.

[0048] Embodiments of the present disclosure provide a method for switching the type of UE. In this method, a terminal device transmits capability information to a network device indicating the support for multiple types of the terminal device. The network device then transmits an instruction to the terminal device to switch the type of the terminal device. The terminal device then performs the type switch based on the instruction and requirements regarding the interruption caused by the type switch.

[0049] This method optimizes the type switching procedure by introducing requirements regarding the interruptions caused by type switching. These requirements ensure a shared understanding between terminal devices and network devices regarding the interruptions caused by type switching. This allows network devices to adjust cell configurations and data scheduling based on these requirements. In this way, transmission failures caused by interruptions due to type switching can be minimized or avoided, resulting in improved resource utilization and transmission flexibility.

[0050] Figure 2 shows a signaling flow 200 between a terminal device, a first network device, and a second network device according to several embodiments of the present disclosure. For convenience of explanation, the signaling flow 200 will be described with reference to Figure 1A.

[0051] As shown in Figure 2, the terminal device 110 transmits capability information to the first network device 120 indicating support for multiple types of terminal devices (205). In response, the first network device 120 receives capability information from the terminal device 110 (210). For example, the type of terminal device 110 includes the UE architecture type. Capability information may be included in a radio access control (RRC) message.

[0052] As an example, capability information may include one or more switching periods required to perform a type switch at terminal device 220. Terminal device 110 may notify the network side of the switching period required to switch the UE type in order to determine how long the interruption caused by the type switch will last. As another example, capability information may include one or more switching directions. One or more switching directions may correspond to one or more switching periods. Alternatively or additionally, capability information may further indicate for each of the one or more switching directions whether the interruption caused by the type switch is acceptable. Terminal device 110 may notify for each of the one or more switching directions whether the interruption in the UE type switch is acceptable.

[0053] In some embodiments in which the terminal device 110 supports at least a first type and a second type, the switching direction can include a first switching direction from type 1 to type 2, and a second switching direction from type 2 to type 1. In this case, two different switching periods can be indicated for each: a first switching period required for switching from the first type to the second type, and a second switching period required for switching from the second type to the first type. The first or second switching period may be set to zero. If the first type is type 1 and the second type is type 2, the switching period from type 2 to type 1 may be set to zero; that is, no additional time is required for the type switching of the UE.

[0054] As yet another example, capability information may include one or more cells or carriers in terminal device 110 that are allowed (or expected) to experience interruptions resulting from type switching. Such cells or carriers are also called victim cells or victim carriers. For example, when terminal device 110 switches from type 1 to type 2, interruptions may be allowed (or expected) in all serving cells within the same band. As yet another example, when terminal device 110 switches from type 2 to type 1, interruptions may be allowed (or expected) in certain carriers, or they may not be allowed (or expected). As yet another example, terminal device 110 may indicate victim carriers (if any) in which interruptions are allowed (or expected) during each switch. One or more carriers may be indicated via a cell or carrier index, or a bitmap may be used to indicate which one or more serving cells are victim carriers. As yet another example, the absence of one or more cells may indicate that there are no interruptions in the type switch.

[0055] Alternatively or additionally, capability information may include support for type switching to non-co-located co-band evolved general-purpose terrestrial radio access new radio dual connectivity (EN-DC) and / or non-co-located co-band new radio carrier aggregation (NR-CA). In this case, one or more switching periods include at least one switching period for EN-DC and / or at least one switching period for NR-CA. For example, different switching periods may be indicated for EN-DC and NR-CA, respectively. Terminal device 110 may indicate a longer switching period when switching from type 1 to type 2 compared to the case of NR-CA, because different RATs may be considered in the case of EN-DC.

[0056] Next, as shown in Figure 2, the first network device 120 sends an instruction to the terminal device 110 to switch the type of the terminal device 110 based on the acquired capability information (215). On the receiving end of the communication, the terminal device 110 receives the instruction from the first network device 120 (220). In embodiments in which the terminal device 110 supports both type 1 and type 2, this instruction may indicate a type switch from type 1 to type 2, or from type 2 to type 1. This instruction may be contained in an RRC message, or a media access control (MAC) message or a Layer 1 (L1) message.

[0057] The terminal device 110 can determine the requirements regarding interruptions caused by type switching based on capability information and instructions. In other words, when the terminal device 110 performs a type switch, for example, when switching architecture types, interruptions may be permitted according to those requirements.

[0058] In some embodiments, the requirements may include an interruption length that defines an upper limit on the interruption allowed for the terminal device 110. The interruption length is determined based on at least the switching period, the switching direction, and / or the subcarrier spacing (SCS) of the affected cell. For example, the terminal device 110 may determine at least the interruption length based on the switching period corresponding to the switching direction indicated in the instructions from the first network device 120, and / or, corresponding to that switching direction, the subcarrier spacing (SCS) of at least one cell or carrier (i.e., the affected cell or carrier) that may be affected by the interruption. For example, the interruption length includes at least the switching period in the corresponding direction of the switching. Different interruption lengths may be determined for different switching directions (e.g., switching from type 1 to type 2 and switching from type 2 to type 1).

[0059] In some embodiments, this requirement may further include processing time required for the terminal device 110 to process instructions from the first network device 120. The terminal device 110 may begin performing the type switch after this processing time. The interruption caused by the type switch begins when the terminal device 110 begins performing the type switch after the processing time. In other words, the processing time is used to determine the interruption point at which the interruption begins. For example, after receiving a network signaling indicating a type switch, the interruption in the affected cell or carrier may begin after a processing time for the terminal device 110 to process the network signaling.

[0060] In other words, terminal device 110 is permitted to interrupt communication, for example, in an affected cell or carrier, according to an interruption window. The interruption window may be defined based on the aforementioned interruption period and the start position of the interruption. For example, if terminal device 110 receives a switching instruction from the first network device 120, the interruption may start several slots / symbols / microseconds after the reception of the switching instruction, since terminal device 110 requires several slots / symbols / microseconds to process the instruction. Subsequently, terminal device 110 performs a type switch according to the switching period, thereby allowing the interruption to continue for a period corresponding to the switching period.

[0061] Next, as shown in Figure 2, the terminal device 110 performs a type switch based on the instructions and requirements (225). The terminal device 110 can perform the instructed type switch based on its capabilities. After the type switch, data transmission with the network side resumes. While the terminal device 110 is switching types, the terminal device 110 is allowed to interrupt communication within the affected cell or carrier during the interruption period, i.e., within the interruption window. For example, if the intended affected cell is not indicated in the capability information, or if the interruption period and location cannot be determined, the interruption may not be performed (or allowed).

[0062] Similarly, the first network device 120 can determine requirements regarding the interruption caused by type switching in the terminal device 110, based on capability information and instructions. For example, the first network device 120 can determine the duration of the interruption and the start point of the interruption.

[0063] Next, the first network device 120 determines the scheduling of the terminal device 110 based on its requirements (230). In some embodiments, the first network device 120 may prevent scheduling of the terminal device 110 based on its requirements. For example, the first network device 120 may refrain from scheduling the terminal device 110 after processing time and during a break period.

[0064] In some embodiments, the first network device 120 may transmit a terminal switching instruction to the second network device 130 indicating a switch in the type of terminal device 110 (235). In response, the second network device 130 may receive a terminal switching instruction from the first network device 120 (240). The terminal switching instruction may include a switching period required for the terminal device 110 to perform the instructed switching. Alternatively or additionally, the terminal switching instruction may include at least one cell or carrier that is allowed to be interrupted, i.e., an affected cell.

[0065] Similarly, the second network device 130 can determine requirements regarding the interruption caused by type switching in the terminal device 110 based on the terminal switching instruction. The second network device 130 then determines the scheduling of the terminal device 110 based on those requirements (245). In some embodiments, the second network device 130 may prevent scheduling of the terminal device 110 based on those requirements. For example, the second network device 130 may refrain from scheduling the terminal device 110 after processing time and during the interruption period.

[0066] For example, technical specifications (TS) 38.133 may be modified as follows: When a UE receives a network instruction [UETypeSwitchingType 1→2], and the UE has the capability of [intraBandNonColocatedCA-r18], interruptions are permitted in [VictimCells1→2] as indicated in the UE capability during the switch from Type 1 to Type 2. This interruption shall be limited to the maximum X1 slot as defined in Table 8.2.2.xy-1. When a UE receives a network instruction [UETypeSwitchingType 2→1], and the UE has the capability of [intraBandNonColocatedCA-r18], an interruption is permitted in the [VictimCells2→1] indicated in the UE capability during the switch from Type 2 to Type 1. This interruption shall be limited to a maximum of X2 slots as specified in Table 8.2.2.xy-1.

[0067] In this way, terminal equipment can understand how quickly UE type switching should be performed and the extent to which each switch may negatively impact other cells and carriers. Based on specified interruption conditions, terminal equipment and network equipment agree on how long the switch will last, which symbols / slots it will occur in, and which carriers will experience data transmission interruptions. This allows network equipment to adjust cell configuration and data scheduling based on interruption requirements. Consequently, transmission failures caused by interruptions resulting from type switching can be minimized or avoided, improving resource utilization efficiency and transmission flexibility.

[0068] Figure 3 shows an example of a UE type switching process according to several embodiments of the present disclosure. It should be understood that the process flow 300 can be considered a more specific example of the signaling flow 200 shown in Figure 2. Thus, UE 301 may be an example of a terminal device 110. Also, as an example, a P cell (PCell) 303 may be provided by a first network device 120, and a secondary cell (S cell (SCell)) 305 may be provided by a second network device 130.

[0069] This exemplary process assumes a non-co-located NR-CA scenario within the same band, but similar procedures can be applied to EN-DC scenarios, i.e., interband EN-DC scenarios where DL bands overlap.

[0070] As shown in Figure 3, at 306, UE301 is connected to PCell303. At 308, UE301 transmits UE capability information indicating that it supports non-co-located CA within the same band. The UE capability information may indicate that UE301 supports multiple UE types (e.g., type 1 and type 2). Alternatively, the UE capability information may indicate that UE301 supports UE type 2, which implicitly means that UE301 supports both type 1 and type 2, since type 1 is the default UE type that is always supported by UE301. Furthermore, in the UE capability information, UE301 may indicate the transition periods required to switch the UE type from type 1 to type 2, and from type 2 to type 1. In this case, as indicated, no interruption occurs during the switch from type 2 to type 1. The presence of transition periods may indicate that UE301 supports UE type switching. On the other hand, if UE301 indicates the capability for non-co-located CA within the same band, but the UE capability information does not indicate a transition period, UE301 may always operate in type 2 mode. Additionally, UE301 may notify affected cells / carriers that may experience interruptions during UE type switching.

[0071] At 310, the network configures a non-co-located CA for UE301 by adding S cell (SCell) 305. After receiving this configuration, UE301 operates with its default UE type (e.g., type 1). Subsequently, at 312 and 314, UE301 receives data from P cell (PCell) 303 and S cell (SCell) 305 via a single Rx chain.

[0072] In step 316, the network determines that P cell 303 and S cell 305 are non-co-located and sends a network signal (e.g., an RRC message) to UE 301 requesting a switch to type 2. Alternatively, or additionally, this step may be integrated into step 310, that is, the network may notify the UE of the type switch when adding S cell 305.

[0073] Upon receiving an RRC message, UE301 requires a certain amount of time to switch to type 2. UE301 experiences processing time for processing the RRC message (318) and a switching period (320) for switching from type 1 to type 2. In 322, P cell 303 notifies S cell 305 of the UE type switch "type 1→2" along with, for example, switching period 1→2. In 324, the network determines the interruption period based on the received switching period 1→2 and may refrain from scheduling UE301 in the affected cell (S cell 305) during this interruption period. UE301 may experience interruptions in S cell 305 during the interruption period. After the UE switches to type 2, the network can restore data transmission in the affected cell.

[0074] Similarly, in 326, the network notifies of the type switch from type 2 to type 1 via an RRC message, for example, when P cell 303 and S cell 305 are co-located. UE 301 processes the RRC message (328) and may then perform the type switch within the target time window as described above (330). In 332, P cell 303 notifies S cell 305 of the UE type switch "type 2→1" along with a switching period of 2→1, for example. In 334, the network determines that no interruption is expected, as indicated in the UE capability information. Therefore, an interruption due to the UE type switch is not permitted in P cell 303 or S cell 305. In 336 and 338, data transmission between UE 301 and the network is performed without interruption.

[0075] Referring to Figure 2, the operations and characteristics described above also apply to process 300, producing similar effects. For simplicity, details are omitted.

[0076] Figure 4 shows a flowchart 400 of a method performed in a terminal device according to some embodiments of the present disclosure. For convenience of explanation, the method 400 will be described from the perspective of the terminal device 110 with reference to Figure 1A.

[0077] In block 410, the terminal device 110 transmits capability information to the first network device 120 indicating that the terminal device 110 supports multiple types. In block 420, the terminal device 110 receives an instruction from the first network device 120 to switch the type of the terminal device 110. In block 430, the terminal device 110 performs the type switch based on the instruction and requirements regarding the interruption caused by the type switch.

[0078] In some embodiments, the terminal device 110 can further determine its requirements based on capability information and instructions.

[0079] In some embodiments, the type of terminal device 110 may include a user equipment (UE) architecture type.

[0080] In some embodiments, capability information may further include at least one of the following: one or more switching periods required to perform type switching; one or more switching directions; one or more cells or carriers that are permitted to be interrupted; or support for type switching to evolved general-purpose terrestrial radio access new radio dual connectivity (EN-DC) and / or non-co-located in-band new radio carrier aggregation (NR-CA).

[0081] In some embodiments, the requirement may include an interruption period, and the terminal device 110 may further determine the interruption period based on at least one of one or more switching periods, which corresponds to the switching direction of the switching indicated in the instruction, and the subcarrier spacing (SCS) of at least one cell or carrier corresponding to the switching direction, which corresponds to one or more cells or carriers. In some embodiments, the terminal device 110 allows an interruption up to the interruption period.

[0082] In some embodiments, the multiple types may include a first type and a second type, and one or more transition periods may include a first transition period required for switching from the first type to the second type, and a second transition period required for switching from the second type to the first type. In some embodiments, the first or second transition period may be set to zero.

[0083] In some embodiments, one or more switching periods may include at least one switching period for EN-DC and at least one switching period for NR-CA.

[0084] In some embodiments, capability information may further indicate whether the interruption caused by type switching is acceptable for each of the one or more switching directions.

[0085] In some embodiments, the requirement includes processing time required for the terminal device 110 to process instructions from the first network device 120, after which the terminal device 110 begins performing the type switch. In some embodiments, the interruption begins when the terminal device 110 begins performing the type switch after the processing time has elapsed.

[0086] In some embodiments, capability information may be included in the radio access control (RRC) message. Alternatively or additionally, such instructions may be included in the RRC message.

[0087] Figure 5 shows a flowchart 500 of a method performed in a first network device according to some embodiments of the present disclosure. For convenience of explanation, the method 500 will be described in terms of the first network device 120 with reference to Figure 1A.

[0088] In block 510, the first network device 120 receives capability information from the terminal device 110 indicating that the terminal device 110 supports multiple types. In block 520, the first network device 120 transmits a signal to the terminal device 110 instructing it to switch its type. In block 530, the first network device 120 determines the scheduling of the terminal device 110 based on the instruction and requirements regarding the interruption caused by the type switching in the terminal device 110.

[0089] In some embodiments, the first network device 120 can further determine its requirements based on capability information and instructions.

[0090] In some embodiments, the type of terminal device 110 may include a user equipment (UE) architecture type.

[0091] In some embodiments, capability information may further include one or more switching periods required to perform type switching, one or more switching directions, one or more cells or carriers that are permitted to be interrupted, and support for type switching to evolved general-purpose terrestrial radio access new radio dual connectivity (EN-DC) and / or non-co-located in-band new radio carrier aggregation (NR-CA).

[0092] In some embodiments, the requirement includes an interruption period, and the first network device 120 may be configured to further operate to determine the interruption period based on at least one of one or more switching periods, which corresponds to the switching direction of the switching indicated in the instruction, and one or more cells or carriers, which corresponds to the subcarrier spacing (SCS) of at least one cell or carrier. In some embodiments, the terminal device 110 may be allowed to be interrupted up to the interruption period.

[0093] In some embodiments, in order to determine scheduling, the first network device 120 may refrain from scheduling the terminal device 110 based on requirements.

[0094] In some embodiments, the multiple types may include a first type and a second type, and one or more transition periods may include a first transition period required for switching from the first type to the second type, and a second transition period required for switching from the second type to the first type. In some embodiments, the first or second transition period may be set to zero.

[0095] In some embodiments, one or more switching periods may include at least one switching period for EN-DC and at least one switching period for NR-CA.

[0096] In some embodiments, capability information may further indicate whether the interruption caused by type switching is acceptable for each of one or more switching directions.

[0097] In some embodiments, the requirement includes processing time required for the terminal device 110 to process instructions from the network device, after which the terminal device 110 begins performing the type switching. In some embodiments, the interruption begins at the point when the terminal device 110 begins performing the type switching after the processing time. In some embodiments, in order to determine the scheduling of the terminal device 110, the first network device 120 may prevent scheduling of the terminal device 110 after the processing time and within the interruption period.

[0098] In some embodiments, capability information may be included in the radio access control (RRC) message. Alternatively or additionally, such instructions may be included in the RRC message.

[0099] In some embodiments, the first network device 120 may further transmit a terminal switching instruction to the second network device 130 indicating a switch in the type of terminal device 110. In some embodiments, the terminal switching instruction may include at least one of the following: a switching period required for the terminal device 110 to perform the instructed switching, and at least one cell or carrier during which interruption is permitted.

[0100] Figure 6 shows a flowchart 600 of a method performed in a second network device according to some embodiments of the present disclosure. For convenience of explanation, the method 600 will be described in terms of the second network device 130 with reference to Figure 1A.

[0101] In block 610, the second network device 130 receives a terminal switching instruction from the first network device 120 indicating a type switch for the terminal device 110. In block 620, the second network device 130 determines the scheduling of the terminal device 110 based on the requirements regarding the interruption caused by the type switch in the terminal device 110.

[0102] In some embodiments, the second network device 130 may further determine the requirement based on a terminal switching instruction.

[0103] In some embodiments, the type of terminal device 110 may include a user equipment (UE) architecture type.

[0104] In some embodiments, the terminal switching instruction may include at least one of the following: a switching period required for the terminal device 110 to perform the instructed switching, and at least one cell or carrier during which interruption is permitted. In some embodiments, the requirement includes an interruption period, and the second network device 130 is further configured to determine the interruption period based on at least one of the switching period and the subcarrier interval (SCS) of at least one cell or carrier. In some embodiments, the terminal device 110 is permitted to be interrupted up to the interruption period.

[0105] In some embodiments, in order to determine scheduling, the second network device 130 may prevent the scheduling of the terminal device 110 based on requirements.

[0106] In some embodiments, the requirement includes processing time required for the terminal device 110 to process instructions from the network device, after which the terminal device 110 begins performing the type switching. In some embodiments, the interruption begins when the terminal device 110 begins performing the type switching after the processing time. In some embodiments, in order to determine the scheduling of the terminal device 110, the second network device 130 may refrain from scheduling the terminal device 110 after the processing time and within the interruption period.

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

[0108] In some embodiments, the device includes means for transmitting capability information indicating support for multiple types of terminal devices to a network device; means for receiving instructions from the network device to switch the type of terminal device; and means for performing the type switch based on the instructions and requirements regarding the interruption caused by the type switch.

[0109] In some embodiments, the apparatus may further include means for determining the requirements based on capability information and instructions.

[0110] In some embodiments, the terminal device type includes user equipment (UE) architecture types.

[0111] In some embodiments, capability information further includes at least one of the following: one or more switching periods required to perform type switching; one or more switching directions; one or more cells or carriers that are permitted to be interrupted; or support for type switching to evolved general-purpose terrestrial radio access new radio dual connectivity (EN-DC) and / or non-co-located in-band new radio carrier aggregation (NR-CA).

[0112] In some embodiments, the requirement includes an interruption period, and the terminal device is further configured to determine the interruption period based on at least one of one or more switching periods, which corresponds to the switching direction of the switching indicated in the instruction, and one or more cells or carriers, which corresponds to the subcarrier spacing (SCS) of at least one cell or carrier. In some embodiments, the terminal device is allowed to interrupt up to the interruption period.

[0113] In some embodiments, the plurality of types include a first type and a second type, and one or more transition periods include a first transition period required for switching from the first type to the second type and a second transition period required for switching from the second type to the first type. In some embodiments, the first or second transition period is set to zero.

[0114] In some embodiments, one or more switching periods include at least one switching period for EN-DC and at least one switching period for NR-CA.

[0115] In some embodiments, capability information further indicates whether the interruption caused by type switching is permissible for each of one or more switching directions.

[0116] In some embodiments, the requirement includes processing time required for the terminal device to process instructions from the network device, after which the terminal device begins performing the type switch. In some embodiments, the interruption begins at the point when the terminal device begins performing the type switch after the processing time.

[0117] In some embodiments, capability information is included in the radio access control (RRC) message, or the instruction is included in the RRC message.

[0118] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of Method 400. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code configured to cause the at least one processor to perform the operation of the apparatus.

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

[0120] In some embodiments, the device includes means for receiving capability information from a terminal device indicating support for multiple types of terminal devices; means for transmitting instructions to the terminal device to switch the type of terminal device; and means for determining the scheduling of the terminal device based on the instructions and requirements regarding interruptions caused by the type switching in the terminal device.

[0121] In some embodiments, the apparatus further includes means for determining requirements based on capability information and instructions.

[0122] In some embodiments, the terminal device type includes user equipment (UE) architecture types.

[0123] In some embodiments, capability information further includes at least one of the following: one or more switching periods required to perform type switching, one or more switching directions, one or more cells or carriers that are permitted to be interrupted, and support for evolved general-purpose terrestrial radio access new radio dual connectivity (EN-DC) and / or non-co-located in-band new radio carrier aggregation (NR-CA).

[0124] In some embodiments, the requirement includes an interruption period, and the first network device is further configured to determine the interruption period based on at least one of one or more switching periods, which corresponds to the switching direction of the switching indicated in the instruction, and the subcarrier spacing (SCS) of at least one cell or carrier, which corresponds to the switching direction, among one or more cells or carriers. In some embodiments, the terminal device is allowed to be interrupted up to the interruption period. In some embodiments, the means for determining scheduling includes means for preventing the scheduling of the terminal device based on the requirement.

[0125] In some embodiments, the plurality of types include a first type and a second type, and one or more transition periods include a first transition period required for switching from the first type to the second type and a second transition period required for switching from the second type to the first type. In some embodiments, the first or second transition period is set to zero.

[0126] In some embodiments, one or more switching periods include at least one switching period for EN-DC and at least one switching period for NR-CA.

[0127] In some embodiments, capability information further indicates whether the interruption caused by type switching is acceptable for each of one or more switching directions.

[0128] In some embodiments, the requirement includes processing time required for the terminal device to process instructions from the network device, after which the terminal device begins performing the type switch. In some embodiments, the interruption begins at the point when the terminal device begins performing the type switch after the processing time. In some embodiments, the means for determining the scheduling of the terminal device includes means for preventing the scheduling of the terminal device after the processing time and within the interruption period.

[0129] In some embodiments, capability information is included in the radio access control (RRC) message, or such instruction is included in the RRC message.

[0130] In some embodiments, the device further includes means for transmitting a terminal switching instruction to a second network device indicating a switch in the type of terminal device. In some embodiments, the terminal switching instruction includes at least one of the following: a switching period required for the terminal device to perform the instructed switching, and at least one cell or carrier that is permitted to be interrupted.

[0131] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of Method 500. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are configured to cause the at least one processor to perform the operation of the apparatus.

[0132] In some embodiments, an apparatus capable of performing Method 600 (e.g., a second network apparatus 130) may include means for performing each step of Method 600. These means may be implemented in any suitable form. For example, these means may be implemented as a circuit or a software module.

[0133] In some embodiments, the device includes means for receiving a terminal switching instruction from a first network device indicating a switch in the type of terminal device, and means for determining the scheduling of the terminal device based on requirements regarding the interruption caused by the type switching in the terminal device.

[0134] In some embodiments, the device further comprises means for determining requirements based on terminal switching instructions.

[0135] In some embodiments, the terminal device type includes user equipment (UE) architecture types.

[0136] In some embodiments, a terminal switching instruction includes at least one of the following: a switching period required for the terminal device to perform the instructed switching, and at least one cell or carrier during which interruption is permitted. In some embodiments, the requirement includes an interruption period, and a second network device is further configured to determine the interruption period based on at least one of the following: the switching period and the subcarrier interval (SCS) of at least one cell or carrier. In some embodiments, the terminal device is permitted to be interrupted up to the interruption period.

[0137] In some embodiments, the means for determining scheduling includes means for preventing scheduling of terminal devices based on the requirements.

[0138] In some embodiments, the requirement includes processing time required for the terminal device to process instructions from the network device, after which the terminal device begins performing the type switch. In some embodiments, the interruption begins at the point when the terminal device begins performing the type switch after the processing time. In some embodiments, the means for determining the scheduling of the terminal device includes means for preventing the terminal device from being scheduled after the processing time and within the interruption period.

[0139] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of Method 600. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are configured to cause the apparatus to perform operations by the at least one processor.

[0140] Figure 7 shows a simplified block diagram of a device 700 suitable for implementing some embodiments of the present disclosure. The device 700 may be provided for implementing a communication device, for example, a terminal device 110, a first network device 120, or a second network device 130, as shown in Figure 1A. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 720 connected to the processors 710, and one or more communication modules 740 connected to the processors 710.

[0141] The communication module 740 is for bidirectional communication. The communication module 740 is equipped with at least one antenna to enable communication. The communication interface can represent any interface necessary for communication with other network elements.

[0142] The processor 710 is of any type suitable for the technology network and, in non-limiting examples, may include one or more general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multicore processor architectures. The device 700 may comprise multiple processors, such as application-specific integrated circuit (ASIC) chips that are time-dependent to a clock that synchronizes the main processor.

[0143] Memory 720 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) 724, electrically rewritable read-only memory (EPROM), flash® memory, hard disks, compact discs (CDs), digital video discs (DVDs), and other magnetic and optical storage devices. Examples of volatile memories include, but are not limited to, random-access memory (RAM) 722 and other volatile memories that are not retained during power-off periods.

[0144] The computer program 730 includes computer executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 724. The processor 710 can perform any appropriate operations and processes by loading the program 730 into the RAM 722.

[0145] Embodiments of the present disclosure are implemented by program 730, which enables the apparatus 700 to perform any process of the present disclosure described with reference to Figures 2 and 3. Embodiments of the present disclosure can also be implemented by hardware, or by a combination of software and hardware.

[0146] In some embodiments, the program 730 may be tangibly stored on a computer-readable medium, either contained within the device 700 (for example, in memory 720) or in another storage device accessible from the device 700. The device 700 can read the program 730 from the computer-readable medium into RAM 722 for execution. The computer-readable medium includes all kinds of tangible non-volatile storage devices, such as ROM, EPROM, flash® memory, hard disk, CD, DVD, etc.

[0147] Figure 8 is a block diagram showing examples of computer-readable media 800 according to some embodiments of the present disclosure. The computer-readable media 800 stores the program 730. In Figure 8, the computer-readable media 800 is shown in the form of a CD or DVD, but the computer-readable media 800 may be in any other form suitable for recording or holding the program 730.

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

[0149] Furthermore, this disclosure provides at least one computer program product tangibly stored in a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as those contained in a program module, which are executed in a device targeting a real or virtual processor and perform the methods described above with reference to any of Figures 4 to 6. 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. The machine-executable instructions for a program module may be executed in a local or distributed device. In a distributed device, the program module may reside in both local and remote storage media.

[0150] Program code for performing the methods of this disclosure 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, and when executed by the processor or controller, it may implement 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.

[0151] In the context of this disclosure, computer program code or related data may be transmitted 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.

[0152] 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, or semiconductor systems, apparatus, or 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. As used herein, the term “non-temporary” is a limitation on the medium itself (i.e., tangible and not signaling), not on the persistence of data storage (e.g., RAM vs. ROM).

[0153] Furthermore, while the operations are shown in a specific order, this does not mean that such operations must be performed in a specific or sequential order shown to obtain the desired result, or that all illustrated operations must be performed. Under certain circumstances, multitasking or parallel processing may be advantageous. Similarly, the above description includes details of several specific embodiments, but these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of individual embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented individually or in any appropriate partial combination in multiple embodiments.

[0154] While this disclosure uses terminology specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the attached claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for carrying out 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, To transmit capability information to the network device indicating support for multiple types of terminal devices, Receiving instructions from the network device to switch the type of the terminal device, Based on the instructions and requirements regarding the interruption caused by the type change, the type change is performed, At least one memory to store instructions to execute, A terminal device equipped with the following features.

2. The aforementioned terminal device further, The system is configured to determine the requirements based on the capability information and the instructions. The terminal device according to claim 1.

3. The terminal device according to claim 1 or 2, wherein the type of the terminal device includes a user equipment (UE) architecture type.

4. The aforementioned capability information further, One or more switching periods required to perform type switching, One or more switching directions, One or more cells or carriers in which the interruption is permitted, Support for switching between the aforementioned types in the evolved general-purpose terrestrial wireless access network, new wireless dual connectivity (EN-DC) and / or non-co-located in-band new wireless carrier aggregation (NR-CA), A terminal device according to any one of claims 1 to 3, comprising at least one of the following.

5. The aforementioned requirements include a period of interruption, and the terminal device further, Of the one or more switching periods, the switching period corresponding to the switching direction indicated in the instruction, and Among the one or more cells or carriers, the subcarrier spacing (SCS) of at least one cell or carrier corresponding to the switching direction, The terminal device according to claim 4, configured to determine the interruption period based on at least one of the following.

6. The terminal device according to claim 5, wherein the terminal device is permitted to be interrupted up to the interruption period.

7. The aforementioned plurality of types include a first type and a second type, and the one or more transition periods are A first switching period required for switching from the first type to the second type, The second switching period required for switching from the second type to the first type, A terminal device according to any one of claims 4 to 6, including the terminal device described in any one of claims 4 to 6.

8. The terminal device according to claim 7, wherein the first switching period or the second switching period is set to zero.

9. The aforementioned one or more switching periods are At least one switching period for the EN-DC, At least one switching period for the NR-CA, A terminal device according to any one of claims 4 to 8, including the terminal device described in any one of claims 4 to 8.

10. The terminal device according to any one of claims 4 to 9, wherein the capability information further indicates whether an interruption caused by type switching is permissible for each of the one or more switching directions.

11. The terminal device according to any one of claims 1 to 10, wherein the requirement includes processing time required for the terminal device to process the instruction from the network device, and the terminal device starts performing the type switching after the processing time.

12. The terminal device according to claim 11, wherein the interruption is initiated when the terminal device starts executing the type switching after the processing time.

13. at least, The capability information is included in the radio access control (RRC) message, or The above instruction is included in the RRC message. The terminal device according to any one of claims 1 to 12.

14. The first network device, At least one processor, When executed by the at least one processor, the first network device will have at least, Receiving capability information from the terminal device indicating support for multiple types of the terminal device, To transmit an instruction to the terminal device to switch the type of the terminal device, Based on the aforementioned instructions and the requirements regarding interruptions caused by type switching in the terminal device, the scheduling of the terminal device is determined. At least one memory to store instructions to execute, A first network device comprising the following:

15. The first network device further includes: Based on the capability information and the instructions, the requirements are determined. The first network device according to claim 14, configured as described above.

16. The first network device according to claim 14 or 15, wherein the type of the terminal device includes a user equipment (UE) architecture type.

17. The aforementioned capability information further, One or more switching periods required to perform type switching, One or more switching directions, One or more cells or carriers in which the interruption is permitted, and Support for switching between the aforementioned types in the evolved general-purpose terrestrial wireless access network, new wireless dual connectivity (EN-DC) and / or non-co-located in-band new wireless carrier aggregation (NR-CA), A first network device according to any one of claims 14 to 16, comprising at least one of the above.

18. The above requirements include an interruption period, and the first network device further, Of the one or more switching periods, the switching period corresponding to the switching direction indicated in the instruction, and Among the one or more cells or carriers, the subcarrier spacing (SCS) of at least one cell or carrier corresponding to the switching direction, The first network device according to claim 17, configured to determine the interruption period based on at least one of the following.

19. The terminal device is the first network device according to claim 18, wherein interruptions up to the interruption period are permitted.

20. The first network device is To prevent scheduling of the terminal device based on the above requirements, The first network device according to any one of claims 14 to 19, configured to determine the scheduling by the above.

21. The aforementioned plurality of types include a first type and a second type, and the one or more transition periods are A first switching period required for switching from the first type to the second type, The second switching period required for switching from the second type to the first type, A first network device according to any one of claims 17 to 20, including the following:

22. The first network device according to claim 21, wherein the first switching period or the second switching period is set to zero.

23. The aforementioned one or more switching periods are At least one switching period for the EN-DC, At least one switching period for the NR-CA, A first network device according to any one of claims 17 to 22, including the following:

24. The first network device according to any one of claims 17 to 23, wherein the capability information further indicates whether an interruption caused by type switching is permissible for each of the one or more switching directions.

25. The requirements include the processing time required for the terminal device to process the instructions from the network device. The terminal device starts the type switching operation after the processing time. The first network device according to any one of claims 14 to 24.

26. The interruption is initiated when the terminal device starts executing the type switching after the processing time, according to the first network device of claim 25.

27. The first network device is After the processing time and within the interruption period, prevent scheduling of the terminal device. The first network device according to claim 25 or 26, configured to determine the scheduling of the terminal device by means of the above.

28. at least, The capability information is included in the radio access control (RRC) message, or The above instruction is included in the RRC message. The first network device according to any one of claims 14 to 27.

29. The first network device further includes: A terminal switching instruction indicating a switch in the type of terminal device is transmitted to the second network device. A first network device according to any one of claims 14 to 28, configured as follows.

30. The aforementioned terminal switching instruction is: The switching period required by the terminal device to perform the instructed switching, and, At least one cell or carrier in which the interruption is permitted, The first network device according to claim 29, comprising at least one of the following:

31. A second network device, At least one processor, When executed by the at least one processor, the second network device will have at least: The first network device receives a terminal switching instruction indicating a switch in the type of terminal device, The scheduling of the terminal device is determined based on the requirements regarding interruptions caused by type switching in the terminal device, At least one memory to store instructions to execute, A second network device equipped with the following:

32. The second network device further includes: Based on the terminal switching instruction, the requirements are determined. The second network device according to claim 31, configured as described above.

33. The second network device according to claim 31 or 32, wherein the type of the terminal device includes a user equipment (UE) architecture type.

34. The aforementioned terminal switching instruction is: The switching period required by the terminal device to perform the instructed switching, and At least one cell or carrier in which the interruption is permitted, A second network device according to any one of claims 31 to 33, comprising at least one of the above.

35. The aforementioned requirements include an interruption period, and the second network device further, During the VR switching period, and The subcarrier interval (SCS) of at least one cell or carrier, The second network device according to claim 34, configured to determine the interruption period based on at least one of the following.

36. The terminal device is the first network device according to claim 35, wherein interruptions up to the interruption period are permitted.

37. The second network device is Based on the above requirements, prevent scheduling of the terminal device. A second network device according to any one of claims 31 to 36, configured to determine the scheduling by the above.

38. The requirements include the processing time required for the terminal device to process the instructions from the network device. The terminal device starts the type switching operation after the processing time. The second network device according to any one of claims 31 to 37.

39. The interruption is initiated when the terminal device starts performing the type switching after the processing time, according to the second network device of claim 38.

40. The second network device is After the processing time and within the interruption period, prevent scheduling of the terminal device. The first network device according to claim 38 or 39, configured to determine the scheduling of the terminal device by means of the above.

41. In a terminal device, capability information indicating support for multiple types of the terminal device is transmitted to a network device. Receiving instructions from the network device to switch the type of the terminal device, Based on the instructions and requirements regarding the interruption caused by the type change, the type change is performed, Methods that include...

42. In the first network device, capability information indicating support for multiple types of terminal devices is received from the terminal device, To transmit an instruction to the terminal device to switch the type of the terminal device, Based on the aforementioned instructions and the requirements regarding interruptions caused by type switching in the terminal device, the scheduling of the terminal device is determined. Methods that include...

43. The second network device receives a terminal switching instruction from the first network device indicating a switch in the type of terminal device, The scheduling of the terminal device is determined based on the requirements regarding interruptions caused by type switching in the terminal device, Methods that include...

44. A terminal device includes means for transmitting capability information indicating support for multiple types of the terminal device to a network device, Means for receiving instructions from the network device to switch the type of the terminal device, Means for performing the type switching based on the instructions and requirements regarding the interruption caused by the type switching, A device equipped with the following features.

45. The first network device includes means for receiving capability information from a terminal device indicating support for multiple types of the terminal device, Means for transmitting instructions to the terminal device to switch the type of the terminal device, Means for determining the scheduling of the terminal device based on the aforementioned instructions and requirements regarding interruptions caused by type switching in the terminal device, A device equipped with the following features.

46. The second network device includes means for receiving a terminal switching instruction from the first network device indicating a switch in the type of terminal device, A means for determining the scheduling of the terminal device based on requirements regarding interruptions caused by type switching in the terminal device, A device equipped with the following features.

47. A non-temporary computer-readable medium for storing program instructions for causing a device to perform at least one of the methods of claims 41 to 43.

Images