US10608797B2 - Distributed unit connection issue - Google Patents
Distributed unit connection issue Download PDFInfo
- Publication number
- US10608797B2 US10608797B2 US16/011,363 US201816011363A US10608797B2 US 10608797 B2 US10608797 B2 US 10608797B2 US 201816011363 A US201816011363 A US 201816011363A US 10608797 B2 US10608797 B2 US 10608797B2
- Authority
- US
- United States
- Prior art keywords
- wireless device
- base station
- message
- radio
- network entity
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/24—Cell structures
- H04W16/28—Cell structures using beam steering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/046—Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
-
- H04W72/085—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
-
- 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/32—Release of transport tunnels
-
- 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
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
Definitions
- FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present invention.
- FIG. 2 is a diagram depicting an example transmission time and reception time for two carriers in a carrier group as per an aspect of an embodiment of the present invention.
- FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present invention.
- FIG. 4 is a block diagram of a base station and a wireless device as per an aspect of an embodiment of the present invention.
- FIG. 5A , FIG. 5B , FIG. 5C and FIG. 5D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present invention.
- FIG. 6 is an example diagram for a protocol structure with multi-connectivity as per an aspect of an embodiment of the present invention.
- FIG. 7 is an example diagram for a protocol structure with CA and DC as per an aspect of an embodiment of the present invention.
- FIG. 8 shows example TAG configurations as per an aspect of an embodiment of the present invention.
- FIG. 9 is an example message flow in a random access process in a secondary TAG as per an aspect of an embodiment of the present invention.
- FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5G core network (e.g. NGC) and base stations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment of the present invention.
- a 5G core network e.g. NGC
- base stations e.g. gNB and eLTE eNB
- FIG. 11A , FIG. 11B , FIG. 11C , FIG. 11D , FIG. 11E , and FIG. 11F are example diagrams for architectures of tight interworking between 5G RAN (e.g. gNB) and LTE RAN (e.g. (e)LTE eNB) as per an aspect of an embodiment of the present invention.
- 5G RAN e.g. gNB
- LTE RAN e.g. (e)LTE eNB
- FIG. 12A , FIG. 12B , and FIG. 12C are example diagrams for radio protocol structures of tight interworking bearers as per an aspect of an embodiment of the present invention.
- FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenarios as per an aspect of an embodiment of the present invention.
- FIG. 14 is an example diagram for functional split option examples of the centralized gNB deployment scenario as per an aspect of an embodiment of the present invention.
- FIG. 18 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 19 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 20 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 22 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 23 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 25 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 26 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 27 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 28 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 30 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 31 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 32 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 33 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 34 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 35 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 36 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 37 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 38 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 39 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 40 is an example diagram of an aspect of an embodiment of the present disclosure.
- FIG. 41 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 42 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 43 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 44 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 45 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 46 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 47 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 48 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 49 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 50 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 51 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 52 is a flow diagram of an aspect of an embodiment of the present disclosure.
- FIG. 53 is a flow diagram of an aspect of an embodiment of the present disclosure.
- Example embodiments of the present invention enable operation of wireless communication systems.
- Embodiments of the technology disclosed herein may be employed in the technical field of multicarrier communication systems. More particularly, the embodiments of the technology disclosed herein may relate to cellular wireless systems in a multicarrier communication systems.
- Example embodiments of the invention may be implemented using various physical layer modulation and transmission mechanisms.
- Example transmission mechanisms may include, but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.
- Various modulation schemes may be applied for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like.
- An example radio transmission method may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like.
- Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions.
- FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present invention.
- arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDM system.
- the OFDM system may use technology such as OFDM technology, DFTS-OFDM, SC-OFDM technology, or the like.
- arrow 101 shows a subcarrier transmitting information symbols.
- FIG. 1 is for illustration purposes, and a typical multicarrier OFDM system may include more subcarriers in a carrier.
- the number of subcarriers in a carrier may be in the range of 10 to 10,000 subcarriers.
- FIG. 1 shows two guard bands 106 and 107 in a transmission band. As illustrated in FIG.
- guard band 106 is between subcarriers 103 and subcarriers 104 .
- the example set of subcarriers A 102 includes subcarriers 103 and subcarriers 104 .
- FIG. 1 also illustrates an example set of subcarriers B 105 . As illustrated, there is no guard band between any two subcarriers in the example set of subcarriers B 105 .
- Carriers in a multicarrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of both contiguous and non-contiguous carriers.
- FIG. 2 is a diagram depicting an example transmission time and reception time for two carriers as per an aspect of an embodiment of the present invention.
- a multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 10 carriers.
- Carrier A 204 and carrier B 205 may have the same or different timing structures. Although FIG. 2 shows two synchronized carriers, carrier A 204 and carrier B 205 may or may not be synchronized with each other.
- Different radio frame structures may be supported for FDD and TDD duplex mechanisms.
- FIG. 2 shows an example FDD frame timing. Downlink and uplink transmissions may be organized into radio frames 201 . In this example, radio frame duration is 10 msec. Other frame durations, for example, in the range of 1 to 100 msec may also be supported.
- each 10 ms radio frame 201 may be divided into ten equally sized subframes 202 .
- Other subframe durations such as including 0.5 msec, 1 msec, 2 msec, and 5 msec may also be supported.
- Subframe(s) may consist of two or more slots (e.g. slots 206 and 207 ).
- 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in each 10 ms interval. Uplink and downlink transmissions may be separated in the frequency domain.
- a slot may be 7 or 14 OFDM symbols for the same subcarrier spacing of up to 60 kHz with normal CP.
- a slot may be 14 OFDM symbols for the same subcarrier spacing higher than 60 kHz with normal CP.
- a slot may contain all downlink, all uplink, or a downlink part and an uplink part and/or alike.
- Slot aggregation may be supported, e.g., data transmission may be scheduled to span one or multiple slots.
- a mini-slot may start at an OFDM symbol in a subframe.
- a mini-slot may have a duration of one or more OFDM symbols.
- Slot(s) may include a plurality of OFDM symbols 203 . The number of OFDM symbols 203 in a slot 206 may depend on the cyclic prefix length and subcarrier spacing.
- FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present invention.
- the resource grid structure in time 304 and frequency 305 is illustrated in FIG. 3 .
- the quantity of downlink subcarriers or RBs may depend, at least in part, on the downlink transmission bandwidth 306 configured in the cell.
- the smallest radio resource unit may be called a resource element (e.g. 301 ).
- Resource elements may be grouped into resource blocks (e.g. 302 ).
- Resource blocks may be grouped into larger radio resources called Resource Block Groups (RBG) (e.g. 303 ).
- the transmitted signal in slot 206 may be described by one or several resource grids of a plurality of subcarriers and a plurality of OFDM symbols.
- multiple numerologies may be supported.
- a numerology may be derived by scaling a basic subcarrier spacing by an integer N.
- scalable numerology may allow at least from 15 kHz to 480 kHz subcarrier spacing.
- the numerology with 15 kHz and scaled numerology with different subcarrier spacing with the same CP overhead may align at a symbol boundary every 1 ms in a NR carrier.
- FIG. 5A , FIG. 5B , FIG. 5C and FIG. 5D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present invention.
- FIG. 5A shows an example uplink physical channel.
- the baseband signal representing the physical uplink shared channel may perform the following processes. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.
- Example modulation and up-conversion to the carrier frequency of the complex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna port and/or the complex-valued PRACH baseband signal is shown in FIG. 5B . Filtering may be employed prior to transmission.
- FIG. 4 is an example block diagram of a base station 401 and a wireless device 406 , as per an aspect of an embodiment of the present invention.
- a communication network 400 may include at least one base station 401 and at least one wireless device 406 .
- the base station 401 may include at least one communication interface 402 , at least one processor 403 , and at least one set of program code instructions 405 stored in non-transitory memory 404 and executable by the at least one processor 403 .
- the wireless device 406 may include at least one communication interface 407 , at least one processor 408 , and at least one set of program code instructions 410 stored in non-transitory memory 409 and executable by the at least one processor 408 .
- Communication interface 402 in base station 401 may be configured to engage in communication with communication interface 407 in wireless device 406 via a communication path that includes at least one wireless link 411 .
- Wireless link 411 may be a bi-directional link.
- Communication interface 407 in wireless device 406 may also be configured to engage in a communication with communication interface 402 in base station 401 .
- Base station 401 and wireless device 406 may be configured to send and receive data over wireless link 411 using multiple frequency carriers.
- transceiver(s) may be employed.
- a transceiver is a device that includes both a transmitter and receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like.
- Example embodiments for radio technology implemented in communication interface 402 , 407 and wireless link 411 are illustrated are FIG. 1 , FIG. 2 , FIG. 3 , FIG. 5 , and associated text.
- An interface may be a hardware interface, a firmware interface, a software interface, and/or a combination thereof.
- the hardware interface may include connectors, wires, electronic devices such as drivers, amplifiers, and/or the like.
- a software interface may include code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like.
- a firmware interface may include a combination of embedded hardware and code stored in and/or in communication with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like.
- the term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics in the device, whether the device is in an operational or non-operational state.
- a 5G network may include a multitude of base stations, providing a user plane NR PDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocol terminations towards the wireless device.
- the base station(s) may be interconnected with other base station(s) (e.g. employing an Xn interface).
- the base stations may also be connected employing, for example, an NG interface to an NGC.
- FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5G core network (e.g. NGC) and base stations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment of the present invention.
- a 5G core network e.g. NGC
- base stations e.g. gNB and eLTE eNB
- the base stations may be interconnected to the NGC control plane (e.g. NG CP) employing the NG-C interface and to the NGC user plane (e.g. UPGW) employing the NG-U interface.
- the NG interface may support a many-to-many relation between 5G core networks and base stations.
- a base station may include many sectors for example: 1, 2, 3, 4, or 6 sectors.
- a base station may include many cells, for example, ranging from 1 to 50 cells or more.
- a cell may be categorized, for example, as a primary cell or secondary cell.
- one serving cell may provide the NAS (non-access stratum) mobility information (e.g. TAI), and at RRC connection re-establishment/handover, one serving cell may provide the security input.
- This cell may be referred to as the Primary Cell (PCell).
- the carrier corresponding to the PCell may be the Downlink Primary Component Carrier (DL PCC), while in the uplink, it may be the Uplink Primary Component Carrier (UL PCC).
- DL PCC Downlink Primary Component Carrier
- U PCC Uplink Primary Component Carrier
- SCells may be configured to form together with the PCell a set of serving cells.
- the carrier corresponding to an SCell may be a Downlink Secondary Component Carrier (DL SCC), while in the uplink, it may be an Uplink Secondary Component Carrier (UL SCC).
- DL SCC Downlink Secondary Component Carrier
- UL SCC Uplink Secondary Component Carrier
- An SCell may or may not have an uplink carrier.
- a cell comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and a cell index.
- a carrier downlink or uplink
- the cell ID or Cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context it is used).
- cell ID may be equally referred to a carrier ID, and cell index may be referred to carrier index.
- the physical cell ID or cell index may be assigned to a cell.
- a cell ID may be determined using a synchronization signal transmitted on a downlink carrier.
- a cell index may be determined using RRC messages.
- the specification when the specification refers to a first physical cell ID for a first downlink carrier, the specification may mean the first physical cell ID is for a cell comprising the first downlink carrier.
- the same concept may apply to, for example, carrier activation.
- the specification indicates that a first carrier is activated, the specification may equally mean that the cell comprising the first carrier is activated.
- Embodiments may be configured to operate as needed.
- the disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like.
- Example criteria may be based, at least in part, on for example, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like.
- traffic load When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.
- a base station may communicate with a mix of wireless devices.
- Wireless devices may support multiple technologies, and/or multiple releases of the same technology.
- Wireless devices may have some specific capability(ies) depending on its wireless device category and/or capability(ies).
- a base station may comprise multiple sectors.
- this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station.
- the plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices perform based on older releases of LTE or 5G technology.
- FIG. 6 and FIG. 7 are example diagrams for protocol structure with CA and multi-connectivity as per an aspect of an embodiment of the present invention.
- NR may support multi-connectivity operation whereby a multiple RX/TX UE in RRC_CONNECTED may be configured to utilize radio resources provided by multiple schedulers located in multiple gNBs connected via a non-ideal or ideal backhaul over the Xn interface.
- gNBs involved in multi-connectivity for a certain UE may assume two different roles: a gNB may either act as a master gNB or as a secondary gNB. In multi-connectivity, a UE may be connected to one master gNB and one or more secondary gNBs.
- FIG. 7 illustrates one example structure for the UE side MAC entities when a Master Cell Group (MCG) and a Secondary Cell Group (SCG) are configured, and it may not restrict implementation.
- MCG Master Cell Group
- SCG Secondary Cell Group
- MBMS Media Broadcast Multicast Service
- the radio protocol architecture that a particular bearer uses may depend on how the bearer is setup. Three alternatives may exist, an MCG bearer, an SCG bearer and a split bearer as shown in FIG. 6 .
- NR RRC may be located in master gNB and SRBs may be configured as a MCG bearer type and may use the radio resources of the master gNB.
- Multi-connectivity may also be described as having at least one bearer configured to use radio resources provided by the secondary gNB. Multi-connectivity may or may not be configured/implemented in example embodiments of the invention.
- the UE may be configured with multiple NR MAC entities: one NR MAC entity for master gNB, and other NR MAC entities for secondary gNBs.
- the configured set of serving cells for a UE may comprise of two subsets: the Master Cell Group (MCG) containing the serving cells of the master gNB, and the Secondary Cell Groups (SCGs) containing the serving cells of the secondary gNBs.
- MCG Master Cell Group
- SCGs Secondary Cell Groups
- a SCG For a SCG, one or more of the following may be applied: at least one cell in the SCG has a configured UL CC and one of them, named PSCell (or PCell of SCG, or sometimes called PCell), is configured with PUCCH resources; when the SCG is configured, there may be at least one SCG bearer or one Split bearer; upon detection of a physical layer problem or a random access problem on a PSCell, or the maximum number of NR RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: a RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of the SCG are stopped, a master gNB may be informed by the UE of a SCG failure type, for split bearer, the DL data transfer over the master gNB is maintained; the NR RLC AM bearer may be configured for the split bearer; like PCell, P
- the master gNB may maintain the RRM measurement configuration of the UE and may, (e.g, based on received measurement reports or traffic conditions or bearer types), decide to ask a secondary gNB to provide additional resources (serving cells) for a UE; upon receiving a request from the master gNB, a secondary gNB may create a container that may result in the configuration of additional serving cells for the UE (or decide that it has no resource available to do so); for UE capability coordination, the master gNB may provide (part of) the AS configuration and the UE capabilities to the secondary gNB; the master gNB and the secondary gNB may exchange information about a UE configuration by employing of NR RRC containers (inter-node messages) carried in Xn messages; the secondary gNB may initiate a reconfiguration of its existing serving cells (e.g., PUCCH towards the secondary gNB);
- NR RRC containers inter-node messages
- serving cells may be grouped in a TA group (TAG).
- TAG TA group
- Serving cells in one TAG may use the same timing reference.
- UE user equipment
- UE may use at least one downlink carrier as a timing reference.
- a UE may synchronize uplink subframe and frame transmission timing of uplink carriers belonging to the same TAG.
- serving cells having an uplink to which the same TA applies may correspond to serving cells hosted by the same receiver.
- a UE supporting multiple TAs may support two or more TA groups.
- One TA group may contain the PCell and may be called a primary TAG (pTAG).
- At least one TA group may not contain the PCell and may be called a secondary TAG (sTAG).
- sTAG secondary TAG
- carriers within the same TA group may use the same TA value and/or the same timing reference.
- cells belonging to a cell group MCG or SCG may be grouped into multiple TAGs including a pTAG and one or more sTAGs.
- FIG. 8 shows example TAG configurations as per an aspect of an embodiment of the present invention.
- pTAG comprises PCell
- an sTAG comprises SCell 1 .
- a pTAG comprises a PCell and SCell 1
- an sTAG comprises SCell 2 and SCell 3 .
- pTAG comprises PCell and SCell 1
- an sTAG 1 includes SCell 2 and SCell 3
- sTAG 2 comprises SCell 4 .
- Up to four TAGs may be supported in a cell group (MCG or SCG) and other example TAG configurations may also be provided.
- MCG cell group
- example TAG configurations may also be provided.
- example mechanisms are described for a pTAG and an sTAG. Some of the example mechanisms may be applied to configurations with multiple sTAGs.
- an eNB may initiate an RA procedure via a PDCCH order for an activated SCell.
- This PDCCH order may be sent on a scheduling cell of this SCell.
- the scheduling cell may be different than the cell that is employed for preamble transmission, and the PDCCH order may include an SCell index.
- At least a non-contention based RA procedure may be supported for SCell(s) assigned to sTAG(s).
- FIG. 9 is an example message flow in a random access process in a secondary TAG as per an aspect of an embodiment of the present invention.
- An eNB transmits an activation command 600 to activate an SCell.
- a preamble 602 (Msg 1 ) may be sent by a UE in response to a PDCCH order 601 on an SCell belonging to an sTAG.
- preamble transmission for SCells may be controlled by the network using PDCCH format 1A.
- Msg 2 message 603 (RAR: random access response) in response to the preamble transmission on the SCell may be addressed to RA-RNTI in a PCell common search space (CSS).
- Uplink packets 604 may be transmitted on the SCell in which the preamble was transmitted.
- initial timing alignment may be achieved through a random access procedure. This may involve a UE transmitting a random access preamble and an eNB responding with an initial TA command NTA (amount of timing advance) within a random access response window.
- NTA amount of timing advance
- the eNB may estimate the uplink timing from the random access preamble transmitted by the UE.
- the TA command may be derived by the eNB based on the estimation of the difference between the desired UL timing and the actual UL timing.
- the UE may determine the initial uplink transmission timing relative to the corresponding downlink of the sTAG on which the preamble is transmitted.
- the mapping of a serving cell to a TAG may be configured by a serving eNB with RRC signaling.
- the mechanism for TAG configuration and reconfiguration may be based on RRC signaling.
- the related TAG configuration may be configured for the SCell.
- an eNB may modify the TAG configuration of an SCell by removing (releasing) the SCell and adding(configuring) a new SCell (with the same physical cell ID and frequency) with an updated TAG ID.
- the new SCell with the updated TAG ID may initially be inactive subsequent to being assigned the updated TAG ID.
- the eNB may activate the updated new SCell and start scheduling packets on the activated SCell.
- the SCell may need to be removed and a new SCell may need to be added with another TAG.
- at least one RRC message for example, at least one RRC reconfiguration message, may be send to the UE to reconfigure TAG configurations by releasing the SCell and then configuring the SCell as a part of the pTAG (when an SCell is added/configured without a TAG index, the SCell may be explicitly assigned to the pTAG).
- the PCell may not change its TA group and may be a member of the pTAG.
- a PUCCH is only transmitted on the PCell (PSCell) to an eNB.
- a UE may transmit PUCCH information on one cell (PCell or PSCell) to a given eNB.
- a PUCCH on an SCell may be introduced to offload the PUCCH resource from the PCell. More than one PUCCH may be configured for example, a PUCCH on a PCell and another PUCCH on an SCell. In the example embodiments, one, two or more cells may be configured with PUCCH resources for transmitting CSI/ACK/NACK to a base station. Cells may be grouped into multiple PUCCH groups, and one or more cell within a group may be configured with a PUCCH.
- one SCell may belong to one PUCCH group.
- SCells with a configured PUCCH transmitted to a base station may be called a PUCCH SCell, and a cell group with a common PUCCH resource transmitted to the same base station may be called a PUCCH group.
- a MAC entity may have a configurable timer timeAlignmentTimer per TAG.
- the timeAlignmentTimer may be used to control how long the MAC entity considers the Serving Cells belonging to the associated TAG to be uplink time aligned.
- the MAC entity may, when a Timing Advance Command MAC control element is received, apply the Timing Advance Command for the indicated TAG; start or restart the timeAlignmentTimer associated with the indicated TAG.
- the MAC entity may, when a Timing Advance Command is received in a Random Access Response message for a serving cell belonging to a TAG and/orif the Random Access Preamble was not selected by the MAC entity, apply the Timing Advance Command for this TAG and start or restart the timeAlignmentTimer associated with this TAG. Otherwise, if the timeAlignmentTimer associated with this TAG is not running, the Timing Advance Command for this TAG may be applied and the timeAlignmentTimer associated with this TAG started. When the contention resolution is considered not successful, a timeAlignmentTimer associated with this TAG may be stopped. Otherwise, the MAC entity may ignore the received Timing Advance Command.
- a timer is running once it is started, until it is stopped or until it expires; otherwise it may not be running.
- a timer can be started if it is not running or restarted if it is running.
- a timer may be started or restarted from its initial value.
- Base stations involved in tight interworking for a certain UE may assume two different roles: a base station may either act as a master base station or as a secondary base station. In tight interworking, a UE may be connected to one master base station and one secondary base station. Mechanisms implemented in tight interworking may be extended to cover more than two base stations.
- a master base station may be an LTE eNB, which may be connected to EPC nodes (e.g. to an MME via the S1-C interface and to an S-GW via the S1-U interface), and a secondary base station may be a gNB, which may be a non-standalone node having a control plane connection via an Xx-C interface to an LTE eNB.
- a user plane for a gNB may be connected to an S-GW through an LTE eNB via an Xx-U interface between LTE eNB and gNB and an S1-U interface between LTE eNB and S-GW.
- a user plane for a gNB may be connected directly to an S-GW via an S1-U interface between gNB and S-GW.
- a master base station may be a gNB, which may be connected to NGC nodes (e.g. to a control plane core node via the NG-C interface and to a user plane core node via the NG-U interface), and a secondary base station may be an eLTE eNB, which may be a non-standalone node having a control plane connection via an Xn-C interface to a gNB.
- NGC nodes e.g. to a control plane core node via the NG-C interface and to a user plane core node via the NG-U interface
- eLTE eNB which may be a non-standalone node having a control plane connection via an Xn-C interface to a gNB.
- a user plane for an eLTE eNB may be connected to a user plane core node through a gNB via an Xn-U interface between eLTE eNB and gNB and an NG-U interface between gNB and user plane core node.
- a user plane for an eLTE eNB may be connected directly to a user plane core node via an NG-U interface between eLTE eNB and user plane core node.
- a master base station may be an eLTE eNB, which may be connected to NGC nodes (e.g. to a control plane core node via the NG-C interface and to a user plane core node via the NG-U interface), and a secondary base station may be a gNB, which may be a non-standalone node having a control plane connection via an Xn-C interface to an eLTE eNB.
- NGC nodes e.g. to a control plane core node via the NG-C interface and to a user plane core node via the NG-U interface
- a secondary base station may be a gNB, which may be a non-standalone node having a control plane connection via an Xn-C interface to an eLTE eNB.
- a user plane for a gNB may be connected to a user plane core node through an eLTE eNB via an Xn-U interface between eLTE eNB and gNB and an NG-U interface between eLTE eNB and user plane core node.
- a user plane for a gNB may be connected directly to a user plane core node via an NG-U interface between gNB and user plane core node.
- FIG. 12A , FIG. 12B , and FIG. 12C are example diagrams for radio protocol structures of tight interworking bearers as per an aspect of an embodiment of the present invention.
- an LTE eNB may be a master base station, and a gNB may be a secondary base station.
- a gNB may be a master base station, and an eLTE eNB may be a secondary base station.
- an eLTE eNB may be a master base station, and a gNB may be a secondary base station.
- the radio protocol architecture that a particular bearer uses may depend on how the bearer is setup.
- NR RRC may be located in master base station, and SRBs may be configured as an MCG bearer type and may use the radio resources of the master base station.
- Tight interworking may also be described as having at least one bearer configured to use radio resources provided by the secondary base station. Tight interworking may or may not be configured/implemented in example embodiments of the invention.
- the UE may be configured with two MAC entities: one MAC entity for master base station, and one MAC entity for secondary base station.
- the configured set of serving cells for a UE may comprise of two subsets: the Master Cell Group (MCG) containing the serving cells of the master base station, and the Secondary Cell Group (SCG) containing the serving cells of the secondary base station.
- MCG Master Cell Group
- SCG Secondary Cell Group
- a SCG For a SCG, one or more of the following may be applied: at least one cell in the SCG has a configured UL CC and one of them, named PSCell (or PCell of SCG, or sometimes called PCell), is configured with PUCCH resources; when the SCG is configured, there may be at least one SCG bearer or one split bearer; upon detection of a physical layer problem or a random access problem on a PSCell, or the maximum number of (NR) RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: a RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of the SCG are stopped, a master base station may be informed by the UE of a SCG failure type, for split bearer, the DL data transfer over the master base station is maintained; the RLC AM bearer may be configured for the split bearer; like PCell, PSCell may
- the master base station may maintain the RRM measurement configuration of the UE and may, (e.g, based on received measurement reports, traffic conditions, or bearer types), decide to ask a secondary base station to provide additional resources (serving cells) for a UE; upon receiving a request from the master base station, a secondary base station may create a container that may result in the configuration of additional serving cells for the UE (or decide that it has no resource available to do so); for UE capability coordination, the master base station may provide (part of) the AS configuration and the UE capabilities to the secondary base station; the master base station and the secondary base station may exchange information about a UE configuration by employing of RRC containers (inter-node messages) carried in Xn or Xx messages; the secondary base station may initiate a reconfiguration of its existing serving cells (e.g., PUCCH towards the secondary base station); the secondary base station may decide which cell is the PSCell
- FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenarios as per an aspect of an embodiment of the present invention.
- the full protocol stack e.g. NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY
- CU Central Unit
- DU Distributed Unit
- the CU-DU interface e.g. Fs interface connecting CU and DU may be ideal or non-ideal.
- Fs-C may provide a control plane connection over Fs interface
- Fs-U may provide a user plane connection over Fs interface.
- different functional split options between CU and DUs may be possible by locating different protocol layers (RAN functions) in CU and DU.
- the functional split may support flexibility to move RAN functions between CU and DU depending on service requirements and/or network environments.
- the functional split option may change during operation after Fs interface setup procedure, or may change only in Fs setup procedure (i.e. static during operation after Fs setup procedure).
- FIG. 14 is an example diagram for different functional split option examples of the centralized gNB deployment scenario as per an aspect of an embodiment of the present invention.
- an NR RRC may be in CU, and NR PDCP, NR RLC, NR MAC, NR PHY, and RF may be in DU.
- an NR RRC and NR PDCP may be in CU, and NR RLC, NR MAC, NR PHY, and RF may be in DU.
- an NR RRC, NR PDCP, and partial function of NR RLC may be in CU, and the other partial function of NR RLC, NR MAC, NR PHY, and RF may be in DU.
- an NR RRC, NR PDCP, and NR RLC may be in CU, and NR MAC, NR PHY, and RF may be in DU.
- an NR RRC, NR PDCP, NR RLC, and partial function of NR MAC may be in CU, and the other partial function of NR MAC, NR PHY, and RF may be in DU.
- an NR RRC, NR PDCP, NR RLC, and NR MAC may be in CU, and NR PHY and RF may be in DU.
- an NR RRC, NR PDCP, NR RLC, NR MAC, and partial function of NR PHY may be in CU, and the other partial function of NR PHY and RF may be in DU.
- an NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY may be in CU, and RF may be in DU.
- the functional split may be configured per CU, per DU, per UE, per bearer, per slice, or with other granularities.
- a CU may have a fixed split, and DUs may be configured to match the split option of CU.
- each DU may be configured with a different split, and a CU may provide different split options for different DUs.
- a gNB (CU and DU) may provide different split options for different UEs.
- per bearer split different split options may be utilized for different bearer types.
- per slice splice different split options may be applied for different slices.
- the new radio access network may support different network slices, which may allow differentiated treatment customized to support different service requirements with end to end scope.
- the new RAN may provide a differentiated handling of traffic for different network slices that may be pre-configured, and may allow a single RAN node to support multiple slices.
- the new RAN may support selection of a RAN part for a given network slice, by one or more slice ID(s) or NSSAI(s) provided by a UE or a NGC (e.g. NG CP).
- the slice ID(s) or NSSAI(s) may identify one or more of pre-configured network slices in a PLMN.
- a UE may provide a slice ID and/or an NSSAI, and a RAN node (e.g. gNB) may use the slice ID or the NSSAI for routing an initial NAS signaling to an NGC control plane function (e.g. NG CP).
- an NGC control plane function e.g. NG CP
- a RAN node may send a NAS signaling to a default NGC control plane function.
- the UE may provide a temporary ID for a slice identification, which may be assigned by the NGC control plane function, to enable a RAN node to route the NAS message to a relevant NGC control plane function.
- the new RAN may support resource isolation between slices. The RAN resource isolation may be achieved by avoiding that shortage of shared resources in one slice breaks a service level agreement for another slice.
- the amount of data traffic carried over cellular networks is expected to increase for many years to come.
- the number of users/devices is increasing and each user/device accesses an increasing number and variety of services, e.g. video delivery, large files, images.
- This requires not only high capacity in the network, but also provisioning very high data rates to meet customers' expectations on interactivity and responsiveness. More spectrum is therefore needed for cellular operators to meet the increasing demand.
- Listen-before-talk may be implemented for transmission in an LAA cell.
- equipment may apply a clear channel assessment (CCA) check before using the channel.
- CCA clear channel assessment
- the CCA utilizes at least energy detection to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear, respectively.
- European and Japanese regulations mandate the usage of LBT in the unlicensed bands.
- carrier sensing via LBT may be one way for fair sharing of the unlicensed spectrum.
- discontinuous transmission on an unlicensed carrier with limited maximum transmission duration may be enabled. Some of these functions may be supported by one or more signals to be transmitted from the beginning of a discontinuous LAA downlink transmission.
- Channel reservation may be enabled by the transmission of signals, by an LAA node, after gaining channel access via a successful LBT operation, so that other nodes that receive the transmitted signal with energy above a certain threshold sense the channel to be occupied.
- Functions that may need to be supported by one or more signals for LAA operation with discontinuous downlink transmission may include one or more of the following: detection of the LAA downlink transmission (including cell identification) by UEs; time & frequency synchronization of UEs.
- DL LAA design may employ subframe boundary alignment according to LTE-A carrier aggregation timing relationships across serving cells aggregated by CA. This may not imply that the eNB transmissions can start only at the subframe boundary.
- LAA may support transmitting PDSCH when not all OFDM symbols are available for transmission in a subframe according to LBT. Delivery of necessary control information for the PDSCH may also be supported.
- LBT procedure may be employed for fair and friendly coexistence of LAA with other operators and technologies operating in unlicensed spectrum.
- LBT procedures on a node attempting to transmit on a carrier in unlicensed spectrum require the node to perform a clear channel assessment to determine if the channel is free for use.
- An LBT procedure may involve at least energy detection to determine if the channel is being used. For example, regulatory requirements in some regions, e.g., in Europe, specify an energy detection threshold such that if a node receives energy greater than this threshold, the node assumes that the channel is not free. While nodes may follow such regulatory requirements, a node may optionally use a lower threshold for energy detection than that specified by regulatory requirements.
- LBT mechanisms may be implemented.
- no LBT procedure may be performed by the transmitting entity.
- Category 2 e.g. LBT without random back-off
- the duration of time that the channel is sensed to be idle before the transmitting entity transmits may be deterministic.
- Category 3 e.g. LBT with random back-off with a contention window of fixed size
- the LBT procedure may have the following procedure as one of its components.
- the transmitting entity may draw a random number N within a contention window.
- the size of the contention window may be specified by the minimum and maximum value of N.
- the size of the contention window may be fixed.
- the random number N may be employed in the LBT procedure to determine the duration of time that the channel is sensed to be idle before the transmitting entity transmits on the channel.
- Category 4 e.g. LBT with random back-off with a contention window of variable size
- the transmitting entity may draw a random number N within a contention window.
- the size of contention window may be specified by the minimum and maximum value of N.
- the transmitting entity may vary the size of the contention window when drawing the random number N.
- the random number N is used in the LBT procedure to determine the duration of time that the channel is sensed to be idle before the transmitting entity transmits on the channel.
- LAA may employ uplink LBT at the UE.
- the UL LBT scheme may be different from the DL LBT scheme (e.g. by using different LBT mechanisms or parameters) for example, since the LAA UL is based on scheduled access which affects a UE's channel contention opportunities.
- Other considerations motivating a different UL LBT scheme include, but are not limited to, multiplexing of multiple UEs in a single subframe.
- a DL transmission burst may be a continuous transmission from a DL transmitting node with no transmission immediately before or after from the same node on the same CC.
- An UL transmission burst from a UE perspective may be a continuous transmission from a UE with no transmission immediately before or after from the same UE on the same CC.
- UL transmission burst is defined from a UE perspective.
- an UL transmission burst may be defined from an eNB perspective.
- DL transmission burst(s) and UL transmission burst(s) on LAA may be scheduled in a TDM manner over the same unlicensed carrier.
- an instant in time may be part of a DL transmission burst or an UL transmission burst.
- a base station may consider radio resource condition and traffic status to configure wireless device control parameters, resource configuration parameters, and/or cell configuration parameters.
- a base station central unit configures wireless device control parameters
- a base station distributed unit may monitor radio resource condition and traffic status of the distributed unit.
- a base station CU may have less information of lower layer radio condition (e.g. physical layer, MAC layer, RLC layer, and/or the like).
- lower layer radio condition e.g. physical layer, MAC layer, RLC layer, and/or the like.
- the lack of lower layer radio condition and/or status information may cause inappropriate configurations, which may decrease cellular system performance.
- the inappropriate configuration may cause increased call dropping ratio, packet error rate, and/or packet transmission delay, and further may decrease communication reliability and/or increase data transmission latency.
- Example implementation of embodiments may support a base station central unit to consider lower layer radio condition information and/or traffic status of cells.
- a distributed unit may transmit a radio link state information for a wireless device to a central unit (CU).
- the radio link state information may comprise one or more indications indicating that the wireless device may experience a radio link failure and/or that the distributed radio access network entity may lose a connection with the wireless device.
- the central unit may determine a radio link failure of the wireless device at least based on one or more elements of the radio link state information, and/or may determine to release a wireless device context of the wireless device.
- Example implementation of embodiments may increase communication reliability and/or reduce data transmission latency of wireless communication systems.
- a cell may be operated with one or more beams employing a multi-antenna system, as shown in FIG. 27 .
- a beam may have a spatial direction, and/or may cover a part of a cell coverage area.
- a combination of one or more beam spatial areas may form a cell coverage.
- a beam transmitting a synchronization signal and/or receiving a signal from a wireless device may be swept over a cell coverage area in a predetermined way.
- a synchronization signal index, a synchronization signal scheduling information, and/or a synchronization signal sequence information may be used to identify a swept beam.
- one or more beams may be managed via a set of L1/L2 procedures to acquire and maintain a set of TRP(s)(Transmission Reception Point) and/or UE beams that may be used for DL and UL transmission/reception, which may include at least following aspects: Beam determination (for TRP(s) or UE to select of its own Tx/Rx beam(s)), Beam measurement (for TRP(s) or UE to measure characteristics of received beamformed signals), Beam reporting (for UE to report information of beamformed signal(s) based on beam measurement), and/or Beam sweeping (operation of covering a spatial area, with beams transmitted and/or received during a time interval in a predetermined way).
- Beam determination for TRP(s) or UE to select of its own Tx/Rx beam(s)
- Beam measurement for TRP(s) or UE to measure characteristics of received beamformed signals
- Beam reporting for UE to report information of beamformed signal(s) based on beam measurement
- Tx/Rx beam correspondence at TRP and UE may be defined as Tx/Rx beam correspondence at TRP and UE.
- Tx/Rx beam correspondence at TRP holds if at least one of the following is satisfied: TRP may be able to determine a TRP Rx beam for the uplink reception based on UE's downlink measurement on TRP's one or more Tx beams; and/or TRP may be able to determine a TRP Tx beam for the downlink transmission based on TRP's uplink measurement on TRP's one or more Rx beams.
- Tx/Rx beam correspondence at UE may hold if at least one of the following is satisfied: UE may be able to determine a UE Tx beam for the uplink transmission based on UE's downlink measurement on UE's one or more Rx beams; UE may be able to determine a UE Rx beam for the downlink reception based on TRP's indication based on uplink measurement on UE's one or more Tx beams; and/or capability indication of UE beam correspondence related information to TRP may be supported.
- the following DL L1/L2 beam management procedures may be supported within one or multiple TRPs.
- P-1 may be used to enable UE measurement on different TRP Tx beams to support selection of TRP Tx beams/UE Rx beam(s).
- it typically may include a intra/inter-TRP Tx beam sweep from a set of different beams.
- it may include a UE Rx beam sweep from a set of different beams.
- P-2 may be used to enable UE measurement on different TRP Tx beams to possibly change inter/intra-TRP Tx beam(s). From a possibly smaller set of beams for beam refinement than in P-1.
- P-2 may be a special case of P-1.
- P-3 may be used to enable UE measurement on the same TRP Tx beam to change UE Rx beam in the case UE uses beamforming.
- At least network triggered aperiodic beam reporting may be supported under P-1, P-2, and P-3 related operations.
- the procedure based on RS for mobility purpose may be not precluded.
- Reporting information may at least include measurement quantities for N beam (s) and information indicating N DL Tx beam(s), if N ⁇ K.
- NZP non-zero power
- a UE may report N′ CRIs (CSI-RS Resource Indicator).
- a UE may be configured with the following high layer parameters for beam management.
- N ⁇ 1 reporting settings, M ⁇ 1 resource settings the links between reporting settings and resource settings may be configured in the agreed CSI measurement setting; CSI-RS based P-1 & P-2 may be supported with resource and reporting settings; and/or P-3 may be supported with or without reporting setting.
- a reporting setting at least including: information indicating selected beam(s); L1 measurement reporting; time-domain behavior, e.g. aperiodic, periodic, semi-persistent; and/or frequency-granularity if multiple frequency granularities are supported.
- a resource setting at least including: time-domain behavior, e.g. aperiodic, periodic, semi-persistent; RS type, e.g.
- NZP CSI-RS at least; at least one CSI-RS resource set, with each CSI-RS resource set having K ⁇ 1 CSI-RS resources (Some parameters of K CSI-RS resources may be the same, e.g. port number, time-domain behavior, density and periodicity if any).
- a beam reporting may be supported at least based on an alternative 1 as follow.
- UE may report information about TRP Tx Beam(s) that may be received using selected UE Rx beam set(s) where a Rx beam set may refer to a set of UE Rx beams that may be used for receiving a DL signal. It may be UE implementation issues on how to construct the Rx beam set.
- each of Rx beam in a UE Rx beam set may correspond to a selected Rx beam in each panel.
- the UE may report TRP Tx Beam(s) and an identifier of the associated UE Rx beam set per reported TX beam(s). Different TRP Tx beams reported for the same Rx beam set may be received simultaneously at the UE. Different TRP TX beams reported for different UE Rx beam set may not be possible to be received simultaneously at the UE.
- a beam reporting may be supported at least based on an alternative 2 as follow.
- UE may report information about TRP Tx Beam(s) per UE antenna group basis where UE antenna group may refer to receive UE antenna panel or subarray.
- the UE may report TRP Tx Beam(s) and an identifier of the associated UE antenna group per reported TX beam.
- Different TX beams reported for different antenna groups may be received simultaneously at the UE. Different TX beams reported for the same UE antenna group may not be possible to be received simultaneously at the UE.
- NR New Radio
- Beam failure event may occur when the quality of beam pair link(s) of an associated control channel falls low enough (e.g. comparison with a threshold, time-out of an associated timer).
- Mechanism to recover from beam failure may be triggered when beam failure occurs.
- the beam pair link may be used for convenience, and may or may not be used in specification.
- Network may configure to UE with resources for UL transmission of signals for recovery purpose. Configurations of resources may be supported where the base station may be listening from all or partial directions, e.g. random access region.
- the UL transmission/resources to report beam failure may be located in the same time instance as PRACH (resources orthogonal to PRACH resources) and/or at a time instance (configurable for a UE) different from PRACH. Transmission of DL signal may be supported for allowing the UE to monitor the beams for identifying new potential beams.
- NR may support beam management with and without beam-related indication.
- beam-related indication information pertaining to UE-side beamforming/receiving procedure used for CSI-RS-based measurement may be indicated through QCL (Quasi Co-Location) to UE.
- QCL Quadrature Co-Location
- NR may support using the same or different beams on control channel and the corresponding data channel transmissions.
- UE may be configured to monitor NR-PDCCH on M beam pair links simultaneously, where M ⁇ 1 and the maximum value of M may depend at least on UE capability.
- UE may be configured to monitor NR-PDCCH on different beam pair link(s) in different NR-PDCCH OFDM symbols.
- Parameters related to UE Rx beam setting for monitoring NR-PDCCH on multiple beam pair links may be configured by higher layer signaling or MAC CE and/or considered in the search space design.
- NR may support indication of spatial QCL assumption between an DL RS antenna port(s), and DL RS antenna port(s) for demodulation of DL control channel.
- Candidate signaling methods for beam indication for a NR-PDCCH may be MAC CE signaling, RRC signaling, DCI signaling, specification-transparent and/or implicit method, and combination of these signaling methods. Indication may not be needed for some cases.
- NR may support indication of spatial QCL assumption between DL RS antenna port(s) and DMRS antenna port(s) of DL data channel.
- Information indicating the RS antenna port(s) may be indicated via DCI (downlink grants).
- the information may indicate the RS antenna port(s) which may be QCL-ed with DMRS antenna port(s).
- Different set of DMRS antenna port(s) for the DL data channel may be indicated as QCL with different set of RS antenna port(s). Indication may not be needed for some cases.
- a CU-DU interface between CU and DU may be defined as an F1 interface.
- higher layer splits may be applicable.
- lower layer splits may also be applicable and preferable to realize enhanced performance (e.g. centralized scheduling).
- preferable option may be different between different types of transport networks (ranging from lower layer split for transport networks with lower transport latency to higher layer split for transport networks with higher transport latency).
- LTE ⁇ ->NR interworking may be based on Dual-Connectivity-like mechanisms. Such approach may not imply a particular functional split.
- the requirement that may be extrapolated by the LTE-NR tight interworking requirement may be that of allowing aggregation of PDCP functionalities, in case of split bearers.
- some possible options for the granularity of the CU/DU functional split may be per CU (each CU may a fixed split, and DUs may be configured to match this) and/or per DU (each DU may be configured with a different split.
- the choice of a DU split may depend on specific topology or backhaul support in an area). For 2 cases, one possible way on how the CU/DU decide or coordinate the split may be through configuration.
- the split may be negotiated taking into account capabilities of the two units (CU and DU), and deployment preference e.g. based on backhaul topology.
- Per CU and Per DU options may pertain to flexibility of network topology, and may be straightforward to support. Whether procedures may be required to handle the initial configuration (or O&M may be relied upon) may not be discussed during the study phase. Note that in the Per DU option, one CU may need to support different split levels in different interfaces, which may not the case in the Per CU option. Further granularity (Per UE, Per bearer, Per slice) may require analysis and justification based on QoS and latency requirements. Note that the Per UE, Per bearer and Per slice options may imply that a particular instance of the interface between CU/DU may need to support simultaneously multiple granularity levels on user plane. The baseline may be CU based or DU based. If there are demands to have finer granularity (e.g. Per UE, Per bearer, Per slice), justification may be made clear first.
- dynamicity may imply that the protocol distribution and the interface between the CU and DU may need to be reconfigured. If the switching occurs in CU-DU setup procedure (F1 interface setup procedure), the interface design may not be influenced largely as the split option may not be changed during operation. If the switching occurs during operation, there may be impact on complexity of interface.
- RRM functions like Call Admission Control and Load balancing in the CU controlling multiple DUs.
- This may allow for the potential of increased efficiency in inter-cell coordination for RRM functions like the coordination of interference management, load balancing and Call Admission Control.
- that efficiency may only be realized if the CU may have reliable and accurate understanding of the current environment at the DU which may include issues beyond just radio conditions, but may include current processing capabilities, or in the case of wireless or mesh backhauling help in determining current terrestrial capacity.
- functional split Option 5, Option 6, Option 7 and Option 8 may allow for scheduling of data transmission in the CU.
- Having centralized scheduling may provide benefit particularly for interference management and coordinated transmission in multiple cells (like soft handover in UMTS, or CoMP in LTE).
- this may require the CU to have an even better understanding of the state of the DU radio conditions than for CAC and other centralized RRM functions.
- It also may require either very low latency/jitter transport or sufficiently tight coordination of timing and reception of user plane data (one solution may be the window mechanism used on the UP in UMTS), but this may be challenging particularly for lower latency use cases in NR.
- Centralization of RAN functions may have strong potential for some benefits such as reduced cost, improved scalability, more efficient inter-cell coordination for interference management as well as improved mobility in ultra-dense deployments.
- the RRC related functions may be located in the CU.
- the RRC message between the gNB and the UE may be transferred through the interface (e.g. F1 interface) between the CU and the DU.
- RRC messages may require a differentiated transport between CU and DU compared to data transport, e.g. in terms of robustness and delay.
- gNB-CU UE F1AP ID may be allocated so as to uniquely identify the UE over the F1 interface within a gNB-CU and an associated gNB-DU.
- a gNB-DU receives a gNB-CU UE F1AP ID, it may store it for the duration of the UE-associated logical F1-connection for this UE.
- the gNB-CU UE F1AP ID may be unique within the gNB-CU logical node and the associated gNB-DU logical node.
- the definition of the AP ID may be pending the decision on whether the DU can be connected to multiple CU.
- UE-associated signaling may be one or more F1AP messages associated to one UE, wherein the one or more F1AP messages may use the UE-associated logical F1-connection for association of the message to the UE in gNB-DU and gNB-CU.
- the UE-associated logical F1-connection may use the identities gNB-CU UE F1AP ID.
- the gNB-CU and gNB-DU may identify the associated UE based on the gNB-CU UE F1AP ID IE.
- the UE-associated logical F1-connection may exist before the F1 UE context is setup in gNB-DU.
- the purpose of the F1 Setup procedure may be to exchange application level data needed for the gNB-DU and the gNB-CU to correctly interoperate on the F1 interface (i.e. CU-DU interface).
- This procedure may be the first FLAP procedure triggered after the TNL association may have become operational.
- the procedure may use non-UE associated signaling.
- This procedure may erase existing application level configuration data in the two nodes and may replace it by the one received and may clear gNB-CU overload state information at the gNB-DU.
- this procedure may re-initialize the F1AP UE-related contexts and may erase related signaling connections in the two nodes like a Reset procedure would do.
- the network may configure time-repetition within one synchronization signal (SS) block, which may comprise at least PSS (Primary synchronization signal), SSS (Secondary synchronization signal), and PBCH (Physical broadcast channel), in a wide beam.
- SS synchronization signal
- the network may configure at least some of these signals and physical channels (e.g. SS Block) in multiple beams such that a UE identifies at least OFDM symbol index, slot index in a radio frame and radio frame number from an SS block.
- An RRC_INACTIVE or RRC_IDLE UE may need to assume that an SS Block may form an SS Block Set and, an SS Block Set Burst, having a given periodicity.
- the SS Block may be transmitted in multiple beams, together forming an SS Burst. If multiple SS Bursts are needed to transmit beams, these SS Bursts together may form an SS Burst Set as illustrated in FIG. 27 .
- FIG. 27 illustrates examples of different configurations of an SS Burst Set. Top: Time-repetition within one SS Burst in a wide beam. Middle: Beam-sweeping of a small number of beams using one SS Burst in the SS Burst Set. Bottom: Beam-sweeping of a larger number of beams using more than one SS Burst in the SS Burst Set to form a complete sweep.
- PSS/SSS/PBCH may be repeated to support cell selection/reselection and initial access procedures.
- TSS Transmission synchronization signal
- a gNB may broadcast PRACH configurations possibly per beam where the TSS may be utilized to imply the PRACH configuration differences.
- FIG. 28 illustrates an example of an RA procedure comprising broadcasting multiple SS blocks.
- the base station may transmit to a wireless device one or more messages comprising configuration parameters of one or more cells.
- the configuration parameters may comprise parameters of a plurality of CSI-RS signal format and/or resources.
- Configuration parameters of a CSI-RS may comprise one or more parameters indicating CSI-RS periodicity, one or more parameters indicating CSI-RS subcarriers (e.g. resource elements), one or more parameters indicating CSI-RS sequence, and/or other parameters. Some of the parameters may be combined into one or more parameters.
- a plurality of CSI-RS signals may be configured.
- the one or more message may indicate the correspondence between SS blocks and CSI-RS signals.
- the one or more messages may be RRC connection setup message, RRC connection resume message, and/or RRC connection reconfiguration message.
- a UE in RRC-Idle mode may not be configured with CSI-RS signals and may receive SS blocks and may measure a pathloss based on SS signals.
- a UE in RRC-connected mode may be configured with CSI-RS signals and may be measure pathloss based on CSI-RS signals.
- a UE in RRC inactive mode may measure the pathloss based on SS blocks, e.g. when the UE moves to a different base station that has a different CSI-RS configuration compared with the anchor base station.
- a PRACH burst may mean a set of PRACH occasions allocated consecutively in time domain, and a PRACH burst set may mean a set of PRACH bursts to enable full RX sweep.
- FIG. 29 illustrates an example of configured PRACH occasion, PRACH burst, and PRACH burst set.
- FIG. 29 illustrates an example of a RACH Occasion, RACH Burst and RACH Burst Set.
- SS blocks DL signal/channel
- PRACH occasion may comprise a set of preambles.
- the gNB may need to know which beam or set of beams it may use to send RAR and the preambles may be used to indicate that.
- NR may configure following partitioning and mappings in multi beam operation:
- the UE may detect SS-block based on DL synchronization signals and differentiate SS-blocks based on the time index.
- the transmission of PRACH preamble resource may be an indication informed by a UE to gNB of the preferred SS-block.
- the PRACH preamble resources of single PRACH occasion may correspond to specific SS-block and mapping may be done based on the SS-block index.
- FIG. 30 illustrates an example of TDM and FDM mapping of PRACH resources.
- the preambles may be divided between SS-blocks and depending on the number of SS-blocks, the available preambles per SS-block may be K/N (K preambles, N SS-blocks).
- the number of available preambles per beam may be determined by the K preambles/number of beams.
- the UE may indicate preferred SS-block but not the preferred individual DL TX beam to gNB.
- the network may configure mapping/partitioning PRACH preamble resources to SS-blocks and/or to individual beams.
- a UE may determine the used partitioning of PRACH preambles, as much as possible, e.g. based on the PRACH configuration.
- Beam-specific PRACH configurations may be configurable when a gNB uses analog RX beamforming.
- a UE sends, for example, a preamble in a beam-specific time/frequency slot associated with one or multiple SS Block transmissions
- the gNB may use the appropriate RX beamforming when receiving the preamble in that time/frequency slot and use the corresponding DL beam when transmitting the RAR.
- beam-specific PRACH configurations may allow the gNB to direct its Rx beamforming in the direction of the same beam when monitoring the associated PRACH resources.
- a UE may be under the coverage of a given DL beam or at least a subset of them in a cell. That may enable the network to send a RAR in this best DL beam and/or perform a more optimized beam sweeping procedure e.g. not transmitting the same RAR message in possible beams (e.g. transmitting the RAR in a single beam as in the figure below) as illustrated in FIG. 33 .
- NR may support the contention-free scenarios in a way to provide a dedicated RACH resource for the preamble transmission as in LTE for handover, DL data arrival, positioning and obtaining timing advance alignment for a secondary TAG.
- a UE may be configured to measure on one or more SS blocks or other RS in a neighboring cell. If one of the neighboring cell SS-block measurements triggers a handover request, the source gNB may signal a preferred beam index in a handover request to the target gNB. The target gNB in turn may provide a beam-specific dedicated RACH resource (including preamble) in the handover command.
- a distributed radio access network entity may detect one or more radio link state indications indicating that a wireless device (e.g. UE) may experience a radio link failure from the distributed radio access network entity and/or that the distributed radio access network entity may lose and/or have lost a connection with the wireless device.
- the wireless device may be configured to be served by the distributed radio access network.
- the one or more radio link state indications may be one or more events that a number of downlink packet retransmissions (e.g. RLC layer packet retransmissions) reaches a threshold number of downlink packet retransmissions.
- the one or more radio link state indications may be one or more events that the distributed radio access network entity does not receive a (periodic) channel quality indication (CQI) report from the wireless device at least for a first threshold time duration.
- the one or more radio link state indications may be one or more events that the distributed radio access network entity does not receive at least one packet from the wireless device at least for a second threshold time duration.
- the one or more radio link state indications may be one or more events that the distributed radio access network entity does not receive a (periodic) precoding matrix indicator (PMI) report and/or a (periodic) rank indicator (RI) from the wireless device at least for a third threshold time duration.
- PMI precoding matrix indicator
- RI rank indicator
- the distributed radio access network entity may receive at least one of the threshold number of downlink packet retransmissions, the first threshold time duration, the second threshold time duration, and/or the third threshold time duration from a central radio access network entity (e.g. central unit, CU, gNB-CU, and/or the like).
- a central radio access network entity e.g. central unit, CU, gNB-CU, and/or the like.
- the threshold number of downlink packet retransmissions, the first threshold time duration, the second threshold time duration, and/or the third threshold time duration may be pre-configured to the distributed radio access network entity.
- the one or more radio link state indications may be one or more physical layer link problems and/or one or more MAC/RLC layer link problems between the distributed radio access network entity and the wireless device, the problems detected by the distributed radio access network entity.
- the distributed radio access network entity may transmit, to a central radio access network entity, a first message comprising a radio link state information for the wireless device.
- the first message may be transmitted via an F1 interface between the distributed radio access network entity and the central radio access network entity.
- the first message may comprise a UE context release request message, a UE context modification required message, a UE status information message, and/or an F1 message comprising radio link state related information of the wireless device.
- the distributed radio access network entity may determine one or more elements of the first message at least based on the detecting of the one or more radio link state indications.
- the radio link state information may be associated with one or more serving cells of the distributed radio access network entity.
- the first message may further comprise one or more cell identifiers of the one or more serving cells associated with the radio link state information.
- the radio link state information may comprise at least one of: an indication indicating that a number of downlink packet retransmissions (e.g. RLC layer packet retransmissions) reaches to the threshold number of downlink packet retransmissions; an indication indicating that the distributed radio access network entity does not receive a (periodic) channel quality indication report from the wireless device at least for a first threshold time duration; an indication indicating that the distributed radio access network entity does not receive a sounding reference signal (SRS) from the wireless device at least for a certain threshold time duration; an indication indicating that the distributed radio access network entity does not receive at least one packet from the wireless device at least for the second threshold time duration; an indication indicating that the distributed radio access network entity does not receive a (periodic) precoding matrix indicator (PMI) report and/or a (periodic) rank indicator (RI) from the wireless device at least for the third threshold time duration; one or more indications indicating one or more physical layer link problems and/or one or more MAC/RLC layer link problems
- the radio link state information may comprise a radio link failure indication explicitly indicating that a radio link of the wireless device may be failed (e.g. as a result that a primary cell of the wireless device has a radio link problem (e.g. connection failure)).
- the radio link state information may comprise a connection loss indication explicitly indicating that the distributed radio access network entity may lose and/or have lost a connection with the wireless device. The distributed radio access network entity may determine that a radio link of the wireless device is failed and/or that a connection with the wireless device is lost at least based on the detecting of the one or more radio link state indications indicating that the wireless device may experience a radio link failure from the distributed radio access network entity.
- the central radio access network entity may determine a radio link failure of the wireless device and/or may determine a connection loss with the wireless device at least based on one or more elements of the first message (e.g. as a result that the radio link state information of the first message indicates that a primary cell of the wireless device has a radio link problem (e.g. connection failure)).
- the central radio access network entity may start one or more timers at least based on one or more elements of the radio link state information received via the first message.
- the central radio access network entity receives, from the distributed radio access network entity, an indication indicating that a radio link failure related situation and/or a connection loss related situation (e.g.
- the central radio access network entity may stop at least one of the one or more timers. If one or more of the one or more timers are expired, the central radio access network entity may determine a radio link failure of the wireless device and/or may determine a connection loss with the wireless device.
- the central radio access network entity may determine a radio link failure of the wireless device and/or may determine a connection loss with the wireless device at least based on detecting that the central radio access network entity (e.g. PDCP layer) does not receive at least one packet from the wireless device at least for a threshold time duration.
- the central radio access network entity e.g. PDCP layer
- the central radio access network entity may release one or more wireless device contexts comprising one or more data radio bearers, one or more bearers, one or more protocol data unit sessions (PDU sessions), one or more QoS flows, one or more security related parameters, one or more configuration parameters for the wireless device, and/or the like.
- PDU sessions protocol data unit sessions
- security related parameters one or more configuration parameters for the wireless device, and/or the like.
- the central radio access network entity may transmit, to the distributed radio access network entity, a second message configured to request a first wireless device context release for the wireless device.
- the second message may be transmitted via an F1 interface between the distributed radio access network entity and the central radio access network entity.
- the second message may comprise a UE context release command message, a UE context modification request message, and/or an F1 message indicating release of UE context of the wireless device.
- One or more elements of the second message may be determined at least based on one or more elements of the radio link state information of the first message.
- the second message may comprise a wireless device identifier (e.g.
- the cause of requesting a first wireless device context release may comprise a radio link failure of the wireless device and/or a connection loss with the wireless device.
- the distributed radio access network entity may release a first wireless device context of the wireless device.
- the first wireless device context may comprise one or more bearers (one or more logical channels), one or more security information, one or more configuration parameters associated with the wireless device, and/or the like.
- the distributed radio access network entity may transmit, to the central radio access network entity, an indication message indicating that the distributed radio access network entity released (removed) one or more of the first wireless device context in response to the second message.
- the distributed radio access network entity may request, to the central radio access network entity, releasing one or more elements of the first wireless device context for the wireless device.
- the distributed radio access network entity may transmit a cause of requesting the release.
- the cause may be at least one of a radio link failure of the wireless device and/or a connection loss with the wireless device.
- the central radio access network entity may transmit, to a core network entity (e.g. AMF, access and mobility management function), a third message configured to request a second wireless device context release for the wireless device.
- a core network entity e.g. AMF, access and mobility management function
- the third message may be a UE context release request message (wireless device context release request message).
- the third message may be transmitted via an interface between the central radio access and the core network entity (e.g. an NG interface).
- the third message may comprise a wireless device identifier (e.g.
- the cause of requesting a second wireless device context release may comprise a radio link failure of the wireless device and/or a connection loss with the wireless device.
- the core network entity may release a second wireless device context associated with an interface connection between the central radio access network entity and the core network entity for the wireless device (e.g. NG connection associated with the wireless device).
- the second wireless device context (for the wireless device) released by the core network entity may comprise one or more bearers (e.g. one or more NG bearers), one or more protocol data unit (PDU) sessions, one or more QoS flows, one or more security information, one or more configuration parameters associated with the wireless device, and/or the like.
- the core network entity may transmit, to the central radio access network entity, an indication message indicating that the core network entity released (removed) one or more of the second wireless device context as a response to the third message.
- a distributed radio access network entity may transmit, to a central radio access network entity, a first message comprising a radio link state information for a wireless device.
- the radio link state information may comprise at least one of: an indication indicating that a number of downlink packet retransmissions reaches to a threshold number of downlink packet retransmissions; an indication indicating that the distributed radio access network entity does not receive a (periodic) channel quality indication report from the wireless device at least for a first threshold time duration; an indication indicating that the distributed radio access network entity does not receive at least one packet from the wireless device at least for a second threshold time duration; and/or a radio link failure indication.
- the distributed radio access network entity may receive, from the central radio access network entity, a second message configured to request a first wireless device context release for the wireless device. The second message may be determined at least based on one or more elements of the radio link state information.
- the radio link state information may be associated with a cell identifier of a serving cell of the distributed radio access network entity.
- the central radio access network entity may determine a radio link failure of the wireless device and/or a connection lose for the wireless device at least based on one or more elements of the radio link state information received via the second message.
- the central radio access network entity may transmit, to a core network entity, a third message configured to request a second wireless device context release for the wireless device.
- the second wireless device context release may be at least associated with an interface connection between the central radio access network entity and the core network entity for the wireless device.
- the first wireless device context release may be associated with releasing a wireless device context of the wireless device.
- the wireless device context may comprise at least one of: one or more data radio bearers; one or more logical channels; one or more security configuration parameters; and/or one or more information associated with the wireless device.
- a base station may consider radio resource condition and traffic status to configure wireless device control parameters, resource configuration parameters, and/or cell configuration parameters.
- a base station central unit configures wireless device control parameters
- a base station distributed unit may monitor radio resource condition and traffic status of the distributed unit.
- a base station CU may have less information of lower layer radio condition (e.g. physical layer, MAC layer, RLC layer, and/or the like).
- lower layer radio condition e.g. physical layer, MAC layer, RLC layer, and/or the like.
- the lack of lower layer status information may cause a central unit to configure system and/or wireless device configuration parameter inappropriate for current radio and/or traffic status.
- the inappropriate configuration may cause increased call dropping ratio, packet error rate, and/or packet transmission delay, and further may decrease communication reliability and/or increase data transmission latency.
- Example implementation of embodiments may support a base station distributed unit to inform a base station central unit of lower layer radio condition information and/or traffic status of cells.
- Example implementation of embodiments may support a base station distributed unit to request a base station central unit to modify radio and/or wireless device configuration parameters (e.g. release/modify bearers) based on lower layer radio condition information and/or traffic status of cells.
- a distributed unit may request, to a central unit (CU), a distributed entity modification for a wireless device based on detecting one or more network system state and/or one or more radio network state associated with the distributed unit.
- the central unit may transmit, to the distributed unit, a response message for the request and/or may modify one or more network configurations for the wireless device at least based on the request.
- Example implementation of embodiments may increase communication reliability and/or reduce data transmission latency of wireless communication systems.
- a distributed radio access network entity may request, to a central radio access network entity (CU, central unit), a distributed entity modification for a wireless device based on detecting one or more network system state and/or one or more radio network state associated with the distributed radio access network entity.
- the central radio access network entity may transmit, to the distributed radio access network entity, a response message for the request and/or may modify one or more network configurations for the wireless device at least based on the request.
- a distributed radio access network entity may transmit, to a central radio access network entity, a first message configured to request a distributed entity modification for a wireless device.
- the first message may be transmitted via an F1 interface between the distributed radio access network entity and the central radio access network entity.
- the first message may comprise at least one of a UE context modification required message, a UE context release request message, and/or a distributed entity modification request message (e.g. gNB-DU modification request, DU modification request).
- the first message may comprise at least one of: one or more data radio bearer identifiers of one or more data radio bearers for the wireless device that the distributed radio access network requests to release, setup, and/or modify; one or more logical channel identifiers (LCIDs) of one or more logical channels for the wireless device that the distributed radio access network requests to release, setup, and/or modify; one or more beam information (e.g.
- beam identifiers of one or more beams recovered by the wireless device; one or more beam information of one or more beams serving the wireless device; one or more beam information of one or more beams released by the wireless device; an indication parameter indicating that the wireless device changed one or more serving beams; and/or the like.
- the distributed unit may request to release/modify (e.g. release part (e.g. QoS flow) of the first bearer) the first bearer via the first message.
- the first bearer may comprise a data radio bearer (DRB) of the wireless device.
- DRB data radio bearer
- one or more beam information may comprise at least one of a beam identifier, a beam index, a synchronization signal block configuration information, a reference signal configuration information, a synchronization signal block scheduling information, a reference signal configuration scheduling information, and/or the like.
- the first message may comprise at least one of an uplink radio resource measurement result measured by the distributed radio access network entity; an interference information associated with the wireless device (uplink interference measured by the distributed radio access network entity, downlink interference measured by the wireless device); an interference information associated with one or more cells of the distributed radio access network entity (uplink interference measured by the distributed radio access network entity, downlink interference measured by the wireless device); one or more radio link configuration changes; and/or the like.
- the one or more radio configuration parameters transmitted via the first message may comprise at least one of a bcch-Config (broadcast control channel configuration parameter), a pcch-Config (paging control channel configuration parameter), a rlc-Config (RLC configuration parameter), a logicalChannelConfig (logical channel configuration parameter), a macMainConfig (MAC configuration parameter), a sps-Config (semi-persistent scheduling configuration parameter), a rach-ConfigCommon (random access configuration parameter), a prach-Config (physical layer random access configuration parameter), a pdsch-ConfigCommon/a pdsch-ConfigDedicated (physical downlink shared channel configuration parameter), a pusch-ConfigCommon/a pusch-ConfigDedicated (physical uplink shared channel configuration parameter), a pucch-ConfigCommon/a pucch-ConfigDedicated (physical uplink control channel configuration parameter), a phich-Config (physical hybrid-ARQ indicator channel configuration parameter,
- the one or more radio configuration parameters may comprise at least one of a PMI report configuration parameter, an RI report configuration parameter), a schedulingRequestConfig (scheduling request configuration parameter), a soundingRS-UL-ConfigCommon/a soundingRS-UL-ConfigDedicated (sounding reference signal uplink configuration parameter), an uplinkPowerControlCommon/an uplinkPowerControlDedicated (uplink power control configuration parameter), a p-Max (uplink maximum power configuration parameter), a phr-Config (power headroom report configuration parameter), an antennaInfoCommon/an antennaInfoDedicated (antenna configuration parameter), an ul-CyclicPrefixLength (uplink cyclic prefix configuration parameter), a tdd-Config (a time division duplex configuration parameter), a system information broadcast message configuration parameter, a channel state information report configuration parameter, a DMRS-Config (demodulation reference signal configuration parameter), a synchronization signal configuration parameter, a reference signal configuration parameter, a drx-Config (schedul
- the central radio access network entity may transmit, to the distributed radio access network entity, a second message at least in response to configuring the one or more configuration parameters for the wireless device.
- the second message may be transmitted via an F1 interface between the central radio access network entity and the distributed radio access network entity.
- the second message may comprise one or more indications indicating at least one of: accepting one or more elements of the first message; rejecting one or more elements of the first message; and/or confirming one or more elements of the first message.
- the second message may comprise one or more configuration indications indicating that the distributed radio access network entity configures one or more configuration parameters for the wireless device at least based on one or more elements of the first message.
- the central radio access network entity may transmit, to the wireless device, a third message at least based on configuring the one or more configuration parameters for the wireless device at least based on one or more elements of the first message.
- the third message may comprise one or more RRC messages (radio resource control messages).
- the third message may comprise at least one of: one or more data radio bearer identifiers of one or more data radio bearers to release, setup, and/or modify; one or more logical channel identifiers (LCIDs) of one or more logical channels to release, setup, and/or modify; one or more QoS flow identifiers of one or more QoS flows to release, setup, and/or modify; one or more PDU session identifiers of one or more PDU sessions to release, setup, and/or modify; one or more beam information (e.g. beam identifiers, beam index, synchronization signal block configuration information, reference signal configuration information, and/or the like); one or more beam utilization information (e.g.
- a channel quality information, a precoding matrix indicator, a rank indicator a channel quality information, a precoding matrix indicator, a rank indicator
- an uplink radio resource measurement result measured by the distributed radio access network entity an interference information associated with the wireless device (uplink interference measured by the distributed radio access network entity, downlink interference measured by one or more wireless device); an interference information associated with one or more cells of the distributed radio access network entity (uplink interference measured by the distributed radio access network entity, downlink interference measured by one or more wireless device); one or more radio link configuration changes; and/or the like.
- a distributed radio access network entity may transmit, to a central radio access network entity, a first message configured to request a distributed entity modification for a wireless device.
- the first message may comprise at least one of: one or more data radio bearer identifiers of one or more data radio bearers to be released; one or more data radio bearer identifiers of one or more data radio bearers to be modified; one or more radio configuration parameters to be changed; one or more beam information of one or more beams recovered by the wireless device; one or more beam information of one or more beams serving the wireless device; one or more beam information of one or more beams released by the wireless device; an indication parameter indicating that the wireless device changed one or more serving beams; and/or the like.
- the distributed radio access network entity may transmit, the first message based on at least one of: a load state (PRB usage state, hardware load state, and/or the like) of the distributed radio access network entity; a radio load state of one or more cells of the distributed radio access network entity; an average uplink/downlink buffer state information of the wireless device; a time alignment timer expiration; a channel state information received from the wireless device (e.g. a channel quality information, a precoding matrix indicator, a rank indicator); an uplink measurement result by the distributed radio access network entity; an interference information associated with the wireless device; an interference information associated with one or more cells of the distributed radio access network entity; and/or one or more radio link configuration changes.
- a load state PRB usage state, hardware load state, and/or the like
- the central radio access network entity may transmit, to the wireless device, a third message comprising one or more radio resource control parameters at least based on one or more elements of the first message.
- the one or more radio resource control parameters may comprise at least one of: one or more data radio bearer identifiers of one or more data radio bearers to be released; one or more data radio bearer identifiers of one or more data radio bearers to be modified; and/or one or more radio link configuration parameters to be changed.
- the distributed radio access network entity may decode the third message, and/or may determine one or more radio link configurations at least based on one or more elements of the third message.
- the lack of lower layer status information may cause a central unit to configure system and/or wireless device configuration parameter inappropriate for current radio and/or traffic status.
- the inappropriate configuration may cause increased call dropping ratio, packet error rate, and/or packet transmission delay, and further may decrease communication reliability and/or increase data transmission latency.
- FIG. 34 is two examples of DMRS design with 4 UEs multiplexed on each DMRS symbol.
- the DMRS of 4 UEs are plotted with different patterns, respectively.
- Figure xxx considers an example with 2 DMRS symbols out of 14 orthogonal frequency-division multiplexing (OFDM) symbols.
- Top of FIG. 34 is a comb pattern used to divide resource elements (REs) in one symbol into DMRS RE groups, and a UE occupies a group of REs to transmit its DMRS. In this way, the DMRS of multiplexed UEs may be orthogonal to guarantee the accuracy of channel estimation and related measurements.
- FIG. 34 is two examples of DMRS design with 4 UEs multiplexed on each DMRS symbol.
- the DMRS of 4 UEs are plotted with different patterns, respectively.
- Figure xxx considers an example with 2 DMRS symbols out of 14 orthogonal frequency-division multiplexing (OFDM) symbols.
- DMRS 34 is a Zadoff-Chu (ZC) sequence with different cyclic shifts used to accommodate multiple UEs' DMRSs in the same OFDM symbol.
- ZC Zadoff-Chu
- CIR channel impulse response
- DMRS may be put on the first 2 OFDM symbols.
- Two set of GF UEs may share the same preamble transmission bandwidth, but different data transmission bandwidth, e.g., the preambles of both set of UEs are multiplexed in the same radio resources.
- the preamble REs that are within the bandwidth for GF UL data transmission may be reused as the reference signals for GF data demodulation.
- the preambles that are transmitted outside of GF data bandwidth may be orthogonally multiplexed with the DMRS of a GB UE. This may reduce the impact to GB UEs.
- FIG. 36 illustrate an example.
- one mini-slot contains 4 OFDM symbols and gNB configures two OFDM symbols for the preamble transmission.
- 3 OFDM symbols are contained in one mini-slot, and the preamble is configured to transmit in 1 OFDM symbol, but in larger transmission BW than the data transmission.
- a gNB may support a K-repetition of the same transport block (TB) transmission over the GF radio resource pool until certain conditions are met.
- the UE may continue the repetitions upto K times for the same TB until one of the following conditions is met: If an UL grant is successfully received for a slot/mini-slot for the same TB; the number of repetitions for that TB reaches K; and/or other termination condition of repetition may apply.
- the number of maximum repetitions, K may be a configurable parameter that may be UE-specific, and/or cell-specific.
- a mini-slot or a symbol may be a unit of the K-repetition.
- a network may configure the number of this repetition and the radio resource in advance.
- the network may assume a set of initial transmission and the repetition as one amount of the transmission.
- the network may not be required to prepare the case of only initial transmission or only repetition.
- One may call the set of initial transmission and this repetition as extended TTI. These repetitions may not be required to be contiguous in time. If transmissions are contiguous, it may allow coherent combining. If transmissions are not contiguous, it may allow time diversity.
- a gNB may fail to detect both UEs' data.
- the two UEs may retransmit the data without UL grants, the two UEs may collide again.
- hopping may be a way to solve the collision problem when radio resources are shared by multiple UEs. Hopping may randomize the collision relationship between UEs within a certain time interval, thus avoiding persistent collision. It may bring a diversity gain on the frequency domain.
- a UE-specific hopping pattern may be pre-configured by a gNB or obtained via some known UE-specific ID.
- FIG. 37 is an example of a UE-specific hopping pattern.
- the hopping pattern design may be many factors considered for the hopping pattern design, such as the number of resource units (RUs), the max number of UEs sharing the same RU, the recently used RU index, the recent hopping index or the current slot index, the information indicating recently used sequence, hopping pattern or hopping rule, etc.
- the sequence described above may be a DMRS, a spreading sequence, or a preamble sequence that may be UE-specific.
- FIG. 38 shows examples of GF resource index and configuration parameters.
- the gNB may support to switch between GF and GB UL transmissions to balance resource utilization and delay/reliability requirements of associated services.
- the GF UL transmission may be based on a semi-static resource configuration that may be beneficial to reduce latency. Such a pre-defined resource configuration may be hard to satisfy all potential services or packet sizes. The overhead may sometimes be large, and the packet size for a service, such as URLLC, may be variable. If a UE's data packet collides with other UE's packets, a re-attempt to access GF radio resources may not achieve the service requirements. In such cases, switching from GF to GB UL transmissions may be beneficial.
- FIG. 39 shows an example of uplink resource selection based on data size.
- the initial transmission on the pre-configured GF radio resources may include UE identification (ID), for example, explicit UE ID information (e.g. C-RNTI) or implicit UE information such as a DMRS cyclic shift (assuming use of ZC sequences) specific signature.
- ID UE identification
- the UE may include buffer status reporting (BSR) with the initial data transmission. If a gNB successfully decodes data transmitted by a UE and determines that the UE has remaining data to transmit (e.g. from a BSR report), the gNB may switch scheduling for UE from GF to GB UL transmissions.
- BSR buffer status reporting
- a gNB may switch scheduling for UE from GF to GB UL transmissions.
- the UL grant for subsequent data transmissions may be with CRC scrambled by the UE C-RNTI (may be determined either by explicit signaling in the initial transmission or implicitly by the DMRS cyclic shift).
- FIG. 40 is an example of UE information request and response procedure.
- One of the termination conditions for the K-repetitions may be a reception of a UL grant which schedules a UL (re)transmission for the same TB.
- a gNB may assign dedicated resources for retransmission in order to ensure the TB is delivered within the latency budget. This behavior may be classified as scheduling switching from GF to GB operation.
- a UE may need to link the received grant with the transmitted TB in order to understand which TB to be retransmitted in case there are multiple ongoing transmission processes at the UE. For these purposes, the UE and gNB may have the same notion of TB counting.
- the TB counting may not be possible if a gNB may not detect some TBs due to collisions.
- a gNB may not detect some TBs due to collisions.
- it may directly associate the DCI with a TB which is being transmitted.
- a UE may deduct that the DCI is for a particular TB by applying an implicit linkage assuming only one TB is transmitted in one transmission interval. In this case, if the interval between detected UE transmission and a grant is fixed, it may unambiguously determine which TB may be retransmitted.
- an explicit indication of the retransmitted TB may be carried by DCI. If a UE detects that a grant for one TB overlaps with transmission of another ongoing TB, the UE may assume precedence of the grant comparing to the grant-free retransmissions. If a grant is received for a new TB (e.g. for aperiodic CSI reporting) and overlaps with the GF UL transmissions, the GF transmissions may be dropped in the resources. Alternatively, a prioritization rule whether to transmit a triggered report or GF data may be introduced depending on priority of the associated services. For example, if URLLC services is assumed, then the CSI reporting may be dropped in this example.
- the physical resources may be shared among multiple UEs who may have their own unique identifiers (e.g., DMRS) used in the GF radio resource pool. Therefore, even for GF UL transmission, if the gNB has successfully received a TB, a unique PHICH may be determined.
- DMRS unique identifiers
- a sequence based signal may be used for early termination of K-repetition.
- a sequence based signal may be transmitted to inform the UE to terminate the repetition of transmission.
- the signal may be transmitted when a gNB successfully decodes a TB.
- the UE may perform a simple signal detection for the presence or absence to decide whether to continue the repetitions or not.
- the GF resource pool configuration may not be known to UEs. It may only need to be coordinated between different cells for interference coordination. If the GF resource pools are known to UEs, those may be semi-statically configured by UE-specific RRC signaling or non-UE-specific RRC signaling.
- the RRC signaling for GF radio resource configuration may include at least one or more parameters indicating GF time/frequency radio resources, DMRS parameters, a modulation and coding scheme (MCS) or equivalently a transport block size (TBS), Number of repetitions K, and/or power control parameters.
- a UE may need to know all necessary parameters for UL grant-free transmission before transmitting on the resource. For this, not only RRC signaling, but also the use of L1 signaling may be useful. For example, RRC signaling may configure the necessary parameters of GF UL transmission to the UE, and L1 signaling may adjust, modify, update, activate, and/or deactivate these parameters.
- the L1 signaling may be a PDCCH, similar to the signaling used for LTE UL semi-persistent scheduling (SPS).
- the MCS may be indicated by the UE within the grant-free data.
- the limited number of MCS levels may be pre-configured by a gNB, e.g., K bits may be used to indicate MCS of grant-free data, where K may be as small as possible.
- the number of REs used to transmit MCS indication in a resource group may be semi-statically configured.
- the NR may predefine a mapping rule between multiple time/frequency resources for UL grant-free transmission and MCSs.
- a UE may select an appropriate MCS according to a DL measurement and associated time/frequency resources to transmit UL data. In this way, UE may choose a MCS based on the channel status and increase the resource utilization.
- a GF UL transmission may be activated in different ways.
- the need for L1 activation signaling may depend on actual service types, and the dynamic activation (e.g, activation via L1 activation) may not be supported in the NR or may be configurable based on service and traffic considerations.
- both activation schemes with and without L1 activation signaling may be supported. It may be up to a gNB to configure a UE which scheme may need to be used by considering, for example, traffic pattern, latency requirements, and other possible aspects.
- a UE may transmit data with the configured time frequency radio resource after receiving L1 activation signaling from gNB. If the L1 activation is not configured, UE may start a UL transmission with the configured GF radio resource at any moment or in a certain time interval (which may be configured by RRC signaling or pre-defined) once the configuration is completed.
- the L1 activation signaling may be beneficial in combination with L1 deactivation signaling to control network resource load and utilization.
- gNB may need to know whether the UE correctly receives it.
- An acknowledgement to the L1 signaling may be transmitted from a UE to a gNB.
- L1 signalling may be useful to reconfigure the GF UL radio resource and/or one or more GF transmission parameters.
- UEs may need to check downlink control signaling periodically whether the time/frequency resources for GF is the same or not. This may increase the power consumption of UE, and the periodicity to check the downlink control signaling may need to be configurable. In an example, if time/frequency radio resource utilization is more important, the periodicity may be configured to be short like every 1 minute or every radio frame. If the power consumption is more important, the periodicity may be configured to be long like every 1 hour.
- the periodicity to check downlink control signaling may need to be allowed to be separated from the periodicity of GF UL transmission, e.g., in order to shorten the latency.
- the periodicity of GF radio resource may be less than 1 ms like 0.125 ms but the periodicity to check downlink control signaling may be 1 minute or 1 hour.
- L1 deactivation signaling may be useful for all services in order to release resources as fast as possible.
- a distributed radio access network entity may transmit, to a central radio access network entity (CU, central unit), a grant free resource utilization information of a serving cell served by the distributed radio access network entity.
- the central radio access network entity may configure and/or reconfigure one or more grant free resources at least based on the grant free resource utilization information.
- the central radio access network entity may request, to the distributed radio access network entity, a grant free resource utilization information report with an event based condition for the report and/or a periodicity to report.
- a distributed radio access network entity may be connected to a central radio access network entity.
- the two entities may be connected via an F1 interface.
- a serving cell of the distributed radio access network entity may support one or more grant free resources for one or more wireless devices.
- the one or more grant free resources may be configured by the distributed radio access network entity and/or by the central radio access network entity.
- One or more of the one or more grant free resources may be utilized for one or more types of services (e.g. selected at least based on a bearer type, a wireless device subscription type, a slice type, a URLLC wireless device type, a machine type communication wireless device type, and/or the like).
- the bearer (logical channel, data radio bearer, QoS flow, PDU session type) may be determined at least based on a QoS information of the bearer (e.g QCI, 5QI, and/or ARP values).
- the slice type may be determined at least based on a slice identifier (e.g. NSSAI, S-NSSAI, and/or the like) of a slice.
- a wireless device may have one or more slices for one or more services (e.g. vehicle communication, emergency service, mobile broadband service, push to talk service, streaming service, high priority services for high price subscribers, and/or the like).
- the central radio access network entity may determine one or more grant free resources (e.g. configured grant/SPS/configured grant type 1 or type 2/periodic resources) for the serving cell of the distributed radio access network entity, and/or may transmit, to the distributed radio access network entity, a first grant free resource configuration information associated with the determined one or more grant free resources.
- the first grant free resource configuration information may be associated with one or more types of services.
- the first grant free resource configuration information may comprise at least one of: a grant free resource scheduling information (e.g. frequency, timing, periodicity, scheduling interval, and/or the like), a type of services (e.g.
- the first grant free resource configuration information may be configured by the distributed radio access network entity.
- the central radio access network entity may transmit, to one or more wireless devices, one or more radio resource control parameters (e.g. one or more radio resource control parameters) at least based on one or more elements of the first grant free resource configuration information.
- the distributed radio access network entity may configure one or more radio configuration parameters at least based on one or more elements of the first grant free resource configuration information, and/or receive one or more packets from one or more wireless devices via one or more of the determined one or more grant free resources.
- the first grant free resource configuration information may be configured by the distributed radio access network entity.
- the distributed radio access network entity may determine/configure one or more grant free resources for the serving cell of the distributed radio access network entity, and/or may transmit, to the central radio access network entity, a second grant free resource configuration information associated with the one or more grant free resources determined/configured by the distributed radio access network entity.
- the second grant free resource configuration information may comprise at least one of: a grant free resource scheduling information (e.g. frequency, timing, periodicity, scheduling interval, and/or the like), a type of services (e.g. bearer type, slice type, and/or the like) allowed to utilize the determined/configured one or more grant free resources, a wireless device type (e.g.
- wireless device subscription type allowed to utilize the determined/configured one or more grant free resources
- a numerology configuration information e.g. which TTI is utilized for the configured one or more grant free resources
- one or more wireless device identifiers of one or more wireless devices allowed to utilize the determined/configured one or more grant free resources e.g. C-RNTI, SPSC-RNTI, IMSI, temporary wireless device identifier for a grant free resource, and/or the like
- a grant free resource configuration index e.g. C-RNTI, SPSC-RNTI, IMSI, temporary wireless device identifier for a grant free resource, and/or the like.
- the central radio access network entity may transmit, to one or more wireless devices, one or more radio resource control parameters at least based on one or more elements of the second grant free resource configuration information received from the distributed radio access network entity.
- the distributed radio access network entity may receive one or more packets from one or more wireless devices via one or more of the determined/configured one or more grant free resources.
- the central radio access network entity may transmit, to the distributed radio access network entity, a fourth message configured to request a grant free resource utilization information.
- the fourth message may be transmitted via the F1 interface.
- the fourth message may be a resource status request message.
- the fourth message may comprise at least one of: one or more cell identifiers (e.g. global cell identifier, physical cell identifier, unique cell identifier at least at the distributed radio access network entity, and/or the like) of one or more cells that the central radio access network entity requests a grant free resource utilization information for, a triggering condition of transmitting a grant free resource utilization information; and/or a reporting periodicity of reporting a grant free resource utilization information.
- cell identifiers e.g. global cell identifier, physical cell identifier, unique cell identifier at least at the distributed radio access network entity, and/or the like
- the triggering condition may comprise at least one of: a maximum grant free resource utilization level threshold (e.g. the distributed radio access network entity may transmit a grant free resource utilization information to the central radio access network entity if a grant free resource utilization level of one or more cells is same and/or higher than the maximum grant free resource utilization level threshold); a minimum grant free resource utilization level threshold (e.g. the distributed radio access network entity may transmit a grant free resource utilization information to the central radio access network entity if a grant free resource utilization level of one or more cells is same and/or lower than the maximum grant free resource utilization level threshold); a threshold number of uplink transmission collisions (e.g.
- the distributed radio access network entity may transmit a grant free resource utilization information to the central radio access network entity if a number of uplink transmission collisions of two or more wireless devices on one or more grant free resources is same and/or larger than the threshold number of uplink transmission collisions); and/or the like.
- the fourth message may further comprise a period to measure a grant free resource utilization state to determine whether one or more elements of the triggering condition are satisfied.
- the distributed radio access network entity may transmit, to the central radio access network entity, a first message comprising a grant free resource utilization information of the serving cell served by the distributed radio access network entity.
- the first message may be determined and/or transmitted at least based on one or more elements of the fourth message.
- the first message may be transmitted via the F1 interface.
- the first message may be a resource status update message.
- one or more elements of the grant free resource utilization information may be determined at least based on the period to measure a grant free resource utilization state, the period received via the fourth message.
- a first message may be triggered at least based on the triggering condition and/or the reporting periodicity associated with one or more cells of the one or more cell identifiers received via the fourth message.
- a ratio of used grant free resources of a serving cell of the distributed radio access network entity is higher than 80% (a maximum grant free resource utilization level threshold: a maximum ratio of used grant free resources)
- the distributed radio access network entity may transmit a grant free resource utilization information for the serving cell to the central radio access network entity.
- the distributed radio access network entity may transmit a grant free resource utilization information for the serving cell to the central radio access network entity.
- the grant free resource utilization information of the first message may comprise at least one of: a ratio (e.g. a percentage) of used grant free resources (e.g. a numerator for the ratio may be an amount of grant free resources utilized by one or more wireless devices among configured grant free resources, and/or a denominator for the ratio may be an amount of configured grant free resources for one or more wireless devices); a collision ratio (e.g. a collision percentage) of grant free resources (e.g.
- a numerator for the collision ratio may be an amount of grant free resources simultaneously attempted to utilize by two or more wireless devices among configured grant free resources
- a denominator for the collision ratio may be an amount of configured grant free resources for one or more wireless devices
- a denominator for the collision ratio may be an amount of grant free resources utilized by one or more wireless devices among configured grant free resources
- an attempt collision ratio e.g. an attempt collision percentage
- a numerator for the attempt collision ratio may be a number of collided transmission attempts of one or more wireless devices via grant free resources
- a denominator for the attempt collision ratio may be a number of transmission attempts of one or more wireless devices via grant free resources
- the ratio of used grant free resources, the collision ratio of grant free resources, and/or the attempt collision ratio of one or more wireless devices may be comprise an indication indicating a ratio level (e.g. high/medium/low, high/medium_high/medium/medium_low/low, and/or the like).
- the grant free resource utilization information may further comprise a numerator and/or a denominator for the ratio of used grant free resources, the collision ratio of grant free resources, the attempt collision ratio of one or more wireless devices, and/or the like.
- the grant free resource utilization information may comprise at least one of: a number of wireless devices activated to use grant free resources; an average number of wireless devices activated to use grant free resources; and/or the like.
- the grant free resource utilization information may comprise a time period to determine one or more elements of the grant free resource utilization information.
- the grant free resource utilization information may be for one or more grant free resources associated with at least one of: a grant free resource scheduling information (e.g. frequency, timing, periodicity, scheduling interval, and/or the like), a type of services (e.g. bearer type, slice type, and/or the like), a wireless device type (e.g. wireless device subscription type, a URLLC wireless device type, machine type communication wireless device type, and/or the like), a numerology configuration information (e.g. which TTI is utilized for the configured one or more grant free resources), one or more wireless device identifiers of one or more wireless devices (e.g. C-RNTI, SPSC-RNTI, IMSI, temporary wireless device identifier for a grant free resource, and/or the like), a grant free resource configuration index, one or more beams to support the one or more grant free resources, and/or the like.
- a grant free resource scheduling information e.g. frequency, timing, periodicity, scheduling interval, and/or the like
- a type of services
- the distributed radio access network entity may transmit, to the central radio access network entity, a grant free resource configuration shift indication indicating that the distributed radio access network entity shifts a grant free resource configuration (e.g. grant free resource scheduling configuration) for one or more wireless device to another grant free resource configuration.
- the grant free resource configuration shift indication may comprise one or more grant free resource configuration index and/or one or more wireless device identifiers of one or more wireless devices associated with the grant free resource configuration shift indication.
- the central radio access network entity may configure one or more grant free resources of the serving cell of the distributed radio access network entity at least based on one or more elements of the grant free resource utilization information received via the first message.
- the central radio access network entity may decide to increase an amount of grant free resources for the first service type in the first serving cell, may reschedule (increase) grant free resources for the first service type, and/or may transmit the rescheduled grant free resource configuration information to the distributed radio access network entity and/or one or more associated wireless devices. In this case (i.e.
- the central radio access network entity may decide to decrease a number of wireless devices allowed to utilize the grant free resources, may reconfigure a list of wireless devices allowed to utilize the grant free resources, and/or may transmit the list to the distributed radio access network entity.
- the central radio access network entity may transmit, to the distributed radio access network entity, a second message comprising a third grant free resource configuration information associated with the one or more grant free resources configured at least based on one or more elements of the grant free resource utilization information received via the first message.
- the third grant free resource configuration information may comprise at least one of: a grant free resource scheduling information (e.g. frequency, timing, periodicity, scheduling interval, and/or the like), a type of services (e.g. bearer type, slice type, and/or the like) allowed to utilize the determined one or more grant free resources, a wireless device type (e.g.
- wireless device subscription type allowed to utilize the determined one or more grant free resources
- a numerology configuration information e.g. which TTI is utilized for the determined one or more grant free resources
- one or more wireless device identifiers of one or more wireless devices allowed to utilize the determined one or more grant free resources e.g. C-RNTI, SPSC-RNTI, IMSI, temporary wireless device identifier for a grant free resource, and/or the like
- a grant free resource configuration index e.g. C-RNTI, SPSC-RNTI, IMSI, temporary wireless device identifier for a grant free resource, and/or the like.
- the third grant free resource configuration information of the second message may comprise a scheduling configuration information of an increased number of grant free resources if one or more elements of the grant free resource utilization information of the first message indicates that grant free resources assigned in the serving cell are not enough to support a requirement of wireless devices.
- the central radio access network entity may transmit, to one or more wireless devices, a third message comprising a fourth grant free resource configuration information (e.g. one or more radio resource control parameters) associated with the one or more grant free resources configured at least based on one or more elements of the grant free resource utilization information received via the first message.
- a fourth grant free resource configuration information e.g. one or more radio resource control parameters
- the distributed radio access network entity may configure one or more radio configuration parameters at least based on one or more elements of the fourth grant free resource configuration information, and/or receive one or more packets from one or more wireless devices via one or more of the one or more grant free resources configured at least based on one or more elements of the grant free resource utilization information.
- the fourth grant free resource configuration information of the third message may comprise a scheduling configuration information of a decreased number of grant free resources if one or more elements of the grant free resource utilization information of the first message indicates that grant free resources assigned in the serving cell are used less than the central radio access network entity expected.
- the central radio access network entity may transmit, to the distributed radio access network entity, at least one of: a first wireless device identifier of a first wireless device allowed to utilize one or more of the one or more grant free resources configured at least based on one or more elements of the grant free resource utilization information; and/or a wireless device specific message associated with the first wireless device.
- the wireless device specific message may comprise at least one of: one or more elements of the fourth grant free resource configuration information; and/or a grant free resource index of the one or more elements of the fourth grant free resource configuration information.
- the distributed radio access network entity may transmit, to the first wireless device at least based on one or more elements of the second message, a grant free resource activation indication indicating when the first wireless device is allowed to utilize the one or more of the one or more grant free resources configured at least based on one or more elements of the grant free resource utilization information.
- the central radio access network entity may transmit, to the first wireless device, a grant free resource activation indication indicating when the first wireless device is allowed to utilize the one or more of the one or more grant free resources configured at least based on one or more elements of the grant free resource utilization information.
- a central radio access network entity may receive, from a distributed radio access network entity, a first message comprising a grant free resource utilization information of a serving cell served by the distributed radio access network entity.
- the central radio access network entity may configure one or more grant free resources of the serving cell at least based on the grant free resource utilization information.
- the central radio access network entity may transmit, to the distributed radio access network entity, a second message comprising a first grant free resource configuration information associated with the one or more grant free resources.
- the central radio access network entity may further transmit, to a wireless device, a third message comprising a second grant free resource configuration information at least based on the first grant free resource configuration information.
- the central radio access network entity may transmit, to the distributed radio access network entity, at least one of: a first wireless device identifier of a first wireless device allowed to utilize one or more of the one or more grant free resources; and/or a wireless device specific message associated with the first wireless device allowed to utilize one or more of the one or more grant free resources.
- the wireless device specific message may comprise at least one of the second grant free resource configuration information and/or a grant free resource index of the second grant free resource configuration information.
- the distributed radio access network entity may transmit to the first wireless device, a grant free resource activation indication indicating when the first wireless device is allowed to utilize one or more of the one or more grant free resources.
- the first message may be transmitted at least based on a fourth message transmitted by the central radio access network entity to the distributed radio access network entity.
- the fourth message may be configured to request the grant free resource utilization information.
- the fourth message comprises at least one of: a triggering condition of transmitting the grant free resource utilization information; and/or a reporting periodicity of reporting the grant free resource utilization information.
- the grant free resource utilization information may comprise at least one of: a ratio of used grant free resources; a percentage of used grant free resources; a collision ratio of grant free resources (with a denominator: used GF resources and/or all GF resources); a collision ratio of access attempts of a wireless device to grant free resources; a number of access attempts of a wireless device; a grant free resource monitoring period information for one or more of the grant free resource utilization information; a number of wireless devices activated to utilize grant free resources (e.g. per beam and/or per cell); an average number of wireless devices activated to utilize grant free resources; and/or the like.
- the grant free resource configuration information may comprises at least one of a frequency information, a time information, and/or an interval information of one or more grant free resources.
- a distributed radio access network entity may be connected to a central radio access network entity.
- the two entities may be connected via an F1 interface.
- One or more licensed assisted access (LAA) cells of the distributed radio access network entity may utilize one or more unlicensed spectrums (one or more unlicensed frequency bands).
- the one or more unlicensed spectrums may be shared with one or more networks, e.g. WLAN, other LTE networks, and/or the like.
- the distributed radio access network entity may use an LBT (Listen Before Talk) function, in which the distributed radio access network entity may detect energy level from other networks on its transmission frequency before transmitting packets through the frequency. In an example, if the energy level detected is higher than a threshold, the distributed radio access network entity may not transmit packets via the frequency.
- LBT Listen Before Talk
- the central radio access network entity may transmit, to the distributed radio access network entity, a fourth message configured to request a radio resource status information of one or more licensed assisted access cells served by the distributed radio access network entity.
- the fourth message may be transmitted via the F1 interface.
- the fourth message may be a resource status request message.
- the fourth message may comprise at least one of: one or more cell identifiers (e.g.
- the central radio access network entity requests a radio resource status information for, a triggering condition of transmitting a radio resource status information; and/or a reporting periodicity of reporting a radio resource status information.
- the triggering condition may comprise at least one of: a maximum LBT Failure Ratio threshold; a minimum LBT Failure Ratio threshold; a maximum LBT Success Ratio threshold; a minimum LBT Success Ratio threshold; a maximum PRB Tried threshold; a minimum PRB Tried threshold; a maximum PRB Failed threshold; a minimum PRB Failed threshold; a maximum PRB Used threshold; a minimum PRB Used threshold; a maximum PRB Usage threshold; a minimum PRB Usage threshold; a maximum Contention Level threshold; a minimum Contention Level threshold; a maximum Average CW (contention window) threshold; a minimum Average CW threshold; a maximum Current CW threshold; a minimum Current CW threshold; an indication indicating that the distributed radio access network entity may report a radio resource status information if absence of any other technology (network) is detected; and/or the like.
- the distributed radio access network entity may transmit a radio resource status information of one or more licensed assisted access cells to the central radio access network entity. In an example, if one or more of measured results are same and/or smaller than one or more associated minimum thresholds of the triggering condition, the distributed radio access network entity may transmit a radio resource status information of one or more licensed assisted access cells to the central radio access network entity.
- the fourth message may further comprise a period to measure a radio resource status of one or more licensed assisted access cells to determine whether one or more elements of the triggering condition are satisfied.
- the distributed radio access network entity may transmit, to the central radio access network entity, a first message comprising a radio resource status information of a licensed assisted access cell (LAA cell) served by the distributed radio access network entity.
- the first message may be determined and/or transmitted at least based on one or more elements of the fourth message.
- the first message may be transmitted via the F1 interface.
- the first message may be a resource status update message.
- one or more elements of the radio resource status information may be determined at least based on the period to measure a radio resource status, the period received via the fourth message.
- the radio resource status information of the licensed assisted access cell may comprise LBT Failure Ratio, LBT Success Ratio, PRB Tried, PRB Failed, PRB Used, PRB Usage, Contention Level, Average CW, Current CW, and/or absenceOfAnyOtherTechnology for the licensed assisted access cell (LAA cell).
- the absenceOfAnyOtherTechnology may indicate absence or presence of any other network sharing a frequency band used by the licensed assisted access cell of the distributed radio access network entity.
- the LBT Failure Ratio, the LBT Success Ratio, the PRB Tried, the PRB Failed, the PRB Used, and/or the PRB Usage may be determined in the time domain and/or in the time-frequency domain.
- the time slot may be considered as used.
- PRBs frequency domain resource blocks
- the PRB may be considered as used.
- the PRB may be considered as failed.
- the Contention Level may comprise a parameter indicating a level of contention on an unlicensed spectrum of the LAA cell (e.g. high contention, low contention; high contention, medium contention, low contention; or high contention, high medium contention, medium contention, low medium contention, low contention).
- a level of contention on an unlicensed spectrum of the LAA cell e.g. high contention, low contention; high contention, medium contention, low contention; or high contention, high medium contention, medium contention, low medium contention, low contention.
- the Contention Level may be the high contention.
- the unlicensed spectrum is rarely occupied by other networks (e.g. if the failure ratio in transmission attempts by the LAA cell is lower than a threshold)
- the Contention Level may be the low contention.
- a UE may report information of PRBs failed to use because of other networks' transmission to its serving eNB.
- an eNB may consider PRBs that the eNB allocated to a UE for uplink transmission but could not receive packets through as PRBs failed in packet transmission.
- the LBT Failure Ratio may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
- the LBT Success Ratio may comprise a ratio of a number of PRBs that the LAA cell used for packet transmission or tried to use but failed because of other networks' transmissions and a number of PRBs that the LAA cell used for packet transmission during the measurement time period.
- a UE may report information of PRBs used for packet transmission to its serving eNB.
- an eNB may consider PRBs that the eNB received packets through as PRBs used for packet transmission.
- the LBT Failure Ratio may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
- the PRB Tried may comprise a ratio of a number of all PRBs available and a number of PRBs that the LAA cell used for packet transmission or tried to use but failed because of other networks' transmissions during the measurement time period. For example,
- PRB ⁇ ⁇ Tried ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ used ⁇ ⁇ for ⁇ ⁇ packet ⁇ ⁇ transmission ⁇ ( T ) + ⁇ number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ failed ⁇ ⁇ in ⁇ ⁇ packet ⁇ ⁇ transmission ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ available ⁇ ( T ) * 100 , where T is the measurement time period.
- the number of PRBs used for packet transmission or failed may be equivalent to the number of PRBs allocated for uplink transmission.
- the PRB Tried may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
- the PRB Failed may comprise a ratio of a number of all PRBs available and a number of PRBs that the LAA cell tried to use for packet transmission but failed because of other networks' transmissions during the measurement time period.
- PRB ⁇ ⁇ Failed ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ failed ⁇ ⁇ in ⁇ ⁇ packet ⁇ ⁇ transmission ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ available ⁇ ( T ) * 100 , where T is the measurement time period.
- a UE may report information of PRBs failed to use because of other networks' transmission to its serving eNB.
- an eNB may consider PRBs that the eNB allocated to a UE for uplink transmission but could not receive packets through as PRBs failed in packet transmission.
- the PRB Failed may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
- the PRB Used may comprise a ratio of a number of all PRBs available and a number of PRBs that the LAA cell used for packet transmission during the measurement time period. For example,
- PRB ⁇ ⁇ Used ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ used ⁇ ⁇ for ⁇ ⁇ packet ⁇ ⁇ transmission ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ available ⁇ ( T ) * 100 , where T is the measurement time period.
- a UE may report information of PRBs used for packet transmission to its serving eNB.
- an eNB may consider PRBs that the eNB received packets through as PRBs used for packet transmission.
- the PRB Used may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
- the PRB Usage may comprise Downlink PRB Usage and/or Uplink PRB Usage.
- the Downlink PRB Usage may comprise a ratio of a number of all PRBs available and a number of PRBs that the LAA cell used for downlink packet transmission during the measurement time period.
- Downlink ⁇ ⁇ PRB ⁇ ⁇ Usage ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ used ⁇ ⁇ for ⁇ ⁇ downlink ⁇ ⁇ packet ⁇ ⁇ transmission ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ available ⁇ ( T ) * 100 , where T is the measurement time period.
- the Uplink PRB Usage may comprise a ratio of the number of all PRBs available and the number of PRBs that the LAA cell used for uplink packet transmission or tried to use for uplink packet transmission but failed because of other networks' transmissions during the measurement time period. For example,
- Uplink ⁇ ⁇ PRB ⁇ ⁇ Usage ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ used ⁇ ⁇ for ⁇ ⁇ uplink ⁇ ⁇ packet ⁇ ⁇ transmission ⁇ ( T ) + ⁇ number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ failed ⁇ ⁇ in ⁇ ⁇ uplink ⁇ ⁇ packet ⁇ ⁇ transmission ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ PRBs ⁇ ⁇ available ⁇ ( T ) * 100 , where T is the measurement time period.
- the number of PRBs used for uplink packet transmission or failed may be equivalent to the number of PRBs allocated for uplink transmission.
- the average contention window size may be calculated by averaging (e.g. combining) all contention window sizes used in every channel access procedure for transmission during the measurement time period for each channel access priority class. For example,
- the average ⁇ ⁇ contention ⁇ ⁇ window ⁇ ⁇ size p ⁇ ( T ) sum ⁇ ⁇ of ⁇ ⁇ contention ⁇ ⁇ window ⁇ ⁇ sizes ⁇ ⁇ for ⁇ ⁇ each ⁇ ⁇ transmission p ⁇ ( T ) number ⁇ ⁇ of ⁇ ⁇ all ⁇ ⁇ transmissions p ⁇ ( T ) .
- T is the measurement time period
- the total average contention window size may be calculated by averaging all contention window sizes used in every channel access procedure for transmission for all channel access priority class during the measurement time period. For example,
- the Average CW may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions. In an example, uplink transmissions using the type 2 UL channel access procedure are excluded in calculation of the Average CW.
- the current contention window size for each channel access priority class may be a contention window size that the LAA cell is currently using for packet transmission of the channel access priority class.
- the total current contention window size may be calculated by averaging the current contention window sizes for each channel access priority class. For example,
- the Current CW may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
- uplink transmissions using the type 2 UL channel access procedure are excluded in calculation of the Current CW.
- the central radio access network entity may configure one or more network configuration parameters of the LAA cell of the distributed radio access network entity at least based on one or more elements of the radio resource status information of the LAA cell received via the first message from the distributed radio access network entity.
- the central radio access network entity may consider the unlicensed frequency of the LAA cell is highly congested. In this case, the central radio access network may redirect one or more wireless devices served via LAA cell to another cell (e.g. another LAA cell using another unlicensed frequency, and/or a cell using a licensed frequency). The central radio access network may initiate a handover of one or more of the one or more wireless device towards another cell, and/or add secondary cells for one or more of the one or more wireless devices.
- another cell e.g. another LAA cell using another unlicensed frequency, and/or a cell using a licensed frequency
- the central radio access network entity may consider that the unlicensed frequency of the LAA cell is not congested and/or has an enough capacity to support more packet transmissions. In this case, the central radio access network may allow more wireless devices to utilize the LAA cell.
- the central radio access network may transmit, to a neighboring base station, a resource status information of the LAA cell, and/or the neighboring base station may initiate a handover and/or a secondary base station addition towards the LAA cell.
- the central radio access network may also add the LAA cell as a secondary cell for other wireless devices.
- the central radio access network entity may transmit, to the distributed radio access network entity, a second message comprising one or more of the one or more network configuration parameters.
- the distributed radio access network entity may configure one or more network configuration parameters at least based on one or more elements of the second message.
- the central radio access network entity may transmit, to one or more wireless devices, a third message comprising one or more radio resource control configuration parameters at least based on the one or more network configuration parameters.
- the one or more wireless device may transmit and/or receive one or more packets via the LAA cell at least based on one or more elements of the third message.
- the one or more network configuration parameters of the second message may be to add or remove the LAA cell as a secondary cell for one or more wireless devices.
- the one or more radio resource radio resource control configuration parameters may be a command for a wireless device to add or remove the LAA cell as a secondary cell.
- the central radio access network entity may transmit, to a first radio access network entity (e.g. neighboring base station), a fifth message at least based on one or more elements of the first message and/or the radio resource status information for the LAA cell received via the first message.
- the fifth message may be configured to indicate at least one of: a load status of the licensed assisted access (LAA) cell with one or more elements of the radio resource status information (e.g. load information message and/or resource status update message); a handover request towards a cell of the first radio access network entity (e.g. handover request message); a handover request acknowledge configured to accept a handover request received by the central radio access network entity from the first radio access network entity (e.g. handover request acknowledge message); a handover preparation failure configured to reject a handover request received by the central radio access network entity from the first radio access network entity (e.g. handover preparation failure message); and/or the like.
- LAA licensed assisted access
- the fifth message may be configured to indicate at least one of:
- the fifth message may be configured to indicate at least one of: a multi (and/or dual) connectivity initiation request for one or more cells of the first radio access network entity (e.g. SgNB addition request message and/or SeNB addition request message); a multi (and/or dual) connectivity initiation request acknowledge configured to accept a multi connectivity initiation request received by the central radio access network entity from the first radio access network entity (e.g. SgNB addition request acknowledge message and/or SeNB addition request acknowledge message); a multi (and/or dual) connectivity initiation request reject configured to reject a multi connectivity initiation request received by the central radio access network entity from the first radio access network entity (e.g. SgNB addition request reject message and/or SeNB addition request reject message); and/or the like.
- a multi (and/or dual) connectivity initiation request for one or more cells of the first radio access network entity e.g. SgNB addition request message and/or SeNB addition request message
- a multi (and/or dual) connectivity initiation request acknowledge configured to accept a multi
- the fifth message may be configured to indicate at least one of: a multi (and/or dual) connectivity modification request for one or more cells of the first radio access network entity (e.g. SgNB modification request message and/or SeNB modification request message); a multi (and/or dual) connectivity modification request acknowledge configured to accept a multi connectivity modification request received by the central radio access network entity from the first radio access network entity (e.g. SgNB modification request acknowledge message and/or SeNB modification request acknowledge message); a multi (and/or dual) connectivity modification request reject configured to reject a multi connectivity modification request received by the central radio access network entity from the first radio access network entity (e.g. SgNB modification request reject message and/or SeNB modification request reject message); and/or the like.
- a multi (and/or dual) connectivity modification request for one or more cells of the first radio access network entity e.g. SgNB modification request message and/or SeNB modification request message
- a multi (and/or dual) connectivity modification request acknowledge configured to accept a multi connectivity modification request received by the central
- the fifth message may be configured to indicate at least one of: a multi (and/or dual) connectivity modification required for one or more cells of the distributed radio access network entity (e.g. SgNB modification required message and/or SeNB modification required message); a multi (and/or dual) connectivity modification confirmation configured to accept a multi connectivity modification requirement received by the central radio access network entity from the first radio access network entity (e.g. SgNB modification confirm message and/or SeNB modification confirm message); a multi (and/or dual) connectivity modification refusal configured to reject a multi connectivity modification requirement received by the central radio access network entity from the first radio access network entity (e.g. SgNB modification refuse message and/or SeNB modification refuse message); and/or the like.
- a multi (and/or dual) connectivity modification required for one or more cells of the distributed radio access network entity e.g. SgNB modification required message and/or SeNB modification required message
- a multi (and/or dual) connectivity modification confirmation configured to accept a multi connectivity modification requirement received by the central radio access network entity from the first
- the fifth message may be configured to indicate at least one of: a multi (and/or dual) connectivity release request for one or more cells of the first radio access network entity (e.g. SgNB release request message and/or SeNB release request message); a multi (and/or dual) connectivity release required for one or more cells of the distributed radio access network entity (e.g. SgNB release required message and/or SeNB release required message); a multi (and/or dual) connectivity release confirmation configured to accept a multi connectivity release requirement received by the central radio access network entity from the first radio access network entity (e.g. SgNB release confirm message and/or SeNB release confirm message); and/or the like.
- a multi (and/or dual) connectivity release request for one or more cells of the first radio access network entity e.g. SgNB release request message and/or SeNB release request message
- a multi (and/or dual) connectivity release required for one or more cells of the distributed radio access network entity e.g. SgNB release required message and/or SeNB release required message
- a central radio access network entity may receive, from a distributed radio access network entity, a first message comprising a radio resource status information of a licensed assisted access cell served by the distributed radio access network entity.
- the radio resource status information may comprise at least one of an LBT Failure Ratio, an LBT Success Ratio, a PRB Tried, a PRB Failed, a PRB Used, a PRB Usage, a Contention Level, an Average CW, a Current CW, and/or an absenceOfAnyOtherTechnology.
- the central radio access network entity may configure one or more network configuration parameters at least based on the radio resource status information.
- the central radio access network entity may transmit, to the distributed radio access network entity, a second message comprising one or more of the one or more network configuration parameters.
- the central radio access network entity may transmit, to a wireless device, a third message comprising one or more radio resource control configuration parameters at least based on the one or more network configuration parameters.
- the first message may be transmitted at least based on a fourth message transmitted by the central radio access network entity to the distributed radio access network entity.
- the fourth message may be configured to request the radio resource status information of the licensed assisted access cell.
- the fourth message may comprise at least one of: a triggering condition of transmitting the radio resource status information; and/or a periodicity of transmitting the radio resource status information.
- the central radio access network entity may transmit, to a first radio access network entity, a fifth message at least based on one or more elements of the first message.
- the fifth message may be configured to indicate at least one of: a load status of the licensed assisted access cell with one or more elements of the radio resource status information; a handover request; a handover request acknowledge configured to accept a handover request received by the central radio access network entity from the first radio access network entity; a handover preparation failure configured to reject a handover request received by the central radio access network entity from the first radio access network entity; a multi connectivity initiation request; a multi connectivity initiation request acknowledge configured to accept a multi connectivity initiation request received by the central radio access network entity from the first radio access network entity; a multi connectivity initiation request reject configured to reject a multi connectivity initiation request received by the central radio access network entity from the first radio access network entity; a multi connectivity modification request; a multi connectivity modification request acknowledge configured to accept a multi connectivity modification request received by the central radio access network entity from the first radio access network entity
- a device such as, for example, a wireless device, off-network wireless device, a base station, and/or the like, may comprise one or more processors and memory.
- the memory may store instructions that, when executed by the one or more processors, cause the device to perform a series of actions.
- Embodiments of example actions are illustrated in the accompanying figures and specification. Features from various embodiments may be combined to create yet further embodiments.
- FIG. 41 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station distributed unit may receive, from a base station central unit, packet data convergence protocol (PDCP) packets of a radio bearer established between a wireless device and the base station central unit.
- PDCP packet data convergence protocol
- the base station distributed unit may transmit, to the wireless device, the PDCP packets via the radio bearer.
- the base station distributed unit may initiate a bearer release procedure.
- the bearer release procedure may comprise transmitting, to the base station central unit, a first message.
- the first message may comprise a first data radio bearer identifier of the radio bearer to be released.
- the base station distributed unit may receive, from the base station central unit, a second message confirming release of the radio bearer by the base station central unit.
- the base station distributed unit may receive, from the base station central unit, a radio resource control message for the wireless device.
- the radio resource control message may comprise the first data radio bearer identifier of the radio bearer to be released by the wireless device.
- the base station distributed unit may transmit, to the wireless device, the radio resource control message.
- the base station distributed unit may release the radio bearer as part of the bearer release procedure. According to an embodiment, the base station distributed unit may release the radio bearer based on the first message.
- the base station distributed unit may transmit the first message based on a load status of the base station distributed unit. According to an embodiment, the base station distributed unit may transmit the first message based on a radio load status of one or more cells of the base station distributed unit. According to an embodiment, the base station distributed unit may transmit the first message based on an uplink or downlink buffer state information of the wireless device. According to an embodiment, the base station distributed unit may transmit the first message based on a time alignment timer expiration. According to an embodiment, the base station distributed unit may transmit the first message based on a channel state information received from the wireless device. According to an embodiment, the base station distributed unit may transmit the first message based on an uplink channel measurement by the base station distributed unit.
- the base station distributed unit may transmit the first message based on a radio link interference associated with the wireless device. According to an embodiment, the base station distributed unit may transmit the first message based on a radio link interference associated with one or more cells of the base station distributed unit. According to an embodiment, the base station distributed unit may transmit the first message based on one or more radio link configuration changes.
- the first message may comprise a first data radio bearer identifier of a second data radio bearer required to be released.
- the first message may comprise a second data radio bearer identifier of a second data radio bearer required to be modified.
- the first message may comprise one or more radio configuration parameters to be changed.
- the first message may comprise one or more beam information of one or more beams recovered by the wireless device.
- the first message may comprise one or more beam information of one or more beams serving the wireless device.
- the first message may comprise one or more beam information of one or more beams released by the wireless device.
- the first message may comprise an information element indicating that the wireless device changed one or more serving beams.
- the radio resource control message may further comprise one or more radio resource control parameters determined based on the first message.
- the one or more radio resource control parameters may comprise a second data radio bearer identifier of a second data radio bearer required to be modified.
- the one or more radio resource control parameters may comprise one or more radio link configuration parameters to be changed.
- the base station distributed unit may decode the radio resource control message. According to an embodiment, the base station distributed unit may determine one or more radio link configurations based on the radio resource control message.
- FIG. 42 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station central unit may transmit, to a base station distributed unit, packet data convergence protocol (PDCP) packets of a radio bearer established between a wireless device and the base station central unit.
- PDCP packet data convergence protocol
- the base station central unit may receive, from the base station distributed unit, a first message comprising a first data radio bearer identifier of the radio bearer to be released. The first message may initiate a bearer release procedure.
- the base station central unit may transmit, to the base station distributed unit, a second message confirming release of the radio bearer.
- the base station central unit may transmit, to the base station distributed unit, a radio resource control message for the wireless device.
- the radio resource control message may comprise the first data radio bearer identifier of the radio bearer to be released by the wireless device.
- the base station distributed unit may release the radio bearer as part of the bearer release procedure.
- the base station central unit may release the radio bearer based on the first message.
- the base station distributed unit may transmit the first message based on a load status of the base station distributed unit. According to an embodiment, the base station distributed unit may transmit the first message based on a radio load status of one or more cells of the base station distributed unit. According to an embodiment, the base station distributed unit may transmit the first message based on an uplink or downlink buffer state information of the wireless device. According to an embodiment, the base station distributed unit may transmit the first message based on a time alignment timer expiration. According to an embodiment, the base station distributed unit may transmit the first message based on a channel state information received from the wireless device. According to an embodiment, the base station distributed unit may transmit the first message based on an uplink channel measurement by the base station distributed unit.
- the base station distributed unit may transmit the first message based on a radio link interference associated with the wireless device. According to an embodiment, the base station distributed unit may transmit the first message based on. According to an embodiment, the base station distributed unit may transmit the first message based on a radio link interference associated with one or more cells of the base station distributed unit. According to an embodiment, the base station distributed unit may transmit the first message based on one or more radio link configuration changes.
- the first message may comprise a first data radio bearer identifier of a second data radio bearer required to be released.
- the first message may comprise a second data radio bearer identifier of a second data radio bearer required to be modified.
- the first message may comprise one or more radio configuration parameters to be changed.
- the first message may comprise one or more beam information of one or more beams recovered by the wireless device.
- the first message may comprise one or more beam information of one or more beams serving the wireless device.
- the first message may comprise one or more beam information of one or more beams released by the wireless device.
- the first message may comprise an information element indicating that the wireless device changed one or more serving beams.
- the radio resource control message may further comprise one or more radio resource control parameters determined based on the first message.
- the one or more radio resource control parameters may comprise a second data radio bearer identifier of a second data radio bearer required to be modified.
- the one or more radio resource control parameters may comprise one or more radio link configuration parameters to be changed.
- FIG. 43 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station distributed unit may receive, from a base station central unit, packet data convergence protocol (PDCP) packets of a radio bearer established between a wireless device and the base station central unit.
- PDCP packet data convergence protocol
- the base station distributed unit may transmit, to the wireless device, the PDCP packets via the radio bearer.
- the base station distributed unit may initiate a bearer release procedure.
- the bearer release procedure may comprise transmitting, to the base station central unit, a first message.
- the first message may comprise a first data radio bearer identifier of the radio bearer to be modified.
- the base station distributed unit may receive, from the base station central unit, a second message confirming modification of the radio bearer by the base station central unit.
- the base station distributed unit may receive, from the base station central unit, a radio resource control message for the wireless device.
- the radio resource control message may comprise the first data radio bearer identifier of the radio bearer to be modified by the wireless device.
- the base station distributed unit may transmit, to the wireless device, the radio resource control message.
- the second message may comprise a first information element.
- the first information element may indicate accepting one or more elements of the first message.
- the first information element may indicate rejecting one or more elements of the first message.
- the first information element may indicate confirming one or more elements of the first message.
- FIG. 44 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station distributed unit may transmit, to a base station central unit, a first message indicating a modification request of a wireless device context of a wireless device.
- the wireless device context may comprise a first data radio bearer identifier of a first data radio bearer required to be released.
- the base station distributed unit may receive, from the base station central unit and in response to the first message, a second message.
- the second message may indicate confirmation of updating the wireless device context based on the first message.
- the base station distributed unit may receive, from the base station central unit, a radio resource control message for the wireless device.
- the radio resource control message may comprise the first data radio bearer identifier of the first data radio bearer required to be released.
- the base station distributed unit may transmit, to the wireless device, the radio resource control message.
- FIG. 45 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station central unit may transmit, to a base station distributed unit, packet data convergence protocol (PDCP) packets of a radio bearer established between a wireless device and the base station central unit.
- the base station distributed unit may transmit the PDCP packets to the wireless device via the radio bearer.
- the base station central unit may receive, from the base station distributed unit, a first message.
- the first message may comprise a first data radio bearer identifier of the radio bearer to be released.
- the first message may initiate a bearer release procedure.
- the base station central unit transmit, to the base station distributed unit, a second message confirming release of the radio bearer.
- the base station central unit may transmit, to the base station distributed unit, a radio resource control message for the wireless device.
- the radio resource control message may comprise the first data radio bearer identifier of the radio bearer to be released by the wireless device.
- the base station distributed unit may transmit the radio resource control message to the wireless device.
- FIG. 46 is an example flow diagram as per as aspect of an embodiment of the present disclosure.
- a base station distributed unit may receive, from a base station central unit, packet data convergence protocol (PDCP) packets of a radio bearer established between a wireless device and the base station central unit.
- PDCP packet data convergence protocol
- the base station distributed unit may transmit, to the wireless device, the PDCP packets via a radio link.
- the base station distributed unit may detect a radio link outage of the radio link.
- the base station distributed unit may transmit, to the base station central unit, a first message.
- the first message may comprise one or more parameters.
- the one or more parameters may comprise a first information element indicating the radio link outage.
- the one or more parameters may comprise a cell identifier of a first cell associated with the radio link outage.
- the base station distributed unit may receive, from the base station central unit and in response to the one or more parameters, a second message indicating a release of a first wireless device context of the radio bearer.
- the base station distributed unit may release the first wireless device context in response to the second message.
- the one or more parameters may further comprise a second information element indicating that a number of downlink packet retransmissions reaches a threshold number of downlink packet retransmissions.
- the one or more parameters may further comprise a third information element indicating at least one failure to receive a channel status information report from the wireless device.
- the one or more parameters may further comprise a fourth information element indicating expiration of a time duration without receiving at least one transport block from the wireless device.
- the one or more parameters may further comprise a fifth information element indicating at least one failure to receive a precoding matrix indicator from the wireless device.
- the one or more parameters may further comprise a sixth information element indicating at least on failure to receive a rank indicator from the wireless device.
- the one or more parameters may further comprise a seventh information element indicating a connection loss of the wireless device.
- the base station central unit may determine a radio link failure of the wireless device based on the one or more parameters of the first message. According to an embodiment, the base station central unit may transmit, to a core network entity, a third message indicating a release request for a second wireless device context of the wireless device.
- the second wireless device context may comprise an interface connection between the base station central unit and the core network entity for the wireless device.
- the first wireless device context may comprise a data radio bearer. According to an embodiment, the first wireless device context may comprise a logical channel. According to an embodiment, the first wireless device context may comprise a security configuration parameter. According to an embodiment, the first wireless device context may comprise an information parameter associated with the wireless device.
- the base station distributed unit may transmit, to the base station central unit, a third message indicating completion of the release of the first wireless device context.
- FIG. 47 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station central unit may transmit, to a base station distributed unit, packet data convergence protocol (PDCP) packets of a radio bearer established between a wireless device and the base station central unit.
- the base station distributed unit may transmit the PDCP packets to the wireless device via a radio link.
- the base station central unit may receive, from the base station distributed unit, a first message.
- the first message may comprise one or more parameters.
- the one or more parameters may comprise a first information element indicating a radio link outage of the radio link.
- the one or more parameters may comprise a cell identifier of a first cell associated with the radio link outage.
- the base station central unit may transmit, to the base station distributed unit and in response to the one or more parameters, a second message indicating a release of a first wireless device context of the radio bearer of the wireless device.
- the base station distributed unit may release the first wireless device context in response to the second message.
- the one or more parameters may further comprise a second information element indicating that a number of downlink packet retransmissions reaches a threshold number of downlink packet retransmissions.
- the one or more parameters may further comprise a third information element indicating at least one failure to receive a channel status information report from the wireless device.
- the one or more parameters may further comprise a fourth information element indicating expiration of a time duration without receiving at least one transport block from the wireless device.
- the one or more parameters may further comprise a fifth information element indicating at least one failure to receive a precoding matrix indicator from the wireless device.
- the one or more parameters may further comprise a sixth information element indicating at least on failure to receive a rank indicator from the wireless device.
- the one or more parameters may further comprise a seventh information element indicating a connection loss of the wireless device.
- the base station central unit may determine a radio link failure of the wireless device based on the one or more parameters of the first message.
- the base station central unit may transmit, to a core network entity, a third message indicating a release request for a second wireless device context of the wireless device.
- the second wireless device context may comprise an interface connection between the base station central unit and the core network entity for the wireless device.
- the first wireless device context may comprise a data radio bearer. According to an embodiment, the first wireless device context may comprise a logical channel. According to an embodiment, the first wireless device context may comprise a security configuration parameter. According to an embodiment, the first wireless device context may comprise an information parameter associated with the wireless device.
- FIG. 48 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station distributed unit may receive, from a base station central unit, a wireless device context setup request for a wireless device.
- the base station distributed unit may configure a first bearer of the wireless device in response to the wireless device context setup request.
- the base station distributed unit may provide a radio link control layer function for the first bearer.
- the base station central unit may provide a packet data convergence protocol layer function for the first bearer.
- the base station distributed unit may detect a radio link outage of a radio link of the wireless device.
- the base station distributed unit may transmit, to the base station central unit, a first message comprising one or more parameters indicating the radio link outage.
- the base station distributed unit may receive, from the base station central unit, a second message indicating a release of a first wireless device context of the wireless device based on the one or more parameters.
- the first wireless device context may comprise the first bearer.
- the base station distributed unit may release the first wireless device context in response to the second message.
- FIG. 49 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station distributed unit may detect a radio link outage of a radio link of a wireless device.
- the base station distributed unit may transmit, to a base station central unit, a first message comprising one or more parameters indicating the radio link outage.
- the base station distributed unit may receive, from the base station central unit, a second message indicating a release of a first wireless device context of the wireless device based on the first message.
- the base station distributed unit may release the first wireless device context in response to the second message.
- the base station distributed unit may receive, from the base station central unit and in response to the one or more parameters, a second message indicating a release of a first wireless device context of the wireless device.
- the first wireless device context may comprise one or more parameters of the radio bearer.
- the base station distributed unit may release the first wireless device context in response to the second message.
- the base station central unit may transmit, to the base station distributed unit, a fourth message comprising a first configuration parameter indicating the first wireless device employs the periodic resources.
- the base station central unit may transmit, to the base station distributed unit, a fifth message comprising a second configuration parameter indicating the second wireless device employs the periodic resources.
- the base station central unit may determine that the second wireless device employs the periodic resources based on the utilization information.
- the base station distributed unit may transmit to the second wireless device, a periodic resource activation control information indicating when the second wireless device is allowed to employ the periodic resources.
- the first resource configuration parameters and the second resource configuration parameters may further comprise a size of the periodic resources. According to an embodiment, the first resource configuration parameters and the second resource configuration parameters may further comprise a frequency offset of the periodic resource.
- the base station central unit may send, to the base station distributed unit, a fourth message indicating a request for the utilization information of the periodic resources.
- the fourth message may comprise a triggering condition for transmitting the utilization information.
- the fourth message may comprise a periodicity of reporting the utilization information.
- FIG. 52 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station central unit may transmit, to a first wireless device, a first message comprising resource configuration parameters of periodic resources of a first cell.
- the base station central unit may transmit, to a base station distributed unit, a second message indicating a request for utilization information of the periodic resources.
- the base station central unit may receive, from the base station distributed unit, a third message comprising the utilization information of the periodic resources.
- the base station central unit may transmit, to the first wireless device and via the base station distributed unit, a fourth message based on the utilization information.
- the fourth message may comprise resource configuration parameters of the periodic resources.
- the utilization information may comprise a first information element indicating a ratio of utilized resources of the periodic resources to a total of the periodic resources.
- FIG. 53 is an example flow diagram as per an aspect of an embodiment of the present disclosure.
- a base station central unit may transmit, to a first wireless device and via a base station distributed unit, a first message comprising cell configuration parameters of a licensed assisted access cell.
- the cell configuration parameters may comprise a cell identifier of the licensed assisted access cell.
- the cell configuration parameters may comprise a listen-before-talk configuration parameter.
- the base station central unit may receive, from the base station distributed unit, a second message comprising resource status information of the licensed assisted access cell.
- the resource status information may comprise a value indicating listen-before-talk failure information of the licensed assisted access cell.
- the base station central unit may transmit, to a second wireless device and via the base station distributed unit, a third message based on the resource status information.
- the third message may comprise the cell configuration parameters of the licensed assisted access cell.
- Embodiments may be configured to operate as needed.
- the disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like.
- Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like.
- various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.
- a base station may communicate with a mix of wireless devices.
- Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology.
- Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies).
- a base station may comprise multiple sectors.
- this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station.
- a and B are sets and every element of A is also an element of B, A is called a subset of B.
- A is called a subset of B.
- the phrase “based on” is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
- the phrase “in response to” is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
- the phrase “depending on” is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
- the phrase “employing/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase “employing/using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.
- the term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state
- parameters may comprise one or more information objects, and an information object may comprise one or more other objects.
- an information object may comprise one or more other objects.
- parameter (IE) N comprises parameter (IE) M
- parameter (IE) M comprises parameter (IE) K
- parameter (IE) K comprises parameter (information element) J.
- N comprises K
- N comprises J.
- one or more (or at least one) message(s) comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.
- one or more (or at least one) message(s) when one or more (or at least one) message(s) indicate a value, event and/or condition, it implies that the value, event and/or condition is indicated by at least one of the one or more messages, but does not have to be indicated by each of the one or more messages.
- modules may be implemented as modules.
- a module is defined here as an element that performs a defined function and has a defined interface to other elements.
- the modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e. hardware with a biological element) or a combination thereof, all of which may be behaviorally equivalent.
- modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Script, or LabVIEWMathScript.
- modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware.
- programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs).
- Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like.
- FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device.
- HDL hardware description languages
- VHDL VHSIC hardware description language
- Verilog Verilog
Abstract
Description
-
- ASIC application-specific integrated circuit
- BPSK binary phase shift keying
- CA carrier aggregation
- CSI channel state information
- CDMA code division multiple access
- CSS common search space
- CPLD complex programmable logic devices
- CC component carrier
- CP cyclic prefix
- DL downlink
- DCI downlink control information
- DC dual connectivity
- eMBB enhanced mobile broadband
- EPC evolved packet core
- E-UTRAN evolved-universal terrestrial radio access network
- FPGA field programmable gate arrays
- FDD frequency division multiplexing
- HDL hardware description languages
- HARQ hybrid automatic repeat request
- IE information element
- LTE long term evolution
- MCG master cell group
- MeNB master evolved node B
- MIB master information block
- MAC media access control
- MAC media access control
- MME mobility management entity
- mMTC massive machine type communications
- NAS non-access stratum
- NR new radio
- OFDM orthogonal frequency division multiplexing
- PDCP packet data convergence protocol
- PDU packet data unit
- PHY physical
- PDCCH physical downlink control channel
- PHICH physical HARQ indicator channel
- PUCCH physical uplink control channel
- PUSCH physical uplink shared channel
- PCell primary cell
- PCell primary cell
- PCC primary component carrier
- PSCell primary secondary cell
- pTAG primary timing advance group
- QAM quadrature amplitude modulation
- QPSK quadrature phase shift keying
- RBG resource block groups
- RLC radio link control
- RRC radio resource control
- RA random access
- RB resource blocks
- SCC secondary component carrier
- SCell secondary cell
- Scell secondary cells
- SCG secondary cell group
- SeNB secondary evolved node B
- sTAGs secondary timing advance group
- SDU service data unit
- S-GW serving gateway
- SRB signaling radio bearer
- SC-OFDM single carrier-OFDM
- SFN system frame number
- SIB system information block
- TAI tracking area identifier
- TAT time alignment timer
- TDD time division duplexing
- TDMA time division multiple access
- TA timing advance
- TAG timing advance group
- TTI transmission time intervalTB transport block
- UL uplink
- UE user equipment
- URLLC ultra-reliable low-latency communications
- VHDL VHSIC hardware description language
- CU central unit
- DU distributed unit
- Fs-C Fs-control plane
- Fs-U Fs-user plane
- gNB next generation node B
- NGC next generation core
- NG CP next generation control plane core
- NG-C NG-control plane
- NG-U NG-user plane
- NR new radio
- NR MAC new radio MAC
- NR PHY new radio physical
- NR PDCP new radio PDCP
- NR RLC new radio RLC
- NR RRC new radio RRC
- NSSAI network slice selection assistance information
- PLMN public land mobile network
- UPGW user plane gateway
- Xn-C Xn-control plane
- Xn-U Xn-user plane
- Xx-C Xx-control plane
- Xx-U Xx-user plane
where T is the measurement time period. In an example, for uplink transmission, the number of PRBs used for packet transmission or failed may be equivalent to the number of PRBs allocated for uplink transmission. In an example, for uplink transmission, a UE may report information of PRBs failed to use because of other networks' transmission to its serving eNB. In an example, for uplink transmission, an eNB may consider PRBs that the eNB allocated to a UE for uplink transmission but could not receive packets through as PRBs failed in packet transmission. In an example, the LBT Failure Ratio may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
where T is the measurement time period. In an example, for uplink transmission, the number of PRBs used for packet transmission or failed may be equivalent to the number of PRBs allocated for uplink transmission. In an example, for uplink transmission, a UE may report information of PRBs used for packet transmission to its serving eNB. In an example, for uplink transmission, an eNB may consider PRBs that the eNB received packets through as PRBs used for packet transmission. In an example, the LBT Failure Ratio may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
where T is the measurement time period. In an example, for uplink transmission, the number of PRBs used for packet transmission or failed may be equivalent to the number of PRBs allocated for uplink transmission. In an example, the PRB Tried may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
where T is the measurement time period. In an example, for uplink transmission, a UE may report information of PRBs failed to use because of other networks' transmission to its serving eNB. In an example, for uplink transmission, an eNB may consider PRBs that the eNB allocated to a UE for uplink transmission but could not receive packets through as PRBs failed in packet transmission. In an example, the PRB Failed may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions.
where T is the measurement time period.
where T is the measurement time period. In an example, the Uplink PRB Usage may comprise a ratio of the number of all PRBs available and the number of PRBs that the LAA cell used for uplink packet transmission or tried to use for uplink packet transmission but failed because of other networks' transmissions during the measurement time period. For example,
where T is the measurement time period. In an example, for the Uplink PRB Usage, the number of PRBs used for uplink packet transmission or failed may be equivalent to the number of PRBs allocated for uplink transmission.
where T is the measurement time period, and p is the channel access priority class, e.g. p=1, 2, 3, or 4. In an example, the total average contention window size may be calculated by averaging all contention window sizes used in every channel access procedure for transmission for all channel access priority class during the measurement time period. For example,
In an example, the Average CW may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions. In an example, uplink transmissions using the
where the number of channel access priority classes may be 4. In an example, the Current CW may be provided for downlink transmissions, for uplink transmission, and/or for all transmissions including both downlink and uplink transmissions. In an example, uplink transmissions using the
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/011,363 US10608797B2 (en) | 2017-06-16 | 2018-06-18 | Distributed unit connection issue |
US16/834,591 US11588594B2 (en) | 2017-06-16 | 2020-03-30 | Releasing wireless device context based radio link outage detection by a base station distributed unit |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201762520943P | 2017-06-16 | 2017-06-16 | |
US201762520952P | 2017-06-16 | 2017-06-16 | |
US201762522276P | 2017-06-20 | 2017-06-20 | |
US201762522263P | 2017-06-20 | 2017-06-20 | |
US16/011,363 US10608797B2 (en) | 2017-06-16 | 2018-06-18 | Distributed unit connection issue |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/834,591 Continuation US11588594B2 (en) | 2017-06-16 | 2020-03-30 | Releasing wireless device context based radio link outage detection by a base station distributed unit |
Publications (2)
Publication Number | Publication Date |
---|---|
US20180368204A1 US20180368204A1 (en) | 2018-12-20 |
US10608797B2 true US10608797B2 (en) | 2020-03-31 |
Family
ID=62981311
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/011,363 Active US10608797B2 (en) | 2017-06-16 | 2018-06-18 | Distributed unit connection issue |
US16/011,371 Active 2038-06-27 US10855420B2 (en) | 2017-06-16 | 2018-06-18 | Distributed unit configuration update |
US16/011,376 Active 2038-09-05 US10594456B2 (en) | 2017-06-16 | 2018-06-18 | Distributed unit status information |
US16/819,830 Active US11381361B2 (en) | 2017-06-16 | 2020-03-16 | Utilization information of a distributed unit for a configured grant in a wireless network |
US16/834,591 Active 2038-08-05 US11588594B2 (en) | 2017-06-16 | 2020-03-30 | Releasing wireless device context based radio link outage detection by a base station distributed unit |
US17/102,746 Active 2039-01-22 US11736249B2 (en) | 2017-06-16 | 2020-11-24 | Communication of resource status information between a base station central unit and a base station distributed unit |
Family Applications After (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/011,371 Active 2038-06-27 US10855420B2 (en) | 2017-06-16 | 2018-06-18 | Distributed unit configuration update |
US16/011,376 Active 2038-09-05 US10594456B2 (en) | 2017-06-16 | 2018-06-18 | Distributed unit status information |
US16/819,830 Active US11381361B2 (en) | 2017-06-16 | 2020-03-16 | Utilization information of a distributed unit for a configured grant in a wireless network |
US16/834,591 Active 2038-08-05 US11588594B2 (en) | 2017-06-16 | 2020-03-30 | Releasing wireless device context based radio link outage detection by a base station distributed unit |
US17/102,746 Active 2039-01-22 US11736249B2 (en) | 2017-06-16 | 2020-11-24 | Communication of resource status information between a base station central unit and a base station distributed unit |
Country Status (3)
Country | Link |
---|---|
US (6) | US10608797B2 (en) |
EP (3) | EP3709763A1 (en) |
WO (1) | WO2018232399A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10772008B2 (en) * | 2018-01-11 | 2020-09-08 | Comcast Cable Communications, Llc | Cell configuration for packet duplication |
US11490272B2 (en) * | 2018-10-16 | 2022-11-01 | Parallel Wireless, Inc. | Radio access network dynamic functional splits |
Families Citing this family (90)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2458258A (en) * | 2008-02-04 | 2009-09-16 | Nec Corp | Method of controlling base station loading in a mobile communication system |
CN114745030A (en) * | 2016-09-29 | 2022-07-12 | 日本电气株式会社 | Wireless terminal, base station and method thereof |
WO2018066727A1 (en) * | 2016-10-06 | 2018-04-12 | 엘지전자 주식회사 | Method for transmitting srs in wireless communication system and terminal therefor |
EP3529935B1 (en) * | 2016-10-18 | 2022-02-23 | Telefonaktiebolaget LM Ericsson (publ) | Determining module and method performed therein for handling dual connectivity in a communication network |
KR102383906B1 (en) * | 2017-02-28 | 2022-04-08 | 삼성전자 주식회사 | Method and apparatus for recognizing users of control and data signal in wirelss cellular communication system |
EP4236616A3 (en) * | 2017-04-27 | 2023-12-13 | Mitsubishi Electric Corporation | Communication system |
US10470159B2 (en) * | 2017-05-08 | 2019-11-05 | Kt Corporation | Method and apparatus for transmitting and receiving message based on fronthaul interface |
WO2018232399A2 (en) | 2017-06-16 | 2018-12-20 | Kyungmin Park | Distributed unit configuration update |
CN109151923B (en) * | 2017-06-16 | 2023-12-12 | 华为技术有限公司 | Communication method and device |
US10980064B2 (en) * | 2017-06-16 | 2021-04-13 | Futurewei Technologies, Inc. | Radio communications using random access in wireless networks |
US20180376380A1 (en) * | 2017-06-23 | 2018-12-27 | Huawei Technologies Co., Ltd. | Exposure of capabilities of central units and distributed units in base station entities for admission control |
US10869353B2 (en) * | 2017-07-23 | 2020-12-15 | Lg Electronics Inc. | Method and apparatus for modifying radio bearer in CU-DU split scenario |
US10952273B2 (en) * | 2017-08-10 | 2021-03-16 | At&T Intellectual Property I, L.P. | Detecting and correcting radio link failures based on different usage scenarios |
US10623078B2 (en) * | 2017-08-11 | 2020-04-14 | Electronics And Telecommunications Research Institute | Method for data communications using multi-beamforming in mobile communication system and apparatus therefor |
WO2019035752A1 (en) * | 2017-08-17 | 2019-02-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Radio link management in a split ran architecture |
US10581495B2 (en) * | 2017-08-18 | 2020-03-03 | Nokia Technologies Oy | Physical layer configuration continuity during radio resource control restoration |
US10708968B2 (en) * | 2017-08-25 | 2020-07-07 | Kt Corporation | Method of controlling mobility of UE and apparatus therefor |
CN116347669A (en) | 2017-09-27 | 2023-06-27 | 三菱电机株式会社 | Communication system, base station device, and communication terminal device |
US10873866B2 (en) * | 2017-09-27 | 2020-12-22 | Electronics And Telecommunications Research Institute | Method for managing radio resources in communication system and apparatus for the same |
EP3836729B1 (en) | 2017-09-28 | 2023-05-17 | Samsung Electronics Co., Ltd. | Methods and devices for network access |
US11265946B2 (en) * | 2017-09-28 | 2022-03-01 | Samsung Electronics Co., Ltd. | Method and device for network access |
WO2019092944A1 (en) * | 2017-11-13 | 2019-05-16 | 日本電気株式会社 | Radio access network node, method therefor, and non-transitory computer-readable medium |
US11382162B2 (en) * | 2017-11-29 | 2022-07-05 | Ntt Docomo, Inc. | User apparatus |
US10784944B2 (en) * | 2018-01-09 | 2020-09-22 | Ofinno, Llc | Timing advance in beam failure recovery request transmission |
CN112469130A (en) * | 2018-04-24 | 2021-03-09 | 华为技术有限公司 | Resource allocation method and node |
US11013036B2 (en) * | 2018-06-14 | 2021-05-18 | Samsung Electronics Co., Ltd. | Method and apparatus on enhancements of NR random access for unlicensed operations |
GB2574898A (en) * | 2018-06-22 | 2019-12-25 | Nec Corp | Communication system |
CN110769510B (en) * | 2018-07-28 | 2022-07-22 | 华为技术有限公司 | Scheduling-free GF (glass fiber) resource allocation method and related equipment |
US11582616B2 (en) * | 2018-08-02 | 2023-02-14 | Samsung Electronics Co., Ltd. | Device and method for selecting cell in wireless communication system |
KR102525428B1 (en) * | 2018-08-07 | 2023-04-26 | 삼성전자 주식회사 | Method and apparatus for downlink data transmission in a wireless communication system |
CN110831248B (en) * | 2018-08-10 | 2021-08-03 | 华为技术有限公司 | Notification method, device and base station |
US11310004B2 (en) * | 2018-08-20 | 2022-04-19 | Qualcomm Incorporated | Master node transport network layer information exchange for downlink data forwarding of a secondary node terminated bearer |
US10797810B2 (en) * | 2018-08-21 | 2020-10-06 | Futurewei Technologies, Inc. | System and method for communications with multi-antenna panel devices |
JP7298683B2 (en) * | 2018-09-26 | 2023-06-27 | 富士通株式会社 | LBT monitoring failure processing method, device and system |
US11452168B2 (en) | 2018-09-26 | 2022-09-20 | Qualcomm Incorporated | Resource management, access control and mobility for grant-free uplink transmission |
US11863372B2 (en) * | 2018-09-27 | 2024-01-02 | Samsung Electronics Co., Ltd. | Apparatus and method for performing dual connectivity in wireless communication system |
EP3857731A4 (en) * | 2018-09-27 | 2022-05-25 | Nokia Technologies Oy | Beam failure recovery for serving cell |
US11722269B2 (en) * | 2018-10-03 | 2023-08-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Compressing user data transmitted between a lower layer split central unit and a radio unit using bitmap representations |
US11196470B2 (en) * | 2018-10-15 | 2021-12-07 | Blue Danube Systems, Inc. | Enhancing throughput using agile beam switching and user scheduling in cellular systems |
US11564077B2 (en) * | 2018-10-25 | 2023-01-24 | Commscope Technologies Llc | Multi-carrier radio point for a centralized radio access network |
US11297669B2 (en) * | 2018-11-02 | 2022-04-05 | Samsung Electronics Co., Ltd. | Method for transmitting control signaling in relay network, configuration method and device |
US20220053502A1 (en) * | 2018-12-27 | 2022-02-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and devices for operating with dual connectivity |
WO2020146631A1 (en) * | 2019-01-09 | 2020-07-16 | Kyungmin Park | Resource configuration for integrated access and backhaul nodes |
CN113261321A (en) * | 2019-01-10 | 2021-08-13 | 索尼集团公司 | Communication control device, communication control method, and computer program |
CN111464218B (en) * | 2019-01-18 | 2022-08-12 | 中国移动通信有限公司研究院 | Method and device for managing downlink wave beams |
CN113748715A (en) * | 2019-02-05 | 2021-12-03 | 谷歌有限责任公司 | Cell group configuration in a split base station architecture |
CN113784370A (en) * | 2019-02-15 | 2021-12-10 | 华为技术有限公司 | Mapping method, node, communication device and storage medium |
US10869336B2 (en) * | 2019-02-15 | 2020-12-15 | Qualcomm Incorporated | Random access channel access and validity procedures |
WO2020171369A1 (en) * | 2019-02-19 | 2020-08-27 | Lg Electronics Inc. | Uplink data fast transmission in cu-du split |
US11490369B2 (en) * | 2019-03-20 | 2022-11-01 | Qualcomm Incorporated | Resource management for multi-hop networks |
US11470615B2 (en) * | 2019-03-22 | 2022-10-11 | Qualcomm Incorporated | Resource availability indication |
EP3949678B1 (en) * | 2019-03-25 | 2022-10-19 | Telefonaktiebolaget Lm Ericsson (Publ) | User equipment, radio network node, computer program products, carriers and methods performed therein for handling communication |
CN111757424B (en) * | 2019-03-29 | 2022-03-22 | 大唐移动通信设备有限公司 | Sharing method and device of wireless access network |
CN111278125B (en) * | 2019-03-29 | 2023-04-18 | 维沃移动通信有限公司 | Transmission method, terminal equipment and network side equipment |
US20220039156A1 (en) * | 2019-04-04 | 2022-02-03 | Lenovo (Beijing) Limited | Determining channel statistics for clear channel assessments |
CN113711666A (en) * | 2019-04-26 | 2021-11-26 | 株式会社Ntt都科摩 | Wireless communication node |
US11265865B2 (en) * | 2019-05-01 | 2022-03-01 | Qualcomm Incorporated | Dynamic physical downlink control channel (PDCCH) resource sharing between PDCCH monitoring and PDCCH transmission in a multi-hop network |
EP3942398A4 (en) * | 2019-05-23 | 2023-04-05 | Hewlett Packard Enterprise Development LP | System and method for facilitating data request management in a network interface controller (nic) |
CN112312459B (en) * | 2019-07-29 | 2022-08-09 | 大唐移动通信设备有限公司 | Method, device and medium for reporting and processing user equipment information |
US10834618B1 (en) * | 2019-08-05 | 2020-11-10 | Sprint Communications Company L.P. | Wireless communication network access using different functionality splits for different communication services |
US20220287135A1 (en) * | 2019-08-16 | 2022-09-08 | Google Llc | Efficient use of physical and logical resources in dual connectivity |
CA3094877A1 (en) * | 2019-09-30 | 2021-03-30 | Comcast Cable Communications, Llc | Communication channel failure detection and recovery |
US11546124B2 (en) | 2019-10-11 | 2023-01-03 | Electronics And Telecommunications Research Institute | Method and apparatus for communication using fronthaul interface |
CN113132142B (en) * | 2019-12-31 | 2022-08-09 | 华为技术有限公司 | Method and device for acquiring network slice identifier |
US11190955B1 (en) | 2020-01-16 | 2021-11-30 | Sprint Communications Company L.P. | Configuration of a wireless network centralized unit (CU) and multiple wireless network distributed units (DUs) |
US11924895B2 (en) * | 2020-02-14 | 2024-03-05 | Qualcomm Incorporated | Techniques for new radio layer two relay |
EP3873019A1 (en) * | 2020-02-28 | 2021-09-01 | Siemens Aktiengesellschaft | A distributed unit for managing a plurality of radio units and a method thereof |
WO2021229136A1 (en) | 2020-05-13 | 2021-11-18 | Nokia Technologies Oy | Prolonging voice service in an active state |
US11425601B2 (en) * | 2020-05-28 | 2022-08-23 | At&T Intellectual Property I, L.P. | Pooling of baseband units for 5G or other next generation networks |
EP4193631A1 (en) * | 2020-08-06 | 2023-06-14 | Telefonaktiebolaget LM Ericsson (publ) | Methods, apparatus and machine-readable media relating to migration in a wireless communication network |
GB2597793A (en) * | 2020-08-06 | 2022-02-09 | Nec Corp | Communication system |
CN116458220A (en) * | 2020-08-06 | 2023-07-18 | 欧芬诺有限责任公司 | Uplink resource release |
US20220104215A1 (en) * | 2020-09-25 | 2022-03-31 | Qualcomm Incorporated | Enhancements for periodic resources in an integrated access and backhaul network |
EP4228360A1 (en) * | 2020-10-05 | 2023-08-16 | Lg Electronics, Inc. | Resource allocation method and device in wireless communication system |
US20220046591A1 (en) * | 2020-10-22 | 2022-02-10 | Honglei Miao | Mbs service multiplexing and resource configuration |
US11304109B1 (en) | 2020-11-10 | 2022-04-12 | Cisco Technology, Inc. | Techniques to prevent and/or minimize user equipment service disruptions in virtualized radio access network architectures |
WO2022120570A1 (en) * | 2020-12-08 | 2022-06-16 | Lenovo (Beijing) Limited | Method and apparatus for reporting configured grant resource |
US11758455B2 (en) | 2021-02-22 | 2023-09-12 | Cisco Technology, Inc. | Distributed unit (DU) failover techniques for high reliability virtualized radio access network architectures |
EP4316144A1 (en) * | 2021-03-31 | 2024-02-07 | Nokia Technologies Oy | Managing listen before talk |
WO2022223178A1 (en) * | 2021-04-19 | 2022-10-27 | Nokia Technologies Oy | Handling temporary f1-u tunnel for multicast broadcast service (mbs) mobility |
US11800404B1 (en) | 2021-05-20 | 2023-10-24 | Amazon Technologies, Inc. | Multi-tenant radio-based application pipeline processing server |
US11720425B1 (en) | 2021-05-20 | 2023-08-08 | Amazon Technologies, Inc. | Multi-tenant radio-based application pipeline processing system |
US11356500B1 (en) | 2021-06-30 | 2022-06-07 | Amazon Technologies, Inc. | Disaggregated processing of radio-based applications |
US11916999B1 (en) | 2021-06-30 | 2024-02-27 | Amazon Technologies, Inc. | Network traffic management at radio-based application pipeline processing servers |
US11889593B2 (en) | 2021-07-16 | 2024-01-30 | T-Mobile Innovations Llc | Wireless communication service over an edge data network (EDN) between a user equipment (UE) and an application server (AS) |
WO2023025384A1 (en) * | 2021-08-25 | 2023-03-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Resource status reporting |
US11539582B1 (en) | 2021-08-30 | 2022-12-27 | Amazon Technologies, Inc. | Streamlined onboarding of offloading devices for provider network-managed servers |
WO2023132766A1 (en) * | 2022-01-07 | 2023-07-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Assistance information for unlicensed spectrum in distributed architecture |
US11824943B1 (en) | 2022-06-29 | 2023-11-21 | Amazon Technologies, Inc. | Managed connectivity between cloud service edge locations used for latency-sensitive distributed applications |
US11937103B1 (en) | 2022-08-17 | 2024-03-19 | Amazon Technologies, Inc. | Enhancing availability of radio-based applications using multiple compute instances and virtualized network function accelerators at cloud edge locations |
Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100003982A1 (en) * | 2008-05-30 | 2010-01-07 | Interdigital Patent Holdings, Inc. | Method and apparatus for delivery notification of non-access stratum retransmission |
US20130136015A1 (en) * | 2010-04-30 | 2013-05-30 | Nokia Corporation | User equipment carrier activation |
US20150223282A1 (en) * | 2014-01-31 | 2015-08-06 | Qualcomm Incorporated | Procedures for managing secondary enb (senb) radio link failure (s-rlf) in dual connectivity scenarios |
US20150280905A1 (en) * | 2014-04-01 | 2015-10-01 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for detecting and correcting pdcp hyper frame number (hfn) desynchronization |
US20160029376A1 (en) * | 2013-04-05 | 2016-01-28 | Kyocera Corporation | Mobile communication system and user terminal |
US20160262118A1 (en) * | 2015-03-06 | 2016-09-08 | Samsung Electronics Co., Ltd. | Method and apparatus for performing and reporting measurements by user equipment configured with multiple carriers in mobile communication systems |
US20170013650A1 (en) * | 2014-03-20 | 2017-01-12 | Kyocera Corporation | Secondary base station, mobile station, communication control method, and master base station |
US20170141771A1 (en) * | 2013-01-11 | 2017-05-18 | International Business Machines Corporation | On-chip randomness generation |
US20170374705A1 (en) * | 2015-01-30 | 2017-12-28 | Kyocera Corporation | User terminal and base station |
US20180206275A1 (en) * | 2017-01-17 | 2018-07-19 | Cisco Technology, Inc. | System and method to facilitate stateless serving gateway operations in a network environment |
US20180227805A1 (en) * | 2017-02-03 | 2018-08-09 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting data in a mobile communication system |
US20180279358A1 (en) * | 2017-03-22 | 2018-09-27 | Ofinno Technologies, Llc | Data Multiplexing in a Wireless Device and Wireless Network |
US20180368166A1 (en) * | 2017-06-16 | 2018-12-20 | Mediatek Inc. | User equipment and method to support data preprocessing |
Family Cites Families (78)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9185621B2 (en) | 2011-04-03 | 2015-11-10 | Lg Electronics Inc. | Server for undertaking control plane in mobile communication network and method for supporting traffic detour service mobility in same server |
US9191806B2 (en) | 2012-10-23 | 2015-11-17 | Lg Electronics Inc. | Method and apparatus for retransmitting MTC group message in wireless communication system |
US20160095154A1 (en) | 2013-05-23 | 2016-03-31 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and Apparatus for Handling Connections to Multiple Radio Access Technologies |
CN105612776A (en) | 2013-07-11 | 2016-05-25 | 诺基亚通信公司 | Method and system for proxy base station |
US10211912B2 (en) | 2014-01-28 | 2019-02-19 | Mitsubishi Electric Corporation | Satellite communication system, satellite repeater, repeating method, communication network control station, satellite communication method, and method to perform data transmission |
CN106465421B (en) * | 2014-03-20 | 2020-02-21 | 松下电器(美国)知识产权公司 | Resource utilization control method and wireless device |
RU2659405C2 (en) | 2015-01-13 | 2018-07-02 | Нек Корпорейшн | Communication equipment, node of support network, system, computer program and methods for re-routing nas messages |
US11218882B2 (en) * | 2015-04-09 | 2022-01-04 | Samsung Electronics Co., Ltd. | LBT technique for frequency reuse in communication system using unlicensed band |
CN107534948B (en) * | 2015-05-14 | 2021-04-16 | 苹果公司 | Apparatus for contention-free uplink synchronization |
RU2696858C1 (en) * | 2015-09-25 | 2019-08-07 | Панасоник Интеллекчуал Проперти Корпорэйшн оф Америка | User equipment and wireless communication method |
WO2017063779A1 (en) * | 2015-10-16 | 2017-04-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Apparatus and method for discovery reference signal aligned scheduling |
CN107041000A (en) * | 2016-02-04 | 2017-08-11 | 电信科学技术研究院 | The transmission method and device of ascending control information |
WO2017138980A1 (en) | 2016-02-11 | 2017-08-17 | Intel IP Corporation | Scheduling request for standalone deployment of a system using beamforming |
WO2017164908A1 (en) | 2016-03-23 | 2017-09-28 | Intel IP Corporation | Radio link failure handling in high-frequency band networks |
US11411694B2 (en) * | 2016-03-31 | 2022-08-09 | Ntt Docomo, Inc. | Method of aperiodic signal transmission, base station, and user equipment |
US10721762B2 (en) * | 2016-03-31 | 2020-07-21 | Samsung Electronics Co., Ltd. | Methods for performing multi-subframe scheduling in enhanced LAA |
US11166282B2 (en) | 2016-04-12 | 2021-11-02 | Apple Inc. | Evolved Node-B (eNB), radio access network (RAN) central unit (RCU) and methods for radio resource control (RRC) |
CN107332646B (en) * | 2016-04-29 | 2021-05-11 | 中兴通讯股份有限公司 | HARQ-ACK sending method and device |
US10568136B2 (en) * | 2016-05-23 | 2020-02-18 | FG Innovation Company Limited | Method and apparatus for control plane and user plane transmissions in a customized C-RAN |
US11451976B2 (en) * | 2016-06-24 | 2022-09-20 | Asustek Computer Inc. | Method and apparatus for performing UE beamforming in a wireless communication system |
CN107548119B (en) * | 2016-06-24 | 2020-10-23 | 华硕电脑股份有限公司 | Method and apparatus for performing user equipment beamforming in wireless communication system |
KR102174932B1 (en) * | 2016-07-01 | 2020-11-06 | 주식회사 케이티 | Methods for transmitting and receiving a data in Dual connectivity and Apparatuses thereof |
EP3494756A4 (en) * | 2016-08-09 | 2019-07-31 | Samsung Electronics Co., Ltd. | Method and apparatus for managing user plane operation in wireless communication system |
CN110290586B (en) * | 2016-08-11 | 2020-08-07 | 华为技术有限公司 | Resource energy determination method and device and computer readable storage medium |
TWI660601B (en) | 2016-08-12 | 2019-05-21 | 聯發科技股份有限公司 | Methods of beam management in beamforming systems and user equipment |
GB2552844A (en) * | 2016-08-12 | 2018-02-14 | Nec Corp | Communication system |
US20180070327A1 (en) * | 2016-09-06 | 2018-03-08 | Qualcomm Incorporated | System and Methods for Performing an Early Radio Link Recovery Procedure on a Multi-Subscriber Identity Module Wireless Communication Device |
US10341960B2 (en) * | 2016-09-23 | 2019-07-02 | Qualcomm Incorporated | Handling transmissions after pause in eLAA |
CN107888256B (en) * | 2016-09-30 | 2022-12-02 | 中兴通讯股份有限公司 | Data transmission and receiving method, device, base station and terminal |
US10925107B2 (en) * | 2016-10-14 | 2021-02-16 | Nokia Technologies Oy | Fast activation of multi-connectivity utilizing uplink signals |
CN115297559A (en) * | 2016-10-19 | 2022-11-04 | 艾普拉控股有限公司 | Apparatus for wireless communication |
RU2719350C1 (en) * | 2016-11-04 | 2020-04-17 | Телефонактиеболагет Лм Эрикссон (Пабл) | Signaling on configuration of demodulation reference signal for transmissions in short uplink tti |
US10742522B2 (en) | 2016-11-14 | 2020-08-11 | Huawei Technologies Co., Ltd. | Creation and modification of shareable slice instances |
US10645590B2 (en) * | 2016-11-16 | 2020-05-05 | Qualcomm Incorporated | Self-contained transmissions for machine type communications |
KR102287842B1 (en) | 2016-11-27 | 2021-08-09 | 엘지전자 주식회사 | Method of deregistration in wireless communication system and apparatus therefor |
WO2018121848A1 (en) | 2016-12-28 | 2018-07-05 | Nokia Technologies Oy | Connection setup recovery for wireless networks |
WO2018128505A1 (en) | 2017-01-06 | 2018-07-12 | 엘지전자(주) | Method for transmitting and receiving data through relay in wireless communication system and apparatus therefor |
US11523319B2 (en) | 2017-01-09 | 2022-12-06 | Lg Electronics Inc. | Method for managing PDU session in wireless communication system and device for same |
US10728952B2 (en) | 2017-01-09 | 2020-07-28 | Huawei Technologies Co., Ltd. | System and methods for session management |
CN108347780B (en) * | 2017-01-25 | 2022-06-14 | 华硕电脑股份有限公司 | Method and apparatus for triggering beam status information report in wireless communication system |
US10506576B2 (en) * | 2017-01-27 | 2019-12-10 | Qualcomm Incorporated | Multi-link new radio (NR)-physical downlink control channel (PDCCH) design |
US10912150B2 (en) | 2017-02-03 | 2021-02-02 | Apple Inc. | Anchor channel design for unlicensed Internet of Things (IoT) |
US10624105B2 (en) | 2017-02-10 | 2020-04-14 | Hon Hai Precision Industry Co., Ltd. | Hierarchical resource scheduling method of wireless communication system |
EP3586542A1 (en) | 2017-02-27 | 2020-01-01 | Intel IP Corporation | Exit conditions for conditional handovers and beam based mobility state estimation |
WO2018156830A1 (en) * | 2017-02-27 | 2018-08-30 | Mavenir Networks, Inc. | System and method for supporting low latency applications in a cloud radio access network |
KR102026137B1 (en) * | 2017-03-15 | 2019-09-27 | 한국전자통신연구원 | Operation method of communication node in communication system based on millimeter wave |
US11057935B2 (en) * | 2017-03-22 | 2021-07-06 | Comcast Cable Communications, Llc | Random access process in new radio |
CN108633105A (en) * | 2017-03-23 | 2018-10-09 | 索尼公司 | Electronic equipment and method for wireless communication |
US11647543B2 (en) | 2017-03-23 | 2023-05-09 | Comcast Cable Communications, Llc | Power control for random access |
US11064522B2 (en) | 2017-03-24 | 2021-07-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Multiple starting and ending positions for scheduled downlink transmission on unlicensed spectrum |
EP3602923A1 (en) * | 2017-03-24 | 2020-02-05 | Intel IP Corporation | Partial uplink subframe transmissions on unlicensed carriers |
US10873962B2 (en) * | 2017-03-29 | 2020-12-22 | Apple Inc. | Mechanisms for handling uplink grants indicating different physical uplink shared channel starting positions in a same subframe |
US11134492B2 (en) | 2017-04-12 | 2021-09-28 | Samsung Electronics Co., Ltd. | Method and apparatus for beam recovery in next generation wireless systems |
US10993252B2 (en) * | 2017-04-14 | 2021-04-27 | Qualcomm Incorporated | Scheduling request multiplexing based on reliability and latency objectives |
WO2018195787A1 (en) * | 2017-04-26 | 2018-11-01 | Qualcomm Incorporated | Enhanced machine type communications quick idle transition after connection release |
SG11201900189YA (en) | 2017-05-03 | 2019-02-27 | Lg Electronics Inc | Method for transmitting and receiving random access channel, and device for same |
US10582432B2 (en) * | 2017-05-04 | 2020-03-03 | Comcast Cable Communications, Llc | Communications for network slicing using resource status information |
EP4013122A1 (en) | 2017-05-04 | 2022-06-15 | Beijing Xiaomi Mobile Software Co., Ltd. | Beam-based measurement configuration |
US10524294B2 (en) * | 2017-05-04 | 2019-12-31 | Ofinno, Llc | Scheduling request transmission |
CN108811153A (en) * | 2017-05-05 | 2018-11-13 | 华为技术有限公司 | Communication means, centralized unit, distributed unit, base station and terminal device |
KR102301907B1 (en) * | 2017-05-05 | 2021-09-15 | 삼성전자 주식회사 | Method for establishing a fronthaul interface, method for performing access for a ue, method and apparatus for performing a handover for a ue, data forwarding method, user equipment and base station |
EP3583707A1 (en) * | 2017-05-05 | 2019-12-25 | National Instruments Corporation | Wireless communication system that performs beam reporting based on a combination of reference signal receive power and channel state information metrics |
US10469358B2 (en) * | 2017-05-18 | 2019-11-05 | Qualcomm Incorporated | Wireless multihop relay |
KR102341820B1 (en) * | 2017-05-26 | 2021-12-21 | 삼성전자주식회사 | Apparatus and method for channel access in wireless communication system |
US10624072B2 (en) * | 2017-06-10 | 2020-04-14 | Qualcomm Incorporated | Shortened transmission time interval (STTI) configuration for low latency communications |
US10568128B2 (en) * | 2017-06-14 | 2020-02-18 | Qualcomm Incorporated | Techniques and apparatuses for scheduling request acknowledgement |
CN110999523A (en) | 2017-06-14 | 2020-04-10 | 三星电子株式会社 | Method and user equipment for reconnecting a radio resource control connection with a radio access network node |
EP3840477B1 (en) | 2017-06-15 | 2024-01-31 | ZTE Corporation | System and method for exchanging configuration information between two nodes in a wireless network |
WO2018227480A1 (en) | 2017-06-15 | 2018-12-20 | Qualcomm Incorporated | Refreshing security keys in 5g wireless systems |
WO2018232399A2 (en) | 2017-06-16 | 2018-12-20 | Kyungmin Park | Distributed unit configuration update |
CN109150451B (en) | 2017-06-16 | 2023-06-20 | 华为技术有限公司 | Communication method, network node and radio access network system |
EP3649816A4 (en) | 2017-07-05 | 2021-01-27 | Telefonaktiebolaget LM Ericsson (publ) | Method and system for flexible sounding reference signal (srs) transmission in a wireless communication network |
US10869353B2 (en) * | 2017-07-23 | 2020-12-15 | Lg Electronics Inc. | Method and apparatus for modifying radio bearer in CU-DU split scenario |
US10708968B2 (en) * | 2017-08-25 | 2020-07-07 | Kt Corporation | Method of controlling mobility of UE and apparatus therefor |
US11082320B2 (en) * | 2017-10-25 | 2021-08-03 | Qualcomm Incorporated | Techniques for RMSI PDCCH transmission and monitoring |
US11153271B2 (en) * | 2018-02-16 | 2021-10-19 | Apple Inc. | Managing bearers in a radio access network |
EP3537835A1 (en) * | 2018-03-05 | 2019-09-11 | ASUSTek Computer Inc. | Method and apparatus of handling beam failure recovery in a wireless communication system |
KR20190129605A (en) | 2018-05-11 | 2019-11-20 | 삼성전자주식회사 | Apparatus and method for uplink scheduling in wireless communication system |
-
2018
- 2018-06-18 WO PCT/US2018/038078 patent/WO2018232399A2/en unknown
- 2018-06-18 EP EP20170839.3A patent/EP3709763A1/en active Pending
- 2018-06-18 EP EP22197455.3A patent/EP4132212A3/en active Pending
- 2018-06-18 EP EP18743614.2A patent/EP3530068A2/en not_active Withdrawn
- 2018-06-18 US US16/011,363 patent/US10608797B2/en active Active
- 2018-06-18 US US16/011,371 patent/US10855420B2/en active Active
- 2018-06-18 US US16/011,376 patent/US10594456B2/en active Active
-
2020
- 2020-03-16 US US16/819,830 patent/US11381361B2/en active Active
- 2020-03-30 US US16/834,591 patent/US11588594B2/en active Active
- 2020-11-24 US US17/102,746 patent/US11736249B2/en active Active
Patent Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100003982A1 (en) * | 2008-05-30 | 2010-01-07 | Interdigital Patent Holdings, Inc. | Method and apparatus for delivery notification of non-access stratum retransmission |
US20130136015A1 (en) * | 2010-04-30 | 2013-05-30 | Nokia Corporation | User equipment carrier activation |
US20170141771A1 (en) * | 2013-01-11 | 2017-05-18 | International Business Machines Corporation | On-chip randomness generation |
US20160029376A1 (en) * | 2013-04-05 | 2016-01-28 | Kyocera Corporation | Mobile communication system and user terminal |
US20150223282A1 (en) * | 2014-01-31 | 2015-08-06 | Qualcomm Incorporated | Procedures for managing secondary enb (senb) radio link failure (s-rlf) in dual connectivity scenarios |
US20170013650A1 (en) * | 2014-03-20 | 2017-01-12 | Kyocera Corporation | Secondary base station, mobile station, communication control method, and master base station |
US20150280905A1 (en) * | 2014-04-01 | 2015-10-01 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for detecting and correcting pdcp hyper frame number (hfn) desynchronization |
US20170374705A1 (en) * | 2015-01-30 | 2017-12-28 | Kyocera Corporation | User terminal and base station |
US20160262118A1 (en) * | 2015-03-06 | 2016-09-08 | Samsung Electronics Co., Ltd. | Method and apparatus for performing and reporting measurements by user equipment configured with multiple carriers in mobile communication systems |
US20180206275A1 (en) * | 2017-01-17 | 2018-07-19 | Cisco Technology, Inc. | System and method to facilitate stateless serving gateway operations in a network environment |
US20180227805A1 (en) * | 2017-02-03 | 2018-08-09 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting data in a mobile communication system |
US20180279358A1 (en) * | 2017-03-22 | 2018-09-27 | Ofinno Technologies, Llc | Data Multiplexing in a Wireless Device and Wireless Network |
US20180368166A1 (en) * | 2017-06-16 | 2018-12-20 | Mediatek Inc. | User equipment and method to support data preprocessing |
Non-Patent Citations (69)
Title |
---|
3GPP TS 36.331 V14.2.2 (Apr. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC);; Protocol specification. |
3GPP TS 38.401 V0.2.0 (Jul. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15). |
R2-1704089-RLM and RLF in NR; 3GPP TSG-RAN WG2 #97bisTdoc ; Spokane, USA Apr. 3-7, 2017(updated version of R2-1702677); ; Agenda Item:10.2.8; Source:Ericsson; Title: RLM and RLF in NR. |
R2-1704089—RLM and RLF in NR; 3GPP TSG-RAN WG2 #97bisTdoc ; Spokane, USA Apr. 3-7, 2017(updated version of R2-1702677); ; Agenda Item:10.2.8; Source:Ericsson; Title: RLM and RLF in NR. |
R2-1704227; 3GPP TSG-RAN WG2 Meeting #98; Hangzhou, China, May 15-19, 2017; Source: CATT; Title: Beam Recovery Failure and RLF. |
R2-1704382-SPS UL skipping in NR; 3GPP TSG-RAN WG2 #98Tdoc ; Hangzou, P.R. of China, May 15-19, 2017; ; Agenda Item:10.3.1.7; Source:Ericsson; Title:Semi-Persistent Scheduling UL skipping in NR. |
R2-1704382—SPS UL skipping in NR; 3GPP TSG-RAN WG2 #98Tdoc ; Hangzou, P.R. of China, May 15-19, 2017; ; Agenda Item:10.3.1.7; Source:Ericsson; Title:Semi-Persistent Scheduling UL skipping in NR. |
R2-1704487; 3GPP TSG-RAN WG2 Meeting #98; Hangzhou, P. R. China, May 15-19, 2017; Agenda Item: 10.2.8; Source: AT&T; Title: Beam Failure (BF) and Radio Link Interruption (RLI). |
R2-1704496 Semi-persistent scheduling in NR; 3GPP TSG-RAN WG2 Meeting #98; Hangzhou, China, May 15-19, 2017; ; ; Agenda Item: 10.3.1.7 (NR_newRAT-Core); Source: LG Electronics Inc. |
R2-1704570 Considerations on main issues with Semi-Persistent Scheduling (SPS) in NR; 3GPP TSG-RAN WG2 #98; Hangzhou, China, May 15-19, 2017; ; Agenda item:10.3.1.7; Source: Samsung Electronics R&D Institute UK; Title: Considerations on main issues with Semi-Persistent Scheduling (SPS) in NR. |
R2-1704698 Consideration on SPS; 3GPP TSG-RAN WG2 Meeting#98 ; Hangzhou, China, May 15-19, 2017; ; Source: ZTE; Title: Consideration on SPS; Agenda item:10.3.1.7. |
R2-1704699 consideration on grant-free transmission; 3GPP TSG-RAN WG2 Meeting#98 ; Hangzhou, China, May 15-19, 2017; ; Source: ZTE; Title: Consideration on grant-free transmission; Agenda item:10.3.1.7. |
R2-1704860; 3GPP TSG-RAN WG2#98; Hangzhou, China, May 15-19, 2017; Source: Huawei, HiSilicon; Title: RLF for NR. |
R2-1704920; 3GPP TSG-RAN WG2 #98; Hangzhou, China, May 15-19, 2017; Agenda Item: 10.2.8; Source: InterDigital Inc.; Title: RLM/RLF for NR. |
R2-1704929_LAA sharing_v1; 3GPP TSG-RAN WG2 #98; Hangzhou, China, May 15-19, 2017; ; ; Agenda Item: 7.1 ; Source:Apple. |
R2-1704934_CR to 36300 for LAA sharing_r13; 3GPP TSG-RAN WG2 #98 ; Hangzhou, China, May 15-19, 2017; CR-Form-v11.2; ; CHANGE REQUEST. |
R2-1705047; 3GPP TSG-RAN WG2 Meeting #98; Hangzhou, China, May 15-19, 2017; ; Source: Potevio; Title:Discussion on UL grant-free transmission for URLLC; Agenda Item:10.3.1.7. |
R2-1705118 Grant-free resource configuration; 3GPP TSG-RAN WG2 Meeting #98; Hangzhou, China, May 15-19, 2017; Source: Huawei, HiSilicon; Title: Grant-free resource configuration; Agenda item:10.3.1; Document for:Discussion and decision. |
R2-1705242 Grant free transmission in NR; 3GPP TSG-RAN WG2 Meeting #98; Hangzhou, China, May 15-19, 2017; ; Agenda Item: 10.3.1.7 (NR_newRAT-Core); Source: LG Electronics Inc.; Title: Grant free transmission in NR. |
R2-1705249_UP latency enhancement; 3GPP TSG-RAN WG2 Meeting #98; Hangzhou, China, May 15-19, 2017; ; Agenda item:10.3.1.7; Source:Samsung; Title:RAN2 consideration on user plane latency enhancement. |
R2-1705504; 3GPP TSG-RAN WG2 Meeting #98; Hangzhou, China, May 15-19, 2017; CR-Form-v11.1; ; CHANGE REQUEST. |
R2-1705594-Potential Issues for UL Transmision with Shared UL Grant among Multiple UEs; 3GPP TSG RAN WG2 #98 ; Hangzhou, China, May 15-19, 2017Resubmission; Agenda Item:10.3.1.5; Souce:Samsung; Title:Potential Issues for UL Transmision with Shared UL Grant; among Multiple UEs. |
R2-1705594—Potential Issues for UL Transmision with Shared UL Grant among Multiple UEs; 3GPP TSG RAN WG2 #98 ; Hangzhou, China, May 15-19, 2017Resubmission; Agenda Item:10.3.1.5; Souce:Samsung; Title:Potential Issues for UL Transmision with Shared UL Grant; among Multiple UEs. |
R2-1706064_CR to 36300 for LAA sharing_R13_r2; 3GPP TSG-RAN WG2 #98 ; Hangzhou, China, May 15-19, 2017; CR-Form-v11.2; ; CHANGE REQUEST. |
R2-1706091_CR to 36300 for LAA sharing_R13; 3GPP TSG-RAN WG2 #98 ; Hangzhou, China, May 15-19, 2017; CR-Form-v11.2; ; CHANGE REQUEST. |
R3-171450; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, China, May 15, 2017-May 19, 2017; Agenda item: 10.10.1; Source: LG Electronics Inc.; Title: Fast re-transmission of lost RLC PDUs. |
R3-171456; 3GPP TSG RAN WG3 Meeting #96; Hangzhou,China, May 15-19, 2017; Source: CATT; Title: Consideration on the RRC message transfer between CU and DU. |
R3-171457; 3GPP TSG RAN WG3 Meeting #96; Hangzhou,China, May 15-19, 2017; Source: CATT; Title: Discussion on L2 measurements support in case of CU/DU split; Agenda Item: 10.10.1. |
R3-171458; 3GPP TSG-RAN WG3 #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: CATT; Title: Discussion on UE Context Management. |
R3-171460; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou,China, May 15-19, 2017; Agenda Item: 10.10.1; Source: CATT; Title: Stage 2 TP for RRC message transfer between CU and DU. |
R3-171460; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou,China, May 15-19, 2017; Agenda Item: 10.10.1; Source: CATT; Title: Stage 3 TP for RRC message transfer in F1 interface. |
R3-171462; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou,China, May 15-19, 2017; Agenda Item: 10.10.1; Source: CATT; Title: Stage 2 TP for L2 measurements support in case of CU/DU split. |
R3-171463; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou,China, May 15-19, 2017; Agenda Item: 10.10.1; Source: CATT; Title: Stage 3 TP for L2 measurements support in case of CU/DU split. |
R3-171464; 3GPP TSG-RAN WG3 #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: CATT; Title: Stage2 TP for UE Context management in F1AP. |
R3-171465; 3GPP TSG-RAN WG3 #96; Hangzhou, P. R. China, May 15-19, 2017; Source: CATT; Title: Stage3 TP for UE context management in F1AP. |
R3-171475; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Source: IAESI, Thales, Fairspectrum, VTT; Title: Central RRM functions and gNB-DU reporting. |
R3-171491; was R3-171342; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P.R. China, May 15-19, 2017. |
R3-171548; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, China, May 15, 2017-May 19, 2017; Agenda item: 10.10.1; Source: LG Electronics Inc.; Title: Functions of the F1 interface. |
R3-171588; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, China, May 15, 2017-May 19, 2017; Agenda item: 10.10.1; Source: LG Electronics Inc.; Title: TP for functions of the F1 interface. |
R3-171590; 3GPP TSG-RAN3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Title: CU-DU interface: On RRC message transport; Source: China Telecom. |
R3-171593; 3GPP TSG RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: ZTE; Title: Solution on RRC message transmission. |
R3-171597; 3GPP TSG RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: ZTE; Title: Discussion on UE Radio Bearer Management over F1 interface. |
R3-171599; 3GPP TSG RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: ZTE; Title: Discussion on flow control over F1-U. |
R3-171631; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung, KT, SK Telecom; Title: Relationship among gNB-CU, gNB-DU and cell. |
R3-171632; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung, KT, SK Telecom; Title: Text proposal for TS38.401 on definition of gNB-DU. |
R3-171633; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung; Title: RRC messages over F1 interface. |
R3-171634; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung; Title: Text proposal for TS38.401 on RRC messages over F1 interface. |
R3-171635; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung, KT, SK Telecom; Title: Interface between gNB-CU/gNB-DU and O&M. |
R3-171636; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung, KT, SK Telecom; Title: Text proposal for TS38.401 on gNB-DU management. |
R3-171637; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung; Title: F1AP functions. |
R3-171638; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung; Title: Text proposal for TS38.401 on F1-C functions. |
R3-171658; 3GPP TSG RAN WG3 Meeting #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda item: 10.10.1; Source: ZTE; Title: CU/DU ID and conception discussion. |
R3-171661; 3GPP TSG RAN WG3 Meeting #96; Hangzhou,P.R.China, May 15-19, 2017; Title: Solution on PDCP PDU retransmission. |
R3-171689; 3GPP TSG-RAN WG3 #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda Item: 10.10.1. CU-DU interface principle and definition; Source: NEC; Title: Specification of L1/L2 configuration Info in F1AP. |
R3-171691; 3GPP TSG-RAN WG3 #96; Hangzhou, P. R. China, May 15-19, 2017; Agenda Item: 10.10.1; Source: Vodafone; Title: Reliability for Core Network and RRC Signalling. |
R3-171696; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P.R.China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung, KT; Title: Global gNB ID (gNB-CU ID & gNB-DU ID) & Cell ID. |
R3-171697; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P.R.China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung, KT, SK Telecom; Title: Intra-CU/Inter-DU Handover support. |
R3-171699; 3GPP TSG-RAN WG3 Meeting #96; Hangzhou, P.R.China, May 15-19, 2017; Agenda item: 10.10.1; Source: Samsung, KT, SK Telecom; Title: Termination of NG and S1-U Interface. |
R3-171815 Discussions on mobility procedure; 3GPP TSG-RAN3 Meeting#96R3-171815 Hang Zhou, China, May 15-19, 2017; ; ; Title: Discussions on mobility procedures; Source: Huawei. |
R3-171818 HLS Architecture Principles-Altiostar; 3GPP TSG RAN WG3 Meeting #96 R3-171818 Hangzhou, P. R. China, May 15-19, 2017; ; Agenda item:10.10.1; Source:Altiostar Networks ; Title:HLS Architecture Principles. |
R3-171818 HLS Architecture Principles—Altiostar; 3GPP TSG RAN WG3 Meeting #96 R3-171818 Hangzhou, P. R. China, May 15-19, 2017; ; Agenda item:10.10.1; Source:Altiostar Networks ; Title:HLS Architecture Principles. |
R3-171819 CU-DU RRM Functions-Altiostar; 3GPP TSG RAN WG3 Meeting #96 R3-171819 Hangzhou, P. R. China, May 15-19, 2017; ; Agenda item:10.10.1; Source:Altiostar Networks, Orange ; Title: Consideration of RRM Functions in CU-DU Split Architecture. |
R3-171819 CU-DU RRM Functions—Altiostar; 3GPP TSG RAN WG3 Meeting #96 R3-171819 Hangzhou, P. R. China, May 15-19, 2017; ; Agenda item:10.10.1; Source:Altiostar Networks, Orange ; Title: Consideration of RRM Functions in CU-DU Split Architecture. |
R3-171820 CU-DU Flow Control-Altiostar; 3GPP TSG RAN WG3 Meeting #96 R3-171820 Hangzhou, P. R. China, May 15-19, 2017; ; Agenda item:10.10.1; Source:Altiostar Networks, Orange ; Title:Flow Control in CU-DU Split Architecture. |
R3-171820 CU-DU Flow Control—Altiostar; 3GPP TSG RAN WG3 Meeting #96 R3-171820 Hangzhou, P. R. China, May 15-19, 2017; ; Agenda item:10.10.1; Source:Altiostar Networks, Orange ; Title:Flow Control in CU-DU Split Architecture. |
R3-171823; TSG-RAN Working Group 3 meeting #96R3-171823 Hangzhou, China, May 15-19, 2017; ; Source: NTT DOCOMO, Inc.; Title: F1 interface: Radio resource configuration management; Agenda item:10.10.1. |
Tdoc R2-1704089; 3GPP TSG-RAN WG2 #97bis; Spokane, USA Apr. 3-7, 2017 (updated version of R2-1702677); Agenda Item: 10.2.8; Source: Ericsson; Title: RLM and RLF in NR. |
Tdoc R3-171724; 3GPP TSG-RAN WG3 #95bis; Spokane, USA, Apr. 3-7, 2017; Agenda Item: 10.10.1; Source: Ericsson; Title: F1 interface functions. |
Tdoc R3-171725; 3GPP TSG-RAN WG3 #96; Hangzhou, China, May 15-19, 2017; Agenda Item: 10.10.1; Source: Ericsson, AT&T, Vodafone; Title: Separation of CP and UP. |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10772008B2 (en) * | 2018-01-11 | 2020-09-08 | Comcast Cable Communications, Llc | Cell configuration for packet duplication |
US11533659B2 (en) | 2018-01-11 | 2022-12-20 | Comcast Cable Communications, Llc | Cell configuration for packet duplication |
US11877185B2 (en) | 2018-01-11 | 2024-01-16 | Comcast Cable Communications, Llc | Cell configuration for packet duplication |
US11490272B2 (en) * | 2018-10-16 | 2022-11-01 | Parallel Wireless, Inc. | Radio access network dynamic functional splits |
Also Published As
Publication number | Publication date |
---|---|
WO2018232399A3 (en) | 2019-01-31 |
US11588594B2 (en) | 2023-02-21 |
US11381361B2 (en) | 2022-07-05 |
US20180368204A1 (en) | 2018-12-20 |
US10855420B2 (en) | 2020-12-01 |
US20180367273A1 (en) | 2018-12-20 |
US20200228278A1 (en) | 2020-07-16 |
EP3530068A2 (en) | 2019-08-28 |
EP3709763A1 (en) | 2020-09-16 |
EP4132212A2 (en) | 2023-02-08 |
US10594456B2 (en) | 2020-03-17 |
US20200220684A1 (en) | 2020-07-09 |
US20180368205A1 (en) | 2018-12-20 |
US20210083821A1 (en) | 2021-03-18 |
EP4132212A3 (en) | 2023-06-07 |
US11736249B2 (en) | 2023-08-22 |
WO2018232399A2 (en) | 2018-12-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11736249B2 (en) | Communication of resource status information between a base station central unit and a base station distributed unit | |
US11528106B2 (en) | Wireless device reconfiguration procedure by a base station central unit | |
US11356229B2 (en) | Bandwidth part inactivity timer | |
US11147064B2 (en) | Resource selection for data multiplexing | |
CN111434067B (en) | Communication method, device and base station based on wireless device capability | |
US20200177357A1 (en) | Layer 1 Reference Signal Received Power Reporting For a Secondary Cell |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
AS | Assignment |
Owner name: OFINNO, LLC, VIRGINIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PARK, KYUNGMIN;DINAN, ESMAEL HEJAZI;BABAEI, ALIREZA;AND OTHERS;SIGNING DATES FROM 20190725 TO 20190729;REEL/FRAME:049898/0784 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: BEIJING XIAOMI MOBILE SOFTWARE CO., LTD., CHINA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:OFINNO, LLC;REEL/FRAME:058857/0329 Effective date: 20220111 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |