Network indicating user equipment on delay for profile activation

Abstract

A user equipment includes at least one memory storing instructions and at least one processor configured to execute the instructions and cause the user equipment to receive (S900) a configuration message indicating a plurality of radio resource control, RRC, configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, transmit (S910) a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations, and activate (S920) the selected RRC configuration.

Description

NETWORK INDICATING USER EQUIPMENT ON DELAY FOR PROFILE ACTIVATIONBACKGROUND

[0001] A mobile telecommunication network or cellular network (generally referred to herein as a communication network) enables communications between two or more communication devices, provides communication devices access to a data network, delivers services provided by third-party applications to communication devices, or provides services offered by the communication network to communication devices.

[0002] A communication network and communication devices may operate in accordance with cellular technologies (otherwise referred to as radio access technologies), such as GSM, UTMS, LTE, LTE-A, and NR. Cellular technologies are standardized by various standards organization, such as the Third Generation Partnership Project (3 GPP) or ETSI (European Telecommunications Standards Institute). 3GPP is currently developing standards for 5th generation cellular technologies (generally referred to a 5G or NR standards) and 6th generation cellular technologies (generally referred to a 6G standards). Communication networks that operate in accordance with 5G or NR standards are generally referred to as 5G networks and communication networks that operate in accordance with 6G standards are generally referred to as 6G networks.

[0003] A communication network (e.g., a 5G network or a 6G network) includes access networks (e.g., radio access networks) that can communicate wirelessly with one or multiple communication devices by sharing available resources (e.g., bandwidth, transmit power, etc.) of the access network (e.g., radio access network). A communication network can also establish reliable, secure connectivity between communication devices and a core network of the communication network via access networks. A communication network (e.g., a 5G network) may provide enhanced mobile broadband services (e.g., telephony, video, data, short message services), ultra-reliable low-latency communication services (e.g., XR services), or massive machine type communication services to communication devices.SUMMARY

[0004] The scope of protection sought for various example embodiments of the disclosure is set out by the independent claims. The example embodiments and / or features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments.

[0005] At least one example embodiment provides a user equipment including at least one memory storing instructions and at least one processor configured to execute the instructions and cause the user equipment to receive a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, transmit a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations, and activate the selected RRC configuration.

[0006] According to at least one example embodiment, the configuration message may be an RRC message.

[0007] According to at least one example embodiment, the configuration message may be a RRC release message, a RRC reconfiguration message, or a RRC configuration message.

[0008] According to at least one example embodiment, the at least on processor is configured to execute the instructions to cause the user equipment to select the selected RRC configuration based on the plurality of network delays.

[0009] According to at least one example embodiment, the request message may be an RRC connection request message or an RRC request for profile change message.

[0010] According to at least one example embodiment, the at least one processor is configured to execute the instructions to cause the user equipment to activate the selected RRC configuration in response to at least one of receiving, from the network node, a RRC configuration message including an update to the plurality of network delays, or transmitting the request message.

[0011] According to at least one example embodiment, the at least one processor is configured to execute the instructions to cause the user equipment to transmit a confirmation message to the network node using MAC CE, the confirmation message indicating successful activation of the selected RRC configuration.

[0012] According to at least one example embodiment, the plurality of network delays may indicate an amount of time the network node takes to activate the respective RRC configurations.

[0013] According to at least one example embodiment, the plurality of RRC configurations may be arranged as a plurality of profiles.

[0014] According to at least one example embodiment, the at least one processor is configured to execute the instructions to cause the user equipment to indicate, to the network node, a requirement to activate the selected RRC configuration using user equipment (UE) assistant information.

[0015] At least one example embodiment provides an apparatus including at least one memory storing instructions and at least one processor configured to execute the instructions and cause apparatus to transmit, to a user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, receive, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations, and activate the selected RRC configuration for the user equipment.

[0016] According to at least one example embodiment, the configuration message may be an RRC message.

[0017] According to at least one example embodiment, the configuration message may be an RRC release message, an RRC configuration message, or an RRC reconfiguration message.

[0018] According to at least one example embodiment, the at least one processor is configured to execute the instructions to cause the apparatus to transmit, to the user equipment, updated network delays corresponding to the plurality of network delays, respectively, the updated network delays based on the selected RRC configuration.

[0019] According to at least one example embodiment, wherein the at least one processor is configured to execute the instructions to cause the apparatus to transmit the updated network delays by at least one of an RRC configuration message, an RRC request for profile change message, a message using medium access control (MAC) control element (CE) signaling, or a message using downlink control information (DCI) signaling.

[0020] According to at least one example embodiment, the at least one processor is configured to execute the instructions to cause the apparatus to activate the selected RRC configuration for the user equipment in response to a user equipment (UE) assistant information requirement to activate the selected RRC configuration.

[0021] According to at least one example embodiment, the at least one processor is configured to execute the instructions to cause the apparatus to activate the selected RRC configuration for the user equipment by completing network side configuration changes to activate the selected RRC configuration for the user equipment.

[0022] At least one example embodiment provides a method for activating a radio resource control (RRC) configuration, the method including receiving a configuration message indicating a plurality of RRC configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations, and activating the selected RRC configuration.

[0023] At least one example embodiment provides a method for activating a radio resource control (RRC) configuration for a user equipment, the method including transmitting, to the user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, receiving, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations, and activating the selected RRC configuration for the user equipment.

[0024] At least one example embodiment provides a non-transitory computer-readable storage medium storing computer-readable instructions that, when executed, cause one or more processors to cause a user equipment to perform a method for activating a radio resource control (RRC) configuration, the method including receiving a configuration message indicating a plurality of RRC configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations, and activating the selected RRC configuration.

[0025] At least one example embodiment provides a non-transitory computer-readable storage medium storing computer-readable instructions that, when executed, cause one or more processors to cause an apparatus to perform a method for activating a radio resource control (RRC) configuration for a user equipment, the method including transmitting, to the user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delays corresponding, respectively,with the plurality of RRC configurations, receiving, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations, and activating the selected RRC configuration for the user equipment.

[0026] At least one example embodiment provides a user equipment including a means for receiving a configuration message indicating a plurality of RRC configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, a means for transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations, and a means for activating the selected RRC configuration.

[0027] At least one example embodiment provides an apparatus including a means for transmitting, to a user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, a means for receiving, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations, and a means for activating the selected RRC configuration for the user equipment.BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Example embodiments will become more fully understood from the detailed description given herein below and the accompanying drawings, wherein like elements are represented by like reference numerals, which are given by way of illustration only and thus are not limiting of this disclosure.

[0029] FIG. 1 illustrates an example of a communication network according to example embodiments.

[0030] FIG. 2 is a comparative example of a RRC procedure delay.

[0031] FIG. 3 is a block diagram illustrating an example apparatus according to example embodiments.

[0032] FIG. 4 is a logical illustration of a RRC profile according to example embodiments.

[0033] FIG. 5 is a signaling diagram illustrating a method according to example embodiments.

[0034] FIG. 6 is a signaling diagram illustrating a method according to example embodiments.

[0035] FIG. 7 is a signaling diagram illustrating a method according to example embodiments.

[0036] FIG. 8 is a signaling diagram illustrating a method according to example embodiments.

[0037] FIG. 9 is a flowchart illustrating a method according to example embodiments.

[0038] FIG. 10 is a flowchart illustrating a method according to example embodiments.

[0039] FIG. 11 is a flowchart illustrating a method according to example embodiments.

[0040] FIG. 12 is a flowchart illustrating a method according to example embodiments.

[0041] It should be noted that these figures are intended to illustrate the general characteristics of methods, structure and / or materials utilized in certain example embodiments and to supplement the written description provided below. These drawings are not, however, to scale and may not precisely reflect the precise structural or performance characteristics of any given embodiment, and should not be interpreted as defining or limiting the range of values or properties encompassed by example embodiments. The use of similar or identical reference numbers in the various drawings is intended to indicate the presence of a similar or identical element or feature.DETAILED DESCRIPTION

[0042] The following embodiments are exemplary. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Further, when a particular feature, structure, or characteristic is described in connection of an embodiment, it is within the knowledge of one skilled in the art to apply such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. It shall be understood that although the terms “first,” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0043] For the purposes of the present disclosure, the phrases “at least one of A or B”, “at least one of A and B”, and “A and / or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0044] Embodiments described may be implemented in a communication network, such as any of the following radio access technologies (RATs): Worldwide Interoperability for MicrowaveAccess (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LIE), LIE- Advanced, and enhanced LTE (eLTE), 5G (also called NR), or any future RAT such as 6G. Moreover, communication within the communication network may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT-s-OFDM).

[0045] As used herein, the term “network device” or “network node” refers to a node in a communication network via which user equipment may access the network and / or which is capable of controlling radio communication and managing radio resources within a cell. The network node or network device may be referred to as a base station (BS), an access point (AP) or an access node. The network device may be, depending on the applied technology, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node, a non-terrestrial network (NTN) or nonground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, or an aircraft network device.

[0046] Moreover, in connection of split radio access network (RAN), the network device may refer to a centralized unit (CU) of a base station and / or a distributed unit (DU) of a base station. An interface between CU and DU may be referred to as an Fl interface in NR In the split RAN architecture, node operations may be carried out, at least partly, in the central / centralized unit, CU, (e.g. server, host or node) operationally coupled to the DU, (e.g. a radio head / node). One CU may control one or more DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some embodiments, the Dus may comprise e.g. a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the CU may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layer. Other functional splits are possible too. In practice, any processing task may beperformed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may depend on the applied implementation.

[0047] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example, a terminal device may be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may include a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computer, desktop computer, image capture terminal device such as a digital camera, gaming terminal device, music storage and play-back appliance, vehicle-mounted wireless terminal device, USB dongle, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wire-less devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like.

[0048] A term “resource”, as used herein, may refer to radio resources in time domain, in frequency domain, in space domain, and / or in code domain. Some examples of resources include e.g. a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. The term “transmission” and / or “reception” may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on radio resources.

[0049] FIG. 1 illustrates an example of a communication network to which examples disclosed herein may be applied. The communication network or a cellular communication network may comprise a network node 110 providing one or more cells, such as cell 100, and a network node 112 providing one or more other cells, such as cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding access node.

[0050] The network node 110 may provide a user equipment (UE) 120 (one or more UEs) with wireless access to the communication network. The wireless access may comprise downlink (DL) communication from the network node to the UE 120 and uplink (UE) communication from the UE 120 to the network node. Examples of uplink channels comprise physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channels comprisephysical downlink control channel (PDCCH) for transmitting control information and physical downlink shared channel (PDSCH) for trans-mitting data towards the user equipment.

[0051] There may be a plurality of UEs 120, 122 in the system. Each of them may be served by the same or by different network nodes 110, 112. A UE may be configured with dual connectivity (DC), wherein the UE, e.g. UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to-device (D2D) communication interface is established between them via a so-called sidelink (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0052] In the case of multiple network nodes in the communication network, the network nodes may be connected to each other via an interface. LTE specifications call such an interface as X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes may be called Xn interface.

[0053] The network nodes 110 and 112 may be further connected via another interface to a core network 116 of the communication network. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise e.g. a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signaling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). The 5G core may comprise e.g. an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other functions. The AMF may handle termination of non-access stratum (NAS) signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example.

[0054] With the advancement of communications technology, a multitude of user equipments (UEs) have been introduced encompassing diverse UE capabilities and catering many different services. These UE types could be intended for offering divergent performance metrics such as high-speed data connectivity, enhanced energy efficiency or ultra-low latency to suit the expected use cases. In the 6G era, with the enhanced range of applications with dissimilar characteristics,such as augmented / virtual reality (AR / VR), massive twinning, immersive smart cities, holographic communications, remote surgery, ambient-IoT, V2X, etc., more customized devices for each of these use cases may be introduced. The identification, interoperability, and coherent management of these various types of UEs may be one of the continuing challenges faced by the telecommunication systems.

[0055] Cellular mobile telecommunication systems are built on top of protocols that control how the data is transmitted between UEs and networks (NWs). These protocols are often divided into user plane (UP) and control plane (CP) sections, wherein the user plane is dedicated to the actual task of transmitting user data between a UE and the NW, the CP is used to maintain operationality of the UP. That means, the CP is used for establishing the UP, and it is the task of CP to ensure the uninterrupted functioning of the UP.

[0056] The primary protocol used for the CP in universal mobile telecommunication system (UMTS) / long term evolution (LTE) / new radio (NR) is the Radio Resource Control (RRC), whose specifications can be found in TS 25.331 (UMTS), TS 36.331 (LTE) and TS 38.331 (NR). The RRC specifications define the mechanisms for setting up the connection, establishing other user plane (UP) protocol layers and reconfiguring their parameters, as well as various procedures intended to maintain both UP and CP operations.

[0057] One objective of The 3rdGeneration Partnership Project (3GPP) is to identify the shortcomings of 5G protocol design and recognize areas of improvements that should lead to the foundation of designs for 6G. The current 5G RRC protocol has evolved through several releases to contain a stable structure, but remains mostly monolithic and complex, with inherent procedural delays imposed for basic operations. Moreover, the same RRC configuration is often repeated many times for the same UE, which results in an inefficient use of the radio resources.

[0058] One or more example embodiments facilitate increased energy efficiency. Thus, one or more example embodiments may support a diverse range of applications with dissimilar requirements, such as augmented / virtual reality (AR / VR), massive twinning, immersive smart cities, holographic communications, remote surgery, etc. This diverse range of applications would inherently benefit from a modular structured design which enables efficient RRC operations with low latency.

[0059] FIG. 2 is a comparative example of a UE side activation delay for RRC configuration.

[0060] The RRC message processing requirements for NR are described in section 12 of 3 GPPSpecification TS38.331. The performance requirement is expressed as the time in ms from the end of reception of the RRC DL command 21 until the UE is ready for the RRC UL response 24 with no access delay other than the transmission time interval (TH)-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronization). The RRC procedure delay 22 indicates the UE side RRC configuration activation delay from the time the UE receives the RRC DL Command 21 containing the activation request from the NW to the time the UE is ready to receive the UL grant 23.

[0061] In case the RRC procedure triggers bandwidth part (BWP) switching, the RRC procedure delay is defined by a look up table plus the BWP switching delay defined in TS 38.133, clause 8.6.3. For example, the RRC procedure delay may be a static delay defined based on a greatest amount of time needed for the RRC procedure.

[0062] RRC profiles-based communication of the RRC configuration to a UE 120 / 122, according to some example embodiments, may allow the NW (e.g., a gNB 110 / 112) to communicate multiple RRC configurations (e.g., RRC profiles) with different characteristics for storage at the UE 120 / 122. An RRC profile is an RRC configuration sent by the network (e.g., gNB 110), stored by the UE, and used when instructed by the network. According to some example embodiments, one of the RRC profiles would be active at a time. The stored profiles may be activated later based on the UE / NW requirements.

[0063] According to some example embodiments, the gNB 110 / 112 may communicate the delay (e.g., network delay) it takes to activate each, or one or more, of the RRC profiles at the gNB 110 / 112 when the gNB 110 / 112 sends the profile configurations to the UE 120 / 122 for storage. The UE 120 / 122 can indicate the most suitable profile to activate considering the NW delay for activating the profiles as per its current requirements.

[0064] For example, if the UE 120 / 122 is moving from a power saving profile to a profile which facilitates higher data rates and needs the RRC configuration to be activated quickly, the UE 120 / 122 can select a stored profile which has indicated a lower network delay for the NW side activation out of the stored RRC profiles and suggest the selected profile to the gNB 110 / 112.

[0065] FIG. 3 is a block diagram illustrating an example apparatus according to example embodiments.

[0066] FIG. 3 shows, by way of example, a block diagram of an apparatus 10. The apparatus 10 comprises, for example, at least one processor 12 and at least one memory 14 storinginstructions 15 that, when executed by the at least one processor, cause the apparatus 10 at least to perform the method or methods as disclosed herein, and any of the embodiments thereof. In an example, the at least one memory and the instructions (e.g. a computer program code, software), are configured, with the at least one processor, to cause the apparatus 10 to perform the method or methods as disclosed herein, and any of the embodiments thereof.

[0067] A processor 12 may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with example embodiments described herein. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and / or digital circuitry, and (b) combinations of hardware circuits and software, such as, as applicable: (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a user equipment, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0068] The memory 14 may be implemented using any suitable data storage technology. The memory may comprise a database for storing data. The memory 14 may be at least in part external to apparatus 10 but accessible to apparatus 10.

[0069] The instructions 15 may be comprised in a computer readable medium or a non-transitory computer readable medium. A term non-transitory, as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. random-access memory (RAM) vs. read-only memory (ROM)).

[0070] For example, the apparatus 10 is a terminal device, such as the UE 120 / 122 of FIG. 1.As another example, the apparatus is comprised in such a terminal device, e.g. as a chipset configured to control the terminal device. The apparatus 10 may be caused or configured to perform at least the UE functions shown in FIGS. 5-8, the method of FIGS. 9 and 11 and / or any one or more of the embodiments described.

[0071] As another example, the apparatus 10 is a network node, e.g. the network node 110 / 112 of FIG. 1. In another embodiment, the apparatus is comprised in such a network node, e.g. as a chipset configured to control the network node. The apparatus 10 may be caused or configured to perform at least the method the gNB functions shown in FIGS. 5-8, the method of FIGS. 10 and 12, and / or any one or more of the embodiments described.

[0072] The apparatus may comprise one or more entities of any of protocol layers, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity or a PHY entity. In some embodiments, the entity is configured to perform at least the UE functions shown in FIGS. 5-8, the gNB functions shown in FIGS. 5-8, the method of FIGS. 9 and 11, the method of FIGS. 10 and 12, and / or any one or more of the embodiments described.

[0073] The apparatus 10 comprises a radio interface 16. The radio interface 16 may provide the apparatus 10 with communication capabilities. The radio interface 16 may comprise a receiver configured to receive information in accordance with at least one cellular or non-cellular standard. The radio interface 16 may comprise a transmitter configured to transmit information in accordance with at least one cellular or non-cellular standard. The receiver may comprise more than one receiver. The transmitter may comprise more than one transmit-ter. The radio interface 16 may comprise a transceiver configured to receive and transmit information in accordance with at least one cellular or non-cellular standard. The transceiver may comprise more than one transceiver.

[0074] The apparatus 10 may comprise a user interface 18 comprising, for example, at least one of a keypad, a microphone, a touch display, a display, a speaker, etc. The user interface 18 may be used to control the apparatus by the user. The user interface 18 may be external to the apparatus 10. For example, the apparatus 10 may be connected to another device, such as a computer, either via wireless or wired connection, and the apparatus 10 is controlled by the user via the computer.

[0075] In an embodiment, at least some of the processes described herein may be carried out by an apparatus comprising means for carrying out at least some of the described processes. Meansfor performing method steps as disclosed herein may include software and / or hardware components of the apparatus 10. For example, the at least one processor 12, the memory 14, and the computer program code form means for carrying out the method or methods as disclosed herein, and any of the embodiments thereof. As used herein the term “means” is to be construed in singular form, i.e. referring to a single element, or in plural form, i.e. referring to a combination of single elements. Therefore, terminology “means for [performing A, B, C]”, is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C. Further, terminology “means for performing A, means for performing B, means for performing C” is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.

[0076] For conciseness, example embodiments will be discussed with reference to gNB 110 and UE 120, however example embodiments are not limited to this example. For example, operations described as being performed by the gNB 110 could be performed by the gNB 112 and / or operations performed by the UE 120 could be performed by the UE 122.

[0077] FIG. 4 is a logical illustration of a RRC profile according to example embodiments.

[0078] Groups of bearers and / or carrier components within a RRC configuration (e.g., a RRC profile) can be formed into RRC configuration threads (RCTs). The RCTs may have respective identifiers. Each thread configures those radio bearers / carrier components to have particular operating characteristics.

[0079] A group or set of configured and activated RCT’s form a final, total or complete RRC configuration (or a RRC profile) for a given user equipment (UE).

[0080] Referring to FIG. 4, a RRC configuration may include three RCTs RCT T1, RCT T2, and / or RCT T3. However, example embodiments are not limited to this example and a RRC configuration may include fewer or greater than three RCTs. RCT T1 is formed from a group of (e.g., RCT T1 includes) configuration components of different protocol layers for Signaling Radio Bearer (SRB) SRBl-SRBn and for Component Carrier (CC) CC1-CC2. As shown in FIG. 4, RCT T1 is formed from the group of configuration components (e.g., RCT T1 includes) RRCl-RRCn, Packet Data Convergence Protocol (PDCP) PDCPl-PDCPn, Radio Link Control (RLC) RLC1-RLCn, CC1-CC2 (Medium Access Control (MAC) layer) and CC1-CC2 (Physical (PHY) layer).

[0081] RCT T2 is formed from a group of (e.g., RCT T2 includes) configuration components of different protocol layers for DRB1-DRB2 and for CC3-CC5. As shown in FIG. 4, RCT T2 is formed from the group of configuration components Service Data Adaptation Protocol (SDAP) SDAPD1-SDAPD2, PDCPD1-PDCPD2, RLCD1A-RLCD2B, CC3-CC5 (MAC layer) and CC3-CC5 (Physical layer). RLCD1A and RLCD2A are related to CC3-CC4 (MAC layer) and CC3-CC4 (Physical layer), while RLCD1B and RLCD2B are related to CC5 (MAC layer) and CC5 (Physical layer).

[0082] RCT T3 is formed from a group of (e.g., RCT T3 includes) configuration components of different protocol layers for DRB3-DRBn and for CCn. As shown in FIG. 4, RCT T3 is formed from the group of configuration components SDAPD3-SDAPDn, PDCPD3-PDCPDn, RLCD3-RLCDn, CC5-CCn (MAC layer) and CC5-CCn (Physical layer).

[0083] According to some example embodiments, if the profiles are arranged as RCTs, the gNB 110 may inform the UE 120 of a network delay for activating each RCT. The UE 120 may be able to decide and inform the most preferred RCT to add to its active profile by considering the network delay the gNB 110 would take to activate the RCT.

[0084] Since the UE 120 according to example embodiments knows in advance the amount of time (e.g., network delay) that the NW will take for the profile change or the RCT addition, the UE 120 may target to complete the corresponding UE side changes within this time. For example, the UE 120 may use parallel activation of some modules or parameters to complete the profile change or RCT addition quickly and prepare to use the updated configuration in a deterministic manner.

[0085] If the UE 120 is connected to two different NWs with RRC profiles stored for both of the NWs, then the UE 120 can use the network delay indication from each NW for each profile to choose the most suitable NW for changing to a different profile quickly for activating a service the UE 120 needs to activate quickly (for example in multi-USIM (MUSIM) usage).

[0086] FIG. 5 is a signaling diagram illustrating a method according to example embodiments.

[0087] The signaling diagram shown in FIG. 5 illustrates a message sequence, according to some example embodiments, for the gNB 110 indicating the delay for profile activation and the UE 120 selecting the most suitable profile considering the delay during initial access (e.g., returning from an idle / inactive mode).

[0088] Referring to FIG. 5, at Bl the UE 120 communicates with the gNB 110 via UL / DLtransmissions. For example, the UE 120 may be in a connected mode with the gNB 110. For example, the connected mode may be an RRC connection. For example, the UE 120 may have established an RRC connection with the gNB 110 prior to Bl according to any known method. At B2, the gNB 110 determines to suspend the RRC connection of the UE 120 and transfer the UE 120 to an inactive / idle mode. For example, the gNB 110 may determine to suspend the RRC connection of the UE 120 based on activity of the UL / DL data transmission between the UE 120 and the gNB 110. For example, the gNB 110 may determine to suspend the RRC connection if the UE 120 does not exchange data with the network (e.g., the gNB 110) for a specified period. For example, the gNB 110 may determine to suspend the RRC connection if the UE 120 does not exchange data with the gNB 110 for a period of 3 minutes.

[0089] The gNB 110 may determine RRC profiles to be stored at the UE 120 when the RRC connection is changed to the inactive / idle mode. For example, the gNB 110 may determine to keep RRC profile 1, RRC profile 2, and RRC profile 3 stored at the UE 120. However, example embodiments are not limited to this example and the gNB 110 may determine different profiles to be stored at the UE 120. For example, the gNB 110 may determine more than 3 or fewer than 3 profiles to be stored at the UE 120.

[0090] At B3, the gNB 110 sends a release message and / or a suspend configuration message to the UE 120. The suspend configuration message may be referred to as a configuration message and / or a reconfiguration message. For example, the gNB 110 may send an RRCRelease message to the UE 120. The RRCRelease message may include a SuspendConfig message.

[0091] For example, the RRCRelease message may include the SuspendConfig message when the gNB 110 determines to transfer the UE 120 to the inactive state. For example, in the inactive state, the UE 120 may maintain a logical connection with the gNB 110 for quick resumption. In the inactive state, the UE 120 can be paged by both the core network and / or the RAN. The connection to the gNB 110 may be resumed faster from the inactive state than from the idle state.

[0092] The RRCRelease message may not include the SuspendConfig message when the gNB 110 determines to transfer the UE 120 to the idle state. For example, in the idle state the UE 120 is not connected to the gNB 110 at the RRC level and instead relies on core network paging. The idle state may facilitate increased power saving compared to the inactive state.

[0093] According to some example embodiments, the release message and / or a suspend configuration message may be sent based on MAC control element (CE) signaling. However,example embodiments are not limited to this example. For example, according to some example embodiments the release message and / or a configuration message may be sent through downlink control information (DCI) signaling.

[0094] The suspend configuration message may include identifications (ID)s of the RRC profile(s) to be stored at the UE 120. The suspend configuration message may additionally include an indication of the network delay needed by the gNB 110 to activate each profile.

[0095] For example, the suspend configuration message may indicate a network delay for activating profile 1 = 12ms, a network delay for activating profile 2 = 6ms, and / or a network delay for activating profile 3 = 8ms. However, these example network delay times are provided only as an example, and example embodiments are not limited to this example. For example, the network delay times may be individually determined by the gNB 110 at the time of sending the suspend configuration message. According to some example embodiments, the gNB 110 may determine the network delays (e.g., delay for activating a respective profile at the gNB 110 side) based on at least one of a network load at the gNB 110, a priority of the UE 120, etc.

[0096] According to some example embodiments, the suspend configuration message may indicate a validity time for the respective network delays. For example, the suspend configuration message may indicate that the network delay for activating profile 1 = 12 ms and that this network delay is valid for 3 minutes from the time the suspend configuration message is sent. However, example embodiments are not limited to this example. For example, the gNB 110 may determine the validity times based on the respective profile configuration and / or a NW load. If the UE 120 initiates access to the gNB 110 after the expiration of the validity time indicated for the respective profile, the network delay for profile activation included in the suspend configuration message would not be applicable.

[0097] At B4, the UE 120 enters the inactive / idle mode according to the release message (e.g., RRCRelease) and / or the suspend configuration message (e.g., SuspendConfig). TheUE 120 stores (e.g., continues to store) only the profiles indicated in the configuration message, along with the associated network delays and / or validity times.

[0098] At B5, the UE 120 determines to initiate an active connection to the gNB 110. For example, the UE 120 may want to establish the active connection quickly. For example, if the UE 120 is quickly moving from a power saving profile to a profile which facilitates higher data rates and / or in MUSIM usage.

[0099] According to some example embodiments, the UE 120 may consider the network delays indicated by the suspend configuration message when determining a profile to request a connection with the gNB 110. For example, the UE 120 may weigh the network delay time along with other characteristics of the profiles when determining which profile to request. For example, the UE 120 may determine a profile to request based on a type of the profile (e.g., a profile intended to provide power saving operations vs a profile intended to provide a higher throughput). The UE 120 may compare the types of profiles available with a current service requirement of the UE 120.

[0100] For example, the UE 120 may select a profile with a shortest delay time. In this example, the UE 120 may select profile 2, since profile 2 is indicated as having a lowest network delay time among profile 1, profile 2, and profile 3. However, example embodiments are not limited to this example.

[0101] At B6, the UE 120 initiates an RRC connection with the gNB 110 indicating the selected profile (e.g., profile 2). For example, the UE 120 may send a connection request message (e.g., RRCSetup and / or RRCResume) to the gNB 110 indicating the selected profile. For example, the connection request message may indicate a request for RRC setup / resume and may indicate the selected profile. According to some example embodiments, the connection request message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. For example, according to some example embodiments the connection request message may be sent through DCI signaling. According to some example embodiments, the UE 120 may activate (e.g., begin to activate) the selected RRC profile when the UE 120 sends the connection request message. For example, the UE 120 may not wait for a response from the gNB 110 before beginning to activate the selected RRC profile and may instead begin to activate the selected profile at the same time as sending the connection request message in anticipation of confirmation from the gNB 110.

[0102] At B7, the gNB 110 considers the connection request from the UE 120 and determines to activate the requested RRC profile. For example, if the requested profile would require higher resources than the gNB 110 can provide, the gNB 110 may decline the request (e.g., at times of high congestion). If the gNB 110 determines to decline the request, the gNB 110 may send a message to the UE 120 indicating the request is denied and the method ends. If the gNB 110 determines to activate the requested RRC profile, the method continues to B8.

[0103] At B8, the gNB 110 sends an RRC configuration message (e.g., RRCReconfiguration)to the UE 120 to activate the requested RRC profile. According to some example embodiments, the RRC configuration message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. For example, according to some example embodiments the RRC configuration message may be sent through DCI signaling.

[0104] The RRC configuration message includes the network delay for activating each profile at the gNB 110 considering the new active profile. For example, the RRC configuration message may include additional profiles not currently stored at the UE 120 (e.g., RRC profile 4). If the RRC configuration message includes such additional profiles, the RRC configuration message may include a corresponding new profile configuration for storage (and for use during future activation) at the UE 120.

[0105] Because the profiles included in the RRC configuration message may be different from the profiles stored (e.g., previously stored) at the UE 120, the time to activate the profiles at the gNB 110 (e.g., NW delays) may be different. For example, the profile 2 configuration (e.g., the active profile) may be more similar to profile 3 than to profile 1 (e.g., the previously active profile). A NW delay to activate profile 3 from profile 2 may be less than a NW delay to activate profile 3 from profile 1. The NW delays may also vary according to NW load, resource availability, etc.

[0106] For example, in the above example where the UE 120 selects profile 2, the configuration message includes an indication of a network delay for activating profile 1 from profile 2 (e.g., 6ms) and a network delay for activating profile 3 from profile 2 (e.g., 10ms). However, example embodiments are not limited to this example.

[0107] According to some example embodiments, the configuration message may indicate a validity time for the respective network delays. For example, the configuration message may indicate that the network delay for activating profile 1 from profile 2 is 6ms and that this delay is valid for 3 minutes from the time the configuration message is sent. However, example embodiments are not limited to this example. If the UE 120 initiates activation of a profile after the expiration of the validity time indicated for the respective profile, the delay for profile activation included in the configuration message would not be applicable.

[0108] At B9, the gNB 110 activates the selected profile for the UE 120 in the associated network delay time. For example, in the above example, the gNB 110 activates profile 2 for the UE 120 and the activation takes 6ms. However, example embodiments are not limited to this example. According to some example embodiments, the gNB 110 may activate the selected profilefor the UE 120 by allocating necessary radio resources required to facilitate the new configuration (e.g., the configuration of the selected RRC configuration profile) for the UE 120.

[0109] At B10, the UE 120 changes to the selected profile. According to some example embodiments, since the UE 120 knows in advance the network delay that the gNB 110 will take to activate the selected profile, (e.g., 6ms to activate profile 2), the UE 120 may target to complete the profile change within this time. For example, the UE 120 can use parallel activation of some modules or parameters to complete the profile change quickly and prepare for data transmission with the new profile configuration. For example, if the selected profile configuration contains certain modules or parameters which can be activated by the UE 120 in parallel independently, the UE 120 may activate such modules and / or parameters to speed up the operation and be ready in time that the gNB 110 completes the NW side activation of the profile.

[0110] At Bll, the UE 120 sends a configuration success message (e.g., RRCReconfigurationComplete) to the gNB 110 confirming the profile activation is successful. According to some example embodiments, the configuration success message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example.

[0111] According to some example embodiments, the configuration success message may include UE delays for profile activation at the UE 120 considering the new active profile. For example, in the example where the UE 120 activates profile 2, the configuration success message may include UE delays for activating profile 1 from profile 2, profile 3 from profile 2, and / or profile 4 from profile 2. However, example embodiments are not limited to this example. According to example embodiments, the UE delays may indicate a time needed by the UE for activating associated modules, parameters, etc. for the respective profiles.

[0112] Thus, according to example embodiments, the UE 120 may more quickly and or more efficiently activate an RRC configuration profile based on known network delay times for activating the profile. For example, because the UE 120 knows in advance the network delay for activating the profile at the gNB 110, the UE 120 may begin and / or complete activation of the RRC profile (e.g., parallel to the activation at the gNB 110, activate some or all component modules within the profile) within the period of the NW delay and be ready to receive a UL grant for initiating data more quickly. FIG. 6 is a signaling diagram illustrating a method according to example embodiments.

[0113] The signaling diagram shown in FIG. 6 illustrates a message sequence, according tosome example embodiments, for the gNB 110 indicating the delay for profile activation and the UE 120 selecting the most suitable profile considering the delay to change profiles.

[0114] Referring to FIG. 6, the UE 120 begins in a connected mode with the gNB 110. For example, the connected mode may be an RRC connection (e.g., an ongoing RRC connection). For example, the UE 120 may have established an RRC connection with the gNB 110 prior to Cl according to any known method.

[0115] At Cl, the gNB 110 configures the UE 120 with RRC profiles. For example, the gNB 110 may transmit an RRC configuration message (e.g., RRCReconfiguration) to the UE 120. According to some example embodiments, the RRC configuration message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. For example, according to some example embodiments the RRC configuration message may be sent through DCI signaling.

[0116] The RRC configuration message may include RRC configuration information for a plurality of RRC profiles. For example, the RRC configuration message may include RRC configuration information for three RRC profiles, profile 1, profile 2, and profile 3. However, example embodiments are not limited to this example. For example, the RRC configuration message may include RRC configuration information for more or fewer than three profiles.

[0117] The RRC configuration message may indicate a profile, of the plurality of profiles, for the UE 120 to activate. For example, the RRC configuration message may inform the UE 120 to activate RRC profile 1. However, example embodiments are not limited to this example.

[0118] For example, at the initial stage at RRC connection setup, the gNB 110 assigns the initial RRC configuration. After an exchange of UE capability information from the UE 120 (e.g., at Cl) the gNB 110 sends the RRC configuration message to assign an optimized RRC configuration (e.g., assign a profile for the UE 120 to activate).

[0119] In some example embodiments, the RRC configuration message includes both of the RRC configuration information for storage at the UE 120 and the indication of a profile to activate at the UE 120. However, example embodiments are not limited to this example and the gNB 110 may send separate messages for the RRC configurations storage and the RRC profile activation, respectively.

[0120] According to some example embodiments, the RRC configuration message may include an indication of the network delay needed by the gNB 110 to activate each profile basedon the active profile. For example, the RRC configuration message may indicate a network delay for activating profile 2 from profile 1 = 12ms and / or a network delay for activating profile 3 from profile 1 = 6ms, and / or a network delay for activating profile 3 = 8ms. However, these example network delay times are provided only as an example, and example embodiments are not limited to this example. For example, the network delay times may be individually determined by the gNB 110 at the time of sending the RRC configuration message.

[0121] According to some example embodiments, the RRC configuration message may indicate a validity time for the respective network delays. For example, the RRC configuration message may indicate that the network delay for activating profile 2 from profile 1 = 12ms and that this network delay is valid for 3 minutes from the time the message is sent. However, example embodiments are not limited to this example. For example, the gNB 110 may determine the validity times based on the respective profile configuration and / or a NW load. If the UE 120 initiates activation of a profile after the expiration of the validity time indicated for the respective profile, the network delay for profile activation included in the RRC configuration message would not be applicable.

[0122] At C2, the UE 120 activates the profile indicated in the RRC configuration message. For example, the UE 120 activates profile 1 in response to the RRC configuration message informing the UE 120 to activate RRC profile 1. However, example embodiments are not limited to this example. The UE 120 stores the profiles indicated in the RRC configuration message along with the associated network delays and / or validity times.

[0123] At C3, the UE 120 sends a configuration success message (e.g., RRCReconfigurationComplete) to the gNB 110 confirming the profile activation is successful. According to some example embodiments, the configuration success message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example.

[0124] According to some example embodiments, the configuration success message may include UE delays for profile activation at the UE 120 considering the new active profile. For example, in the example where the UE 120 activates profile 1, the configuration success message may include UE delays for activating profile 2 from profile 1 and / or UE delays for activating profile 3 from profile 1. However, example embodiments are not limited to this example.

[0125] At C4, the UE 120 determines to change to a different active profile. For example, the UE 120 may want to change to the different active profile quickly. For example, if the UE 120 isquickly moving from a power saving profile to a profile which facilitates higher data rates and / or in MUSIM usage.

[0126] According to some example embodiments, the UE 120 may consider the network delays indicated by the RRC configuration message when determining a profile to change to. For example, the UE 120 may weigh the network delay time along with other characteristics of the profiles when determining which profile to change to.

[0127] For example, the UE 120 may select a profile with a shortest delay time. In this example, the UE 120 may select profile 3 since profile 3 is indicated as having a lowest network delay time among profile 2 and profile 3. However, example embodiments are not limited to this example.

[0128] At C5, the UE 120 requests a profile change from the gNB 110. For example, the UE 120 may send a request for profile change message to the gNB 110 indicating the selected profile. According to some example embodiments, the request for profile change message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example.

[0129] According to some example embodiments, the UE 120 may activate (e.g., begin to activate) the selected RRC profile when the UE 120 sends the connection request message. For example, the UE 120 may not wait for a response from the gNB 110 before beginning to activate the selected RRC profile and may instead begin to active the selected profile at the same time as sending the connection request message in anticipation of confirmation from the gNB 110.

[0130] At C6, the gNB 110 considers the profile change request from the UE 120 and determines to activate the requested RRC profile. For example, if the requested profile would require higher resources than the gNB 110 can provide, the gNB 110 may decline the request (e.g., at times of high congestion). If the gNB 110 determines to decline the request, the gNB 110 may send a message to the UE 120 indicating the request is denied and the method ends. If the gNB 110 determines to activate the requested RRC profile, the method continues to C7.

[0131] At C7, the gNB 110 sends an RRC profile change message to the UE 120 to activate the requested RRC profile. According to some example embodiments, the RRC profile change message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. For example, according to some example embodiments the RRC profile change message may be sent through DCI signaling.

[0132] The RRC profile change message includes the network delay for activating each profileat the gNB 110 considering the new active profile. According to some example embodiments, the gNB 110 may determine the network delays (e.g., delay for activating a respective profile at the gNB 110 side) based on at least one of a network load at the gNB 110, a priority of the UE 120, etc.

[0133] For example, in the above example where the UE 120 selects profile 3, the RRC profile change message includes an indication of a network delay for activating profile 1 from profile 3 (e.g., 6ms) and a network delay for activating profile 2 from profile 3 (e.g., 10ms). However, example embodiments are not limited to this example.

[0134] According to some example embodiments, the RRC profile change message may indicate a validity time for the respective network delays. For example, the RRC profile change message may indicate that the network delay for activating profile 1 from profile 3 is 6ms and that this delay is valid for 3 minutes from the time the RRC profile change message is sent. However, example embodiments are not limited to this example. For example, the gNB 110 may determine the validity times based on the respective profile configuration and / or a NW load. If the UE 120 initiates activation of a profile after the expiration of the validity time indicated for the respective profile, the delay for profile activation included in the RRC profile change message would not be applicable.

[0135] At C8, the gNB 110 activates the selected profile for the UE 120 in the associated network delay time. For example, in the above example, the gNB 110 activates profile 3 for the UE 120 and the activation takes 6ms. However, example embodiments are not limited to this example.

[0136] At C9, the UE 120 changes to the selected profile. According to some example embodiments, since the UE 120 knows in advance the network delay that the gNB 110 will take to activate the selected profile, (e.g., 6ms to activate profile 3), the UE 120 may target to complete the profile change within this time. For example, the UE 120 can use parallel activation of some modules or parameters to complete the profile change quickly and prepare for data transmission with the new profile configuration.

[0137] At CIO, the UE 120 sends an RRC profile change success message (e.g., RRCReconfigurationComplete) to the gNB 110 confirming the profile change is successful. According to some example embodiments, the RRC profile change success message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example.According to some example embodiments, the RRC profile change success message may include UE delays for profile activation at the UE 120 considering the new active profile. For example, in the example where the UE 120 activates profile 3, the RRC profile change success message may include UE delays for activating profile 1 from profile 3 and / or UE delays for activating profile 2 from profile 3. However, example embodiments are not limited to this example.

[0138] Thus, according to example embodiments, the UE 120 may more quickly and or more efficiently change an active RRC configuration profile based on known network delay times for activating the profile. For example, because the UE 120 knows in advance the network delay for activating the profile at the gNB 110, the UE 120 may begin or complete activation of the RRC profile (e.g., activate some or all component modules within the profile parallel to the activation at the gNB) within the period of the NW delay and be ready to receive a UL grant for initiating data more quickly.

[0139] FIG. 7 is a signaling diagram illustrating a method according to example embodiments.

[0140] The signaling diagram shown in FIG. 7 illustrates a message sequence, according to some example embodiments, for the gNB 110 indicating the delay for profile activation and the UE 120 selecting the most suitable profile considering the delay and indicating the change using UE Assistance Information (UAI).

[0141] Referring to FIG. 7, the UE 120 begins in a connected mode with the gNB 110. For example, the connected mode may be an RRC connection (e.g., an ongoing RRC connection). For example, the UE 120 may have established an RRC connection with the gNB 110 prior to DI according to any known method.

[0142] DI to D4 may be the same as Cl to C4, respectively, described above. Repeated description is therefore omitted.

[0143] At D5, the UE 120 requests a profile change from the gNB 110. For example, the UE 120 may send a UE assistance information (UAI) request for the profile change to the gNB 110 indicating the selected profile (e.g., change to profile 3).

[0144] According to some example embodiments, the UE 120 may activate (e.g., begin to activate) the selected RRC profile when the UE 120 sends the UAI request for the profile change. For example, the UE 120 may not wait for a response from the gNB 110 before beginning to activate the selected RRC profile and may instead begin to active the selected profile at the same time as sending the UAI request for the profile change in anticipation of confirmation from thegNB 110.

[0145] At D6 the gNB 110 considers the profile change request from the UE 120 and determines to activate the requested RRC profile.

[0146] At D7, the gNB 110 sends an RRC profile change message to the UE 120 to activate the requested RRC profile. According to some example embodiments, the RRC profile change message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. For example, according to some example embodiments the RRC profile change message may be sent through DCI signaling.

[0147] The RRC profile change message includes the network delay for activating each profile at the gNB 110 considering the new active profile. According to some example embodiments, the gNB 110 may determine the network delays (e.g., delay for activating a respective profile at the gNB 110 side) based on at least one of a network load at the gNB 110, a priority of the UE 120, etc.

[0148] For example, in the above example where the UE 120 selects profile 3, the RRC profile change message includes an indication of a network delay for activating profile 1 from profile 3 (e.g., 6 ms) and a network delay for activating profile 2 from profile 3 (e.g., 10ms). However, example embodiments are not limited to this example.

[0149] According to some example embodiments, the RRC profile change message may indicate a validity time for the respective network delays. For example, the RRC profile change message may indicate that the network delay for activating profile 1 from profile 3 is 6ms and that this delay is valid for 3 minutes from the time the RRC profile change message is sent. However, example embodiments are not limited to this example. For example, the gNB 110 may determine the validity times based on the respective profile configuration and / or a NW load. If the UE 120 initiates activation of a profile after the expiration of the validity time indicated for the respective profile, the delay for profile activation included in the RRC profile change message would not be applicable.

[0150] At D8, the UE 120 sends an acknowledgement message acknowledging receipt of the RRC profile change message. According to some example embodiments, the RRC profile change message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. At D9, the gNB 110 activates the selected profile for the UE 120 in the associated network delay time. For example, in the above example, the gNB 110 activates profile3 for the UE 120 and the activation takes 6ms. However, example embodiments are not limited to this example.

[0151] At DIO, the UE 120 changes to the selected profile. For example, the UE 120 may activate, from a currently active profile, the selected profile. For example, the UE 120 may change from an active profile 1 to profile 2 by activating profile 2. According to some example embodiments, since the UE 120 knows in advance the network delay that the gNB 110 will take to activate the selected profile, (e.g., 6ms to activate profile 3), the UE 120 may target to complete the profile change within this time. For example, the UE 120 can use parallel activation of some modules or parameters to complete the profile change quickly and prepare for data transmission with the new profile configuration.

[0152] At Dll, the UE 120 optionally sends an RRC profile change success message (e.g., RRCReconfigurationComplete) to the gNB 110 confirming the profile change is successful. According to some example embodiments, the RRC profile change success message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example.

[0153] According to some example embodiments, the RRC profile change success message may include UE delays for profile activation at the UE 120 considering the new active profile. For example, in the example where the UE 120 activates profile 3, the RRC profile change success message may include UE delays for activating profile 1 from profile 3 and / or UE delays for activating profile 2 from profile 3. However, example embodiments are not limited to this example. Thus, according to example embodiments, the UE 120 may more quickly and or more efficiently change an active RRC configuration profile based on known network delay times for activating the profile. For example, because the UE 120 knows in advance the network delay for activating the profile at the gNB 110, the UE 120 may begin or complete activation of the RRC profile (e.g., activate some or all component modules within the profile parallel to the activation at the gNB) within the period of the NW delay and be ready to receive a UL grant for initiating data more quickly.

[0154] FIG. 8 is a signaling diagram illustrating a method according to example embodiments.

[0155] The signaling diagram shown in FIG. 8 illustrates a message sequence, according to some example embodiments, for the gNB 110 indicating the delay for RCT addition and the UE 120 selecting the most suitable RCT considering the delay.

[0156] Referring to FIG. 8, the UE 120 begins in a connected mode with the gNB 110. Forexample, the connected mode may be an RRC connection (e.g., an ongoing RRC connection). For example, the UE 120 may have established an RRC connection with the gNB 110 prior to El according to any known method.

[0157] At El, the gNB 110 configures the UE 120 with RRC profiles including RCTs. For example, the gNB 110 may transmit an RRC configuration message (e.g., RRCReconfiguration) to the UE 120. According to some example embodiments, the RRC configuration message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. For example, according to some example embodiments the RRC configuration message may be sent through DCI signaling.

[0158] The RRC configuration message may include RRC configuration information for a plurality of RRC profiles. For example, the RRC configuration message may include RRC configuration information for two RRC profiles, profile 1 and profile 2. However, example embodiments are not limited to this example. For example, the RRC configuration message may include RRC configuration information for more or fewer than two profiles.

[0159] The RRC configuration message may additionally include RCT configuration information for each RRC profile. For example, the configuration message may indicate an RCT ID 1 associated with profile 1 and RCT ID 2 and RCT ID 3 associated with profile 2. However, example embodiments are not limited to this example and the RRC information message may include more or fewer RCTs (e.g., RCT IDs) for each RRC profile.

[0160] The RRC configuration message may indicate a profile, of the plurality of profiles, for the UE 120 to activate. For example, the RRC configuration message may inform the UE 120 to activate RRC profile 1 (RCT ID 1). However, example embodiments are not limited to this example. For example, if the gNB 110 indicates a profile including multiple RCTs for the UE 120 to activate, the gNB 110 may indicate an RCT ID other than ID 1 to be activated. For example, the gNB 110 may inform the UE 120 to activate RRC profile 2 (RCT ID 3) and to store the remaining RCT configuration(s) (e.g., RCT ID 2) for later activation.

[0161] According to some example embodiments, the RRC configuration message may include an indication of the network delay needed by the gNB 110 to activate each profile based on the active profile and / or a network delay for activating each RCT stored in all profiles. For example, the RRC configuration message may indicate that all profiles include three RCTs RCT ID 1, RCT ID 2, and / or RCT ID 3. However, example embodiments are not limited to this example,and the RRF configuration profiles may include more or fewer than three RCTs. For example, the RRC configuration message may indicate a network delay for activating profile 2 from profile 1 = 10ms, a network delay for activating RCT ID 2 for profile 1 = 5m, and / or a network delay for activating RCT ID 3 for profile 1 = 3ms. However, these example network delay times are provided only as an example, and example embodiments are not limited to this example. For example, the network delay times may be individually determined by the gNB 110 at the time of sending the RRC configuration message.

[0162] According to some example embodiments, the RRC configuration message may indicate a validity time for the respective network delays. For example, the RRC configuration message may indicate that the network delay for activating RCT ID 2 for profile 1 = 5ms and that this network delay is valid for 3 minutes from the time the message is sent. However, example embodiments are not limited to this example. For example, the gNB 110 may determine the validity times based on the respective profile configuration and / or a NW load. If the UE 120 initiates activation of a profile after the expiration of the validity time indicated for the respective profile, the network delay for profile activation included in the RRC configuration message would not be applicable.

[0163] At E2, the UE 120 activates the profile indicated in the RRC configuration message. For example, the UE 120 activates profile 1 (and RCT ID 1) in response to the RRC configuration message informing the UE 120 to activate RRC profile 1. However, example embodiments are not limited to this example. The UE 120 stores the profiles and RCTs indicated in the RRC configuration message along with the associated network delays and / or validity times.

[0164] At E3, the UE 120 sends a configuration success message to the gNB 110 confirming the profile activation is successful. According to some example embodiments, the configuration success message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example.

[0165] According to some example embodiments, the configuration success message may include UE delays for profile and / or RCT activation at the UE 120 considering the new active profile. For example, in the example where the UE 120 activates profile 1, the configuration success message may include UE delays for activating profile 2 from profile 1 and for activating RCT ID 2 for profile 1 and / or for activating RCT ID 3 for profile 1. However, example embodiments are not limited to this example. At E4, the UE 120 determines to enhance the activeprofile by adding an RCT. For example, the UE 120 may need to activate a higher throughput (e.g., an RCT providing a higher throughput) quickly if the capacity provided by the active RRC configuration is not sufficient.

[0166] According to some example embodiments, the UE 120 may consider the network delays indicated by the RRC configuration message when determining a RCT to activate. For example, the UE 120 may weigh the network delay time along with other characteristics of the RCTs (e.g., additional capacity that could be facilitated through the RCT to be added) when determining which profile to change to.

[0167] For example, the UE 120 may select an RCT with a shortest delay time. In this example, the UE 120 may select RCT ID 3 to be added to profile 1 since RCT ID 3 is indicated as having a lowest network delay time among RCT ID 2 and RCT ID 3. However, example embodiments are not limited to this example.

[0168] At E5, the UE 120 requests for RCT activation to the active profile from the gNB 110. F or example, the UE 120 may send a request for RCT activation message to the gNB 110 indicating the selected RCT. According to some example embodiments, the request for profile change message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. For example, according to some example embodiments, the UE 120 could use UAI to indicate the RCT change requirement to the gNB 110.

[0169] According to some example embodiments, the UE 120 may activate (e.g., begin to activate) the selected RCT when the UE 120 sends the request for RCT activation message. For example, the UE 120 may not wait for a response from the gNB 110 before beginning to activate the selected RCT and may instead begin to active the selected RCT at the same time as sending the request for RCT activation message in anticipation of confirmation from the gNB 110.

[0170] At E6, the gNB 110 considers the RCT activation request from the UE 120 and determines to activate the requested RCT. For example, if there is a resource limitation at the gNB 110, the gNB 110 may decline the request (e.g., at times of high congestion). If the gNB 110 determines to decline the request, the gNB 110 may send a message to the UE 120 indicating the request is denied and the method ends. If the gNB 110 determines to activate the requested RCT, the method continues to E7.

[0171] At E7, the gNB 110 sends an RRC RCT / Component activation request message to the UE 120 to activate the requested RCT. According to some example embodiments, the RRCRCT / Component activation request message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example. For example, according to some example embodiments the RRC RCT / Component activation request message may be sent through DCI signaling.

[0172] At E8, the gNB 110 activates the selected RCT for the UE 120 in the associated network delay time. For example, in the above example, the gNB 110 activates RCT ID 3 for the UE 120 and the activation takes 3ms. However, example embodiments are not limited to this example.

[0173] At E9, the UE 120 activates the selected RCT. According to some example embodiments, since the UE 120 knows in advance the network delay that the gNB 110 will take to activate the selected RCT, (e.g., 3ms to activate RCT ID 3), the UE 120 may target to complete the UE side RCT addition within this time. For example, the UE 120 can use parallel activation of some modules or parameters to complete the profile change quickly and prepare for data transmission with the new profile configuration.

[0174] At E10, the UE 120 sends an RRC RCT / Component activation response message to the gNB 110 confirming the RCT addition is successful. According to some example embodiments, the RRC RCT / Component activation response message may be sent based on MAC CE signaling. However, example embodiments are not limited to this example.

[0175] According to some example embodiments, the RRC RCT / Component activation response message may include UE delays for profile activation at the UE 120 considering the new active RCT. According to some example embodiments, the gNB 110 may determine the network delays (e.g., delay for activating a respective profile at the gNB 110 side) based on at least one of a network load at the gNB 110, a priority of the UE 120, etc.

[0176] Thus, according to example embodiments, the UE 120 may more quickly and / or more efficiently add a RCT to an active RRC configuration profile based on known network delay times for activating the profile. For example, because the UE 120 knows in advance the network delay for activating the RCT at the gNB 110, the UE 120 may begin or complete activation of the RCT (e.g., activate some or all component modules within the RCT parallel to the activation at the gNB) within the period of the NW delay and be ready to receive a UL grant for initiating data more quickly.

[0177] FIG. 9 is a flow chart illustrating a method according to some example embodiments. The method shown in FIG. 9 may be performed at the UE 120. For example, the method shown inFIG. 9 may be performed by the processor 12 of the UE 120.

[0178] Referring to FIG. 9, at S900 the UE 120 receives a configuration message indicating delays. For example, the configuration message may have been transmitted by the gNB 110. The configuration message may include information on a plurality of RRC configurations (e.g., profiles). For example, the configuration message may include a plurality of network delays (e.g., network delay times) for each profile indicating a delay time required for activating the corresponding profile at the gNB 110.

[0179] At S910, the UE 120 transmits a request message indicating a selected RRC configuration. For example, the UE 120 may select a RRC configuration to activate based on the associated network delays. For example, the UE 120 may select a RRC configuration having a smallest network delay.

[0180] At S920, the UE 120 activates the selected RRC configuration. According to some example embodiments, since the UE 120 knows in advance the network delay that the gNB 110 will take to activate the selected profile, the UE 120 may target to complete the profile change within this time. For example, the UE 120 can use parallel activation of some modules or parameters to complete the profile change quickly and prepare for data transmission with the new profile configuration.

[0181] FIG. 10 is a flow chart illustrating a method according to some example embodiments. The method shown in FIG. 10 may be performed at the gNB 110. For example, the method shown in FIG. 10 may be performed by the processor 12 of the gNB 110.

[0182] Referring to FIG. 10, at SI 000, the gNB 110 transmits a configuration message indicating network delays. For example, the gNB 110 may transmit the configuration message to the UE 120. The configuration message may include information on a plurality of RRC configurations (e.g., profiles). For example, the configuration message may include a plurality of network delays (e.g., network delay times) for each profile indicating a delay time required for activating the corresponding profile at the gNB 110.

[0183] At SI 010, the gNB 110 receives a request message indicating a selected RRC configuration. For example, the gNB 110 may receive the request message from a UE 120 requesting to activate a RRC configuration. For example, the UE 120 may select the selected RRC configuration based on the associated network delays. For example, the UE 120 may select a RRC configuration having a smallest network delay.

[0184] Thus, as the configuration message from the gNB 110 includes the associated network delays, the UE 120 knows in advance the network delay that the gNB 110 will take to activate the selected profile, and may target to complete the profile change within this time. For example, the UE 120 can use parallel activation of some modules or parameters to complete the profile change quickly and prepare for data transmission with the new profile configuration.

[0185] At SI 020, the gNB 110 activates the selected RRC configuration.

[0186] FIG. 11 is a flow chart illustrating a method according to some example embodiments. The method shown in FIG. 11 may be performed at the UE 120. For example, the method shown in FIG. 11 may be performed by the processor 12 of the UE 120.

[0187] Referring to FIG. 11, at SI 100 the UE 120 receives a configuration message indicating delays. For example, the configuration message may have been transmitted by the gNB 110. The configuration message may include information on a plurality of RRC configurations (e.g., profiles). For example, the configuration message may include a plurality of network delays (e.g., network delay times) for each profile indicating a delay time required for activating the corresponding profile at the gNB 110 and the configuration message may include network delays for each RCT indicating a network delay time for activating the corresponding RCT at the gNB 110.

[0188] At SI 110, the UE 120 transmits a request message indicating a selected RRC configuration. For example, the UE 120 may select a RRC configuration to activate based on the associated network delays. For example, the UE 120 may select a RRC configuration having a smallest network delay.

[0189] At SI 120, the UE 120 activates the selected RRC configuration. According to some example embodiments, since the UE 120 knows in advance the network delay that the gNB 110 will take to activate the selected profile, the UE 120 may target to complete the profile change within this time. For example, the UE 120 can use parallel activation of some modules or parameters to complete the profile change quickly and prepare for data transmission with the new profile configuration.

[0190] FIG. 12 is a flow chart illustrating a method according to some example embodiments. The method shown in FIG. 12 may be performed at the gNB 110. For example, the method shown in FIG. 12 may be performed by the processor 12 of the gNB 110.

[0191] Referring to FIG. 12, at S1200, the gNB 110 transmits a configuration messageindicating network delays. For example, the gNB 110 may transmit the configuration message to the UE 120. The configuration message may include information on a plurality of RRC configurations (e.g., profiles). For example, the configuration message may include a plurality of network delays (e.g., network delay times) for each profile indicating a delay time required for activating the corresponding profile at the gNB 110 and the configuration message may include network delays for each RCT indicating a network delay time for activating the corresponding RCT atthe gNB 110.

[0192] At SI 210, the gNB 110 receives a request message indicating a selected RRC configuration. For example, the gNB 110 may receive the request message from a UE 120 requesting to activate a RRC configuration. For example, the UE 120 may select the selected RRC configuration based on the associated network delays. For example, the UE 120 may select a RRC configuration having a smallest network delay.

[0193] Thus, as the configuration message from the gNB 110 includes the associated network delays, the UE 120 knows in advance the network delay that the gNB 110 will take to activate the selected profile, and may target to complete the profile change within this time. For example, the UE 120 can use parallel activation of some modules or parameters to complete the profile change quickly and prepare for data transmission with the new profile configuration.

[0194] At SI 220, the gNB 110 activates the selected RRC configuration.

[0195] Illustrative Embodiment 1 : A user equipment comprising: at least one memory storing instructions; and at least one processor configured to execute the instructions and cause the user equipment to receive a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, transmit a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations, and activate the selected RRC configuration.

[0196] Illustrative Embodiment 2: The user equipment of the illustrative embodiment 1, wherein the configuration message is an RRC message.

[0197] Illustrative Embodiment 3: The user equipment of illustrative embodiments 1 or 2, wherein the configuration message is an RRC release message, a RRC reconfiguration message, or a RRC configuration message.

[0198] Illustrative Embodiment 4: The user equipment of any one of illustrative embodiments1-3, wherein the at least on processor is configured to execute the instructions to cause the user equipment to select the selected RRC configuration based on the plurality of network delays.

[0199] Illustrative Embodiment 5: The user equipment of any one of illustrative embodiments 1-4, wherein the request message is an RRC connection request message or an RRC request for profile change message.

[0200] Illustrative Embodiment 6: The user equipment of any one of illustrative embodiments 1-5, wherein the at least one processor is configured to execute the instructions to cause the user equipment to activate the selected RRC configuration in response to at least one of receiving, from the network node, a RRC configuration message including an update to the plurality of network delays, or transmitting the request message.

[0201] Illustrative Embodiment 7: The user equipment of any one of illustrative embodiments 1-6, wherein the at least one processor is configured to execute the instructions to cause the user equipment to transmit a confirmation message to the network node using MAC CE, the confirmation message indicating successful activation of the selected RRC configuration.

[0202] Illustrative Embodiment 8: The user equipment of any one of illustrative embodiments 1-7, wherein the plurality of network delays indicate an amount of time the network node takes to activate the respective RRC configurations.

[0203] Illustrative Embodiment 9: The user equipment of any one of illustrative embodiments 1-8, wherein the plurality of RRC configurations are arranged as a plurality of profiles.

[0204] Illustrative Embodiment 10: The user equipment of any one of illustrative embodiments 1-9, wherein the at least one processor is configured to execute the instructions to cause the user equipment to indicate, to the network node, a requirement to activate the selected RRC configuration using user equipment (UE) assistant information.

[0205] Illustrative Embodiment 11: An apparatus comprising: at least one memory storing instructions; and at least one processor configured to execute the instructions and cause apparatus to transmit, to a user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, receive, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations, and activate the selected RRC configuration for the user equipment.

[0206] Illustrative Embodiment 12: The apparatus of illustrative embodiment 11, wherein theconfiguration message is an RRC message.

[0207] Illustrative Embodiment 13: The apparatus of illustrative embodiments 11 or 12, wherein the configuration message is an RRC release message, an RRC configuration message, or an RRC reconfiguration message.

[0208] Illustrative Embodiment 14: The apparatus of any one of illustrative embodiments 11-13, wherein the at least one processor is configured to execute the instructions to cause the apparatus to transmit, to the user equipment, updated network delays corresponding to the plurality of network delays, respectively, the updated network delays based on the selected RRC configuration.

[0209] Illustrative Embodiment 15: The apparatus of illustrative embodiment 14, wherein the at least one processor is configured to execute the instructions to cause the apparatus to transmit the updated network delays by at least one of an RRC configuration message, an RRC request for profile change message, a message using medium access control (MAC) control element (CE) signaling, or a message using downlink control information (DCI) signaling.

[0210] Illustrative Embodiment 16: The apparatus of any one of illustrative embodiments 11- 15, wherein the at least one processor is configured to execute the instructions to cause the apparatus to activate the selected RRC configuration for the user equipment in response to a user equipment (UE) assistant information requirement to activate the selected RRC configuration.

[0211] Illustrative Embodiment 17: The apparatus of any one of illustrative embodiments 11- 16, wherein the at least one processor is configured to execute the instructions to cause the apparatus to activate the selected RRC configuration for the user equipment by completing network side configuration changes to activate the selected RRC configuration for the user equipment.

[0212] Illustrative Embodiment 18: A method for activating a radio resource control (RRC) configuration, the method comprising: receiving a configuration message indicating a plurality of RRC configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations; transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations; and activating the selected RRC configuration.

[0213] Illustrative Embodiment 19: A method for activating a radio resource control (RRC) configuration for a user equipment, the method comprising: transmitting, to the user equipment, aconfiguration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations; receiving, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations; and activating the selected RRC configuration for the user equipment.

[0214] Illustrative Embodiment 20: A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed, cause one or more processors to cause a user equipment to perform a method for activating a radio resource control (RRC) configuration, the method comprising: receiving a configuration message indicating a plurality of RRC configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations; transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations; and activating the selected RRC configuration.

[0215] Illustrative Embodiment 21: A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed, cause one or more processors to cause an apparatus to perform a method for activating a radio resource control (RRC) configuration for a user equipment, the method comprising: transmitting, to the user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations; receiving, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations; and activating the selected RRC configuration for the user equipment.

[0216] Illustrative Embodiment 22: A user equipment comprising: a means for receiving a configuration message indicating a plurality of RRC configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations; a means for transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations; and a means for activating the selected RRC configuration.

[0217] Illustrative Embodiment 23: An apparatus comprising: a means for transmitting, to a user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delayscorresponding, respectively, with the plurality of RRC configurations; a means for receiving, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations; and a means for activating the selected RRC configuration for the user equipment.

[0218] Illustrative Embodiment 24: A user equipment comprising: at least one memory storing instructions; and at least one processor configured to execute the instructions and cause the user equipment to receive a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with a network node, the plurality of RRC configurations including a number of configuration threads, and a number of first network delays corresponding, respectively, with the number of configuration threads, transmit a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations, and activate the selected RRC configuration.

[0219] Illustrative Embodiment 25: The user equipment of illustrative embodiment 24, wherein the at least one processor is configured to execute the instructions to cause the user equipment to select a configuration thread of the number of configuration threads based on the number of first network delays.

[0220] Illustrative Embodiment 26: The user equipment of illustrative embodiment 25, wherein the at least one processor is configured to execute the instructions to cause the user equipment to transmit a request to the network node to activate the selected configuration thread.

[0221] Illustrative Embodiment 27: The user equipment of illustrative embodiments 25 or 26, wherein the at least one processor is configured to execute the instructions to cause the user equipment to indicate, to the network node, a requirement to activate the selected configuration thread using user equipment (UE) assistant information.

[0222] Illustrative Embodiment 28: The user equipment of any one of illustrative embodiments 25-27, wherein the at least one processor is configured to execute the instructions to cause the user equipment to activate the selected configuration thread.

[0223] Illustrative Embodiment 29: The user equipment of any one of illustrative embodiments 24-28, wherein the configuration message indicates a plurality of second network delays corresponding, respectively, with the plurality of RRC configurations.

[0224] Illustrative Embodiment 30: The user equipment of any one of illustrative embodiments 24-29, wherein the at least one processor is configured to execute the instructions to cause the userequipment to receive a response message including updated network delays corresponding to the plurality of network delays, respectively, the updated network delays based on the selected RRC configuration.

[0225] Illustrative Embodiment 31: The user equipment of any one of illustrative embodiments 24-30, wherein the plurality of RRC configurations are arranged as a plurality of profiles.

[0226] Illustrative Embodiment 32: An apparatus comprising: at least one memory storing instructions; and at least one processor configured to execute the instructions and cause the apparatus to transmit, to a user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus, the plurality of RRC configurations including a number of configuration threads, a number of first network delays corresponding, respectively, with the number of configuration threads, receive a request message from the user equipment indicating a selected RRC configuration of the plurality of RRC configurations, and activate the selected RRC configuration for the user equipment.

[0227] Illustrative Embodiment 33: The apparatus of illustrative embodiment 32, wherein the at least one processor is configured to execute the instructions to cause the apparatus to activate, for the user equipment, a selected configuration thread of the number of configuration threads in response to receiving a request from the user equipment indicating the selected configuration thread.

[0228] Illustrative Embodiment 34: The apparatus of illustrative embodiments 32 or 33, wherein the at least one processor is configured to execute the instructions to cause the apparatus to activate, for the user equipment, a selected configuration thread of the number of configuration threads in response to a user equipment (UE) assistant information requirement to activate the selected configuration thread.

[0229] Illustrative Embodiment 35: The apparatus of any one of illustrative embodiments 32- 34, wherein the at least one processor is configured to execute the instructions to cause the apparatus to transmit an activation request message to the user equipment in response to receiving a request from the user equipment indicating a selected configuration thread.

[0230] Illustrative Embodiment 36: The apparatus of any one of illustrative embodiments 32- 35, wherein the configuration message indicates a plurality of second network delays corresponding, respectively, with the plurality of RRC configurations.

[0231] Illustrative Embodiment 37: The apparatus of any one of illustrative embodiments 32-36, wherein the at least one processor is configured to execute the instructions to cause the apparatus to transmit, to the user equipment, updated network delays corresponding to the number of network delays, respectively, the updated network delays based on the selected RRC configuration.

[0232] Illustrative Embodiment 38: The apparatus of illustrative embodiment 37, wherein the at least one processor is configured to execute the instructions to cause the apparatus to transmit the updated network delays by at least one of an RRC configuration message, an RRC request for profile changes message, a message using medium access control (MAC) control element (CE) signaling, or a message using downlink control information (DCI) signaling.

[0233] Illustrative Embodiment 39: A method for activating a radio resource control (RRC) configuration, the method comprising: receiving a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with a network node, the plurality of RRC configurations including a number of configuration threads, and a number of first network delays corresponding, respectively, with the number of configuration threads; transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations; and activating the selected RRC configuration.

[0234] Illustrative Embodiment 40: A method for activating a radio resource control (RRC) configuration for a user equipment, the method comprising: transmitting, to the user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus, the plurality of RRC configurations including a number of configuration threads, a number of first network delays corresponding, respectively, with the number of configuration threads; receiving a request message from the user equipment indicating a selected RRC configuration of the plurality of RRC configurations; and activating the selected RRC configuration for the user equipment.

[0235] Illustrative Embodiment 41: A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed, cause one or more processors to cause a user equipment to perform a method for activating a radio resource control (RRC) configuration, the method comprising: receiving a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with a network node, the plurality of RRC configurations including a number of configuration threads, and a number of first network delayscorresponding, respectively, with the number of configuration threads; transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations; and activating the selected RRC configuration.

[0236] Illustrative Embodiment 42: A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed, cause one or more processors to cause a user equipment to perform a method for activating a radio resource control (RRC) configuration for a user equipment, the method comprising: transmitting, to the user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus, the plurality of RRC configurations including a number of configuration threads, a number of first network delays corresponding, respectively, with the number of configuration threads; receiving a request message from the user equipment indicating a selected RRC configuration of the plurality of RRC configurations; and activating the selected RRC configuration for the user equipment.

[0237] Illustrative Embodiment 43: A user equipment comprising: a means for receiving a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with a network node, the plurality of RRC configurations including a number of configuration threads, and a number of first network delays corresponding, respectively, with the number of configuration threads; a means for transmitting a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations; and a means for activating the selected RRC configuration.

[0238] Illustrative Embodiment 44: An apparatus comprising: a means for transmitting, to the user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus, the plurality of RRC configurations including a number of configuration threads, a number of first network delays corresponding, respectively, with the number of configuration threads; a means for receiving a request message from the user equipment indicating a selected RRC configuration of the plurality of RRC configurations; and a means for activating the selected RRC configuration for the user equipment.

[0239] Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope ofthis disclosure. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0240] When an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. By contrast, when an element is referred to as being “directly connected” or “directly coupled” to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between” versus “directly between” “adjacent” versus “directly adjacent” etc.).

[0241] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” “comprising” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0242] It should also be noted that in some alternative implementations, the functions / acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functionality / acts involved.

[0243] Specific details are provided in the description to provide a thorough understanding of example embodiments. However, it will be understood by one of ordinary skill in the art that example embodiments may be practiced without these specific details. For example, systems may be shown in block diagrams so as not to obscure the example embodiments in unnecessary detail. In other instances, well-known processes, structures and techniques may be shown without unnecessary detail in order to avoid obscuring example embodiments.

[0244] As discussed herein, illustrative embodiments are described with reference to acts and symbolic representations of operations (e.g., in the form of flow charts, flow diagrams, data flow diagrams, structure diagrams, block diagrams, etc.) that may be implemented as program modules or functional processes include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types and may be implemented using existing hardware at, for example, existing network apparatuses, elements or entities includingcloud-based data centers, computers, cloud-based servers, or the like. Such existing hardware may be processing or control circuitry such as, but not limited to, one or more processors, one or more Central Processing Units (CPUs), one or more controllers, one or more arithmetic logic units (AUUs), one or more digital signal processors (DSPs), one or more microcomputers, one or more field programmable gate arrays (FPGAs), one or more System-on-Chips (SoCs), one or more programmable logic units (PLUs), one or more microprocessors, one or more Application Specific Integrated Circuits (ASICs), or any other device or devices capable of responding to and executing instructions in a defined manner.

[0245] Although a flow chart may describe the operations as a sequential process, many of the operations may be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. A process may be terminated when its operations are completed, but may also have additional steps not included in the figure. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

[0246] As disclosed herein, the term “storage medium” “computer readable storage medium” or “non-transitory computer readable storage medium” may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and / or other tangible machine-readable mediums for storing information. The term “computer-readable medium” may include, but is not limited to, portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instruction(s) and / or data.

[0247] Furthermore, example embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine or computer readable medium such as a computer readable storage medium. When implemented in software, a processor or processors will perform the necessary tasks. For example, as mentioned above, according to one or more example embodiments, at least one memory may include or store computer program code, and the at least one memory and the computer program code may be configured to, with at leastone processor, cause a network apparatus, network element or network device to perform the necessary tasks. Additionally, the processor, memory and example algorithms, encoded as computer program code, serve as means for providing or causing performance of operations discussed herein.

[0248] A code segment of computer program code may represent a procedure, function, subprogram, program, routine, subroutine, module, software package, class, or any combination of instructions, data structures or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable technique including memory sharing, message passing, token passing, network transmission, etc.

[0249] The terms “including” and / or “having,” as used herein, are defined as comprising (i.e., open language). The term “coupled,” as used herein, is defined as connected, although not necessarily directly, and not necessarily mechanically. Terminology derived from the word “indicating” (e.g., “indicates” and “indication”) is intended to encompass all the various techniques available for communicating or referencing the object / information being indicated. Some, but not all, examples of techniques available for communicating or referencing the object / information being indicated include the conveyance of the object / information being indicated, the conveyance of an identifier of the object / information being indicated, the conveyance of information used to generate the object / information being indicated, the conveyance of some part or portion of the object / information being indicated, the conveyance of some derivation of the object / information being indicated, and the conveyance of some symbol representing the object / information being indicated.

[0250] According to example embodiments, network apparatuses, elements or entities including cloud-based data centers, computers, cloud-based servers, or the like, may be (or include) hardware, firmware, hardware executing software or any combination thereof. Such hardware may include processing or control circuitry such as, but not limited to, one or more processors, one or more CPUs, one or more controllers, one or more ALUs, one or more DSPs, one or more microcomputers, one or more FPGAs, one or more SoCs, one or more PLUs, one or more microprocessors, one or more ASICs, or any other device or devices capable of responding to and executing instructions in a defined manner.

Claims

WHAT IS CLAIMED IS:

1. A user equipment comprising:at least one memory storing instructions; andat least one processor configured to execute the instructions and cause the user equipment toreceive a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with a network node and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations, transmit a request message to the network node indicating a selected RRC configuration of the plurality of RRC configurations, andactivate the selected RRC configuration.

2. The user equipment of claim 1, wherein the configuration message is a RRC message.

3. The user equipment of claim 1, wherein the configuration message is a RRC release message, a RRC reconfiguration message, or a RRC configuration message.

4. The user equipment of claim 1, wherein the at least one processor is configured to execute the instructions to cause the user equipment to select the selected RRC configuration based on the plurality of network delays.

455. The user equipment of claim 1, wherein the request message is an RRC connection request message or an RRC request for profile change message.

6. The user equipment of claim 1, wherein the at least one processor is configured to execute the instructions to cause the user equipment to activate the selected RRC configuration in response to at least one of,receiving, from the network node, an RRC configuration message including an update to the plurality of network delays, ortransmitting the request message.

7. The user equipment of claim 1, wherein the at least one processor is configured to execute the instructions to cause the user equipment to transmit a confirmation message to the network node using MAC CE, the confirmation message indicating successful activation of the selected RRC configuration.

8. The user equipment of claim 1, wherein the plurality of network delays indicate an amount of time the network node takes to activate the respective RRC configurations.

9. The user equipment of claim 1, wherein the plurality of RRC configurations are arranged as a plurality of profiles.

10. The user equipment of claim 1, wherein the at least one processor is configured to execute the instructions to cause the user equipment to indicate, to the network node, a requirement to activate the selected RRC configuration using user equipment (UE) assistant information.

11. An apparatus comprising:at least one memory storing instructions; andat least one processor configured to execute the instructions and cause the apparatus to transmit, to a user equipment, a configuration message indicating a plurality of radio resource control (RRC) configurations for communication with the apparatus and a plurality of network delays corresponding, respectively, with the plurality of RRC configurations,receive, from the user equipment, a request message indicating a selected RRC configuration of the plurality of RRC configurations, andactivate the selected RRC configuration for the user equipment.

12. The apparatus of claim 11, wherein the configuration message is an RRC message.

13. The apparatus of claim 11, wherein the configuration message is an RRC release message, an RRC configuration message, or an RRC reconfiguration message.

14. The apparatus of claim 11, wherein the at least one processor is configured to execute the instructions to cause the apparatus totransmit, to the user equipment, updated network delays corresponding to the plurality of network delays, respectively, the updated network delays based on the selected RRC configuration.

15. The apparatus of claim 14, wherein the at least one processor is configured to execute the instructions to cause the apparatus to transmit the updated network delays by at least one of an RRC configuration message,an RRC request for profile change message,a message using medium access control (MAC) control element (CE) signaling, or a message using downlink control information (DCI) signaling.

16. The apparatus of claim 11, wherein the at least one processor is configured to execute the instructions to cause the apparatus to activate the selected RRC configuration for the user equipment in response to a user equipment (UE) assistant information requirement to activate the selected RRC configuration.

17. The apparatus of claim 11, wherein the at least one processor is configured to execute the instructions to cause the apparatus to activate the selected RRC configuration for the user equipment by completing network side configuration changes to activate the selected RRC configuration for the user equipment.

Images