JP2017127018A - Method and apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method or the like.SOLUTION: A method comprises a step of performing a media access control reset. The media access control reset is provided without performing at least one of a radio link control reset and a packet data convergence protocol reset.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a method and apparatus, and more specifically, but not exclusively, to a method and apparatus, particularly but not exclusively, used in any reconfiguration and / or handover.

  A communication system allows communication between two or more communication devices, such as user terminals, base stations, and / or other nodes, by providing a carrier wave between the communication devices. In a wireless communication system, at least a portion of communication between at least two stations occurs via a wireless interface. The user can access the communication system using an appropriate communication device or terminal. The communication device is equipped with suitable signal reception and transmission devices to enable communication, for example to enable access to a communication network or direct communication with other users. The communication device accesses a carrier provided by a station, eg, a cell base station, and transmits and / or receives communications on the carrier.

  Carrier aggregation may be used to enhance performance. In carrier aggregation, a plurality of carriers are aggregated to increase the bandwidth. Carrier aggregation comprises aggregating a plurality of component carriers into a carrier, referred to herein as an aggregated carrier.

  According to a first aspect, a method is provided comprising performing a media access control reset without performing at least one of a radio link control reset and a packet data convergence protocol reset.

  According to a second aspect, there is provided a computer program comprising computer-executable instructions configured to perform the method of the first aspect when run.

  According to a third aspect, in an apparatus comprising at least one processor and at least one memory containing computer program code, the at least one memory and computer program code together with the at least one processor An apparatus is provided that is configured to cause a device to perform a media access control reset without performing at least one of a radio link control reset and a packet data convergence protocol reset.

  According to a fourth aspect, there is provided a user equipment comprising the device according to the third aspect.

  The embodiments will now be described in further detail, by way of example only, with reference to the following examples and the accompanying drawings.

1 illustrates an example system that can implement the embodiments described below. An example of a communication device is shown. An example of a control device is shown. The aggregated carrier wave is schematically shown. 2 illustrates a method of an embodiment.

  In the following, certain exemplary embodiments are described in the context of a wireless communication system serving device adapted for wireless communication. Therefore, before discussing the exemplary embodiments in detail, certain of the wireless system and its components and devices for wireless communication are intended to assist in understanding the technology underlying the described example. Is briefly described in connection with the system 10 of FIG. 1, the device 20 of FIG. 2, and the controller 30 of FIG.

  The communication device can be used to access various services and / or applications provided via the communication system. In a wireless or mobile communication system, access is provided via a wireless access interface between the mobile communication device and a suitable access system. A communication device can access the communication system wirelessly via a base station. A base station site is one that provides one or more cells of a cellular system. The base station can provide, for example, three carriers, and each carrier provides a cell. In FIG. 1, for example, the base station 12 is shown as providing three cells 1, 2, and 3. These cells provide carriers F1, F2, F3, respectively. Each communication device 20 and base station may have one or more radio channels open at the same time and may receive signals from more than one source.

  It should be appreciated that the number of carriers provided by each base station may be more or less than three and may change over time.

  In some embodiments, it may be appreciated that there is an in-frequency serving cell change.

  In some embodiments, it may be appreciated that there is a serving cell reconfiguration of certain parameters that are not mobile.

  It should be pointed out that at least one of the cells 1 to 3 may be provided by the remote radio head of the base station 12. In some embodiments, at least one of the carriers may be provided by a station that is not co-located with the base station 12, but can only be controlled by the same controller as the other cells. It ’s like that. This possibility is represented by station 11 in FIG. For example, block 13 may be used to control at least one other station, such as an intra-eNB. Interactions between different stations and / or their controllers may also be negotiated differently if, for example, the station is provided as an intersite eNB. The cell controller has sufficient information for all of the aggregated carriers (cells).

  A base station is typically controlled by at least one suitable controller to allow management of its mobile communications device communicating with its base station. A control entity may be interconnected with other control entities. The control entity may be part of the base station. In FIG. 1, the controller is shown as being provided by block 13. The controller device may comprise at least one memory, at least one data processing unit, and an input / output interface. It should be understood that the control function may be distributed among a plurality of control units. The base station controller device may be configured to execute appropriate software code to provide the control functions described in more detail below.

  In FIG. 1, base station 12 is connected to data network 18 via a suitable gateway 15. Gateway functionality between the access system and another network, such as a packet data network, may be provided by any suitable gateway node, eg, a packet data gateway and / or access gateway. A communication system is thus provided by one or more interconnected networks and elements thereof, and one or more gateway nodes are provided for interconnecting various networks.

  An example of a standardized architecture is known as Long Term Evolution (LTE) of Universal Mobile Telecommunications System (UMTS) radio access technology. LTE is being standardized by the 3rd Generation Partnership Project (3GPP). Various stages of development of the 3GPP LTE standard are called releases. LTE evolution is often referred to as LTE Advanced (LTE-A).

  A communication device will access a communication system based on various access techniques such as code division multiple access (CDMA) or wideband CDMA (WCDMA). The latter technique is used by communication systems based on the 3rd Generation Partnership Project (3GPP) standard. Other examples include time division multiple access (TDMA), frequency division multiple access (FDMA), space division multiple access (SDMA), and the like. A non-limiting example of a mobile architecture to which the principles described herein can be applied is known as an evolved universal terrestrial radio access network (E-UTRAN). In LTE, orthogonal frequency division multiplexing (OFDMA) access techniques are used.

  Non-limiting examples of cellular system base stations are those referred to in the 3GPP vocabulary as NodeB or Evolved NodeB (eNB).

  FIG. 2 shows a schematic diagram of a partial cross-sectional display of a communication device 20 that a user can use for communication. Such communication devices are often referred to as user equipment (UE) or terminals. The device may be mobile or have a generally fixed location. A suitable communication device will be provided by any device capable of transmitting and receiving wireless signals. Non-limiting examples include mobile stations (MS), such as those known as mobile phones or “smartphones”, portable computers with wireless interface cards or other wireless interface equipment, wireless communication capabilities Personal data assistant (PDA), or some combination of these and the like. A communication device provides communication of data to carry communications such as, for example, voice, electronic mail (email), text messages, multimedia, positioning data, other data, and the like. Users are thus presented and provided with a number of services via their communication devices. Non-limiting examples of these services include two-way or multi-way calls, data communications, or multimedia services, or simply access to a data communications network system such as the Internet.

  The communication device typically includes at least one data processing entity 23, at least one memory 24, and the device performs, including access to the base station and other communication devices and control of communication therewith. Software for the task being designed and other possible components 29 used in hardware assisted execution are provided. Data processing, storage, and other related control devices may be provided on appropriate circuit boards and / or in the chipset. This mechanism is represented by reference numeral 26.

  The user may control the operation of the communication device using a suitable user interface such as keypad 22, voice commands, touch sensitive screen or pad, combinations thereof, or the like. A display 25, speakers, and microphone are also typically provided. The communication device may also include appropriate connectors (either wired or wireless) to connect other devices and / or external accessories such as hands-free equipment to the communication device.

  Device 20 may receive and transmit signal 28 via a device suitable for receiving and transmitting the signal. In FIG. 2, the transceiver device is schematically indicated by block 27. The transceiver device is equipped with wireless capability. The transceiver may be provided, for example, by a wireless portion and an associated antenna arrangement. The antenna array may be arranged internally or externally with respect to the mobile device.

  FIG. 3 shows an example of a control device 30 for connecting and / or controlling an access node to a station in a wireless service area, for example one of the nodes 11 or 12 of FIG. 1 as an example. ing. The controller is part of the base station itself in some embodiments. The controller 30 may be arranged to provide control over the configuration, measurement, information processing, and / or communication operations of the access node. The control device according to FIG. 3 is configured to provide control functions associated with the generation, communication and translation of information relating to carrier aggregation and / or other operations. In order to provide the desired operation, the control device 30 comprises at least one memory 31, at least one data processing unit 32, 33 and an input / output interface 34. Via the interface, the control device is coupled to the associated node. Controller 30 may be configured to execute appropriate software to provide a control function.

  It should be appreciated that FIG. 1 shows only one scenario in which the embodiment may be used.

  Currently in LTE, for reconfiguration, intra-cell handover HO is mostly performed, and in order to avoid any ambiguity as to whether the EU is using the old or new configuration, Synchronization must be ensured between the eNB and the EU. For example, because TTI (Transmission Time Interval) bundling affects HARQ (Hybrid Automatic Repeat Request) operation, it is mostly enabled or disabled through intra-cell handover. Similarly, in-cell HO is used when it becomes necessary to change the security key while staying in the same cell (eg, to avoid HFN (Hyperframe Number Wrap Around)). Intra-cell handover means that MAC (Media Access Control), RLC (Radio Link Control), and PDCP (Packet Data Convergence Protocol) are reset, the security key is updated, and the random access procedure is performed in the target cell. It is not different from normal handover. Intra-cell handover is characterized only in that it signals to a target cell that is identical to the source.

  A feature of LTE Advanced is that it can provide carrier aggregation. For example, Release 10 of the E-UTRAN standard (Rel-10) says that two or more component carriers (CC) are aggregated to support a wider transmission bandwidth in the range up to 100 MHz. Carrier Aggregation (CA) is introduced. In CA, the UE is configured to aggregate different numbers of CCs originating from the same eNodeB (eNB), possibly CCs with different uplink (UL) and / or downlink (DL) bandwidths. It is possible. Reference is made to FIG. 4, which shows an aggregated five component carrier. Each component carrier is 20 MHz in this example, giving an aggregate bandwidth of 100 MHz.

  When CA is configured, the UE has only one RRC connection with the network. During RRC (Radio Resource Control) connection establishment / re-establishment / handover, one serving cell provides NAS (non-access layer) protocol mobility information (eg, TAI tracking area identification) to re-establish / During handover, one serving cell provides security input. The security input may be one ECGI (E-UTRAN cell global identifier), one PCI (physical cell identifier), and one ARFCN (absolute radio frequency channel number). This serving cell is called a primary cell (PCell). In the downlink, the carrier corresponding to PCell is the downlink primary component carrier (DL PCC), and in the uplink it is the uplink primary component carrier (UP PCC).

  Depending on the UE capabilities, the secondary cell (SCell) is configured to form a set of serving cells together with the PCell. In the downlink, the carrier corresponding to the SCell is a downlink secondary component carrier (DL SCC), and in the uplink it is an uplink secondary component carrier (UL SCC).

  The set of serving cells configured for the UE thus consists of one PCell and one or more SCells.

  A 3GPP Release 8 UE is assumed to be served by one serving cell, while an LTE Advanced terminal can receive or transmit on multiple serving cells simultaneously.

  From the UE perspective, each uplink resource belongs to only one serving cell. The number of serving cells that can be configured depends on the UE's aggregation capability. The PCell and / or SCell (s) may be changed in the handover procedure of the described embodiment below. PCell is used for transmission of PUCCH. NAS information can be taken from PCell.

  It should be appreciated that some embodiments can also be used in non-carrier aggregation scenarios. For example, in some embodiments, there may be intra-eNB handover, in which case there is no carrier aggregation.

  In Rel-10, one handover procedure is used despite the introduction of carrier aggregation. Regardless of whether the target cell belongs to the configured set of serving cells, handover, ie MAC (Media Access Control), RLC (Radio Link Control), and PDCP (Packet Data Convergence Protocol) are reset and security A procedure is used in which the key is updated and a random access procedure is performed in the target cell.

  Finally, even in a scenario where a baseband pooling architecture such as liquid radio is deployed, handover is always used regardless of whether the target cell belongs to the same hardware pool as the source.

  Liquid radio adapts network capacity and coverage to balance fluid user demands. The baseband processing remains pooled and remote, and the radio frequency elements and antennas are sized and deployed as required.

  Baseband pooling centralizes the digital signal processing typically done at the base station site and separates it from several sites to ensure that capacity is used dynamically as needed. To do. This can balance the network with the end user's actual capacity requirements that fluctuate throughout the day or over longer periods of time.

  When the security key changes, the PDCP layer that performs encryption and integrity protection needs to be reset. When the target cell belongs to the same eNB as the source (or belongs to the same hardware pool as the source), the key change is proposed by the PCC change in 3GPP document R2-102061, which key Not needed as long as you know what will be used (unless the procedure intends to refresh the key to avoid HFN wraparound).

  Normal reconfiguration without HO has been discussed for intra-cell / "serving cell set" handover, but to avoid asynchronous procedures that cause PHY problems, such as PUCCH (physical uplink control channel) ambiguity Is not convincing.

  Changes to the handover procedure are as follows: 3GPP document R2-102061 (PCC change, CATT) for LTE Rel-8 in-cell / in-eNB HO and 3GPP document TS36.331-Radio Resource Control Protocol for Rel-10 Has been discussed in terms of carrier aggregation. It has been proposed to omit the random access process for the target cell and / or leave the security key unchanged to avoid an L2 reset.

  The gain from omitting the RACH (Random Access Channel) process will be limited (several ms on non-contention based RACH). In addition, this process further introduces an ambiguity period, and during that period, the PUCCH needs to be decoded at the eNB.

  Also, if a full L2 reset is to be avoided, the number of HARQ processes in the MAC layer changes when the total number of HARQ processes changes due to TTI (transmission time interval) bundling or TDD (time division duplex) configuration change between the source and target cells. Such a problem will be brought in.

  Some embodiments may provide a somewhat lighter handover procedure to minimize UP (user face) interrupts.

  Embodiments provide a procedure that exists between RRC reconfiguration and handover procedures. This procedure initiates a MAC reset and random access procedure. This means that no RLC / PDCP reset is required. This means that there is no need to change the security key.

  In one embodiment, one bit (or IE or information element) is used independently of mobility control information in the RRC reconfiguration message. The mobility control information may comprise one or more parameters related to mobility by network control to / within the radio access network. This information may comprise handover information. The mobility control information may comprise any suitable parameter. By way of example only, these parameters may include one or more of a parameter indicating a target cell ID, a carrier bandwidth, a random access channel parameter, an uplink bandwidth, and / or a downlink bandwidth. Let's prepare. In the current LTE proposal, this information is called mobilityControlInfo.

  In one embodiment, in an RRC reconfiguration message that does not have mobility control information, the bit indicating reconfiguration is an RRC reconfiguration that requires a MAC reset and a random access procedure (if the target cell is Since it is the same as the source, it is equivalent to the in-cell HO which does not indicate the target cell nor change any keys).

  Alternatively or additionally, in an RRC reconfiguration message with mobility control information, the bit indicating reconfiguration has a MAC reset and random access procedure, but no key change and no RLC / PDCP reset HO.

  In either case, the UE resets the MAC and performs a random access procedure using the RACH for the target cell partner.

  Alternatively or additionally, bits or information elements may be added to the mobility control information. This information element is used to cause the UE to reset the MAC and perform a random access procedure. This information element can be added into the mobility control information. In one embodiment, this mobility control information is provided as part of the RRC reconfiguration message.

  It should be appreciated that the MAC reset and random access procedure may be provided with more than one bit or information element, or in other formats other than one or more bits.

  In other embodiments, it should be appreciated that the information that causes the MAC reset and random access procedures may additionally or alternatively be provided in some other suitable message (s).

  Some embodiments have a RACH procedure that avoids some ambiguous periods. A MAC reset ensures that there are no problems for HARQ operation. Since there is no RLC / PDCP reset, there are fewer UP interrupts. As a result, intra-eNB handover, which would be the majority of handovers in a baseband pooling architecture such as liquid radio, becomes more efficient.

  For example, the method may be performed by one or more processors having one or more memories. Embodiments may be accomplished, at least in part, by execution of one or more computer instructions or computer programs. Reference is now made to FIG. 5, which illustrates the method of the embodiment.

  In step S1, the UE receives reconfiguration information from the base station. This will be provided in an RRC reconfiguration message with instructions to initiate a MAC reset and random access procedure.

  In step S2, the UE performs a MAC reset, for example, resets the NDI (new data indication), flushes the HARQ buffer, etc. as defined in 3GPP TS36.321 as an example. It is also possible to limit to a subset of reset options, for example, only operations related to HARQ may be reset. If reconfiguration is applied in step S3, for example applying the configuration provided in the reconfiguration message (eg enabling or disabling TTI bundling, etc.) and mobility information is included The serving cell is changed to a newly configured serving cell and the associated PHY / MAC configuration is applied. This may be as provided in the radioResourceConfigDedicated message described in 3GPP TS 36.331. In step S4, the UE performs random access to the target cell partner. This is the same as the source cell in some embodiments. In other embodiments, the target cell is different from the source cell. Steps S3 and S4 are interchanged in some embodiments.

  In step S5, the UE completes the serving cell synchronized reconfiguration / handover to the target cell.

  It should be appreciated that one or more of the above steps may be performed as a single step.

  In some embodiments, the reconfiguration message may or may not have a dedicated preamble.

  The random access procedure may be triggered by UL data in a message indicating that RRC reconfiguration is complete. This message may be an RRC Reconfiguration Complete message.

  One or more of the steps may be performed under the control of one or more processors associated with one or more memories. A step may be the result of one or more computer instructions being executed by one or more processors.

  Embodiments can be used for intra-cell handover, some inter-cell handover, and / or some reconfiguration scenarios.

  Embodiments can be used in any one of the following situations.

  1. The eNB is providing more than one cell and the UE is handed over from one of them to the other.

  2. The HetNet scenario is a heterogeneous network deployment with both wide area (macro eNB) and local area (micro / pico / home or femto eNB) access points. In some embodiments, the UE has been handed over from the macro eNB cell to the associated home / micro / pico eNB cell or vice versa. This is only an example. The two cells may be a macro cell and a pico cell, a macro cell and a femto cell, a pico cell and a femto cell, a pico cell and a pico cell, or a femto cell and a femto cell.

  3. In liquid radio, handover is between different base stations. Nevertheless, base station resources are pooled and managed in common.

  4). Reconfiguration without mobility, for example, without changing physical layer parameters.

  Embodiments may be used in situations where there is carrier aggregation in scenarios other than the LTE situation described above. Alternatively or additionally, embodiments may be used in situations where a simplified handover procedure can be used. Some embodiments may be used in scenarios that do not use carrier aggregation.

  Embodiments are implemented by one or more computer programs running on one or more processors, hardware, firmware, dedicated circuitry, or some combination of two or more of the foregoing. I want you to be able to evaluate it. Some embodiments utilize one or more memories. For example, a computer program may comprise computer-executable instructions stored in one or more memories. When run, the computer program (s) uses data stored in one or more memories.

  Although the embodiments have been described with reference to a particular architecture, it should be pointed out that similar principles can be applied to other communication systems where carrier aggregation is not provided. For example, an application in which no fixed access node is provided, such as an ad hoc network, but a communication system is provided using a plurality of user devices. Furthermore, the above principle can also be used in networks where relay nodes are employed to relay transmissions. Thus, while the foregoing describes, by way of example, specific embodiments in connection with specific exemplary wireless network architectures, technologies, and standards, the embodiments are not intended to be anything other than shown and described herein. It can also be applied to other suitable forms of communication systems. It should also be pointed out that various combinations of different embodiments can be implemented. Also, while the above describes exemplary embodiments of the present invention, it is also pointed out that several variations and modifications can be made to the disclosed solution without departing from the spirit and scope of the present invention. Keep it.

1, 2, 3 cells F1, F2, F3 Carrier 10 System 11 Station 12 Base station 13 Controller 15 Gateway 18 Data network 20 Communication device 22 Keypad 23 Data processing entity 24 Memory 25 Display 26 Circuit board or chipset 27 Transceiver device 28 Signals 29 Components for Task Execution 30 Controller 31 Memory 32, 33 Data Processing Unit 34 Input / Output Interface

Claims (24)

  Performing a media access control reset without performing at least one of a radio link control reset and a packet data convergence protocol reset.   The method of claim 1, comprising performing a random access procedure.   Performing the method when the user equipment needs to perform one of intra-cell handover, reconfiguration without mobility, and inter-cell handover between commonly managed cells The method according to claim 1, comprising the step of:   The method according to any one of the preceding claims, comprising receiving a reconfiguration message and performing the media access control reset and / or the random access procedure in response to the reconfiguration message.   The method of claim 4, comprising performing reconfiguration in response to the reconfiguration message.   The method of claim 5, wherein the reconfiguration is performed after the media access control reset and before the random access procedure.   The method according to claim 5 or 6, comprising performing the random access procedure in response to completion of the reconfiguration.   The method of claim 5, wherein the reconfiguration is performed after the media access control reset and after the random access procedure.   9. The reconfiguration message comprises at least one information element, and in response to the information element, the media access control reset and / or the random access procedure is performed. The method described.   The media access control reset comprises performing at least one of resetting a new data indication and flushing a hybrid automatic repeat request buffer. Method.   Performing reconfiguration comprising at least one of enabling transmission time interval bundling, disabling transmission time interval bundling, and changing a serving cell to a newly configured serving cell. A method according to any one of the preceding claims, comprising:   A computer program comprising computer-executable instructions configured to perform the method according to any one of the preceding claims when run. An apparatus comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and computer program code together with the at least one processor are at least in the apparatus,
An apparatus configured to perform a media access control reset without performing at least one of a radio link control reset and a packet data convergence control reset.   The apparatus of claim 13, wherein the at least one memory and computer program code are configured to perform a random access procedure with the at least one processor.   The at least one memory and computer program code, together with the at least one processor, allows the user equipment to perform intra-cell handover, reconfiguration without mobility, and inter-cell handover between commonly managed cells, 15. An apparatus according to claim 13 or 14, configured to perform the media access control reset when it is necessary to perform one of the following.   The at least one memory and computer program code, together with the at least one processor, receive a reconfiguration message and perform the media access control reset and / or the random access procedure in response to the reconfiguration message. The device according to any one of claims 13 to 15, wherein the device is configured.   The apparatus of claim 16, wherein the at least one memory and computer program code are configured to perform reconfiguration in response to the reconfiguration message with the at least one processor.   18. The at least one memory and computer program code is configured to, with the at least one processor, perform the reconfiguration after the media access control reset and before the random access procedure. The device described in 1.   18. The apparatus of claim 16 or 17, wherein the at least one memory and computer program code are configured to perform the random access procedure in response to completion of the reconfiguration with the at least one processor.   The at least one memory and computer program code are configured to, with the at least one processor, perform the reconfiguration after the media access control reset and after the random access procedure. 18. The device according to item 17.   The reconfiguration message comprises at least one information element, and the at least one memory and computer program code, together with the at least one processor, in response to the information element, the media access control reset and / or the random 21. An apparatus according to any one of claims 16 to 20, configured to perform an access procedure.   The media access comprising the at least one memory and computer program code, with the at least one processor, performing at least one of resetting a new data indication and flushing a hybrid automatic repeat request buffer. 22. Apparatus according to any one of claims 13 to 21 configured to perform a control reset.   The at least one memory and computer program code together with the at least one processor enabling or disabling transmission time interval bundling and changing a serving cell to a newly configured serving cell; 23. Apparatus according to any one of claims 13 to 22, configured to perform a reconfiguration comprising at least one.   A user equipment comprising the device according to claim 13.

Images