BR112018001598B1 - MECHANISMS FOR DIFFERENTIATED TREATMENT OF UNLOADED TRAFFIC - Google Patents

Abstract

MECHANISMS FOR DIFFERENTIATED TREATMENT OF OFF-LOAD TRAFFIC. Communication using a RAN radio access network (404) including a primary cell (406) for licensed spectrum access and a secondary cell (408) for unlicensed spectrum access can be enhanced to provide optimal performance while considering cell characteristics primary cell (406) and the secondary cell (408). The apparatus may be a core network entity (410). The core network entity (410) is connected to a RAN (404) that includes a primary cell (406) utilizing licensed spectrum and a secondary cell (408) utilizing unlicensed spectrum. The core network entity (410) determines an authorization for the data traffic to be offloaded to the secondary cell (408) based on the data traffic characteristics. The core network (410) transmits an authorization indication to the RAN (404)

Description

CROSS REFERENCE TO RELATED REQUEST(S)

[001] This application claims the benefit of US Provisional Patent Application Serial No. 62/198,026, entitled "MECHANISMS FOR DIFFERENTIATED TREATMENT OF OFFLOADED TRAFFIC" and filed on July 28, 2015, and US Patent Application No. 15/ 183,218, entitled "MECHANISMS FOR DIFFERENTIATED TREATMENT OF OFFLOADED TRAFFIC" and filed on June 15, 2016, which are expressly incorporated herein by reference in their entirety.

FUNDAMENTALS Field

[002] The present invention generally relates to communication systems and, more particularly, to communication via a licensed spectrum and/or an unlicensed spectrum.

Fundamentals

[003] Wireless communication systems are widely implemented to provide various telecommunications services, such as telephony, video, data, messaging and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, frequency division multiple access (FDMA) systems, frequency division multiple access systems (OFDMA), single carrier frequency division multiple access systems (SC-FDMA), and time division synchronous code division multiple access systems (TD-SCDMA).

[004] These multiple access technologies have been adopted in various telecommunications standards for the provision of a common protocol that allows different wireless devices to communicate on a municipal, regional, regional, and even global level. An example of a telecommunications standard is the Long Term Evolution (LTE) LTE is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership (3 GPP) project LTE is designed to support mobile broadband access through improved spectral efficiency, reduced costs, and enhanced services using OFDMA on the downlink, SC-FDMA on the uplink, and multiple-input multiple-output (MIMO) antenna technology. However, as demand for mobile broadband access continues to increase, there is a need for additional improvements to LTE technology. These enhancements may also be applicable to other multiple access technologies and telecommunications standards that employ these technologies.

[005] Radio access network may include different types of cells. One cell can be used for communication in a licensed spectrum, while another cell can be used for communication in an unlicensed spectrum. Therefore, the use of different cell types can be improved by considering the characteristics of different cell types.

SUMMARY

[006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all aspects covered, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[007] Radio access network may include a primary cell that is used for communication in a licensed spectrum and a secondary cell that is used for communication in an unlicensed spectrum. When the load for data traffic is performed, a core network must distinguish data traffic over the primary cell from data traffic over the secondary cell. Furthermore, the core network must be able to determine which traffic is carried over which cell type (either primary or secondary) based on traffic characteristics. Additionally, because load can be different between two different cells based on load requirements, a mechanism is needed to differentiate the maximum aggregate bit rate values for primary cells and secondary cells.

[008] In one aspect of the description, a method, a computer-readable medium and an apparatus are provided. The apparatus may be a core network entity. The core network entity is connected to a radio access network (RAN) including a primary cell using licensed spectrum and a secondary cell using unlicensed spectrum. The core network entity determines an authorization for data traffic to be offloaded to the secondary cell based on data traffic characteristics. The core network transmits an authorization indication to the RAN.

[009] In one aspect, the apparatus may be a core network entity, where the core network entity is connected to a RAN including a primary cell using licensed spectrum and a secondary cell using unlicensed spectrum. The core network entity includes means for determining an authorization for data traffic to be offloaded to the secondary cell based on data traffic characteristics and means for transmitting an indication of the authorization to the RAN.

[0010] In one aspect, the apparatus may be a core network entity, where the core network entity is connected to a RAN including a primary cell utilizing licensed spectrum and a secondary cell utilizing unlicensed spectrum. The core network entity includes a memory and at least one processor coupled to the memory. At least one processor is configured to: determine an authorization for the data traffic to be offloaded to the secondary cell based on the data traffic characteristics, and transmit an indication of the authorization to the RAN.

[0011] In one aspect, a computer-readable medium that stores computer-executable code for wireless communication by a core network entity is provided, wherein the core network entity is connected to a RAN including a primary cell utilizing a licensed spectrum and a secondary cell using unlicensed spectrum. Computer-readable medium includes code: determining an authorization for data traffic to be offloaded to the secondary cell based on data traffic characteristics, and transmitting an indication of the authorization to the RAN.

[0012] In another aspect of the description, a method, a computer-readable medium, and an apparatus are provided. The device may be a core network entity. The core network entity is connected to a RAN including a primary cell using licensed spectrum and a secondary cell using unlicensed spectrum. The core network entity receives one or more packets from the RAN, where at least one of the one or more packets is marked with an indication associated with communication through the secondary cell. The core network entity determines a load operation based on one or more packets.

[0013] In one aspect, the apparatus may be a core network entity, where the core network entity is connected to a RAN including a primary cell utilizing licensed spectrum and a secondary cell utilizing unlicensed spectrum. The core network entity includes means for receiving one or more packets from the RAN serving the primary cell, wherein at least one of the one or more packets is marked with an indication associated with communication through the secondary cell, and means for determining a charging operation with based on one or more packages.

[0014] In one aspect, the apparatus may be a core network entity, where the core network entity is connected to a RAN including a primary cell utilizing licensed spectrum and a secondary cell utilizing unlicensed spectrum. The core network entity includes a memory and at least one processor coupled to the memory. At least one processor is configured to: receive one or more packets from the RAN, wherein at least one of the one or more packets is marked with an indication associated with communication through the secondary cell, and determine a charging operation based on one or more packages.

[0015] In one aspect, a computer-readable medium that stores computer-executable code for wireless communication by a core network entity is provided, wherein the core network entity is connected to a RAN including a primary cell utilizing a licensed spectrum and a secondary cell using unlicensed spectrum. The computer-readable medium includes code for: receiving one or more packets from the RAN, wherein at least one of the one or more packets is marked with an indication associated with communication through the secondary cell, and determining a charging operation based on one or more more packages.

[0016] In another aspect of the description, a method, a computer program product, and an apparatus are provided. The device may be a RAN entity. The RAN entity receives, from a core network, an authorization indication for data traffic to be offloaded to a secondary cell using unlicensed spectrum, where the authorization indication is based on data traffic characteristics. The RAN entity determines, based on the authorization indication, to communicate through at least one of a primary cell using licensed spectrum or the secondary cell using unlicensed spectrum, the primary cell and the secondary cell being included in a RAN.

[0017] In one aspect, the apparatus may be a RAN entity. The RAN entity includes means for receiving, from a core network, an indication for authorization for data traffic to be offloaded to a secondary cell using unlicensed spectrum, wherein the authorization indication is based on data traffic characteristics. , and means for determining, based on the authorization indication, communication through at least one of a primary cell using licensed spectrum or the secondary cell using unlicensed spectrum, the primary cell and the secondary cell being included in a RAN.

[0018] In one aspect, the apparatus may be a RAN entity, where the RAN entity includes a memory and at least one processor coupled to the memory. The at least one processor is configured to: receive, from a core network, an indication for authorization for data traffic to be offloaded to a secondary cell using unlicensed spectrum, where the indication for authorization is based on traffic characteristics of data, and determine based on the authorization indication, to communicate through at least one of a primary cell using licensed spectrum or the secondary cell using unlicensed spectrum, the primary cell and the secondary cell being included in a RAN .

[0019] In one aspect, a computer-readable medium that stores computer-executable code for wireless communication by a RAN entity is provided. The machine-readable medium includes code to: receive, from a core network, an indication for authorization for data traffic to be offloaded to a secondary cell using unlicensed spectrum, where the indication for authorization is based on traffic characteristics of data, and determine based on the authorization indication, to communicate through at least one of a primary cell using licensed spectrum or the secondary cell using unlicensed spectrum, the primary cell and the secondary cell being included in a RAN .

[0020] In another aspect of the description, a method, a computer program product and an apparatus are provided. The device may be a RAN entity for a RAN that includes a primary cell using licensed spectrum and a secondary cell using unlicensed spectrum. The RAN entity marks at least one of one or more packets by adding an indication associated with communication through the secondary cell. The RAN entity transmits at least one of one or more packets to a central network.

[0021] In one aspect, the apparatus may be a RAN entity for a RAN that includes a primary cell utilizing licensed spectrum and a secondary cell utilizing unlicensed spectrum. The RAN entity includes means for marking at least one of one or more packets by adding an indication associated with communication through the secondary cell, and means for transmitting the at least one of one or more packets to a core network.

[0022] In one aspect, the apparatus may be a RAN entity for a RAN that includes a primary cell utilizing licensed spectrum and a secondary cell utilizing unlicensed spectrum. The RAN entity includes a memory and at least one processor coupled to the memory. The at least one processor is configured to: mark at least one of one or more packets by adding an indication associated with communication through the secondary cell, and transmit the marked at least one of one or more packets to a central network.

[0023] In one aspect, a computer-readable medium that stores computer-executable code for wireless communication by a RAN entity to a RAN is provided, wherein the RAN includes a primary cell utilizing the licensed spectrum and a secondary cell utilizing the licensed spectrum. unlicensed spectrum. Computer-readable medium includes code: marking at least one of one or more packets by adding an indication associated with communication through the secondary cell, and transmitting the at least one of one or more packets to a core network.

[0024] In carrying out the foregoing and related purposes, the one or more aspects comprise the characteristics hereinafter fully described and particularly pointed out in the claims. The following description and the attached drawings present in detail certain illustrative aspects of one or more aspects. These features are indicative, however, of only some of the various ways in which principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network.

[0026] Figures 2A, 2B, 2C and 2D are diagrams illustrating LTE examples of a DL frame structure, DL channels within the DL frame structure, a UL frame structure, and UL channels within the frame structure of UL, respectively.

[0027] Figure 3 is a diagram illustrating an example of an evolved Node B (eNB) and user equipment (UE) in an access network.

[0028] Figure 4 is an example diagram illustrating a network architecture including a primary cell and a secondary cell.

[0029] Figure 5 is an example diagram illustrating a fastening procedure in accordance with an aspect of the invention.

[0030] Figure 6 is an example diagram illustrating a standard EPS carrier activation procedure in accordance with an aspect of the disclosure.

[0031] Figure 7 is an example diagram illustrating a dedicated EPS carrier activation procedure in accordance with an aspect of the disclosure.

[0032] Figure 8 is an example diagram illustrating an EPS carrier modification procedure in accordance with an aspect of the disclosure.

[0033] Figure 9 is an example diagram illustrating a service request procedure in accordance with an aspect of the invention.

[0034] Figure 10 is an example diagram illustrating explicit marking according to the second disclosure approach.

[0035] Figure 1 is a flowchart of a wireless communication method, in accordance with one aspect of the disclosure.

[0036] Figure 12 is a flowchart of a wireless communication method, expanding from the flowchart of Figure 1.

[0037] Figure 13 is a flowchart of a wireless communication method, in accordance with one aspect of the disclosure.

[0038] Figure 14 is a flowchart of a wireless communication method, expanding from the flowchart of Figure 1.

[0039] Figure 15 is a conceptual data flowchart illustrating the flow of data between different modules/media/components in an exemplary apparatus.

[0040] Figure 16 is a diagram illustrating an example of a hardware implementation for a device that employs a processing system.

[0041] Figure 17 is a flowchart of a wireless communication method, in accordance with one aspect of the disclosure.

[0042] Figure 18 is a flowchart of a wireless communication method, expanding from the flowchart of Figure 17.

[0043] Figure 19 is a flowchart of a wireless communication method, in accordance with one aspect of the disclosure.

[0044] Figure 20 is a flowchart of a wireless communication method, expanding from the flowchart of Figure 19.

[0045] Figure 21 is a conceptual data flowchart illustrating the flow of data between different modules/media/components in an exemplary apparatus.

[0046] Figure 22 is a diagram illustrating an example of a hardware implementation for a device that employs a processing system.

DETAILED DESCRIPTION

[0047] The detailed description presented below in connection with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a complete understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0048] Various aspects of telecommunications systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements") These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0049] By way of example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems in one chip (STC), baseband processors. Field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this description. One or more processors in the processing system may execute software. Software shall be interpreted broadly to mean instructions, sets of instructions, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads execution, procedures, functions, etc. 0, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0050] Consequently, in one or more exemplary embodiments, the described functions can be implemented in hardware, software, or any combination thereof. If implemented in software, functions may be stored in or encoded as one or more instructions or code in a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer readable media may comprise a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage , magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0051] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, and an Evolved Packet Core (EPC) 160. Base stations 102 may include macro cells (high power cellular base station) and/or small cells (low power cellular base station). The macro cells include eNBs. Small cells include femto cells, pico cells and micro cells.

[0052] The base stations 102 (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN)) interface with the EPC 160 via intermediate link 132 (e.g., SI interface) . In addition to other functions, the base stations 102 may perform one or more of the following functions: user data transfer, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g. handover, connectivity dual), inter-cell interference coordination, connection and connection release, load balancing, distribution to non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, Service Multicast Multimedia Broadcast (MBMS), subscriber and equipment trace, RAN information management (RIM), alerting, positioning and warning message delivery. Base stations 102 may communicate directly or indirectly (e.g., via EPC 160) with each other via intermediate link 134 (e.g., X2 interface). Backhaul links 134 may be wired or wireless .

[0053] The base stations 102 may communicate wirelessly with the UEs 104. Each of the base stations 102 may provide communications coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include Evolved Home Nodes (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). Communication links 120 between base stations 102 and UEs 104 may include uplink (UL) (also referred to as reverse link transmissions) from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link transmission) from a base station 102 to a UE 104. Communication links 120 may utilize MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmission diversity. Communication links can be through one or more transporters. The base stations 102/UEs 104 may utilize spectrum up to 7 MHz (e.g., 5, 10, 15, 20 MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x carrier components). used for transmission in each direction. Carriers may or may not be adjacent to each other Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL) Component carriers may include a component carrier primary and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (Pcell) and a secondary component carrier may be referred to as a secondary cell (SCell)

[0054] The wireless communications system may further include a Wi-Fi access point (AP) 150 communicating with Wi-Fi stations (STAs) 152 via communication links 154 in an unlicensed 5 GHz frequency spectrum When communicating in an unlicensed frequency spectrum, the STAs 152/AP 150 may perform a clear channel assessment (CCA) before communicating for the purpose of determining whether the channel is available.

[0055] The small cell 102' may operate in a licensed and/or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ LTE and use the same unlicensed 5 GHz frequency spectrum as used by the Wi-Fi AP 150. The Small Cell 102', employ LTE in a spectrum unlicensed frequency band, may increase coverage for and/or increase the capacity of the access network. LTE in an unlicensed spectrum, referred to as LTE-unlicensed (LTE-U), licensed assisted access (LAA), or MuLTEfire.

[0056] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Service gateway 166, a Multicast Broadcast Multimedia Service (MBMS) gateway 168, a Multicast Broadcast Service Center (BM- SC) 170, and a Packet Data Network (PDN) Connection Point 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides carrier and connection management. All user Internet Protocol (IP) packets are transferred through the Service Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service (PSS), and/or others IP services. The BM-SC 170 can provide functions for the provision and provision of MBMS user services. The BM-SC 170 can serve as an entry point for the content provider's MBMS transmission, can be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and can be used to schedule MBMS transmissions . The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multiple Frequency Single Frequency Network (MBSFN) broadcast area of a particular service, and may be responsible for session management (downtime). start) and to collect MBMS-related load information.

[0057] The base station may also be referred to as a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, radio transceiver, a transceiver function, a set of services basic services (BSS), an extended service set (ESS), or some other suitable terminology. The base station 102 provides an access point for the EPC 160 to a UE 104. Examples of UEs 104 include a cell phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet , a smart device, a useful device, or any other similarly functioning device. The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a telephone handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0058] Referring back to Figure 1, in certain aspects, the UE 104/eNB 102 may be configured to determine whether a given data may be offloaded to the UE a secondary cell for unlicensed spectrum communication and/or to mark packets with an indication that provides information about a cell that was used to communicate the packet (198).

[0059] Figure 2A is a diagram 200 illustrating an example of a DL LTE frame structure. Figure 2B is a diagram 230 illustrating an example of channels within the DL frame structure in LTE. Figure 2C is a diagram 250 illustrating an example of a UL frame structure in LTE. Figure 2D is a diagram 280 illustrating an example of channels within the UL frame structure in LTE. Other wireless communication technologies may have a different frame structure and/or different channels. In LTE, a frame (10 ms) can be divided into 10 equally sized subframes. Each subframe can include two consecutive time slots. A resource grid can be used to represent the two time windows, each time partition including one or more blocks of concurrent time resources (RBs) (also referred to as physical Rsbs (PRBs)). Resource elements (REs). In LTE, for a normal cyclic prefix, an RB contains 12 consecutive sub-carriers in the frequency domain and 7 consecutive symbols (for DL, OFDM symbols; for UL symbols, SC-FDMA) in the time domain, for a total of 84 REs for an extended cyclic prefix, an RB contains 12 consecutive sub-carriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs, the number of bits carried by each RE depends on the modulation scheme.

[0060] As illustrated in Figure 2A, some of the REs carry DL (pilot) reference signals (DL-RS) for channel estimation in the UE. The DL-RS may include cell-specific reference signals (CRS) (also sometimes called common RS), UE-specific reference signals (UE-RS), and channel state information reference signals (CS1-RS). ). Figure 2A illustrates the CRS for antenna ports 0, 1, 2, and 3 (denoted as R0, R1, R2, and R3, respectively), UE-RS for antenna port 5 (denoted as R5), and CS1 -RS to antenna port 15 (denoted as R). Figure 2B illustrates an example of multiple channels within a DL subframe of a structure. The physical control format indicator channel (PCFICH) is within symbol 0 of partition 0, and carries a Control Format Indicator (CFI) that indicates whether the physical downlink control channel (PDCCH) occupies 1, 2, or 3 symbols (Figure 2B illustrates a PDCCH that occupies 3 symbols) The PDCCH carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including nine RE Groups (REGs), each REG including four Consecutive groups in one OFDM Symbol. A UE can be configured with a UE-specific enhanced PDCCH (ePDCCH) that also ports DCI. The ePCCH can have 2, 4, or 8 RB pairs (Figure 2B shows two RB pairs, each subset including one RB pair) The physical hybrid automatic repeat request (ARQ) (HARQ) indicator channel (PHICH) is also within of symbol 0 of partition 0 and carries the HARQ Indicator (Hl) which indicates HARQ acknowledgment (ACK)/negative ACK (NACK) feedback based on the physical uplink shared channel (PUSCH). The primary synchronization channel (PSCH) is within symbol 6 of partition 0 within subframes 0 and 5 of a frame, and carries a primary synchronization signal (PSS) that is used by a UE to determine subframe timing and a physical layer identity. The secondary synchronization channel (SSCH) is within symbol 5 of partition 0 within subframes 0 and 5 of a frame, and carries a secondary synchronization signal (SSS) that is used by a UE to determine an identity group number of physical layer cell. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH) is within symbols 0,1,2, 3 of partition 1 of substructure 0 of a structure, and carries a master information block (MIB). The MIB provides a number of RBs in width DL system bandwidth, a PHICH configuration, and a system frame number (SFN). The physical downlink shared channel (PDSCH) carrying user data carries broadcast system information not transmitted through the PBCH, such as system information blocks (SIBs) and alert messages.

[0061] As illustrated in Figure 2C, some of the REs carry demodulation reference signals (DM-RS) for channel estimation in the eNB. The UE may additionally transmit sound reference signals (SRS) in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS in one of the combs. The SRS can be used by an eNB for channel quality estimation to enable frequency-dependent scheduling in the UL. Figure 2D illustrates an example of multiple channels within a UL subframe of a structure. A physical random access channel (PRACH) can be within one or more subframes within a frame based on the PRACH configuration. The PRACH can include six consecutive RB pairs within a subframe. PRACH allows the UE to perform initial system access and obtain UL Synchronization. A physical uplink control channel (PUCCH) can be located at the bandwidth edges of the UL system. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a classification indicator (RI), and ACK/NACK HARQ feedback. The PUC transports the data, and can additionally be used to transport a temporary storage status report (BSR), a power header report (PHR), and/or UCI.

[0062] Figure 3 is a block diagram of an eNB 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control layer (RLC), and a medium access control (MAC) layer. Controller/processor 375 provides RRC layer functionality associated with disseminating system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, modifying of RRC connection, and RRC connection release), radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (encryption, Integrity Protection decryption, integrity checking), and transfer support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC Data PDUs, and reordering of RLC Data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs over transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling scheduling information, error correction via HARQ, handling priority, and logical channel prioritization.

[0063] The transmit (TX) processor 316 and the receiver (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) encoding/decoding of transport channels, interleaving, rate matching, mapping onto physical channels, physical channel modulation/demodulation and MIMO antenna processing. The TX 316 processor handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M phase shift keying ( M-PSK), M-quadrature amplitude modulation (M-QAM)) The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g. Pilot) in the time and/or frequency domain and then combined together using an Inverse Fourier Transform (IFFT) to produce a physical channel that carries a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-coded to produce multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate TX transmitter 318. Each 318 TX transmitter can modulate an RF carrier with a respective spatial flow for transmission.

[0064] In the UE 350, each RX receiver 354 receives a signal through its respective antenna 352. Each RX receiver 354 recovers information modulated by an RF carrier and provides the information to the receive processor (RX) 356. The TX processor 368 and RX 356 processor implements layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX 356 processor then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. . The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 310. These soft decisions can be based on channel estimates computed by the channel estimator 358. soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 310 on the physical channel. Data and control signals are then provided to controller/processor 359, which implements Layer 3 and Layer 2 functionality.

[0065] The controller/processor 359 may be associated with a memory 360 that stores program codes and data. Memory 360 may be referred to as a computer-readable medium. In UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 also is responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[0066] Similar to the functionality described in connection with DL transmission by eNB 310, controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and reporting. measurement; PDCP layer functionality associated with header compression/decompression, and security (encryption, decryption, integrity protection, integrity checking); RLC layer functionality associated with transferring upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC Data PDUs, and reordering of RLC Data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs into TBs, demultiplexing MAC SDUs from TBs, information scheduling information, error correction via HARQ, priority handling, and data prioritization. logical channel.

[0067] Channel estimates derived by a channel estimator 358 from a reference or return signal transmitted by the eNB 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 can be provided to different antenna 352 through separate TX transmitters 354. Each 354 TX transmitter can modulate an RF carrier with a respective spatial flow for transmission.

[0068] The UL transmission is processed in the eNB 310 in a manner similar to that described in connection with the receiver function in the UE 350. Each receiver 318 RX receives a signal through its respective antenna 320. Each receiver 318 RX recovers information modulated in an RF Carrier and provides information to an RX 370 Processor.

[0069] The controller/processor 375 may be associated with a memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. In UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to retrieve IP packets from the UE 350. IP packets from the controller /processor 375 may be provided for the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[0070] A UE may be connected to a primary cell providing licensed access (e.g., in a licensed spectrum) and a secondary cell providing unlicensed access (e.g., in an unlicensed spectrum). In particular, the UE may be connected to a primary cell providing communication over a licensed frequency band, for example, an LTE frequency band, and a secondary cell providing communication over an unlicensed frequency band, for example, a WiFi frequency band. For example , the UE can be connected to a RAN that includes the primary cell and the secondary cell. In one example, the RAN may include an eNB that supports LTE communication. For licensed access in the primary cell and Unlicensed LTE (e.g. LTE-U) for unlicensed access in the secondary cell. In another example, the RAN may include an eNB for cellular communication for licensed access in the primary cell and a wireless local area network (WLAN) router for unlicensed access in the secondary cell.

[0071] Figure 4 is an example diagram 400 illustrating a network architecture including a primary cell and a secondary cell. The UE 402 is connected to a RAN 404 including a primary cell 406 for licensed access and a secondary cell 408 for unlicensed access. In particular, the UE 402 may be connected to both the primary cell 406 and the secondary cell 408 406. The primary cell 406 communicates with the EPC (e.g., core network) 410 that includes an MME 412, other MMEs 414, a communication port (S-GW) 416, a PDN Gateway (P-GW) 418, and an HSS 420. In particular, the primary cell 406 communicates with the MME 412 via an S1-MME interface, and communicates with service port 416 via an S1-U interface. It is observed that the S1-MME interface provides an interface with a control plane, and the S1-U interface provides an interface with a user plane. The MME 412 communicates with the service port 416 through the A SI interface, and the service port 416 communicates with the PDN Gateway 418 through the A S5 interface. The MME 412 communicates with the HSS 420 via an S6a interface. The EPC 410 communicates with the IP Services 422. In particular, the PDN Gateway 418 communicates with the IP Services 422 via an SGi interface.

[0072] In network architecture such as the architecture illustrated in Figure 4, packets of a service data stream (SDF) on a carrier may be communicated over the primary cell and/or over the secondary cell, or some packets from the SDF can be carried on the primary cell while other SDF packages can be transported on the secondary cell. Each SDF can carry a different type of service. For example, one SDF may carry data associated with a video stream, and another SDF may carry data associated with the voice-over-IP call. The UE 402 may receive multiple SDFs through the RAN 404. The eNB (e.g., the eNB serving the primary cell) may decide which packets are communicated through the primary cell and which packets are communicated through the secondary cell. The decision whether packets are sent through the primary cell or the secondary cell may depend on several factors such as load conditions, radio conditions, local policies, visited network policies, etc. of the primary cell and the secondary cell. The eNB serving the primary cell can determine which packets should be transported over the primary cell and which packets should be transported over the secondary cell. The eNB (e.g. eNB serving the primary cell) may also decide how to communicate some data packets through the secondary cell based on (e.g. based on an algorithm)

[0073] The core network generally performs traffic loading and traffic loading in such a way that an operator (e.g., the UE) can differentiate when data packets are communicated through the primary cell and when data packets are communicated through the secondary cell. In particular, traffic policing is concerned with providing authorization under which data traffic (e.g., packets from an SDF) is permitted to be communicated as well as conditions under which data traffic is permitted to be communicated. Traffic loading includes generating load information so that the core network can load the operator based on the amount of data traffic transmitted and how the data traffic is routed. Note that when the operator uses a secondary cell with unlicensed access, the operator may be loaded differently than in a case where the operator uses a primary cell with licensed access (e.g., due to difference in operator policy or requirements regulators)

[0074] When the core network performs a loading function, the core network may consider several factors including an air interface (data plane) offloading using secondary cell to carry data traffic through the secondary cell, a core network that offloads into local network in the secondary cell, and a control plane signaling that is communicated via LTE to provide UE service using the secondary cell. Furthermore, one or more loading models such as volume loading and time loading can be used. In particular, according to the volumetric load, the operator may be loaded (e.g., by the core network) based on a quantity of data (e.g., a number of packets) transmitted through the primary cell and a quantity of data transmitted through the secondary cell, for each of the uplink communications and downlink communications. According to the time load, the operator is loaded (e.g. by the core network) based on a connectivity duration over the primary cell and a connectivity duration over the secondary cell. In one aspect, the operator may be loaded for duration of connectivity through the primary cell for licensed access, and may not be loaded for duration of connectivity through the secondary cell for unlicensed access. Thus, for example, the operator cannot be loaded for a connectivity duration in accordance with the present invention connectivity on the secondary cell exists and connectivity on the primary cell does not exist, but it can be loaded for a connectivity duration when connectivity exists on the primary cell. Therefore, when the core network performs the loading function, the core network needs to distinguish the data traffic over the primary cell from the data traffic over the secondary cell. For purposes of illustration but not limitation, the primary cell described herein operates in a licensed spectrum and the secondary cell described herein operates in an unlicensed spectrum.

[0075] The core network may perform a policing function to manage how the core network determines which traffic is carried over which type of cell (whether the primary cell or the secondary cell). Policing may be, for example, based on characteristics. of traffic. The following factors may need to be considered in relation to the policing function. According to one factor, considering the specific cell characteristics rules, the core network must be able to manage how the eNB provides access through the primary cell and secondary cell to the UE, based on the cell characteristics of each cell. For example, the core network may determine a percentage (e.g., a maximum cap or a minimum cap) of bytes of data to be communicated about each cell and/or may determine a percentage (e.g., a maximum cap or a minimum cap) of bytes of data to be communicated on the downlink and/or to be communicated on the uplink, for each cell. According to another factor, the core network must be able to impose different guidelines for specific devices depending on whether a cell with a certain cell characteristic (e.g., unlicensed spectrum) is available or not. For example, if a maximum coverage for data over the licensed spectrum is reached, the P-GW may decide whether to disable the carrier or block subsequent data traffic (e.g., UL/DL traffic) depending on whether the UE is connected to a secondary cell providing unlicensed access (e.g. LTE-U or aggregation over WLAN) If the secondary cell is available and maximum coverage over the licensed spectrum is achieved, P-GW may instruct (e.g. based on a policy) that all subsequent data traffic must be scheduled over the secondary cell in the unlicensed spectrum. Thus, the P-GW may need to receive information as to whether communication over unlicensed spectrum is available or not in order to enforce policy rules accordingly. According to another factor, the core network (e.g., a policy and rule loading function (PCRF)) must provide guidelines based on whether a cell with a certain cell characteristic (e.g., unlicensed spectrum) is available to the device.

[0076] The S1-U interface may not contain separate explant tunnels for data to be communicated through the primary cell and for data to be communicated through the secondary cell. Thus, a tunnel provided by S1-U may not distinguish whether data is communicated through the primary cell or the secondary cell. Additionally, billing data records (CDRs) can be created on the core (S-GW/P-GW) network elements (e.g., not on the RAN). The eNB can generate some information to help the core network create CDRs. CDRs can be used to charge the UE user for a communicated amount of data traffic. Because CDRs may not be created in the RAN, the RAN may not be able to provide information about whether the communication is related to using the primary cell or using the secondary cell. Because the core network does not currently know which data is communicated through the primary cell or the secondary cell, the core network may not be able to perform the upload correctly. CDR containers can be opened or closed when the UE user location information (ULI) changes. For example, when a UE location changes and thus the ULI changes, the UE opens or closes CDR containers based on whether the UE is operating over licensed spectrum or unlicensed spectrum. If the UE is operating over unlicensed spectrum, the UE closes the CDR containers to avoid overloading, and when the UE is in LTE, the UE opens the CDR containers to start charging.

[0077] The maximum Aggregate bit rate (ABR) of the UE can be considered for communication over the primary cell and/or the secondary cell. The ABR is a per-UE value that is provided by the core network to the RAN (e.g., to the eNB), so that the eNB can use the ABR to enforce the total maximum bitrate for all bitrate bearers. not guaranteed (non-GBR). For example, the MME may transmit the UE-ABR for each Radio Access Technology (RAT) in the e-UTRAN radio access bearer (e-RAB) messages. The core network can provide one ABR value for either the primary cell or the secondary cell, rather than providing two separate ABR values, an AMBE value for communication over the primary cell and an ABR Value for communication over the secondary cell. Since charging may be performed differently for different cell types (e.g., based on charging requirements), a mechanism is needed to differentiate ABR values for primary cells and secondary cells. Method, for example, a different one from another cell, the ndro network develops different ABR Valmines for the two different cells. Furthermore, the UE can use DL communications in one RAT (e.g., a secretariat) and UL communications in another RAT (e.g., a primary cell). In such a case, a mechanism is needed to provide separate AMBR values for UL communication and for DL communication. For example, DL communication can be used in the secondary cell to receive primary data, and UL communication can be used in the primary cell to transmit control signals to the core network. It is noted that AMBRs may be included in the mandatory fields in the INITIAL CONTEXT ADJUSTMENT REQUEST message and may be optional in an E-RAB CONFIGURATION REQUEST, and E-RAB MODIFICATION REQUEST, or an E-RAB RELEASE COMMAND. RAB.

[0078] Some Problems associated with charging can be addressed by having the eNB perform separate accounting and reporting of a volume of data transmitted from the primary cell and a volume of data transmitted from the secondary cell (e.g., by counting a number of packets communicated over the primary cell, and a number of packets communicated over the secondary cell). The report can be reported using the control plane or the user plane. Process for using a plane-type control system, the eNB provides a count information of the number of packets through the MME to the service port and then the service port sends the information from PDN Gateway A to the CDR Service Gateway and a Gateway PDN CDR can be extended to include explicit account information for data volumes about the primary cell and the secondary cell. In another approach using the control plane, the eNB provides accounting information to the Service Port directly through the S1-U interface via a separate General Packet Radio Service (GPRS) tunneling protocol for the messages. control plane (GTP-C) and then the Service Port passes forward account information to the PDN port, with a Service Port CDR and a PDN Gateway CDR extended to include explicit account information for data volumes over the primary cell and the secondary cell. In yet another approach using the control plane, the eNB reports data volumes in the primary cell and/or a secondary cell directly to a Load Port Function (CGF) using an eNB CDR or directly to a Data Function. (CDF) if a CRD eNB is not included in the eNB. The CGF or some other billing entity may correlate a Service Port CDR, a PDN Gateway CDR, and an eNB CDR (e.g. to provide charging consistency). Additionally, in a user plane approach, the eNB can provide account information to the Service Port directly over the S1-U interface (e.g., in the GPRS tunneling protocol for user plane tunneling (GTP). -U) as a part of new header extensions for the carrier or separate GTP-C messages).

[0079] If charging per data stream (for example, by SDF) is carried out on the PDN port, the eNB must perform accounting of the data volume per data stream. However, the eNB may not be aware of the data flows. Therefore, the eNB can be aware of data flows, either via direct configuration when a carrier is established or through user plane packet marking performed on the PDN port. A PDN Gateway can mark packets by including a certain traffic flow identifier in each packet header.

[0080] In particular, it may be desirable for the core network (e.g., Home Public Land Mobile Network (HPLMN)) to retain control of whether data traffic from a given device can be offloaded to the secondary cell (e.g. , of the primary cell) it may also be desirable for the core network to retain control of the type of data traffic and/or what amount of data traffic can be offloaded to the secondary cell. Thus, according to the description, instead of relying on the eNB for authorization and accounting decisions, the core network can be configured to make authorization and accounting decisions. The core network may be configured to determine whether data traffic from a given device can be offloaded to the secondary cell (e.g., the primary cell). To implement such authorization and accounting decisions, the core network must be able to indicate to the RAN whether specific data traffic can be offloaded to the secondary cell (or whether aggregation of data traffic is permitted) in accordance with a first approach. Upon disclosure, the core network is configured to make authorization decisions for data flow and/or data traffic to a primary cell and to a secondary cell, and such authorization decision is passed to a PDN port. The core network can make the authorization decision using a policy and load control (PCC) function. The MME may modify the authorization decision and/or may add additional guidelines (e.g., for authorization and/or accounting), based on a UE signature profile. The authorization decision can be combined with OAM information (for example, because OAM information can provide real-time conditions in the network, such as congestion, load shedding, etc.). The first disclosure approach may consider at least one of a Quality of Service (QoS) class indicator, PCC-originated information, P-GW-originated information, MME-originated information, or OAM-originated information.

[0081] According to a first aspect of the first approach, a new QoS class identifier (QCI) can be introduced for data streams communicated over unlicensed spectrum (unlicensed access data streams). When an SDF is created in the core network, the core network assigns a QCI to the SDF to indicate what quality of service should be provided to the SDF. In addition to a QCI that is conventionally used, the first aspect of the first approach defines a new QCI Value that a core network can assign to an SDF if the SDF is allowed/requested to be offloaded to the secondary cell. Thus, the core network assigns the new QCI value to the SDF-T and/or data traffic that the core network authorizes to offload to the secondary cell. Based on the new QCI value, the RAN (e.g. eNB) determines which data traffic can be offloaded to a secondary cell.

[0082] Several options may be available to implement the first aspect of the first approach to utilizing the new QCI. According to a first option of the first aspect of the first approach, the core network assigns, as a new QCI, a separate QCI called an Unlicensed access QCI to an SDF, to indicate that the core network authorizes the data stream to be downloaded. to a secondary cell (e.g. where the separate QCI is distinct from a conventional QCI). For example, if the RAN detects unlicensed QCI access assigned to the SDF, the RAN MAY determine to offload the RAN SDF to the secondary cell. On the other hand, if the RAN detects a (conventional) QCI assigned to the SDF, the RAN may determine not to offload the SDF to the secondary cell. Referring back to Figure 4, for example, the EPC 410 may transmit the conventional QCI and/or the Unlicensed access QCI to the RAN 404 (e.g., to the eNB for the primary cell 406) and the RAN 404 may subsequently determine The SDF is downloaded to the secondary cell 408 based on whether unlicensed QCI is received or Conventional QCI is received to the SDF. QCI unlicensed access can specify whether download to the SDF applies to UL communication, DL communication, or UL and DL communication to the SDF. In one aspect, the eNB (e.g. eNB for primary cell406) determines based on unlicensed QCI access that the SDF is authorized to be downloaded to the secondary cell (e.g. secondary cell. And determines whether to download the SDF to the secondary cell, According to another aspect, unlicensed access QCI Indicates that the core network (e.g., EPC. Requests that the data stream be offloaded to the secondary cell (e.g., secondary cell 408) whenever the secondary cell is available. In this regard, the eNB downloads SDFs with unlicensed QCI access each time a secondary cell is available and radio conditions allow such download.

[0083] According to a second option of the first aspect of the first approach, rather than implementing a separate unlicensed access QCI, the (conventional) QCI is increased to include a new QCI Value that indicates the load capacity for the cell secondary. Thus, when the core network authorizes offloading of a specific SDF to the secondary cell, the core network can assign a new QCI value to the specific SDF and include the new QCI Value in the QCI to indicate offload capability to the secondary cell. Reference back to Figure 4, for example, the EPC 410 may include the new QCI value in the QCI to indicate the offload capability for the secondary cell 408, and transmit the QCI including the new QCI Value to the RAN 404 (e.g., to the eNB to the primary cell 406). The new QCI value in QCI can specify whether offloading to the SDF applies to UL communication, DL communication, or UL and DL communication to the SDF. In one aspect, the new QCI value may indicate that the eNB (e.g., eNB for primary cell 406) may offload the SDF to the secondary cell (e.g., secondary cell 408). In another aspect, the new QCI value may indicate that the eNB (e.g., eNB for primary cell 406) should download the SDF to the secondary cell (e.g., secondary cell 408) whenever the secondary cell is available. In one aspect, the core network may assign the new QCI to different data streams based on whether the core network allows the data streams to be loaded/aggregated over the secondary cell or not.

[0084] According to a second aspect of the first approach, the core network provides an explicit indication of authorization for download (offload)) to the secondary cell via the PCC and/or PDN port. PCC functionality may include a PCRF and a policy and load fulfillment function (PCEF). If the secondary cell is supported in the service network, the PCRF (visited-PCRF if roaming) provides an indicator via a Gx interface to the PCEF to indicate for each flow whether the secondary cell (for unlicensed access) can be or must be (e.g., is asked to be) used. For example, the PCRF provides the indicator to indicate that data traffic is allowed for download or the traffic is requested to be downloaded. The PCRF creates and sends an Application Detection and Control (ADC) Rule for a specific Differentiated Service Code Point (DSCP) indicating unlicensed access. After receiving the indicator information, the PCEF at the PDN Gateway marks the carrier(s) with an indication that the data traffic can be offloaded or must be uploaded to the secondary cell for unlicensed access. The PCEF can mark each carrier with a new indication. Process for preparing a workpiece (EPS) carrier QoS information. Marking can be performed via the path to the eNB. The eNB can use information in the old tag to determine whether certain data traffic can be downloaded or should be loaded.

[0085] Figure 5 is an example diagram 500 illustrating a clamping procedure in accordance with the second aspect of the first approach of the description. Initially, a UE registers with the core network to receive services that require registration through a pinning procedure. Example diagram 500 shows interactions between the UE 502, an eNB 504, a new MME 506, an old MME/SGSN 508, an Equipment Identity Register (EIR) 510, an S-GW 512, a P-GW 514 , a PCRF 516 and an HSS 518. In operation 1, the UE 502 sends an attach request to the eNB 504, which forwards the attachment request (operation 2) to a new MME 506. In response, in operation 3, the new MME 506 sends the identification request to the old MME/SGSN 508, which returns an identification response back to the new MME 506. If the UE 502 is unknown in both the old MME/SGSN 508 and the New MME 506, the new MME 506 sends an identity request to the UE 502, which returns an identity response to the new MME 506 (operation 4). In operation 5a, authentication and security establishment is performed between the UE 502 and the new MME 506 as well as the module between the new MME 506 and the HSS 518. In operation 5b, the new MME 506 recovers a mobile equipment (ME) identity of the UE 502 through the identity request/response procedure, and the new MME 506 subsequently checks the ME Identity with the EIR 510 to decide whether to continue with the pinning procedure. In operation 6, the UE 502 retrieves the cipher options from the New MME 506 by the cipher option request/response procedure

[0086] In operation 7, if there are active bearer contexts in the new MME 506 for the same UE 502, the new MME 506 deletes these active bearer contexts by sending a Session Cancel Request to the S-GW 512 and the P- GW 514, which acknowledges with a Session Cancel Response, and the PCEF on the P-GW 514 performs an IP Connectivity Access Network (IP-CAN) Session Termination Procedure with the PCRF 516 to indicate that resources have been released .

[0087] In operation 8, the new MME 506 may transmit a Location Update Request to the HSS 518. In operation 9, the HSS sends a Cancel Location message to the old MME/SGSN 508, which acknowledges with a message From Cancellation Location Cancellation and removes the bearer contexts. In operation 10, if there are active carrier contexts in the old MME/SGSN 508 to the UE 502, the old MME/SGSN 508 deletes these active carrier contexts by sending a delete request to the S-GW 512 and the P-GW 514 , which it acknowledges with a Session Cancel Response, and the PCEF in the P-GW 514 performs the request for an IP-CAN Session Termination procedure with the PCRF 516 to indicate that the resources have been released. In operation 11, the HSS 518 may acknowledge the Location Update Request by sending an Update Location Ack message to the new MME 506.

[0088] In operation 12, the new MME 506 selects the S-GW 512 and sends a Create Session Request to the S-GW 512. In operation 13, the S-GW 512 forwards the Create Session Request to the P-GW 514. In operation 14, the P-GW 514 performs an IP-CAN Session Establishment procedure, and thus obtains standard PCC rules for the UE 502. In operation 14, during IP-CAN Session Establishment/Modification CAN, the PCRF 516 sends to the P-GW 514 an ADC Rule for a specific DSCP indicating Unlicensed Access. In operation 15, the P-GW 514 returns a Session Creation Response to the S-GW 512, and the first downlink data may be communicated from the P-GW 514 to the S-GW 512. The P-GW 514 may authorize offload capability for the secondary cell to the carrier, and include an indication of offload capability. In the Create Session Request sent to the S-GW 512 in Operation 15 in Operation 16, the Create Session Response is sent to the new MME 506. The S-GW 512 may forward the offload capability indication through the session creation request sent to the new MME 506 in operation 16. In operation 17, the new MME 506 sends a context establishment request Initial to the eNB 504. The new MME 506 can send the download capacity indication to the eNB 504 through the Initial Context establishment request sent to the eNB 504, in operation 17.

[0089] In operation 18, the eNB 504 sends an RRC Connection Reconfiguration message including the EPS Radio Bearer Identity to the UE 502, and the Connection Accept message will be sent along the UE 502. In operation 19 , the UE 502 sends an RRC Connection Configuration Reconfiguration complete message to the eNB 504. In operation 20, the eNB 504 sends the Initial Context Response message to the new MME 506. In operation 21, the UE 502 sends a Direct Transfer message to the eNB 504, which includes a Connection Complete message. In operation 22, the eNB 504 sends the Connection Complete message to the new MME 506 in an Uplink NAS Transport Message, and then the first UL data can be communicated to the P-GW 514 through S-GW 512 .

[0090] In operation 23, upon receipt of both the Initial Context Response message in operation 20 and the Link Complete message in operation 22, the new MME sends a Modify Bearer Request Message to the S-GW 512. In operation 23a, if a Handover Indication is included in operation 23, the S-GW 512 sends a Modification Support Request message to the P-GW 514 to direct the P-GW 514 to tunnel packets to from the AT a non-3 GPP IP access system to a 3 GPP access system and immediately begin routing packets to the S-GW 512. In operation 23b, the P-GW 514 acknowledges by sending the Modification Bearer Response to the S-GW 512. In operation 24, the S-GW 512 acknowledges by sending the Modification Bearer Response message to the new MME 506. Then, the UE 502 can receive the first DL data from the UE P-GW 514 through the S-GW 512. In operation 25, the new MME 506 sends a Notification Request Including APN Identity and P-GW 514 to the HSS 518 for mobility with non-GPP 3 accesses, and then receives a Response from the HSS 518 of Notification.

[0091] Several different options are available for data programming according to the second aspect of the first approach. According to a first option for programming data according to the second aspect of the first approach, the P-GW can provide instructions/policies in programming the data about the secondary cell. Instructions can be provided per EPS carrier and/or per data stream. Instructions may be provided during standard EPS carrier activation and/or dedicated EPS carrier activation and/or dedicated/dedicated EPS carrier modification.

[0092] According to the first option for data programming, if instructions/policies on data programming about the secondary cell are provided during standard EPS carrier activation, the P-GW can receive specific EPS characteristic guidelines. cell from the PCRF, where the guidelines apply to both the primary cell and the secondary cell. P-GW decides certain cell characteristic specific usage rules (cell characteristic specific usage rules) based on the cell characteristic specific policies, and forward these cell characteristic specific usage rules to the eNB, (e.g. example, through S-GW and MME) cell characteristic specific usage rules can be defined for UL communication and DL communication separately. Cell characteristic-specific usage rules may include, for example, a desired percentage of a data quantity (e.g., 50%) transmitted through the secondary cell (in the unlicensed spectrum) relative to a data quantity transmitted through of the primary cell (in the licensed spectrum) Cell characteristic-specific usage rules may include a maximum amount of data (e.g., in bytes) allowed to be communicated through the primary cell. Once the eNB receives cell characteristic-specific usage rules, the eNB will then use these cell characteristic-specific usage rules to determine how the carrier is served. For example, if the carrier is not permitted for WLAN use, then the eNB may not initiate WLAN exchange to a corresponding UE when there are no permitted bearers for WLAN. Similarly if one or more carriers are enabled WLAN bearers, the eNB can initiate WLAN interworking for the Corresponding UE. An example of use for the first option for data programming is illustrated in Figure 6.

[0093] Figure 6 is an example diagram 600 illustrating a standard EPS carrier activation procedure in accordance with an aspect of the disclosure. Example diagram 600 shows interactions between the UE 602, an eNB 604, an MME 606, an S-GW 608, a P-GW 610, a PCRF 612, and an HSS 614. A standard carrier activation procedure can be activated by the UE 602 through a PDN connectivity request, which may be standalone or included in an attach request message during a pinning procedure. In operation 1, the UE 602 sends the PDN Connectivity Request to the MME 606. In operation 2, the MME 606 allocates a bearer identifier, and sends a Session Creation Request to the S-GW 608. In operation 3, the S-GW 608 forwards the Session Creation Request to the P-GW 610. In operation 4, the P-GW 610 performs the IP-CAN Session Establishment/Modification with the PCRF 612. Namely, during session establishment IP-CAN, the P-GW 610 can receive from the PCRF 612 cell characteristic specific policies that are available for the standard carrier. In operation 5, the P-GW 610 sends the Creation Response to the S-GW 608, and then the first DL data can be sent from the P-GW 610 to the S-GW 608. In particular, in operation 5, the P-GW 610 decides cell characteristic-specific usage rules based on the cell characteristic-specific policies received from the PCRF 612, and includes the cell characteristic-specific usage rules in the Creation Session Response to be sent to the S-GW 608. The P-GW 610 may include the cell characteristic-specific usage rules in a new information element for the cell characteristic-specific usage rules within the Session Creation Response. In operation 6, the S-GW 608 forwards the Session Creation Response to the MME 606. Thus, in operation 6, the S-GW 608 forwards the cell characteristic specific usage rules within the Session Creation Response to the MME 606. In operation 7, the MME 606. The specific cell feature usage rules to the eNB 604 through a Bearer Establishment Request message, and may also forward a PDN Connectivity acceptance message to the eNB 604. It is noted that subsequent operations including operations 8-16 can be performed in accordance with cell characteristic-specific usage rules.

[0094] In operation 8, the eNB 604 sends an RRC Connection Reconfiguration to the UE 602, where the RRC Connection reconfiguration may include the PDN Connectivity acceptance message, and in operation 9, the UE 602 sends the Reconfiguration of Complete RRC Connection to the eNB 604. In operation 10, the eNB 604 sends a Bearer Configuration Response to the MME 606. In operation 11, the UE 602 constructs a complete PDN Connectivity message including an EPS Bearer identity, and then sends a Direct Handover (PDN Connection Complete) message to the eNB 604. In operation 12, the eNB 604 sends an Uplink NAS Transport Network (PDN) message to the MME 606. Subsequently, when the UE obtains a PDN address information, the UE can send UL data to the eNB 604. The UP Data is then tuned to the S-GW 608 and P-GW 610.

[0095] In operation 13, upon receiving the Bearer Establishment Response message (e.g., in operation10) and the PDN Connectivity complete message (e.g., in operation12), the MME 606 sends a Modify Bearer Request to the S-GW 608. In operation 13a, if a Handover Indication is included in operation 13, the S-GW 608 sends a Modification Agent Request to the P-GW 610 to guide the P-GW 610 to tunnel packets from a non-T-3-T GPP IP to a 3 GPP access system and to initiate routing packets to S-GW 608 for standard EPS bearers and any established dedicated EPS bearers. In operation 13b, the P-GW 610 acknowledges by sending a Modification Bearer Response to the S-GW 608. In operation 14, the S-GW 608 acknowledges by sending a Modification Carrier Response to the MME 606. Then, The UE 602 can receive DL data from the P-GW 610 through the S-GW GW 608. After the MME 606 receives the Modification Carrier Response in Operation 14 and certain conditions are satisfied, the MME 606 in Operation 15 sends a Request Notification including P-GW address and APN for HSS 614 for mobility with 3 GPP accesses. In operation 16, the HSS 614 stores the P-GW identity and associated APN, and sends a Notification Response to the MME 606.

[0096] According to a second option for data programming, instructions can be provided during activation of the dedicated EPS carrier, as illustrated in Figure 7, for example. Figure 7 is an example diagram 700 illustrating a dedicated EPS carrier activation procedure in accordance with one aspect of the disclosure. The example diagram 700 shows the interactions between the UE 702, an eNB 704, an MME 706, an S-GW 708, a P-GW 710, and a PCRF 712. Operation 1, during IP-CAN Session Modification, the PCRF 712 provides cell characteristic specific policies for the dedicated carrier for the P-GW 710. In operation 2, the P-GW 710 sends the Creation Response to the S-GW 708. In particular, in operation 2, the P -GW 710 decides cell characteristic specific usage rules based on the cell characteristic specific policies received from the PCRF 712 and includes the cell characteristic specific usage rules in the Creation Session Response to be sent to the S- GW 708. The P-GW 710 may include the cell characteristic specific usage rules in a new information element for the cell characteristic specific usage rules within the Session Creation Response. In operation 3, the S-GW 708 forwards the Session Creation Response to the MME 706. Thus, in operation 3, the S-GW 708 forwards to the MS-cell specific usage rules characteristics within the Session Creation Response to the MME 706. In operation 4, the MME 706 forwards cell characteristic-specific usage rules to the eNB 704 via a Bearer Establishment Request Message, and may forward a Session Management Request to the eNB 704. It is noted that subsequent operations including operations 5-12 can be performed according to the cell characteristic specific usage rules.

[0097] In operation 5, the eNB 704 maps the EPS bearer QoS to the radio bearer QoS, and then sends an RRC Connection Reconfiguration message to the UE 702, and in operation 6, the UE 702 UE acknowledges radio bearer activation to the eNB 704 by sending an RRC Link Reset message to the eNB 704. In operation 7, the eNB 704 acknowledges carrier activation to the MME 706 by sending a Carrier Establishment response message to the MME 706. In operation 8, the UE 702 constructs a Session Management Response including the EPS Bearer Identity, and then sends a Direct Transfer message (including the Session Management Response) to the eNB 704. In operation 9, the eNB 704 sends the Administration Response Session to the MME 706. In operation 10, after receiving the Carrier Establishment Response message (in operation7) and the Session Management Response message (in operation9), the MME 706 confirms carrier activation to the S-GW 708 by sending a Create Bearer Response Message to the S-GW 708. In operation 11, the S-GW 708 confirms carrier activation to the P-GW 710 by sending a Create Carrier Response to the P-GW 710. In operation 12, the P-GW 710 performs the IP-CAN Modification procedure with the PCRF 712. For example, in operation 12, if the dedicated carrier activation procedure was triggered by a PCC Decision Provision message from the PCRF 712, the P-GW 710 indicates to the PCRF 712 whether the requested PCC decision (QoS Policy) could be enforced or not, allowing the termination of the PCC procedure. CAN IP Session Modification.

[0098] According to a third option for data programming, the P-GW may provide instructions for data programming during the EPS carrier modification procedure. The core network may initiate the EPS carrier modification procedure (e.g., with the RAN) due to changing policies or conditions regarding specific cell characteristic usage. For example, if the UE reaches a maximum data amount of licensed spectrum usage (e.g. based on the user's data plan), the core network may initiate the EPS bearer modification procedure to indicate to the eNB that the spectrum is not licensed spectrum may be used and licensed spectrum shall not be used. An example of use for the third option for data programming is illustrated in Figure 8.

[0099] Figure 8 is an example diagram 800 illustrating an EPS carrier modification procedure in accordance with an aspect of the invention. Example diagram 800 shows the interactions between the UE 802, an eNB 804, an MME 806, an S-GW 808, a P-GW 810, and a PCRF 812. In operation 1, the PCRF 812 initiates the Modification Procedure of EPS carrier by performing IP CAN session modification with the P-GW 810. For example, the PCRF 812 may send a PCC Decision Provision (QoS Policy) message to the P-GW 810 as initial operations of the EPS carrier modification procedure. In operation 2, the P-GW 810 determines (e.g., based on the QoS policy) that the authorized QoS of a service data stream has changed or not, and then sends the Update Bearer Request to the S-GW 808. Thus, in operation 2, the P-GW 810 performs an initial part of the carrier modification procedure, for example, to change cell characteristic-specific usage rules (e.g., based on the QoS policy from of PCRF 812). In operation 2, after the cell characteristic specific usage rules are changed, the P-GW 810 includes the cell characteristic specific usage rules in the Update Carrier Request for S-GW 808. In one aspect, the P -GW 810 may also include, in the Update Carrier Request, an indication to the UE 802 surrounding the change in cell characteristic specific usage rules. In operation 3, the S-GW 808 sends the Update Bearer Request to the MME 806, and thus transfers the cell characteristic-specific usage rules to the MME 806. In operation 4, the MME 806 forwards the usage rules specific cell characteristics to the eNB 804 via a Carrier Modification Request Message. It is noted that subsequent operations, including operations 5 to 12, can be performed according to the specific usage rules of cell characteristics.

[00100] In operation 5, the eNB 804 maps the modified EPS bearer QoS to the radio bearer QoS, and then sends an RRC Connection Reconfiguration message to the UE 802, and in operation 6, the UE 802 acknowledges activation of the radio bearer to the eNB 804 by sending an RRC Connection Configuration Reconfiguration message to the eNB 804. In operation 7, the eNB 804 acknowledges the carrier modification to the MME 806 by sending a Radio Modify Response message. Bearer to the MME 806. In operation 8, the UE 802 constructs a Session Management Response including the EPS Bearer Identity, and then sends a Direct Transfer message to the eNB 804. In operation 9, the eNB 804 sends a Session Management Response message to the MME 806. In operation 10, after receiving the Bearer Modification Response message (in operation 7) and the Session Management Response message (in operation 9), the MME 806 recognizes the carrier modification to the S-GW 808 by sending an Update Carrier Response Message to the S-GW 808. In operation 11, the S-GW 808 recognizes the carrier modification to the P-GW 810 by sending the Carrier Response Update carrier for the P-GW 810. In operation 12, the P-GW 810 performs the IP-CAN modification procedure with the PCRF 812. For example, in operation 12, if the carrier modification procedure was triggered by a PCC Decision Supply message from the PCRF 812, the P-GW 810 indicates to the PCRF 812 whether the same requested PCC decision (QoS policy) could be enforced or not, allowing the Session Modification procedure to complete CANIP.

[00101] In accordance with a third aspect of the first approach, the MME is configured to provide the cell characteristic-specific usage rules to the RAN as an explicit indication of the MME, as discussed above, the cell characteristic-specific usage rules cell can be applied per UE. Cell characteristic-specific usage rules may be based on subscription information received from the HSS and/or configuration information. The RAN may determine to match cell characteristic-specific usage rules. In more detail, according to the third aspect of the first approach, the MME provides the cell characteristic-specific usage rules during an S1-AP Context Establishment between the MME and the eNB for each UE. S1-AP context establishment is performed between the MME and the eNB when the UE is establishing a new connection with the eNB. The S1-AP context setting may be performed during at least one of a clamping procedure, a tracking area update procedure, a service request procedure, or a handover procedure (e.g., established between an eNB target and a target MME) the MME may provide cell characteristic-specific usage rules in the initial context establishment request sent from the MME to the eNB. Additionally, the MME may initiate a UE Context Modification Procedure to change cell characteristic-specific rules, for example, if the UE is transferred to a new area where different cell characteristic-specific rules apply.

[00102] Figure 9 is an example diagram 900 illustrating a service request procedure in accordance with the third aspect of the first approach of the description. Example diagram 900 shows interactions between the UE 902, an eNB 904, an MME 906, an S-GW 908, a P-GW 910, a PCRF 912 and an HSS 914. In operation 1, the UE 902 sends a NAS Message Service Request to the eNB 904, and in operation 2, the eNB 904 forwards the NAS Message Service Request to the MME 906. The NAS Message Service Request may be encapsulated in an EU-AP:UE message Home. In operation 3, authentication and security procedures are performed between the UE 902 and the MME 906, and the MME 906 and the HSS 914. In operation 4, the MME 906 sends an Initial Context Establishment Request from S1-AP to the eNB 904. In particular, in operation 4, the MME 906 provides the cell characteristic specific rules in the S1-AP Initial Context Establishment request to the eNB 904.

[00103] In operation 5, the eNB 904 performs the radio bearer establishment procedure with the UE 902. In operation 6, the eNB 904 sends UL data to the S-GW 908, which forwards the UL data to the P-GW 910. In operation 7, the eNB 904 sends an Initial Context Establishment S1-AP Complete message to the MME 906. In operation 8, the MME 906 sends a modification Bearer Request to the S-GW 908. In operation 9, if a certain change has occurred (e.g., in the RAT type or UE location), the S-GW 908 sends a Modification Bearer Request to the P-GW 910. In operation 10, the P- GW 910 interacts with the PCRF 912 to obtain the PCC Rules according to the RAT Type through a PCEF-Initiated CAN IP Session Modification Procedure. In operation 11, the P-GW 910 sends a Modification Carrier Response to the S-GW 908.

[00104] According to a fourth aspect of the first approach, the RAN can be configured (for example, by the core network) with the specific cell characteristic usage rule through the OAM function. In particular, the eNB can be configured with cell characteristic-specific usage rules at any point. Note that the RAN may determine to match specific cell characteristic usage rules.

[00105] A second approach to the invention addresses problems related to accounting and cargo. According to the description, loading (e.g. loading for communicated data) can be performed explicitly or implicitly. The explicit payload may be based on marking packets transported through the secondary cell or marking packets when the eNB does not need to perform any data volume reporting transmitted through the primary cell and/or the secondary cell. In one aspect, the RAN (e.g., the eNB) may provide explicit marking by marking packets with an indication that provides information as to whether the packet was communicated over the primary cell in the licensed spectrum or over the secondary cell in the unlicensed spectrum. . In particular, the RAN (e.g., the eNB) identifies which packets were transported via licensed access or via unlicensed access, and marks such packets accordingly. Tagging can be performed through the core network to create rules. The rules created can be a rule that packets in the DL would be communicated in the same way as the UL packet (either over the primary cell or the secondary cell), or a rule that defines specific loading and accounting instructions for packets with that marking. of DSCP in UL and DL Communication.

[00106] Figure 10 is an example diagram 1000 illustrating explicit marking according to the second approach of the description. Example diagram 1000 shows interactions between an eNB 1002, an S-GW 1004, a P-GW 1006, a traffic detection function (TDF) 1008, and a PCRF 1010. In operation 0 and operation 1, the eNB " mark" (e.g., via the S1-U interface) the GTP-U header of packets that were actually transported through the secondary cell by adding a new indication (e.g. Add a new Information Element to the GTR-U header) to indicate that packets were communicated through the secondary cell. Thus, in operation 1, a packet with the GTP-U marking in the header is sent from the eNB 1002 to the S-GW 1004. In operation 2, the S-GW maintains the same GTP-U marking on the interface S5 and/or the S8 interface, and sends the packet with the same GTP-U marking to the P-GW 1006 that includes the PCEF. In operation 3, the P-GW 1006 marks the IP packet containing this GTP-U with a Differentiated Services Code Point (DSCP) value. For example, a DSCP value that has not been used for specific meaning may be used to mark the IP Packet, such as DSCP values in ranges reserved for experimental or local use. Alternatively, a new DSCP value that has not been previously used can be set to indicate unlicensed access and to mark the IP packet. Additionally, in operation 3, the DSCP may transmit the marked IP packets to the TDF 1008. In operation 4, the TDF 1008 combines detected UL traffic with a specific DSCP within a detection and Installed Application Control (ADC) rule. and sends an event initiation message to PCRF 1010. In particular, the TDF 1008 may provide information about packets (whether packets are communicated through the primary cell or the secondary cell) to the PCRF 1010. In operation 5a, the PCRF creates a new ADC rule that the TDF 1008 uses to mark packets in DL with the DSCP value, so that the packets in the DL would be communicated in the same way as the UL packet (either over the primary cell or the secondary cell) and provides the new ADC rule for the TDF 1008. In operation 5b, the PCRF creates a new PCC rule to define the specific payload and accounting instructions for packets with this DSCP marking in UL and DL Communication, and provides the new ADC rule for PCC to P-GW 1006.

[00107] In one aspect, if any part of a packet has been transported through the secondary cell, then the entire packet is marked as being routed over the secondary cell. It is also noted that, this solution assumes that if data traffic for a carrier is being routed in UL over the secondary cell, then data traffic for that carrier is considered routed through the secondary cell for accounting purposes.

[00108] Explicit marking according to the second disclosure approach can provide the following advantages. No special charging or accounting functionality is required on eNB. The eNB is not required to receive PCC rules and/or detect SDFs within the carrier. The PCRF is configured to create new PCC and ADC Rules that only map specific types of traffic to unlicensed (for example allowing streaming video in unlicensed spectrum, but not allowing file transfer across unlicensed spectrum). Explicit marking can also provide sufficient separation between a Visited Public Land Mobile Network (VPLMN) and an HPLMN since the second disclosure approach does not require the HPLMN to expose the loading rules to the VPLMN.

[00109] In another aspect, the eNB may provide relationship marking to indicate the relationship of KT an amount of data communicated over the primary cell and an amount of data communicated through the secondary cell. The ratio of data amounts between the primary and secondary cells for UL packets may be different from the ratio of data amounts between the primary and secondary cells for DL packets, and thus separate ratio values may be provided for the UL packet. and for DL packages. In one example, 100% DL packets (and 0% UL packets) can be communicated in the secondary cell, while 100% UL packets (and 0% DL packets) can be communicated in the primary cell. In another example, 40% of DL packets (and 60% of UL packets) can be communicated in the secondary cell, while 50% of UL packets (and 50% of DL packets) can be communicated in the primary cell. The eNB makes a decision as to which packets are communicated through the primary cell or which packets are communicated through the secondary cell. Such a decision may depend on several factors, such as load conditions, radio conditions, local policies, visited network policies, etc.

[00110] In this regard, to provide more accurate loading, the eNB marks the UL packets of a data stream with an indication of the ratio of UL packets being sent through the primary cell versus the secondary cell to the core network. In an example, the indication may include a single ratio value (e.g., 30%) that should be interpreted by the core network as 30% of UL packets and 30% of DL packets should be communicated over the secondary cell. In another example, the indication may include two ratio values (e.g. UL 30%-DL 70%) in order to provide a more accurate indication of the actual ratio of packets sent through the secondary cell to UL and DL separately. The eNB can provide such an indication in each packet. Alternatively, the eNB may provide such an indication based on a packet interval defined by the eNB. For example, the eNB may establish the relationship and send such an indication periodically based on the time interval t0. In one example, the eNB may not send a new indication on UE UL SDF packets until the eNB determines that the relationship has changed. As another alternative, the eNB can mark each packet with a value (e.g. 0 or 1), where each value corresponds to the signaled component (total secondary cell traffic or UL or DL) so that the signaled component relationship can be determined based on the relationship of values measured over time. For example, if the value 0 corresponds to licensed access and the value 1 corresponds to unlicensed access, and 40 packets are received through unlicensed access out of 100 packets received, the core network may determine that 40% of the packets should be communicated over the secondary cell (and 60% over the primary cell) Additionally, for SDFs that may have only one DL Component (and no UL Components) or very few UL Packets (e.g. less than the number of UL Packets required to report charging information), the eNB may generate a dummy packet (e.g., with a known non-routable destination IP address) that is received by the PDN Gateway to determine the relationship. However, the PDN Gateway may not forward the dummy packet to another entity.

[00111] It may be desirable to allow the core network to instruct the RAN how to perform marking. For example, the RAN may belong to one operator and the other core network may belong to another operator, to ensure that the operation works correctly, when a bearer is created, the PDN GW provides indications to the RAN of the required marking type . Upon establishment of the data bearer, the PDN GW (based on the information received by the PCRF as described in the previous solution), can provide indications to the RAN of the type of marking required. The indication may include at least one marking for each packet, marking when the ratio changes more than a certain percentage, or marking at a certain packet frequency. The PDN GW may also provide the eNB with the format or Destination IP address of dummy packets that the eNB may need to send to DL SDFs only.

[00112] Another aspect of the second approach implements implicit loading, where the core network (e.g., the P-GW) carries data using a downloadable carrier as if the data packets are routed in the secondary cell. Thus, whenever a data carrier is configured to offload data packets to the secondary cell, the data carrier is loaded as if the data packets were routed in the secondary cell. For example, when the core network authorizes an SDF to be downloaded to a secondary cell or requests that the SDF be downloaded to the secondary cell, the SDF is loaded as if the SDF had been downloaded to the secondary cell, regardless of whether the SDF is it actually routed over the secondary cell or not.

[00113] A third approach to the invention provides a mechanism associated with the same ABR. Core network (e.g., PCRF, PDN GW, or MME) selects multiple UE-ABR values, including at least one UE-ABR for the primary cell (licensed access) and at least one UE-ABR for the secondary cell (licensed access). unlicensed) For example, the core network may select an ABR value for DL and UL communications over the primary cell, and an ABR value for DL and UL communications over the secondary cell. In this example, the core network can send multiple ABR values to the RAN (e.g., to the eNB) with an indication of which value is for the primary cell and which value is for the secondary cell. In another example, the core network may select an ABR value for DL Communication over the primary cell, an AMBE value for UL Communication over the primary cell, an ABR value for DL Communication over the secondary cell, and a From ABR to UL communication through the secondary cell. In this example, the core network can send multiple ABR values to the RAN (e.g., to the eNB) with an indication of which AMBE value is for UL communication over the primary cell, which ABR value is for DL over the primary cell, whose ABR value is for UL communication over the secondary cell, and whose ABR value is for DL communication over the secondary cell. The RAN (e.g. eNB) applies the ABR values to the corresponding cells as indicated. For example, current messages that support provisioning or UE-ABR (e.g., NAS Messages including the INITIAL and optional CONTEXT CONFIGURATION REQUEST message in E-RAB CONFIGURATION REQUEST, E-RAB MODIFICATION REQUEST, E-RAB RELEASE COMMAND) can be extended to deliver multiple UE-AMT Values.

[00114] Figure 1 is a flowchart 1100 of a wireless communication method, in accordance with an aspect of the disclosure. The method may be performed by a core network entity (e.g., the Gateway PDN 418, the appliance 1502/1502'). The core network entity is connected to a RAN including a primary cell using licensed spectrum and a secondary cell using licensed spectrum. an unlicensed spectrum. At 1102, the core network entity determines an authorization for data traffic to be offloaded to the secondary cell based on data traffic characteristics. At 1104, the core network transmits an authorization indication to the RAN. For example, as discussed above, the core network can be configured to make authorization and accounting decisions. For example, as discussed above, the core network may be configured to determine whether data traffic from a certain device can be carried to the secondary cell (e.g., from the primary cell). For example, as discussed above, to implement such decisions authorization and accounting, the core network must be able to indicate to the RAN whether specific data traffic can be offloaded to the secondary cell (or whether aggregation of data traffic is permitted). At 1106, the core network may perform additional features, as discussed below

[00115] In one aspect, the authorization indication includes a QCI, and the QCI includes a download indication associated with data traffic that is authorized to be uploaded to the secondary cell. In one aspect, the QCI is separate from another QCI for data traffic transmitted through the primary cell. For example, as discussed above, the core network assigns the new QCI value to SDF and/or data traffic that the core network authorizes offloading to the secondary cell. For example, as discussed above, based on the new QCI value, the RAN (e.g. eNB) determines which data traffic can be carried to a secondary cell. In one aspect, the offload statement indicates that data traffic is allowed to be offloaded. For example, as discussed above, as a new QCI, a separate QCI called a QCI unlicensed access to an SDF so as to indicate that the core network authorizes the data stream to be offloaded to a secondary cell. For example, as discussed above, the (conventional) QCI is increased to include a new QCI Value that indicates the charging capacity for the secondary cell. In one aspect, offload indicates that data traffic should be offloaded to the secondary cell whenever the secondary cell is available. For example, as discussed above, according to another aspect, unlicensed access QCI indicates that the core network (e.g., EPC410) requests that the data stream be offloaded to the secondary cell (e.g., secondary cell 408) whenever the secondary cell is available. For example, as discussed above, the new QCI value in QCI can specify whether offloading to the SDF applies to UL communication, DL communication, or UL and DL communication to the SDF. In such an aspect, the offload indication applies to at least one of an uplink communication over the secondary cell, a downlink communication over the secondary cell, or both uplink communication and downlink communication over the secondary cell. . For example, as discussed above, QCI unlicensed access can specify whether offloading to the SDF applies to UL communication, DL communication, or UL and DL communication to the SDF.

[00116] In one aspect, the authorization indication indicates that a carrier that is allowed to be downloaded is being routed to the secondary cell. For example, as discussed above, the core network (e.g., the P-GW) carries data usage from an offloadable carrier as if the data packets are routed in the secondary cell.

[00117] In one aspect, the core network entity determines authorization for data traffic to be offloaded to the network by a secondary cell receiving a policy associated with cell characteristics for the RAN from a PCRF, where the indication of Authorization is determined based on the policy received. In such an aspect, the authorization indication is used for at least one marking of a radio carrier to indicate whether to use the primary cell or the secondary cell or both the primary cell and the secondary cell, or to identify certain cell usage rules based on the received policy, where the primary cell and secondary cell are used based on the cell usage rules. For example, as discussed above, if the secondary cell is supported in the service network, the PCRF (PCRF visited if roaming) provides an indicator via a Gx interface to the PCEF to indicate for each flow whether the secondary cell (for the unlicensed access) can be or should be (e.g., is asked to be) used. For example, as discussed above, the PCRF provides the indicator to indicate that data traffic is allowed for offloading or the traffic is requested to be offloaded. For example, as discussed above, after receiving the indicator information, the PCEF at the PDN Gateway marks the carrier(s) with an indication that the data traffic can be offloaded or should be uploaded to the secondary cell for unlicensed access.

[00118] In such aspect, the authorization indication includes cell usage rules determined based on the received policy, and the primary cell and secondary cell are used based on the cell usage rules. In such an aspect, the cell usage rules include at least one of a number of a percentage of data to be communicated about the secondary cell with respect to a percentage of data to be communicated about the primary cell, or a maximum amount of data to be communicated through the primary cell. For example, as discussed above, the P-GW decides certain cell feature-specific usage rules (cell feature-specific usage rules) based on the cell feature-specific policies, and forwards these feature-specific usage rules from cell to eNB, (e.g., via the S-GW and MME), for example, as discussed above, cell characteristic specific usage rules may include, for example, a desired percentage of a data quantity (e.g., 50%) Transmitted through the secondary cell (in unlicensed spectrum) with respect to an amount of data transmitted through the primary cell (in licensed spectrum) For example, as discussed above, feature-specific usage rules cell may include a maximum amount of data (e.g., in bytes) allowed to be communicated through the primary cell.

[00119] In such an aspect, the policy is received for at least one of a standard radio bearer activation or a dedicated radio bearer activation. For example, as discussed above, the P-GW may provide instructions/policies in programming data about the secondary cell. Instructions can be provided per EPS carrier and/or per data stream. For example, as discussed above, instructions may be provided during standard EPS carrier activation and/or dedicated EPS carrier activation and/or dedicated/dedicated EPS carrier modification.

[00120] In such an aspect, when there is a change in at least one of the guidelines or conditions associated with the characteristics of the cell, the policy is received from the PCRF, and the authorization indication is determined based on the received policy. For example, as discussed above, the core network may initiate the EPS carrier modification procedure (e.g., with the RAN) due to changing policies or conditions regarding specific cell characteristic usage.

[00121] In one aspect, the authorization indication is transmitted to the RAN via an OAM protocol. For example, as discussed above, the RAN can be configured (e.g., by the core network) with cell-specific characteristic usage rule through the OAM function.

[00122] Figure 12 is a flowchart 1200 of a wireless communication method, expanding from the flowchart 1100 of Figure 11. The method may be performed by a core network entity (e.g., the PDN Gateway 418, the device 1502/1502') At 1106, flowchart 1200 is expanded from flowchart 1100 of Figure 11 at 1204, the core network entity determines a first ABR value for the primary cell and a second ABR value for the secondary cell for an equipment of user. At 1206, the core network entity transmits the first ABR Value and the second ABR Value to the RAN with KT an indication that the first ABR Value is for the primary cell and the second ABR Value is for the secondary cell. In one aspect, the first ABR value includes a first uplink ABR value and a first downlink ABR value for the primary cell, and the second ABR value includes a second uplink ABR value and a second downlink ABR value. to the secondary cell. For example, as discussed above, the core network (e.g., PCRF, PDN GW, or MME) selects multiple UE-ABR values, including at least one UE-ABR for the primary cell (licensed access) and at least one UE- ABR for secondary cell (unlicensed access), For example, as discussed above, the core network may select an ABR value for DL and UL communications over the primary cell, and an ABR value for DL and UL communications over the secondary cell. In one example, as discussed above, the core network may send multiple ABR values to the RAN (e.g., to the eNB) with an indication of which value is for the primary cell and which value is for the secondary cell. In another example, as discussed above, the core network may select an ABR value for DL Communication over the primary cell, an ABR value for UL Communication over the primary cell, an ABR Value for DL communication over the secondary cell, and an ABR value for UL Communication through the secondary cell.

[00123] Figure 13 is a flowchart 1300 of a wireless communication method, in accordance with an aspect of the disclosure. The method may be performed by a core network entity (e.g., the Gateway PDN 418, the appliance 1502/1502'). The core network entity is connected to a RAN including a primary cell using licensed spectrum and a secondary cell using licensed spectrum. an unlicensed spectrum. At 1302, the core network entity receives one or more packets from the RAN, wherein at least one of the one or more packets is marked with an indication associated with communication through the secondary cell. At 1304, the core network entity determines a load operation based on one or more packets. For example, as discussed above, the RAN (e.g., the eNB) may provide explicit marking by marking packets with an indication that provides information as to whether the packet was communicated over the primary cell in the licensed spectrum or over the secondary cell in the licensed spectrum. unlicensed spectrum. For example, as discussed above, tagging can be performed through the core network to create rules. At 1306, the core network may perform additional features, as discussed below.

[00124] In one aspect, the indication indicates that at least a portion of the one or more packets has been communicated through the secondary cell. In such an aspect, at least one of the one or more packets is marked by marking at least one of the one or more packets with an indication when at least a portion of a corresponding packet has been communicated through the secondary cell. For example, as discussed above, the indication provides information as to whether the packet was communicated over the primary cell in licensed spectrum or over the secondary cell in unlicensed spectrum. For example, as discussed above, the RAN (e.g., the eNB) identifies which packets were transported through licensed access or through unlicensed access, and marks such packets accordingly.

[00125] In one aspect, the indication includes an indication of a communication relationship over the primary cell and communication over the secondary cell. In such an aspect, the ratio indication includes a ratio value for UL communication over the secondary cell and DL communication over the secondary cell. In such an aspect, the ratio indication includes a ratio value of UL for UL communication over the ATT secondary cell and a ratio value of DL for DL communication over the secondary cell. For example, as discussed above, the eNB may provide relationship marking to indicate the relationship of ATT an amount of data communicated over the primary cell and an amount of data communicated through the secondary cell. For example, as discussed above, the ratio of data amounts between primary and secondary cells and for UL packets may be different from the ratio of data amounts between primary and secondary cells for DL packets, and thus separate ratio values can be provided for UL package and DL packages.

[00126] In one aspect, the relationship indication is marked on each package. In one aspect, the relationship indication is marked on a corresponding packet when there is a change in the relationship. For example, as discussed above, to provide a more accurate payload, the eNB marks the UL packets of a data stream with an indication of the ratio of packets in the UL being sent through the primary cell versus the secondary cell to the core network. For example, as discussed above, the eNB may provide such an indication in each packet. Alternatively, for example, as discussed above, the eNB may provide such an indication based on a packet interval defined by the eNB. In one aspect, one or more packets are marked with respective numerical values, each of the numerical values indicating whether each of the one or more packets has been communicated about the primary cell or the secondary cell, where the relationship is based on the numerical values during a period of time. As another alternative, for example, as discussed above, the eNB may mark each packet with a value (e.g. 0 or 1), where each value corresponds to the signaled component (total secondary cell traffic or UL or DL) so that the relationship of the signaled component can be determined based on the relationship of measured values over time. In one aspect, the one or more packets are dummy packets, each of the dummy packets including indicating the communication relationship over the primary cell and the communication over the secondary cell, and the dummy packets are discarded by the core network entity. For example, as discussed above, for SDFs that may have only one DL Component (and no UL components) or very few UL packets (e.g., fewer than the number of UL packets required to report billing information), The eNB may generate a dummy packet (e.g., with a known non-routable destination IP address) that is received by the PDN Gateway to determine the relationship.

[00127] Figure 14 is a flowchart 1400 of a wireless communication method, expanding from the flowchart 1300 of Figure 13. The method may be performed by a core network entity (e.g., the PDN Gateway 418, the device 1502/1502') At 1306, flowchart 1400 is expanded from flowchart 1300 of Figure at 1404, the core network entity marks the one or more packets with a DSCP value that is used to match uplink traffic. . At 1406, the core network entity transmits the one or more marked packets to a TDF. For example, as illustrated in Figure 10, in operation 3, the P-GW 1006 marks the IP packet containing this GTP-U header with a DSCP value. For example, as illustrated in Figure 10, in operation 3, the DSCP may transmit the marked IP packets to the TDF 1008. In one aspect, the DSCP value is used to create a first rule for marking a packet in downlink traffic with a corresponding DSCP, and a second rule to define loading and accounting instructions for a packet with the corresponding DSCP. For example, as discussed above, the PCRF creates a new ADC Rule that the TDF 1008 uses to mark packets in DL with the DSCP value. For example, as discussed above, the PCRF creates a new PCC rule to define the specific payload and accounting instructions for packets with this DSCP marking in UL and DL Communication, and provides the new PCC rule to the P-GW 1006 .

[00128] Figure 15 is a conceptual data flowchart 1500 illustrating the flow of data between different media/components in Figure an exemplary apparatus 1502. The apparatus may be a core network entity (e.g., the PDN418 port). The apparatus includes a receiving component 1504, a transmitting component 1506, an authorization component 1508, an ABR component 1510, a charging component 1512, and a marking component 1514.

[00129] The core network entity is connected to a RAN (e.g., RAN1850) including a primary cell utilizing licensed spectrum and a secondary cell utilizing unlicensed spectrum. According to one approach, the authorization component 1508 determines an authorization parameter for data traffic to be carried to the secondary cell based on data traffic characteristics, and transmits through the transmission component 1506 an indication of the authorization to to RAN 1550, in 1560 and 1562.

[00130] In one aspect, the authorization indication includes a QCI, and the QCI includes a download indication associated with data traffic that is authorized to be uploaded to the secondary cell. In one aspect, the QCI is separate from another QCI for data traffic transmitted through the primary cell. In such aspect, the indication download indicates that the data traffic is allowed to be downloaded. In this aspect, the indication offload indicates that data traffic should be offloaded to the secondary cell whenever the secondary cell is available. In such an aspect, the offload indication applies to at least one uplink communication over the secondary cell, downlink communication over the secondary cell, or both uplink communication and downlink communication over the secondary cell. In one aspect, the authorization indication indicates that a carrier that is permitted for offloading to be carried is being routed to the secondary cell.

[00131] In one aspect, the core network entity determines authorization for data traffic to be offloaded to the network by a secondary cell receiving a policy associated with cell characteristics for the RAN from a PCRF, where the indication of Authorization is determined based on the policy received. In such an aspect, the authorization indication is used for at least one of the devices marking a radio carrier to indicate whether it uses the primary cell or the secondary cell or both the primary cell and the secondary cell, or to identify cell usage rules. determined based on the received policy, where the primary cell and secondary cell are used based on the cell usage rules. In such aspect, the indication of authorization of cell usage rules determined based on the received policy, and the primary cell and secondary cell are used based on the cell usage rules. In such an aspect, the authorization indication contains information of a packet format and packet destination address to be used by the RAN to generate dummy UL packets in accordance with the present invention the communication does not have UL components or when UL packets are fewer and/or less frequent than the number of UL packages required to report loading information. In such an aspect, the cell usage rules include at least one of a number of a percentage of data to be communicated about the secondary cell with respect to a percentage of data to be communicated about the primary cell, or a maximum amount of data to be communicated through the primary cell. In such an aspect, the policy is received by at least one of a standard radio bearer activation or a dedicated radio bearer activation. In this regard, when there is a change in at least one of the guidelines or conditions associated with the characteristics of the cell, the policy is received from the PCRF, and the authorization indication is determined based on the received policy.

[00132] In one aspect, the authorization indication is transmitted to the RAN via an OAM protocol.

[00133] In one aspect, the ABR component 1510 determines a first ABR Value for the AMT primary cell and a second ABR value for the secondary cell to a user equipment, and transmits through the transmission component 1506 the first ABR value and the second ABR Value for the RAN 1550 with an indication that the first ABR value is for the primary cell and the second ABR Value is for the secondary cell, at 1564 and 1562. The ABR 1510 component may also receive communication from the RAN 1550 through the receiving component 1504, at 1568 and 1566. In one aspect, the first ABR value includes a first uplink ABR value and a first downlink ABR value for the primary cell, and the second ABR value includes a second ABR value of Uplink and A second downlink ABR value for the secondary cell.

[00134] According to another approach, the receiving component 1504 receives one or more packets from the RAN 1550, at 1568, wherein at least one of the one or more packets is marked with an indication associated with communication through the secondary cell, and the loading component 1512 determines a loading operation based on one or more packets (e.g., received from receiving component 1504 in 1570). The payload component 1512 may forward the one or more packets to the marking component 1514 at 1572, and/or the receiving component 1504 may forward the one or more packets to the marking component 1514 at 1574.

[00135] In one aspect, the indication indicates that at least a portion of the one or more packets has been communicated through the secondary cell. In such an aspect, at least one of the one or more packets is marked by marking each of the one or more packets with an indication when at least a portion of a corresponding packet has been communicated through the secondary cell.

[00136] In one aspect, the marking component 1514 marks the one or more packets with a DSCP value that is used to match uplink traffic, and transmits through the transmission component 1506 the one or more marked packets for a TDF across RAN 1550, at 1576 and 1564. In one aspect, the DSCP value is used to create a first rule to mark a packet in downlink traffic with a corresponding DSCP, and a second rule to define load and load instructions. accounting for a packet with the corresponding DSCP.

[00137] In one aspect, the indication includes an indication of a communication relationship over the primary cell and communication over the secondary cell. In such an aspect, the ratio indication includes a ratio value for UL communication over the secondary cell and DL communication over the secondary cell. In such an aspect, the ratio indication includes a ratio value of UL for UL communication over the ATT secondary cell and a ratio value of DL for DL communication over the secondary cell. In one aspect, the relationship statement is marked on each package. In one aspect, the relationship indication is marked on a corresponding packet when there is a change in the relationship. In one aspect, one or more packets are marked with respective numerical values, each of the numerical values indicating whether each of the one or more packets has been communicated about the primary cell or the secondary cell, where the relationship is based on the numerical values during a period of time.

[00138] In one aspect, the one or more packets are dummy packets, each of the dummy packets including indicating the communication relationship over the primary cell and the communication over the secondary cell, and the dummy packets are discarded by the core network entity . For example, one or more packets may be dummy UL packets that are generated by LT in accordance with the present invention the communication does not have a UL component or has few UL packets (e.g., fewer than the number of UL packets required to report charging information). In one aspect, dummy packets are sent by the RAN 1550 to the RAN receiving component 1504 by 1568 in a format and addressed to an address, where the format and address are communicated by the core network to the RAN when offloading to the secondary cell is authorized by the core network. In one aspect, upon receiving such dummy packets, the receiving component 1504 uses the indication of the relationship of communication over the primary cell and communication over the secondary cell and passes it to the loading component 1512 at 1570, and the receiving component 1504 drops the dummy packet.

[00139] The apparatus may include additional components that perform each of the algorithm blocks in the flowcharts mentioned above in Figures 11-14. As such, each block in the above-mentioned flowcharts of Figures 11-14 may be realized by a component and the apparatus may include one or more of these components. The components may be one or more hardware components specifically configured to perform the established processes/algorithm, implemented by a processor configured to perform the established processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination of the same.

[00140] Figure 16 is a diagram 1600 illustrating an example of a hardware implementation for an apparatus 1502' that employs a processing system 1614. The processing system 1614 may be implemented with a bus architecture, generally represented by the bus 1624. Bus 1624 may include any number of interconnect buses and bridges depending on the specific application of processing system 1614 and overall design constraints. The bus 1624 connects various circuits including one or more processors and/or hardware components, represented by the processor 1604, the components 1504, 1506, 1508, 1510, 1512, 1514, and the computer-readable medium/memory 1606. The bus 1624 It can also connect various other circuits, such as timing supplies, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described below.

[00141] The processing system 1614 may be coupled to a transceiver 1610. The Transceiver 1610 is coupled to one or more antennas 1620. The Transceiver 1610 provides a means for communicating with various other devices via a transmission medium. The transceiver 1610 receives a signal from one or more antennas 1620, extracts information from the received signal, and provides the extracted information to the processing system 1614, specifically the receiving component 1504. Additionally, the transceiver 1610 receives information from the system processing system 1614, specifically, the transmission component 1506, and based on the information received, generates a signal to be applied to one or more antennas 1620. The processing system 1614 includes a processor 1604 coupled to a computer readable medium/memory 1606. Processor 1604 is responsible for general processing, including executing software stored on the computer-readable medium/memory 1606. The software, when executed by processor 1604, causes processing system 1614 to perform the various functions described above to any particular device. The computer-readable medium/memory 1606 may also be used to store data that is manipulated by the processor 1604 when executing software. The processing system 1614 further includes at least one of the components 1504, 1506, 1508, 1510, 1512, 1514. The components may be software components running on the processor 1604, resident/stored in the computer-readable medium/memory 1606, a or more hardware components coupled to processor 1604, or some combination thereof.

[00142] In one embodiment, the apparatus 1502/1502' for wireless communication includes means for determining an authorization for data traffic to be uploaded to the secondary cell based on data traffic characteristics, means for transmitting an indication of the authorization for the RAN, means for determining a first ABR Value for the primary cell and a second ABR Value for the secondary cell to a user equipment, and means for transmitting the first ABR Value and the second ABR Value to the base station with an indication that the first ABR Value is for the primary cell and the second ABR Value is for the secondary cell. In one aspect, the apparatus 1502/1502' for wireless communication includes means for receiving one or more packets from the RAN, wherein at least one of the one or more packets is marked with an indication associated with communication through the secondary cell means for determining a loading operation based on one or more packets, means for marking the one or more packets with a DSCP value that is used to match uplink traffic, and means for transmitting the one or more marked packets to a TDF. The aforementioned means may be one or more of the aforementioned components of the apparatus 1502 and/or the processing system 1614 of the apparatus 1502' configured to perform the aforementioned functions by the aforementioned means.

[00143] Figure 17 is a flowchart 1700 of a wireless communication method, in accordance with an aspect of the disclosure. The method may be performed by a RAN entity such as an eNB (e.g., the eNB serving the primary cell 406, the apparatus 2102/2102'). At 1702, the RAN entity receives, from a core network, an indication for authorization to data traffic to be offloaded to a secondary cell using unlicensed spectrum, where the authorization indication is based on data traffic characteristics. At 1704, the RAN entity determines, based on the authorization indication, to communicate through at least one of a primary cell using licensed spectrum or the secondary cell using unlicensed spectrum, the primary cell and the secondary cell being included in a RAN. For example, as discussed above, the core network may be configured to determine whether data traffic from a certain device can be carried to the secondary cell (e.g., from the primary cell). For example, as discussed above, to implement such decisions authorization and accounting, the core network must be able to indicate to the RAN whether specific data traffic can be offloaded to the secondary cell (or whether aggregation of data traffic is permitted). At 1706, the RAN entity may perform additional features as discussed below

[00144] In one aspect, the authorization indication includes a QCI, and wherein the QCI includes a discharge indication associated with data traffic that is authorized to be uploaded to the secondary cell. In one aspect, the QCI is separate from another QCI for data traffic transmitted through the primary cell. For example, as discussed above, the core network assigns the new QCI value to the SDF value and/or data traffic that the core network authorizes offloading to the secondary cell. For example, as discussed above, based on the new QCI value, the RAN (e.g. ENB) which data traffic can be offloaded to a secondary cell. In one aspect, the offload statement indicates that data traffic is allowed to be offloaded. For example, as discussed above, as a new QCI, a separate QCI called a QCI unlicensed access to an SDF so as to indicate that the core network authorizes the data stream to be offloaded to a secondary cell. For example, as discussed above, the (conventional) QCI is increased to include a new QCI Value that indicates the charging capacity for the secondary cell. In one aspect, offload indicates that data traffic should be offloaded to the secondary cell whenever the secondary cell is available. For example, as discussed above, according to another aspect, unlicensed access QCI indicates that the core network (e.g., EPC410) requests that the data stream be offloaded to the secondary cell (e.g., secondary cell 408) whenever the secondary cell is available. For example, as discussed above, the new QCI value in QCI can specify whether offloading to the SDF applies to UL communication, DL communication, or UL and DL communication to the SDF. In one aspect, the offload indication applies to at least one of an uplink communication over the secondary cell, a downlink communication over the secondary cell, or both uplink communication and downlink communication over the secondary cell. . For example, as discussed above, QCI unlicensed access can specify whether offloading to the SDF applies to UL communication, DL communication, or UL and DL communication to the SDF.

[00145] In one aspect, the authorization indication indicates that a carrier that is permitted for offloading to be carried as being routed to the secondary cell. For example, as discussed above, the core network (e.g., the P-GW) carries data usage from an offloadable carrier as if the data packets are routed in the secondary cell.

[00146] In one aspect, the authorization indication includes cell usage rules determined based on a policy of a PCRF, the policy being associated with cell characteristics for the RAN, and the primary cell and secondary cell being used based on cell usage rules. In such an aspect, the authorization indication is used for at least one of the devices marking a radio carrier to indicate whether it uses the primary cell or the secondary cell or both the primary cell and the secondary cell, or to identify cell usage rules. determined based on the received policy, where the primary cell and secondary cell are used based on the cell usage rules. In such an aspect, the cell usage rules include at least one of a number of a percentage of data to be communicated about the secondary cell with respect to a percentage of data to be communicated about the primary cell, or a maximum amount of data to be communicated through the primary cell. For example, as discussed above, if the secondary cell is supported in the service network, the PCRF (visited-PCRF if roaming) provides an indicator through a Gx interface to the PCEF to indicate for each flow whether the secondary cell (for the unlicensed access) can be or should be (e.g., is requested to be) used. For example, as discussed above, the P-GW decides certain cell feature-specific usage rules (cell feature-specific usage rules) based on the cell feature-specific policies, and forwards these feature-specific usage rules from cell to eNB, (e.g., through the S-GW and the MME), for example, as discussed above, the PCRF provides the indicator to indicate that data traffic is allowed for offloading or the traffic is requested to be downloaded. For example, as discussed above, after receiving the indicator information, the PCEF nO PDN Gateway marks the carrier(s) with an indication that the data traffic can be offloaded or must be uploaded to the secondary cell for unlicensed access. For example, as discussed above, specific cell characteristic usage rules may include, for example, a desired percentage of a quantity of data (e.g., 50%) transmitted through the secondary cell (in the unlicensed spectrum) with respect to to an amount of data transmitted through the primary cell (in the licensed spectrum) For example, as discussed above, cell characteristic-specific usage rules may include a maximum amount of data (e.g., in bytes) allowed to be communicated through of the primary cell.

[00147] In such an aspect, the policy is for at least one of a standard radio bearer activation or a dedicated radio bearer activation. For example, as discussed above, the P-GW may provide instructions/policies in programming data about the secondary cell. Instructions can be provided per EPS carrier and/or per data stream. For example, as discussed above, instructions may be provided during standard EPS carrier activation and/or dedicated EPS carrier activation and/or dedicated/dedicated EPS carrier modification.

[00148] In such aspect, cell usage rules are received from the MME during an S1-AP establishment between the MME and the base station. In such an aspect, the cell usage rules are received from the MME through at least one of tT an initial context establishment request or a context modification message sent from the MME, for example, as discussed above , the MME is configured to provide specific usage rules characteristics to the RAN as an explicit indication of the MME. For example, as discussed above, the MME provides the cell characteristic specific usage rules during an S1-AP context establishment between the MME and the eNB for each UE.

[00149] In one aspect, the authorization indication is received via an OAM protocol. For example, as discussed above, the RAN can be configured (e.g., by the core network) with specific cell characteristic usage rule through the OAM function.

[00150] Figure 18 is a flowchart 1800 of a wireless communication method, expanding from the flowchart 1700 of Figure 17. The method may be performed by a RAN Entity such as an eNB (e.g., the eNB serving the cell 406, the apparatus 2102/2102') At 1706, the flowchart 1800 is expanded from the flowchart 1700 of Figure 17. At 1804, the RAN entity receives a first ABR value for the primary cell and a second ABR value for the primary cell. secondary with KT an indication that the first ABR Value is for the primary cell and the second ABR Value is for the secondary cell. In one aspect, the determination of communicating through at least one of the primary cell or the secondary cell is further based on at least one of the first ABR value or the second ABR value. In one aspect, the first ABR value includes a first uplink ABR value and a first downlink ABR value for the primary cell, and the second ABR value includes a second uplink ABR value and a second downlink ABR value. to the secondary cell. For example, as discussed above, the core network (e.g., PCRF, PDN GW, or MME) selects multiple UE-ABR values, including at least one UE-ABR for the primary cell (licensed access) and at least one UE -ABR for secondary cell (unlicensed access). For example, as discussed above, the core network may select an ABR value for DL and UL communications over the primary cell, and an ABR value for DL and UL communications over the secondary cell. In one example, as discussed above, the core network may send multiple ABR values to the RAN (e.g., to the eNB) with an indication of which value is for the primary cell and which value is for the secondary cell. In another example, as discussed above, the core network may select an ABR value for DL Communication over the primary cell, an ABR value for UL Communication over the primary cell, an ABR Value for DL communication over the secondary cell, and an ABR value for UL Communication through the secondary cell.

[00151] Figure 19 is a flowchart 1900 of a wireless communication method, in accordance with an aspect of the disclosure. The method can be carried out by a RAN entity that includes a primary cell using licensed spectrum and a secondary cell using unlicensed spectrum. For example, the method may be performed by a RAN entity such as an eNB (e.g., the eNB serving the primary cell 406, the apparatus 2102/2102'). The RAN entity serves a primary cell in a licensed spectrum. In 1902, the RAN entity marks at least one of one or more packets by adding an indication associated with communication through the secondary cell. In 1904, the RAN entity transmits at least one of one or more packets to a central network. For example, as discussed above, the RAN (e.g., the eNB) may provide explicit marking by marking packets with an indication that provides information as to whether the packet was communicated over the primary cell in the licensed spectrum or over the secondary cell in the licensed spectrum. unlicensed spectrum. For example, as discussed above, tagging can be performed through the core network to create rules. In 1906, the core network can perform additional features, as discussed below.

[00152] In one aspect, the indication indicates that at least a portion of the one or more packets has been communicated through the secondary cell. In such an aspect, marking the at least one of the one or more packets comprises marking the at least one or more packets with an indication when at least a portion of a corresponding packet has been communicated through the secondary cell. For example, as discussed above, the indication provides information as to whether the packet was communicated over the primary cell in licensed spectrum or over the secondary cell in unlicensed spectrum. For example, as discussed above, the RAN (e.g., the eNB) identifies which packets were transported through licensed access or through unlicensed access, and marks such packets accordingly.

[00153] In one aspect, the indication includes an indication of a communication relationship over the primary cell and communication over the secondary cell. In such an aspect, the ratio indication includes a ratio value for UL communication over the secondary cell and DL communication over the secondary cell. In such an aspect, the ratio indication includes a UL ratio value for UL communication over the secondary cell and a DL ratio value for DL communication over the secondary cell. For example, as discussed above, the eNB may provide relationship marking to indicate the relationship of an amount of data communicated about the primary cell and an amount of data communicated through the secondary cell. For example, as discussed above, the ratio of data amounts between primary and secondary cells and for UL packets may be different from the ratio of data amounts between primary and secondary cells for DL packets, and thus separate ratio values can be provided for UL package and DL packages.

[00154] In one aspect, the relationship indication is marked on each package. In one aspect, the relationship indication is marked on a corresponding packet when there is a change in the relationship. For example, as discussed above, to provide a more accurate payload, the eNB marks the UL packets of a data stream with an indication of the ratio of packets in the UL being sent through the primary cell versus the secondary cell to the core network. For example, as discussed above, the eNB may provide such an indication in each packet. Alternatively, for example, as discussed above, the eNB may provide such an indication based on a packet interval defined by the eNB. In one aspect, the one or more packets are dummy packets, each of the dummy packets including indicating the communication relationship over the primary cell and the communication over the secondary cell, and the dummy packets are forwarded to a core network entity. For example, as discussed above, for SDFs that may have only one DL Component (and no UL Components) or very few UL packets (e.g., fewer than the number of UL packets required to report load information), The eNB may generate a dummy packet (e.g., with a known non-routable destination IP address) that is received by the PDN Gateway to determine the relationship.

[00155] Figure 20 is a flowchart 2000 of a wireless communication method, expanding from the flowchart 1900 of Figure 1. The method may be performed by a RAN entity such as the eNB (e.g., the eNB serving the cell primary 406, apparatus 2102/2102') In 1906, flowchart 2000 is expanded from flowchart 1900 of FIG. in 2002, the RAN entity marks the one or more packets with respective numeric values, each of the numeric values indicating whether each of the one or more packets was communicated over the primary cell or the secondary cell. In one aspect, the relationship is based on numerical values over a period of time. For example, as discussed above, the eNB may mark each packet with a value (e.g. 0 or 1), where each value corresponds to the signaled component (total secondary cell traffic or UL or DL) so that the signaled component relationship can be determined based on the relationship of values measured over time.

[00156] Figure 21 is a conceptual data flowchart 2100 that illustrates the flow of data between different media/components in an exemplary apparatus 2102. The Apparatus may be a RAN entity such as an eNB. The apparatus includes a receiving component 2104, a transmitting component 2106, a communication management component 2108, an ABR component 2110, and a marking component 2112.

[00157] According to one approach, the communication management component 2108 receives through the receiving component 2104, from a core network 2150, at 2162 and 2164, an indication for authorization for data traffic to be downloaded to a secondary cell using unlicensed spectrum, where authorization indication is based on data traffic characteristics. The communication management component 2108 determines, based on the authorization indication, to communicate through at least one of a primary cell utilizing licensed spectrum or the secondary cell utilizing unlicensed spectrum, the primary cell and the secondary cell being included in a RAN. The communication management component 2108 may communicate using the receive component 2104 and the transmit component, at 2164 and 2166.

[00158] In one aspect, the authorization indication includes a QCI, and wherein the QCI includes a download indication associated with data traffic that is authorized to be uploaded to the secondary cell. In one aspect, the QCI is separate from another QCI for data traffic transmitted through the primary cell. In one aspect, the offload statement indicates that data traffic is allowed to be offloaded. In one aspect, offload indicates that data traffic should be offloaded to the secondary cell whenever the secondary cell is available. In one aspect, the offload indication applies to at least one of an uplink communication over the secondary cell, a downlink communication over the secondary cell, or both uplink communication and downlink communication over the secondary cell. . In one aspect, the authorization indication indicates that a carrier that is permitted for offloading to be carried is being routed to the secondary cell.

[00159] In one aspect, the authorization indication includes cell usage rules determined based on a policy of a PCRF, the policy being associated with the cell characteristics for the RAN, and the primary cell and the secondary cell are used based on cell usage rules. In such an aspect, the authorization indication is used for at least one of the devices marking a radio carrier to indicate whether it uses the primary cell or the secondary cell or both the primary cell and the secondary cell, or to identify cell usage rules. determined based on the received policy, where the primary cell and secondary cell are used based on the cell usage rules. In such an aspect, the cell usage rules include at least one of a number of a percentage of data to be communicated about the secondary cell with respect to a percentage of data to be communicated about the primary cell, or a maximum amount of data to be communicated through the primary cell. In such an aspect, the policy is for at least one of a standard radio bearer activation or a dedicated radio bearer activation. In such aspect, cell usage rules are received from the MME and during each S1-AP set between the MME and the base station. In such an aspect, cell usage rules are received from the MME via ATT at least one of an initial context establishment request or a context modification message sent from the MME.

[00160] In one aspect, the authorization indication is received via an OAM protocol.

[00161] In one aspect, the ABR component 2110 receives through the receiving component 2104. A first ABR Value for the primary cell and a second ABR Value for the secondary cell with an indication that the first ABR Value is for the primary cell and the second ABR Value is for the secondary cell, at 2162 and 2168. The AMBE Component 21 10 may forward the first ABR value and the Second ABR value to the communication management component 2108, at 2170. In one aspect, the component communication management system 2108 may determine whether to communicate through at least one of the primary cells or the secondary cell based on at least one of the first ABR value or the second ABR value. In one aspect, the first ABR value includes a first uplink ABR value and a first downlink ABR value for the primary cell, and the second ABR value includes a second uplink ABR value and a second downlink ABR value. to the secondary cell.

[00162] According to another approach, where the eNB operates in the RAN that includes a primary cell using licensed spectrum and a secondary cell using unlicensed spectrum, the marking component 21 12 marks at least one of one or more packets by adding an indication associated with communication through the secondary cell. The marking component 2112 may receive one or more packets from the receiving component 2104 at 2172. The marking component 2112 transmits through the transmitting component 2106 the at least one of one or more packets to a core network 2150, at 2174 and 2176 .

[00163] In one aspect, the indication indicates that at least a portion of the one or more packets has been communicated through the secondary cell. In such an aspect, marking at least one of the one or more packets comprises marking at least one of the one or more packets with indicating when at least a portion of a corresponding packet has been communicated through the secondary cell.

[00164] In one aspect, the indication includes an indication of a communication relationship over the primary cell and communication over the secondary cell. In such an aspect, the ratio indication includes a ratio value for UL communication over the secondary cell and DL communication over the secondary cell. In such an aspect, the ratio indication includes a ratio value of UL for UL and ATT communication over the secondary cell and a ratio value of DL for DL communication over the secondary cell. In such aspect, the relationship indication is marked on each package. In such aspect, the relationship indication is marked in a corresponding packet when there is a change in the relationship.

[00165] In one aspect, the marking component 21 12 marks the one or more packets with respective numeric values, each of the numeric values indicating whether each of the one or more packets was communicated about the primary cell or the secondary cell. In one aspect, the relationship is based on numerical values over a period of time. In one aspect, the one or more packets are dummy packets, each of the dummy packets including indicating the communication relationship over the primary cell and the communication over the secondary cell, and the dummy packets are forwarded to a core network entity. For example, one or more packets may be dummy UL packets that are generated by LT in accordance with the present invention the communication does not have a UL component or has few UL packets (e.g., fewer than the number of UL packets necessary to report load information) In one aspect, fictitious packets are sent by the transmission component 2106 and the core network 2150 in a format and addressed to an address, at 2174 and 2176, where the format and address are communicated by the core network to the THT RAN when offloading to the secondary cell is authorized by the core network.

[00166] The apparatus may include additional components that perform each of the algorithm blocks in the flowcharts mentioned above in Figures 17-20. As such, each block in the aforementioned flowcharts of Figures 17-20 may be realized by a component and the apparatus may include one or more of these components. The components may be one or more hardware components specifically configured to perform the established processes/algorithm, implemented by a processor configured to perform the established processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination of the same.

[00167] Figure 22 is a diagram 2200 that illustrates an example of a hardware implementation for an apparatus 2102' that employs a processing system 2214. The processing system 2214 can be implemented with a bus architecture, generally represented by the bus 2224. Bus 2224 may include any number of interconnect buses and bridges depending on the specific application of processing system 2214 and overall design constraints. Bus 2224 connects various circuits including one or more processors and/or hardware components, represented by processor 2204, components 2104, 2106, 2108, 2110, 2112, and computer-readable medium/memory 2206. Bus 2224 can also connect various other circuits, such as timing supplies, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described below.

[00168] The processing system 2214 may be coupled to a transceiver 2210. The Transceiver 2210 is coupled to one or more antennas 2220. The Transceiver 2210 provides a means for communicating with various other devices via a transmission medium. The transceiver 2210 receives a signal from one or more antennas 2220, extracts information from the received signal, and provides the extracted information to the processing system 2214, specifically the receiving component 2104. Additionally, the transceiver 2210 receives information from the system processing system 2214, specifically, the transmission component 2106, and based on the information received, generates a signal to be applied to one or more antennas 2220. The processing system 2214 includes a processor 2204 coupled to a computer readable medium/memory 2206. Processor 2204 is responsible for general processing, including executing software stored on the computer-readable medium/memory 2206. The software, when executed by processor 2204, causes processing system 2214 to perform the various functions described above to any particular device. The computer-readable medium/memory 2206 may also be used to store data that is manipulated by the processor 2204 when executing software. The processing system 2214 further includes at least one of the components 2104,2106,2108, 2110, 2112. The components may be software components running on the processor 2204, resident/stored in the computer-readable medium/memory 2206, one or more hardware components coupled to processor 2204, or some combination thereof. The processing system 2214 may be a component of the eNB 310 and may include memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

[00169] In one configuration, the apparatus 2102/2102' for wireless communication includes means for receiving, from a core network, an indication for authorization for data traffic to be offloaded to a secondary cell using unlicensed spectrum, where the indication for authorization is based on data traffic characteristics, means for determining, based on the indication for authorization, to communicate through at least one of a primary cell using licensed spectrum or the secondary cell using unlicensed spectrum , the primary cell and the secondary cell being included in a RAN, and means for receiving a first ABR Value for the primary cell and a second ABR Value for the secondary cell with an indication that the first ABR Value is for the primary cell and the second ABR Value is for the secondary cell. In one aspect, the apparatus 2102/2102' for wireless communication includes means for marking at least one of one or more packets by adding an indication associated with the communication through the secondary cell, means for transmitting the at least one of one or more packets to a core network, and means for marking the one or more packets with respective numerical values, each of the numerical values indicating whether each of the one or more packets was communicated over the primary cell or the secondary cell. The aforementioned means may be one or more of the aforementioned components of the apparatus 2102 and/or the processing system 2214 of the apparatus 2102' configured to perform the aforementioned functions by the aforementioned means. As described above, the processing system 2214 may include the TX processor 316, the RX processor 370, and the controller/processor 375. As such, in one configuration, the aforementioned device may be the TX processor 316, the RX processor 370 , and the controller/processor 375 configured to perform the aforementioned functions by the aforementioned means.

[00170] It is understood that the specific order or hierarchy of blocks in the presented processes/flowcharts is an illustration of exemplary approaches. Based on design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts can be rearranged. Additionally, some blocks can be combined or omitted. Tracking method claims the elements of the various blocks in a sample order, and are not intended to be limited to the specific order or hierarchy presented.

[00171] The foregoing description is provided to enable anyone skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein, but the full scope consistent with the language claims must be agreed, in which reference to an element in the singular is not intended to mean "one and only one", the unless specifically mentioned otherwise, but rather one or more. "The word "exemplary" is used here to mean "serving as an example, case, or illustration." "Any aspect described herein as "exemplary" should not necessarily be considered as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term "some" refers to one or more combinations such as " at least one of A, B, or C, "one or more of A, B, or C," at least one of A, B, and C, "one or more of A, B, and C," and "A, B , C, or any combination thereof”, including any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C," one or more of A, B, or C, "at least one of A, B, and C," one or more of A, B, and C," and "A, B, C, or any combination thereof may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any of these combinations may contain one or more members or members of A, B or C. All structural and functional equivalents to elements of the various aspects described throughout this description that are known or hereafter should be known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such description is explicitly recited in the claims. The words “module”, “mechanism”, “element”, “device”, and the like may not be a substitute for the word “medium”. As such, no claimed element is to be construed as a means plus function unless the element is expressly recited using the phrase “means to”.

Claims (15)

1. Method (1100) of wireless communication by a core network entity, characterized by the fact that the core network entity is connected to a radio access network, RAN, including a primary cell using a first radio access technology radio, RAT, and a secondary cell using a second RAT, the method comprising: determining an authorization for data traffic to be offloaded to the secondary cell based on data traffic characteristics; and transmitting (1104) an indication of authorization to the RAN; receiving one or more packets from the RAN, wherein the one or more packets are marked by the RAN with an indication indicating that the one or more packets have been communicated through the secondary cell; and update authorization based on one or more packages. 2. Method according to claim 1, characterized in that the authorization indication includes a quality of service class identifier, QoS, QCI, which is separate from another QCI for data traffic transmitted through the primary cell, and wherein the QCI includes an offload indication associated with a descriptor that identifies data traffic that is authorized to be offloaded to the secondary cell. 3. Method according to claim 2, characterized by the fact that the download indication includes at least one of an indication that the data traffic is allowed to be downloaded or an indication that the data traffic must be downloaded to the secondary cell whenever the secondary cell is available, and wherein the offload indication applies to at least one of an uplink communication over the secondary cell, a downlink communication over the secondary cell, or both uplink communication over the secondary cell and downlink communication over the secondary cell. 4. Method according to claim 1, characterized by the fact that the authorization indication indicates that a bearer that is allowed to be downloaded is loaded as being routed in the secondary cell, wherein determining the authorization for data traffic to be downloaded to the secondary cell comprises receiving a policy associated with cell characteristics to the RAN from a policy and rule loading function, PCRF, and wherein the authorization indication is determined based on the received policy. 5. The method of claim 4, wherein the authorization indication is used to at least one of marking a radio bearer to indicate whether it uses the primary cell or the secondary cell or both the primary cell and the secondary cell, or identify cell usage rules determined based on the received policy, where the primary cell and secondary cell are used based on the cell usage rules. 6. Method, according to claim 1, characterized by the fact that the authorization indication is transmitted to the RAN through an operation, administration and maintenance protocol, OAM. 7. The method of claim 1, further comprising: determining a first aggregate maximum bit rate value, AMBR, for the primary cell and a second AMBR value for the secondary cell for a user equipment; and transmitting the first AMBR value and the second AMBR value to the RAN with an indication that the first AMBR value is for the primary cell and the second AMBR value is for the secondary cell, wherein the first AMBR value includes a first AMBR value uplink value and a first downlink AMBR value for the primary cell, and the second AMBR value includes a second uplink AMBR value and a second downlink AMBR value for the secondary cell. 8. Method (1700) of wireless communication by a radio access network entity, RAN, characterized by the fact that it comprises: receiving (1702), from a core network, an indication for authorization for data traffic be downloaded to a secondary cell using a second radio access technology, RAT, in which the indication for authorization is based on data traffic characteristics; and determining (1704), based on the indication for authorization, communication through at least one of a primary cell using a first RAT or the secondary cell using the second RAT, the primary cell and the secondary cell being included in an access network radio, RAN; transmitting one or more packets to the core network, wherein the one or more packets are marked by the RAN with an indication indicating that the one or more packets have been communicated through the secondary cell; and receive authorization updates from the core network based on the one or more packets. 9. Method according to claim 8, characterized by the fact that the authorization indication includes a quality of service class identifier, QoS, QCI, which is separate from another QCI for data traffic transmitted through the primary cell, and wherein the QCI includes an offload indication associated with the data traffic that is authorized to be offloaded to the secondary cell. 10. The method of claim 9, wherein the download indication includes at least one of an indication that the data traffic is permitted to be downloaded or an indication that the data traffic is to be downloaded to the secondary cell whenever the secondary cell is available, and wherein the discharge indication applies to at least one of an uplink communication over the secondary cell, a downlink communication over the secondary cell, or both uplink communication over the secondary cell and downlink communication over the secondary cell. 11. Method according to claim 8, characterized by the fact that the authorization indication indicates that a carrier that is allowed to be downloaded is loaded as being routed to the secondary cell, wherein the authorization indication includes rules for using cell determined based on a policy of a policy and rule loading function, PCRF, the policy being associated with cell characteristics for the RAN, and in which the primary cell and secondary cell are used based on the cell usage rules cell. 12. The method of claim 11, wherein the authorization indication is used to at least one of marking a radio bearer to indicate whether it uses the primary cell or the secondary cell or both the primary cell and the secondary cell, or identify cell usage rules determined based on the received policy, where the primary cell and secondary cell are used based on the cell usage rules. 13. The method of claim 11, wherein cell usage rules are received from a mobility management entity, MME, during an S1, S1-AP, application protocol establishment between the MME and the RAN entity; or wherein the cell usage rules are received from the MME through at least one of an initial context establishment request or a context modification message sent from the MME. 14. Method, according to claim 8, characterized by the fact that the authorization indication is received through an operation, administration and maintenance protocol, OAM. 15. The method of claim 8, further comprising: receiving a first aggregate maximum bit rate value, AMBR, for the primary cell and a second AMBR value for the secondary cell with an indication that the first AMBR value is for the primary cell and the second AMBR value is for the secondary cell, wherein the determination to communicate through at least one of the primary cell or the secondary cell is further based on at least one of the first value AMBR or the second AMBR value, wherein the first AMBR value includes a first uplink AMBR value and a first downlink AMBR value for the primary cell, and the second AMBR value includes a second uplink AMBR value and a second downlink AMBR value for the secondary cell.