Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
  • H04W8/24—Transfer of terminal data
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/15—Setup of multiple wireless link connections

Definitions

• the present disclosure relates to cellular devices and more specifically to indicating support of more than one data radio bearer for cellular internet of things devices.
• Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device.
• Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLAN), which is commonly known to industry groups as Wi-Fi.
• 3GPP 3rd Generation Partnership Project
• LTE long term evolution
• IEEE 802.16 which is commonly known to industry groups as worldwide interoperability for microwave access
• Wi-Fi wireless local area networks
• the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE).
• E-UTRAN Evolved Universal Terrestrial Radio Access Network
• Node B also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB
• RNC Radio Network Controller
• RANs use a radio access technology (RAT) to communicate between the RAN Node and UE.
• RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provide access to communication services through a core network.
• GSM global system for mobile communications
• EDGE enhanced data rates for GSM evolution
• GERAN enhanced data rates for GSM evolution
• UTRAN Universal Terrestrial Radio Access Network
• E-UTRAN which provide access to communication services through a core network.
• Each of the RANs operates according to a specific 3GPP RAT.
• the GERAN implements GSM and/or EDGE RAT
• the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT
• E- UTRAN implements LTE RAT.
• UMTS universal mobile telecommunication system
• a core network can be connected to the UE through the RAN Node.
• the core network can include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobility management entity (MME).
• SGW serving gateway
• PGW packet data network gateway
• ANDSF access network detection and selection function
• ePDG enhanced packet data gateway
• MME mobility management entity
• FIG. 1 is a schematic diagram of a communication system for providing wireless communication services to a UE or other mobile wireless device consistent with
• FIG. 2 is a process diagram illustrating a UE requested bearer resource modification consistent with embodiments disclosed herein.
• FIG. 3 is a process diagram of a dedicated bearer activation procedure consistent with embodiments disclosed herein.
• FIG. 4 is code illustrating a UE-Capability-NB information element consistent with embodiments disclosed herein.
• FIG. 5 is another table illustrating an example of a bit listing 500 for a UE network capability information element consistent with embodiments disclosed herein.
• FIG. 6 is a flow chart illustrating a method for indicating support for more than one data radio bearer for a NB-IoT cellular device.
• FIG. 7 is a data flow diagram illustrating data flow between a UE and Serving Gateway /Packet Data Network (PDN) Gateway (S/P-GW) in dual connectivity configuration consistent with embodiments disclosed herein.
• PDN Packet Data Network
• S/P-GW Serving Gateway /Packet Data Network Gateway
• FIG. 8 is a block diagram illustrating electronic device circuitry that may be radio access network (RAN) node circuitry (such as an eNB circuitry), UE circuitry, network node circuitry, or some other type of circuitry consistent with embodiments disclosed herein.
• RAN radio access network
• FIG. 9 is a block diagram illustrating example components of a user equipment (UE) or mobile station (MS) device consistent with embodiments disclosed herein.
• UE user equipment
• MS mobile station
• a cellular internet of things (CIoT) device to indicate support (or lack thereof) for more than one data radio bearer (DRB).
• DRB data radio bearer
• a maximum number of bearers is fixed to a known value and there is no signaling to convey this information to the network, and the network's mechanisms are not defined, assuming always that each UE might support a different number of bearers.
• NB-IoT it can be defined as an optional capability feature that UEs have different maximum supported number of bearers.
• mechanisms to exchange the UE bearer capability information can be used to communicate with the network to handle and/or ensure that the network only establishes up to the maximum supported number of bearers.
• This mechanism can be related to 3GPP radio interface architecture and protocols, UE-Core Network-L3 radio protocols, core network side of the IoT reference point, system- wide architecture, and devices operated in long term evolution (LTE), UMTS, GERAN, fourth generation (4G) and fifth generation (5G) RATs.
• LTE long term evolution
• UMTS UMTS
• GERAN fourth generation
• 5G fifth generation
• This mechanism can be applicable for UEs (such as phones or smartphones) where, for example, the systems can support normal access or can tolerate long delays in terms of reachability.
• the mechanism can be applicable, for example, for Cellular Internet of Things (CIoT), Machine-Type Communications (MTC), narrowband IoT (NB-IoT) or non- B-IoT (i.e., wide band UEs that operate within the whole system bandwidth (BW), e.g., WB-E-UTRAN) devices. Therefore this mechanism can be applicable to any UE category, although for simplicity this disclosure focuses on MTC related UE categories, such as a Rel-13 category Ml UE or a Rel-13 NB-IoT UE.
• CCIoT Cellular Internet of Things
• MTC Machine-Type Communications
• NB-IoT narrowband IoT
• BW system bandwidth
• UEs of categories 1 - 5 support 8 data radio bearers (DRBs). Defining a UE that supports less than 8 bearers and associated signaling of the maximum number of DRBs supported would enable less capable UEs. A motivation can be to reduce a size for the associated UE hardware and/or memories and a corresponding UE cost. This reduced DRB capability can also increase network resources available, because without more information, a network currently assumes that UEs can establish up to 8 DRBs. In the network side, there can be a one-to-one mapping of these DRBs to the end-to-end evolved packet system (EPS) bearers.
• EPS evolved packet system
• This mechanism introduces optional Multiple DRB UE capability for UEs supporting Rel-13 CIoT UP solution (i.e., transfer of user data via DRB and UE AS context caching). Multiple DRB UE capabilities can be signaled with a solution for 2 DRBs.
• a NB-IoT UE supporting user plane optimization can optionally support more than 1 DRB.
• a higher capable NB-IoT UE can support 2 DRBs.
• This signaling to the network can help limit creation of new DRBs beyond what is supported by the UE.
• a UE can limit sending a request to establish new bearers.
• limiting DRB creation by the UE is not possible and the decision needs to be driven by the network, as the UE might not have all the required information.
• the request can be controlled by the UE.
• the UE According to the Rel-12 version of TS 24.301, section 6.5.1.4A, "[i]f the maximum number of active EPS bearer contexts is reached at the UE (see subclause 6.5.0) and the upper layers of the UE request connectivity to a PDN the UE shall not send a PDN CONNECTIVITY REQUEST message unless an active EPS bearer is deactivated."
• the UE does not know if the new PDN connection requested by the UE requires the usage of a new bearer or not.
• a PDN connection pinned to the Control plane e.g., a Service Capability Exposure Function (SCEF) connection
• SCEF Service Capability Exposure Function
• DRB new RAN bearer
• SRB signaling radio bearer
• NAS non-access stratum
• the UE sends a request for dedicated resources, e.g., for IP connectivity (even for non-guaranteed bit rate (GBR)), then it is up to the core network (CN) nodes to decide whether a new EPS bearer will be created or whether an existing one will be modified. E.g., this might be a decision taken by the MME, the Packet Data Network
• P-GW Policy and Charging Rules Function
• PCRF Policy and Charging Rules Function
• the activation of a dedicated EPS bearer can also be initiated by the CN, e.g., triggered by an application server (AS) or by some information sent by the UE on the application level.
• AS application server
• New mechanisms can be used to exchange the UE bearer capability information with the network and to actually handle and/or ensure that the UE only establishes up to the maximum supported number of DRBs that can be used.
• These mechanisms can be applicable for various systems (e.g., UE and network side systems) that are designed to operate in full system bandwidth (BW), reduced bandwidth (BR) or narrowband (NB).
• BW system bandwidth
• BR reduced bandwidth
• NB narrowband
• the UE or network can operate within the full BW, BR or NB, such as 20MHz, 10MHz, 1.4MHz, 200kHz or 180kHz bandwidth.
• LTE systems e.g., UE and network side systems
• BR reduced bandwidth
• NB narrowband
• the UE or network can operate within the full BW, BR or NB, such as 20MHz, 10MHz, 1.4MHz, 200kHz or 180kHz bandwidth.
• LTE systems e.g., NB-IoT systems or 5G UE and/or network systems.
• NAS PDU Protocol Data Unit
• containers For new elements or messages, exemplary names are used for simplicity, but naming conventions should not restrict the scope of embodiments disclosed herein.
• DRBs data radio bearers
• SRB signal radio bearers
• a similar kind of capability or signaling mechanism can be defined to enable a separate control of each of these different kinds of bearers.
• New mechanisms are defined to exchange the UE bearer capability information with the network and to actually handle and/or ensure that the UE only establishes up to the maximum supported number of bearers.
• the UE bearer capability information (sometimes referred to as bearer-support) is a single option or multiple options that the UE can support.
• This bearer-support information indicates the maximum number of data radio bearers that a UE can support.
• This information can be conveyed to the network in different ways, including UE radio access capability information, a new indication IE defined in the UE context but outside of the UE radio capabilities (the bearer-support indication is sent to the CN node or the UE sends the bearer- support indication to eNB in random access channel (RACH) or radio resource control (RRC) message) or new information stored in UE subscription data in a home subscriber server (HSS), home location register (HLR), or authentication authorization and accounting (AAA) server.
• RACH random access channel
• RRC radio resource control
• the bearer-support information is present in a new IE within the UE radio access capability information (see 3GPP TS 36.331).
• the UE radio access capabilities are retrieved by the eNB during a connection and stored in the MME when the UE is idle.
• the MME provides it to the eNB when the UE transitions from idle to connected mode; alternatively this information is also kept stored in the eNB if the UE is suspended.
• the UE radio capabilities are stored in a transparent manner within the UE context in the MME, which means that the MME might not interpret the capability information.
• the MME interpret this information in order to determine a maximum number of data radio bearers supported by the UE.
• a new indication IE is defined in the UE context but outside of the UE radio capabilities.
• the bearer-support information can be within a new IE that is indicated to the network in different ways.
• this new IE is created outside of the UE radio access capability structure which is stored transparently within the UE context in the MME. The MME would be able to get this information without having to check the UE radio access capability structure.
• the bearer-support indication is sent to the CN node (e.g., MME) via, e.g., a NAS message.
• a NAS message e.g., a NAS message.
• this information might be defined within the NAS Attach Request or NAS tracking area update (TAU)/routing area update (RAU) Request.
• TAU NAS tracking area update
• RAU routing area update
• the UE sends the bearer-support indication to eNB in a RACH or RRC message (e.g., RRC Connection Request, RRC Connection Setup Complete, RRC Connection Reconfiguration, UE Capability Information, etc.).
• RACH or RRC message e.g., RRC Connection Request, RRC Connection Setup Complete, RRC Connection Reconfiguration, UE Capability Information, etc.
• This option includes the possibility that the bearer-support indication is included as part of the UE radio access capabilities provided to the eNB.
• the eNB can then indicate the bearer-support indication to the MME by adding the new indication IE in an Sl-AP message.
• This Sl-AP message can be a legacy Sl-AP message (e.g., Sl-AP initial UE message) or a new Sl-AP message can be defined to carry this bearer-support indication in other cases.
• this new bearer-support indication can be determined based on other information that allows the network to distinguish or characterize the UEs for a certain maximum number or bearers. This can be for UEs belonging to a certain group, a certain UE category or certain UE class, or certain UE service category classes. New information can be stored in UE subscription data in a home subscriber server (HSS), a home location register (HLR), or an authentication authorization and accounting (AAA) server.
• HSS home subscriber server
• HLR home location register
• AAA authentication authorization and accounting
• this information is downloaded to MME from these entities as part of an Insert Subscription Data During Attach/TAU procedure.
• This support information is also sent by MME to another MME during inter MME relocation/handover.
• this approach ties the subscription and the device capabilities together which can have some implications. For example, if the USIM was placed into a UE of a different UE capabilities then the network which is getting the bearer-support indication from the subscription data can continue to treat this UE based on the bearer-support subscription indication regardless of its UE capabilities.
• eUICCs embedded UICCs
• IMEI International Mobile Equipment Identity
• IMEISV International Mobile Equipment Identity
• a mechanism can be provided to ensure that the UE does not exceed the maximum bearers supported.
• the maximum number indicated by the bearer-support can be used by the CN node (e.g., MME) or eNB when having to establish a new PDN connection or reconfiguring an existing one based on a new request. This can involve the CN node or eNB rejecting a request from another node to establish a bearer taking into account the maximum number of data radio bearers supported by the UE.
• the node receives a Bearer Establishment Request for a UE from another node and this node realizes all of the DRBs that the UE is capable of supporting are already established, it can reject the Bearer Establishment Request.
• the node looks at the quality of service (QoS) requirements for the bearer establishment and may reject it even if the maximum number of DRBs that the UE is capable of is not established. This can be based on the priority of the Bearer Request to allow a spare DRB to be kept for higher priority.
• the node may preempt an existing DRB of the UE to allow the establishment of a higher priority DRB when all the DRBs the UE is capable of supporting were already established.
• QoS quality of service
• the UE can also use this information when deciding whether to request or accept the
• the bearer-support indication can also be used by the MME during PDN connection establishment, when deciding whether to pin the PDN connection to the Control plane or not.
• SCEF service capability exposure function
• the MME could still decide to pin the PDN connection or not (e.g., based on the APN requested by the UE). Pinning the PDN connection would allow the UE to have more additional PDN connections active simultaneously.
• FIG. 1 is a schematic diagram of a communication system 100 for providing wireless communication services to a UE 102 or other mobile wireless device.
• the system 100 includes a plurality of RANs including RAN Node 104 through which the UE 102 may access IP services or other data services within cell coverage 108 of the RAN Node 104, such as voice services or the Internet.
• the system 100 may include a global system for mobile communications (GSM) enhanced data rates for GSM evolution (EDGE) RAN (GERAN), a UTRAN, and/or an E-UTRAN, which provide access to communication services through a core network 116 (e.g., an EPC).
• GSM global system for mobile communications
• EDGE enhanced data rates for GSM evolution
• GERAN enhanced data rates for GSM evolution
• UTRAN e.g., an EPC
• Each of the RANs operates according to a specific 3 GPP RAT.
• the GERAN implements GSM and/or EDGE RAT
• the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3 GPP RAT
• the E-UTRAN implements LTE RAT.
• Each of the RANs includes one or more base stations or other infrastructure for wirelessly communicating with the UE 102 and providing access to communication services.
• the E-UTRAN includes one or more e Bs, such as RAN Node 104, which are configured to wirelessly communicate with the UE 102.
• the core network 116 may include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an ANDSF server, and an enhanced packet data gateway ePDG.
• SGW serving gateway
• PGW packet data network gateway
• ANDSF server an enhanced packet data gateway ePDG.
• the PGW may be connected to the WAG via the ePDG using the S2b interface (for the case of untrusted access) and to the TWAG and ASN-GW using the S2a interface (for the case of trusted access).
• SGW serving gateway
• PGW packet data network gateway
• ANDSF server an enhanced packet data gateway ePDG.
• the PGW may be connected to the WAG via the ePDG using the S2b interface (for the case of untrusted access) and to the TWAG and ASN-GW using the S2a interface (for the case of trusted access).
• UE 102 communicates with the EPC 116 through an access link 112 to the RAN Node 104 using a RAT, which then uses a backhaul link 118 to provide the UE
• the EPC 116 How many DRBs 120, 122 are supported by UE 102 can be indicated by Multiple DRB supported indicator 103.
• the UE 102 supports multiple DRBs 120, 122 and using the two DRBs 120, 122 to communicate with the RAN Node 104 over access link 112.
• the DRBs 120, 122 have a one-to-one correspondence with EPS bearers 124, 126 in communication with the EPC 116 over backhaul link 118.
• FIG. 2 shows a UE requested bearer resource modification.
• a UE 202 sends a request bearer resource modification message 216 through the link with the eNodeB 204 to the MME 206.
• the MME 206 sends a bearer resource command 217 to the S-GW 210.
• the S-GW 210 sends a bearer resource command 218 to the PDN-GW 212.
• the PDN-GW 212 and PCRF 214 perform a first part of a policy and charging enforcement function (PCEF) initiated internet protocol connectivity access network (IP-CAN) session modification 220.
• PCEF policy and charging enforcement function
• the system 200 can perform 222 dedicated bearer activation, a bearer modification procedure or a dedicated bearer deactivation procedure.
• the PDN-GW 212 can then communicate the second part of a PCEF initiated IP-CAN session modification 224 to the PCRF 214.
• the MME 206, the P-GW or the PCRF can use the bearer-support indication together with the number of already allocated DRBs when processing a request from the UE for dedicated bearer resources for a PDN connection for which one or more DRBs have already been allocated.
• the network can decide to allocate a new EPS bearer or to modify an existing one.
• the network should - if possible - modify an existing EPS bearer (e.g., by modifying the QoS Class Identifier (QCI) of the bearer and adding the packet filter(s) for the new packet flow to the corresponding traffic flow template (TFT)).
• QCI QoS Class Identifier
• TFT traffic flow template
• the MME 206 could signal with the GTP message bearer resource command to the Serving-GW (S-GW) 210, P-GW and PCRF either: (1) both the maximum number of DRBs supported by the UE and the number of already allocated DRBs; or (2) only an indication whether establishment of another DRB is not possible (i.e., whether the number of already allocated DRBs is equal to the maximum number of DRBs supported by the UE).
• S-GW Serving-GW
• PCRF only an indication whether establishment of another DRB is not possible (i.e., whether the number of already allocated DRBs is equal to the maximum number of DRBs supported by the UE).
• the second option can be sufficient, because a UE can have PDN connections to multiple P-GWs or SCEFs (or both), and it is not intended to inform P-GW 1 when the UE deactivates an EPS bearer related to a PDN connection towards, e.g., P-GW 2. This means the indication might be valid for the specific bearer resource allocation and is not supposed to be stored by the P-GW 1 for later use.
• FIG. 3 shows a dedicated bearer activation procedure 300.
• the PCRF communicates an IP-CAN session modification 320 to the PDN-GW 310.
• PDN-GW sends a create bearer request 322 to the serving GW 308.
• the serving GW 308 sends a create bearer request 324 to the MME 306.
• the MME 306 sends a bearer setup request/session management request 326 to the eNodeB 304.
• the eNodeB 304 sends a RRC Connection Reconfiguration 328 to UE 302.
• the UE 302 sends a RRC connection reconfiguration complete message 330 to eNodeB 304.
• the eNodeB 304 sends a bearer setup response 322 to MME 306.
• the UE 302 sends a direct transfer 334 to eNodeB 304.
• the eNodeB 304 sends a session management response 336 to MME 306.
• the MME 306 sends a create bearer response 338 to serving GW 308.
• Serving GW 308 sends a create bearer response 340 to PDN GW 310.
• PDN GW 310 sends an IP-CAN session modification 342 to PCRF 312.
• the MME 306 can, after operation 3 (i.e., upon receipt of a create bearer request from the S-GW), check whether the number of already allocated DRBs is equal to the maximum number of DRBs supported by the UE. If yes, then the MME 306 could immediately reject the request, thus avoiding the unnecessary signaling shown in operations 4 to 9 (324 to 336) in FIG. 3.
• the PCRF 312 or the P-GW terminates the bearer activation and initiates a modification of an existing EPS bearer instead.
• the MME 306 could proceed with the signaling procedure as shown in FIG. 3. It is then left to the UE to decide upon receipt of the RRC Connection Reconfiguration message in operation 5 whether to reject the request (not shown in the figure); or whether to accept the request temporarily (operation 6) and afterwards deactivate one of the existing EPS bearers using a DRB by means of a UE requested bearer resource modification (see FIG. 2).
• the deactivated EPS bearer can belong to another PDN connection which is no longer needed or which has a lower priority compared to the PDN connection for which the new EPS bearer was created.
• Max Bearer-Support support can also be used as a UE configuration.
• the operator may want to restrict the maximum number of data radio bearers a UE could establish even though the device itself is capable of establishing multiple bearers (for example to reduce the number of applications requiring DRB on the device, or to reduce the UE's ability of causing congestion in the network).
• the operator may configure the device, for example using SFM-OTA or OMA-DM, to a certain "Max Bearer- Support" value.
• FIG. 4 shows a UE-Capability-NB information element 400.
• the MultipleDRB-rl3 field is part of a UE-Capability NB-rl3 information element 400. This field defines whether the UE supports multiple DRBs. In some embodiments, this field is applicable if the UE supports User plane CIoT EPS Optimization and a UE-Category-NB. In the embodiment, if a UE of this release supports multiple DRBs, the UE supports at least two simultaneous DRBs. In an alternative embodiment, the MultipleDRB-rl3 field is encoded as an integer value defining the maximum number of DRBs the UE can support.
• FIG. 5 shows an example of a bit listing 500 for a UE network capability information element.
• a purpose of the UE network capability information element is to provide the network with information concerning aspects of the UE related to EPS or interworking with GPRS. The contents might affect the manner in which the network handles the operation of the UE.
• the UE network capability information indicates general UE characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on.
• the UE network capability information element can be coded as shown in FIG. 5.
• the UE network capability is a type 4 information element with a minimum length of 4 octets and a maximum length of 15 octets.
• Multiple DRB support (multipleDRB which is octet 9, bit 1) indicates the capability to support multiple user plane radio bearers in NB-Sl mode.
• a bit set to 0 indicates that Multiple DRB is not supported.
• a bit set to 1 indicates Multiple DRB is supported.
• Other bits in octet 10 to 15 are spare and can be coded as zero, if the respective octet is included in the information element.
• the multipleDRB field is encoded as an integer value in 2 or more bits defining the maximum number of DRBs the UE can support.
• FIG. 6 shows a method for indicating support for more than one data radio bearer for a NB-IoT cellular device. This can be performed by systems shown in FIGs. 1, 7, 8 or 9, including a UE, baseband circuitry, and RF circuitry, among others.
• a narrowband internet of things (NB-IoT) cellular device determines that a set of radio access capability parameters including a value indicating support for more than one data radio bearer are to be signaled to a network.
• the NB-IoT cellular device generates a message to the network including the value indicating support for more than one data radio bearer with the radio access capability parameters.
• Block 602 can be performed as a part of an attach procedure or tracking update procedure or as part of otherwise providing an information element.
• the UE can operate the other way around.
• the UE is configured by the operator to a new value (as described above), the UE determines that the value of the Support Indicator has changed and therefore it needs to signal the new value to the network. To this purpose it initiates a tracking area update (TAU) procedure.
• TAU tracking area update
• an attach procedure initiation is performed. If the UE supports user plane CIoT EPS optimization and multiple user plane radio bearers in NB-Sl mode, then the UE shall set the Multiple DRB support bit to "Multiple DRB supported" in the UE network capability IE of the ATTACH REQUEST message.
• normal and periodic tracking area updating procedure initiation can be performed. If the UE supports user plane CIoT EPS optimization and multiple user plane radio bearers in NB-Sl mode, then the UE shall set the Multiple DRB support bit to "Multiple DRB supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message.
• the following UE radio access capability parameters are applicable in NB-IoT: The UE radio access capability parameters can be included. The following subclauses define the UE radio access capability parameters and minimum capabilities for multimedia broadcast multicast service (MBMS) capable UE. Only parameters for which there is the possibility for UEs to signal different values are considered as UE radio access capability parameters. Therefore, mandatory features without capability parameters that are the same for all UEs are not listed here. Also capabilities which are optional or conditionally mandatory for UEs to implement but do not have UE radio access capability parameter are listed in this specification.
• MBMS multimedia broadcast multicast service
• E-UTRAN needs to respect the signalled UE radio access capability parameters when configuring the UE and when scheduling the UE.
• NB-IoT is a separate RAT from E-UTRAN.
• the UE radio access capability parameter indicates whether the feature has been implemented and successfully tested.
• the parameter indicates whether the feature has been successfully tested.
• the IE UE-Capability-NB can be used to convey the NB-IoT UE radio access capability parameters.
• the IE UE-Capability-NB is transferred in NB-IoT.
• the UE- Capability-NB information element can include: multipleDRB-rl3 which is ENUMERATED ⁇ supported ⁇ and OPTIONAL.
• Radio Resource Control protocol can be specified for the radio interface between UE and E-UTRAN as well as for the radio interface between RN and E-UTRAN.
• a scope of the description can include: the radio related information transported in a transparent container between source eNB and target eNB upon inter eNB handover; and the radio related information transported in a transparent container between a source or target eNB and another system upon inter RAT handover.
• Control plane CIoT EPS optimization can enable support of efficient transport of user data (IP, non-IP or SMS) over the control plane via the MME without triggering data radio bearer establishment.
• the RRC protocol can include the following main functions: Establishment/ modification/release of RBs carrying user data (DRBs); and NB-IoT RRC multiplicity and type constraint values.
• a UECapabilitylnformation-NB message is used to transfer of UE radio access capabilities requested by the E-UTRAN.
• This transfer can include a Signaling radio bearer: SRB1 or SRB lbis, a RLC-SAP: AM, a Logical channel: DCCH and/or Direction: UE to E UTRAN.
• the IE UE-Capability-NB is used to convey the NB-IoT UE Radio Access Capability Parameters.
• the IE UE-Capability-NB is transferred in NB-IoT only. It can include a multipleDRB field that defines whether the UE supports multiple DRBs.
• FIG. 7 is a data flow diagram illustrating data flow between a UE and Serving Gateway /Packet Data Network (PDN) Gateway (S/P-GW) in dual connectivity configuration consistent with embodiments disclosed herein. While this example uses two radio links, one towards Master eNB (MeNB) and one towards Secondary eNB (SeNB), it should be recognized that a single link can be used.
• Application specific packets 722, 724 and 726 are generated from applications 702, 704 and 706 on UE 708.
• a first traffic flow template (TFT) including one or more packet filters 736 routes packets 722, 724 to a first wireless interface for transmission to MeNB 710 based on application specific attributes or bearer.
• TFT first traffic flow template
• a second TFT including one or more packet filters 736 routes packets 726 to a second wireless interface for transmission to SeNB 711.
• one of the TFTs may be missing, and any packet which does not match the filter criteria of any of the packet filters of the other TFT(s) is routed to the wireless interface not associated with a TFT (default wireless interface).
• MeNB 710 and SeNB 711 transmit the packets 722, 724 and 726 to S/P- GW 712.
• S/P-GW 712 transmits traffic flows 762, 764 and 766 to service 714 that includes application 1 (716), application 2 (718) and application 3 (720).
• traffic flow aggregates can be formed by means of the TFTs (a first TFT that includes packet filters matching packets 722 and 724 and a second TFT that includes packet filters matching packets 726).
• Packets 722 and 724 flow through PDCP layer 728 (becoming associated with a radio bearer) through RLC layer 730 (becoming associated with a logical channel (DTCH)) through MAC layer 732 (becoming associated with a transport channel (ULSCH)) and through the PHY layer 734 (becoming associated with a physical channel (PUSCH)) to be transmitted to MeNB 710.
• Packets 726 flow through a second protocol stack through PDCP layer 738 (becoming associated with a radio bearer) through RLC layer 740 (becoming associated with a logical channel (DTCH)) through MAC layer 742 (becoming associated with a transport channel (ULSCH)) and through the PHY layer 744 (becoming associated with a physical channel (PUSCH)) to be transmitted to SeNB 711.
• PDCP layer 738 becoming associated with a radio bearer
• RLC layer 740 (becoming associated with a logical channel (DTCH))
• MAC layer 742 becoming associated with a transport channel (ULSCH)
• PHY layer 744 becoming associated with a physical channel (PUSCH)
• the packets 722, 724 and 726 are received by MeNB 710 and SeNB 711 and sent to S/P-GW 712, which can provide the packets to service 714 that includes application 1 (716), application 2 (718) and application 3 (720).
• a transmission from UE 708 to SeNB 711 based on packets 726 is routed through PHY layer 754 to MAC layer 756 to RLC layer 758 to PDCP layer 760 and then through an EPS bearer to S/P-GW 712 which routes packets 726 to application 720 (becoming traffic flow 762).
• a transmission from UE 708 to MeNB 710 based on packets 722 and 724 is routed through PHY layer 746 to MAC layer 748 to RLC layer 750 to PDCP layer 752 and then through an EPS bearer to S/P-GW 712 which routes packets 722 and 724 to applications 716 and 718 (becoming traffic flows 766 and 764).
• UE is running a GPS voice directions application.
• Current positioning information is reported by application 1 (702 on UE 708 and 716 on service 714).
• Voice directions are handled by application 2 (704 on UE 708 and 718 on service 714).
• a background map cache is provided by application 3 (706 on UE 708 and 720 on service 714).
• Positioning information (packets 724) and voice directions (packets 724) can be timing and reliability sensitive (as routes may need to be recalculated).
• a background map cache (packets 726) can be quickly loaded and stored for later use, allowing for high current data rates, but more unreliable connections if small updates are needed.
• MeNB 746 can determine that application 3 (706 on UE 708 and 720 on service 714) can make use of SeNB 711 and enables SeNB 711 for use (such as a request to turn on and/or accept connections from UE 708).
• MeNB 710 can then configure the radio bearer (738 on UE 708 and 760 on network side) to be used with the second TFT including packet filters 736 (on both UE 708 and EPC, such as S/P-GW 712) to filter packets based on application based criteria (such as IP address, application of origin, etc.).
• Positioning information (packets 724) and voice directions (packets 722) are routed over a more robust (but potentially slower) link to MeNB 710 by packet filter 736.
• Background map cache (packets 726) are routed over a less robust (but potentially faster) link from SeNB 711 to UE 708 by packet filters in the S/P-GW 712.
• the sequence of events is: 1) The UE requests additional bearer resources (see, e.g., FIG. 2). 2) The network then activates a dedicated EPS bearer (with associated TFT). At this point the first EPS bearer (default bearer) and the new, dedicated bearer are both between UE and (M)eNB. The UE uses the TFT(s) to map the uplink packets to one of the two EPS bearers and such to one of the two DRBs and P-GW uses the TFT(s) to map the downlink packets to one of the 2 EPS bearers. 3) (M)e B decides to switch to a dual connectivity configuration.
• the first EPS bearer (default bearer) is between UE and MeNB, and the dedicated bearer is between UE and SeNB.
• the UE still uses the TFT(s) to map the uplink packets to one of the two EPS bearers and P-GW still uses the TFT(s) to map the downlink packets to one of the two EPS bearers.
• the WLAN technology can be used instead of an SeNB.
• FIG. 8 is a block diagram illustrating electronic device circuitry 800 that may be radio access node (RAN) node circuitry (such as an eNB circuitry), UE circuitry, network node circuitry, or some other type of circuitry in accordance with various embodiments.
• the electronic device circuitry 800 may be, or may be incorporated into or otherwise a part of, a RAN Node (e.g., an eNB), a UE, a mobile station (MS), a BTS, a network node, or some other type of electronic device.
• the electronic device circuitry 800 may include radio transmit circuitry 810 and receive circuitry 812 coupled to control circuitry 814 (e.g., baseband processor(s), etc.).
• the transmit circuitry 810 and/or receive circuitry 812 may be elements or modules of transceiver circuitry, as shown.
• some or all of the control circuitry 815 can be in a device separate or external from the transmit circuitry 810 and the receive circuitry 812 (baseband processors shared by multiple antenna devices, as in cloud-RAN (C-RAN) implementations, for example).
• C-RAN cloud-RAN
• the electronic device circuitry 810 may be coupled with one or more plurality of antenna elements 816 of one or more antennas.
• the electronic device circuitry 800 and/or the components of the electronic device circuitry 800 may be configured to perform operations similar to those described elsewhere in this disclosure.
• the transmit circuitry 810 can transmit an information element and/or a bearer resource modification request as shown in FIG. 2.
• the receive circuitry 812 can receive a RRC connection reconfiguration message as shown in FIG. 3.
• the transmit circuitry 810 can transmit a RRC connection reconfiguration message as shown in FIG. 3.
• the receive circuitry 812 can receive a RRC connection reconfiguration complete message or direct transfer message as shown in FIG. 3.
• a bearer setup request is received from the MME via a fixed line and not via a radio interface.
• the electronic device circuitry 800 shown in FIG. 8 is operable to perform one or more methods, such as the methods shown in FIG. 6.
• circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware
• ASIC Application Specific Integrated Circuit
• processor shared, dedicated, or group
• memory shared, dedicated, or group
• circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
• circuitry may include logic, at least partially operable in hardware.
• FIG. 9 is a block diagram illustrating
• example components of a user equipment (UE) or mobile station (MS) device 900 may include application circuitry 902, baseband circuitry 904, Radio Frequency (RF) circuitry 906, front-end module (FEM) circuitry 908, and one or more antennas 910, coupled together at least as shown in FIG. 9.
• UE user equipment
• MS mobile station
• the UE device 900 may include application circuitry 902, baseband circuitry 904, Radio Frequency (RF) circuitry 906, front-end module (FEM) circuitry 908, and one or more antennas 910, coupled together at least as shown in FIG. 9.
• RF Radio Frequency
• FEM front-end module
• the application circuitry 902 may include one or more application processors.
• the application circuitry 902 may include one or more single- core or multi-core processors.
• the processor(s) may include any combination of general- purpose processors and dedicated processors (e.g., graphics processors,
• the processor(s) may be operably coupled and/or include memory/storage, and may be configured to execute instructions stored in the mem ory /storage to enable various applications and/or operating systems to run on the system.
• the baseband circuitry 904 may include one or more single-core or multi-core processors.
• the baseband circuitry 904 may include one or more baseband processors and/or control logic.
• the baseband circuitry 904 may be configured to process baseband signals received from a receive signal path of the RF circuitry 906.
• the baseband 904 may also be configured to generate baseband signals for a transmit signal path of the RF circuitry 906.
• the baseband processing circuitry 904 may interface with the application circuitry 902 for generation and processing of the baseband signals, and for controlling operations of the RF circuitry 906.
• the baseband circuitry 904 may include at least one of a second generation (2G) baseband processor 904 A, a third generation (3G) baseband processor 904B, a fourth generation (4G) baseband processor 904C, other baseband processor(s) 904D for other existing generations, and generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
• the baseband circuitry 904 e.g., at least one of baseband processors 904A-904D
• the radio control functions may include signal modulation/demodulation, encoding/decoding, radio frequency shifting, other functions, and combinations thereof.
• modulation/demodulation circuitry of the baseband circuitry 904 may be programmed to perform Fast-Fourier Transform (FFT), precoding, constellation mapping/demapping functions, other functions, and combinations thereof.
• FFT Fast-Fourier Transform
• encoding/decoding circuitry of the baseband circuitry 904 may be programmed to perform convolutions, tail-biting convolutions, turbo, Viterbi, Low Density Parity Check (LDPC) encoder/decoder functions, other functions, and combinations thereof.
• Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and may include other suitable functions.
• the baseband circuitry 904 may include elements of a protocol stack.
• elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements.
• a central processing unit (CPU) 904E of the baseband circuitry 904 may be programmed to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
• the baseband circuitry 904 may include one or more audio digital signal processor(s) (DSP) 904F.
• the audio DSP(s) 904F may include elements for compression/decompression and echo cancellation.
• the audio DSP(s) 904F may also include other suitable processing elements.
• the baseband circuitry 904 may further include memory/storage 904G.
• the memory/storage 904G may include data and/or instructions for operations performed by the processors of the baseband circuitry 904 stored thereon.
• the memory/storage 904G may include any combination of suitable volatile memory and/or nonvolatile memory.
• the memory/storage 904G may also include any combination of various levels of memory/storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc.
• ROM read-only memory
• DRAM dynamic random access memory
• the memory/storage 904G may be shared among the various processors or dedicated to particular processors.
• Components of the baseband circuitry 904 may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 904 and the application circuitry 902 may be implemented together, such as, for example, on a system on a chip (SOC).
• SOC system on a chip
• the baseband circuitry 904 may provide for
• the baseband circuitry 904 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
• EUTRAN evolved universal terrestrial radio access network
• WMAN wireless metropolitan area networks
• WLAN wireless local area network
• WPAN wireless personal area network
• multi-mode baseband circuitry Embodiments in which the baseband circuitry 904 is configured to support radio communications of more than one wireless protocol.
• the RF circuitry 906 may enable communication with wireless networks
• the RF circuitry 906 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
• the RF circuitry 906 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 908, and provide baseband signals to the baseband circuitry 904.
• the RF circuitry 906 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 904, and provide RF output signals to the FEM circuitry 908 for transmission.
• the RF circuitry 906 may include a receive signal path and a transmit signal path.
• the receive signal path of the RF circuitry 906 may include mixer circuitry 906A, amplifier circuitry 906B, and filter circuitry 906C.
• the transmit signal path of the RF circuitry 906 may include filter circuitry 906C and mixer circuitry 906A.
• the RF circuitry 906 may further include synthesizer circuitry 906D configured to synthesize a frequency for use by the mixer circuitry 906A of the receive signal path and the transmit signal path.
• the mixer circuitry 906A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906D.
• the amplifier circuitry 906B may be configured to amplify the down-converted signals.
• the filter circuitry 906C may include a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
• Output baseband signals may be provided to the baseband circuitry 904 for further processing.
• the output baseband signals may include zero- frequency baseband signals, although this is not a requirement.
• the mixer circuitry 906A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
• the mixer circuitry 906A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 906D to generate RF output signals for the FEM circuitry 908.
• the baseband signals may be provided by the baseband circuitry 904 and may be filtered by filter circuitry 906C.
• the filter circuitry 906C may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
• the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path may include two or more mixers, and may be arranged for quadrature downconversion and/or upconversion, respectively.
• the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 906A of the receive signal path and the mixer circuitry 906A of the transmit signal path may be configured for super-heterodyne operation.
• the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
• the output baseband signals and the input baseband signals may be digital baseband signals.
• the RF circuitry 906 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 904 may include a digital baseband interface to communicate with the RF circuitry 906.
• ADC analog-to-digital converter
• DAC digital-to-analog converter
• the synthesizer circuitry 906D may include one or more of a fractional -N synthesizer and a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
• synthesizer circuitry 906D may include a delta-sigma synthesizer, a frequency multiplier, a synthesizer comprising a phase-locked loop with a frequency divider, other synthesizers and combinations thereof.
• the synthesizer circuitry 906D may be configured to synthesize an output frequency for use by the mixer circuitry 906A of the RF circuitry 906 based on a frequency input and a divider control input.
• the synthesizer circuitry 906D may be a fractional N/N+l synthesizer.
• frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
• VCO voltage controlled oscillator
• Divider control input may be provided by either the baseband circuitry 904 or the applications processor 902 depending on the desired output frequency.
• a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 902.
• the synthesizer circuitry 906D of the RF circuitry 906 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
• the divider may include a dual modulus divider (DMD)
• the phase accumulator may include a digital phase accumulator (DP A).
• the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
• the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
• the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
• the DLL may provide negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
• the synthesizer circuitry 906D may be configured to generate a carrier frequency as the output frequency.
• the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency, etc.) and used in conjunction with a quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
• the output frequency may be a LO frequency (fLO).
• the RF circuitry 906 may include an IQ/polar converter.
• the FEM circuitry 908 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 910, amplify the received signals, and provide the amplified versions of the received signals to the RF circuitry 906 for further processing.
• the FEM circuitry 908 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 906 for transmission by at least one of the one or more antennas 910.
• the FEM circuitry 908 may include a TX/RX switch configured to switch between a transmit mode and a receive mode operation.
• the FEM circuitry 908 may include a receive signal path and a transmit signal path.
• the receive signal path of the FEM circuitry 908 may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 906).
• LNA low-noise amplifier
• the transmit signal path of the FEM circuitry 908 may include a power amplifier (PA) configured to amplify input RF signals (e.g., provided by RF circuitry 906), and one or more filters configured to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 910.
• PA power amplifier
• the MS device 900 may include additional elements such as, for example, memory/storage, a display, a camera, one of more sensors, an input/output (I/O) interface, other elements, and combinations thereof.
• additional elements such as, for example, memory/storage, a display, a camera, one of more sensors, an input/output (I/O) interface, other elements, and combinations thereof.
• the MS device 900 may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof.
• circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor
• circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
• circuitry may include logic, at least partially operable in hardware.
• Example 1 is an apparatus of a narrowband user equipment (UE).
• the apparatus includes storage designed to store a set of radio access capability parameters for the narrowband UE including an indicator of support for more than one data radio bearer.
• the apparatus includes one or more baseband processors designed to determine that the set of radio access capability parameters are to be signaled to a network, and encode a message for the network including the indicator of support for more than one data radio bearer with the set of radio access capability parameters.
• Example 2 is the apparatus of Example 1, where to determine that the set of radio access capability parameters are to be signaled to a network further includes to initiate an attach procedure that discloses the set of radio access capability parameters.
• Example 3 is the apparatus of Example 1, where to determine that the set of radio access capability parameters are to be signaled to a network further includes to initiate a tracking area updating procedure.
• Example 4 is the apparatus of Example 1, where the message is a radio resource control message.
• Example 5 is the apparatus of Example 4, where the indicator is part of a
• Example 6 is the apparatus of Example 1, where the UE is designed to
• NB-IoT narrowband internet of things
• Example 7 is the apparatus of Example 1, where the UE is designed to
• E-UTRAN evolved UMTS Terrestrial Radio Access Network
• Example 8 is the apparatus of Example 1, where the network includes at least one of an enhanced Node B (eNB) or mobility management entity (MME).
• eNB enhanced Node B
• MME mobility management entity
• Example 9 is the apparatus of Example 1, where the message is an Evolved Packet System (EPS) Mobility Management (MM) message.
• EPS Evolved Packet System
• MM Mobility Management
• Example 10 is the apparatus of Example 9, where the indicator is part of a UE network capability information element.
• Example 11 is an apparatus of an evolved universal mobile telecommunications system (UMTS) Terrestrial Radio Access Network (E-UTRAN) entity.
• the apparatus includes storage designed to store a variety of sets of radio access capability parameters for one or more cellular internet of things (CIoT) user equipments (UEs), a set of radio access capability parameters including an indicator of support for more than one data radio bearer.
• the apparatus includes one or more processing units designed to process a variety of sets of radio access capability parameters from a set of CIoT UEs including indicators of support for more than one data radio bearer, and process a first request to establish an additional evolved packet system (EPS) bearer for a first CIoT UE from the set of CIoT UEs.
• EPS evolved packet system
• the apparatus also includes one or more processing units designed to, in response to the first request, determine that the first CIoT UE supports more than one data radio bearer based at least in part on a first indicator of support for more than one data radio bearer, and based at least in part on the first indicator of support for more than one data radio bearer indicating a support for more than one data radio bearer, design the additional radio bearer for use with the first CIoT UE.
• Example 12 is the apparatus of Example 11, where the one or more processing units are further designed to process a second request to establish an additional EPS bearer for a second CIoT UE from the set of CIoT UEs.
• the processing units are further designed to process in response to the second request; determine that the second CIoT UE supports one data radio bearer based at least in part on a second indicator of support for more than one data radio bearer, and based at least in part on the second indicator of support for more than one data radio bearer indicating a lack of support for more than one data radio bearer, reuse an existing radio bearer for the CIoT UE, create an additional packet data network (PDN) connection without a data radio bearer, or reject the second request.
• PDN packet data network
• Example 13 is the apparatus of Example 12, where to reuse an existing radio bearer further includes to use an existing radio bearer.
• Example 14 is the apparatus of Example 12, where to reuse an existing radio bearer further includes to release an existing radio bearer and create a new radio bearer.
• Example 15 is the apparatus of Example 11, where the E-UTRAN entity is an enhanced Node B (eNB).
• eNB enhanced Node B
• Example 16 is the apparatus of Example 11, where the E-UTRAN entity is a mobility management entity (MME).
• MME mobility management entity
• Example 17 is the apparatus of Example 11, where to process the set of radio access capability parameters from a CIoT UE including the first indicator of support for more than one data radio bearer further includes to process a message from an attach procedure that discloses the set of radio access capability parameters.
• Example 18 is the apparatus of Example 11, where to process the set of radio access capability parameters from a CIoT UE including the first indicator of support for more than one data radio bearer further includes to process a message from a tracking area updating procedure.
• Example 19 is the apparatus of Example 11, where to process the set of radio access capability parameters from a CIoT UE including the first indicator of support for more than one data radio bearer further includes to process a EPS mobility management (MM) message that includes the first indicator of support for more than one data radio bearer.
• MM EPS mobility management
• Example 20 is the apparatus of Example 19, where the indicator is part of a UE network capability information element.
• Example 21 is the apparatus of Example 11, where E-UTRAN communication with the CIoT UE uses a narrowband internet of things (NB-IoT) radio access technology.
• NB-IoT narrowband internet of things
• Example 22 is the apparatus of Example 11, where to process the set of radio access capability parameters from a CIoT UE including the first indicator of support for more than one data radio bearer further includes to process a radio resource control message that includes the first indicator of support for more than one data radio bearer.
• Example 23 is the apparatus of Example 22, where the indicator is part of a UECapabilitylnformation- B information element.
• Example 24 is a computer program product.
• the computer program product includes a computer-readable storage medium that stores instructions for execution by one or more processors to perform operations of a narrowband internet of things (NB-IoT) cellular device, the operations, when executed by the one or more processors to determine that a set of radio access capability parameters including a value indicating support for more than one data radio bearer are to be signaled to a network, and generate a message to the network including the value indicating support for more than one data radio bearer with the set of radio access capability parameters.
• NB-IoT narrowband internet of things
• Example 25 is the computer program product of Example 24, where to determine that the set of radio access capability parameters are to be signaled to a network further includes to initiate an attach procedure that discloses the set of radio access capability parameters.
• Example 26 is the computer program product of Example 24, where to determine that the set of radio access capability parameters are to be signaled to a network further includes to initiate a tracking area updating procedure.
• Example 27 is the computer program product of Example 24, where to generate the message further includes to generate an evolved packet system (EPS) mobility management (MM) message with the indicator.
• Example 28 is the computer program product of Example 27, where to generate the message further includes to include the indicator as part of a UE network capability information element.
• EPS evolved packet system
• MM mobility management
• Example 29 is the computer program product of Example 24, where the instructions, when executed by the one or more processors, are further designed to transmit the message using a narrowband internet of things ( B-IoT) radio access technology.
• B-IoT narrowband internet of things
• Example 30 is the computer program product of Example 24, where to generate the message further includes to generate the message as a radio resource control message.
• Example 31 is the computer program product of Example 30, where to generate the message as the radio resource control message further includes to include the value as part of a UECapabilitylnformation- B information element.
• Example 32 is the computer program product of Example 24, where the value indicates a maximum number of data radio bearers supported by the NB-IoT cellular device.
• Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system.
• a computer system may include one or more general- purpose or special-purpose computers (or other electronic devices).
• the computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.
• Suitable networks for configuration and/or use as described herein include one or more local area networks, wide area networks, metropolitan area networks, and/or Internet or IP networks, such as the World Wide Web, a private Internet, a secure Internet, a value-added network, a virtual private network, an extranet, an intranet, or even stand-alone machines which communicate with other machines by physical transport of media.
• a suitable network may be formed from parts or entireties of two or more other networks, including networks using disparate hardware and network communication technologies.
• One suitable network includes a server and one or more clients; other suitable networks may contain other combinations of servers, clients, and/or peer-to-peer nodes, and a given computer system may function both as a client and as a server.
• Each network includes at least two computers or computer systems, such as the server and/or clients.
• a computer system may include a workstation, laptop computer, disconnectable mobile computer, server, mainframe, cluster, so-called “network computer” or "thin client,” tablet, smart phone, personal digital assistant or other hand-held computing device, "smart” consumer electronics device or appliance, medical device, or a combination thereof.
• Suitable networks may include communications or networking software, such as the software available from Novell®, Microsoft®, and other vendors, and may operate using TCP/IP, SPX, IPX, and other protocols over twisted pair, coaxial, or optical fiber cables, telephone lines, radio waves, satellites, microwave relays, modulated AC power lines, physical media transfer, and/or other data transmission "wires" known to those of skill in the art.
• the network may encompass smaller networks and/or be connectable to other networks through a gateway or similar mechanism.
• Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD- ROMs, hard drives, magnetic or optical cards, solid-state memory devices, a nontransitory computer-readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
• the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device.
• the volatile and nonvolatile memory and/or storage elements may be a RAM, an EPROM, a flash drive, an optical drive, a magnetic hard drive, or other medium for storing electronic data.
• the eNB (or other base station) and UE (or other mobile station) may also include a transceiver component, a counter component, a processing component, and/or a clock component or timer component.
• One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high-level procedural or an object-oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
• Each computer system includes one or more processors and/or memory; computer systems may also include various input devices and/or output devices.
• the processor may include a general purpose device, such as an Intel®, AMD®, or other "off-the-shelf microprocessor.
• the processor may include a special purpose processing device, such as ASIC, SoC, SiP, FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.
• the memory may include static RAM, dynamic RAM, flash memory, one or more flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, or other computer storage medium.
• the input device(s) may include a keyboard, mouse, touch screen, light pen, tablet, microphone, sensor, or other hardware with accompanying firmware and/or software.
• the output device(s) may include a monitor or other display, printer, speech or text synthesizer, switch, signal line, or other hardware with accompanying firmware and/or software.
• a component may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, or off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
• VLSI very large scale integration
• a component may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
• Components may also be implemented in software for execution by various types of processors.
• An identified component of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, a procedure, or a function. Nevertheless, the executables of an identified component need not be physically located together, but may comprise disparate instructions stored in different locations that, when joined logically together, comprise the component and achieve the stated purpose for the component.
• a component of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
• operational data may be identified and illustrated herein within components, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
• the components may be passive or active, including agents operable to perform desired functions.
• a software module or component may include any type of computer instruction or computer-executable code located within a memory device.
• a software module may, for instance, include one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that perform one or more tasks or implement particular data types. It is appreciated that a software module may be implemented in hardware and/or firmware instead of or in addition to software.
• One or more of the functional modules described herein may be separated into sub-modules and/or combined into a single or smaller number of modules.
• a particular software module may include disparate instructions stored in different locations of a memory device, different memory devices, or different computers, which together implement the described functionality of the module.
• a module may include a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices.
• Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network.
• software modules may be located in local and/or remote memory storage devices.
• data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.

Landscapes

• Engineering & Computer Science (AREA)
• Databases & Information Systems (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)
• Telephonic Communication Services (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=57610423

Family Applications (1)

Country Status (3)

Families Citing this family (5)

Family Cites Families (5)

• 2016
  • 2016-12-06 WO PCT/US2016/065180 patent/WO2017189043A1/en active Application Filing
  • 2016-12-06 EP EP16816830.0A patent/EP3449654A1/de not_active Ceased
• 2017
  • 2017-03-03 TW TW106106959A patent/TWI771290B/zh active

Also Published As

Similar Documents

Legal Events