TW201739310A - Systems, methods and devices for indicating support of more than one data radio bearer for cellular internet of things devices - Google Patents

Abstract

A cellular internet of things (CIoT) device can indicate support (or lack thereof) for more than one data radio bearer (DRB). For example, in at least some long term evolution (LTE) embodiments, a maximum number of bearers is fixed to a known value. In a narrowband internet of things (NB-IoT), it can be defined as an optional capability feature that user equipments (UEs) have different maximum supported numbers of bearers. In some embodiments, mechanisms to exchange the UE bearer capability information can be used to communicate with the network to ensure that the network only establishes up to the maximum supported number of bearers.

Description

System, method and apparatus for indicating support for more than one data radio bearer for a cellular IoT device

The present disclosure relates to cellular devices and, more particularly, to indicating support for more than one data radio bearer for a cellular IoT device.

Wireless mobile communication technology uses various standards and protocols to transfer data between a base station and a wireless mobile device. Wireless communication system standards and protocols may include Third Generation Partnership Project (3GPP) Long Term Evolution (LTE); Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, commonly known as the Global Interoperability for Microwave Access (WiMAX) industry group; And the IEEE 802.11 standard for wireless local area networks (WLANs), commonly known as the Wi-Fi industry group. In a 3GPP Radio Access Network (RAN) in an LTE system, a base station may include an E-UTRAN Node B, such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), in an E-UTRAN (also often indicated as An evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and/or a Radio Network Controller (RNC) RAN node that communicates with a wireless communication device called a User Equipment (UE).

The RAN uses a Radio Communication Technology (RAT) for communication between the RAN node and the UE. The RAN may include Global System for Mobile Communications (GSM), GSM Evolution Enhanced Data Rate (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which are provided over a core network. Access to communication services. The RANs each operate in accordance with a particular 3GPP RAT. For example, GERAN implements a GSM and/or EDGE RAT, UTRAN implements a Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, and E-UTRAN implements an LTE RAT.

A core network can be connected to the UE via the RAN. The core network may include a servo gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, and an enhanced packet data. A gateway (ePDG), and/or a mobility management entity (MME).

In accordance with an embodiment of the present invention, a device for a narrowband user equipment (UE) is specifically provided, comprising: a memory configured to store a set of radio access capability parameters for the narrowband UE, the set of radios The access capability parameter includes an indicator supporting one of more than one data radio bearer; one or more baseband processors configured to: determine that the set of radio access capability parameters are to transmit signaling to a network; The network code 1 includes a message that supports the indicator of more than one data radio bearer along with the set of radio access capability parameters.

A detailed description of one of the systems and methods consistent with embodiments of the present disclosure is provided below. Although a few embodiments are described, it should be understood that the present disclosure is not limited to any embodiment, but includes many alternatives, modifications, and equivalents. In addition, some of the embodiments may be practiced without some or all of these details in order to provide a thorough understanding of the details. In addition, some of the technical material known in the art is not described in detail in order to avoid obscuring the disclosure.

The disclosed techniques, equipment, and methods enable a cellular Internet of Things (CIoT) device to indicate support (or lack of support) to more than one data radio bearer (DRB). For example, in at least some LTE embodiments, the maximum number of bearers is fixed to a known value and no signaling is used to transmit the information to the network, and the mechanism of the network is not defined, provided that Always each UE may support a different number of bearers. In NB-IoT, it can be defined as an optional capability feature in which the UE has one of the different maximum supported bearers. In some embodiments, the mechanism for exchanging UE bearer capability information can be used to communicate with the network to manipulate and/or ensure that the network only establishes a maximum supported number of bearers.

This mechanism may be related to 3GPP radio interface architecture and protocols, UE-Core Network-L3 radio protocol, core network side of IoT reference point, full system architecture, and in Long Term Evolution (LTE), UMTS, GERAN, and fourth generation ( 4G) and fifth generation (5G) RAT operating devices. This mechanism can be applied to UEs (such as mobile phones or smart phones) where, for example, the systems can support normal access or can accommodate long delays depending on reachability. For example, the mechanism can be applied to cellular Internet of Things (CIoT), machine type communication (MTC), narrowband IoT (NB-IoT) or non-NB-IoT (ie broadband operation within the overall system bandwidth (BW)). UE, such as WB-E-UTRAN) device. Therefore, this mechanism can be applied to any UE class, but for the sake of brevity, the disclosure focuses on MTC-related UE categories, such as a Rel-13 class M1 UE or a Rel-13 NB-IoT UE.

In LTE, UEs of categories 1 to 5 support 8 data radio bearers (DRBs) according to section 11 of 3GPP TS 36.331. Defining a UE that supports less than 8 bearers and one of the supported DRB maximum number of associated signaling will achieve a smaller UE. One motivation may be to reduce the size of one of the associated UE hardware and/or memory, and to reduce the cost of a corresponding UE. Reducing DRB capabilities can also increase the available network resources, because without more information, a network currently assumes that the UE can establish up to eight DRBs. In the network side, these DRBs can have a one-to-one mapping relationship with an end-to-end evolved packet system (EPS) bearer.

This mechanism introduces optional multi-DRB UE capabilities for UEs supporting the Rel-13 CIoT UP solution (ie, transferring user data via DRB and UE AS context). Multiple DRB UE capabilities can convey signaling in one of two DRB solutions. One of the NB-IoT UEs that support user plane optimization can optionally support more than one DRB. A higher capability NB-IoT UE can support 2 DRBs.

This signaling to the network can help limit the creation of new DRBs beyond the range that the UE can support. In some cases, a UE may restrict sending a request to establish a new bearer. However, there are situations where it is not possible to restrict the UE from creating a DRB, but rather to drive the decision through the network, since the UE may not have all the required information.

In a first example, if the UE requests to establish a new additional PDN connection, in principle, the UE may control the request whether to send a new PDN connection request. According to Section 6.5.1.4A of Rel-12, TS 24.301, "If the maximum number of active EPS bearers has been reached at the UE (refer to section 6.5.0), and the upper layer of the UE requests connectivity to a PDN, Then the UE shall not send a PDN CONNECTIVITY REQUEST message unless the action of the EPS bearer stops. However, after Rel-13, the UE does not know whether a new PDN connection requested by the UE needs to use a new bearer. For example, a PDN connection pinned to a control plane (eg, a Service Capability Exposure Function (SCEF) connection) would not require the use of a new RAN bearer (ie, DRB) because the data is transmitted through a signaling radio bearer ( SRB) to send (ie, the data is encapsulated through a non-access stratum (NAS)). The UE may not be aware of this information in advance because a network node (e.g., MME) is making decisions during the establishment of the PDN connection (e.g., based on the APN requested by the UE, and the subscription information provided by the HSS, or other criteria).

In a second example, if the UE sends a request for one of the exclusive resources, such as for IP connectivity (even for non-guaranteed bit rate (GBR)), then the core network (CN) node decides whether A new EPS bearer will be created, or an existing one will be modified. For example, this may be a decision made by the MME, the Packet Data Network Gateway (P-GW), or the Policy and Charging Rules Function (PCRF).

The initiation of a dedicated EPS bearer can also be initiated by the CN, for example, by an application server (AS), or by some information sent by the UE on the application layer. In addition, it would be helpful to have the network know in advance whether the UE can support the DRB for another dedicated EPS bearer. If not, the first CN node (eg, MME or P-GW) having information about the maximum number of DRBs that the UE can support can terminate the initiation of a dedicated EPS bearer, thereby avoiding unnecessary signaling between the network and the UE. .

The new mechanism can be used to exchange UE bearer capability information with the network and to actually manipulate and/or ensure that the UE only establishes a maximum of the maximum number of available DRBs.

These mechanisms are applicable to a variety of systems designed to operate at full system bandwidth (BW), reduced bandwidth (BR), or narrowband (NB) (eg, UE and network side systems). The UE or network can operate in full BW, BR or NB, such as 20 MHz, 10 MHz, 1.4 MHz, 200 kH or 180 kHz bandwidth. These mechanisms are applicable to LTE systems, NB-IoT systems, or 5G UEs and/or network systems.

The description herein uses exemplary network messages, but it should be recognized that the scope of the disclosure is not limited to such specific messages. This information can be implemented by other online messages. The mechanism acts as an illustrative use of certain RRC messages, S1 Application Agreement (S1-AP) messages, or a Non-Access Layer Protocol Data Unit (NAS PDU) or container. For new elements or messages, the exemplary names are used for the sake of brevity, but the naming convention should not limit the scope of the embodiments disclosed herein.

The term "carrier" shall not be restricted to a data radio bearer (DRB) even if it is used as an example in the embodiment. In the disclosed embodiment, the DRB is given as an example, but the concept can also be extended to the concept of an EPS bearer or an EPS bearer. Additionally, embodiments may be extended to include other types of carriers, such as signal radio bearers (SRBs). Alternatively, a similar type of capability or signaling mechanism can be defined to enable each of these different kinds of bearers to be individually controlled.

The embodiments focus on transmitting signaling to convey information to the eNodeB or MME, however, it should be appreciated that a similar mechanism may be extended to other CN nodes (such as S-GW, P-GW, PCRF, etc.), It is to be understood that other messages may be involved depending on the interface being affected.

A new mechanism is defined to exchange UE bearer capability information with the network, and to actually manipulate and/or ensure that the UE establishes at most the maximum supported number of bearers.

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 transmitted to the network in a variety of ways, including a Home Subscriber Server (HSS), Local Scratchpad (HLR), or Authentication Authorization and Accountability (AAA) server. UE radio access capability information, one of the UE contexts but one of the UE radio capabilities defined new indication IE (in the random access channel (RACH) or radio resource control (RRC) message, the bearer indication is sent to the CN node, or the UE sends The bearer supports the indication to the eNB), or new information.

In a first embodiment, the bearer support information is presented in a new IE within the UE radio access capability information (please refer to 3GPP TS 36.331). The UE radio access capability is retrieved by the eNB during a connection and is stored in the MME when the UE is idle. The MME provides the UE to the eNB when it transitions from idle to connected mode; alternatively, if the UE is suspended, this information is also kept stored in the eNB.

The UE radio capability is stored in the UE context in the MME in a transparent manner, which means that the MME may not interpret the capability information. However, it is possible for the MME to interpret this information in order to determine the maximum number of data radio bearers supported by the UE.

In another embodiment, a new indication IE is defined in the UE context but outside the UE radio capabilities. The bearer support information can be in a new IE indicating to the network in different ways. In an embodiment, the new IE is created outside the UE radio access capability structure that is transparently stored in the UE context in the MME. The MME will be able to obtain this information without checking the UE radio access capability structure.

In a first embodiment, the bearer support indication is sent to the CN node (e.g., MME) via, for example, a NAS message. Because this information is not expected to change dynamically, this information may be defined in a NAS Attach Request or NAS Tracking Area Update (TAU) / Routing Arrangement Area Update (RAU) request. For example, it may be possible to add a new parameter to the UE Network Capability IE provided to the network during the attach procedure and the TAU/RAU procedure (see, for example, 3GPP TS 24.301 section 9.9.3.34). However, if it is expected to be information that may be dynamically changed, the information may be included in other information elements, such as in a service request, a control plane service request message, and the like. For example, it may be possible to add a new parameter to the device nature IE (see section 9.9.2.0A of 3GPP TS 24.301). The NAS message is forwarded to the MME by the eNB but is not interpreted by the eNB.

In a second embodiment, the UE transmits a bearer support indication to the eNB in a RACH or RRC message (eg, RRC Connection Request, RRC Connection Setup Complete, RRC Connection Reassembly, UE Capability Information, etc.). This option includes the possibility of including a bearer support indication as part of the UE radio access capability provided to the eNB. The eNB may then indicate the bearer support indication to the MME by adding a new indication IE to the S1-AP message. The S1-AP message may be an old S1-AP message (eg, an S1-AP initial UE message), or in other situations, a new S1-AP message may be defined to enforce the bearer support indication.

Alternatively, the new bearer support indication can be determined based on other information that allows the network to distinguish or characterize the UE for a certain maximum number of bearers. This may be for UEs belonging to a certain group, a certain UE class or a certain UE class, or a certain UE service class level. New information may be stored in a UE subscription profile in a Home Subscriber Server (HSS), a Local Register (HLR), or an Authentication Authorization and Accountability (AAA) server.

In some embodiments, this information is downloaded from these entities to the MME as part of the insertion of the subscription material during an add/TAU procedure. This support information is also sent by the MME to another MME during relocation/delivery between MMEs. If the information is statically grouped in HSS/HLR/AAA, this approach will tie the subscription with certain implications to the device capabilities. For example, if the USIM is placed in one UE of a different UE capability, the network that is obtaining the bearer support indication from the subscription data can continue to process the UE based on the bearer support subscription indication, and the UE Nothing to do. However, with the introduction of the embedded UICC (eUICC) for machine type communication devices, it is possible that this form of "USIM roaming" ("plastic card roaming") may become less relevant.

It may also be possible to use the International Mobile Equipment Identity (IMEI or IMEISV) of the UE provided by the MME to the HSS/HLR during the attach procedure in the update location request to perform mapping of one of the bearer support indications. This indication is then downloaded to the MME (and any subsequent MMEs) in the update location Ack.

One mechanism can be provided to ensure that the UE does not exceed the maximum bearer support. In a first embodiment, for a given UE, the maximum number of bearer support indications may be re-assigned by a CN node (eg, MME) or eNB when a new PDN connection must be established, or based on a new request. Used when. This may involve the CN node or eNB rejecting a request from one of the other nodes to establish a carrier that takes into account the maximum number of data radio bearers supported by the UE. For example, if a node receives a bearer setup request for a UE from another node, and the node understands that all DRBs that the UE can support have been established, the bearer setup request may be rejected. Another example may be that the node establishes a Quality of Service (QoS) requirement for the bearer and rejects it even if the maximum number of DRBs that the UE can do is not established. This allows for the priority of a standby DRB to be maintained with a higher priority based on the bearer request. In yet another example, the node may preempt one of the existing DRBs of the UE to allow establishment of a higher priority DRB when all DRBs that the UE can support have been established.

In a second embodiment, and in addition to or in lieu of the first embodiment, the UE may also use this information when deciding whether to request or accept the establishment of a new bearer.

In a third embodiment, when determining whether to pin a PDN connection to the control plane, the MME may also use the carrier support indication during the PDN connection setup. According to 3GPP TS 23.401, when a PDN connection is established for a Service Capability Exposure Function (SCEF), the MME does not select (ie, the PDN connection will be pinned to the control plane and no DRB is established); but it is connected to a P - GW one of the PDN connections, the MME may still decide whether to pin the PDN connection (eg based on the APN requested by the UE). Pinning a PDN connection will allow the UE to have more additional PDN connections at the same time.

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 a RAN node 104 through which the UE 102 can access IP services or other data services within its cell coverage range 108, such as voice services or the Internet. In particular, system 100 can include a Global System for Mobile Communications (GSM), GSM Evolution Enhanced Data Rate (EDGE) RAN (GERAN), a UTRAN, and/or an E-UTRAN that communicates through a core network 116 (eg, An EPC) provides access to communication services. The RANs each operate in accordance with a particular 3GPP RAT. For example, GERAN implements a GSM and/or EDGE RAT, UTRAN implements a Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, and E-UTRAN implements an LTE RAT.

The RANs each include one or more base stations, or other infrastructure for wirelessly communicating with the UE 102 and providing access to communication services. For example, E-UTRAN includes one or more eNBs, such as RAN node 104, that are configured to communicate wirelessly with UE 102.

The core network 116 can include a servo gateway (SGW), a packet data network (PDN) gateway (PGW), an ANDSF server, and an enhanced packet data gateway ePDG. The PGW can connect to the WAG via the ePDG using the S2b interface (access is an untrusted condition), and can connect to the TWAG and ASN-GW using the S2a interface (access is a trusted condition). Those of ordinary skill in the art will recognize that many other components and functions may be included or implemented in the core network 116.

The UE 102 communicates with the EPC 116 over an access link 112 connected to the RAN node 104 using a RAT, which in turn provides UE communication to the EPC 116 using a backhaul link 118. The number of DRBs 120, 122 supported by the UE 102 can be indicated by the multiple DRB support indicator 103. In the illustrated embodiment, the UE 102 supports multiple DRBs 120, 122 and communicates with the RAN node 104 over the access link 112 using two DRBs 120, 122. The DRBs 120, 122 have a one-to-one correspondence with the EPS bearers 124, 126 when communicating with the EPC 116 via the return link 118.

Figure 2 shows a UE requesting bearer resource modification. A UE 202 transmits a request bearer resource modification message 216 to the MME 206 over the link with the eNodeB 204. 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 the PCRF 214 perform a policy and billing enforcement function (PCEF) initiated by the first part of the Internet Protocol Connectivity Access Network (IP-CAN) Work Phase Modification 220. Depending on whether the UE can support another bearer as indicated by the bearer support indicator, the system 200 can perform 222 exclusive bearer startup, a bearer modification procedure, or a dedicated bearer stop action procedure. PDN-GW 212 may then pass a second portion of a PCEF initiated IP-CAN session modification 224 to PCRF 214.

In a fourth embodiment, and as a further possible use case, the MME 206, P-GW or MME 206, when processing one of the dedicated bearer resources from the UE for one of the one or more DRB connections has been allocated The PCRF can use the bearer support indication along with the number of allocated DRBs. In general, depending on the QoS requested for the new dedicated bearer resource and the QoS of the established EPS, the network may decide to allocate a new EPS bearer or modify an existing one. If the UE has reached the maximum number of supported DRBs, the network should modify an existing EPS bearer if possible (for example by modifying the QoS Class Identifier (QCI) of the bearer and for the new packet stream (more) Packet filtering is added to the corresponding Traffic Flow Template (TFT).

To achieve this, the MME 206 can transmit signaling to the Serving GW (S-GW) 210, the P-GW, and the PCRF by using the GTP Message Bearer Resource Command: (1) The maximum number of DRBs supported by the UE and the number of allocated DRBs Or (2) only if it is impossible to establish one of the other DRB indications (ie, whether the number of allocated DRBs is equal to the maximum number of DRBs supported by the UE).

In principle, the second option may be sufficient because a UE may have a PDN connection to multiple P-GWs or SCEFs (or both) and is not intended to inform the P-GW 1 when the UE is headed towards, for example, the P-GW. 2 One of the PDN connections is related to one of the EPS carriers stopping the action. This means that the indication may be valid for a particular bearer resource allocation and should not be stored by P-GW 1 for later use.

FIG. 3 shows a dedicated carrier launcher 300. In the illustrated embodiment, the PCRF passes an IP-CAN session modification 320 to the PDN-GW 310. Next, the PDN-GW sends a Create Bearer Request 322 to the Serving GW 308. Servo GW 308 sends a Create Bearer Request 324 to MME 306. The MME 306 sends a bearer setup request/work phase management request 326 to the eNodeB 304. The eNodeB 304 sends an RRC Connection Reassembly 328 to the UE 302. The UE 302 sends an RRC Connection Reassembly Complete message 330 to the eNodeB 304. The eNodeB 304 sends a bearer setup response 322 to the MME 306. UE 302 sends a direct transfer 334 to eNodeB 304. The eNodeB 304 sends a Work Phase Management Response 336 to the MME 306. The MME 306 sends a Create Bearer Response 338 to the Serving GW 308. Servo GW 308 sends a Create Bearer Response 340 to PDN GW 310. The PDN GW 310 sends an IP-CAN session modification 342 to the PCRF 312.

For example, if the PCRF 312 of the P-GW initiates the initiation of a dedicated EPS bearer, the MME 306 may check the assigned after operation 3 (ie, upon receiving a request to create a bearer from the S-GW). Whether the number of DRBs is equal to the maximum number of DRBs supported by the UE. If so, the MME 306 can immediately reject the request, thereby avoiding the unnecessary signaling shown in operations 4 through 9 (324 through 336) in FIG. It may also be dependent on the reason for the rejection received in the creation of the bearer response message (ie "maximum number of EPS bearers"), the PCRF 312 or P-GW terminates the bearer activation, and instead initiates one of the existing EPS bearers. modify.

As an alternative solution, the MME 306 may perform the signaling procedure as shown in FIG. 3 instead of rejecting the request from the S-GW 308 after operation 3. Then, after receiving the RRC connection re-assembly message in operation 5, the UE decides whether to reject the request (not shown); or whether to temporarily accept the request (operation 6), and then by a UE The requested bearer resource modification uses a DRB to stop one of the existing EPS bearers (see Figure 2). The STOP action EPS bearer may belong to another PDN connection that is no longer needed, or has a lower priority than the PDN connection that creates the new EPS bearer.

The "Maximum Carrier Support" support can also be used as a UE configuration. In some scenarios, even if the device itself is capable of establishing multiple bearers (for example, to reduce the number of applications on the device that require DRB, or to reduce the ability of the UE to cause network congestion), the operator may still want Limit the maximum number of data radio bearers that a UE can establish. In such a scenario, the operator can group the device into a "maximum carrier support" value, for example using SIM-OTA or OMA-DM.

FIG. 4 shows a UE-Capability-NB information element 400. The MultipleDRB-r13 field is part of a UE-Capability NB-r13 information element 400. This field defines whether the UE supports multiple DRBs. In some embodiments, this field is suitable for the case where the UE supports user plane CIoT EPS optimization with a UE-Category-NB. In this embodiment, if one UE of this version supports multiple DRBs, the UE supports at least two simultaneous DRBs. In an alternate embodiment, the MultipleDRB-r13 field is encoded as an integer value that defines the maximum number of DRBs that the UE can support.

Figure 5 shows an example of a meta-list 500 for a UE network capability information element. In some embodiments, one of the UE network capability information elements is used to provide the network with information relating to the aspects of the EPS-related or GPRS-connected UE. Content may affect the way the network operates the UE. The UE network capability information indicates general UE characteristics, and therefore, except for the explicitly indicated field, it should be independent of the frequency band of the channel through which it is transmitted.

The UE network capability information element can be coded as shown in FIG. The UE network capability is a type 4 information element having a minimum length of 4 octets and a maximum length of 15 octets.

In the present embodiment, multiple DRB support (multiple DRB with octet 9 and bit 1) indicates the ability to support multiple user plane radio bearers in NB-S1 mode. A bit set to 0 indicates that multiple DRBs are not supported. A bit set to 1 indicates that multiple DRBs are supported. If the information element includes a respective octet, the other bits of octet 10 to 15 are reserved and can be written to zero. In an alternate embodiment, the multipleDRB field is encoded as an integer value of two or more bits defining the maximum number of DRBs that the UE can support.

Figure 6 shows a method for indicating support for more than one data radio bearer for an NB-IoT cellular device. This can be done by a system including a UE, a baseband circuitry, and an RF circuitry, etc., as shown in Figures 1, 7, 8 or 9. In block 602, a narrowband Internet of Things (NB-IoT) cellular device decision includes a set of radio access capability parameters indicating support for more than one data radio bearer to transmit signaling to a network. In block 604, the NB-IoT cellular device generates a message to the network that includes the value of supporting more than one data radio bearer along with the indication of the set of radio access capability parameters. Program block 602 can be implemented as part of an add-on or trace update procedure, or as part of providing an information element in other manners.

In some embodiments, it can operate in reverse. For example, the UE is configured by the operator to form a new value (as described above), and the UE determines that the support indicator has changed value, and therefore, the new value needs to be transmitted to the network. To this end, it initiates a Tracking Area Update (TAU) program.

In other embodiments, an attachment procedure is initiated. If the UE supports user plane CIoT EPS optimization and multiple user plane radio bearers in the NB-S1 mode, the UE shall set the multiple DRB support bits in the UE network capability IE of the ATTACH REQUEST message to " Multiple DRB support."

In some embodiments, a normal and periodic tracking area update procedure can be initiated. If the UE supports user plane CIoT EPS optimization and multiple user plane radio bearers in the NB-S1 mode, the UE shall set the multiple DRB support bits in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. Become "multiple DRB support".

In some embodiments, the following UE radio access capability parameters are applicable in NB-IoT: may include UE radio access capability parameters. The following sections have Multimedia Broadcast Multicast Service (MBMS) capable UEs that define UE radio access capability parameters and minimum capabilities. Only the parameters that the UE may transmit different values are considered as UE radio access capability parameters. Therefore, mandatory features that do not have the same capability parameters for all UEs are not listed here. The ability for the UE to perform optional or conditionally mandatory but without UE radio access capability parameters is also listed in this specification.

In some embodiments, the E-UTRAN needs to comply with the UE radio access capability parameters for transmitting signaling when assembling the UE and scheduling the UE. Regarding mobility, NB-IoT is a different RAT than E-UTRAN.

In an embodiment, and for optional features, the UE radio access capability parameter indicates whether a feature has been implemented and successfully tested. For mandatory features with UE radio access capability parameters, the parameter indicates whether the feature has been successfully tested.

The IE UE-Capability-NB can be used to transmit NB-IoT UE radio access capability parameters. IE UE-Capability-NB is transferred in NB-IoT. The UE-Capability-NB information element may include: multipleDRB-r13 belonging to ENUMERATED {supported} and OPTIONAL.

Radio resource control may be specified for the radio interface between the UE and the E-UTRAN, and for the radio interface between the RN and the E-UTRAN.

A category of the description may include: radio related information transmitted in a transparent container between the source eNB and the target eNB according to inter-eNB handover; and a handover between the source or target eNB and another system according to RAT handover Transmitting radio related information delivered in the container.

The control plane CIoT EPS optimization may have the ability to efficiently transfer user data (IP, non-IP or SMS) via the control plane via the MME, but without triggering the establishment of the data radio bearer.

The RRC protocol may include the following main functions: establishing/modifying/releasing RBs carrying user data (DRB); and NB-IoT RRC multiplicity and type restriction condition values.

The multiplicity and type restriction condition definition may include a field called maxDRB-NB-r13 in an information element, which is an INTEGER ::= 2, and defines a maximum number of DRBs for NB-IoT.

A UECapabilityInformation-NB message is used to transfer the UE radio access capability requested by the E-UTRAN. This transfer may include a signaling radio bearer: SRB1 or SRB1bis, an RLC-SAP: AM, a logical channel: DCCH and/or direction: UE to E UTRAN.

In an embodiment, the IE UE-Capability-NB is used to transmit the NB-IoT UE radio access capability parameter. The IE UE-Capability-NB is only transferred in the NB-IoT. It may include defining whether the UE supports one of the multiple DRB fields of the multiple DRBs.

Figure 7 is consistent with the embodiment disclosed herein, and is a data flow diagram showing a UE and a servo gateway/packet data network (PDN) gateway in a dual connectivity configuration (S/ Data flow between P-GW). Although this example uses two radio links, one towards the master eNB (MeNB) and one towards the 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 the packets 722, 724 to a first wireless interface for transmission to the MeNB 710 based on a particular application attribute or bearer. A second TFT, including one or more packet filters 736, routes the packet 726 to a second wireless interface for transmission to the SeNB 711. In some embodiments, one of the TFTs may be omitted and any packets that do not conform to the filtering criteria of any one of the other TFT's packet filters may be routed to a TFT (preset wireless interface). Wireless interface that is not associated. MeNB 710 and SeNB 711 transmit packets 722, 724, and 726 to S/P-GW 712. S/P-GW 712 transmits traffic streams 762, 764, and 766 to services 714 including Application 1 (716), Application 2 (718), and Application 3 (720).

For example, because the packet filter 736 resides on the PDCP layers 728 and 738, the traffic stream can be aggregated by a TFT (including a first TFT filtered with packets conforming to the packets 722 and 724, and a packet including the matching packet 726). A second TFT is filtered to form. Packets 722 and 724 flow through PDCP layer 728 (which becomes associated with a radio bearer), flow through RLC layer 730 (becomes associated with a logical channel (DTCH)), and flow through MAC layer 732 (becomes one The transport channel (ULSCH) is associated, and flows through the PHY layer 734 (which becomes associated with a physical channel (PUSCH)) and is transmitted to the MeNB 710. The packet 726 flows through a second protocol stack that flows through the PDCP layer 738 (which becomes associated with a radio bearer), flows through the RLC layer 740 (becomes associated with a logical channel (DTCH)), and flows through the MAC. Layer 742 (which becomes associated with a transport channel (ULSCH)) and flows through PHY layer 744 (which becomes associated with a physical channel (PUSCH)) is transmitted to SeNB 711.

Packets 722, 724, and 726 are received by MeNB 710 and SeNB 711 and sent to S/P-GW 712, which may include services including Application 1 (716), Application 2 (718), and Application 3 (720). 714 provides the packets. A transmission from the UE 708 to the SeNB 711 based on the packet 726 is routed through the PHY layer 754 to the MAC layer 756, to the RLC layer 758, to the PDCP layer 760, and then routed through an EPS bearer to the S/P-GW. 712, which routes the packet 726 to the application 720 (becomes the traffic stream 762). Through the PHY layer 746, one of the packets from the UE 708 to the MeNB 710 based on the packets 722 and 724 is routed to the MAC layer 748, to the RLC layer 750, to the PDCP layer 752, and then routed through an EPS bearer to the S/P. - GW 712, which routes packets 722 and 724 to applications 716 and 718 (becomes traffic flows 766 and 764).

For example, the UE is running on a GPS voice guidance application. The current location information is reported by Application 1 (702 on UE 708 and 716 on Service 714). Voice guidance is 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). Location information (packet 724) and voice guidance (packet 724) may be sensitive to timing and reliability (because routing arrangements may need to be recalculated). However, a background map cache (packet 726) can be quickly loaded and stored for later use, allowing for a high current data rate, but the connection is less reliable when a small update is required. MeNB 746 may determine that application 3 (706 on UE 708 and 720 on service 714) may utilize SeNB 711 and can use SeNB 711 (such as a request to connect and/or accept a connection from UE 708). The MeNB 710 can then assemble the radio bearers (738 on the UE 708 and 760 on the network side) to include the packet filtering 736 (on both the UE 708 and the EPC, such as the S/P-GW 712). The two TFTs are used together to filter the packets based on application-based criteria (such as IP address, origin application, etc.). Location information (packet 724) and voice guidance (packet 722) are routed to MeNB 710 by packet filtering 736 through a more robust (but potentially slower) link. The background mapping cache (packet 726) is routed from the SeNB 711 to the UE 708 by packet filtering in the S/P-GW 712 over a less robust (but potentially faster) link.

In one embodiment, the sequence of events is: 1) The UE requests additional bearer resources (see, eg, Figure 2). 2) The network then initiates a dedicated EPS bearer (associated with the TFT). At this point, the first EPS bearer (preset bearer) and the new and dedicated bearer are both between the UE and the (M)eNB. The UE maps the uplink packet to one of the two EPS bearers using the TFT(s) and maps it to one of the two DRBs, and the P-GW uses the TFT(s) to packet the downlink packet Map to one of the 2 EPS bearers. 3) (M) The eNB decides to switch to a dual connectivity configuration. At this point, the first EPS bearer (preset bearer) is between the UE and the MeNB, and the dedicated bearer is between the UE and the SeNB. The UE still uses the TFT(s) to map the uplink packet to one of the two EPS bearers, while the P-GW still uses the TFT(s) to map the downlink packet to one of the two EPS bearers. .

In some embodiments, WLAN technology may be used instead of a SeNB.

8 is a block diagram illustrating a radio access node (RAN) node circuitry (such as an eNB circuitry), a UE circuitry, a network node circuitry, or some other, in accordance with various embodiments. Circuitry type electronic device circuitry 800. In an embodiment, the electronic device circuitry 800 may be, or may be incorporated in or otherwise part of, a RAN node (eg, an eNB), a UE, a mobile station (MS), a BTS, a network node Or some other type of electronic device. In an embodiment, electronic device circuitry 800 may include radio transmission circuitry 810 and receiving circuitry 812 coupled to control circuitry 814 (eg, a baseband processor(s), etc.). In an embodiment, transmission circuitry 810 and/or receiving circuitry 812 may be an element or module of a transceiver circuitry, as shown. In some embodiments, control circuitry 815 may be located in some or all of the devices separate from or external to transmission circuitry 810 and receiving circuitry 812 (eg, such as a cloud radio access network (C- RAN) In the implementation, a baseband processor shared by multiple antenna devices).

Electronic device circuitry 810 can be coupled to one or more antenna elements 816 of one or more antennas. Electronic device circuitry 800 and/or components thereof can be configured to perform operations similar to those described elsewhere in this disclosure.

In an embodiment where the electronic device circuitry 800 is, or is incorporated in, or otherwise belongs to a portion of the UE, the electronic device circuitry 810 can transmit an information component and/or a carrier resource modification request, as illustrated 2 is shown. The receiving circuitry 812 can receive an RRC connection reassembly message, as shown in FIG.

In an embodiment where the electronic device circuitry 800 is an eNB, a BTS, and/or a network node, or is incorporated, or otherwise part of one of the eNBs, BTSs, and/or a network node, the transmission circuitry System 810 can transmit an RRC connection reassembly message, as shown in FIG. The receiving circuitry 812 can receive an RRC connection reassembly complete message or a direct transfer message, as shown in FIG. In an embodiment, a bearer setup request is received from the MME via a fixed line and not via a radio interface.

In some embodiments, the electronic device circuitry 800 of FIG. 8 is operable to perform one or more methods, such as the method illustrated in FIG.

The term "circuitry" as used herein may mean, be part of, or include an application-specific integrated circuit (ASIC), an electronic circuit, a processor (shared, exclusive, or group), And/or memory (shared, exclusive, or group) that performs one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry can be implemented in one or more software or firmware modules, or the functionality associated with the circuitry can be implemented by one or more software or firmware modules. In some embodiments, the circuitry can include logic that is at least partially operable in hardware.

The embodiments described herein can be implemented in a system using any suitably assembled hardware and/or software. 9 is a block diagram showing an exemplary component of a User Equipment (UE) or Mobile Station (MS) device 900, in one embodiment. In some embodiments, UE device 900 can include application circuitry 902, baseband circuitry 904, radio frequency (RF) circuitry 906, front end module (FEM) circuitry 908 coupled together at least as shown in FIG. And one or more antennas 910.

Application circuitry 902 can include one or more application processors. By way of non-limiting example, application circuitry 902 can include one or more single core or multi-core processors. This (etc.) processor can include any combination of general purpose processors and proprietary processors (graphics processors, application processors, etc.). The processor can be operatively coupled and/or include a memory/storage and can be configured to execute instructions stored in the memory/storage to allow for various applications and/or jobs. The system is running on this system.

By way of non-limiting example, baseband circuitry 904 can include one or more single core or multi-core processors. The baseband circuitry 904 can include one or more baseband processors and/or control logic. The baseband circuitry 904 can be configured to process the baseband signals received from the receive signal path of one of the RF circuitry 906. The baseband circuitry 904 can also be configured to generate a baseband signal for the transmit signal path of the RF circuitry 906. The baseband processing circuitry 904 can interface with the application circuitry 902 for generating and processing such baseband signals and for controlling the operation of the RF circuitry 906.

By way of non-limiting example, baseband circuitry 904 can include at least one of: a second generation (2G) baseband processor 904A, a third generation (3G) baseband processor 904B, a fourth generation (4G) baseband processor 904C, other existing generations, and other baseband processor(s) 904D(s) in development or future generations (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 904 (e.g., one or more of the baseband processors 904A through 904D) can handle various radio control functions that allow communication with one or more radio networks via the RF circuitry 906. By way of non-limiting example, such radio control functions may include signal modulation/demodulation, encoding/decoding, radio frequency offset, other functions, and combinations thereof. In some embodiments, the modulation/demodulation circuitry of the baseband circuitry 904 can be programmed to perform Fourier transform (FFT), precoding, and constellation mapping/demapping functions, other functions, and more. The combination. In some embodiments, the encoding/decoding circuitry of the baseband circuitry 904 can be programmed to perform convolution, tail code cancellation convolution, turbo, Viterbi, low density parity check (LDPC) encoder/decoder functions. , other features, and combinations of the above. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples and may include other suitable functions.

In some embodiments, the baseband circuitry 904 can include an element of a protocol stack. By way of non-limiting example, an element of an evolved universal terrestrial radio access network (EUTRAN) protocol includes, by way of example, a physical (PHY), medium access control (MAC), radio link control (RLC), Packet Data Convergence Protocol (PDCP), and/or Radio Resource Control (RRC) elements. The central processing unit (CPU) 904E of the baseband circuitry 904 can be programmed to run the elements of this protocol stack for PHY, MAC, RLC, PDCP, and/or RRC signaling. In some embodiments, baseband circuitry 904 can include one or more audio digital signal processors (DSPs) 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 can further include a memory/storage 904G. Memory/storage 904G may include data and/or instructions stored thereon for operation by a processor of baseband circuitry 904. In some embodiments, the memory/storage 904G can include any combination of suitable electrical and/or non-electrical memory. The memory/storage 904G may also include any combination of various memory/storage levels including, but not limited to, read only memory (ROM) with embedded software instructions (eg, firmware), random access memory. Body (such as dynamic random access memory (DRAM)), cache memory, buffers, and so on. In some embodiments, memory/storage 904G may be shared between or among various processors or specific to a particular processor.

In some embodiments, the components of the baseband circuitry 904 can be suitably combined in a single wafer, in a single wafer set, or on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuitry 904 and the application circuitry 902 can be implemented together, such as, for example, on a system (SOC) on a wafer.

In some embodiments, baseband circuitry 904 can be used to communicate with one or more radio technologies. For example, in some embodiments, the baseband circuitry 904 can support an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area network (WMAN), a wireless local area network ( WLAN), a wireless personal area network (WPAN) communication. Embodiments in which baseband circuitry 904 is configured to support radio communications over more than one wireless protocol may be referred to as multimode baseband circuitry.

The RF circuitry 906 can allow communication with the wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuitry 906 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. RF circuitry 906 can include a receive signal path that can include circuitry for downconverting RF signals received from FEM circuitry 908 and providing baseband signals to baseband circuitry 904. The RF circuitry 906 can also include a transmit signal path that can include circuitry for upconverting the baseband signal provided by the baseband circuitry 904 and providing an RF output signal to the FEM circuitry 908 for transmission.

In some embodiments, RF circuitry 906 can include a receive signal path and a transmit signal path. The receive signal path of RF circuitry 906 can include mixer circuitry 906A, amplifier circuitry 906B, and filter circuitry 906C. The transmit signal path of RF circuitry 906 can include filter circuitry 906C and mixer circuitry 906A. The RF circuitry 906 can further include a synthesizer circuitry 906D that is configured to combine a frequency for the receive signal path and the mixer circuitry 906A of the transmit signal path. In some embodiments, the mixer circuit circuitry 906A of the receive signal path can be configured to downconvert the RF signal received from the FEM circuitry 908 based on the synthesized frequency provided by the synthesizer circuitry 906D. Amplifier circuitry 906B can be configured to amplify the downconverted signal.

Filter circuitry 906C can include a low pass filter (LPF) or a band pass filter (BPF) that is configured to remove unwanted signals from the downconverted signals to produce an output baseband signal. . The baseband circuitry 904 can be provided with an output baseband signal for further processing. In some embodiments, the output baseband signals may include a zero frequency baseband signal, but this is not a requirement. In some embodiments, the mixer circuit system 906A that receives the signal path can include a passive mixer, although the scope of such embodiments is not limited in this respect.

In some embodiments, the transmit signal path mixer circuit 906A can be configured to upconvert the input baseband signal to generate the FEM circuitry 908 based on the synthesized frequency provided by the synthesizer circuitry 906D. The RF output signal used. These baseband signals may be provided by baseband circuitry 904 and may be filtered by filter circuitry 906C. Filter circuitry 906C may include a low pass filter (LPF), although the scope of such embodiments is not limited in this respect. In some embodiments, the mixer circuit 906A of the receive signal path and the mixer circuit 906A of the transmit signal path may include two or more mixers and may be arranged for orthogonality, respectively. Down conversion and / or up conversion. In some embodiments, the mixer circuit circuitry 906A that receives the signal path and the mixer circuitry 906A of the transmission signal path can include two or more mixers and can be arranged for image rejection ( For example, Hartley image exclusion). In some embodiments, the mixer circuit circuitry 906A and the mixer circuitry 906A of the receive signal path can be arranged for direct down conversion and/or direct conversion, respectively. In some embodiments, the mixer circuit 906A of the receive signal path and the mixer circuit 906A of the transmit signal path can be configured for superheterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of such embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In such an embodiment, RF circuitry 906 can include an analog digital converter (ADC) and digital analog converter (DAC) circuitry, and baseband circuitry 904 can include a communication with RF circuitry 906. The digital baseband interface.

In some dual mode embodiments, separate radio ICs for processing signals may be provided for each spectrum, although the scope of such embodiments is not limited in this respect.

In some embodiments, synthesizer circuitry 906D may include one or more of a fractional-N synthesizer and a fractional N/N+1 synthesizer, although the scope of such embodiments is not limited in this respect because There are other suitable types of frequency synthesizers. For example, synthesizer circuitry 906D can include a delta-sigma synthesizer, a frequency multiplier, a synthesizer including a phase-locked loop with one of the dividers, other synthesizers, and combinations thereof.

Synthesizer circuitry 906D can be configured to synthesize an output frequency for use by mixer circuitry 906A of RF circuitry 906 based on a frequency input and a divider control input. In some embodiments, synthesizer circuitry 906D can be a fractional N/N+1 synthesizer.

In some embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO), but this is not a requirement. The divider control input can be provided by the baseband circuitry 904 or the application processor 902, depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) can be determined via a lookup table based on a channel indicated by application processor 902.

The synthesizer circuitry 906D of the RF circuitry 906 can include a divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider can include a dual modulus divider (DMD), and the phase accumulator can include a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by N or N+1 (eg, based on a carry output) to provide a fractional allocation ratio. In some exemplary embodiments, the DLL may include a set of cascades, adjustable, delay elements, a phase detector, a charge pump, and a D-type flip-flop. In such embodiments, the delay elements can be configured to divide a VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL can provide negative feedback and help ensure that the total delay through this delay line is one VCO period.

In some embodiments, synthesizer circuitry 906D can be configured to generate a carrier frequency as the output frequency. In some embodiments, the output frequency can be a multiple of the carrier frequency (eg, twice the carrier frequency, four times the carrier frequency, etc.) and can be used with an orthogonal generator and divider circuitry for The carrier frequency produces a plurality of signals having a plurality of phases different from each other. In some embodiments, this output frequency can be an LO frequency (fLO). In some embodiments, RF circuitry 906 can include an IQ/polarity converter.

FEM circuitry 908 can include a receive signal path that can include being configured to operate on RF signals received from one or more antennas 910, amplify such received signals, and to RF circuitry 906 provides circuitry that such amplified versions have received signals for further processing. FEM circuitry 908 may also include a transmission signal path that may include circuitry that is configured to amplify the transmission signals provided by RF circuitry 906 for transmission by at least one of one or more antennas 910.

In some embodiments, FEM circuitry 908 can include a TX/RX switch that is configured to switch between a transmission mode and a receive mode operation. FEM circuitry 908 can include a receive signal path and a transmit signal path. The receive signal path of FEM circuitry 908 can include a low noise amplifier (LNA) for amplifying the received RF signal and providing the amplified received RF signal as an output (e.g., to RF circuitry 906). The transmit signal path of FEM circuitry 908 can include a power amplifier (PA) that is configured to amplify an input RF signal (such as provided by RF circuitry 906), and one or more components that are configured to generate an RF signal. A filter for subsequent transmission (e.g., by one or more of one or more antennas 910).

In some embodiments, the MS device 900 can include additional components such as, for example, a memory/storage, a display, a camera, one of the more sensors, and an input/output (I/O) interface. , other components, and combinations of the above.

In some embodiments, MS device 900 can be configured to perform one or more processes, techniques, and/or methods, or portions thereof, as described herein.

The term "circuitry" as used herein may mean, be part of, or include an application-specific integrated circuit (ASIC), an electronic circuit, a processor (shared, exclusive, or group), And/or memory (shared, exclusive, or group) that performs one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry can be implemented in one or more software or firmware modules, or the functionality associated with the circuitry can be implemented by one or more software or firmware modules. In some embodiments, the circuitry can include logic that is at least partially operable in hardware. Instance

The following examples relate to further embodiments.

Example 1 is an equipment belonging to a narrowband user equipment (UE). The apparatus includes a memory designed to store a set of radio access capability parameters for the narrowband UE, the set of radio access capability parameters including an indicator supporting one of the data radio bearers. 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 to encode the network including a set of radio access capability parameters A message that supports this indicator for more than one data radio bearer.

Example 2 is the apparatus of example 1, wherein determining the set of radio access capability parameters to transmit signaling to a network further comprises: initiating an attach procedure that exposes the set of radio access capability parameters.

Example 3 is the apparatus of example 1, wherein determining the set of radio access capability parameters to transmit signaling to a network further comprises: initiating a tracking area update procedure.

Example 4 is the apparatus of Example 1, wherein the message is a radio resource control message.

Example 5 is the apparatus of Example 4, wherein the indicator is part of a UECapabilityInformation-NB information element.

Example 6 is the apparatus of Example 1, wherein the UE is designed to communicate with the network using a narrowband Internet of Things (NB-IoT) radio access technology.

Example 7 is the apparatus of Example 1, wherein the UE is designed to communicate with the network including an evolved UMTS Terrestrial Radio Access Network (E-UTRAN).

Example 8 is the apparatus of example 1, wherein the network comprises at least one of an enhanced Node B (eNB) or a Mobility Management Entity (MME).

Example 9 is the apparatus of Example 1, wherein the message is an Evolutionary Partitioning System (EPS) Mobility Management (MM) message.

Example 10 is the apparatus of Example 9, wherein the indicator is part of a UE network capability information element.

Example 11 is an apparatus belonging to an evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) entity. The apparatus includes a memory designed to store various sets of radio access capability parameters for one or more cellular Internet of Things (CIoT) User Equipments (UEs), including one that supports more than one data radio bearer A set of radio access capability parameters for the indicator. The apparatus includes one or more processing units designed to process various sets of radio access capability parameters from a set of CIoT UEs including metrics supporting more than one data radio bearer, and processing from the set of CIoT UEs A first CIoT UE establishes a first request for an additional evolved packet system (EPS) bearer. The apparatus also includes one or more processing units designed to respond to the first request, based at least in part on supporting a first indicator of one of the data radio bearers to determine that the first CIoT UE supports more than one data radio bearer And designing the additional radio bearer for use with the first CIoT UE based at least in part on indicating the first indicator of support for more than one data radio bearer for more than one data radio bearer.

Example 12 is the apparatus of example 11, wherein the one or more processing units are further designed to process a second request to establish an additional EPS bearer from a second CIoT UE of the set of CIoT UEs. The processing units are further designed to be responsive to the second request for processing; determining that the second CIoT UE supports a data radio bearer, and at least in part based at least in part on supporting a second indicator of one of the data radio bearers Providing an additional packet for the CIoT UE to reuse an existing radio bearer without using a data radio bearer based on the indication that the lack of support for support of more than one data radio bearer exceeds the second indicator of a data radio bearer The data network (PDN) connects or rejects the second request.

Example 13 is the apparatus of example 12, wherein reusing an existing radio bearer further includes using the existing radio bearer.

Example 14 is the apparatus of example 12, wherein reusing an existing radio bearer further includes releasing the existing radio bearer and creating a new radio bearer.

Example 15 is the apparatus of example 11, wherein the E-UTRAN entity is an enhanced Node B (eNB).

Example 16 is the apparatus of example 11, wherein the E-UTRAN entity is a Mobility Management Entity (MME).

Example 17 is the apparatus of example 11, wherein processing the set of radio access capability parameters from a CIoT UE including the first indicator supporting more than one data radio bearer further comprises: processing the exposure from an attach procedure A message of the group radio access capability parameters.

Example 18 is the apparatus of example 11, wherein processing the set of radio access capability parameters from a CIoT UE including the first indicator supporting more than one data radio bearer further comprises: processing one from a tracking area update procedure message.

Example 19 is the apparatus of example 11, wherein processing the set of radio access capability parameters from a CIoT UE including the first indicator supporting more than one data radio bearer further comprises: processing including supporting more than one data radio bearer An EPS mobility management (MM) message of the first indicator.

Example 20 is the apparatus of example 19, wherein the indicator is part of a UE network capability information element.

Example 21 is the apparatus of Example 11, wherein the E-UTRAN communication with the first CIoT UE uses a narrowband Internet of Things (NB-IoT) radio access technology.

Example 22 is the apparatus of example 11, wherein processing the set of radio access capability parameters from a CIoT UE including the first indicator supporting more than one data radio bearer further comprises: processing including supporting more than one data radio bearer A radio resource control message of the first indicator.

Example 23 is the apparatus of Example 22, wherein the indicator is part of a UECapabilityInformation-NB information element.

Example 24 is a computer program product. The computer program product includes a computer readable storage medium storing instructions for execution by one or more processors to perform operations of a narrowband Internet of Things (NB-IoT) cellular device, the operations being subject to the one or Executing, by the plurality of processors, determining that a set of radio access capability parameters including a value indicating that more than one data radio bearer is supported to transmit signaling to a network, and generating the inclusion along the network The indication of the set of radio access capability parameters supports a message that exceeds the value of a data radio bearer.

Example 25 is the computer program product of example 24, wherein determining the set of radio access capability parameters to transmit signaling to a network further comprises: initiating an attach procedure for revealing the set of radio access capability parameters.

Example 26 is the computer program product of example 24, wherein determining the set of radio access capability parameters to transmit signaling to a network further comprises: initiating a tracking area update procedure.

Example 27 is the computer program product of example 24, wherein generating the message further comprises: generating an evolved system (EPS) mobility management (MM) message with the indicator.

The example 28 is the computer program product of the example 27, wherein the generating the message further comprises: including the indicator as part of a UE network capability information component.

Example 29 is the computer program product of example 24, wherein the instructions, when executed by the one or more processors, are further designed to transmit the message using a narrowband Internet of Things (NB-IoT) radio access technology. .

Example 30 is the computer program product of example 24, wherein generating the message further comprises: generating the message as a radio resource control message.

Example 31 is the computer program product of example 30, wherein generating the message as the radio resource control message further comprises: including the value as part of a UECapabilityInformation-NB information element.

Example 32 is the computer program product of example 24, wherein the value indicates the maximum number of data radio bearers supported by the NB-IoT cellular device.

Embodiments and implementations of the systems and methods described herein can include various operations that can be embodied as machine-executable instructions to be executed by a computer system. A computer system can include one or more general purpose or special purpose computers (or other electronic devices). The computer system can include hardware components that contain specific logic for performing such operations, or can include a combination of hardware, software, and/or firmware.

The computer system and the computer in a computer system can be connected via a network. A network suitable for assembly and/or use as described herein includes one or more regional networks, wide area networks, metropolitan area networks, and/or internet or IP networks, such as the World Wide Web, Private internet, a secure internet, a value-added network, a virtual private network, an external network, an internal network, or even a separate machine that communicates with other machines through the physical entity of the media . In particular, a suitable network may be formed in part or in whole by two or more other networks, including networks using different hardware and network communication technologies.

Other suitable networks include a server and one or more clients; other suitable networks may contain other combinations of servers, clients, and/or nodes in the same class, and a given computer system can simultaneously function as A client and role acts as a server. Each network includes at least two computers or computer systems, such as servers and/or clients. A computer system can include a workstation, a laptop, a mobile computer that can be disconnected, a server, a large computer, a cluster, a so-called "network computer" or "thin client", a tablet, a smart phone, Personal digital assistant or other handheld computing device, "smart" consumer electronic device or appliance, medical device, or a combination of the above.

Suitable networks may include communication or network connectivity software, such as software available from NovellR, MicrosoftR, and other vendors, and may be through twisted pair, coaxial, or fiber optic cable, telephone line, radio wave, satellite, microwave. Relays, modulated AC power lines, physical media transfers, and/or other data transmission "wires" known to those of ordinary skill in the art are operated using TCP/IP, SPX, IPX, and other protocols. The network can include smaller networks and/or can be connected to other networks via a gateway or smaller mechanism.

Various techniques, or some aspects or portions thereof, may take the form of, for example, a flexible magnetic disk, a CD-ROM, a hard disk drive, a magnetic or optical card, a solid state memory device, a non-transitory computer readable storage medium, or A code (ie, an instruction) embodied in a tangible medium such as any other machine-readable storage medium that becomes a technique for practicing such a technique when a machine such as a computer loads and executes the code. equipment. If the program code is executed on a planable computer, the computing device may include a processor, a storage medium (including electrically and non-electrical memory and/or storage elements) readable by the processor, At least one input device and at least one output device. The electrical and non-electrical memory and/or storage component can be a RAM, an EPROM, a flash drive, an optical drive, a magnetic hard drive, or other medium for storing electronic data. . The eNBs (or other base stations) and UEs (or other mobile stations) may also include a transceiver component, a counter component, a processing component, and/or a clock component or timer component. One or more of the various techniques described herein may implement or utilize an application programming interface (API), reusable controls, and the like. Such programs can be implemented as a high-level procedural or object-oriented programming language for communicating with a computer system. However, this (etc.) program can be implemented as a combination or machine language as desired. In either case, the language can be a compiled or interpreted language and combined with a hardware implementation.

Each computer system includes one or more processors and/or memory; the computer system can also include various input devices and/or output devices. The processor can include a general purpose device such as an IntelR, AMDR, or other "off the shelf" microprocessor. The processor may include a special purpose processing device such as an ASIC, SoC, SiP, FPGA, PAL, PLA, FPLA, PLD, or other custom or planable device. The memory may include static RAM, dynamic RAM, flash memory, one or more flip-flops, ROM, CD-ROM, DVD, disc, magnetic tape, or magnetic, optical, or other computer storage media. The input device may include a keyboard, a mouse, a touch screen, a light pen, a tablet, a microphone, a sensor, or other hardware that is accompanied by a firmware and/or a soft body. The output device may include a monitor or other display, printer, voice or text synthesizer, switch, signal line, or other hardware that is accompanied by firmware and/or software.

It should be understood that many of the functional units described in this specification can be implemented as one or more components, which is one of the terms used to more specifically emphasize the factual independence. For example, a component can be implemented to include a custom ultra-large integrated body (VLSI) circuit or gate array, or a hardware circuit such as an off-the-shelf semiconductor, transistor, or other discrete component such as a logic die. A component can also be implemented as a programmable hardware device such as a field programmable gate array, programmable array logic, programmable logic devices, or the like.

Components can also be implemented as software for execution by various types of processors. An identified executable code component, for example, can include one or more computer instruction entities or logic blocks, which can be organized, for example, as an object, a program, or a function. However, once the identified component's executable file does not need to be located in one place, it may contain different instructions stored in different locations that, when logically linked together, contain the component and achieve the stated purpose of the component.

An executable code component can indeed be a single instruction or many instructions, and can even be distributed over several different code segments, different programs, and several memory devices. Similarly, operational data may be identified and described herein within the components, and may be embodied in any suitable form and organized in any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed in different locations, including distributed to different storage devices, and may exist as an electronic signal at least partially on a system or network. These components can be passive or active, including agents that are operable to perform the desired function.

Several aspects of the described embodiments will be described as software modules or components. A software module or component, as used herein, can include any type of computer instruction or computer executable code located within a memory device. A software module, for example, may include one or more entities or logic blocks of computer instructions that may be organized to perform one or more tasks or implement one of a particular data type routine, program, object, component, Data structure, etc. It is understood that a software module can be implemented as a hardware and/or a firmware instead of or in software. One or more of the functional modules described herein can be divided into sub-modules and/or combined into a single or smaller number of modules.

In some embodiments, a particular software module can include different instructions stored in different locations of a memory device, a different memory device, or a different computer, which together implement the functions of the module. A module may indeed include a single instruction or many instructions, and may even be distributed over several different code segments, different programs, and several memory devices. Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device coupled through a communications network. In a distributed computing environment, the software module can be located in the local and/or remote memory storage device. In addition, the data tied or presented in a database record may reside in the same memory device, or reside in a plurality of memory devices, and may be recorded in a database spanning one network. The columns are linked together.

Reference to "an example" throughout this specification means that a particular feature, structure, or characteristic of one of the embodiments described herein is included in at least one embodiment of the invention. Therefore, the words "in an example" are not necessarily all referring to the same embodiment throughout the specification.

When multiple items, structured elements, component elements, and/or materials are used herein, they may be presented in a common list for convenience. However, these lists should be treated as if each member of the list was individually identified as a different and unique member. Therefore, this list should not have individual members who are considered to be physically equal to any other member of the same list because they exist in a common group and have no contralateral indication. Additionally, various embodiments and examples of the invention may be referred to herein as alternatives to various components thereof. It is understood that such embodiments, examples, and alternatives are not considered as actual equivalents of each other, but rather as distinct and autonomous representations of the present invention.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Many specific details are provided in the following description, such as materials, frequencies, dimensions, lengths, widths, shapes, and the like, to provide a thorough understanding of the embodiments of the invention. It will be appreciated, however, that the invention may be practiced without one or more of the specific details, or other methods, components, materials, etc.. In other instances, well known structures, materials, or operations are not shown or described in detail in order to avoid obscuring aspects of the invention.

It will be appreciated that the systems described herein are illustrative of specific embodiments. These embodiments can be combined into a single system, partially combined into other systems, segmented into multiple systems, or otherwise differentiated or combined. Additionally, it is contemplated that the parameters/attributes/states/etc. of an embodiment may be used in another embodiment. For the sake of clarity, the parameters/attributes/states/etc. are only described in one or more embodiments, and it is recognized that the parameters/attributes/stations/etc can be combined with parameters of another embodiment/ Attribute/etc. combination, or replace it unless there is a specific waiver in this article.

Although the foregoing has been described in some detail, it will be understood that It should be understood that there are many alternative ways of implementing the processes and equipment described herein. Therefore, the present embodiments are to be considered as illustrative and not restrictive, and the scope of the inventions

It will be apparent to those skilled in the art that many variations can be made in the details of the embodiments described above without departing from the basic principles of the invention. The scope of the invention should therefore be determined solely by the following claims.

100‧‧‧Communication system
102, 202, 302, 708‧‧‧ UE
103‧‧‧Multiple DRB support indicators
104‧‧‧RAN node
108‧‧‧cell coverage
112‧‧‧Access link
116‧‧‧EPC
118‧‧‧Return link
120, 122‧‧‧DRB
124, 126‧‧‧ EPS carrier
200‧‧‧ system
204, 304‧‧‧eNodeB
206, 306‧‧ MME
210‧‧‧S-GW
212, 310‧‧‧PDN-GW
214, 312‧‧‧ PCRF
216‧‧‧Request carrier resource modification message
217~218‧‧‧Carrier Resource Command
220, 224‧‧‧ PCEF initiated IP-CAN work phase modification
222‧‧‧
300‧‧‧Exclusive carrier launching procedure
308‧‧‧Server GW
320, 342‧‧‧IP-CAN work phase modification
322, 324‧‧ ‧ carrier request
326‧‧‧Carrier setup request/work phase management request
328‧‧‧RRC connection re-assembly
330‧‧‧RRC Connection Reassembly Complete Message
332‧‧‧Carrier setting response
334‧‧‧Direct transfer
336‧‧‧Working stage management response
338, 340‧‧‧ Create a carrier response
400‧‧‧UE-Capability-NB information component
500‧‧‧ bit list
602~604‧‧‧Program Block
702~706, 716~720‧‧‧Application
710‧‧‧MeNB
711‧‧‧SeNB
712‧‧‧S/P-GW
714‧‧‧Service
722~726‧‧‧Package
728, 738, 752, 760‧‧ ‧PDCP layer
730, 740, 750, 758‧‧ ‧ RLC layer
732, 742, 748, 756‧‧‧ MAC layer
734, 744, 746, 754‧‧‧ PHY layer
736‧‧‧Packet filtration
762~766‧‧‧ News flow
800‧‧‧Electronic device circuitry
810‧‧‧Radio transmission circuitry
812‧‧‧ receiving circuit system
814, 815‧‧‧Control circuit system
816‧‧‧Antenna components
900‧‧‧UE device
902‧‧‧Application Circuit System
904, 904F‧‧‧ fundamental frequency circuit system
904A~904D‧‧‧Base frequency processor
904E‧‧‧Central Processing Unit
904G‧‧‧Memory/storage
906‧‧‧RF (RF) circuitry
906A‧‧‧Mixer circuit system
906B‧‧‧Amplifier Circuit System
906C‧‧‧Filter Circuit System
906D‧‧‧Synthesizer Circuitry
908‧‧‧ Front End Module (FEM) circuitry
910‧‧‧Antenna

1 is consistent with the embodiments disclosed herein, and is a schematic diagram of a communication system for providing wireless communication services to a UE or other mobile wireless device.

FIG. 2 is consistent with the embodiment disclosed herein, and is a process diagram illustrating a UE requesting bearer resource modification.

Figure 3, consistent with the embodiments disclosed herein, is a process diagram of a dedicated carrier launch procedure.

4 is consistent with the embodiments disclosed herein to illustrate the code of a UE-Capability-NB information element.

5, consistent with the embodiments disclosed herein, is another table that depicts one instance of a one-bit list 500 for a UE network capability information element.

6 is a flow chart showing a method for indicating support for more than one data radio bearer for an NB-IoT cellular device.

Figure 7 is consistent with the embodiment disclosed herein, and is a data flow diagram showing a UE and a servo gateway/packet data network (PDN) gateway in a dual connectivity configuration (S/ Data flow between P-GW).

8 is consistent with the embodiments disclosed herein, and is a block diagram illustrating a radio access network (RAN) node circuitry (such as an eNB circuitry), a UE circuitry, and a network node circuitry. Electronic device circuitry of the system, or some other circuitry type.

9 is consistent with the embodiments disclosed herein, and is a block diagram illustrating an exemplary component of a User Equipment (UE) or Mobile Station (MS) device.

100‧‧‧Communication system

102‧‧‧UE

103‧‧‧Multiple DRB support indicators

104‧‧‧RAN node

108‧‧‧cell coverage

112‧‧‧Access link

116‧‧‧EPC

118‧‧‧Return link

120, 122‧‧‧DRB

124, 126‧‧‧ EPS carrier

Claims (28)

An apparatus for a narrowband user equipment (UE), comprising: a storage configured to store a set of radio access capability parameters for the narrowband UE, the set of radio access capability parameters including supporting more than one data radio bearer One of a plurality of baseband processors, which are configured to: determine that the set of radio access capability parameters are to transmit signaling to a network; and encode the network including one of the set of radios The capability parameter supports the message of the indicator exceeding one data radio bearer. The apparatus of claim 1, wherein determining that the set of radio access capability parameters are to be signaled to the network further comprises: initiating an attach procedure that reveals the set of radio access capability parameters. The equipment of claim 1, wherein determining the set of radio access capability parameters to transmit signaling to the network further comprises: initiating a tracking area update procedure. The equipment of claim 1, wherein the message is a radio resource control message. The equipment of claim 4, wherein the indicator is part of a UECapabilityInformation-NB information element. The apparatus of claim 1, wherein the UE is configured to communicate with the network using a narrowband Internet of Things (NB-IoT) radio access technology. The apparatus of claim 1 wherein the UE is configured to communicate with the network comprising an evolved UMTS terrestrial radio access network (E-UTRAN). The apparatus of claim 1, wherein the network comprises at least one of an enhanced Node B (eNB) or a Mobility Management Entity (MME). The equipment of claim 1, wherein the message is an evolved packet system (EPS) mobility management (MM) message. The equipment of claim 9, wherein the indicator is part of a UE network capability information element. An apparatus of an evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) entity, comprising: a storage unit configured to be stored for one or more cellular Internet of Things (CIoT) User equipment (UE) complex array radio access capability parameter, a set of radio access capability parameters including one indicator supporting more than one data radio bearer; one or more processing units, which are configured to: The CIoT UE includes the complex array radio access capability parameter supporting an indicator of more than one data radio bearer; processing a first request to establish an additional evolved packet system (EPS) from the first CIoT UE of the group of CIoT UEs Responding to the first request: determining, based at least in part on the first indicator supporting one of the data radio bearers, that the first CIoT UE supports more than one data radio bearer; and based at least in part on the indication support The support of the data radio bearer exceeds a first indicator of the data radio bearer, and the additional EPS bearer is assembled for the first Used with CIoT UE. The apparatus of claim 11, wherein the one or more processing units are further configured to: process a second request to establish a second additional EPS bearer from a second CIoT UE from the group of CIoT UEs; The second request: determining that the second CIoT UE supports a data radio bearer based at least in part on supporting a second indicator of one of the data radio bearers; and based at least in part on indicating lack of support for more than one data radio bearer Supporting more than one data radio bearer second indicator, reusing an existing radio bearer for the second CIoT UE, creating an additional packet data network (PDN) connection without using a data radio bearer, or rejecting the second request. The apparatus of claim 12, wherein reusing the existing radio bearer further comprises using the existing radio bearer. The apparatus of claim 12, wherein reusing the existing radio bearer further comprises releasing the existing radio bearer and creating a new radio bearer. The apparatus of claim 11, wherein the E-UTRAN entity is an enhanced Node B (eNB). The equipment of claim 11, wherein the E-UTRAN entity is a Mobility Management Entity (MME). The apparatus of claim 11, wherein processing the set of radio access capability parameters from the first CIoT UE including the indicator supporting more than one data radio bearer further comprises: processing the exposed radio set from an attach procedure Take a message of the capability parameter. The apparatus of claim 11, wherein processing the set of radio access capability parameters from the first CIoT UE including the indicator supporting more than one data radio bearer further comprises processing a message from a tracking area update procedure. The apparatus of claim 11, wherein processing the set of radio access capability parameters from the first CIoT UE including the first indicator supporting more than one data radio bearer further comprises: processing including supporting more than one data radio bearer An EPS mobility management (MM) message for this indicator. The apparatus of claim 19, wherein the first indicator is part of a UE network capability information element. The apparatus of claim 11, wherein the E-UTRAN communication with the first CIoT UE uses a narrowband Internet of Things (NB-IoT) radio access technology. The apparatus of claim 11, wherein processing the set of radio access capability parameters from the first CIoT UE including the indicator supporting more than one data radio bearer further comprises: processing including supporting the indicator of more than one data radio bearer a radio resource control message. The apparatus of claim 22, wherein the first indicator is part of a UECapabilityInformation-NB information element. A computer program product comprising a computer readable storage medium for execution by one or more processors for operation of a narrowband Internet of Things (NB-IoT) cellular device, such The operation, when executed by the one or more processors, is to: determine to include a set of radio access capability parameters indicating support for more than one data radio bearer to transmit signaling to a network; and to the network The path generates a message including support for the value of more than one data radio bearer along with the indication of the set of radio access capability parameters. The computer program product of claim 24, wherein the instructions, when executed by the one or more processors, are further configured to transmit using a narrowband Internet of Things (NB-IoT) radio access technology message. The computer program product of claim 24, wherein the generating the message further comprises: generating the message as a radio resource control message. The computer program product of claim 26, wherein the generating the message as the radio resource control message further comprises: including the value as part of a UECapabilityInformation-NB information element. The computer program product of claim 24, wherein the value indicates a maximum number of data radio bearers supported by the NB-IoT cellular device.