Triggered selection of base station unit in response to handover condition
阅读说明：本技术 响应于切换条件被触发选择基站单元 (Triggered selection of base station unit in response to handover condition ) 是由 吴联海 韩晶 汪海明 张卓韵 李宏超 于 2018-01-10 设计创作，主要内容包括：公开了用于响应于切换条件被触发而选择基站单元的装置、方法和系统。一种方法包括响应于多个基站单元中的至少一个基站单元触发切换条件,选择多个基站单元中的一个基站单元用于切换。该方法包括将随机接入前导发送到基站单元。该方法包括响应于确定无法接入多个基站单元中的满足切换条件的每个基站单元而执行重建过程以与多个基站单元中的一个基站单元建立通信。(Apparatus, methods, and systems are disclosed for selecting a base station unit in response to a handover condition being triggered. A method includes selecting one of a plurality of base station units for handover in response to at least one of the plurality of base station units triggering a handover condition. The method includes transmitting a random access preamble to a base unit. The method includes performing a re-establishment procedure to establish communication with one of the plurality of base station units in response to determining that each of the plurality of base station units that satisfies the handover condition cannot be accessed.)
1. A method, comprising:
selecting one of a plurality of base station units for handover in response to at least one of the plurality of base station units triggering a handover condition;
transmitting a random access preamble to the base station unit; and
in response to determining that each of the plurality of base station units that satisfies the handover condition cannot be accessed, performing a re-establishment procedure to establish communication with one of the plurality of base station units.
2. The method of claim 1, further comprising determining that the base unit cannot be accessed.
3. The method of claim 2, wherein determining that the base unit cannot be accessed comprises: receiving no response from the base unit as a result of transmitting the random access preamble to the base unit.
4. The method of claim 2, further comprising: in response to determining that the base station unit cannot be accessed, transmitting a second random access preamble to a second base station unit of the plurality of base station units.
5. The method of claim 1, further comprising: receiving configuration information indicating a handover condition corresponding to the base station unit.
6. The method of claim 5, wherein the configuration information comprises a radio resource control connection reconfiguration message with mobility control information.
7. An apparatus, comprising:
a processor that selects one of a plurality of base station units for handover in response to at least one of the plurality of base station units triggering a handover condition; and
a transmitter that transmits a random access preamble to the base unit;
wherein the processor performs a re-establishment procedure to establish communication with one of the plurality of base station units in response to determining that each of the plurality of base station units that satisfies the handover condition cannot be accessed.
8. The apparatus of claim 7, wherein the processor determines that the base unit cannot be accessed.
9. The apparatus of claim 8, further comprising a receiver, wherein the processor determining that the base unit cannot be accessed comprises: the receiver receives no response from the base unit as a result of transmitting the random access preamble to the base unit.
10. The apparatus of claim 8, wherein the transmitter transmits a second random access preamble to a second base unit of the plurality of base units in response to the processor determining that the base unit cannot be accessed.
11. The apparatus of claim 7, further comprising a receiver that receives configuration information indicating a handover condition corresponding to the base unit.
12. The apparatus of claim 11, wherein the configuration information comprises a radio resource control connection reconfiguration message with mobility control information.
13. A method, comprising:
receiving a random access message from a remote unit; and
in response to receiving the random access message, sending a request for sequence number state transition information, data forwarding information, or a combination thereof to a base unit.
14. The method of claim 13, wherein the random access message comprises a random access preamble.
15. The method of claim 13, wherein the random access message comprises a radio resource control reconfiguration complete message.
16. The method of claim 13, further comprising: receiving, in response to sending the request, the sequence number state transition information, data corresponding to the data forwarding information, or a combination thereof.
17. An apparatus, comprising:
a receiver that receives a random access message from a remote unit; and
a transmitter that, in response to receiving the random access message, sends a request for sequence number state transition information, data forwarding information, or a combination thereof to a base station unit.
18. The apparatus of claim 17, wherein the random access message comprises a random access preamble.
19. The apparatus of claim 17, wherein the random access message comprises a radio resource control reconfiguration complete message.
20. The apparatus of claim 17, wherein the receiver receives the sequence number state transition information, data corresponding to the data forwarding information, or a combination thereof, in response to the transmitter sending the request.
Technical Field
The subject matter disclosed herein relates generally to wireless communications, and more particularly to triggered selection of a base station unit in response to a handover condition.
Background
The following abbreviations are defined herein, at least some of which are referred to in the following description: third generation partnership project ("3 GPP"), authentication authorization and accounting ("AAA"), acknowledgement ("ACK"), acknowledged mode ("AM"), access and mobility management function ("AMF"), access server ("AS"), authentication server function ("AUSF"), cell radio network temporary identifier ("C-RNTI"), dedicated control channel ("DCCH"), downlink ("DL"), domain name system ("DNS"), enhanced mobile broadband ("eMBB"), evolved node B ("eNB"), enhanced subscriber identity module ("eSIM"), equipment identity register ("EIR"), evolved packet core ("EPC"), european telecommunications standards institute ("ETSI"), E-UTRAN radio access bearer ("E-RAB"), evolved universal terrestrial radio access network ("E-UTRAN") Frequency division duplexing ("FDD"), frequency division multiple access ("FDMA"), fully qualified domain name ("FQDN"), global system for mobile communications association ("GSMA"), hybrid automatic repeat request ("HARQ"), home policy control function ("H-PCF"), home public land mobile network ("HPLMN"), identity or identifier or identification ("ID"), international mobile equipment identity ("IMEI"), international mobile subscriber identity ("IMSI"), internet of things ("IoT"), long term evolution ("LTE"), multiple access ("MA"), modulation and coding scheme ("MCS"), mobile country code ("MCC"), mobile network code ("MNC"), machine type communication ("MTC"), master information block ("MIB"), mobility management ("MM"), mobility management entity ("MME"), non-access stratum ("NAS"), narrowband ("NB"), "mobile network code (" MNC "), machine type communication (" MTC, or a combination thereof, Negative acknowledgement ("NACK") or ("NAK"), next generation node B ("gNB"), orthogonal frequency division multiplexing ("OFDM"), over the air ("OTA"), policy control function ("PCF"), packet data convergence protocol ("PDCP"), public land mobile network ("PLMN"), pointer ("PTR"), quality of service ("QoS"), random access channel ("RACH"), radio link control ("RLC"), radio link failure ("RLF"), radio network layer ("RNL"), radio resource control ("RRC"), radio resource management ("RRM"), radio access network ("RAN"), reference signal received power ("RSRP"), reference signal received quality ("RSRQ"), reception ("RX"), service data unit ("SDU"), sequence number ("SN"), single carrier frequency division multiple access ("SC-FDMA"), "FDMA, A subscriber management function ("SMF"), a subscriber identity module ("SIM"), a system information block ("SIB"), a hidden subscriber identifier ("SUCI"), a subscription permanent identifier ("SUPI"), a timing advance group ("TAG"), a tracking area ("TA"), a transport network layer ("TNL"), a transmit ("TX"), a unified data management ("UDM"), a user data repository ("UDR"), a user entity/device (mobile terminal) ("UE"), a universal integrated circuit card ("UICC"), an uplink ("UL"), a universal mobile telecommunications system ("UMTS"), a user plane function ("UPF"), a universal subscriber identity module ("USIM"), an access policy control function ("V-PCF"), a visited public land mobile network ("VPLMN"), and worldwide interoperability for microwave access ("WiMAX"). As used herein, "HARQ-ACK" may collectively refer to positive acknowledgement ("ACK") and negative acknowledgement ("NAK"). ACK means that the TB is correctly received, and NAK means that the TB is incorrectly received.
In some wireless communication networks, a remote unit may have multiple base units that trigger a handoff condition. In such a network, a base station unit may be selected for communication.
Disclosure of Invention
A method for selecting a base station unit in response to triggering a handover condition is disclosed. The apparatus and system also perform the functions of the apparatus. In one embodiment, the method includes selecting one of the plurality of base station units for handover in response to at least one of the plurality of base station units triggering a handover condition. In various embodiments, the method includes transmitting a random access preamble to a base unit. In some embodiments, the method includes performing a re-establishment procedure to establish communication with one of the plurality of base units in response to determining that each of the plurality of base units that satisfies the handover condition cannot be accessed.
In one embodiment, the method includes determining that a base unit cannot be accessed. In another embodiment, determining that the base unit cannot be accessed includes receiving no response from the base unit due to the random access preamble being transmitted to the base unit. In certain embodiments, the method comprises: in response to determining that the base station unit cannot be accessed, a second random access preamble is transmitted to a second base station unit of the plurality of base station units. In various embodiments, the method includes receiving configuration information indicating a handover condition corresponding to a base station unit. In some embodiments, the configuration information comprises a radio resource control connection reconfiguration message with mobility control information.
In one embodiment, an apparatus for selecting a base station unit in response to triggering a handover condition includes a processor that selects a base station unit of a plurality of base station units for handover in response to at least one of the plurality of base station units triggering a handover condition. In various embodiments, the apparatus includes a transmitter that transmits a random access preamble to a base unit. In some embodiments, the processor performs a re-establishment procedure to establish communication with one of the plurality of base units in response to determining that each of the plurality of base units that satisfies the handover condition cannot be accessed.
In one embodiment, a method for sending an information request includes receiving a random access message from a remote unit. In various embodiments, the method comprises: in response to receiving the random access message, a request for sequence number state transition information, data forwarding information, or a combination thereof is sent to the base unit.
In one embodiment, the random access message includes a random access preamble. In a further embodiment, the random access message comprises a radio resource control reconfiguration complete message. In some embodiments, the method includes receiving sequence number state transition information, data corresponding to data forwarding information, or a combination thereof in response to sending the request.
In one embodiment, an apparatus for sending an information request, comprises: a receiver that receives a random access message from a remote unit. In various embodiments, the apparatus includes a transmitter that sends a request for sequence number state transition information, data forwarding information, or a combination thereof to a base station in response to receiving a random access message.
Drawings
A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of its scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
FIG. 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for selecting a base unit in response to a handover condition being triggered;
FIG. 2 is a schematic block diagram illustrating one embodiment of an apparatus for selecting a base unit in response to a handover condition being triggered;
FIG. 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to send a request for information;
FIG. 4 illustrates one embodiment of communications for handover;
fig. 5 illustrates one embodiment of communications for a contention-based random access procedure;
fig. 6 illustrates one embodiment of communications for a non-contention based random access procedure;
FIG. 7 illustrates one embodiment of communications for conditional switching;
fig. 8 illustrates one embodiment of communications for conditional handover corresponding to non-contention based random access;
fig. 9 illustrates one embodiment of communications for conditional handover corresponding to contention-based random access;
FIG. 10 is a schematic flow chart diagram illustrating one embodiment of a method for selecting a base station unit in response to a handover condition being triggered; and
FIG. 11 is a schematic flow chart diagram illustrating one embodiment of a method for sending a request for information.
Detailed Description
As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," module "or" system. Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and/or program code, referred to hereinafter as code. The storage device may be tangible, non-transitory, and/or non-transmissive. The storage device may not embody the signal. In a certain embodiment, the memory device only employs signals for accessing the code.
Some of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, comprise one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer-readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer-readable storage devices.
Any combination of one or more computer-readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. A storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The code for performing the operations of an embodiment may be any number of lines and may be written in any combination including one or more of an object oriented programming language such as Python, Ruby, Java, Smalltalk, C + +, etc., and conventional procedural programming languages, such as the "C" programming language, and/or a machine language, such as assembly language. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer, partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
Reference in the specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise. The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a", "an" and "the" also mean "one or more", unless expressly specified otherwise.
Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that an embodiment may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.
Aspects of the embodiments are described below with reference to schematic flow charts and/or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow chart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flow chart diagrams and/or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart and/or schematic block diagram block or blocks.
The code may also be stored in a memory device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the memory device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart and/or schematic block diagram block or blocks.
The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The schematic flow charts and/or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flow chart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is contemplated that other steps and methods may be equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated figures.
Although various arrow types and line types may be employed in the flow chart diagrams and/or block diagram blocks, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and code.
The description of the elements in each figure may refer to elements of the previous figures. Like numbers refer to like elements throughout, including alternative embodiments of the same elements.
Fig. 1 depicts an embodiment of a wireless communication system 100 for selecting a base station unit in response to a handover condition being triggered. In one embodiment, wireless communication system 100 includes a remote unit 102 and a network unit 104. Although a particular number of remote units 102 and network units 104 are depicted in fig. 1, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.
In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smart phone, a smart television (e.g., a television connected to the internet), a set-top box, a gaming console, a security system (including a monitoring camera), an in-vehicle computer, a network device (e.g., a router, switch, modem), an IoT device, and so forth. In some embodiments, remote unit 102 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, and so forth. Moreover, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terminology used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals.
The network elements 104 may be distributed over a geographic area. In certain embodiments, the network element 104 may also be referred to as an access point, access terminal, base unit, base station, node-B, eNB, gNB, home node-B, relay node, device, network device, or any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the internet and public switched telephone networks, among others. These and other elements of the radio access and core networks are not illustrated but are generally well known to those of ordinary skill in the art. In some embodiments, network element 104 may include one or more of the following network components: eNB, gNB, AMF, DB, MME, PCF, UDR, UPF, serving gateway, and/or UDM.
In one embodiment, wireless communication system 100 conforms to LTE of the 3GPP protocol, where network elements 104 transmit using an OFDM modulation scheme on the DL and remote units 102 transmit using an SC-FDMA scheme or an OFDM scheme on the UL. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocols, such as WiMAX, as well as other protocols. The present disclosure is not intended to be limited to implementation by any particular wireless communication system architecture or protocol.
Network element 104 may serve multiple remote units 102 within a service area (e.g., a cell or cell sector) via wireless communication links. The network element 104 transmits DL communication signals in the time, frequency, and/or spatial domains to serve the remote unit 102.
In some embodiments, the remote unit 102 may select one of the plurality of base units for handover in response to at least one of the plurality of base units triggering a handover condition. In various embodiments, remote unit 102 may transmit a random access preamble to the base unit. In some embodiments, in response to determining that each of the plurality of base units that satisfies the handoff condition cannot be accessed, the remote unit 102 may perform a re-establishment procedure to establish communication with one of the plurality of base units. Thus, in response to a handoff condition being triggered, the remote unit 102 may be used to select a base unit.
In various embodiments, network element 104 may receive a random access message from remote unit 102. In some embodiments, network element 102 may send a request for sequence number state transition information, data forwarding information, or a combination thereof to a base unit in response to receiving a random access message. Thus, the network element 104 may be used to send a request for information.
Fig. 2 depicts one embodiment of an apparatus 200 that may be used to select a base unit in response to a handover condition being triggered. The apparatus 200 includes one embodiment of the remote unit 102. In addition, remote unit 102 may include a processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touch screen. In some embodiments, remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, remote unit 102 may include one or more of processor 202, memory 204, transmitter 210, and receiver 212, and may not include input device 206 and/or display 208.
In one embodiment, processor 202 may include any known controller capable of executing computer readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processor ("GPU"), auxiliary processing unit, field programmable gate array ("FPGA"), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. In some embodiments, processor 202 may select one of the plurality of base units for handover in response to at least one of the plurality of base units triggering a handover condition. In various embodiments, processor 202 may perform a re-establishment procedure to establish communication with one of the plurality of base units in response to determining that each of the plurality of base units that satisfies the handover condition cannot be accessed. The processor 202 is communicatively coupled to a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212.
In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, the memory 204 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and/or static RAM ("SRAM"). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and nonvolatile computer storage media. In some embodiments, memory 204 stores data related to triggering a handover condition. In some embodiments, memory 204 also stores program code and related data, such as an operating system and other controller algorithms operating on remote unit 102.
In one embodiment, input device 206 may comprise any known computer input device, including a touchpad, buttons, keyboard, stylus, microphone, and the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touch screen or similar touch sensitive display. In some embodiments, the input device 206 includes a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.
In one embodiment, the display 208 may comprise any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or tactile signals. In some embodiments, display 208 comprises an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, display 208 may include a wearable display such as a smart watch, smart glasses, heads-up display, and the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alarm or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for generating vibrations, motions, or other haptic feedback. In some embodiments, all or part of the display 208 may be integrated with the input device 206. For example, the input device 206 and the display 208 may form a touch screen or similar touch sensitive display. In other embodiments, the display 208 may be located near the input device 206.
The transmitter 210 is used to provide UL communication signals to the network element 104 and the receiver 212 is used to receive DL communication signals from the network element 104. In some embodiments, the transmitter 210 is configured to transmit a random access preamble to the base unit. Although only one transmitter 210 and one receiver 212 are illustrated, remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.
FIG. 3 depicts one embodiment of an
In various embodiments, the
Fig. 4 illustrates one embodiment of a communication 400 for handover. In particular, communication 400 between a UE402, a source eNB404, a target eNB406, an MME 408, and a serving gateway 410 is illustrated. It is to be appreciated that any of the communications 400 described herein can be considered messages and/or portions of messages. Furthermore, in some embodiments, neither the MME 408 nor the serving gateway 410 can change during the handover procedure.
In some embodiments, the UE402 context within the source eNB404 may include information about roaming and access restrictions that may have been provided at connection establishment and/or the last TA update. Information may be provided to and/or from the source eNB404, the target eNB406, the MME 408, and/or the serving gateway 410.
In some embodiments, the source eNB404 may send information to the UE402 in the first communication 414. In particular, the source eNB404 may configure the UE402 measurement procedures based on roaming and access restriction information and/or other information, such as available multiple frequency band information. In certain embodiments, the measurements provided by the source eNB404 may assist in controlling the functionality of the connection mobility of the UE 402.
In various embodiments, the UE402 may transmit information to the source eNB404 in the second communication 416. In particular, the measurement report may be triggered by the UE402 and sent to the source eNB404 as part of the second communication 416.
In certain embodiments, the source eNB404 may make the decision 418 based on the measurement report and RRM information for the handover UE 402.
In some embodiments, the source eNB404 may send information to the target eNB406 in the third communication 420. In particular, the source eNB404 may issue a handover request message to the target eNB 406. In various embodiments, the source eNB404 may communicate information to prepare the target eNB406 for handover. Such information may include the UE 402X2 signaling context reference, the UE402S1EPC signaling context reference, the target cell ID, RRC context information including the C-RNTI of the UE402, AS configuration, and/or the E-RAB context and physical layer ID of the source cell. In some embodiments, the UE 402X2 and/or UE402S1 signaling references may enable the target eNB406 to address the source eNB404 and EPC. In various embodiments, the E-RAB context may include the necessary RNL and TNL addressing information and/or QoS profiles for the E-RAB.
In various embodiments, admission control may be performed 422 by the target eNB 406. In one embodiment, admission control may depend on the E-RAB QoS information, thereby increasing the likelihood of a successful handover, such as whether resources are granted by the target eNB 406. In some embodiments, the target eNB406 can configure the required resources based on the received E-RAB QoS information and reserve the C-RNTI and optional RACH preamble. In some embodiments, the AS configuration that may be used in the target cell may be specified (e.g., established) independently or AS an increment (e.g., reconfiguration) compared to the AS configuration used in the source cell.
In certain embodiments, the target eNB406 may transmit the information to the source eNB404 in a fourth communication 424. Specifically, the target eNB406 may send a handover request confirm message to the source eNB 404. In some embodiments, the target eNB406 prepares for a handover with level 1 ("L1") and/or level 2 ("L2") and sends a handover request confirm message to the source eNB 404. In various embodiments, the handover request confirm message includes a transparent container to be sent as an RRC message to the UE402 to perform the handover. In such embodiments, the transparent container may include the new C-RNTI, the target eNB406 security algorithm identifier for the selected security algorithm, the dedicated RACH preamble, and/or other parameters (e.g., access parameters, SIBs, etc.). In one embodiment, the handover request confirm message may include RNL and/or TNL information for forwarding the tunnel. In some embodiments, data forwarding may be initiated after the source eNB404 receives the handover request acknowledge message, or upon initiating transmission of a handover command in the DL.
In some embodiments, the source eNB404 may send the information to the UE402 in a fifth communication 426. In particular, the source eNB404 may send an RRC message generated by the target eNB406 to the UE402 to perform the handover. The RRC message may include a radio resource control connection reconfiguration message (e.g., RRCConnectionReconfiguration) having mobility control information (e.g., mobility control information). In various embodiments, the source eNB404 may perform integrity protection and ciphering of the RRC message prior to sending the RRC message. In certain embodiments, the UE402 receives a radio resource control connection reconfiguration message with parameters (e.g., new C-RNTI, target eNB406 security algorithm identifier, dedicated RACH preamble, target eNB406 SIB, etc.) and the eNB404 is instructed by the source to perform handover. In certain embodiments, the UE402 does not delay handover execution for delivery of the HARQ/ARQ response to the source eNB 404.
In various embodiments, the UE402 may detach 428 from the old cell and synchronize with the new cell. In certain embodiments, the source eNB404 may deliver 430 buffered and in-transit packets to the target eNB 406.
In some embodiments, in the sixth communication 432, the source eNB404 may send information to the target eNB 406. In particular, source eNB404 can send a SN status transfer message to target eNB406 to convey uplink PDCP SN receiver status and downlink PDCP SN transmitter status (e.g., for RLC AM) for the E-RAB to which PDCP status preservation is applied. In some embodiments, the uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL SDU and may include a bitmap of the reception status of out-of-sequence UL SDUs that the UE needs to retransmit in the target cell, if any such SDUs exist. In various embodiments, the downlink PDCP SN transmitter status may indicate a next PDCP SN that target eNB406 may assign to a new SDU that does not yet have a PDCP SN. In some embodiments, the source eNB404 may omit sending this message if none of the E-RABs of the UE402 are handled with PDCP status preservation.
In various embodiments, the target eNB406 may buffer 434 packets received from the source eNB 404.
In certain embodiments, the UE402 may send the information to the target eNB406 in a seventh communication 436. Specifically, the UE402 may perform synchronization with the target eNB406 and may access the target cell via the RACH after receiving a radio resource control connection reconfiguration message including mobility control information. In some embodiments, synchronization may occur after a contention-free procedure if a dedicated RACH preamble is indicated in the mobility control information, or may occur after a contention-based procedure if no dedicated preamble is indicated. In various embodiments, the UE402 derives the target eNB406 specific key and configures the security algorithm to be used in the target cell.
In some embodiments, the target eNB406 may send information to the UE402 in an eighth communication 438. In particular, the target eNB406 may be responsive to synchronization of the UE402 with UL allocation and timing advance information.
In various embodiments, the UE402 may transmit information to the target eNB406 in a ninth communication 440. Specifically, the UE402 may send a radio resource control connection reconfiguration complete (e.g., rrcconnectionreconfiguration complete) message including the C-RNTI after successfully accessing the target cell to confirm the handover. In some embodiments, the UE402 may send an uplink buffer status report to the target eNB406 to indicate that the handover procedure for the UE402 is complete. In some embodiments, the target eNB406 can verify the C-RNTI sent in the radio resource control connection reconfiguration complete message. In one embodiment, the target eNB406 can begin transmitting data to the UE402 after the target eNB406 verifies the C-RNTI.
In certain embodiments, in a tenth communication 442, the target eNB406 may send information to the MME 408. Specifically, the target eNB406 may send a path switch request message to the MME 408 to inform the MME 408 that the UE402 has changed cells.
In some embodiments, in the eleventh communication 444, the MME 408 may send the information to the serving gateway 410. In particular, MME 408 may send a modify bearer request message to serving gateway 410.
In various embodiments, the serving gateway 410 may switch 446 the downlink data path to the target eNB 406. In some embodiments, the serving gateway 410 sends one or more end-marker packets to the source eNB404 on the old path, and may then release any user plane and/or TNL resources corresponding to the source eNB 404.
In some embodiments, the serving gateway 410 may send the information to the MME 408 in a twelfth communication 448. In particular, serving gateway 410 may send a modify bearer response message to MME 408.
In some embodiments, in the thirteenth communication 450, the MME 408 may send the information to the target eNB 406. In particular, the MME 408 may acknowledge the path switch request message with a path switch request acknowledge message sent to the target eNB 406.
In various embodiments, in the fourteenth communication 452, the target eNB406 may transmit the information to the source eNB 404. In particular, the target eNB406 may send a UE402 context release message to the source eNB404 to inform the source eNB404 of the successful handover. In one embodiment, the source eNB404 receiving the context release message may trigger a resource release by the source eNB 404. Further, the target eNB406 may send a context release message after receiving the path switch request confirm message from the MME 408.
In certain embodiments, upon receiving the UE402 context release message, the source eNB404 may release 454 the radio and control plane related resources allocated to the UE402 context. In such an embodiment, any ongoing data forwarding may continue.
In various embodiments, the random access procedure may be divided into two different types. For example, the random access procedure may be a contention-based random access procedure as described with respect to fig. 5, or the random access procedure may be a non-contention-based random access procedure as described with respect to fig. 6.
Fig. 5 illustrates one embodiment of a communication 500 for a contention-based random access procedure. In particular, communication 500 between a UE502 and an eNB 504 is illustrated. It is to be appreciated that any of the communications 500 described herein can be considered a message and/or a portion of a message.
In some embodiments, the UE502 may send information to the eNB 504 in the first communication 506. In particular, the UE502 may transmit a random access preamble in the uplink to the eNB 504.
In various embodiments, the eNB 504 may transmit information to the UE502 in the second communication 508. In particular, the eNB 504 may send a random access response to the UE 502. In some embodiments, the random access response may convey one or more of a random access preamble identifier, timing alignment information of a TAG, and/or an assignment of an initial UL grant and a temporary C-RNTI (e.g., which may or may not become permanent in contention resolution).
In certain embodiments, the UE502 may send information to the eNB 504 in the third communication 510. Specifically, the UE502 may send a first scheduled UL transmission to the eNB 504. In various embodiments, the first scheduled UL transmission may convey a ciphered and integrity protected RRC handover acknowledgement generated by the RRC layer and sent by the DCCH, convey a C-RNTI of the UE502 (e.g., allocated by a handover command), and/or include an uplink buffer status report.
In some embodiments, the eNB 504 may send information to the UE502 in the fourth communication 512. Specifically, the eNB 504 may send a contention resolution message to the UE 502.
Fig. 6 illustrates one embodiment of a communication 600 for a non-contention based random access procedure. In particular, communication 600 between a UE602 and an eNB604 is illustrated. It is to be appreciated that any of the communications 600 described herein can be considered a message and/or a portion of a message.
In some embodiments, the eNB604 may send information to the UE602 in the first communication 606. In particular, the eNB604 may send the random access preamble assignment via DL dedicated signaling. In various embodiments, the eNB604 may assign a non-contention random access preamble to the UE602 via a handover command.
In certain embodiments, the UE602 may send information to the eNB604 in the second communication 608. Specifically, the UE602 may transmit a random access preamble to the eNB 604. In some embodiments, the UE602 may send the assigned random access preamble.
In various embodiments, in the third communication 610, the eNB604 may send information to the UE 602. In particular, the eNB604 may transmit a random access response, such as on a DL shared channel. In one embodiment, the third communication 610 may include timing alignment information, an initial UL grant for a handover, a timing alignment information DL data arrival, and/or a random access preamble identifier.
In some embodiments, the handover may not occur correctly due to the following results: RLF occurs after the UE has stayed in a cell for a long period of time and the UE may attempt to re-establish a radio link connection in a different cell (e.g., too late handover); RLF occurs shortly after a successful handover from the source cell to the target cell or during the handover procedure and the UE may attempt to re-establish the radio link connection in the source cell (e.g., too early handover); and/or RLF may occur after or shortly after successful handover from the source cell to the target cell and the UE may attempt to re-establish a radio link connection (e.g., handover to the wrong cell) in cells other than the source cell and the target cell. To overcome the switch from occurring incorrectly, a conditional switch may be used. Conditional switching may function as described with respect to fig. 7.
Fig. 7 illustrates one embodiment of a communication 700 for conditional switching. In particular, communication 700 between a UE 702, a source gNB704 (e.g., or source eNB), a first target gNB 706 (e.g., or target eNB), and a second target gNB708 (e.g., or target eNB) is illustrated. It is to be appreciated that any of the communications 700 described herein can be considered a message and/or a portion of a message.
In some embodiments, in first communication 710, UE 702 may send information to source gNB 704. Specifically, UE 702 may report the measurement results (e.g., RSRP, RSRQ, etc.) to source gNB 704.
In some embodiments, source gNB704 may send information to first target gNB 706 in second communication 712. In particular, source gNB704 may send a handover request to first target gNB 706. In some embodiments, if source gNB704 decides to perform a conditional handover based on measurements sent from UE 702 to source gNB704, source gNB704 sends a handover request to first target gNB 706.
In various embodiments, source gNB704 may send information to second target gNB708 in third communication 714. In particular, source gNB704 may send a handover request to second target gNB 708. Furthermore, in some embodiments, source gNB704 may send handover requests to any number of target gnbs.
In some embodiments, in fourth communication 716, first target gNB 706 may send information to source gNB 704. Specifically, first target gNB 706 may send a handover confirmation to source gNB 704.
In some embodiments, in fifth communication 718, second target gNB708 may send information to source gNB 704. Specifically, second target gNB708 may send a handover acknowledgement to source gNB 704. A handover confirmation message may be sent from any number of target gnbs to source gNB 704.
In various embodiments, in sixth communication 720, source gNB704 may send information to UE 702. In particular, source gNB704 may send information to UE 702 including a radio resource control connection reconfiguration message with conditions and mobility control information for handover configured by source gNB 704. In some embodiments, the sixth communication 720 may include a handover condition corresponding to each of the one or more target gnbs.
In some embodiments, the UE 702 may determine 722 whether a handover condition is satisfied (e.g., triggered) for each of the one or more target gnbs.
In certain embodiments, the UE 702 may send the information to the first target gNB 706 in a seventh communication 724. In particular, the UE 702 may apply radio resource control connection reconfiguration and access the first target gNB 706 in response to the handover condition being satisfied.
In various embodiments, the UE 702 may send the information to the first target gNB 706 in an eighth communication 726. Specifically, UE 702 may send an RRC reconfiguration complete message to first target gNB 706.
In some embodiments, the first target gNB 706 may perform 728 a path switch associated with the core network.
In some embodiments, in ninth communication 730, first target gNB 706 may send information to source gNB 704. Specifically, first target gNB 706 may send a handover complete message to source gNB704 to indicate successful completion.
Fig. 8 illustrates one embodiment of communications 800 for conditional handover corresponding to non-contention based random access. Specifically, communication 800 between UE 802, source gNB804 (e.g., source eNB), first target gNB 806 (e.g., target eNB, base station unit, etc.), and second target gNB808 (e.g., target eNB, base station unit, etc.). It is to be appreciated that any of the communications 800 described herein can be considered a message and/or a portion of a message.
In some embodiments, in the first communication 810, the UE 802 may send information to the source gNB 804. Specifically, UE 802 may report measurement results (e.g., RSRP, RSRQ, etc.) to source gNB 804.
In some embodiments, in second communication 812, source gNB804 may send information to first target gNB 806. In particular, source gNB804 may send a handover request to first target gNB 806. Source gNB804 decides to perform a conditional handover based on measurements sent from UE 802 to source gNB804, source gNB804 sending a handover request to first target gNB 806.
In various embodiments, in third communication 814, source gNB804 may send information to second target gNB 808. In particular, source gNB804 may send a handover request to second target gNB 808. Thus, source gNB804 may send handover requests to any number of target gnbs.
In some embodiments, in fourth communication 816, first target gNB 806 may send information to source gNB 804. Specifically, first target gNB 806 may send a handover acknowledgement to source gNB 804.
In some embodiments, in fifth communication 818, second target gNB808 may send information to source gNB 804. Specifically, second target gNB808 may send a handover acknowledgement to source gNB 804. A handover confirmation message may be sent from any number of target gnbs to source gNB 804.
In various embodiments, in sixth communication 820, source gNB804 may send information to UE 802. In particular, the source gNB804 may send information to the UE 802 including a radio resource control connection reconfiguration message with the conditions for handover and mobility control information configured by the source gNB 804. In certain embodiments, the sixth communication 820 may include a handover command that includes information about one or more target gnbs. In such embodiments, each target gNB may be associated with one condition for triggering a handover. In various embodiments, the radio resource control connection reconfiguration message may include information indicating a non-contention random access preamble.
In some embodiments, the UE 802 may determine 822 whether a handover condition for each of the one or more target gnbs is satisfied (e.g., triggered). In one embodiment, UE 802 may inform source gNB804 with which cell UE 802 is to perform random access prior to selecting one of the one or more target gnbs.
In certain embodiments, in a seventh communication 824, UE 802 may send information to first target gNB 806. In particular, in response to the handover condition being satisfied, the UE 802 transmits a random access preamble to the first target gNB 806. In various embodiments, first target gNB 806 may be selected as a first option for handover because a handover condition corresponding to first target gNB 806 is satisfied, and first target gNB 806 has a higher signal strength (e.g., power level) than other target gnbs of the satisfied handover condition. In some embodiments, UE 802 may not successfully perform a handover to first target gNB 806, such as due to a failure to access first target gNB 806. In such embodiments, the inability to access the first target gNB 806 may be due to the UE 802 not receiving any response from the first target gNB 806 in response to the seventh communication 824. In embodiments where the UE 802 did not successfully perform a handover to the first target gNB 806, the UE 802 may attempt to perform a handover to any other target gNB that satisfies the handover condition (e.g., the UE 802 may select the target gNB based on their signal strength, with the higher signal strength being selected first). Accordingly, any communication described herein corresponding to first target gNB 806 may also relate to communications corresponding to any target gNB. If the UE 802 does not successfully perform a handover to any target gNB that satisfies the handover condition, the UE 802 may perform a re-establishment procedure. In some embodiments, the UE 802 may select any target gNB (e.g., one that does not satisfy the handover condition) to establish communication. In such embodiments, the UE 802 may select the target gNB based on the signal strength without regard to the handover condition (e.g., select the target gNB with the highest signal strength).
In various embodiments, in an eighth communication 826, the first target gNB 806 may send information to the source gNB 804. In particular, first target gNB 806 may send information including the request signaling to source gNB 804. The request signaling may be a request for sequence number state transition information and/or data forwarding information. By sending request signaling in response to receiving the random access preamble, sequence number state transition information and/or data may be sent from source gNB804 to first target gNB 806 before sending the handover complete message, thereby reducing latency.
In some embodiments, in the ninth communication 828, the first target gNB 806 may send information to the UE 802. In particular, the first target gNB 806 may send a random access response to the UE 802.
In some embodiments, in tenth communication 830, source gNB804 may send information to first target gNB 806. In particular, source gNB804 may send sequence number state transition information and/or perform data forwarding procedures to first target gNB 806 to forward data information to first target gNB 806.
In various embodiments, in the eleventh communication 832, the UE 802 may transmit information to the first target gNB 806. Specifically, the UE 802 may send an RRC reconfiguration complete message to the first target gNB 806.
In some embodiments, the first target gNB 806 may perform 834 a path switch associated with the core network.
In some embodiments, in a twelfth communication 836, first target gNB 806 may send information to source gNB 804. In particular, first target gNB 806 may send a handover complete message to source gNB804 to indicate that the handover was successfully completed.
Fig. 9 illustrates one embodiment of communications 900 for conditional handover corresponding to contention-based random access. Specifically, communication 900 between a UE 902, a source gNB904 (e.g., source eNB), a first target gNB906 (e.g., target eNB, base station unit, etc.), and a second target gNB908 (e.g., target eNB, base station unit, etc.) is illustrated. It is to be appreciated that any of the communications 900 described herein can be considered a message and/or a portion of a message.
In some embodiments, in the first communication 910, the UE 902 may send information to the source gNB 904. Specifically, UE 902 may report measurement results (e.g., RSRP, RSRQ, etc.) to source gNB 904.
In certain embodiments, in second communication 912, source gNB904 may send information to first target gNB 906. In particular, source gNB904 may send a handover request to first target gNB 906. Source gNB904 decides to perform conditional handover based on measurements sent from UE 902 to source gNB904, source gNB904 sending a handover request to first target gNB 906.
In various embodiments, in third communication 914, source gNB904 may send information to second target gNB 908. In particular, source gNB904 may send a handover request to second target gNB 908. Further, source gNB904 may send handover requests to any number of target gnbs.
In some embodiments, in fourth communication 916, first target gNB906 may send information to source gNB 904. Specifically, first target gNB906 may send a handover confirmation to source gNB 904.
In some embodiments, the second target gNB908 may send information to the source gNB904 in a fifth communication 918. Specifically, the second target gNB908 may send a handover confirmation to the source gNB 904. A handover confirmation message may be sent from any number of target gbbs to source gbb 904.
In various embodiments, in sixth communication 920, source gNB904 may send information to UE 902. In particular, source gNB904 may send information to UE 902 including a radio resource control connection reconfiguration message with conditions and mobility control information configured by source gNB904 for handover. In some embodiments, the sixth communication 920 may include a handover condition corresponding to each of the one or more target gnbs. In various embodiments, the radio resource control connection reconfiguration message may include information indicating a non-contention random access preamble.
In some embodiments, the UE 902 may determine 922 whether a handover condition is satisfied (e.g., triggered) for each of the one or more target gnbs. In one embodiment, UE 902 may inform source gNB904 which cell UE 902 is to perform random access with before selecting one of the one or more target gnbs.
In certain embodiments, in the seventh communication 924, the UE 902 may send information to the first target gNB 906. In particular, the UE 902 may transmit a random access preamble to the first target gNB906 in response to the handover condition being satisfied. In various embodiments, the first target gNB906 may be selected as a first option for a handover because a handover condition corresponding to the first target gNB906 is satisfied and the first target gNB906 has a higher signal strength (e.g., power level) than other target gnbs of the satisfied handover condition. In some embodiments, the UE 902 may fail to successfully perform a handover to the first target gNB906, such as due to a failure to access the first target gNB 906. In such embodiments, the inability to access the first target gNB906 may be due to the UE 902 not receiving any response from the first target gNB906 in response to the seventh communication 924. In embodiments where the UE 902 did not successfully perform a handover to the first target gNB906, the UE 902 may attempt to perform a handover to any other target gNB that satisfies the handover condition (e.g., the UE 902 may select the target gNB based on their signal strengths, with the higher signal strength being selected first). Accordingly, any communication described herein corresponding to the first target gNB906 may also relate to a communication corresponding to any target gNB. The UE 902 may perform the re-establishment procedure if the UE 902 does not successfully perform a handover to any target gNB that satisfies the handover condition. In some embodiments, the UE 902 may select any target gNB (e.g., a target gNB that does not satisfy a handover condition) to establish communication with. In such embodiments, the UE 902 may select the target gNB based on the signal strength without regard to the handover condition (e.g., select the target gNB with the highest signal strength).
In some embodiments, in the eighth communication 926, the first target gNB906 may send information to the UE 902. In particular, the first target gNB906 may send a random access response to the UE 902.
In various embodiments, in the ninth communication 928, the UE 902 may send information to the first target gNB 906. Specifically, the UE 902 may send a first scheduled UL transmission to the first target gNB 906.
In certain embodiments, in the tenth communication 930, the first target gNB906 may send information to the UE 902. In particular, the first target gNB906 may send contention resolution to the UE 902.
In some embodiments, in the eleventh communication 932, the UE 902 may transmit information to the first target gNB 906. In particular, the UE 902 may send an RRC reconfiguration complete message to the first target gNB906 after determining that the random access is successful.
In various embodiments, in a twelfth communication 934, the first target gNB906 may send information to the source gNB 904. In particular, the first target gNB906 may send information including the request signaling to the source gNB 904. In some embodiments, the request signaling may be a request for sequence number state transition information and/or data forwarding information. By sending request signaling in response to receiving the RRC reconfiguration complete message, sequence number state transition information and/or data may be sent from source gNB904 to first target gNB906 prior to sending the handover complete message, thereby reducing latency.
In some embodiments, the first target gNB906 may perform 936 a path switch associated with the core network.
In certain embodiments, in a thirteenth communication 938, source gNB904 may send information to first target gNB 906. In particular, the source gNB904 may send sequence number state transition information to the first target gNB906 and/or perform data forwarding procedures for forwarding data information to the first target gNB 906.
In various embodiments, in a fourteenth communication 940, the first target gNB906 may send information to the source gNB 904. In particular, first target gNB906 may send a handover complete message to source gNB904 to indicate that the handover was successfully completed.
Figure 10 is a schematic flow chart diagram illustrating one embodiment of a
The
In one embodiment,
FIG. 11 is a schematic flow chart diagram illustrating one embodiment of a
The
In one embodiment, the random access message includes a random access preamble. In another embodiment, the random access message comprises a radio resource control reconfiguration complete message. In certain embodiments,
Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
- 上一篇：一种医用注射器针头装配设备
- 下一篇：多无线电接入技术双连接中的移动性中断减少