(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
`(19) World Intellectual Property
`Organization
`International Bureau
`
`(43) International Publication Date
`2 6 January
`2017
`(26.01.2017)
`
`P O P C T
`
`(10) International Publication Number
`WO 2017/014802 Al
`
`(51) International Patent Classification:
`H04W 28/02 (2009.01)
`H04W 88/06 (2009.01)
`H04W 36/00 (2009.01)
`(21) International Application Number:
`
`PCT/US20 15/067077
`
`(22) International Filing Date:
`
`2 1 December 2015 (21 .12.2015)
`English
`English
`
`(25) Filing Language:
`(26) Publication Language:
`(30) Priority Data:
`22 July 2015 (22.07.2015)
`62/195,620
`US
`(71) Applicant: INTEL IP CORPORATION [US/US]; 2200
`Mission College Boulevard, Santa Clara, California 95054
`(US).
`(72) Inventors: ZHANG, Yujian; Room 3 12, Building 21,
`CAAS, No. 12 ZhongGuanCunNanDaJie, Haidian District,
`Beijing, Heilongjiang 100081 (CN). FONG, Mo-Han; 409
`Spencer Terrace, Sunnyvale, California 94089 (US). YIU,
`Candy; 1750 SW Broadway Dr., Portland, Oregon 97201
`(US). GUY, Wey-Yi W.; 18067 SW Ingrid Terr., Beaver-
`
`ton, Oregon 97007 (US). PHUYAL, Umesh; 20782 NW
`Longbow Ln., Beaverton, Oregon 97006 (US). HEO,
`Youn Hyoung; 4F, 27-3, Hana Daetoo Securities Bldg.,
`Yeouido-dong, Yeongdeungpo-gu,
`Seoul, KR 150-705
`(KR).
`(74) Agents: ESCHWEILER, Thomas G. et al; ESCH-
`WEILER & ASSOCIATES, LLC, 629 Euclid Ave., Suite
`1000, Cleveland, Ohio 441 14 (US).
`(81) Designated States (unless otherwise indicated, for every
`kind of national protection available): AE, AG, AL, AM,
`AO, AT, AU, AZ, BA, BB, BG, BH, BN, BR, BW, BY,
`BZ, CA, CH, CL, CN, CO, CR, CU, CZ, DE, DK, DM,
`DO, DZ, EC, EE, EG, ES, FI, GB, GD, GE, GH, GM, GT,
`HN, HR, HU, ID, IL, IN, IR, IS, JP, KE, KG, KN, KP, KR,
`KZ, LA, LC, LK, LR, LS, LU, LY, MA, MD, ME, MG,
`MK, MN, MW, MX, MY, MZ, NA, NG, NI, NO, NZ, OM,
`PA, PE, PG, PH, PL, PT, QA, RO, RS, RU, RW, SA, SC,
`SD, SE, SG, SK, SL, SM, ST, SV, SY, TH, TJ, TM, TN,
`TR, TT, TZ, UA, UG, US, UZ, VC, VN, ZA, ZM, ZW.
`(84) Designated States (unless otherwise indicated, for every
`kind of regional protection available): ARIPO (BW, GH,
`GM, KE, LR, LS, MW, MZ, NA, RW, SD, SL, ST, SZ,
`
`[Continued on nextpage]
`
`(54) Title: CONVERGENCE LAYER FOR 5G COMMUNICATION SYSTEMS
`(57) Abstract: A network device (e.g., an evolved Node B (eNB), user
`equipment (UE) or the like) can operate to reduce an interruption time dur
`ing a fallback operation resulting from a communication link blockage con
`dition (e.g., a human blockage or other natural/physical wireless blockage).
`The network device includes a network convergence protocol
`(NCP) layer
`that enables communication between other network devices of different ra
`dio access technologies (RATs) in a heterogeneous network.
`
`f V
`
`J
`-S5/8 1 0
`
`S-GVV
`
`V
`
`>
`
`J
`
`APPLE 1007
`
`1
`
`

`

`w o 2017/014802 Ai III III IIII III III III II
`
`III IIII I II 11III II III
`
`TZ, UG, ZM, ZW), Eurasian (AM, AZ, BY, KG, KZ, RU, Published
`TJ, TM), European (AL, AT, BE, BG, CH, CY, CZ, DE,
`with international search report (Art. 21(3))
`DK, EE, ES, FI, FR, GB, GR, HR, HU, IE, IS, IT, LT,
`LU, LV, MC, MK, MT, NL, NO, PL, PT, RO, RS, SE,
`SI, SK, SM, TR), OAPI (BF, BJ, CF, CG, CI, CM, GA,
`GN, GQ, GW, KM, ML, MR, NE, SN, TD, TG).
`
`2
`
`

`

`CONVERGENCE LAYER FOR 5G COMMUNICATION SYSTEMS
`
`REFERENCE TO RELATED APPLICATIONS
`[0001]
`This application claims the benefit of U.S. Provisional Application No.
`62/1 95,620 filed July 22, 201 5 , entitled "CONVERGENCE LAYER FOR 5G
`COMMUNICATION SYSTEMS", the contents of which are herein incorporated by
`reference in their entirety.
`
`FIELD
`[0002]
`The present disclosure relates to wireless communications, and more
`specifically, to a convergence protocol
`layer for wireless communications.
`
`BACKGROUND
`[0003]
`The fifth generation of mobile technology (5G) is positioned to address the
`It has potential to enable a fully
`demands and business contexts of 2020 and beyond.
`mobile and connected society and to empower socio-economic transformations in a
`including those for
`countless number of ways, many of which are unimagined,
`productivity, sustainability and well-being.
`[0004]
`The new radio access technology (RAT) to be introduced for 5G can be
`deployed in a high frequency band, e.g. millimeter wave (mmW), ranging from about
`In high frequency,
`it is possible that the channel condition
`30GHz to about 300 GHz.
`between a wireless device (e.g., a user equipment (UE)) and a network can drop or lose
`connection suddenly due to blockage from building, vehicles, human movement, or
`other conditions. There can be two main types of blockage. One is channel condition or
`environment changes within a short time interval, which may last for tens of milliseconds.
`Additionally, human blockage can be another with a duration that can last several
`for example, or more or less. Such long interruption time may
`hundreds of milliseconds,
`cause transmission control protocol (TCP) connection to return to a slow start mode,
`which reduces the throughput perceived by the user, therefore impacting user
`throughput and quality of experience (QoE).
`[0005]
`In 3GPP radio access network (RAN) long term evolution LTE systems, the
`node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-
`UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs,
`eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with
`
`3
`
`

`

`the UE. The downlink (DL) transmission can be a communication from the node (e.g.,
`eNB) to the UE, and the uplink (UL) transmission can be a communication from the
`wireless device to the node.
`In LTE, data can be transmitted from the eNodeB to the
`UE via a physical downlink shared channel (PDSCH). A physical uplink control channel
`(PUCCH) can be used to acknowledge that data was received. Downlink and uplink
`channels can use time-division duplexing (TDD) or frequency-division duplexing (FDD).
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`FIG. 1 illustrates a block diagram illustrating an example radio access
`[0006]
`network (RAN) anchored wireless wireless local area network (WLAN) wireless
`communications network environment for a UE or eNB according to various
`embodiments.
`[0007]
`FIGs. 2 illustrates an example network convergence protocol layer
`architecture applicable to the network environments, network devices (NDs) and
`processes according to various embodiments being disclosed.
`[0008]
`FIG. 3 illustrates a wireless communications network system with one or more
`NDs according to various embodiments.
`[0009]
`FIG. 4 illustrates another wireless communications network system with one
`or more NDs according to various embodiments.
`[0010]
`FIG. 5 illustrates another wireless communications network system with one
`or more NDs according to various embodiments.
`FIG. 6 illustrates another wireless communications network system for one or
`[001 1]
`more NDs according to various embodiments.
`[0012]
`FIG. 7 illustrates an example packet data unit (PDU) format of a PDU
`according to various embodiments.
`[0013]
`FIG. 8 illustrates another example packet data unit (PDU) format of a PDU
`according to various embodiments.
`[0014]
`FIG. 9 illustrates another example packet data unit (PDU) format for a status
`report PDU according to various embodiments.
`[0015]
`FIG. 10 illustrates another example packet data unit (PDU) format of a PDU
`according to various embodiments.
`[0016]
`FIG. 11 illustrates another example packet data unit (PDU) format of a PDU
`according to various embodiments.
`
`4
`
`

`

`FIG. 12 illustrates an example process flow for an NCP layer according to
`[0017]
`various embodiments.
`FIG. 13 is a block diagram illustrating an example user equipment (UE)
`[0018]
`useable in connection with various aspects described herein.
`FIG. 14 is a block diagram of an enhanced node B (eNB) or other network
`[0019]
`device that facilitates bearer splitting according to various aspects described herein.
`
`DETAILED DESCRIPTION
`[0020]
`The present disclosure will now be described with reference to the attached
`drawing figures, wherein like reference numerals are used to refer to like elements
`throughout, and wherein the illustrated structures and devices are not necessarily drawn
`to scale. As utilized herein, terms "component," "system," "interface," and the like are
`intended to refer to a computer-related entity, hardware, software (e.g., in execution),
`and/or firmware. For example, a component can be a processor, a process running on
`a processor, a controller, a circuit or a circuit element, an object, an executable, a
`program, a storage device, a computer, a tablet PC and/or a mobile phone with a
`processing device. By way of illustration, an application running on a server and the
`server can also be a component. One or more components can reside within a
`process, and a component can be localized on one computer and/or distributed
`between two or more computers. A set of elements or a set of other components can
`be described herein, in which the term "set" can be interpreted as "one or more."
`[0021] Further, these components can execute from various computer readable
`storage media having various data structures stored thereon such as with a module, for
`example. The components can communicate via local and/or remote processes such
`as in accordance with a signal having one or more data packets (e.g., data from one
`component interacting with another component in a local system, distributed system,
`and/or across a network, such as, the Internet, a local area network, a wide area
`network, or similar network with other systems via the signal).
`[0022] As another example, a component can be an apparatus with specific
`functionality provided by mechanical parts operated by electric or electronic circuitry, in
`which the electric or electronic circuitry can be operated by a software application or a
`firmware application executed by one or more processors. The one or more processors
`can be internal or external to the apparatus and can execute at least a part of the
`software or firmware application. As yet another example, a component can be an
`
`5
`
`

`

`apparatus that provides specific functionality through electronic components or
`elements without mechanical parts; the electronic components can include one or more
`processors therein to execute software and/or firmware that confer(s), at least in part,
`the functionality of the electronic components.
`[0023] Use of the word exemplary is intended to present concepts in a concrete
`fashion. As used in this application, the term "or" is intended to mean an inclusive "or"
`rather than an exclusive "or". That is, unless specified otherwise, or clear from context,
`"X employs A or B" is intended to mean any of the natural inclusive permutations. That
`is, if X employs A ; X employs B; or X employs both A and B, then "X employs A or B" is
`satisfied under any of the foregoing instances.
`In addition, the articles "a" and "an" as
`used in this application and the appended claims should generally be construed to
`mean "one or more" unless specified otherwise or clear from context to be directed to a
`singular form. Furthermore, to the extent that the terms "including", "includes", "having",
`"has", "with", or variants thereof are used in either the detailed description and the
`claims, such terms are intended to be inclusive in a manner similar to the term
`"comprising".
`[0024]
`In consideration of the above described deficiencies, various process and
`network devices are discloses to facilitate packet communications with a network
`convergence protocol (NCP) layer without having to utilizing bearer switching as a result
`of a fallback operation or other change from one serving access node (access point or
`network device (ND)) serving a UE. For example, such fallback operation can include
`changing the serving node from one radio access technology (RAT) (e.g., an LTE or
`5GPP millimeter wave (mmW) to another (e.g., 5G mmW or other RAT) in response to
`various network conditions (e.g., blockage) that make the fallback target cell more
`optimal for the UE.
`[0025]
`Communication in mmW spectrum has gained an increasing interest for
`tackling the spectrum crunch problem and meeting the high network capacity demand in
`4G and beyond. Considering the channel characteristics of mmW bands, it can be fit
`into heterogeneous networks (HetNet) for boosting local-area data rate with a booster
`node together with at least one anchor node, as an anchor-booster based
`heterogeneous networks (HetNets) with mmW 5G capable booster cells.
`[0026]
`In one example, a network device (e.g., an eNB, management entity, UE or
`any device communicatively coupled to a network) can be communicatively coupled to a
`multi-radio HetNet of a RAN. The multi-radio HetNet can comprise various multi-radio
`
`6
`
`

`

`connections of various RATs, such as 3GPP, LTE, 5G, mmW, legacy 3GPP RATs via
`one or more NDs. The network device can comprise a NCP layer that operates to
`reduce interruption time from blockage events by controlling retransmissions, reordering
`processes, and duplicate elimination / discarding operations in response to fallback
`operations or processes.
`[0027]
`The network device can include a memory with computer-executable
`components or instructions, and processing circuitry, communicatively coupled to the
`memory, which facilitates execution of the computer-executable components. The
`computer-executable components can include a receive logic component that receives,
`from a first layer (e.g., an upper or lower protocol layer), a first data unit or packet (e.g.,
`a NCP protocol data unit (PDU) or a NCP service data unit (SDU)) that is associated
`with the NCP layer. The NCP layer can further control data unit / packet flow without
`bearer switching in response to fallback operations from a network device (e.g., an LTE
`or 5G anchor node or eNB) of the multi-radio heterogeneous network of the RAN. A
`control logic component can generate a second data unit associated with the NCP layer
`based on the first data unit. A transmit logic component can transmit the second data
`unit to a second layer (e.g., a lower or upper protocol
`layer) that is different from and
`opposite in protocol level than the first layer. For example, the upper layer can be an
`internet protocol (IP) layer and the lower layer a packet data convergence protocol
`PDCP. Additional aspects and details of the disclosure are further described below with
`reference to figures.
`FIG. 1 illustrates a 3GPP RAN anchor-booster 5G network architectures 100
`[0028]
`for LTE-5G aggregation in accordance with various aspects or embodiments being
`described.
`[0029]
`The network architecture 100 can comprise an end-to-end network for cellular
`including a UE 110 , an eNB 120, and the following two gateway
`communications,
`entities of an evolved packet core (EPC), or other network core, which are examples of
`network entities and can be extended to other network entities such as for 5G and
`beyond : a serving gateway (S-GW) 130 and a packet data network (PDN) gateway
`(PDN GW, or P-GW) 140, as well as other network entities or components, for example.
`One of ordinary skill in the art will recognize that an EPC can include other network
`entities and interfaces not further detailed such as for 5G networks or otherwise.
`[0030]
`The UE 110 can communicate with the eNB 120 through an air interface Uu
`150 (also referred to as a cellular link), which can comprise a wireless radio
`
`7
`
`

`

`communication channel defined in 3GPP standards for long term evolution (LTE)
`wireless networks. The UE 110 can also operate as a dual connected device or dual
`radio UE 110 by being communicatively coupled to a 5G interface 196 or one or more
`other communication links / interfaces on the network concurrently or at the same time.
`[0031]
`The S-GW 130, in communication with the eNB 120 through an interface 160
`(e.g., an S 1 or other interface), provides a point of interconnect between the wireless
`radio side and the EPC side of the network architecture 100, as a co-located or a non-
`collated eNB 120, in which "collocated" refers to the LTE AP (e.g., the eNB 120) being
`located in the same network device 199 or component as the 5G ND or AP 180. The
`interface 160 can also be connected separately and independently to both the LTE eNB
`120 and the 5G AP 180. Network devices herein can be a gateway support node
`device, a cellular management entity device, a packet data gateway device, an eNB, for
`example, as well as other network devices functionally serving network communications
`for UEs and combinations of these devices communicatively coupled to one another.
`[0032]
`The S-GW 130 can comprise the anchor point for the intra-LTE mobility, i.e.,
`in case of a handover between eNBs and between LTE and other 3GPP accesses. The
`S-GW 130 is logically connected to the other gateway, the P-GW 140, through an S5/8
`interface 170. 3GPP standards specify separately the S-GW 130 and the P-GW 140,
`but in practice, these gateways can be combined as a common network component
`provided by a network equipment vendor. The P-GW 140 further provides a point of
`interconnect between the EPC and an external
`internet protocol (IP) network (not
`shown). An external
`IP network is also called a packet data network (PDN). The P-GW
`140 can route IP packets to and from PDNs.
`[0033]
`In addition to the aforementioned end-to-end cellular network components,
`FIG. 1 further illustrates that the UE 110 can communicate with the eNB 120 through a
`5G AP 180 via an interface 190, and can be connected to both the 5G AP 180 and the
`eNB 120 concurrently or simultaneously via interfaces 196 and 150, respectively. The
`interface 190 represents the operative network connection and protocols between the
`UE 110 and its associated LTE cellular base station (BS), the eNB 120.
`In other words,
`the interface 190 can be a logical interface that can be realized by a mmW point-to-point
`communication link between the UE 110 and the eNB 120 for routing the UE 110's
`cellular traffic (e.g., voice or data) via the 5G AP 180.
`[0034]
`In one embodiment, the 5G AP 180 network device can comprise network
`convergence protocol (NCP) layer 194 while the UE device 110 can comprise an NCP
`
`8
`
`

`

`layer 192. The NCP layers 194 or 192 can enable packet communications involving
`packet retransmission, reordering for out-of-sequence occurrences, or duplication
`removal/discard/elimination processes without having to utilize a different bearer as a
`result of a fallback operation from the LTE eNB 120 to the 5G AP 180, or vice versa.
`[0035]
`In the 3GPP terminology, a bearer represents a class of traffic having a set of
`network parameters that establish a specific standard treatment for the traffic or data
`being communicated on the particular class of traffic (e.g., voice or the like) for one or
`more UEs or network devices (e.g., eNBs or the like). Bearers can be used to carry
`user plane traffic (i.e., user data) on an air interface, for example.
`[0036]
`Fallback operations with 5G can occur in response to signal blockages, in
`which shorter wave mmW signals can be more susceptible to. Thus, for longer
`blockages call drops could occur more frequently. However, the NCP layers 194 or 192
`can decrease the amount of interruption experienced by providing a specialized protocol
`layer in the communication processing that detects such blockages based on one or
`more criteria including any network condition or measurement related to the frequency
`band, network device operating (communicating) on the frequency band, or channel
`conditions, such as a signal strength, a channel quality, a load condition of the ND, or
`other parameter such as a reference signal received power (RSRP), a reference signal
`received quality (RSRQ), channel state information (CSI), one or more channel quality
`In response to one or more criteria being satisfied
`indicators (CQIs) or the like.
`according to a predetermined threshold, for example, a fallback operation can occur
`where the NCP layer 192, 194 operates at a receiving side and a transmitting side,
`either at different NDs (e.g., the UE 110 , the 5G AP 180, the LTE eNB 120, or other
`ND), or within the receive and transmit side circuitry components of each ND.
`Depending on the deployment environment, LTE eNB 120 and 5G AP 180 new RAT
`can co-exist. The 3GPP interface can be used as the control and mobility anchor for
`the 5G link (e.g., 190 or 196), which can serve as an additional "carrier" within the 3GPP
`network and used for data offload.
`In one aspect, the interface link 198 can be a user
`plane or control plane protocol.
`[0037]
`In one example, the LTE eNB 120 can be configured for coverage (i.e.
`mobility), while the 5G AP 180 RAT can be used for data offloading (as known as
`anchor-booster architecture). Other architectures or network configurations can also be
`envisioned also. For example, both anchor and booster node can be one or more 5G
`access nodes. For LTE-5G anchor booster architecture the bearer can be mapped to
`
`9
`
`

`

`either the LTE eNB 120 or the 5G AP 180, where fallback to the LTE eNB would utilize
`explicit radio resource control (RRC) signaling to switch the bearer type, which could
`incur a long interruption time without the NCP layer 192 or 194 in operation.
`Referring briefly to FIG. 2 before returning to FIG. 1, illustrated is an example
`[0038]
`network device 200 (e.g., a UE, a eNB of either 5G or LTE, or other ND) comprising a
`network convergence protocol layer for 5G communication system integration in
`accordance with various aspects. Embodiments herein relate to the NCP layer 204 to
`enable blockage issues that can occur in high frequency bands of 5G wireless systems.
`The NCP layer 204 can control packet retransmission / reordering / duplicate removal
`processes that result from the fallback between a 5G ND and an LTE ND, for example.
`[0039]
`Different link aggregation architectures can be utilized with embodiments
`herein for enabling different communication links (e.g., 5G or LTE eNB or other
`communication links associated with different RATs). The TCP/IP layer 202 comprises
`a Transmission Control Protocol/Internet Protocol layers that is the basic
`communication language or protocol of the Internet, and can be used as a
`communications protocol in a private network (either an intranet or an extranet). The
`TCP/IP layer 202 facilitates communications protocols used to connect network devices
`on the Internet.
`[0040]
`The NCP layer 204 can be utilized to meet demand for faster data rates and
`prevent the incurrence of long interruption times by blockages occurring over one or
`more 5G ND 180. The 5G ND 180 can be used for data offloading in order to alleviate
`or enable efficient load balancing on the network. By combining multiple channels at
`different frequencies and even different radio technologies or RATs (e.g., LTE and 5G
`mmW), the NCP layer 204 can operate on the DL or UL to facilitate traffic operations
`such as retransmissions, reordering, or duplicate discarding/elimination processes
`without bearer switching. This can enable fallback to other nodes, such as from the 5G
`ND 180 to another 5G AP coupled thereat or the LTE ND 120, for example.
`[0041]
`The NCP layer 204 can be added can be added on top of or above one or
`more packet data convergence protocol (PDCP) layers 206, 206' (lower layer(s))
`to perform IP packet retransmissions in either LTE eNB or another 5G node in case of
`blockage in one 5G node. It should be noted that the NCP layer 204 could also have
`other names, such as a Hyper Convergence Protocol (HCP), a Node Convergence
`Protocol (NCP), a Multi-Node Convergence Protocol (MNCP), a Multi-Node Flow
`
`10
`
`

`

`Control (MNFC), and is not limited to any one particular name for converging a 5G ND
`communications with an LTE ND 120 or UE 110 .
`[0042]
`The Packet Data Convergence Protocol (PDCP) layer(s) 206, 206' residing
`below or lower than the NCP layer 204 can be one of the layers of the Radio Traffic
`Stack in LTE, UMTS and can perform IP header compression and decompression,
`transfer of user data and maintenance of sequence numbers for Radio Bearers.
`[0043]
`The radio link control (RLC) layer(s) 208, 208' below or lower than the PDCP
`layer(s) 206, 206' can handle an automatic repeat request fragmentation protocol used
`over a wireless air interface. The RLC can detect packet losses and perform various
`other retransmissions aside from fall back conditions from a 5G node controlled by the
`NCP layer 204 to bring packet loss down to a low percentage rate, which is suitable for
`TCP/IP applications.
`[0044]
`The physical (PHY) and MAC layers 2 10 and 214, corresponding to separate
`RATs respectively, can operate to provide an electrical, mechanical, and procedural
`interface to the transmission medium. The physical layer translates logical
`communications requests from the data link layer into hardware-specific operations to
`affect transmission or reception of electronic signals. The MAC sublayer provides
`addressing and channel access control mechanisms that make it possible for
`several terminals or network nodes to communicate within a multiple access network
`that incorporates a shared medium.
`FIG. 3 illustrates an example of a network 300 having various network
`[0045]
`devices (e.g., a UE, eNB of one or more of LTE/5G RATs). The network device 302
`can be a serving node operating as a 5G mmW RAT node for downlinking data to a UE,
`for example. The network system 300 can utilize the NCP layer 204 for controlling
`fallback communications without bearer switching from a 5G mmW ND / node toward
`another 5G ND or LTE ND in response to a blockage being detected. The
`corresponding receiving side operation is further illustrated in FIG. 4 . Embodiments
`relate to how the bearer/packet flow handled by 5G node 302 can be enabled to fallback
`to other nodes (e.g., the in case there is blockage experienced in the 5G ND 302.
`[0046]
`In one aspect, the fallback operation can be performed in various directions
`such as towards the LTE or 5G ND 200, which can operate as the anchor node of the
`network 300. The fallback could also be performed towards another 5G node/ND 304.
`In this scenario, typically the 5G ND 304 can also be deployed in high frequency bands,
`and thus can provide similar throughput as 5G ND 302. The fallback operation could
`
`11
`
`

`

`also be performed towards at least one of the LTE or 5G anchor node 200 and another
`5G node (e.g., 5G ND 304).
`[0047]
`In another aspect, the NCP layer 204 could comprise a transmit logic
`component 306 for transmitting one or more packet or data units to lower layers of the
`protocol stack. The transmit logic component 306 as well as the NCP layer 204 could
`reside as part of logic within the protocol stack as well as integrated in the logic circuitry
`(transceiver, transmitter or receiver circuitry) of a respective network device (e.g., UE,
`LTE eNB, 5G eNB, or otherwise). At the transmitting side, for example, the transmit
`logic component 402, in response to a reception of a NCP service data unit (SDU) from
`upper layers, process the NCP SDU and submit a resulting NCP layer PDU to a lower
`layer.
`In addition, FIG. 4 illustrates the NCP layer 204 comprising the transmit logic
`[0048]
`component 306 along with a receive logic component 402 for receiving and passing
`along packet or data units to upper or lower layers of the protocol stack. The receive
`logic component 402 can reside or operate at a receiving side, and in response to a
`reception of the NCP PDU from one or more lower layers, process the NCP PDU and
`deliver the resulting NCP layer SDU to an upper layer; in which as illustrated in FIG. 2
`above, the upper layer 202 can be an Internet Protocol (IP) layer 202, and the lower
`layer can be PDCP layer 206 as a layer that resides immediately below the NCP layer
`204.
`[0049]
`Referring to FIG. 5, illustrates one example network system 500 for
`converging communications across different network device RATs. The network
`environment 500 comprises an NCP layer component 504 that receives data from
`various different network devices as data traffic 502 from UEs 520-528, data traffic via
`interfaces 530-540 from one or more APs, eNBs, or other network devices or
`components of one or more different RATs. Various other architectures can also be
`envisioned. For example, the NCP layer component 504 can include the TX logic
`component 306, and the RX logic component 204 as part of the NCP layer 204 across
`one or more NDs (e.g., eNBs, UEs or network entities).
`[0050]
`The NCP layer component 504 can be a part of the NCP layer 204 or vice
`versa. The NCP layer component 504 can enable the network environment 500 to be
`delay aware by detecting blockage at a 5G mmW node (e.g., ND 5 12) and operating
`retransmission processes / reordering processes / duplication removal process and the
`like among network devices 5 12-51 6 and the UEs 520-528 as the result of a fallback
`
`12
`
`

`

`from a detected blockage. The UE (e.g., 524 or otherwise) or the eNB 514 in connected
`mode or DL operations with the UE 524 can detect the blockage via a channel quality,
`SNR, a status report or other measurement or indication. For example, a status report
`can be sent to the eNB 514 via the UE 524 at regular scheduled intervals, based on an
`event trigger (e.g., low channel quality, SNR, low power, etc.) or be sent based on upon
`request from the eNB 514.
`[0051]
`The network devices 512-516 can comprise one or more WLAN network
`devices, eNBs, small cell network devices, routers or other network devices of different
`RATs configured to communicate with the various UEs 520-528 within one or more
`network zones for communication and managing operations. The network device 5 12 ,
`for example, can comprise a 5G mmW ND 5 12 with a base station queue 506 for
`buffering traffic thereat. The network device 514, for example, can comprise another
`5G mmW ND with a buffer / queue 508. Further, another network device 5 16 can
`comprise an LTE eNB or hybrid LTE/ 5G eNB anchor node with a base station queue
`5 10 . Likewise, one or more additional or alternative base station RATs can also be
`coupled to or comprise the NCP convergence layer 204 with traffic buffers or queues
`thereat for offloading and downlinking data for traffic flow.
`[0052]
`Each UE 520-528 can be single or dual connected devices that are
`communicatively coupled to one or more communication links (e.g., license or
`unlicensed links) via one or more network devices or nodes (e.g., 5G 5 12 and eNB 5 16 ,
`or any other RAT network device) and can also be coupled to or comprise the NCP
`layer 204, for example. The network system 500 can include any number of base
`stations/access points/ RATs across which the traffic can be converged for each UE
`520-528 for fallback operations involving a switch between a 5G ND, an LTE/5G node
`5 16 ND and another ND or node. Various processes can be executed by the NCP layer
`component 504, which can be located or reside at the eNB (e.g., 5 16) and other devices
`(e.g., NDs 5 12-514, and UEs 520-528) in cellular networks.
`[0053]
`In one aspect, to enable dynamic fallback, the UEs 520-528 maintain the
`necessary parts related to the bearer (or IP data flow). For example, when fallback is
`performed towards the LTE / 5G anchor node 5 12 from the 5G node 514 or other 5G
`ND 5 12 as a result of a blockage condition, the UE 520-528 can maintain or store layer
`2 protocols (e.g. PDCP/RLC/MAC) corresponding to the LTE / 5G anchor node, as well
`as layer 2 protocols corresponding to 5G ND 5 14 .
`
`13
`
`

`

`[0054]
`Similarly, dynamic fallback without bearer mapping or switching can also be
`facilitated when fallback is performed towards another 5G node 5 12 from the 5G node
`5 14 or other node.
`In this scenario, typically the 5G node 5 12 can also be deployed in
`high frequency bands, and thus, can provide similar throughput as 5G node 5 14 on
`which data was originally being offloaded, for example. The UE (e.g., 520-528) can
`thus also keep, maintain or store the layer 2 protocols (e.g. PDCP/RLC/MAC)
`corresponding to 5G node 5 14 , as well as layer 2 protocols corresponding to 5G node
`5 12 to which fallback is toward.
`[0055]
`In case of a blockage in 5G or at the 5G node (e.g., 5G mmW ND 514), when
`a UE (e.g., any of UEs 520-528) (as in the above described scenarios as well), in
`downlink communications, the LTE / 5G eNB 5 16 being switched to in fallback can
`perform retransmission / new transmissions in the LTE part of eNB 516 (or from another
`5G RAT node) directly without bearer switching or mapping of a different bearer via the
`NCP layer 204. Similarly for UL, a UE (e.g., any UE 520-528) also can perform
`retransmission / new transmissions in the LTE part within the same ND 5 16 (if a hybrid
`LTE/ 5G, or to another 5G RAT node) directly without bearer switching. The switching
`or fallback operations, fo