Patent Application
20230086614
The present disclosure relates to conditional mobility failure handling in wireless communications.
3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.
Work has started in international telecommunication union (ITU) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.
The NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. The NR shall be inherently forward compatible.
In conditional mobility, UE may receive RRC reconfigurations (i.e., conditional mobility commands) for a mobility in advance, compared to legacy mobility. If/when a mobility condition is satisfied for a target cell related to one of the conditional mobility commands, the UE may trigger an execution of a mobility to the target cell. However, if/when this mobility fails, the UE may perform a cell selection to select a cell for a RRC re-establishment procedure.
An aspect of the present disclosure is to provide method and apparatus for conditional mobility failure handling in a wireless communication system.
Another aspect of the present disclosure is to provide method and apparatus for a CHO based failure handling in a wireless communication system.
Another aspect of the present disclosure is to provide method and apparatus for a CPC based failure handling in a wireless communication system.
According to an embodiment of the present disclosure, a method performed by a wireless device in a wireless communication system comprises: receiving a first conditional mobility command related to a target cell and a second conditional mobility command related to a potential target cell; triggering an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled; performing a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility; and performing a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command.
According to an embodiment of the present disclosure, a wireless device in a wireless communication system comprises: a transceiver; a memory; and at least one processor operatively coupled to the transceiver and the memory, and configured to: control the transceiver to receive a first conditional mobility command related to a target cell and a second conditional mobility command related to a potential target cell; trigger an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled; perform a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility; and perform a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command.
According to an embodiment of the present disclosure, a processor for a wireless device in a wireless communication system is configured to control the wireless device to perform operations comprising: receiving a first conditional mobility command related to a target cell and a second conditional mobility command related to a potential target cell; triggering an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled; performing a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility; and performing a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command.
According to an embodiment of the present disclosure, a computer-readable medium having recorded thereon a program for performing each step of a method on a computer is provided. The method comprises: receiving a first conditional mobility command related to a target cell and a second conditional mobility command related to a potential target cell; triggering an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled; performing a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility; and performing a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command.
According to an embodiment of the present disclosure, a method performed by a source radio access network (RAN) node related to a source cell in a wireless communication system comprises: receiving, from a target RAN node related to a target cell, a second conditional mobility command related to a potential target cell; and transmitting, to a wireless device, a first conditional mobility command related to the target cell, and the second conditional mobility command related to the potential target cell, wherein the wireless device is configured to: trigger an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled; perform a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility; and perform a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command.
According to an embodiment of the present disclosure, a source radio access network (RAN) node related to a source cell in a wireless communication system comprises: a transceiver; a memory; and at least one processor operatively coupled to the transceiver and the memory, and configured to: control the transceiver to receive, from a target RAN node related to a target cell, a second conditional mobility command related to a potential target cell; and control the transceiver to transmit, to a wireless device, a first conditional mobility command related to the target cell, and the second conditional mobility command related to the potential target cell, wherein the wireless device is configured to: trigger an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled; perform a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility; and perform a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command.
The present disclosure can have various advantageous effects.
For example, the disclosure may enhance a mobility robustness by performing a CHO based failure handling using candidate cell lists which are provided from not only the source PCell but also other serving cells, target cells and/or potential target cells. It means that the UE has further changes to initiate another mobility instead of the connection re-establishment from declaring mobility failure (i.e., reconfiguration with sync failure) when there is no CHO configuration provided by the source PCell.
Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and/or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.
The technical features described below may be used by a communication standard by the 3rd generation partnership project (3GPP) standardization organization, a communication standard by the institute of electrical and electronics engineers (IEEE), etc. For example, the communication standards by the 3GPP standardization organization include long-term evolution (LTE) and/or evolution of LTE systems. The evolution of LTE systems includes LTE-advanced (LTE-A), LTE-A Pro, and/or 5G new radio (NR). The communication standard by the IEEE standardization organization includes a wireless local area network (WLAN) system such as IEEE 802.11a/b/g/n/ac/ax. The above system uses various multiple access technologies such as orthogonal frequency division multiple access (OFDMA) and/or single carrier frequency division multiple access (SC-FDMA) for downlink (DL) and/or uplink (UL). For example, only OFDMA may be used for DL and only SC-FDMA may be used for UL. Alternatively, OFDMA and SC-FDMA may be used for DL and/or UL.
Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and/or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and/or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and/or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and/or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate personal area networks (PANs) associated with small/low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.
In the present disclosure, “A or B” may mean “only A”, “only B”, or “both A and B”. In other words, “A or B” in the present disclosure may be interpreted as “A and/or B”. For example, “A, B or C” in the present disclosure may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”.
In the present disclosure, slash (/) or comma (,) may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B or C”.
In the present disclosure, “at least one of A and B” may mean “only A”, “only B” or “both A and B”. In addition, the expression “at least one of A or B” or “at least one of A and/or B” in the present disclosure may be interpreted as same as “at least one of A and B”.
In addition, in the present disclosure, “at least one of A, B and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. In addition, “at least one of A, B or C” or “at least one of A, B and/or C” may mean “at least one of A, B and C”.
Also, parentheses used in the present disclosure may mean “for example”. In detail, when it is shown as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” in the present disclosure is not limited to “PDCCH”, and “PDDCH” may be proposed as an example of “control information”. In addition, even when shown as “control information (i.e., PDCCH)”, “PDCCH” may be proposed as an example of “control information”.
Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.
The terms used throughout the disclosure can be defined as the followings:
‘Mobility’ refers to a procedure for i) changing a PCell of a UE (i.e., handover or PCell change), ii) changing a PSCell of a UE (i.e., SN change or PSCell change), and/or iii) adding a PSCell for a UE (i.e., SN addition or PSCell addition). Therefore, the mobility may comprise at least one of a handover, an SN change or an SN addition. In other words, the mobility may comprise at least one of PCell change, PSCell change or PSCell addition. Throughout the disclosure, performing a mobility to a target cell may refer to applying a mobility command of the target cell or applying a target cell configuration for the target cell in the mobility command of the target cell. The target cell configuration for the target cell may comprise RRC reconfiguration parameters associated with the mobility to the target cell. Further, RRC reconfiguration and RRC connection reconfiguration may be used interchangeably.
In the disclosure, the target cell configuration may also be referred to as candidate cell configuration. The candidate cell configuration may comprise reconfigurationWithSync, which comprise parameters for the synchronous reconfiguration to the target SpCell. For example, the reconfigurationWithSync may comprise at least one of a new UE-identity (i.e., a kind of RNTI value), timer T304, spCellConfigCommon, rach-ConfigDedicated or smtc. The spCellConfigCommon may comprise ServingCellConfigCommon which is used to configure cell specific parameters of a UE's serving cell. The rach-ConfigDedicated may indicate a random access configuration to be used for a reconfiguration with sync (e.g., mobility). The smtc may indicate a synchronization signal/physical broadcast channel (SS/PBCH) block periodicity/offset/duration configuration of target cell for PSCell change, PCell change and/or PSCell addition. The SS/PBCH block may be simply referred to as synchronization signal block (SSB).
‘SN mobility’ refers to a procedure for i) changing a PSCell of a UE (i.e., SN change or PSCell change), and/or ii) adding a PSCell for a UE (i.e., SN addition or PSCell addition). Therefore, the SN mobility may comprise at least one of an SN change or an SN addition. In other words, the SN mobility may comprise at least one of PSCell change or PSCell addition. Throughout the disclosure, performing an SN mobility to a target cell may refer to applying an SN mobility command of the target cell or applying a target cell configuration for the target cell in the SN mobility command of the target cell. The target cell configuration for the target cell may comprise RRC reconfiguration parameters associated with the SN mobility to the target cell. The SN mobility may be a kind of a mobility. The SN mobility command may comprise a SN change command for performing SN change, or SN addition command for performing SN addition.
‘Mobility condition for a target cell’ refers to a triggering condition for a mobility to the target cell. That is, the mobility condition for a target cell refers to a condition that should be satisfied for triggering a mobility to the target cell. Mobility condition may comprise at least one of event A3 condition (i.e., mobility condition for event A3) or event A5 condition (i.e., mobility condition for event A5). The event A3 condition may comprise at least one of an offset value, or a time-to-trigger (TTT). The event A5 condition may comprise at least one of a serving cell threshold, a target cell threshold, or a TTT. The mobility condition for an event may be satisfied if/when an entering condition (or, also referred to as entry condition) for the event is satisfied for at least the TTT. For example, the entering condition for event A3 may be satisfied if a signal quality for a target cell is better than that for a serving cell more than or equal to the offset value. For another example, an entering condition for event A5 may be satisfied if a signal quality for a target cell is better than the target cell threshold and a signal quality for a serving cell is lower than the serving cell threshold. The mobility condition may also be referred to as an execution condition/conditional execution condition/conditional mobility execution condition (e.g., CHO execution condition).
‘SN mobility condition for a target cell’ refers to a triggering condition for an SN mobility (i.e., SN addition or SN change) to the target cell. That is, the SN mobility condition for a target cell refers to a condition that should be satisfied for triggering an SN mobility to the target cell. SN mobility condition for a target cell may be classified as:
i) SN addition condition for a target cell, which refers to a triggering condition for an SN addition of the target cell; or
ii) SN change condition for a target cell, which refers to a triggering condition for an SN change to the target cell.
SN mobility condition may comprise at least one of an event, time-to-trigger (TTT), offset value, or threshold value(s). The SN mobility condition for an event may be satisfied if an entering condition for the event is satisfied for at least the TTT.
For example, SN addition condition may be related to event A4 or event B1. The entering condition for event A4 or B1 may be satisfied if a signal quality for a target cell is better than a threshold.
For example, SN change condition may be related to event A3 or event A5. The entering condition for event A3 may be satisfied if a signal quality for a target cell is better than that for a source PScell more than or equal to the offset value. For another example, the entering condition for event A5 may be satisfied if a signal quality for a target cell is better than a first threshold and a signal quality for a source PScell is lower than a second threshold.
‘Conditional mobility’ refers to a mobility that is performed to a target cell which satisfies a triggering condition among a plurality of candidate target cells. Throughout the disclosure, performing a conditional mobility to a target cell may refer to applying a conditional mobility command of a target cell which satisfies a mobility condition for the target cell among a plurality of candidate target cells or applying a target cell configuration for the target cell in the conditional mobility command of the target cell which satisfies a mobility condition for the target cell among the plurality of candidate target cells. The target cell configuration for the target cell may comprise RRC reconfiguration parameters associated with the conditional mobility to the target cell. Conditional mobility may comprise a conditional handover (i.e., conditional PCell change), a conditional SN change (i.e., conditional PSCell change (CPC)), and/or conditional SN addition (i.e., conditional PSCell addition (CPA)). The conditional PSCell addition/change (CPAC) may comprise the CPC and/or the CPA.
Throughout the disclosure, the terms ‘radio access network (RAN) node’, ‘base station’, ‘eNB’, ‘gNB’ and ‘cell’ may be used interchangeably. Further, a UE may be a kind of a wireless device, and throughout the disclosure, the terms ‘UE’ and ‘wireless device’ may be used interchangeably.
Throughout the disclosure, the terms ‘cell quality’, ‘signal strength’, ‘signal quality’, ‘channel state’, ‘channel quality’, ‘channel state/reference signal received power (RSRP)’ and ‘reference signal received quality (RSRQ)’ may be used interchangeably.
The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals/messages/fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings.
The 5G usage scenarios shown in
Referring to
eMBB focuses on across-the-board enhancements to the data rate, latency, user density, capacity and coverage of mobile broadband access. The eMBB aims ˜10 Gbps of throughput. eMBB far surpasses basic mobile Internet access and covers rich interactive work and media and entertainment applications in cloud and/or augmented reality. Data is one of the key drivers of 5G and may not be able to see dedicated voice services for the first time in the 5G era. In 5G, the voice is expected to be processed as an application simply using the data connection provided by the communication system. The main reason for the increased volume of traffic is an increase in the size of the content and an increase in the number of applications requiring high data rates. Streaming services (audio and video), interactive video and mobile Internet connectivity will become more common as more devices connect to the Internet. Many of these applications require always-on connectivity to push real-time information and notifications to the user. Cloud storage and applications are growing rapidly in mobile communication platforms, which can be applied to both work and entertainment. Cloud storage is a special use case that drives growth of uplink data rate. 5G is also used for remote tasks on the cloud and requires much lower end-to-end delay to maintain a good user experience when the tactile interface is used. In entertainment, for example, cloud games and video streaming are another key factor that increases the demand for mobile broadband capabilities. Entertainment is essential in smartphones and tablets anywhere, including high mobility environments such as trains, cars and airplanes. Another use case is augmented reality and information retrieval for entertainment. Here, augmented reality requires very low latency and instantaneous data amount.
mMTC is designed to enable communication between devices that are low-cost, massive in number and battery-driven, intended to support applications such as smart metering, logistics, and field and body sensors. mMTC aims ˜10 years on battery and/or ˜1 million devices/km2. mMTC allows seamless integration of embedded sensors in all areas and is one of the most widely used 5G applications. Potentially by 2020, internet-of-things (IoT) devices are expected to reach 20.4 billion. Industrial IoT is one of the areas where 5G plays a key role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructures.
URLLC will make it possible for devices and machines to communicate with ultra-reliability, very low latency and high availability, making it ideal for vehicular communication, industrial control, factory automation, remote surgery, smart grids and public safety applications. URLLC aims ˜1 ms of latency. URLLC includes new services that will change the industry through links with ultra-reliability/low latency, such as remote control of key infrastructure and self-driving vehicles. The level of reliability and latency is essential for smart grid control, industrial automation, robotics, drones control and coordination.
Next, a plurality of use cases included in the triangle of
5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means of delivering streams rated from hundreds of megabits per second to gigabits per second. This high speed can be required to deliver TVs with resolutions of 4K or more (6K, 8K and above) as well as virtual reality (VR) and augmented reality (AR). VR and AR applications include mostly immersive sporting events. Certain applications may require special network settings. For example, in the case of a VR game, a game company may need to integrate a core server with an edge network server of a network operator to minimize delay.
Automotive is expected to become an important new driver for 5G, with many use cases for mobile communications to vehicles. For example, entertainment for passengers demands high capacity and high mobile broadband at the same time. This is because future users will continue to expect high-quality connections regardless of their location and speed. Another use case in the automotive sector is an augmented reality dashboard. The driver can identify an object in the dark on top of what is being viewed through the front window through the augmented reality dashboard. The augmented reality dashboard displays information that will inform the driver about the object's distance and movement. In the future, the wireless module enables communication between vehicles, information exchange between the vehicle and the supporting infrastructure, and information exchange between the vehicle and other connected devices (e.g. devices accompanied by a pedestrian). The safety system allows the driver to guide the alternative course of action so that he can drive more safely, thereby reducing the risk of accidents. The next step will be a remotely controlled vehicle or self-driving vehicle. This requires a very reliable and very fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, a self-driving vehicle will perform all driving activities, and the driver will focus only on traffic that the vehicle itself cannot identify. The technical requirements of self-driving vehicles require ultra-low latency and high-speed reliability to increase traffic safety to a level not achievable by humans.
Smart cities and smart homes, which are referred to as smart societies, will be embedded in high density wireless sensor networks. The distributed network of intelligent sensors will identify conditions for cost and energy-efficient maintenance of a city or house. A similar setting can be performed for each home. Temperature sensors, windows and heating controllers, burglar alarms and appliances are all wirelessly connected. Many of these sensors typically require low data rate, low power and low cost. However, for example, real-time high-definition (HD) video may be required for certain types of devices for monitoring.
The consumption and distribution of energy, including heat or gas, is highly dispersed, requiring automated control of distributed sensor networks. The smart grid interconnects these sensors using digital information and communication technologies to collect and act on information. This information can include supplier and consumer behavior, allowing the smart grid to improve the distribution of fuel, such as electricity, in terms of efficiency, reliability, economy, production sustainability, and automated methods. The smart grid can be viewed as another sensor network with low latency.
The health sector has many applications that can benefit from mobile communications. Communication systems can support telemedicine to provide clinical care in remote locations. This can help to reduce barriers to distance and improve access to health services that are not continuously available in distant rural areas. It is also used to save lives in critical care and emergency situations. Mobile communication based wireless sensor networks can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring costs are high for installation and maintenance. Thus, the possibility of replacing a cable with a wireless link that can be reconfigured is an attractive opportunity in many industries. However, achieving this requires that wireless connections operate with similar delay, reliability, and capacity as cables and that their management is simplified. Low latency and very low error probabilities are new requirements that need to be connected to 5G.
Logistics and freight tracking are important use cases of mobile communications that enable tracking of inventory and packages anywhere using location based information systems. Use cases of logistics and freight tracking typically require low data rates, but require a large range and reliable location information.
NR supports multiple numerology (or, subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, wide area in traditional cellular bands may be supported. When the SCS is 30 kHz/60 kHz, dense-urban, lower latency and wider carrier bandwidth may be supported. When the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.
The NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2. The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean “sub 6 GHz range”, FR2 may mean “above 6 GHz range,” and may be referred to as millimeter wave (mmW).
As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).
The first device 210 includes a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone, an unmanned aerial vehicle (UAV), an artificial intelligence (AI) module, a robot, an AR device, a VR device, a mixed reality (MR) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fin-tech device (or, a financial device), a security device, a climate/environmental device, a device related to 5G services, or a device related to the fourth industrial revolution.
The second device 220 includes a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fin-tech device (or, a financial device), a security device, a climate/environmental device, a device related to 5G services, or a device related to the fourth industrial revolution.
For example, the UE may include a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation device, a slate personal computer (PC), a tablet PC, an ultrabook, a wearable device (e.g. a smartwatch, a smart glass, a head mounted display (HMD)). For example, the HMD may be a display device worn on the head. For example, the HMD may be used to implement AR, VR and/or MR.
For example, the drone may be a flying object that is flying by a radio control signal without a person boarding it. For example, the VR device may include a device that implements an object or background in the virtual world. For example, the AR device may include a device that implements connection of an object and/or a background of a virtual world to an object and/or a background of the real world. For example, the MR device may include a device that implements fusion of an object and/or a background of a virtual world to an object and/or a background of the real world. For example, the hologram device may include a device that implements a 360-degree stereoscopic image by recording and playing stereoscopic information by utilizing a phenomenon of interference of light generated by the two laser lights meeting with each other, called holography. For example, the public safety device may include a video relay device or a video device that can be worn by the user's body. For example, the MTC device and the IoT device may be a device that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include a smart meter, a vending machine, a thermometer, a smart bulb, a door lock and/or various sensors. For example, the medical device may be a device used for the purpose of diagnosing, treating, alleviating, handling, or preventing a disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, alleviating, or correcting an injury or disorder. For example, the medical device may be a device used for the purpose of inspecting, replacing or modifying a structure or function. For example, the medical device may be a device used for the purpose of controlling pregnancy. For example, the medical device may include a treatment device, a surgical device, an (in vitro) diagnostic device, a hearing aid and/or a procedural device, etc. For example, a security device may be a device installed to prevent the risk that may occur and to maintain safety. For example, the security device may include a camera, a closed-circuit TV (CCTV), a recorder, or a black box. For example, the fin-tech device may be a device capable of providing financial services such as mobile payment. For example, the fin-tech device may include a payment device or a point of sales (POS). For example, the climate/environmental device may include a device for monitoring or predicting the climate/environment.
The first device 210 may include at least one or more processors, such as a processor 211, at least one memory, such as a memory 212, and at least one transceiver, such as a transceiver 213. The processor 211 may perform the functions, procedures, and/or methods of the first device described throughout the disclosure. The processor 211 may perform one or more protocols. For example, the processor 211 may perform one or more layers of the air interface protocol. The memory 212 is connected to the processor 211 and may store various types of information and/or instructions. The transceiver 213 is connected to the processor 211 and may be controlled by the processor 211 to transmit and receive wireless signals.
The second device 220 may include at least one or more processors, such as a processor 221, at least one memory, such as a memory 222, and at least one transceiver, such as a transceiver 223. The processor 221 may perform the functions, procedures, and/or methods of the second device 220 described throughout the disclosure. The processor 221 may perform one or more protocols. For example, the processor 221 may perform one or more layers of the air interface protocol. The memory 222 is connected to the processor 221 and may store various types of information and/or instructions. The transceiver 223 is connected to the processor 221 and may be controlled by the processor 221 to transmit and receive wireless signals.
The memory 212, 222 may be connected internally or externally to the processor 211, 212, or may be connected to other processors via a variety of technologies such as wired or wireless connections.
The first device 210 and/or the second device 220 may have more than one antenna. For example, antenna 214 and/or antenna 224 may be configured to transmit and receive wireless signals.
Specifically,
Referring to
The E-UTRAN consists of one or more evolved NodeB (eNB) 320. The eNB 320 provides the E-UTRA user plane and control plane protocol terminations towards the UE 10. The eNB 320 is generally a fixed station that communicates with the UE 310. The eNB 320 hosts the functions, such as inter-cell radio resource management (RRM), radio bearer (RB) control, connection mobility control, radio admission control, measurement configuration/provision, dynamic resource allocation (scheduler), etc. The eNB 320 may be referred to as another terminology, such as a base station (BS), a base transceiver system (BTS), an access point (AP), etc.
A downlink (DL) denotes communication from the eNB 320 to the UE 310. An uplink (UL) denotes communication from the UE 310 to the eNB 320. A sidelink (SL) denotes communication between the UEs 310. In the DL, a transmitter may be a part of the eNB 320, and a receiver may be a part of the UE 310. In the UL, the transmitter may be a part of the UE 310, and the receiver may be a part of the eNB 320. In the SL, the transmitter and receiver may be a part of the UE 310.
The EPC includes a mobility management entity (MME), a serving gateway (S-GW) and a packet data network (PDN) gateway (P-GW). The MME hosts the functions, such as non-access stratum (NAS) security, idle state mobility handling, evolved packet system (EPS) bearer control, etc. The S-GW hosts the functions, such as mobility anchoring, etc. The S-GW is a gateway having an E-UTRAN as an endpoint. For convenience, MME/S-GW 330 will be referred to herein simply as a “gateway,” but it is understood that this entity includes both the MME and S-GW. The P-GW hosts the functions, such as UE Internet protocol (IP) address allocation, packet filtering, etc. The P-GW is a gateway having a PDN as an endpoint. The P-GW is connected to an external network.
The UE 310 is connected to the eNB 320 by means of the Uu interface. The UEs 310 are interconnected with each other by means of the PC5 interface. The eNBs 320 are interconnected with each other by means of the X2 interface. The eNBs 320 are also connected by means of the S1 interface to the EPC, more specifically to the MME by means of the S1-MME interface and to the S-GW by means of the S1-U interface. The S1 interface supports a many-to-many relation between MMEs/S-GWs and eNBs.
Specifically,
Referring to
The 5GC includes an access and mobility management function (AMF), a user plane function (UPF) and a session management function (SMF). The AMF hosts the functions, such as NAS security, idle state mobility handling, etc. The AMF is an entity including the functions of the conventional MME. The UPF hosts the functions, such as mobility anchoring, protocol data unit (PDU) handling. The UPF an entity including the functions of the conventional S-GW. The SMF hosts the functions, such as UE IP address allocation, PDU session control.
The gNBs 421 and ng-eNBs 422 are interconnected with each other by means of the Xn interface. The gNBs 421 and ng-eNBs 422 are also connected by means of the NG interfaces to the 5GC, more specifically to the AMF by means of the NG-C interface and to the UPF by means of the NG-U interface.
A protocol structure between network entities described above is described. On the system of
The user/control plane protocol stacks shown in
Referring to
The MAC sublayer belongs to L2. The main services and functions of the MAC sublayer include mapping between logical channels and transport channels, multiplexing/de-multiplexing of MAC service data units (SDUs) belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of one UE by means of logical channel prioritization (LCP), etc. The MAC sublayer offers to the radio link control (RLC) sublayer logical channels.
The RLC sublayer belong to L2. The RLC sublayer supports three transmission modes, i.e. transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM), in order to guarantee various quality of services (QoS) required by radio bearers. The main services and functions of the RLC sublayer depend on the transmission mode. For example, the RLC sublayer provides transfer of upper layer PDUs for all three modes, but provides error correction through ARQ for AM only. In LTE/LTE-A, the RLC sublayer provides concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer) and re-segmentation of RLC data PDUs (only for AM data transfer). In NR, the RLC sublayer provides segmentation (only for AM and UM) and re-segmentation (only for AM) of RLC SDUs and reassembly of SDU (only for AM and UM). That is, the NR does not support concatenation of RLC SDUs. The RLC sublayer offers to the packet data convergence protocol (PDCP) sublayer RLC channels.
The PDCP sublayer belong to L2. The main services and functions of the PDCP sublayer for the user plane include header compression and decompression, transfer of user data, duplicate detection, PDCP PDU routing, retransmission of PDCP SDUs, ciphering and deciphering, etc. The main services and functions of the PDCP sublayer for the control plane include ciphering and integrity protection, transfer of control plane data, etc.
The service data adaptation protocol (SDAP) sublayer belong to L2. The SDAP sublayer is only defined in the user plane. The SDAP sublayer is only defined for NR. The main services and functions of SDAP include, mapping between a QoS flow and a data radio bearer (DRB), and marking QoS flow ID (QFI) in both DL and UL packets. The SDAP sublayer offers to 5GC QoS flows.
A radio resource control (RRC) layer belongs to L3. The RRC layer is only defined in the control plane. The RRC layer controls radio resources between the UE and the network. To this end, the RRC layer exchanges RRC messages between the UE and the BS. The main services and functions of the RRC layer include broadcast of system information related to AS and NAS, paging, establishment, maintenance and release of an RRC connection between the UE and the network, security functions including key management, establishment, configuration, maintenance and release of radio bearers, mobility functions, QoS management functions, UE measurement reporting and control of the reporting, NAS message transfer to/from NAS from/to UE.
In other words, the RRC layer controls logical channels, transport channels, and physical channels in relation to the configuration, reconfiguration, and release of radio bearers. A radio bearer refers to a logical path provided by L1 (PHY layer) and L2 (MAC/RLC/PDCP/SDAP sublayer) for data transmission between a UE and a network. Setting the radio bearer means defining the characteristics of the radio protocol layer and the channel for providing a specific service, and setting each specific parameter and operation method. Radio bearer may be divided into signaling RB (SRB) and data RB (DRB). The SRB is used as a path for transmitting RRC messages in the control plane, and the DRB is used as a path for transmitting user data in the user plane.
An RRC state indicates whether an RRC layer of the UE is logically connected to an RRC layer of the E-UTRAN. In LTE/LTE-A, when the RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in the RRC connected state (RRC_CONNECTED). Otherwise, the UE is in the RRC idle state (RRC_IDLE). In NR, the RRC inactive state (RRC_INACTIVE) is additionally introduced. RRC_INACTIVE may be used for various purposes. For example, the massive machine type communications (MMTC) UEs can be efficiently managed in RRC_INACTIVE. When a specific condition is satisfied, transition is made from one of the above three states to the other.
A predetermined operation may be performed according to the RRC state. In RRC_IDLE, public land mobile network (PLMN) selection, broadcast of system information (SI), cell re-selection mobility, core network (CN) paging and discontinuous reception (DRX) configured by NAS may be performed. The UE shall have been allocated an identifier (ID) which uniquely identifies the UE in a tracking area. No RRC context stored in the BS.
In RRC_CONNECTED, the UE has an RRC connection with the network (i.e. E-UTRAN/NG-RAN). Network-CN connection (both C/U-planes) is also established for UE. The UE AS context is stored in the network and the UE. The RAN knows the cell which the UE belongs to. The network can transmit and/or receive data to/from UE. Network controlled mobility including measurement is also performed.
Most of operations performed in RRC_IDLE may be performed in RRC_INACTIVE. But, instead of CN paging in RRC_IDLE, RAN paging is performed in RRC_INACTIVE. In other words, in RRC_IDLE, paging for mobile terminated (MT) data is initiated by core network and paging area is managed by core network. In RRC_INACTIVE, paging is initiated by NG-RAN, and RAN-based notification area (RNA) is managed by NG-RAN. Further, instead of DRX for CN paging configured by NAS in RRC_IDLE, DRX for RAN paging is configured by NG-RAN in RRC_INACTIVE. Meanwhile, in RRC_INACTIVE, 5GC-NG-RAN connection (both C/U-planes) is established for UE, and the UE AS context is stored in NG-RAN and the UE. NG-RAN knows the RNA which the UE belongs to.
NAS layer is located at the top of the RRC layer. The NAS control protocol performs the functions, such as authentication, mobility management, security control.
The physical channels may be modulated according to OFDM processing and utilizes time and frequency as radio resources. The physical channels consist of a plurality of orthogonal frequency division multiplexing (OFDM) symbols in time domain and a plurality of subcarriers in frequency domain. One subframe consists of a plurality of OFDM symbols in the time domain. A resource block is a resource allocation unit, and consists of a plurality of OFDM symbols and a plurality of subcarriers. In addition, each subframe may use specific subcarriers of specific OFDM symbols (e.g. first OFDM symbol) of the corresponding subframe for a physical downlink control channel (PDCCH), i.e. L1/L2 control channel. A transmission time interval (TTI) is a basic unit of time used by a scheduler for resource allocation. The TTI may be defined in units of one or a plurality of slots, or may be defined in units of mini-slots.
The transport channels are classified according to how and with what characteristics data are transferred over the radio interface. DL transport channels include a broadcast channel (BCH) used for transmitting system information, a downlink shared channel (DL-SCH) used for transmitting user traffic or control signals, and a paging channel (PCH) used for paging a UE. UL transport channels include an uplink shared channel (UL-SCH) for transmitting user traffic or control signals and a random access channel (RACH) normally used for initial access to a cell.
Different kinds of data transfer services are offered by MAC sublayer. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels.
Control channels are used for the transfer of control plane information only. The control channels include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH) and a dedicated control channel (DCCH). The BCCH is a DL channel for broadcasting system control information. The PCCH is DL channel that transfers paging information, system information change notifications. The CCCH is a channel for transmitting control information between UEs and network. This channel is used for UEs having no RRC connection with the network. The DCCH is a point-to-point bi-directional channel that transmits dedicated control information between a UE and the network. This channel is used by UEs having an RRC connection.
Traffic channels are used for the transfer of user plane information only. The traffic channels include a dedicated traffic channel (DTCH). The DTCH is a point-to-point channel, dedicated to one UE, for the transfer of user information. The DTCH can exist in both UL and DL.
Regarding mapping between the logical channels and transport channels, in DL, BCCH can be mapped to BCH, BCCH can be mapped to DL-SCH, PCCH can be mapped to PCH, CCCH can be mapped to DL-SCH, DCCH can be mapped to DL-SCH, and DTCH can be mapped to DL-SCH. In UL, CCCH can be mapped to UL-SCH, DCCH can be mapped to UL-SCH, and DTCH can be mapped to UL-SCH.
The frame structure illustrated in
Referring to
The following table shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per for the extended CP, according to the subcarrier spacing Δf=2 u*15 kHz.
A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g. subcarrier spacing) and carrier, a resource grid of Nsize,ugrid,x*NRBsc subcarriers and Nsubframe,usymb OFDM symbols is defined, starting at common resource block (CRB) Nstart,ugrid indicated by higher-layer signaling (e.g. radio resource control (RRC) signaling), where Nsize,ugrid,x is the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink. NRBsc is the number of subcarriers per RB. In the 3GPP based wireless communication system, NRBsc is 12 generally. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth Nsize,ugrid for subcarrier spacing configuration u is given by the higher-layer parameter (e.g. RRC parameter). Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is referred to as a resource element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index 1 representing a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In the 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with ‘point A’ which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and numbered from 0 to NsizeBWP,i−1, where i is the number of the bandwidth part. The relation between the physical resource block nPRB in the bandwidth part i and the common resource block nCRB is as follows: nPRB=nCRB+NsizeBWP,i, where NsizeBWP,i is the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.
In the present disclosure, the term “cell” may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A “cell” of a geographic area may be understood as coverage within which a node can provide service using a carrier and a “cell” as radio resources (e.g. time-frequency resources) is associated with bandwidth (BW) which is a frequency range configured by the carrier. The “cell” associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a downlink (DL) component carrier (CC) and a uplink (UL) CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the “cell” of radio resources used by the node. Accordingly, the term “cell” may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.
In carrier aggregation (CA), two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured the UE only has one radio resource control (RRC) connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the non-access stratum (NAS) mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of Special Cell. The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For dual connectivity operation, the term Special Cell (SpCell) refers to the PCell of the master cell group (MCG) or the PSCell of the secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprising of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprising of the PSCell and zero or more SCells, for a UE configured with dual connectivity (DC). For a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the PCell. For a UE in RRC_CONNECTED configured with CA/DC the term “serving cells” is used to denote the set of cells comprising of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.
In
In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to PDSCH, PBCH and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to PUCCH, and downlink control information (DCI) is mapped to PDCCH. A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.
Data unit(s) (e.g. PDCP SDU, PDCP PDU, RLC SDU, RLC PDU, RLC SDU, MAC SDU, MAC CE, MAC PDU) in the present disclosure is(are) transmitted/received on a physical channel (e.g. PDSCH, PUSCH) based on resource allocation (e.g. UL grant, DL assignment). In the present disclosure, uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink assignment. The resource allocation includes time domain resource allocation and frequency domain resource allocation. In the present disclosure, an uplink grant is either received by the UE dynamically on PDCCH, in a Random Access Response, or configured to the UE semi-persistently by RRC. In the present disclosure, downlink assignment is either received by the UE dynamically on the PDCCH, or configured to the UE semi-persistently by RRC signalling from the BS.
Hereinafter, signalling radio bearer (SRB) is described.
Signalling radio bearer may be defined as a radio bearer (RB) that is used only for a transmission of RRC and/or NAS messages. More specifically, the following SRBs may be defined:
SRB0 may be used for RRC messages using the CCCH logical channel;
SRB1 may be used for for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages prior to the establishment of SRB2, all using DCCH logical channel;
SRB2 may be used for NAS messages and for RRC messages which include logged measurement information, all using DCCH logical channel. SRB2 has a lower priority than SRB1 and may be configured by the network after AS security activation; and
SRB3 may be used for specific RRC messages when UE is in DC (e.g., (NG)EN-DC and/or NR-DC), all using DCCH logical channel.
In downlink, piggybacking of NAS messages may be used only for one dependant (i.e. with joint success/failure) procedure: bearer establishment/modification/release. In uplink, piggybacking of NAS message may be used only for transferring the initial NAS message during connection setup and connection resume.
The NAS messages transferred via SRB2 may also be contained in RRC messages, which however do not include any RRC protocol control information.
Once AS security is activated, all RRC messages on SRB1, SRB2 and SRB3, including those containing NAS messages, may be integrity protected and ciphered by PDCP. NAS may independently apply integrity protection and ciphering to the NAS messages.
Split SRB may be supported for all the MR-DC options in both SRB1 and SRB2 (split SRB may not be supported for SRB0 and SRB3).
For operation with shared spectrum channel access, SRB0, SRB1 and SRB3 may be assigned with the highest priority Channel Access Priority Class (CAPC), (i.e. CAPC=1) while CAPC for SRB2 is configurable.
The purpose of the RRC connection re-establishment procedure is to re-establish the RRC connection. A UE in RRC_CONNECTED, for which AS security has been activated with SRB2 and at least one DRB setup, may initiate the RRC re-establishment procedure in order to continue the RRC connection. The connection re-establishment may succeed if the network is able to find and verify a valid UE context or, if the UE context cannot be retrieved, and the network may respond with an RRCSetup.
The network may apply the RRC connection re-establishment procedure as follows:
When AS security has been activated and the network retrieves or verifies the UE context:
to re-activate AS security without changing algorithms;
to re-establish and resume the SRB1;
When UE is re-establishing an RRC connection, and the network is not able to retrieve or verify the UE context:
to discard the stored AS Context and release all RBs;
to fallback to establish a new RRC connection.
If AS security has not been activated, the UE shall not initiate the RRC connection re-establishment procedure but instead move to RRC_IDLE directly, with release cause ‘other’. If AS security has been activated, but SRB2 and at least one DRB are not setup, the UE may not initiate the RRC connection re-establishment procedure but instead move to RRC_IDLE directly, with release cause ‘RRC connection failure’.
The UE may initiate the RRC connection re-establishment procedure when one of the following conditions is met:
1>upon detecting radio link failure of the MCG and t316 is not configured; or
1>upon detecting radio link failure of the MCG while SCG transmission is suspended; or
1>upon detecting radio link failure of the MCG while PSCell change is ongoing; or
1>upon re-configuration with sync failure of the MCG; or
1>upon mobility from NR failure; or
1>upon integrity check failure indication from lower layers concerning SRB1 or SRB2, except if the integrity check failure is detected on the RRCReestablishment message; or
1>upon an RRC connection reconfiguration failure; or
1>upon detecting radio link failure for the SCG while MCG transmission is suspended in NR-DC or in NE-DC; or
1>upon reconfiguration with sync failure of the SCG while MCG transmission is suspended; or
1>upon SCG change failure while MCG transmission is suspended; or
1>upon SCG configuration failure while MCG transmission is suspended in NR-DC or in NE-DC; or
1>upon integrity check failure indication from SCG lower layers concerning SRB3 while MCG is suspended; or
1>upon T316 expiry.
During the RRC connection re-establishment procedure upon/after the RRC connection re-establishment procedure is initiated, the UE may perform steps S901 to S903. In step S901, the UE may transmit an RRCReestablishmentRequest message to the network. In step S1903, the network may transmit an RRCReestablishment message to the UE. In step S1905, the UE may transmit an RRCReestablishmentComplete message to the network.
Referring to
MN (e.g., MN 1011) refers to a main RAN node providing services to a UE in DC situation. SN (e.g., SN 1021) refers to an additional RAN node providing services to the UE with the MN in the DC situation. If one RAN node provides services to a UE, the RAN node may be a MN. SN can exist if MN exists.
For example, the MN may be associated with macro cell whose coverage is relatively larger than that of a small cell. However, the MN does not have to be associated with macro cell—that is, the MN may be associated with a small cell. Throughout the disclosure, a RAN node that is associated with a macro cell may be referred to as ‘macro cell node’. MN may comprise macro cell node.
For example, the SN may be associated with small cell (e.g., micro cell, pico cell, femto cell) whose coverage is relatively smaller than that of a macro cell. However, the SN does not have to be associated with small cell—that is, the SN may be associated with a macro cell. Throughout the disclosure, a RAN node that is associated with a small cell may be referred to as ‘small cell node’. SN may comprise small cell node.
The MN may be associated with a master cell group (MCG). MCG may refer to a group of serving cells associated with the MN, and may comprise a primary cell (PCell) and optionally one or more secondary cells (SCells). User plane data and/or control plane data may be transported from a core network to the MN through a MCG bearer. MCG bearer refers to a bearer whose radio protocols are located in the MN to use MN resources. As shown in
The SN may be associated with a secondary cell group (SCG). SCG may refer to a group of serving cells associated with the SN, and may comprise a primary secondary cell (PSCell) and optionally one or more SCells. User plane data may be transported from a core network to the SN through a SCG bearer. SCG bearer refers to a bearer whose radio protocols are located in the SN to use SN resources. As shown in
User plane data and/or control plane data may be transported from a core network to the MN and split up/duplicated in the MN, and at least part of the split/duplicated data may be forwarded to the SN through a split bearer. Split bearer refers to a bearer whose radio protocols are located in both the MN and the SN to use both MN resources and SN resources. As shown in
According to various embodiments, PDCP anchor/PDCP anchor point/PDCP anchor node refers to a RAN node comprising a PDCP entity which splits up and/or duplicates data and forwards at least part of the split/duplicated data over X2/Xn interface to another RAN node. In the example of
According to various embodiments, the MN for the UE may be changed. This may be referred to as handover, or a MN handover.
According to various embodiments, a SN may newly start providing radio resources to the UE, establishing a connection with the UE, and/or communicating with the UE (i.e., SN for the UE may be newly added). This may be referred to as a SN addition.
According to various embodiments, a SN for the UE may be changed while the MN for the UE is maintained. This may be referred to as a SN change.
According to various embodiments, DC may comprise E-UTRAN NR-DC (EN-DC), and/or multi-radio access technology (RAT)-DC (MR-DC). EN-DC refers to a DC situation in which a UE utilizes radio resources provided by E-UTRAN node and NR RAN node. MR-DC refers to a DC situation in which a UE utilizes radio resources provided by RAN nodes with different RATs.
Referring to
In step S1103, the UE may transmit a measurement report message to the source cell. The measurement report message may comprise a result of measurement on neighbor cell(s) around the UE which can be detected by the UE. The UE may generate the measurement report message according to a measurement configuration and/or measurement control information in the measurement control message received in step S1101.
In step S1105, the source cell may make a mobility decision based on the measurement report. For example, the source cell may make a mobility decision and determine candidate target cells (e.g., target cell 1 and target cell 2) for mobility among neighbor cells around the UE based on a result of measurement (e.g., signal quality, reference signal received power (RSRP), reference signal received quality (RSRP)) on the neighbor cells.
In step S1107, the source cell may transmit mobility request messages to the target cell 1 and the target cell 2 which are determined in step S1105. That is, the source cell may perform mobility preparation with the target cell 1 and the target cell 2. The mobility request message may comprise necessary information to prepare the mobility at the target side (e.g., target cell 1 and target cell 2).
In step S1109, each of the target cell 1 and the target cell 2 may perform an admission control based on information included in the mobility request message. The target cell may configure and reserve the required resources (e.g., C-RNTI and/or RACH preamble). The AS-configuration to be used in the target cell can either be specified independently (i.e. an “establishment”) or as a delta compared to the AS-configuration used in the source cell (i.e. a “reconfiguration”).
In step S111, the target cell and the target cell 2 may transmit a mobility request acknowledge (ACK) message to the source cell. The mobility request ACK message may comprise information on resources reserved and prepared for a mobility. For example, the mobility request ACK message may comprise a transparent container to be sent to the UE as an RRC message to perform the mobility. The container may include a new C-RNTI, target gNB security algorithm identifiers for the selected security algorithms, a dedicated RACH preamble, and/or possibly some other parameters i.e. access parameters, SIBs. If RACH-less mobility is configured, the container may include timing adjustment indication and optionally a preallocated uplink grant. The mobility request ACK message may also include RNL/TNL information for forwarding tunnels, if necessary. As soon as the source cell receives the mobility request ACK message, or as soon as the transmission of the conditional mobility command is initiated in the downlink, data forwarding may be initiated.
In step S1113, the source cell may transmit a conditional reconfiguration to the UE. The conditional reconfiguration may be also referred to as (or, may comprise) conditional handover (CHO) configuration and/or a conditional mobility command (e.g., CHO command). The conditional reconfiguration may comprise a conditional reconfiguration for each of the candidate target cells (e.g., target cell 1, target cell 2). For example, the conditional reconfiguration may comprise a conditional reconfiguration for the target cell 1, and a conditional reconfiguration for the target cell 2. The conditional reconfiguration for the target cell 1 may comprise a mobility condition for the target cell 1, and a target cell configuration for the target cell 1. The target cell configuration for the target cell 1 may comprise RRC reconfiguration parameters associated with a mobility to the target cell 1, including information on resources reserved for the mobility to the target cell 1. Similarly, the conditional reconfiguration for the target cell 2 may comprise a mobility condition for the target cell 2, and a target cell configuration for the target cell 2. The target cell configuration for the target cell 2 may comprise RRC reconfiguration parameters associated with a mobility to the target cell 2, including information on resources reserved for the mobility to the target cell 2.
The mobility condition may inform at least one measurement ID. For example, the mobility condition may inform at most 2 measurement IDs. If a mobility condition of a target cell informs a measurement ID which is related to a measurement object A and a report configuration B, evaluating the mobility condition may comprise determining whether a measurement result on the measurement object A satisfies a report condition in the report configuration B. If the measurement result on the measurement object A satisfies the report condition in the report configuration B according to the evaluation of the mobility condition, the UE may determine that the mobility condition of the target cell is satisfied (or, the target cell/measurement result for the target cell satisfies the mobility condition of the target cell), and perform a mobility to the target cell.
In step S1115, the UE may perform an evaluation of the mobility condition for the candidate target cells (e.g., target cell 1, target cell 2) and select a target cell for a mobility among the candidate target cells. For example, the UE may perform measurements on the candidate target cells, and determine whether a candidate target cell satisfies a mobility condition for the candidate target cell among the candidate target cells based on a result of the measurements on the candidate target cells. If the UE identifies that the target cell 1 satisfies a mobility condition for the target cell 1, the UE may select the target cell 1 as a target cell for the mobility.
In step S1117, the UE may perform a random access to the selected target cell (e.g., target cell 1). For example, the UE may transmit a random access preamble to the target cell 1, and receive a random access response comprising an uplink grant from the target cell 1. If RACH-less mobility is configured, the step S1117 may be omitted, and the uplink grant may be provided in step S1113.
In step S1119, the UE may transmit a mobility complete message to the target cell 1. When the UE has successfully accessed the target cell 1 (or, received uplink grant when RACH-less mobility is configured), the UE may transmit a mobility complete message comprising a C-RNTI to confirm the mobility, along with uplink buffer status report, whenever possible, to the target cell 1 to indicate that the mobility procedure is completed for the UE. The target cell 1 may verify the C-RNTI transmitted in the mobility complete message.
In step S1121, the target cell 1 may transmit a sequence number (SN) status request message to the source cell. The target cell 1 may request the source cell to inform the target cell 1 of a SN of a packet the target cell 1 has to transmit after the mobility, via the SN status request message.
In step S1123, the source cell may transmit a conditional mobility cancellation message to the target cell 2 which is not selected as a target cell for a mobility among the candidate target cells. After receiving the conditional mobility cancellation message, the target cell 2 may release resources that are reserved in case of a mobility.
In step S1125, the target cell 2 may transmit a conditional mobility cancellation confirmation message to the source cell, as a response for the conditional mobility cancellation message. The conditional mobility cancellation confirmation message may inform that the target cell 2 has released resources reserved in case of a mobility.
In step S1127, the source cell may transmit a SN status transfer message to the target cell 1, as a response for the SN status request message. The SN status transfer message may inform the target cell 1 of a SN of a packet the target cell 1 has to transmit after the mobility.
In step S1129, the source cell may perform a data forwarding to the target cell 1. For example, the source cell may forward data received from a core network to the target cell 1 so that the target cell 1 can now transmit the data to the UE.
Conditional mobility is a kind of conditional reconfiguration. Hereinafter, Conditional reconfiguration is described.
The network may configure the UE with conditional reconfiguration (i.e., conditional handover and/or conditional PSCell addition/change) including per candidate target cell an RRCConnectionReconfiguration (i.e., conditional mobility command) to only be applied upon the fulfilment of an associated execution condition (i.e., mobility condition).
For conditional reconfiguration, the UE shall:
1>if the received conditionalReconfiguration includes the condReconfigurationToRemoveList:
2>perform the conditional reconfiguration removal procedure;
1>if the received conditionalReconfiguration includes the condReconfigurationToAddModList:
2>perform the conditional reconfiguration addition/modification procedure.
I. Conditional Reconfiguration Addition/Modification
The UE shall:
1>for each condReconfigurationId (i.e., index related to a mobility command) included in the received condReconfigurationToAddModList:
2>if an entry with the matching condReconfigurationId exists in the condReconfigurationList within the VarConditionalReconfiguration (i.e., list of {index, mobility condition, mobility command} for each target cell stored in the UE):
3>replace the entry with the values received for this condReconfigurationId;
2>else:
3>add a new entry for this condReconfigurationId within the VarConditionalReconfiguration;
3>store the associated RRCConnectionReconfiguration (i.e., mobility command and/or mobility condition) in VarConditionalReconfiguration;
2>monitor the triggering conditions (i.e., mobility conditions) associated to the measurement identities of that condReconfigurationId;
II. Conditional Reconfiguration Removal
The UE shall:
1>for each condReconfigurationId included in the received condReconfigurationToRemoveList that is part of the current UE configuration in VarConditionalReconfiguration:
2>stop the monitoring of triggering conditions linked by the measurement identities;
2>remove the entry with the matching condReconfigurationId from the condReconfigurationList within the VarConditionalReconfiguration;
The UE does not consider the conditional reconfiguration message as erroneous if the condReconfigurationToRemoveList includes any condReconfigurationId value that is not part of the current UE configuration.
III. Conditional Reconfiguration Execution
For the measId for which the triggering condition for conditional reconfiguration was fulfilled, the UE shall:
1>for each condReconfigurationId within the VarConditionalReconfiguration that has that measId associated to its stored RRCConnectionReconfiguration (i.e., mobility command):
2>if all triggering conditions are fulfilled for that condReconfigurationId:
3>consider the target cell candidate within the stored RRCConnectionReconfiguration, associated to that condReconfigurationId, as a triggered cell;
1>if the more than one triggered cell exists:
2>select one of the triggered cells as the selected cell for conditional reconfiguration;
1>for the selected cell of conditional reconfiguration:
2>if the stored RRCConnectionReconfiguration associated to the selected cell includes mobilityControlInfo (conditional handover):
3>apply the stored RRCConnectionReconfiguration associated to that condReconfigurationId and perform a handover to the selected cell;
2>else if the stored RRCConnectionReconfiguration includes nr-Config (conditional PSCell addition/change):
3>apply the stored RRCConnectionReconfiguration associated to that condReconfigurationId and perform the SN change/addition procedure for the selected cell;
If multiple cells are triggered in conditional PSCell addition/change execution, the UE may consider beams and beam quality to select one of the triggered cells for execution.
The structure of the conditional reconfiguration message or the information element (IE) ConditionalReconfiguration may be as the following Table 5. The IE ConditionalReconfiguration may be used to add, modify or release the configuration of a conditional handover, a conditional PSCell addition/change per target candidate cell.
In Table 5, condReconfigurationToAddModList may refer to list of conditional reconfigurations (i.e. conditional handover or conditional PSCell change/addition) to add and/or modify. Also, condReconfigurationToRemoveList may refer to list of conditional reconfigurations (i.e. conditional handover or conditional PSCell change/addition) to remove. CondReconfigurationId may refer to an index related to a mobility command. The contents of the IE CondReconfigurationId may be as the following Table 6. The IE ConditionalReconfigurationId may be used to identify a conditional reconfiguration.
In Table 6, maxCondConfig may refer to the maximum number of conditional reconfigurations (i.e., CondReconfigurationAddMods). The structure of IE CondReconfigurationToAddModList may be as the following Table 7. The IE CondReconfigurationToAddModList may concern a list of conditional reconfigurations (i.e. conditional handover, conditional PSCell addition/change) to add or modify, with for each entry the measId (associated to the triggering condition configuration) and the associated RRCConnectionReconfiguration.
In Table 7, CondReconfigurationAddMod may refer to a conditional reconfiguration for a target cell. CondReconfigurationId may refer to an index of the CondReconfigurationAddMod, which may be related to a mobility command of the target cell. The triggerCondition may refer to a mobility condition for the target cell. The RRCConnectionReconfiguration contained in the condReconfigurationToApply may refer to a mobility command of the target cell. As described above, the conditional reconfiguration may also be referred to as CHO configuration. The structure of the CHO configuration or IE CHOConfiguration may be as the following Table 8:
In Table 8, CHOToReleaseList may correspond to condReconfigurationToRemoveList. CHOToAddModList may correspond to CondReconfigurationToAddModList. CHOCondition may correspond to triggerCondition. The maxCHO may correspond to maxCondConfig. That is, the maxCHO may refer to the maximum number of CHO configurations (i.e., CHOToAddMods). The chold may correspond to condReconfigurationId. CHOToAddMod may correspond to CondReconfigurationToAddMod, which may refer to a CHO configuration for a target cell. The choId may refer to an index of the CondReconfigurationToAddMod, which may be related to a mobility command of the target cell. The conditionId may refer to an index of the CHOCondition (i.e., mobility condition for the target cell), which may be related to a choConditionConfig. The CHOCellConfiguration contained in the choCellConfiguration may refer to a mobility command of the target cell. The choCellConfiguration may correspond to condReconfigurationToApply.The structure of IE CHOCondition may be as the following Table 9:
In the disclosure, various timers may be defined as the following table 10:
As described above, a UE may receive a conditional handover command related to a target cell. The conditional handover command may comprise a handover condition for the target cell, candidate cell configuration for the target cell, and the candidate cell configuration for the target cell may comprise timer T304. If the handover condition for the target cell is satisfied, the UE may execute/trigger a conditional handover to the target cell based on the candidate cell configuration for the target cell, upon which the timer T304 starts. While the timer T304 is running (i.e., during a procedure of the conditional handover to the target cell), the UE may attempt a random access on the target cell. Upon successful completion of the random access on the target cell (i.e., upon successful completion of the conditional handover to the target cell), the timer T304 may stop. However, if the random access on the target cell fails (i.e., the conditional handover to the target cell fails) and the timer T304 expires, the UE shall: 1>release dedicated preambles provided in rach-ConfigDedicated if configured;
1>revert back to the UE configuration used in the source PCell (i.e., revert back to the source cell configuration);
1>initiate the RRC connection re-establishment procedure.
The UE configuration may comprise state variables and parameters of each radio bearer.
Hereinafter, fast MCG recovery is described.
A UE may be configured with a timer T316. If the UE is configured with the timer T316, the UE may consider that the fast MCG recovery is available.
The UE may detect a radio link failure (RLF) of a MCG (or, detect a MCG failure/MCG RLF) according to the following procedure:
1>upon T310 expiry in PCell; or
1>upon random access problem indication from MCG MAC while neither T300, T301, T304, T311 nor T319 are running; or
1>upon indication from MCG RLC that the maximum number of retransmissions has been reached:
2>consider radio link failure to be detected for the MCG (i.e., RLF of the MCG/MCG failure).
Upon detecting the RLF of the MCG and fast MCG link recovery is not available (i.e., T316 is not configured), the UE may initiate a RRC connection re-establishment procedure. However, upon/after detecting the RLF of the MCG but fast MCG link recovery is available (i.e., T316 is configured), the UE shall:
1>if fast MCG link recovery is configured (i.e., T316 is configured); and
1>if SCG transmission is not suspended; and
1>if PSCell change is not ongoing (i.e., timer T304 for the NR PSCell is not running in case of NR-DC or timer T307 of the E-UTRA PSCell is not running in NE-DC):
2>initiate the MCG failure information procedure (also referred to as fast MCG recovery procedure) to report MCG radio link failure.
The purpose of the MCG failure information procedure may comprise informing NR MN about an MCG failure the UE has experienced (i.e., MCG radio link failure). A UE in RRC_CONNECTED, for which AS security has been activated with SRB2 and at least one DRB setup, may initiate the fast MCG link recovery procedure in order to continue the RRC connection without re-establishment.
A UE configured with split SRB1 or SRB3 may initiate the procedure to report MCG failures when neither MCG nor SCG transmission is suspended, fast MCG link recovery is configured (i.e. T316 is configured), and upon detecting a RLF of the MCG while T316 is not running.
Upon initiating the MCG failure information procedure, the UE shall:
1>suspend MCG transmission for all SRBs and DRBs, except SRB0;
1>reset MCG-MAC;
1>start timer T316;
1>if SRB1 is configured as split SRB:
2>submit the MCGFailureInformation message to lower layers for transmission via SRB1, upon which the procedure ends;
2>else (i.e. SRB3 configured):
3>submit the MCGFailureInformation message to lower layers for transmission embedded in NR RRC message ULInformationTransferMRDC via SRB3.
For example, if the UE receives RRCReconfiguration message comprising reconfigurationWithSync for the PCell in response to the MCGFailureInformation message, the UE may determine that the fast MCG recovery succeeds, and stop the timer T316. For another example, if the UE receives MobilityFromNRCommand message in response to the MCGFailureInformation message, the UE may determine that the fast MCG recovery succeeds, and stop the timer T316. The UE may also stop the timer T316 upon receiving RRCRelease message, and/or upon initiating the RRC connection re-establishment procedure.
On the other hand, if T316 expires (i.e., fast MCG recovery fails), the UE may initiate the RRC connection re-establishment procedure.
In summary, if the fast MCG recovery is configured (i.e., T316 is configured), the UE may trigger an MCG fast recovery procedure in which a MCG failure information message is transmitted to the network via SCG, upon detecting a PCell failure (i.e., MCG failure). And if the fast MCG recovery fails (i.e., T316 expires), the UE may initiate the RRC re-establishment procedure.
Hereinafter, CHO failure handling (or, CHO based failure handling/conditional mobility failure handling) is described.
Upon initiation of the RRC re-establishment procedure, the UE shall:
1>start timer T311;
1>stop timer T316, if running;
1>perform cell selection in accordance with a cell selection process.
As a result of the cell selection in the cell selection process, the UE may select a suitable NR cell. Upon selecting a suitable NR cell and while the timer T311 is running, the UE shall:
1>if attemptCHO (i.e., conditional mobility attempt configuration) is configured; and
1>if the selected cell is one of the candidate cells in VarCHO-Config (i.e., if the selected cell is one of the candidate cells related to conditional mobility commands the UE has received and stored):
2>apply the stored cho-RRCReconfig associated to the selected cell (i.e., apply the stored candidate cell configuration for the selected cell) and perform a mobility to the selected cell.
In summary, during the RRC connection re-establishment procedure, if a serving cell (e.g., PCell) configured the UE to try CHO at the selected CHO candidate cell (i.e., if the network configured the UE with attemptCHO/attemptCondReconfig/conditional mobility attempt configuration), the UE may perform a cell selection and if the selected cell is a CHO candidate, then the UE may attempt CHO execution to the selected cell by using the stored CHO command/candidate cell configuration for the selected cell (e.g., condRRCReconfig for the selected cell)—otherwise, the re-establishment procedure may be performed. The UE may perform the CHO execution instead of performing legacy re-establishment, since the UE still has CHO candidate available. The conditional mobility attempt configuration may comprise an indication to perform a conditional mobility failure handling (i.e., indication to perform a conditional mobility to a candidate cell selected in a RRC connection re-establishment procedure if/when the selected candidate cell is related to one of conditional mobility command(s) stored in the wireless device).
As illustrated above, upon a handover failure (i.e., reconfiguration with sync failure and/or T304 expiry), the UE may revert back to the UE configuration used in the source PCell (i.e., source cell configuration) and initiate the CHO based failure handling.
However, the CHO based failure handling may only be able to be allowed if the source PCell has configured the CHO configuration (i.e., conditional mobility command) before. Thus, it may cause an increase in a mobility failure rate by performing RRC Re-establishment procedure even though there is at least one candidate cell list of conditional mobility from other serving cell and/or potential target cell for the UE capable to perform the CHO based failure handling. This is because the UE currently cannot reuse CHO and/or CPC configuration which is configured by other serving cells and/or the potential target cells by focusing on the UE configuration used in the source PCell only.
Therefore, various embodiments of the present disclosure provide solutions to utilize at least one candidate cell list of conditional mobility from other serving cell and/or potential target cell for the UE capable to perform the CHO based failure handling (i.e., conditional mobility failure handling).
In the disclosure, further definitions may be used:
“Source cell (or, serving cell)” refers to a cell currently serving a UE/wireless device, and from which a mobility is to be performed. The source cell may comprise source PCell, source SCell and/or source PSCell.
“Target cell” refers to a cell to which a mobility is to be performed from the source cell. The target cell may comprise target PCell, target SCell and/or target PSCell.
“Potential target cell” refers to a cell to which a mobility is to be performed from a target cell, after performing a mobility from a source cell to the target cell. The potential target cell may comprise potential target PCell, potential target PSCell and/or potential target SCell.
“Mobility command related to a target cell” refers to a mobility command configured/generated/provided by a source cell and used for a mobility from the source cell to the target cell.
“Mobility command related to a potential target cell” refers to a mobility command configured/generated/provided by a target cell and used for a mobility from the target cell to the potential target cell.
Referring to
In step S1203, the wireless device may trigger an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled.
In step S1205, the wireless device may perform a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility.
In step S1207, the wireless device may perform a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command (i.e., based on that the selected cell is the potential target cell).
According to various embodiments, the wireless device may revert back to a source cell configuration after detecting a failure of the mobility to the target cell.
According to various embodiments, the wireless device may identify a conditional mobility command which is related to the selected cell and is not part of the source cell configuration. The conditional mobility command may be used for a mobility from a cell which is not included in a current MCG. After identifying the second conditional mobility command related to the selected cell, the wireless device may perform the mobility to the selected cell based on the second conditional mobility command.
According to various embodiments, the wireless device may add the second conditional mobility command to the source cell configuration. The wireless device may identify whether a conditional mobility command related to the selected cell is in the source cell configuration. After identifying the second conditional mobility command related to the selected cell in the source cell configuration, the wireless device may perform the mobility to the selected cell based on the second conditional mobility command.
According to various embodiments, the target cell may comprise a target primary cell (PCell), and the potential target cell may comprise a potential target PCell.
According to various embodiments, the target cell may comprise a target primary cell (PCell), and the potential target cell may comprise a potential target primary secondary cell (PSCell).
According to various embodiments, the first conditional mobility command may comprise a conditional handover command provided by a source primary cell (PCell) and used for a handover from the source PCell to the target cell.
According to various embodiments, the second conditional mobility command may comprise a conditional handover command provided by the target cell and used for a handover from the target cell to the potential target cell.
According to various embodiments, the second conditional mobility command may comprise a conditional primary secondary cell addition/change (CPAC) command generated by the target cell and used for a CPAC for the potential target cell.
According to various embodiments, the wireless device may start a timer T304 upon triggering the execution of the mobility to the target cell. The wireless device may perform a random access attempt towards the target cell while the timer T304 is running. The wireless device may detect that the random access attempt fails and the timer T304 expires, to detect the failure of the mobility to the target cell. The wireless device may perform the mobility to the selected cell by using the second conditional mobility command related to the selected cell based on that a conditional mobility attempt configuration (i.e., attemptCHO or attetmpCondReconfig) is configured from a network.
According to various embodiments, after completing the mobility to the selected cell which is a potential primary secondary cell (PSCell), the wireless device may transmit a master cell group (MCG) failure information message to the potential target PSCell.
According to various embodiments, the MCG failure information message may be transmitted via a radio resource control (RRC) reconfiguration complete message.
According to various embodiments, the wireless device may receive a first mobility command from a source cell for a mobility from the source cell to a target cell. The wireless device may detect a failure of applying the first mobility command and/or a radio link failure (RLF) on the source cell. The wireless device may check whether a second mobility command generated by a cell other than the source cell exists. The wireless device may perform a cell selection for a connection re-establishment. The wireless device may perform a mobility to a selected cell by the cell selection based on the second mobility command if/when the selected cell is associated with the second mobility command.
According to various embodiments, the wireless device may receive a first mobility command from a source cell for a mobility from the source cell to a target cell. The wireless device may apply a UE configuration based on the first mobility command. The wireless device may detect a failure to apply the first mobility command and/or a radio link failure on the source cell. The wireless device may revert to the UE configuration used in the source cell. The wireless device may check whether a second mobility command configured/generated/provided by a cell other than the source cell exists. The wireless device may add the second mobility command to the UE configuration used in the source cell. The wireless device may perform a selection for a connection re-establishment. The wireless device may perform a mobility to a selected cell by the cell selection based on the second mobility command if/when the selected cell is related to the second mobility command.
Referring to
In step S1303, the wireless device may trigger an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled.
In step S1305, the wireless device may perform a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility.
In step S1307, the wireless device may perform a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command (i.e., based on that the selected cell is the potential target cell).
The source RAN node in
In the present disclosure, in an aspect, the UE may detect a handover failure and/or reconfiguration with sync failure (i.e., T304 expiry), on source PCell and the UE may initiate the connection re-establishment procedure. In the connection re-establishment procedure, the UE may perform cell selection and, after cell selection, the UE may check whether the newly selected cell is one of the candidate cells which is associated with any conditional mobility configuration (e.g., any stored CHO and/or CPC configuration/command currently). Any conditional mobility configuration may have been provided/configured by not only the source PCell, but also any other serving cells and/or potential target PCell. It means that a handover command or PSCell change command (i.e., reconfiguration with sync) for conditional mobility is included not only in the source PCell configuration but also in the source PSCell configuration and/or target PCell configuration and/or potential target PCell configuration, (i.e., other candidate cells except the target PCell).
If the newly selected cell is one of the candidate cells which is associated with the any conditional mobility configuration which has been provided for the UE regardless of the source PCell and has been stored by the UE, the UE may perform mobility towards the newly selected cell using the conditional mobility configuration corresponding to the newly selected cell (i.e., apply the stored conditional mobility configuration, namely, RRC Reconfiguration message including reconfiguration with sync).
In another aspect, the UE may detect radio link failure of the source PCell (i.e., MCG failure), by any reason (e.g., T310 expiry, random access problem indication from MCG MAC, an indication of the maximum number of retransmissions from MCG RLC or fast MCG recovery failure such as T316 expiry) and the UE may initiate the connection re-establishment procedure. In the connection re-establishment procedure, the UE may perform a cell selection and, after the cell selection, the UE may check if the newly selected cell is one of the candidate cells which is associated with the any conditional mobility configuration which has been provided for the UE regardless of the source PCell and has been stored by the UE. If the newly selected cell is one of the candidate cells which is associated with the any conditional mobility configuration which has been provided for the UE regardless of the source PCell and has been stored by the UE, the UE may perform a mobility towards the newly selected cell using corresponding conditional mobility configuration corresponding to the newly selected cell.
Upon successful completion of the mobility towards the newly selected cell (i.e., after MAC of an NR cell group successfully completes a Random Access procedure triggered by this mobility), the UE may check whether the corresponding conditional mobility configuration was included in RRC Reconfiguration of MCG and/or SCG. If the corresponding conditional mobility configuration was included in RRC Reconfiguration of SCG (i.e., the newly selected cell is for PSCell), the UE may regard the newly selected cell as new PSCell of SCG and initiate the MCG failure information procedure to report MCG failure. Otherwise, (i.e., the newly selected cell is for PCell), the UE may regard the newly selected cell as new PCell of MCG.
Referring to
In step S1403, upon reception of the handover request message from the source PCell, the target PCell may perform admission control for the UE. The target PCell may also decide to provide conditional handover command, (i.e., CHO configuration which would be used for the target PCell after handover complete). The target PCell may initiate a conditional handover preparation by sending a conditional handover request message to the cell A. The cell A may be or comprise a potential target PCell. The target PCell may receive a conditional handover request acknowledge message in response to the conditional handover request message. In the conditional handover request acknowledge message, there is a first container that includes CHO configuration for cell A (i.e., CHO command related to the cell A). The first container may be generated by the cell A.
In step S1405, upon a reception of the conditional handover request acknowledge message from the cell A, the target PCell may transmit to the source PCell a handover request acknowledge message in response to the handover request message. In the handover request acknowledge message, there is a second container that includes a handover command (i.e., RRC Reconfiguration message including reconfiguration with sync, for handover from the source PCell to the target PCell). The second container may be generated by the target PCell. Also, in the handover command, there is a third container that includes CHO configuration for cell A. The third container may be the same as the first container which is included in the conditional handover request acknowledge message.
In step S1407, the UE may receive an RRC reconfiguration message including reconfiguration with sync (i.e., the handover command for handover from the source PCell to the target PCell). The UE may also receive the CHO configuration for cell A. The UE may store the CHO configuration for cell A, (i.e., add a new entry for the CHO configuration for cell A within a UE variable). The UE variable may include the accumulated configuration of the CHO and/or conditional PSCell change (i.e., CPC configurations including the pointers to CHO and/or CPC execution condition which comprise associated measId(s) and/or the stored target candidate cell's RRC Reconfiguration message(s)).
In step S1409, the UE may apply the RRC Reconfiguration and start the T304 timer for mobility.
In step S1411, the UE may perform synchronisation to the target PCell and access to the target PCell via RACH configuration which is configured by the RRC Reconfiguration message.
In step S1413, the T304 may expire and the may not succeed to access the target PCell. The UE may store the CHO configuration for cell A (i.e., add a new entry for this CHO configuration within the UE variable if there is new information to be stored).
In step S1415, the UE may initiate the RRC re-establishment procedure and perform cell selection. The UE may not initiate the RRC re-establishment procedure if the UE is able to perform a conditional mobility execution to the selected cell by using the stored conditional mobility command related to the selected cell without initiating the RRC Re-establishment procedure. For the cell selection, cell selection criteria may be configured by dedicated RRC signalling and/or system information.
In step S1417, after the cell selection, the UE may check if the selected cell is one of the candidate cells for which the CHO configuration is included in the UE variable regardless of current MCG. Before the cell selection, the UE may have stored the CHO configuration for cell A (i.e., added a new entry for this CHO configuration within the UE variable if there is new information to be stored)
In step S1419, since the cell A is one of candidate cells in the UE variable, the UE man not initiate a transmission of the RRC reestablishment request message to the cell A, but apply the CHO configuration for the cell A and access the cell A via RACH configuration which is configured by the CHO configuration.
Referring to
In step S1503, upon reception of the handover request message from the source PCell, the target PCell may perform admission control. The target PCell may also decide to provide conditional PSCell addition/change command, (i.e., CPC configuration which would be used for the target PCell after handover complete). The target PCell may initiate conditional PSCell change preparation by sending a conditional PSCell addition/change request message to the cell A. The cell A may be or comprise a potential target PSCell. The target PCell may receive a conditional PSCell addition/change request acknowledge message in response to the conditional PSCell addition/change request message, if possible. In the conditional PSCell addition/change request acknowledge message, there is a first container that includes CPC configuration for cell A (i.e., CPC command related to the cell A). The first container may be generated by the cell A.
In step S1505, upon reception of the conditional PScell addition/change request acknowledge message from the cell A, the target PCell may transmit to the source PCell a handover request acknowledge message in response to the handover request message. In the handover request acknowledge message, there is a second container that includes a handover command (i.e., RRC Reconfiguration message including reconfiguration with sync), for handover from the source PCell to the target PCell. The second container may be generated by the target PCell. Also, in the handover command, there is a third container that includes CPC configuration for cell A. The third container may be the same as the first container which is included in the conditional handover request acknowledge message.
In step S1507, the UE may receive an RRC reconfiguration message including reconfiguration with sync (i.e., the handover command for handover from the source PCell to the target PCell). The UE may also receive the CPC configuration for cell A. The UE may store the CPC configuration for cell A, (i.e., add a new entry for this CPC configuration within a UE variable). The UE variable may include the accumulated configuration of the CHO and/or conditional PSCell change (i.e., CPC configurations including the pointers to CHO and/or CPC execution condition i.e. associated measId(s) and the stored target candidate cell's RRC Reconfiguration message(s)).
In step S1509, the UE may apply the RRC reconfiguration and start the T304 timer for mobility.
In step S1511, the UE may perform synchronisation to the target PCell and access to the target PCell via RACH configuration which is configured by the RRC Reconfiguration message.
In step S1513, the T304 may expire and the UE may not succeed to access to the target PCell. The UE may store the CPC configuration for cell A (i.e., add a new entry for this CPC configuration within the UE variable if there is new information to be stored).
In step S1515, the UE may initiate the RRC Re-establishment procedure and perform a cell selection. The UE may not initiate the RRC Re-establishment procedure if the UE is able to perform a conditional mobility execution to the selected cell by using the stored conditional mobility command related to the selected cell without initiating the RRC Re-establishment procedure. For the cell selection, cell selection criteria may be configured by dedicated RRC signalling and/or system information.
In step S1517, after the cell selection, the UE may check if the selected cell is one of the candidate cells for which the CHO and/or CPC configuration is included in the UE variable regardless of current MCG. Before the cell selection, the UE may have stored the CPC configuration for cell A (i.e., add a new entry for this CPC configuration within the UE variable if there is new information to be stored).
In step S1519, since the cell A is one of candidate cells in the UE variable, the UE may not initiate a transmission of the RRC Reestablishment request message to the cell A, but apply the CPC configuration for the cell A and access to the cell A via RACH configuration which is configured by the CPC configuration.
In step S1521, the cell A may respond with UL allocation and timing advance. The cell A may provide uplink grant via PDCCH of the cell A if RACH-less HO is configured in the CPC configuration.
In step S1523, the UE may send RRC reconfiguration complete message to confirm the mobility (i.e., CPC). The UE may include MCG failure information in the RRC Reconfiguration Complete message for signalling optimisation. The mobility procedure may be completed for the UE when the UE receives the UE contention resolution identity MAC control element from the cell A.
In step S1525, the UE may send an MCG failure information message if needed (e.g., if the RRC Reconfiguration Complete message of step S1523 doesn't include the MCG failure information message).
In the present disclosure, the UE may detect a handover failure and/or reconfiguration with sync failure *i.e., T304 expiry), on source PCell and the UE may be ready to initiate the connection re-establishment procedure. Before initiating the connection re-establishment procedure, the UE may revert back to the UE configuration used in the source PCell. When reverting back to the UE configuration used in the source PCell, the UE may check whether there is a new entry for conditional mobility configuration (i.e., CHO/CPC configuration which has provided by other cells (i.e., serving cells except for the source PCell, target PCell, target PSCell, potential target PCells and/or potential target PSCell.
The serving cell may comprise a set of cells comprising a special cell(s) (SpCell(s)) and all secondary cells (SCells) for the UE configured with CA or DC.
The target PCell may comprise a cell to be accessed by the conventional handover and/or CHO. In the case of the CHO, a CHO execution condition for the target PCell should be met.
The potential target PCell may comprise a set of cells in the candidate cell list of CHO configuration of the current MCG except for the target PCell that haven't met a CHO execution condition.
If there is a conditional mobility configuration that has been provided by other cells, the UE may add new entries for the conditional mobility configuration for the current MCG as the UE configuration used in the source PCell (i.e., delta operation for the conditional mobility configuration which is not yet applied may be performed for the UE configuration used in the source PCell). An example is described in
After the delta operation for the conditional mobility configuration which is not yet applied is performed for the UE configuration used in the source PCell, the UE may initiate the connection re-establishment procedure. In the connection re-establishment procedure, the UE may perform a cell selection and, after the cell selection, the UE may check whether a newly selected cell is one of the candidate cells which is associated with the conditional mobility configuration in the UE configuration used in the source PCell. If the newly selected cell is one of the candidate cells which is associated with the conditional mobility configuration, the UE may perform a mobility towards the newly selected cell using the conditional mobility configuration corresponding to the selected cell (i.e., apply the stored conditional mobility configuration, namely, RRC Reconfiguration message including reconfiguration with sync).
The UE may have the same behaviour in case of the radio link failure of the MCG.
The UE may detect radio link failure of the source PCell (i.e., MCG failure), by any reason (e.g., T310 expiry, random access problem indication from MCG MAC, an indication of the maximum number of retransmissions from MCG RLC or fast MCG recovery failure such as T316 expiry) and the UE may be ready to initiate the connection re-establishment procedure. Before initiating the connection re-establishment procedure, the UE may revert back to the UE configuration used in the source PCell. When reverting back to the UE configuration used in the source PCell, the UE may check whether there is a new entry for conditional mobility configuration (i.e., CHO/CPC configuration which has provided by other cells, for example, serving cells except for the source PCell and/or target PCell and/or potential target PCells).
The serving cell may comprise a set of cells comprising a special cell(s) (SpCell(s)) and all secondary cells (SCells) for the UE configured with CA or DC.
The target PCell may comprise a cell to be accessed by the conventional handover and/or CHO. In the case of the CHO, a CHO execution condition for the target PCell should be met.
The potential target PCell may comprise a set of cells in the candidate cell list of CHO configuration of the current MCG except for the target PCell that haven't met a CHO execution condition.
If there is a conditional mobility configuration that has provided by other cells, the UE may add new entries for conditional mobility configuration for the current MCG as the UE configuration used in the source PCell (i.e., delta operation for the conditional mobility configuration which is not yet applied may be performed for the UE configuration used in the source PCell).
After the delta operation for the conditional mobility configuration which is not yet applied is performed for the UE configuration used in the source PCell, the UE may initiate the connection re-establishment procedure. In the connection re-establishment procedure, the UE may perform a cell selection and, after the cell selection, the UE may check whether a newly selected cell is one of the candidate cells which is associated with the conditional mobility configuration in the UE configuration used in the source PCell. If the newly selected cell is one of the candidate cells which is associated with the conditional mobility configuration, the UE may perform a mobility towards the newly selected cell using the conditional mobility configuration corresponding to the selected cell (i.e., apply the stored conditional mobility configuration, namely, RRC Reconfiguration message including reconfiguration with sync).
According to various embodiments, the UE shall:
1>if T304 of the MCG expires:
2>release dedicated preambles provided in rach-ConfigDedicated if configured;
2>if dapsConfig is configured for any DRB, and radio link failure is not detected in the source PCell:
3>release target PCell configuration;
3>reset target MAC and release the target MAC configuration;
3>for each DRB with a DAPS PDCP entity:
4>release the RLC entity and the associated logical channel for the target;
4>reconfigure the PDCP entity to normal PDCP;
3>for each SRB:
4>if the masterKeyUpdate was not received:
5>configure the PDCP entity for the source with the same state variables as the PDCP entity for the target;
4>release the PDCP entity for the target;
4>release the RLC entity and the associated logical channel for the target;
3>release the physical channel configuration for the target;
3>revert back to the SDAP configuration used in the source;
3>discard the keys used in target (the KgNB key, the S-KgNB key, the S-KeNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any;
3>resume suspended SRBs in the source;
3>for each DRB without a DAPS PDCP entity:
4>revert back to the UE configuration used for the DRB in the source, includes PDCP, RLC states variables, the security configuration and the data stored in transmission and reception buffers in PDCP and RLC entities;
3>revert back to the UE RRM configuration used in the source;
3>initiate the failure information procedure to report DAPS handover failure.
2>else:
3>revert back to the UE configuration used in the source PCell:
4>if any received ConditionalReconfiguration IE exists in the RRCReconfiguration which is not part of the UE configuration used in the source PCell (i.e., received from any cell but not stored yet):
5>for each condConfigId received in the condConfigToAddModList IE of the ConditionalReconfiguration IE, the UE shall:
6>add a new entry for this condConfigId within the VarConditionalConfig of the UE configuration used in the source PCell;
3>initiate the connection re-establishment procedure.
In the context above, “the UE configuration” may include state variables and parameters of each radio bearer.
1>else if T304 of a secondary cell group expires:
2>release dedicated preambles provided in rach-ConfigDedicated, if configured;
2>initiate the SCG failure information procedure to report SCG reconfiguration with sync failure, upon which the RRC reconfiguration procedure ends;
1>else if T304 expires when RRCReconfiguration is received via other RAT (HO to NR failure):
2>reset MAC;
2>perform the actions defined for this failure case as defined in the specifications applicable for the other RAT.
A UE includes a processor 1710 (i.e., processor 211), a power management module 1711, a battery 1712, a display 1713, a keypad 1714, a subscriber identification module (SIM) card 1715, a memory 1720 (i.e., memory 212), a transceiver 1730 (i.e., transceiver 213), one or more antennas 1731, a speaker 1740, and a microphone 1741.
The processor 1710 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of the radio interface protocol may be implemented in the processor 1710. The processor 1710 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device. The processor 1710 may be an application processor (AP). The processor 1710 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor 1710 may be found in SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung®, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or a corresponding next generation processor.
The processor 1710 may be configured to, or configured to control the transceiver 1730 to implement steps performed by the UE and/or the wireless device throughout the disclosure.
The power management module 1711 manages power for the processor 1710 and/or the transceiver 1730. The battery 1712 supplies power to the power management module 1711. The display 1713 outputs results processed by the processor 1710. The keypad 1714 receives inputs to be used by the processor 1710. The keypad 1714 may be shown on the display 1713. The SIM card 1715 is an integrated circuit that is intended to securely store the international mobile subscriber identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices (such as mobile phones and computers). It is also possible to store contact information on many SIM cards.
The memory 1720 is operatively coupled with the processor 1710 and stores a variety of information to operate the processor 1710. The memory 1720 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and/or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 1720 and executed by the processor 1710. The memory 1720 can be implemented within the processor 1710 or external to the processor 1710 in which case those can be communicatively coupled to the processor 1710 via various means as is known in the art.
The transceiver 1730 is operatively coupled with the processor 1710, and transmits and/or receives a radio signal. The transceiver 1730 includes a transmitter and a receiver. The transceiver 1730 may include baseband circuitry to process radio frequency signals. The transceiver 1730 controls the one or more antennas 1731 to transmit and/or receive a radio signal.
The speaker 1740 outputs sound-related results processed by the processor 1710. The microphone 1741 receives sound-related inputs to be used by the processor 1710.
According to various embodiments, the processor 1710 may be configured to, or configured to control the transceiver 1730 to implement steps performed by the UE and/or the wireless device throughout the disclosure. For example, the processor 1710 may be configured to control the transceiver 1730 to receive a first conditional mobility command related to a target cell and a second conditional mobility command related to a potential target cell. The processor 1710 may be configured to trigger an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled. The processor 1710 may be configured to perform a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility. The processor 1710 may be configured to perform a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command (i.e., based on that the selected cell is the potential target cell).
According to various embodiments, the processor 1710 may be configured to revert back to a source cell configuration after detecting a failure of the mobility to the target cell.
According to various embodiments, the processor 1710 may be configured to identify a conditional mobility command which is related to the selected cell and is not part of the source cell configuration. The conditional mobility command may be used for a mobility from a cell which is not included in a current MCG. After identifying the second conditional mobility command related to the selected cell, the processor 1710 may be configured to perform the mobility to the selected cell based on the second conditional mobility command.
According to various embodiments, the processor 1710 may be configured to add the second conditional mobility command to the source cell configuration. The processor 1710 may be configured to identify whether a conditional mobility command related to the selected cell is in the source cell configuration. After identifying the second conditional mobility command related to the selected cell in the source cell configuration, the processor 1710 may be configured to perform the mobility to the selected cell based on the second conditional mobility command.
According to various embodiments, the target cell may comprise a target primary cell (PCell), and the potential target cell may comprise a potential target PCell.
According to various embodiments, the target cell may comprise a target primary cell (PCell), and the potential target cell may comprise a potential target primary secondary cell (PSCell).
According to various embodiments, the first conditional mobility command may comprise a conditional handover command provided by a source primary cell (PCell) and used for a handover from the source PCell to the target cell.
According to various embodiments, the second conditional mobility command may comprise a conditional handover command provided by the target cell and used for a handover from the target cell to the potential target cell.
According to various embodiments, the second conditional mobility command may comprise a conditional primary secondary cell addition/change (CPAC) command generated by the target cell and used for a CPAC for the potential target cell.
According to various embodiments, the processor 1710 may be configured to start a timer T304 upon triggering the execution of the mobility to the target cell. The processor 1710 may be configured to perform a random access attempt towards the target cell while the timer T304 is running. The processor 1710 may be configured to detect that the random access attempt fails and the timer T304 expires, to detect the failure of the mobility to the target cell. The processor 1710 may be configured to perform the mobility to the selected cell by using the second conditional mobility command related to the selected cell based on that a conditional mobility attempt configuration (i.e., attemptCHO or attetmpCondReconfig) is configured from a network.
According to various embodiments, after completing the mobility to the selected cell which is a potential primary secondary cell (PSCell), the processor 1710 may be configured to control the transceiver 1730 to transmit a master cell group (MCG) failure information message to the potential target PSCell.
According to various embodiments, the MCG failure information message may be transmitted via a radio resource control (RRC) reconfiguration complete message.
Referring to
The first device 1810 may include at least one transceiver, such as a transceiver 1811, and at least one processing chip, such as a processing chip 1812. The processing chip 1812 may include at least one processor, such a processor 1813, and at least one memory, such as a memory 1814. The memory may be operably connectable to the processor 1813. The memory 1814 may store various types of information and/or instructions. The memory 1814 may store a software code 1815 which implements instructions that, when executed by the processor 1813, perform operations of the first device 910 described throughout the disclosure. For example, the software code 1815 may implement instructions that, when executed by the processor 1813, perform the functions, procedures, and/or methods of the first device 1810 described throughout the disclosure. For example, the software code 1815 may control the processor 1813 to perform one or more protocols. For example, the software code 1815 may control the processor 1813 to perform one or more layers of the radio interface protocol.
The second device 1820 may include at least one transceiver, such as a transceiver 1821, and at least one processing chip, such as a processing chip 1822. The processing chip 1822 may include at least one processor, such a processor 1823, and at least one memory, such as a memory 1824. The memory may be operably connectable to the processor 1823. The memory 1824 may store various types of information and/or instructions. The memory 1824 may store a software code 1825 which implements instructions that, when executed by the processor 1823, perform operations of the second device 1820 described throughout the disclosure. For example, the software code 1825 may implement instructions that, when executed by the processor 1823, perform the functions, procedures, and/or methods of the second device 1820 described throughout the disclosure. For example, the software code 1825 may control the processor 1823 to perform one or more protocols. For example, the software code 1825 may control the processor 1823 to perform one or more layers of the radio interface protocol.
According to various embodiments, the first device 1810 as illustrated in
According to various embodiments, a computer-readable medium having recorded thereon a program for performing each step of a method on a computer is provided. The method comprises: receiving a first conditional mobility command related to a target cell and a second conditional mobility command related to a potential target cell; triggering an execution of a mobility to the target cell based on that a mobility condition in the first conditional mobility command is fulfilled; performing a cell selection to select a cell for a connection re-establishment after detecting a failure of the mobility; and performing a mobility to the selected cell based on that the selected cell is related to the second conditional mobility command.
The present disclosure may be applied to various future technologies, such as AI, robots, autonomous-driving/self-driving vehicles, and/or extended reality (XR).
<AI>
AI refers to artificial intelligence and/or the field of studying methodology for making it. Machine learning is a field of studying methodologies that define and solve various problems dealt with in AI. Machine learning may be defined as an algorithm that enhances the performance of a task through a steady experience with any task.
An artificial neural network (ANN) is a model used in machine learning. It can mean a whole model of problem-solving ability, consisting of artificial neurons (nodes) that form a network of synapses. An ANN can be defined by a connection pattern between neurons in different layers, a learning process for updating model parameters, and/or an activation function for generating an output value. An ANN may include an input layer, an output layer, and optionally one or more hidden layers. Each layer may contain one or more neurons, and an ANN may include a synapse that links neurons to neurons. In an ANN, each neuron can output a summation of the activation function for input signals, weights, and deflections input through the synapse. Model parameters are parameters determined through learning, including deflection of neurons and/or weights of synaptic connections. The hyper-parameter means a parameter to be set in the machine learning algorithm before learning, and includes a learning rate, a repetition number, a mini batch size, an initialization function, etc. The objective of the ANN learning can be seen as determining the model parameters that minimize the loss function. The loss function can be used as an index to determine optimal model parameters in learning process of ANN.
Machine learning can be divided into supervised learning, unsupervised learning, and reinforcement learning, depending on the learning method. Supervised learning is a method of learning ANN with labels given to learning data. Labels are the answers (or result values) that ANN must infer when learning data is input to ANN. Unsupervised learning can mean a method of learning ANN without labels given to learning data. Reinforcement learning can mean a learning method in which an agent defined in an environment learns to select a behavior and/or sequence of actions that maximizes cumulative compensation in each state.
Machine learning, which is implemented as a deep neural network (DNN) that includes multiple hidden layers among ANN, is also called deep learning. Deep learning is part of machine learning. In the following, machine learning is used to mean deep learning.
The AI device 1900 may be implemented as a stationary device or a mobile device, such as a TV, a projector, a mobile phone, a smartphone, a desktop computer, a notebook, a digital broadcasting terminal, a PDA, a PMP, a navigation device, a tablet PC, a wearable device, a set-top box (STB), a digital multimedia broadcasting (DMB) receiver, a radio, a washing machine, a refrigerator, a digital signage, a robot, a vehicle, etc.
Referring to
The communication part 1910 can transmit and/or receive data to and/or from external devices such as the AI devices and the AI server using wire and/or wireless communication technology. For example, the communication part 1910 can transmit and/or receive sensor information, a user input, a learning model, and a control signal with external devices. The communication technology used by the communication part 1910 may include a global system for mobile communication (GSM), a code division multiple access (CDMA), an LTE/LTE-A, a 5G, a WLAN, a Wi-Fi, Bluetooth™, radio frequency identification (RFID), infrared data association (IrDA), ZigBee, and/or near field communication (NFC).
The input part 1920 can acquire various kinds of data. The input part 1920 may include a camera for inputting a video signal, a microphone for receiving an audio signal, and a user input part for receiving information from a user. A camera and/or a microphone may be treated as a sensor, and a signal obtained from a camera and/or a microphone may be referred to as sensing data and/or sensor information. The input part 1920 can acquire input data to be used when acquiring an output using learning data and a learning model for model learning. The input part 1920 may obtain raw input data, in which case the processor 1970 or the learning processor 1930 may extract input features by preprocessing the input data.
The learning processor 1930 may learn a model composed of an ANN using learning data. The learned ANN can be referred to as a learning model. The learning model can be used to infer result values for new input data rather than learning data, and the inferred values can be used as a basis for determining which actions to perform. The learning processor 1930 may perform AI processing together with the learning processor of the AI server. The learning processor 1930 may include a memory integrated and/or implemented in the AI device 1900. Alternatively, the learning processor 1930 may be implemented using the memory 1960, an external memory directly coupled to the AI device 1900, and/or a memory maintained in an external device.
The sensing part 1940 may acquire at least one of internal information of the AI device 1900, environment information of the AI device 1900, and/or the user information using various sensors. The sensors included in the sensing part 1940 may include a proximity sensor, an illuminance sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, a light detection and ranging (LIDAR), and/or a radar.
The output part 1950 may generate an output related to visual, auditory, tactile, etc. The output part 1950 may include a display unit for outputting visual information, a speaker for outputting auditory information, and/or a haptic module for outputting tactile information.
The memory 1960 may store data that supports various functions of the AI device 1900. For example, the memory 1960 may store input data acquired by the input part 1920, learning data, a learning model, a learning history, etc.
The processor 1970 may determine at least one executable operation of the AI device 1900 based on information determined and/or generated using a data analysis algorithm and/or a machine learning algorithm. The processor 1970 may then control the components of the AI device 1900 to perform the determined operation. The processor 1970 may request, retrieve, receive, and/or utilize data in the learning processor 1930 and/or the memory 1960, and may control the components of the AI device 1900 to execute the predicted operation and/or the operation determined to be desirable among the at least one executable operation. The processor 1970 may generate a control signal for controlling the external device, and may transmit the generated control signal to the external device, when the external device needs to be linked to perform the determined operation. The processor 1970 may obtain the intention information for the user input and determine the user's requirements based on the obtained intention information. The processor 1970 may use at least one of a speech-to-text (STT) engine for converting speech input into a text string and/or a natural language processing (NLP) engine for acquiring intention information of a natural language, to obtain the intention information corresponding to the user input. At least one of the STT engine and/or the NLP engine may be configured as an ANN, at least a part of which is learned according to a machine learning algorithm. At least one of the STT engine and/or the NLP engine may be learned by the learning processor 1930 and/or learned by the learning processor of the AI server, and/or learned by their distributed processing. The processor 1970 may collect history information including the operation contents of the AI device 1900 and/or the user's feedback on the operation, etc. The processor 1970 may store the collected history information in the memory 1960 and/or the learning processor 1930, and/or transmit to an external device such as the AI server. The collected history information can be used to update the learning model. The processor 1970 may control at least some of the components of AI device 1900 to drive an application program stored in memory 1960. Furthermore, the processor 1970 may operate two or more of the components included in the AI device 1900 in combination with each other for driving the application program.
Referring to
The cloud network 2000 may refer to a network that forms part of a cloud computing infrastructure and/or resides in a cloud computing infrastructure. The cloud network 2000 may be configured using a 3G network, a 4G or LTE network, and/or a 5G network. That is, each of the devices 2010a to 2010e and 2020 consisting the AI system may be connected to each other through the cloud network 2000. In particular, each of the devices 2010a to 2010e and 2020 may communicate with each other through a base station, but may directly communicate with each other without using a base station.
The AI server 2020 may include a server for performing AI processing and a server for performing operations on big data. The AI server 2020 is connected to at least one or more of AI devices constituting the AI system, i.e. the robot 2010a, the autonomous vehicle 2010b, the XR device 2010c, the smartphone 2010d and/or the home appliance 2010e through the cloud network 2000, and may assist at least some AI processing of the connected AI devices 2010a to 2010e. The AI server 2020 can learn the ANN according to the machine learning algorithm on behalf of the AI devices 2010a to 2010e, and can directly store the learning models and/or transmit them to the AI devices 2010a to 2010e. The AI server 2020 may receive the input data from the AI devices 2010a to 2010e, infer the result value with respect to the received input data using the learning model, generate a response and/or a control command based on the inferred result value, and transmit the generated data to the AI devices 2010a to 2010e. Alternatively, the AI devices 2010a to 2010e may directly infer a result value for the input data using a learning model, and generate a response and/or a control command based on the inferred result value.
Various embodiments of the AI devices 2010a to 2010e to which the technical features of the present disclosure can be applied will be described. The AI devices 2010a to 2010e shown in
The present disclosure can have various advantageous effects.
For example, the disclosure may enhance a mobility robustness by performing a CHO based failure handling using candidate cell lists which are provided from not only the source PCell but also other serving cells, target cells and/or potential target cells. It means that the UE has further changes to initiate another mobility instead of the connection re-establishment from declaring mobility failure (i.e., reconfiguration with sync failure) when there is no CHO configuration provided by the source PCell.
Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and/or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.
In view of the exemplary systems described herein, methodologies that may be implemented in accordance with the disclosed subject matter have been described with reference to several flow diagrams. While for purposed of simplicity, the methodologies are shown and described as a series of steps or blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the steps or blocks, as some steps may occur in different orders or concurrently with other steps from what is depicted and described herein. Moreover, one skilled in the art would understand that the steps illustrated in the flow diagram are not exclusive and other steps may be included or one or more of the steps in the example flow diagram may be deleted without affecting the scope of the present disclosure.
Claims in the present description can be combined in a various way. For instance, technical features in method claims of the present description can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2020-0036193 | Mar 2020 | KR | national |
| 10-2020-0036195 | Mar 2020 | KR | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2021/002956 | 3/10/2021 | WO |
