EP3454624B1 - Appareil et systeme pour la gestion de partie de bande passante et des connections de resource radios - Google Patents
Appareil et systeme pour la gestion de partie de bande passante et des connections de resource radios Download PDFInfo
- Publication number
- EP3454624B1 EP3454624B1 EP18193395.3A EP18193395A EP3454624B1 EP 3454624 B1 EP3454624 B1 EP 3454624B1 EP 18193395 A EP18193395 A EP 18193395A EP 3454624 B1 EP3454624 B1 EP 3454624B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- bwp
- carrier
- communication device
- rrc connection
- rrc
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000004891 communication Methods 0.000 claims description 41
- 238000000034 method Methods 0.000 claims description 36
- 238000012545 processing Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 description 18
- 230000005540 biological transmission Effects 0.000 description 11
- 239000000969 carrier Substances 0.000 description 5
- 235000019527 sweetened beverage Nutrition 0.000 description 5
- 238000007726 management method Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 101150069124 RAN1 gene Proteins 0.000 description 2
- 101100355633 Salmo salar ran gene Proteins 0.000 description 2
- 230000004075 alteration Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000001228 spectrum Methods 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/20—Selecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/34—Selective release of ongoing connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
Definitions
- the present invention relates to a device and system for handling a radio resource control connection.
- a new radio (NR) system initiated by the third generation partnership project (3GPP), is regarded as a new radio interface and a radio network architecture that provides a high data rate, low latency, packet optimization, and improved system capacity and coverage area.
- a radio access network includes a plurality of NR base stations (BSs) (called gNBs), and communicates with a plurality of mobile stations (called user equipments (UEs)).
- BSs NR base stations
- UEs user equipments
- a user equipment receives a radio resource control (RRC) connection release message including redirection information from a serving cell.
- RRC radio resource control
- the UE determines whether to ignore the redirection information in the RRC connection release message according to a release cause of an RRC connection release and a user preference between a unicast service and a multimedia broadcast/multicast service (MBMS) service. If it is determined to ignore the redirection information, the UE ignores the redirection information in the RRC connection release message.
- RRC radio resource control
- Document WO 2016/048114 A1 discloses a method for a terminal managing a configuration for a device-to-device (D2D) operation in a wireless communication system, and a terminal using the method.
- the method is characterized by receiving a D2D configuration for a D2D operation from a network, and maintaining the D2D configuration for the D2D operation without releasing same when leaving the RRC connected state.
- Observation 1 In NR, the UE may not support as large bandwidth as that of the serving cell.
- Observation 2 In L TE, one CC corresponds to one cell, and the maximum bandwidth for one CC is 20MHz both in the network and the UE.
- Observation 3 Multiple CCs can be configured for one UE within same band and/or in different bands.
- one UE can be configured multiple BWPs in each CC, but at most one DL BWP and at most one UL BWP is active at a given time for a serving cell.
- Observation 5 Based on RAN1 agreements, default DL BWP and default DL/UL BWP pair need to be configured via RRC signaling for connected UE working under paired spectrum and unpaired spectrum, respectively.
- Observation 6 Based on RAN1 agreements, the first active DUUL BWP need to be configured via RRC signaling for connected UE in SCell.
- UL BWP fallback for UE-initiated CBRA may introduce a retuning gap, but corresponding performance loss can be ignored since UE is not expecting data for such scenario (uplink synchronization is lost or UE does not have any PUCCH resources available for SR).
- Proposal 1 SSB(s) within the same carrier bandwidth of the cell use the same PCI.
- Proposal 2 Similar to PCell in LTE, one of CCs should be configured as "primary" CC for the purpose of CA management.
- Proposal 3 During connected mode, which BWP is active at a given time is not visible to RRC.
- Proposal 4 Dedicated RRC reconfiguration message is used for addition, release and reconfiguration of BWP.
- Proposal 5 If active BWP is released by explicit BWP release signaling, UE falls back to default DL BWP or default DL/UL BWP pair.
- Proposal 6 In PCell/PSCell, BWP release is implicitly triggered by RLF, PCell handover or PSCell change.
- Proposal 7 BWPs configured in SCell are implicitly released by SCell release.
- Proposal 8 Network can configure a special UL BWP with PRACH resource, together with the corresponding common search space in a DL BWP, for UE in connected mode to fallback and perform CBRA when PRACH resources are not configured in current active UL BWP.
- Proposal 9 If UE does not have configured the special UL BWP, it uses the initial active BWP to perform CBRA in both idle and connected mode unless instructed by network otherwise.
- Proposal 10 During handover, a UL BWP with PRACH resource and corresponding DL BWP with common search space for RACH response of target cell are signaled in HO command so that UE can perform CFRA or CBRA on them.
- Proposal 11 BWPs and measurement object are independently configured, and it is up to gNB implementation to associate BWP quality and RRM reports (i.e. BWP is transparent to both SSB based and CSI-RS based RRM).
- Document US 2018/0139778 A1 discloses a method for wireless communication of UE in a RRC Inactive state, the method includes sending, by the UE, an RRC Connection Resume Request message to a base station, and transmitting, by the UE, a packet to the base station using one or more radio resources allocated by the base station, where the base station identifies the UE based on the RRC Connection Resume Request message, which includes a UE ID or a UE-specific preamble.
- the base station sends a pre-configured random access configuration to the UE for transmitting the packet in a subsequent a random access procedure.
- the pre-configured random access configuration includes at least one of a pre-configured bandwidth part configuration, a plurality of access control parameters, the UE ID, and a time pattern for the random access procedure.
- Proposal-1 Adopt DL assignment/UL grant based activation/deactivation/adaptation of an active BWP.
- Proposal-2 A UE monitors a single DCI format size for DL assignments and a single DCI format for UL grants irrespective of the active BWP it operates on. FFS same DCI format size for DL assignment and UL grants.
- Proposal-3 if UE is configured with more than one BWP, a DL assignment or UL grant contains an explicit DCI field (BWPI), which indicates to a UE a BWP on which the data transmission has been scheduled.
- BWPI explicit DCI field
- a gNB may (transparently) duplicate the DL assignments on both BWPs (departure BWP and destination BWP) to increase reliability of dynamic switching.
- Proposal-4 UE is not expected to receive DL assignments scheduling PDSCH on a BWP within K symbols after PDCCH of the BWP that scheduled PDSCH on the other BWP.
- Proposal-5 For FDD, UE is not expected to receive UL grants scheduling PUSCH for one UL BWP within K symbols after a scheduled PUSCH transmission for another UL BWP.
- Proposal-6 A gNB may configure at least a default DL BWP to a UE; the default DL BWP contains a CSS of the UE.
- Proposal-7 A gNB may configure a UE with: a timer, which triggers the UE to retune to the default DL BWP, if DL assignment or UL grant is not received for X slots on the current active DL BWP; time-pattern, a periodic pattern, which orders UE to retune to a DL BWP.
- Proposal-8 A UE is configured explicitly with a reference-point, with respect to the edge of SSB, given SSB numerology and with RB granularity.
- Proposal-9 The reference point corresponds to commonly indexed sub-carrier #0 which is aligned for all the numerologies. The reference point determines the start of DMRS sequence, the start of RBG grid and the CSI sub-band grid of the NW carrier.
- Proposal-10 A user-specific BWP is configured in terms of PRBs with respect to the reference point and given the SSB numerology.
- a wireless communication system 10 is briefly composed of a network and a plurality of communication devices.
- the network and a communication device may communicate with each other via one or more carriers.
- the network and the communication device may communicate with each other via one or multiple cells (e.g., multiple carriers) belonging to one or multiple base stations (BSs).
- BSs base stations
- the network may include a radio access network (RAN) and a core network.
- the RAN may include at least one base station (BS).
- the RAN may be a next generation (NG) RAN (or called 5G RAN) or an evolved NG-RAN or a sixth generation (6G) RAN.
- the core network may be a 5G core (5GC) network, an evolved 5GC network or a 6G core network.
- a communication device may be a user equipment (UE), an internet-of-thing (IoT) device, a mobile phone, a laptop, a tablet computer, an electronic book, a portable computer system, a vehicle, a ship or an aircraft.
- the network and the communication device can be seen as a transmitter or a receiver according to direction (i.e., transmission direction), e.g., for an uplink (UL), the communication device is the transmitter and the network is the receiver, and for a downlink (DL), the network is the transmitter and the communication device is the receiver.
- direction i.e., transmission direction
- a communication device 20 may be the communication device 100, the BS(s) 102 and/or 104 shown in Fig. 1 , but is not limited herein.
- the communication device 20 includes at least one processing circuit 200 such as a microprocessor or Application Specific Integrated Circuit (ASIC), at least one storage device 210 and at least one communication interfacing device 220.
- the at least one storage device 210 may be any data storage device that may store program codes 214, accessed and executed by the at least one processing circuit 200.
- Examples of the at least one storage device 210 include but are not limited to a subscriber identity module (SIM), read-only memory (ROM), flash memory, random-access memory (RAM), hard disk, optical data storage device, non-volatile storage device, non-transitory computer-readable medium (e.g., tangible media), etc.
- SIM subscriber identity module
- ROM read-only memory
- RAM random-access memory
- the at least one communication interfacing device 220 is preferably at least one transceiver and is used to transmit and receive signals (e.g., data, messages and/or packets) according to processing results of the at least one processing circuit 200.
- a UE is used for representing the communication device 100 in Fig. 1 , to simplify the illustration of the examples.
- a carrier e.g., component carrier
- BWP BWP1 which includes a synchronization signal block (SSB) and remaining system information (RMSI).
- SSB synchronization signal block
- RMSI remaining system information
- BWP BWP2 which does not include the SSB and the RMSI.
- BWP BWP3 which includes the SSB but does not include the RMSI.
- the SSB includes a primary SS (PSS), a secondary SS (SSS) and/or a physical broadcast channel (PBCH).
- the RMSI includes a system information block (SIB).
- a DL carrier has no BWP (e.g., the whole DL carrier is a BWP), or has at least two BWPs of which each BWP belongs to one of the three types.
- a UL carrier has no BWP (e.g., the UE is capable of transmitting on the whole bandwidth of the UL carrier), or has at least two BWPs of which each BPW is the BWP BWP2.
- the DL carrier and the UL carrier may be the same carrier or different carriers.
- a process 40 in Fig. 4 is utilized in a first BS (e.g., in the network in Fig. 1 ), and includes the following steps:
- the first BS configures a RRC connection and a data radio bearer (DRB) to communicate data associated to the RRC connection and the DRB with the first UE in the first BWP.
- the first carrier may include at least two BWPs, and the first BWP is one of the at least two BWPs.
- the first BS only transmits a control signal (e.g., Physical DL Control Channel (PDCCH)) and the data associated to the RRC connection and the DRB to the first UE in the first BWP. That is, only the first BWP used by the first BS for communications between the first UE and the first BS.
- PDCH Physical DL Control Channel
- the first BS transmits the data to the first UE in the first BWP, and transmits a control signal in a third BWP or a fourth BWP of the at least two BWPs at the first carrier. In one example, the first BS transmits a control signal and the data to the first UE in the first BWP and one of a third BWP or a fourth BWP of the at least two BWPs.
- a location (i.e., in a frequency domain) of the second BWP is different from a location of the first BWP. Locations of the at least two BWPs may or may not be overlapped.
- the first BS receives first UE capabilities (e.g., in UE-NR-Capability) from the first UE, a second BS or a core network node (e.g., Access and Mobility Management function (AMF) or Mobility Management Entity (MME)).
- the first UE capabilities may indicate (e.g., include) a first maximum transmission bandwidth (TX_BW) and a first maximum reception bandwidth (RX_BW) for a first frequency band belonging to the first carrier.
- the first maximum TX_BW may be equal to or smaller than the first maximum RX_BW.
- the first maximum RX_BW indicates a maximum RX_BW on which the UE is capable of performing a reception.
- the first maximum TX_BW indicates a maximum TX_BW on which the UE is capable of performing a transmission.
- the first maximum TX_BW is greater than or equal to a first TX_BW (i.e., a bandwidth where a UL transmission spans is smaller than or equal to the first TX_BW) configured by the first BS to the UE.
- the first BS configures or schedules any transmission from the UE within the first TX_BW.
- a bandwidth of the first/second BWP is smaller than or equal to the first maximum RX_BW.
- the first carrier is identified by a first Absolute Radio Frequency Channel Number (ARFCN), and the second carrier is identified by a second ARFCN.
- the first carrier may be same as the second carrier, and the first ARFCN is same as the second ARFCN.
- the first carrier may be different from the second carrier, and the first ARFCN is different from the second ARFCN.
- the RRC Connection Release message may or may not include the second ARFCN.
- the RRC Connection Release message may include BWP information/configuration.
- the BWP information/configuration indicates a location of the RX_BW identifying the second BWP.
- the BWP information/configuration indicates a RX_BW of the second BWP.
- the first UE selects a cell in a BWP at the first carrier to camp on.
- the BWP is different from the first BWP.
- the first UE if the first UE fails to find any suitable cell on the second BWP at the second carrier configured in the RRC Connection Release message, the first UE searches any suitable cell in a BWP at any carrier different from the second carrier configured in the RRC Connection Release message.
- the first BS obtains (e.g., determines) which BWP configured to a UE in the RRC Connection Release message according to a maximum RX_BW of the UE and/or distributing (e.g., allocating) UEs in BWPs of a carrier.
- the first BS may communicate with a second UE in the first BWP at the first carrier.
- the first BS transmits a RRC Connection Release message to the second UE, wherein the RRC Connection Release message configures the second UE to enter an IDLE state or an INACTIVE state and to camp on a fifth BWP at a second carrier.
- a location of the fifth BWP is different from a location of the first BWP and the second BWP.
- the first BS determines which BWP configured to a UE in the RRC Connection Release message according to characteristic(s) of a BWP.
- the characteristic(s) includes at least one of a subcarrier spacing of the BWP, a bandwidth of the BWP, SSBs broadcasted and essential SIB(s) broadcasted.
- the essential SIB(s) includes a SIB type 1 (SIB1) and/or a SIB type 2 (SIB2).
- the first BS determines to configure the second BWP in the RRC Connection Release message, considering/when SSBs and essential SIB(s) are broadcasted in the second BWP (e.g., while the SSBs and/or the essential SIB(s) is/are not broadcasted in the first BWP).
- the first BS determines to configure the second BWP in the RRC Connection Release message, considering/when the second BWP has a subcarrier spacing and/or a bandwidth smaller than that of the first BWP.
- the BWP information/configuration may include the characteristic(s).
- the BWP information/configuration indicates the subcarrier spacing or indicates location of the SSBs and/or the essential SIB(s).
- a process 50 in Fig. 5 is utilized in a UE, and includes the following steps:
- the UE selects a cell on the second BWP.
- the description for the process 40 may be applied to the process 50.
- a process 60 in Fig. 6 is utilized in a UE, and includes the following steps:
- the UE selects a cell on the second BWP.
- the RRC Connection Release message configures neither a carrier nor a BWP. That is, the RRC Connection Release message may not include carrier information/configuration (e.g., ARFCN) and BWP information/configuration.
- the UE may determine to select the cell in the second BWP at the first carrier. In one example, the UE determines to select the second BWP instead of the first BWP, when SSB(s) is broadcasted in the second BWP and no SSB is broadcasted in the first BWP.
- the UE determines to select the second BWP instead of the first BWP, when SSBs and essential SIB(s) (e.g., SIB 1 and/or SIB2) are broadcasted in the second BWP and no essential SIB or no SSB is broadcasted in the first BWP.
- the UE determines to select the second BWP instead of the first BWP according to its stored configuration. For example, the UE receives the stored configuration in a SIB.
- the UE receives the stored configuration in a dedicated message (e.g., RRC message, Open Mobile Alliance (OMA) message, Bearer Independent Protocol (BIP) message or Non Access Stratum (NAS) message).
- a dedicated message e.g., RRC message, Open Mobile Alliance (OMA) message, Bearer Independent Protocol (BIP) message or Non Access Stratum (NAS) message.
- the UE communicates with the first BS via the cell in the first BWP at the first carrier or via another cell in the second BWP at the first carrier.
- the UE in the IDLE state camps on a cell of the first BS in the second BWP at the first carrier. Then, the UE performs a RRC procedure (e.g., RRC connection establishment procedure) via the cell of the first BS in the second BWP at the first carrier, to enter a CONNECTED state from the IDLE state. The UE performs a RRC connection reconfiguration procedure (initiated by the first BS) with the first BS via the cell of the first BS in the second BWP at the first carrier.
- a RRC procedure e.g., RRC connection establishment procedure
- the UE performs a RRC connection reconfiguration procedure (initiated by the first BS) with the first BS via the cell of the first BS in the second BWP at the first carrier.
- the first BS transmits a RRC Connection Reconfiguration message of the RRC connection reconfiguration procedure in the second BWP to the UE, wherein the RRC Connection Reconfiguration message configures the UE to communicate with the first BS in the first BWP at the first carrier.
- the first BS performs Step 402 according to the RRC Connection Reconfiguration message.
- the UE performs Step 502 or Step 602 in response to/according to the RRC Connection Reconfiguration message.
- the UE may transmit a RRC Connection Reconfiguration Complete message in response to the RRC Connection Reconfiguration message in the first BWP at the first carrier, the second BWP at the first carrier, or a sixth BWP at a third carrier.
- the first carrier and the third carrier are TDD carriers.
- the first carrier is a FDD carrier for a DL
- the third carrier is a FDD carrier for a UL.
- a bandwidth of the sixth BWP is not greater than the maximum TX_BW of the UE.
- the UE in the INACTIVE state camps on a cell of the first BS in the second BWP at the first carrier. Then, the UE performs a RRC procedure (e.g., RRC connection resume procedure) via the cell of the first BS in the second BWP at the first carrier, to enter the CONNECTED state from the INACTIVE state.
- a RRC procedure e.g., RRC connection resume procedure
- the UE may resume communicating with the first BS in the first BWP.
- the UE may receive Physical DL Shared Channel (PDSCH) transmissions from the first BS in the first BWP at the first carrier.
- PDSCH Physical DL Shared Channel
- Each of the PDSCH transmissions may include a Medium Access Control (MAC) protocol data unit (PDU).
- PDU Medium Access Control
- the UE transmits Physical UL Shared Channel (PUSCH) transmissions to the first BS in the first BWP at the first carrier or in a seventh BWP at a fourth carrier.
- Each of the PUSCH transmissions may include a MAC PDU.
- the first carrier and the seventh carrier are TDD carriers.
- the first carrier is a FDD carrier for a DL
- the fourth carrier is a FDD carrier for a UL.
- the fourth carrier may be same as or different from the third carrier.
- the seventh BWP may be same as or different from the sixth BWP.
- a bandwidth of the seventh BWP is not larger than the maximum TX_BW of the UE.
- a RX_BW of a BWP may be represented by the number of physical resource blocks (PRBs).
- a location of a BWP may be indicated by location(s) of the PRBs.
- BWP information/configuration may include information indicating a starting PRB of the BWP, an end PRB of the BWP or a center PRB of the BWP, to indicate the location of the BWP.
- BWP information/configuration may include a starting PRB number identifying the starting PRB and the number of PRBs, to indicate the location of the BWP.
- the present invention provides a method and related communication device for handling a RRC connection.
- the communication device knows how to camp on a proper BPW at a carrier according to a received RRC message.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Claims (6)
- Un dispositif de communication (20) pour gérer une connexion de contrôle de ressources radio (radio resource control, RRC) comprenant :au moins un dispositif de stockage (210) ; etau moins un circuit de traitement (200), couplé à l'au moins un dispositif de stockage (210), dans lequel l'au moins un dispositif de stockage (210) stocke (214), et l'au moins un circuit de traitement (200) est configuré pour exécuter des instructions de :communiquer (602) avec une station de base (base station, BS) dans une première partie de bande passante (bandwidth part, BWP) à une première porteuse ;recevoir (604) un message de Libération de Connexion RRC de la BS, dans lequel le message de Libération de Connexion RRC configure le dispositif de communication (20) pour entrer dans un état VEILLE ou un état INACTIF ; etcamper (606) sur un deuxième BWP à la première porteuse ;caractérisé en ce que le dispositif de communication (20) est configuré pour déterminer de sélectionner le deuxième BWP à la première porteuse au lieu de la première BWP à la première porteuse, lorsqu'un bloc de signal de synchronisation (synchronization signal block, SSB) et un bloc d'informations système (system information block, SIB) essentiel sont diffusés dans la deuxième BWP à la première porteuse et qu'aucun SIB essentiel ou aucun SSB n'est diffusé dans la première BWP à la première porteuse.
- Le dispositif de communication (20) de la revendication 1, dans lequel le message de Libération de Connexion RRC ne configure pas une porteuse et une BWP au dispositif de communication (20).
- Le dispositif de communication (20) de la revendication 1, dans lequel le dispositif de communication (20) sélectionne une cellule dans la deuxième BWP à la première porteuse selon une configuration stockée dans le dispositif de communication (20) ; et la configuration stockée est reçue dans un bloc d'informations système (system information block, SIB) ou est reçue dans un message dédié.
- Le dispositif de communication (20) de la revendication 1, dans lequel les instructions comprennent en outre :camper sur une cellule dans la deuxième BWP à la première porteuse, lorsque le dispositif de communication (20) est dans l'état VEILLE ; etexécuter une procédure RRC via la cellule dans la deuxième BWP à la première porteuse, pour entrer dans un état CONNECTÉ à partir de l'état VEILLE.
- Un système pour gérer une connexion de contrôle de ressources radio (radio resource control, RRC) comprenant :un dispositif de communication (20) selon l'une quelconque des revendications 1 à 4 ; etune station de base (base station, BS), la BS comprenant :au moins un dispositif de stockage (210) ; etau moins un circuit de traitement (200), couplé à l'au moins un dispositif de stockage (210), dans lequel le au moins un dispositif de stockage (210) stocke (214), et l'au moins un circuit de traitement (200) est configuré pour exécuter des instructions de :communiquer (402), avec le dispositif de communication (20), dans une première partie de bande passante (bandwidth part, BWP) à une première porteuse ; ettransmettre (404) un message de Libération de Connexion RRC au dispositif de communication (20), dans lequel le message de Libération de Connexion RRC configure le dispositif de communication (20) pour entrer dans un état VEILLE ou un état INACTIF.
- Le système de la revendication 5, dans lequel les instructions comprennent en outre :
configurer une connexion RRC et un support radio de données (data radio bearer, DRB), pour communiquer des données associées à la connexion RRC et au DRB avec le dispositif de communication (20) dans la première BWP à la première porteuse.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201762556500P | 2017-09-10 | 2017-09-10 |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3454624A1 EP3454624A1 (fr) | 2019-03-13 |
EP3454624B1 true EP3454624B1 (fr) | 2022-04-06 |
Family
ID=63578970
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP18193395.3A Active EP3454624B1 (fr) | 2017-09-10 | 2018-09-10 | Appareil et systeme pour la gestion de partie de bande passante et des connections de resource radios |
Country Status (2)
Country | Link |
---|---|
US (1) | US10660142B2 (fr) |
EP (1) | EP3454624B1 (fr) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11147009B2 (en) * | 2018-08-07 | 2021-10-12 | Mediatek Inc. | Apparatuses and methods for configuration of initial downlink (DL) bandwidth part (BWP) |
CN110831126A (zh) * | 2018-08-10 | 2020-02-21 | 华为技术有限公司 | 一种通信方法、装置及系统 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103828423B (zh) * | 2011-09-30 | 2018-04-27 | Sca艾普拉控股有限公司 | 移动通信系统,基础设施设备,基站和方法 |
US9510252B2 (en) * | 2012-04-24 | 2016-11-29 | Lg Electronics Inc. | Method and apparatus for selecting cell in wireless communication system |
WO2016048114A1 (fr) * | 2014-09-27 | 2016-03-31 | 엘지전자 주식회사 | Procédé pour qu'un terminal gère une configuration pour une opération de dispositif à dispositif (d2d) dans un système de communication sans fil, et terminal l'utilisant |
WO2018086600A1 (fr) * | 2016-11-11 | 2018-05-17 | Chou Chie Ming | Distribution de paquets de données dans un état inactif rrc |
-
2018
- 2018-09-10 US US16/125,795 patent/US10660142B2/en active Active
- 2018-09-10 EP EP18193395.3A patent/EP3454624B1/fr active Active
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
US20190082480A1 (en) | 2019-03-14 |
EP3454624A1 (fr) | 2019-03-13 |
US10660142B2 (en) | 2020-05-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11071086B2 (en) | Wireless communications for network access configuration | |
EP3751776A1 (fr) | Communications sans fil et transmission/réception d'informations de contrôle | |
CN109327907B (zh) | 处理带宽部分的装置及方法 | |
US20220247518A1 (en) | Uplink Channel Switching Capability and Selecting Between Uplink Channels in a Cell Group Based Thereon | |
US20220140950A1 (en) | Wireless Device Control Channel Monitoring | |
EP3439221B1 (fr) | Dispositif et procédé de gestion d'agrégation de porteuses et de double connectivité | |
EP3183924B1 (fr) | Techniques de transmettre et recevoir de messages de recherche par une bande spectrale de fréquences radio sans licence | |
US10212732B2 (en) | Method for transmitting and receiving uplink data using contention based resources in wireless communication system and apparatus therefor | |
JP2019216481A (ja) | Eノードb間のキャリアアグリゲーションのためのul tdmの方法 | |
WO2018230604A1 (fr) | Système de communication | |
US11259335B2 (en) | Resource allocation method, terminal, and network device | |
JP7348301B2 (ja) | リソース構成方法、デバイス及び記憶媒体 | |
US10531508B2 (en) | Device and method of handling carrier aggregation and dual connectivity | |
JP2022538211A (ja) | Bwpの管理方法および装置、端末 | |
JP2022528627A (ja) | ランダムアクセス方法及び装置 | |
EP3439421B1 (fr) | Dispositif et procédé supportant l'accès à des cellules secondaires pour une double connectivité | |
EP3240310A1 (fr) | Dispositifs de transfert de connexion | |
EP3454624B1 (fr) | Appareil et systeme pour la gestion de partie de bande passante et des connections de resource radios | |
US20230164807A1 (en) | Communication method and device based on common frequency resource for group common transmission in wireless communication system | |
JP6887135B2 (ja) | 装置間(d2d)通信における改良されたリソース割当て | |
WO2022217459A1 (fr) | Perforation de symboles pendant une procédure de canal d'accès aléatoire (rach) | |
CN117643171A (zh) | 多卡场景下的mg配置方法、装置、设备及存储介质 | |
CN116491198A (zh) | 用于下行链路传输的频域资源分配的方法及设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20180910 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 48/20 20090101ALN20211006BHEP Ipc: H04W 76/36 20180101AFI20211006BHEP |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 48/20 20090101ALN20211011BHEP Ipc: H04W 76/36 20180101AFI20211011BHEP |
|
INTG | Intention to grant announced |
Effective date: 20211102 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1482622 Country of ref document: AT Kind code of ref document: T Effective date: 20220415 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602018033263 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1482622 Country of ref document: AT Kind code of ref document: T Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220808 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220706 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220707 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220706 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220806 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602018033263 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20230110 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20220930 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20220910 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230602 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20220930 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20220910 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20220930 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20230719 Year of fee payment: 6 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20220930 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20230720 Year of fee payment: 6 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20230703 Year of fee payment: 6 Ref country code: DE Payment date: 20230718 Year of fee payment: 6 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20180910 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |