WO2018085713A2 - Sélection d'accès initial et de mode dans des réseaux d'évolution à long terme (lte) évolués - Google Patents

Sélection d'accès initial et de mode dans des réseaux d'évolution à long terme (lte) évolués Download PDF

Info

Publication number
WO2018085713A2
WO2018085713A2 PCT/US2017/060033 US2017060033W WO2018085713A2 WO 2018085713 A2 WO2018085713 A2 WO 2018085713A2 US 2017060033 W US2017060033 W US 2017060033W WO 2018085713 A2 WO2018085713 A2 WO 2018085713A2
Authority
WO
WIPO (PCT)
Prior art keywords
connection mode
lte
indication
elte
mode
Prior art date
Application number
PCT/US2017/060033
Other languages
English (en)
Other versions
WO2018085713A3 (fr
Inventor
Candy YIU
Alexandre Saso STOJANOVSKI
Sudeep Palat
Original Assignee
Intel IP Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2018085713A2 publication Critical patent/WO2018085713A2/fr
Publication of WO2018085713A3 publication Critical patent/WO2018085713A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection

Definitions

  • the present disclosure relates generally to the field of wireless communications, and more specifically to connection mode selection.
  • UEs In legacy approaches to connection of a user equipment (UE) to a core network in a long term evolution (LTE) context, UEs are typically connected to an evolved packet core (EPC) network. This may not apply to situations where UEs are operating in evolved LTE (eLTE) networks.
  • EPC evolved packet core
  • Figure 1 schematically illustrates a wireless network environment, showing a deployment scenario for eLTE, in accordance with various embodiments.
  • Figure 2 schematically illustrates a handover procedure for a user equipment moving from an eLTE region to an LTE only region, in accordance with various embodiments.
  • Figure 3 illustrates an architecture of a system of a network, in accordance with some embodiments.
  • Figure 4 illustrates an architecture of a system of a network in accordance with some embodiments.
  • Figure 5 illustrates example components of a device, in accordance with some embodiments.
  • Figure 6 illustrates example interfaces of baseband circuitry, in accordance with some embodiments.
  • Figure 7 is a block diagram illustrating components able to read instructions from a machine-readable or computer-readable medium and perform any one or more of the methodologies described in accordance with various embodiments.
  • Figure 8 schematically illustrates a flow diagram for a connection mode process, in accordance with various embodiments.
  • Figure 9 schematically illustrates a flow diagram for a process of selecting a connection mode, in accordance with various embodiments.
  • Some embodiments may relate to a deployment scenario where a LTE radio access network (RAN) may be connected to a Next Generation (NG) core network (which may be called 5G Core).
  • RAN radio access network
  • NG Next Generation
  • eLTE a deployment scenario
  • legacy LTE devices e.g., UEs with LTE but not NG capability
  • the eLTE cells may support LTE devices in various embodiments.
  • a UE supporting both LTE and eLTE may operate in either connection mode (LTE or eLTE) in the eLTE cells.
  • Various embodiments may relate to one or more wireless network elements that select between LTE and eLTE connection modes and/or the manner in which the selection may be performed.
  • Embodiments herein may include identification of a preferred mode in a transmission from a wireless network, selecting a LTE connection mode or an eLTE connection mode based at least in part on the identified preferred mode, and transmission of an indication of the selected LTE connection mode or the eLTE connection mode to the wireless network.
  • An apparatus may include memory to store an indication of a preferred connection mode and processing circuitry coupled with the memory to generate a first message to provide an indication of a preferred connection mode to one or more UEs, where the preferred connection mode is a LTE connection mode or an eLTE connection mode, process a second message that includes an indication of a selected connection mode from a first UE in response to the indication of the preferred connection mode, and facilitate a connection of the first UE to a core network based at least in part on the indication of the selected connection mode.
  • processing circuitry coupled with the memory to generate a first message to provide an indication of a preferred connection mode to one or more UEs, where the preferred connection mode is a LTE connection mode or an eLTE connection mode, process a second message that includes an indication of a selected connection mode from a first UE in response to the indication of the preferred connection mode, and facilitate a connection of the first UE to a core network based at least in part on the indication of the selected connection mode.
  • phrase “A and/or B” means (A), (B), or (A and B).
  • phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
  • Coupled with along with its derivatives, may be used herein.
  • Coupled may mean one or more of the following. “Coupled” may mean that two or more elements are in direct physical or electrical contact. However, “coupled” may also mean that two or more elements indirectly contact each other, but yet still cooperate or interact with each other, and may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • FIG. 1 schematically illustrates a wireless network environment 10, showing a deployment scenario for eLTE, in accordance with various embodiments.
  • the wireless network environment 10 may include a home subscriber server (HSS) 12 coupled with an evolved packet core (EPC) network 14.
  • HSS home subscriber server
  • EPC evolved packet core
  • the HSS 12 may be coupled with the EPC network 14 over a link 16.
  • the link 16 may be or include a S6a interface.
  • the HSS 12 may also be coupled with a next generation (NG) core network 18 over a link 20.
  • the link 20 may be or include a NG S6a interface.
  • an eLTE RAN 22 may be associated with a eLTE cell 24.
  • the eLTE RAN 22 may be or include an eLTE evolved Node B
  • the eLTE RAN 22 may be coupled with both the EPC 14 and the NG core network 18 to support LTE devices connecting to the EPC 14 and eLTE devices connecting to the NG core network 18.
  • the eLTE RAN 22 may be coupled with the EPC 14 over a link 26.
  • the link 26 may be or include a S I interface.
  • the eLTE RAN 22 may be coupled with the NG core network 18 over a link 28.
  • the link 28 may be or include one or more of a NG-C interface or an NG-U interface.
  • the eLTE RAN 22 may serve a first UE 30 and a second UE 32 in the eLTE cell 24. In some
  • the first UE 30 may be a legacy UE having LTE but not eLTE capability and the second UE 32 may be an eLTE UE having both LTE and eLTE capability.
  • the eLTE RAN 22 may facilitate connection of the first UE 30 to the EPC 14 in a connection 34.
  • the eLTE RAN 22 may facilitate connection of the second eLTE UE 32 to the EPC 14 in a first connection 36 when the second UE 32 connects in a LTE connection mode or to the NG core network 18 in a second connection 38 when the second UE 32 connects in an eLTE connection mode.
  • a NG RAN 40 may be associated with a NG cell 42.
  • the NG RAN 40 may be coupled with the NG core network 18 over a link 44.
  • the link 44 may be or include one or more of a NG-C interface or an NG-U interface.
  • the NG RAN 40 may serve a third UE 46.
  • the third UE 46 may be a NG UE.
  • the NG RAN 40 may facilitate a connection of the third UE 46 to the NG core network 18 in a connection 48.
  • a cell may serve both LTE and eLTE UEs.
  • LTE UEs may be connected to an EPC (e.g., EPC 14) while eLTE UEs may be connected to a NG core network (e.g., NG core network 18).
  • Various embodiments may include a mechanism to connect a UE to an appropriate core network (CN) when the UE (e.g., first UE 30 or second UE 32) makes an access to the cell.
  • CN appropriate core network
  • the network may decide which mode of operation (e.g., LTE connection mode or eLTE connection mode) to use for a particular UE.
  • One or more components of the network e.g., eLTE RAN 22
  • a UE e.g., first UE 30 or second UE 32
  • Some embodiments may support a change of mode between LTE and eLTE at a crossing of a LTE/eLTE border (e.g., tracking area (TA) border) for UEs in Idle mode and may be performed as part of a TA update procedure.
  • the network may release the connection to the UE and request the UE to perform an Attach in the other mode. This may be done using an indication in an equivalent of a radio resource control (RRC) connection release message in some embodiments.
  • RRC radio resource control
  • a UE may indicate to the network what mode it is operating in before or along with an initial direct transfer message to the CN, or when data is sent.
  • a change of connection mode between LTE and eLTE may be supported using an inter-mode handover (HO) procedure for UEs in Connected mode.
  • an inter-mode HO for UEs in Connected mode may be used for a change of connection mode between LTE and eLTE in the same cell.
  • a UE supporting both LTE and eLTE which may be referred to as (e)LTE in some embodiments, may operate in either connection mode in the eLTE cells.
  • a particular mode of operation may be chosen for the UE.
  • Various embodiments may include a LTE - eLTE mode selection.
  • the eLTE cells may indicate support of both LTE and eLTE devices.
  • all of the system information (SI) and other common channels defined to support LTE devices may be supported on eLTE cells in addition to eLTE specific SI and common channels (if any).
  • an LTE or eLTE mode selection may also be based on a partitioning of a load from a RAN to the two core networks (e.g., EPC and NG core network).
  • the network may determine which mode of operation to use for a particular UE.
  • mode selection may be performed during initial access.
  • a UE attaching to the network may indicate whether it supports both modes in, for example, RRC message 5 or as part of the UE capability that may already have been provided to the network over a previous connection.
  • SIB system information block
  • UEs may only indicate an eLTE capability when the UE has determined the network supports eLTE.
  • UEs may be capable of determining whether the network supports LTE and eLTE.
  • one or more UEs may signal the network of which mode to support via RRC message 5 or any other suitable message (e.g., message 1 or message 3).
  • the signaling of the network of which mode to support via message 1 may be performed with a choice of random access channel (RACH) preamble to provide the indication.
  • the signaling of the network of which mode to support via message 3 may include an indication at a medium access control (MAC) layer or an indication in RRC.
  • MAC medium access control
  • the network may signal one or more UEs of which mode to support via system information (e.g., using a system information block (SIB)).
  • system information e.g., using a system information block (SIB)
  • SIB system information block
  • the signaling of the network to one or more UEs of which mode to support may be encoded in the tracking area (TA) identifier (ID).
  • the same TA ID may be used for LTE and eLTE modes in some embodiments.
  • the same broadcast TA ID in SIB2 may be used for both LTE and eLTE modes.
  • LTE and eLTE modes may be broadcast in different SIBs.
  • a change of mode from LTE to eLTE for Idle UEs may only be supported at the time of a TA update procedure in some embodiments.
  • cells of a TA may support the same mode(s) of operation.
  • a change of mode of the UE may only be applied at TA update in idle mode. In some embodiments, a change of mode of the UE in idle mode may be performed via paging. In some embodiments, a change of mode of the UE in idle mode may be performed in an updated SIB.
  • a UE may indicate the modes it supports and the network may direct the Attach message to the appropriate node. In some embodiments, this may function with an Attach message that may be the same for EPC and NG Core. In some embodiments, the network may broadcast a preferred mode bit which may be used by the UE to select a mode to Attach in. In a second option according to some embodiments, a UE may select one mode (either left to UE implementation, pre-specified or broadcast). If this mode is not considered acceptable to the network, it may subsequently change the mode of operation in some embodiments.
  • a UE indicates the modes it supports in an attach message, or along with an attach message, during initial access. In some embodiments, a UE selects one mode based on network support and the network may reconfigure the mode.
  • the network may broadcast a preferred mode bit.
  • the preferred mode may be specified.
  • a UE when attaching for the first time in an eLTE network, a UE selects a preferred mode.
  • the preferred mode may be specified or broadcast in various embodiments.
  • the preferred mode of the network may be broadcast or may be sent in a dedicated signal to the UE.
  • the preferred mode may also be preprogrammed in the UE (e.g., in UE subscriber identity module (SIM)).
  • SIM subscriber identity module
  • the UE may continue to be served in the mode that it was attached while it is within a tracking area.
  • the UE may indicate to the network at least by msg 5, whether it is accessing EPC or NG Core. This may be, for example, by way of Physical Random Access Channel (PRACH) partitioning, some indication in msg 3 (e.g., through System Architecture Evolution (SAE) Temporary Mobile Subscriber Identity (S- TMSI) or a cause value), or in msg 5.
  • PRACH Physical Random Access Channel
  • SAE System Architecture Evolution
  • S- TMSI Temporary Mobile Subscriber Identity
  • this may allow the eLTE NB to route the Service request or other Initial transfer message to EPC or NG Core.
  • the eLTE NB may have a capability to identify by message 5 whether the UE was connected to EPC or NG Core for access within a Tracking area.
  • Some embodiments may support a change of mode between LTE and eLTE.
  • a change of mode between LTE and eLTE may be supported when a UE moves between two regions (e.g., a LTE only region and an eLTE region.) As discussed above, this border may coincide with a TA boundary.
  • a UE may be in a connected state or an Idle state while crossing such a TA border and both states may be supported in some embodiments.
  • a UE may only be allowed to change mode when crossing the TA boundary. In other embodiments, the UE may change mode within the TA boundary in response to a signal from the network to change mode.
  • mobility between LTE and eLTE modes in Idle mode may be supported.
  • a change of mode between LTE and eLTE may be supported at crossing a LTE/eLTE border (TA border) for UEs in Idle mode.
  • TA border LTE/eLTE border
  • eLTE to LTE when moving from an eLTE region to an LTE only region, a UE performs a legacy TA update or an Attach or dual Attach procedure. In some embodiments, this may result in a change of mode from eLTE to LTE.
  • LTE to eLTE Similar to the initial access, in some embodiments, a UE chooses the mode it was in (in this case, LTE). If the chosen mode is eLTE, the UE performs a legacy TA update or an Attach or dual Attach procedure.
  • FIG. 2 schematically illustrates a HO procedure 60 for a UE 62 moving from an eLTE to an LTE only region, in accordance with various embodiments.
  • the UE 62 may initially be connected over eLTE as shown in a box 64.
  • the UE 62 may initially be in an eLTE region (e.g., cell 24 of Figure 1) and may be connected to a NG core 66 via a eLTE eNB 68.
  • LTE measurements may be performed at a block 70, and the eLTE eNB 68 may determine at a block 72 that a HO to LTE will be performed based at least in part on the LTE
  • the eLTE eNB 68 may then send a HO required message 74 to the NG core 66.
  • the NG core 66 may perform a conversion to an EPC context at a block 76 and send a context transfer message 78 to an EPC 80.
  • the EPC 80 may send a HO request 82 to an LTE eNB 84 in response to the context transfer message 78.
  • the HO request 82 may include a UE context that may include EPS bearers.
  • the LTE eNB 84 may establish a HO command at a block 86 based at least in part on the UE context and data radio bearers (DRBs) to be set up.
  • the LTE eNB 84 may send an HO request acknowledgment (Ack) 88 to the EPC 80 and the EPC 80 may send a handover ack 90 to the NG Core 66.
  • the NG core 66 may send a HO command 92 to the eLTE eNB 68.
  • the eLTE eNB 68 may send a HO command 94 to the UE 62.
  • the UE 62 may access LTE with a configuration and DRBs in the HO command 94.
  • the UE may have LTE access 98 via the LTE eNB 84.
  • mobility between LTE and eLTE modes in Connected mode may be supported.
  • a change of mode may be possible during HO at least at an LTE-eLTE border (e.g., from a first geographical region that supports LTE but not eLTE to a second geographical region that supports eLTE, or from a first geographical region that supports eLTE to a second geographical region that supports LTE but not eLTE).
  • the geographical regions may be TAs.
  • a change of mode between LTE and eLTE may only be supported using a HO procedure for UEs in Connected mode. The following scenarios and procedures may be supported in various embodiments:
  • eLTE to LTE When moving from an eLTE region to a LTE only region, network performs an inter-mode HO.
  • An example HO procedure is shown in Figure 2.
  • LTE to eLTE The network chooses the mode after the HO. If the chosen mode is eLTE, network performs an inter-mode HO. Otherwise UE continues in LTE mode using a legacy intra-RAT HO.
  • a change of mode operation may be performed only using a HO procedure.
  • Some embodiments may include signaling a "change of mode" to indicate to the UE a change of mode operation. This may be a change from LTE to eLTE or eLTE to LTE.
  • Some embodiments may include signaling a "change of mode request" to indicate from the UE to the network to request a change of mode. This may be a 1 bit indication to request a change of mode or may detail an indication from LTE to eLTE or eLTE to LTE.
  • some embodiments may also support a change of mode while the UE is connected or during an access attempt in an intra-cell scenario. In some embodiments, this may be achieved using an intra-cell/inter- mode HO using the same inter-mode HO procedure mentioned above for the border case. In some embodiments, an inter-mode HO for UEs in Connected mode can be used for a change of mode between LTE and eLTE in the same cell.
  • Some embodiments may use something similar to a load balancing tracking area update (TAU).
  • TAU load balancing tracking area update
  • a UE connection may be released with a cause value that forces the UE to immediately re-access the cell using a TA update or Attach in the other mode.
  • circuitry may refer to, be part of, or include an
  • ASIC Application Specific Integrated Circuit
  • 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 components that provide the described functionality.
  • the 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. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.
  • FIG. 3 illustrates an architecture of a system 200 of a network in accordance with some embodiments.
  • the system 200 is shown to include a user equipment (UE) 201 and a UE 202.
  • the UEs 201 and 202 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets or any computing device including a wireless communications interface.
  • any of the UEs 201 and 202 can comprise an Internet of
  • IoT Internet-to-machine
  • M2M machine-to-machine
  • MTC machine-type communications
  • PLMN public land mobile network
  • Proximity-Based Service ProSe
  • D2D device-to-device
  • the M2M or MTC exchange of data may be a machine- initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UEs 201 and 202 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 210—
  • RAN radio access network
  • the RAN 210 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access
  • UMTS Evolved Universal Mobile Telecommunications System
  • the UEs 201 and 202 utilize connections 203 and 204, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 203 and 204 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 201 and 202 may further directly exchange communication data via a ProSe interface 205.
  • the ProSe interface 205 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 202 is shown to be configured to access an access point (AP) 206 via connection 207.
  • the connection 207 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP 206 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 206 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 210 can include one or more access nodes that enable the connections 203 and 204.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 210 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 211 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 212.
  • macro RAN node 211 e.g., macro RAN node 211
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes 21 1 and 212 can terminate the air interface protocol and can be the first point of contact for the UEs 201 and 202.
  • any of the RAN nodes 21 1 and 212 can fulfill various logical functions for the RAN 210 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs 201 and 202 can be configured to communicate using Orthogonal Frequency -Division Multiplexing (OFDM)
  • OFDM Orthogonal Frequency -Division Multiplexing
  • OFDMMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 21 1 and 212 to the UEs 201 and 202, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel (PDSCH) may carry user data and higher- layer signaling to the UEs 201 and 202.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 201 and 202 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • PDSCH physical downlink shared channel
  • PDCCH physical downlink control channel
  • H-ARQ Hybrid Automatic Repeat Request
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 201 and 202.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 210 is shown to be communicatively coupled to a core network (CN)
  • CN core network
  • the CN 220 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 213 is split into two parts: the Sl-U interface 214, which carries traffic data between the RAN nodes 211 and 212 and the serving gateway (S-GW) 222, and the SI -mobility management entity (MME) interface 215, which is a signaling interface between the RAN nodes 211 and 212 and MMEs 221.
  • S-GW serving gateway
  • MME SI -mobility management entity
  • the CN 220 comprises the MMEs 221, the S-GW 222, the Packet Data Network (PDN) Gateway (P-GW) 223, and a home subscriber server (HSS) 224.
  • the MMEs 221 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 221 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 224 may comprise a database for network users, including subscription-related information to support the network entities' handling of
  • the CN 220 may comprise one or several HSSs 224, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 224 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 222 may terminate the S 1 interface 213 towards the RAN 210, and routes data packets between the RAN 210 and the CN 220.
  • the S-GW 222 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 223 may terminate an SGi interface toward a PDN.
  • the P-GW 223 may route data packets between the EPC network 223 and external networks such as a network including the application server 230 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 225.
  • the application server 230 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 223 is shown to be communicatively coupled to an application server 230 via an IP communications interface 225.
  • the application server 230 can also be configured to support one or more communication services (e.g., Voice- over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 201 and 202 via the CN 220.
  • VoIP Voice- over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 223 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 226 is the policy and charging control element of the CN 220.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • PCRF 226 may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN).
  • the PCRF 226 may be
  • the application server 230 may signal the PCRF 226 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 226 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 230.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 4 illustrates an architecture of a system 300 of a network in accordance with some embodiments.
  • the system 300 is shown to include a UE 301, which may be the same or similar to UEs 201 and 202 discussed previously; a RAN node 311 , which may be the same or similar to RAN nodes 211 and 212 discussed previously; a User Plane Function (UPF) 302; a Data network (DN) 303, which may be, for example, operator services, Internet access or 3rd party services; and a 5G Core Network (5GC or CN) 320.
  • UPF User Plane Function
  • DN Data network
  • 5GC or CN 5G Core Network
  • the CN 320 may include an Authentication Server Function (AUSF) 322; a Core Access and Mobility Management Function (AMF) 321 ; a Session Management Function (SMF) 324; a Network Exposure Function (NEF) 323; a Policy Control function (PCF) 326; a Network Function (NF) Repository Function (NRF) 325; a Unified Data
  • AUSF Authentication Server Function
  • AMF Core Access and Mobility Management Function
  • SMF Session Management Function
  • NEF Network Exposure Function
  • PCF Policy Control function
  • NF Network Function
  • UPF Unified Data
  • the CN 320 may also include other elements that are not shown, such as a Structured Data Storage network function (SDSF), an Unstructured Data Storage network function (UDSF), and the like.
  • SDSF Structured Data Storage network function
  • UDSF Unstructured Data Storage network function
  • the UPF 302 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN 303, and a branching point to support multi-homed PDU session.
  • the UPF 302 may also perform packet routing and forwarding, packet inspection, enforce user plane part of policy rules, lawfully intercept packets (UP collection); traffic usage reporting, perform QoS handling for user plane (e.g. packet filtering, gating, UL/DL rate enforcement), perform Uplink Traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering.
  • UPF 302 may include an uplink classifier to support routing traffic flows to a data network.
  • the DN 303 may represent various network operator services, Internet access, or third party services.
  • NY 303 may include, or be similar to application server 230 discussed previously.
  • the AUSF 322 may store data for authentication of UE 301 and handle authentication related functionality.
  • the AUSF 322 may facilitate a common
  • the AMF 321 may be responsible for registration management (e.g., for registering UE 301 , etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization.
  • AMF 321 may provide transport for SM messages between and SMF 324, and act as a transparent proxy for routing SM messages.
  • AMF 321 may also provide transport for short message service (SMS) messages between UE 301 and an SMS function (SMSF) (not shown by Figure 4).
  • SMS short message service
  • SMSF SMS function
  • AMF 321 may act as Security Anchor Function (SEA), which may include interaction with the AUSF 322 and the UE 301, receipt of an intermediate key that was established as a result of the UE 301 authentication process.
  • SEA Security Anchor Function
  • the AMF 321 may retrieve the security material from the AUSF 322.
  • AMF 321 may also include a Security Context Management (SCM) function, which receives a key from the SEA that it uses to derive access-network specific keys.
  • SCM Security Context Management
  • AMF 321 may be a termination point of RAN CP interface (N2 reference point), a termination point of NAS (Nl) signalling, and perform NAS ciphering and integrity protection.
  • AMF 321 may also support NAS signalling with a UE 301 over an N3
  • the N3IWF may be used to provide access to untrusted entities.
  • N33IWF may be a termination point for the N2 and N3 interfaces for control plane and user plane, respectively, and as such, may handle N2 signalling from SMF and AMF for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated to such marking received over N2.
  • N3IWF may also relay uplink and downlink control-plane NAS (Nl) signalling between the UE 301 and AMF 321, and relay uplink and downlink user-plane packets between the UE 301 and UPF 302.
  • the N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 301.
  • the SMF 324 may be responsible for session management (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation & management (including optional Authorization); Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; termination of interfaces towards Policy control functions; control part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI System); termination of SM parts of NAS messages; downlink Data Notification; initiator of AN specific SM information, sent via AMF over N2 to AN; determine SSC mode of a session.
  • session management e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node
  • UE IP address allocation & management including optional Authorization
  • Selection and control of UP function Configures traffic steering at UPF to route traffic to proper destination; termination of interfaces towards Policy control functions; control part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI System); termination of
  • the SMF 324 may include the following roaming functionality: handle local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI System); support for interaction with external DN for transport of signalling for PDU session
  • the NEF 323 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re- exposure, Application Functions (e.g., AF 328), edge computing or fog computing systems, etc.
  • the NEF 323 may authenticate, authorize, and/or throttle the AFs.
  • NEF 323 may also translate information exchanged with the AF 328and information exchanged with internal network functions. For example, the NEF 323 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 323 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 323 as structured data, or at a data storage NF using a standardized interfaces. The stored information can then be re-exposed by the NEF 323 to other NFs and AFs, and/or used for other purposes such as analytics.
  • NFs network functions
  • the NRF 325 may support service discovery functions, receive NF Discovery Requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 325 also maintains information of available NF instances and their supported services.
  • the PCF 326 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behaviour.
  • the PCF 326 may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of UDM 327.
  • FE front end
  • the UDM 327 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 301.
  • the UDM 327 may include two parts, an application FE and a User Data Repository (UDR).
  • the UDM may include a UDM FE, which is in charge of processing of credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing; user identification handling; access authorization; registration/mobility management; and subscription management.
  • the UDR may interact with PCF 326.
  • UDM 327 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously.
  • the AF 328 may provide application influence on traffic routing, access to the Network Capability Exposure (NCE), and interact with the policy framework for policy control.
  • the NCE may be a mechanism that allows the 5GC and AF 328 to provide information to each other via NEF 323, which may be used for edge computing implementations.
  • the network operator and third party services may be hosted close to the UE 301 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.
  • the 5GC may select a UPF 302 close to the UE 301 and execute traffic steering from the UPF 302 to DN 303 via the N6 interface.
  • AF 328 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 328 to interact directly with relevant NFs.
  • the CN 320 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 301 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router.
  • the SMS may also interact with AMF 321 and UDM 327 for notification procedure that the UE 301 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327 when UE 301 is available for SMS).
  • the system 300 may include the following service-based interfaces: Namf:
  • Service-based interface exhibited by AMF Service-based interface exhibited by AMF
  • Nsmf Service-based interface exhibited by SMF
  • Nnef Service-based interface exhibited by NEF
  • Npcf Service-based interface exhibited by PCF
  • Nudm Service-based interface exhibited by UDM
  • Naf Service-based interface exhibited by AF
  • Nnrf Service-based interface exhibited by NRF
  • Nausf Service-based interface exhibited by AUSF.
  • the system 300 may include the following reference points: Nl : Reference point between the UE and the AMF; N2: Reference point between the (R)AN and the AMF; N3: Reference point between the (R)AN and the UPF; N4: Reference point between the SMF and the UPF; and N6: Reference point between the UPF and a Data Network.
  • N5 reference point may be between the PCF and the AF; an N7 reference point may be between the PCF and the SMF; an Nl 1 reference point between the AMF and SMF; etc.
  • the CN 320 may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME 221) and the AMF 321 in order to enable interworking between CN 320 and CN 220.
  • system 300 may include multiple RAN nodes 31 1 wherein an Xn interface is defined between two or more RAN nodes 31 1 (e.g., gNBs and the like) that connecting to 5GC 320, between a RAN node 31 1 (e.g., gNB) connecting to 5GC 320 and an eNB (e.g., a RAN node 211 of Figure 3), and/or between two eNBs connecting to 5GC 320.
  • RAN nodes 31 1 e.g., gNBs and the like
  • a RAN node 31 1 e.g., gNB
  • eNB e.g., a RAN node 211 of Figure 3
  • the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface.
  • the Xn-U may provide non- guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality.
  • the Xn-C may provide management and error handling
  • the mobility support may include context transfer from an old (source) serving RAN node 311 to new (target) serving RAN node 311 ; and control of user plane tunnels between old (source) serving RAN node 311 to new (target) serving RAN node 31 1.
  • a protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs.
  • the Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on an SCTP layer.
  • the SCTP layer may be on top of an IP layer.
  • the SCTP layer provides the guaranteed delivery of application layer messages.
  • point-to-point transmission is used to deliver the signaling PDUs.
  • the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.
  • Figure 5 illustrates example components of a device 500 in accordance with some embodiments.
  • the device 500 may include application circuitry 502, baseband circuitry 504, Radio Frequency (RF) circuitry 506, front-end module (FEM) circuitry 508, one or more antennas 510, and power management circuitry (PMC) 512 coupled together at least as shown.
  • the components of the illustrated device 500 may be included in a UE or a RAN node.
  • the device 500 may include less elements (e.g., a RAN node may not utilize application circuitry 502, and instead include a processor/controller to process IP data received from an EPC).
  • the device 500 may include additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • C-RAN Cloud-RAN
  • the application circuitry 502 may include one or more application processors.
  • the application circuitry 502 may include circuitry such as, but not limited to, 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, application processors, etc.).
  • the processors may be coupled with or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the device 500.
  • processors of application circuitry 502 may process IP data packets received from an EPC.
  • the baseband circuitry 504 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 504 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 506 and to generate baseband signals for a transmit signal path of the RF circuitry 506.
  • Baseband processing circuity 504 may interface with the application circuitry 502 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 506.
  • the baseband circuitry 504 may include a third generation (3G) baseband processor 504A, a fourth generation (4G) baseband processor 504B, a fifth generation (5G) baseband processor 504C, or other baseband processor(s) 504D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 504 e.g., one or more of baseband processors 504A-D
  • baseband processors 504A-D may be included in modules stored in the memory 504G and executed via a Central Processing Unit (CPU) 504E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 504 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 504 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 504 may include one or more audio digital signal processor(s) (DSP) 504F.
  • the audio DSP(s) 504F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 504 and the application circuitry 502 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 504 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 504 may support communication with an evolved universal terrestrial radio access network (EUTRAN) 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
  • Embodiments in which the baseband circuitry 504 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 506 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 506 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 506 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 508 and provide baseband signals to the baseband circuitry 504.
  • RF circuitry 506 may also include a transmit signal path which may include circuitry to up- convert baseband signals provided by the baseband circuitry 504 and provide RF output signals to the FEM circuitry 508 for transmission.
  • the receive signal path of the RF circuitry 506 may include mixer circuitry 506a, amplifier circuitry 506b and filter circuitry 506c.
  • the transmit signal path of the RF circuitry 506 may include filter circuitry 506c and mixer circuitry 506a.
  • RF circuitry 506 may also include synthesizer circuitry 506d for synthesizing a frequency for use by the mixer circuitry 506a of the receive signal path and the transmit signal path.
  • the mixer circuitry 506a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 508 based on the synthesized frequency provided by synthesizer circuitry 506d.
  • the amplifier circuitry 506b may be configured to amplify the down-converted signals and the filter circuitry 506c may be 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 504 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 506a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 506a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 506d to generate RF output signals for the FEM circuitry 508.
  • the baseband signals may be provided by the baseband circuitry 504 and may be filtered by filter circuitry 506c.
  • the mixer circuitry 506a of the receive signal path and the mixer circuitry 506a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 506a of the receive signal path and the mixer circuitry 506a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rej ection).
  • the mixer circuitry 506a of the receive signal path and the mixer circuitry 506a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 506a of the receive signal path and the mixer circuitry 506a 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 506 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 504 may include a digital baseband interface to communicate with the RF circuitry 506.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 506d may be a fractional -N synthesizer or 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 506d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 506d may be configured to synthesize an output frequency for use by the mixer circuitry 506a of the RF circuitry 506 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 506d 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 504 or the applications processor 502 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 502.
  • Synthesizer circuitry 506d of the RF circuitry 506 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be 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.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 506d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with 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 506 may include an IQ/polar converter.
  • FEM circuitry 508 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 510, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 506 for further processing.
  • FEM circuitry 508 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 506 for transmission by one or more of the one or more antennas 510.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 506, solely in the FEM 508, or in both the RF circuitry 506 and the FEM 508.
  • the FEM circuitry 508 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 506).
  • the transmit signal path of the FEM circuitry 508 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 506), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 510).
  • PA power amplifier
  • the PMC 512 may manage power provided to the baseband circuitry 504.
  • the PMC 512 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 512 may often be included when the device 500 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 512 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics. While Figure 5 shows the PMC 512 coupled only with the baseband circuitry 504. However, in other embodiments, the PMC 512 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 502, RF circuitry 506, or FEM 508.
  • the PMC 512 may control, or otherwise be part of, various power saving mechanisms of the device 500. For example, if the device 500 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 500 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 500 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 500 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 500 may not receive data in this state, in order to receive data, it must transition back to
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 502 and processors of the baseband circuitry 504 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 504 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 504 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • Figure 6 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 504 of Figure 5 may comprise processors 504A-504E and a memory 504G utilized by said processors.
  • Each of the processors 504A-504E may include a memory interface, 604A-604E, respectively, to send/receive data to/from the memory 504G.
  • the baseband circuitry 504 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 612 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 504), an application circuitry interface 614 (e.g., an interface to send/receive data to/from the application circuitry 502 of Figure 5), an RF circuitry interface 616 (e.g., an interface to send/receive data to/from RF circuitry 506 of Figure 5), a wireless hardware connectivity interface 618 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 620 (e.g., an interface to send/receive power or control signals to/from the PMC 512.
  • a memory interface 612 e.g., an interface to send/rece
  • Figure 7 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 7 shows a diagrammatic representation of hardware resources 700 including one or more processors (or processor cores) 710, one or more memory /storage devices 720, and one or more communication resources 730, each of which may be communicatively coupled via a bus 740.
  • node virtualization e.g., NFV
  • a hypervisor 702 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 700
  • the processors 710 may include, for example, a processor 712 and a processor 714.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory /storage devices 720 may include main memory, disk storage, or any suitable combination thereof.
  • the memory /storage devices 720 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable readonly memory (EPROM), electrically erasable programmable read-only memory
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable readonly memory
  • the communication resources 730 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 704 or one or more databases 706 via a network 708.
  • the communication resources 730 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • wired communication components e.g., for coupling via a Universal Serial Bus (USB)
  • cellular communication components e.g., for coupling via a Universal Serial Bus (USB)
  • NFC components e.g., NFC components
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • Instructions 750 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 710 to perform any one or more of the methodologies discussed herein.
  • the instructions 750 may reside, completely or partially, within at least one of the processors 710 (e.g., within the processor's cache memory), the memory /storage devices 720, or any suitable combination thereof.
  • any portion of the instructions 750 may be transferred to the hardware resources 700 from any combination of the peripheral devices 704 or the databases 706.
  • the memory of processors 710, the memory/storage devices 720, the peripheral devices 704, and the databases 706 are examples of computer-readable and machine-readable media.
  • one or more components of Figures 3, 4, 5, 6, and/or 7, and particularly the baseband circuitry of Figure 5, may be to: store an indication of a preferred connection mode; generate a first message to provide an indication of a preferred connection mode to one or more UEs, where the preferred connection mode is a LTE connection mode or an eLTE connection mode; process a second message that includes an indication of a selected connection mode from a first UE in response to the indication of the preferred connection mode; and facilitate a connection of the first UE to a core network based at least in part on the indication of the selected connection mode.
  • one of more components of Figures 3, 4, 5, 6, and/or 7, and particularly the baseband circuitry 504 may be to: identify a preferred mode in a transmission from a wireless network; select a LTE connection mode or an eLTE connection mode based at least in part on the identified preferred mode; and generate a first message to provide an indication of the selected LTE connection mode or the eLTE connection mode to the wireless network.
  • a process 800 may include: sending or causing to send an indication of a preferred connection mode at a block 802; receiving an indication of a selected connection mode from a UE in response to the sent indication of the preferred connection mode at a block 804; and connecting or causing to connect the UE to a core network based at least in part on the indication of the selected connection mode at a block 206.
  • the electronic device(s), network(s), system(s), chip(s), and/or component(s) or portions or implementations thereof, of Figures 3, 4, 5, 6, 7, and/or some other figure herein may be configured to perform one or more processes, techniques, and/or methods as described herein, or portions thereof. Another such process is depicted in Figure 9.
  • the process 900 may include: identifying or causing to identify a preferred mode in a transmission from a wireless network at a block 902; selecting or causing to select a LTE connection mode or an eLTE connection mode based at least in part on the identified preferred mode at a block 904; and generating or causing to generate a message to provide an indication of the selected LTE connection mode or the eLTE connection mode to the wireless network at a block 906.
  • Example 1 may include at least one non-transitory computer-readable medium comprising instructions stored thereon that, in response to execution of the instructions by one or more processors cause a wireless communications device to: receive an indication of a selected connection mode from a user equipment (UE), wherein the selected connection mode is a long term evolution (LTE) connection mode or an evolved LTE (eLTE) connection mode; and connect the UE to a core network based at least in part on the indication of the selected connection mode.
  • LTE long term evolution
  • eLTE evolved LTE
  • Example 2 may include the subject matter of Example 1, wherein the wireless communications device is also to: send an indication of a preferred connection mode, wherein the preferred connection mode is a LTE connection mode or an eLTE connection mode, wherein the indication of the selected connection mode is received in response to the sent indication of the preferred connection mode.
  • the wireless communications device is also to: send an indication of a preferred connection mode, wherein the preferred connection mode is a LTE connection mode or an eLTE connection mode, wherein the indication of the selected connection mode is received in response to the sent indication of the preferred connection mode.
  • Example 3 may include the subject matter of Example 2, wherein the indication of the preferred connection mode is directed specifically to the UE.
  • Example 4 may include the subject matter of Example 2, wherein the wireless communications device is to send the indication of the preferred connection mode in a broadcast transmission.
  • Example 5 may include the subject matter of any one of Examples 1-4, wherein the indication of the selected connection mode is to be received via radio resource control (RRC).
  • RRC radio resource control
  • Example 6 may include the subject matter of Examples 5, wherein the indication of the selected connection mode is to be received via RRC message 5.
  • Example 7 may include the subject matter of any one of Examples 2-6, wherein the preferred connection mode is to be encoded in a tracking area (TA) identifier (ID).
  • TA tracking area
  • ID identifier
  • Example 8 may include the subject matter of any one of Examples 1-7, wherein the wireless communications device is also to send an indication that both LTE and eLTE devices are supported.
  • Example 9 may include the subject matter of any one of Examples 1-8, wherein the wireless communications device is also to broadcast a tracking area (TA) identifier (ID) in system information block (SIB) 2 to be used for both LTE and eLTE modes.
  • TA tracking area
  • ID system information block
  • Example 10 may include the subject matter of any one of Examples 1 -9, wherein the core network is an evolved packet core (EPC) network, and the wireless
  • EPC evolved packet core
  • communications device is also to: determine the UE moves from a first region that supports LTE but not eLTE to a second region that supports both LTE and eLTE; and connect the UE to a next generation (NG) core network in response to the determination that the UE moves from the first region to the second region.
  • NG next generation
  • Example 11 may include the subject matter of any one of Examples 1 -9, wherein the core network is a next generation (NG) core network, and the wireless
  • Example 12 may include the subject matter of any one of Examples 10-11, wherein the UE is in an idle mode when the UE moves from the first region to the second region.
  • Example 13 may include the subject matter of any one of Examples 10-12, wherein the UE crosses from the first region to the second region at a tracking area border.
  • Example 14 may include the subject matter of any one of Examples 10-13, wherein the wireless communications device is to change the connection mode of the UE via paging.
  • Example 15 may include the subject matter of any one of Examples 10-13, wherein the wireless communications device is to change the connection mode of the UE in an updated system information block (SIB).
  • SIB system information block
  • Example 16 may include the subject matter of Example 10, wherein the indication of the selected connection mode corresponds to a first connection mode, and the wireless communications device is also to release a connection of the UE to the EPC network and request the UE to perform an attach to the NG core network in a second connection mode different from the first connection mode.
  • Example 17 may include the subject matter of Example 11, wherein the indication of the selected connection mode corresponds to a first connection mode, and the wireless communications device is also to release a connection of the UE to the NG core network and request the UE to perform an attach in a second connection mode different from the first connection mode.
  • Example 18 may include the subject matter of any one of Examples 1-3, wherein the indication of the selected connection mode is to be received with an initial direct transfer message from the UE.
  • Example 19 may include the subject matter of any one of Examples 10-11, wherein the UE is in a connected mode when the UE moves from the first region to the second region.
  • Example 20 may include the subject matter of Example 19, wherein the wireless communications device is to perform the change in connection with an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 21 may include the subject matter of any one of Examples 1-9, wherein the core network is a first core network, and the wireless communications device is further to: identify a request from the UE to change a connection mode; and connect the UE to a second core network different from the first core network based at least in part on the request.
  • Example 22 may include the subject matter of Example 21, wherein the request is a one bit indication.
  • Example 23 may include the subject matter of Example 21, wherein the request indicates a change from LTE to eLTE, or from eLTE to LTE.
  • Example 24 may include the subject matter of any one of Examples 1-9, wherein the wireless communications device is further to determine a change of connection mode for the UE while the UE is in a cell that supports both LTE and eLTE.
  • Example 25 may include the subject matter of Example 24, wherein the UE is in a connected mode and the wireless communications device is to change the mode of the UE with an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 26 may include the subject matter of any one of Examples 24-25, wherein the wireless communications device is further to signal to the UE the change of connection mode.
  • Example 27 may include the subject matter of Example 26, wherein the change of connection mode is from LTE to eLTE or from eLTE to LTE.
  • Example 28 may include an apparatus comprising: memory to store an indication of a preferred connection mode; and processing circuitry, coupled with the memory to: process a first message that includes an indication of a selected connection mode from a first UE, wherein the selected connection mode is a long term evolution (LTE) connection mode or an evolved LTE (eLTE) connection mode; and facilitate a connection of the first UE to a core network based at least in part on the indication of the selected connection mode.
  • LTE long term evolution
  • eLTE evolved LTE
  • Example 29 may include the subject matter of Example 28, wherein the processing circuitry is also to generate a second message to provide an indication of a preferred connection mode to the UE, wherein the preferred connection mode is a LTE connection mode or an eLTE connection mode, wherein the first message from the first UE is in response to the indication of the preferred connection mode in the second message.
  • the processing circuitry is also to generate a second message to provide an indication of a preferred connection mode to the UE, wherein the preferred connection mode is a LTE connection mode or an eLTE connection mode, wherein the first message from the first UE is in response to the indication of the preferred connection mode in the second message.
  • Example 30 may include the subject matter of Example 29, wherein the indication of the preferred connection mode is directed specifically to the first UE.
  • Example 31 may include the subject matter of Example 29, wherein the first message to provide the indication of the preferred connection mode is to be sent in a broadcast transmission.
  • Example 32 may include the subject matter of any one of Examples 28-31 , wherein the indication of the selected connection mode is to be received via radio resource control (RRC).
  • RRC radio resource control
  • Example 33 may include the subject matter of any one of Examples 28-31 , wherein the indication of the selected connection mode is to be received via message 1 or message 3.
  • Example 34 may include the subject matter of any one of Examples 29-30, wherein the preferred connection mode is encoded in a tracking area (TA) identifier (ID).
  • TA tracking area
  • ID identifier
  • Example 36 may include the subject matter of any one of Examples 28-35, wherein the processing circuitry is also to generate a tracking area (TA) identifier (ID) in system information block (SIB) 2 to be used for both LTE and eLTE modes.
  • TA tracking area
  • ID system information block
  • Example 37 may include the subject matter of any one of Examples 28-35, wherein the processing circuitry is also to generate a first tracking area (TA) identifier (ID) in a first system information block (SIB) for LTE mode and a second TA ID in a second SIB for eLTE mode.
  • TA tracking area
  • SIB system information block
  • Example 38 may include the subject matter of any one of Examples 28-37, wherein the core network is an evolved packet core (EPC) network, and the processing circuitry is also to: determine the first UE moves from a first region that supports LTE but not eLTE to a second region that supports both LTE and eLTE; and facilitate a connection of the first UE to a next generation (NG) core network in response to the determination that the first UE moves from the first region to the second region.
  • EPC evolved packet core
  • NG next generation
  • Example 39 may include the subject matter of any one of Examples 28-37, wherein the core network is a next generation (NG) core network, and the processing circuitry is also to: determine the first UE moves from a first region that supports LTE and eLTE to a to a second region that does not support eLTE; and facilitate a connection of the first UE to an evolved packet core (EPC) network in response the determination that the first UE moves from the first region to the second region.
  • NG next generation
  • EPC evolved packet core
  • Example 40 may include the subject matter of any one of Examples 38-39, wherein the first UE is in an idle mode when the first UE moves from the first region to the second region.
  • Example 41 may include the subject matter of any one of Examples 38-40, wherein the first UE crosses from the first region to the second region at a tracking area border.
  • Example 42 may include the subject matter of any one of Examples 38-41, wherein the processing circuitry is to change the mode of the first UE via paging.
  • Example 43 may include the subject matter of any one of Examples 38-41, wherein the processing circuitry is to change the mode of the first UE in an updated system information block (SIB).
  • SIB system information block
  • Example 44 may include the subject matter of Example 38, wherein the indication of the selected connection mode corresponds to a first connection mode, and the processing circuitry is also to facilitate a release of a connection of the first UE to the EPC network and generate a request for the first UE to perform an attach in a second connection mode different from the first connection mode.
  • Example 45 may include the subject matter of Example 39, wherein the indication of the selected connection mode corresponds to a first connection mode, and the processing circuitry is also to facilitate a release of a connection of the first UE to the NG core network and generate a request for the first UE to perform an attach in a second connection mode different from the first connection mode.
  • Example 46 may include the subject matter of any one of Examples 28-31, wherein the indication of the selected connection mode is to be received with an initial direct transfer message from the first UE.
  • Example 47 may include the subject matter of any one of Examples 38-39, wherein the first UE is in a connected mode when the first UE moves from the first region to the second region.
  • Example 48 may include the subject matter of Example 47, wherein the processing circuitry is to facilitate the change in connection with an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 49 may include the subject matter of any one of Examples 28-37, wherein the core network is a first core network, and the processing circuitry is further to: identify a request from the first UE to change a connection mode; and facilitate a connection of the first UE to a second core network different from the first core network based at least in part on the request.
  • the core network is a first core network
  • the processing circuitry is further to: identify a request from the first UE to change a connection mode; and facilitate a connection of the first UE to a second core network different from the first core network based at least in part on the request.
  • Example 50 may include the subject matter of Example 49, wherein the request is a one bit indication.
  • Example 51 may include the subject matter of Example 49, wherein the request indicates a change from LTE to eLTE, or from eLTE to LTE.
  • Example 52 may include the subject matter of any one of Examples 28-37, wherein the processing circuitry is further to determine a change of connection mode for the first UE while the first UE is in a cell that supports both LTE and eLTE.
  • Example 53 may include the subject matter of Example 52, wherein the first UE is in a connected mode and the processing circuitry is to change the mode of the first UE with an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 54 may include the subject matter of any one of Examples 52-53, wherein the processing circuitry is further to generate a third message to provide an indication of the change of connection mode to the first UE.
  • Example 55 may include the subject matter of Example 54, wherein the change of connection mode is from LTE to eLTE or from eLTE to LTE.
  • Example 56 may include an apparatus comprising: means for receiving an indication of a selected connection mode from a user equipment (UE), wherein the selected connection mode is a long term evolution (LTE) connection mode or an evolved LTE (eLTE) connection mode; and means for facilitating a connection of the UE to a core network based at least in part on the indication of the selected connection mode.
  • LTE long term evolution
  • eLTE evolved LTE
  • Example 57 may include the subject matter of Example 56, further comprising means for sending an indication of a preferred connection mode, wherein the preferred connection mode is a LTE connection mode or an eLTE connection mode, wherein the means for receiving the indication of the selected connection mode from the UE is to receive the indication of the preferred connection mode in response to the sent indication of the preferred connection mode.
  • Example 58 may include the subject matter of Example 57, wherein the indication of the preferred connection mode is directed specifically to the UE.
  • Example 59 may include the subject matter of Example 57, wherein the means for sending the indication of the preferred connection mode is to send the indication of the preferred connection mode in a broadcast transmission.
  • Example 60 may include the subject matter of any one of Examples 56-59, wherein the indication of the selected connection mode is to be received via radio resource control (RRC).
  • RRC radio resource control
  • Example 61 The apparatus of claim 60, wherein the indication of the selected connection mode is to be received via RRC message 5.
  • Example 62 may include the subject matter of any one of Examples 57-59, wherein the preferred connection mode is encoded in a tracking area (TA) identifier (ID).
  • Example 64 may include the subject matter of any one of Examples 56-63, further comprising means for broadcasting a tracking area (TA) identifier (ID) in system information block (SIB) 2 to be used for both LTE and eLTE modes.
  • TA tracking area
  • ID system information block
  • Example 65 may include the subject matter of any one of Examples 56-63, further comprising means for broadcasting a first tracking area (TA) identifier (ID) in a first system information block (SIB) for LTE mode and a second TA ID in a second SIB for eLTE mode.
  • TA tracking area
  • SIB system information block
  • Example 66 may include the subject matter of any one of Examples 56-65, wherein the core network is an evolved packet core (EPC) network, and the apparatus further includes means for determining the UE moves from a first region that supports LTE but not eLTE to a second region that supports both LTE and eLTE, wherein the means for facilitating a connection of the UE to a core network is also to facilitate a connection of the UE to a next generation (NG) core network in response to the determination that the UE moves from the first region to the second region.
  • EPC evolved packet core
  • NG next generation
  • Example 67 may include the subject matter of any one of Examples 56-65, wherein the core network is a next generation (NG) core network, and the apparatus further includes means for determining the UE moves from a first region that supports LTE and eLTE to a second region that does not support eLTE, wherein the means for facilitating a connection of the UE to a core network is also to facilitate a connection of the UE to an evolved packet core (EPC) network in response to the determination that the UE moves from the first region to the second region.
  • NG next generation
  • EPC evolved packet core
  • Example 68 may include the subject matter of any one of Examples 66-67, wherein the UE is in an idle mode when the UE moves from the first region to the second region.
  • Example 69 may include the subject matter of any one of Examples 66-68, wherein the UE crosses from the first region to the second region at a tracking area border.
  • Example 70 may include the subject matter of any one of Examples 66-69, wherein the means for facilitating a connection of the UE to a core network is to change the mode of the UE via paging.
  • Example 71 may include the subject matter of any one of Examples 66-69, wherein the means for facilitating a connection of the UE to a core network is to change the mode of the UE in an updated system information block (SIB).
  • Example 72 may include the subject matter of Example 66, wherein the indication of the selected connection mode corresponds to a first connection mode, and the means for facilitating a connection of the UE to a core network is also to facilitate a release of a connection of the UE to the EPC network and request the UE to perform an attach in a second connection mode different from the first connection mode.
  • SIB system information block
  • Example 73 may include the subject matter of Example 67, wherein the indication of the selected connection mode corresponds to a first connection mode, and the means for facilitating a connection of the UE to a core network is also to facilitate a release of a connection of the UE to the NG core network and request the UE to perform an attach in a second connection mode different from the first mode.
  • Example 74 may include the subject matter of any one of Examples 56-59, wherein the indication of the selected connection mode is to be received with an initial direct transfer message from the UE.
  • Example 75 may include the subject matter of any one of Examples 66-67, wherein the UE is in a connected mode when the UE moves from the first region to the second region.
  • Example 76 may include the subject matter of Example 75, wherein the means for facilitating a connection of the UE to a core network is to perform the change in connection with an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 77 may include the subject matter of any one of Examples 56-65, wherein the core network is a first core network, and the means for facilitating a connection of the UE to a core network is further to identify a request from the UE to change a connection mode and facilitate a connection of the UE to a second core network different from the first core network based at least in part on the request.
  • Example 78 may include the subject matter of Example 77, wherein the request is a one bit indication.
  • Example 79 may include the subject matter of Example 77, wherein the request indicates a change from LTE to eLTE, or from eLTE to LTE.
  • Example 80 may include the subject matter of any one of Examples 56-65, further comprising means for determining a change of connection mode for the UE while the UE is in a cell that supports both LTE and eLTE.
  • Example 81 may include the subject matter of Example 80, wherein the UE is in connected mode and the apparatus further includes means for changing the mode of the UE with an inter-mode handover (HO) procedure.
  • Example 82 may include the subject matter of any one of Examples 80-81 , further comprising means for signaling to the UE the change of connection mode.
  • Example 83 may include the subject matter of Example 82, wherein the change of connection mode is from LTE to eLTE or from eLTE to LTE.
  • Example 84 may include a method comprising: receiving an indication of a selected connection mode from a user equipment (UE), wherein the selected connection mode is a long term evolution (LTE) connection mode or an evolved LTE (eLTE) connection mode; and connecting the UE to a core network based at least in part on the indication of the selected connection mode.
  • LTE long term evolution
  • eLTE evolved LTE
  • Example 85 may include the subject matter of Example 84, further comprising sending an indication of a preferred connection mode, wherein the preferred connection mode is a LTE connection mode or an eLTE connection mode, wherein the indication of the selected connection mode is received from the UE in response to the sent indication of the preferred connection mode.
  • Example 86 may include the subject matter of Example 85, wherein the indication of the preferred connection mode is directed specifically to the UE.
  • Example 87 may include the subject matter of Example 85, wherein sending the indication of the preferred connection mode is performed in a broadcast transmission.
  • Example 88 may include the subject matter of any one of Examples 84-87, wherein receiving the indication of the selected connection mode includes receiving the indication of the selected connection mode via radio resource control (RRC).
  • RRC radio resource control
  • Example 89 may include the subject matter of Example 88, wherein the indication of the selected connection mode is received via RRC message 5.
  • Example 90 may include the subject matter of any one of Examples 85-87, wherein the preferred connection mode is encoded in a tracking area (TA) identifier (ID).
  • TA tracking area
  • ID identifier
  • Example 92 may include the subject matter of any one of Examples 84-91, further comprising broadcasting a tracking area (TA) identifier (ID) in system information block (SIB) 2 to be used for both LTE and eLTE modes.
  • TA tracking area
  • ID system information block
  • Example 93 may include the subject matter of any one of Examples 84-91, further comprising broadcasting a first tracking area (TA) identifier (ID) in a first system information block (SIB) for LTE mode and a second TA ID in a second SIB for eLTE mode.
  • TA tracking area
  • SIB system information block
  • Example 94 may include the subject matter of any one of Examples 84-93, wherein the core network is an evolved packet core (EPC) network, and the method further includes: determining the UE moves from a first region that supports LTE but not eLTE to a second region that supports both LTE and eLTE; and connecting the UE to a next generation (NG) core network in response to the determination that the UE moves from the first region to the second region.
  • EPC evolved packet core
  • Example 95 may include the subject matter of any one of Examples 84-93, wherein the core network is a next generation (NG) core network, and the method further includes: determining the UE moves from a first region that supports LTE and eLTE to a second region that does not support eLTE; and connecting the UE to an evolved packet core (EPC) network in response to the determination that the UE moves from the first region to the second region.
  • NG next generation
  • EPC evolved packet core
  • Example 96 may include the subject matter of any one of Examples 94-95, wherein the UE is in an idle mode when the UE moves from the first region to the second region.
  • Example 97 may include the subject matter of any one of Examples 94-95, wherein the UE crosses from the first region to the second region at a tracking area border.
  • Example 98 may include the subject matter of any one of Examples 94-95, further comprising changing the mode of the UE via paging.
  • Example 99 may include the subject matter of any one of Examples 94-97, further comprising changing the mode of the UE in an updated system information block (SIB).
  • SIB system information block
  • Example 100 may include the subject matter of Example 94, wherein the indication of the selected connection mode corresponds to a first connection mode, and the method further includes releasing a connection of the UE to the EPC network and requesting the UE to perform an attach in a second connection mode different from the first connection mode.
  • Example 101 may include the subject matter of Example 95, wherein the indication of the selected connection mode corresponds to a first connection mode, and the method further includes releasing a connection of the UE to the NG core network and requesting the UE to perform an attach in a second connection mode different from the first connection mode.
  • Example 102 may include the subject matter of any one of Examples 84-87, wherein the indication of the selected connection mode is received with an initial direct transfer message from the UE.
  • Example 103 may include the subject matter of any one of Examples 94-95, wherein the UE is in a connected mode when the UE moves from the first region to the second region.
  • Example 104 may include the subject matter of Example 103, further comprising performing the change in connection with an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 105 may include the subject matter of any one of Examples 84-93, wherein the core network is a first core network, and the method further includes:
  • Example 106 may include the subject matter of Example 105, wherein the request is a one bit indication.
  • Example 107 may include the subject matter of Example 105, wherein the request indicates a change from LTE to eLTE, or from eLTE to LTE.
  • Example 108 may include the subject matter of any one of Examples 84-93, wherein the method includes determining a change of connection mode for the UE while the UE is in a cell that supports both LTE and eLTE.
  • Example 109 may include the subject matter of Example 108, wherein the UE is in a connected mode and the method includes changing the mode of the UE with an inter- mode handover (HO) procedure.
  • HO inter- mode handover
  • Example 110 may include the subject matter of any one of Examples 108-109, further comprising signaling to the UE the change of connection mode.
  • Example 11 1 may include the subject matter of Example 1 10, wherein the change of connection mode is from LTE to eLTE or from eLTE to LTE.
  • Example 1 12 may include at least one non-transitory computer-readable medium comprising instructions stored thereon that, in response to execution of the instructions by one or more processors cause a user equipment (UE) to: identify a preferred mode; select a long term evolution (LTE) connection mode or an evolved (e) LTE connection mode based at least in part on the identified preferred mode; and transmit an indication of the selected LTE connection mode or the eLTE connection mode to a wireless network.
  • Example 113 may include the subject matter of Example 1 12, wherein the UE is to identify the preferred mode in a transmission from the wireless network.
  • Example 114 may include the subject matter of Example 1 13, wherein the transmission from the wireless network is directed specifically to the UE.
  • Example 115 may include the subject matter of Example 1 13, wherein the transmission from the wireless network is a broadcast transmission.
  • Example 116 may include the subject matter of any one of Examples 112-1 15, wherein the UE is to transmit the indication of the selected LTE connection mode via radio resource control (RRC).
  • RRC radio resource control
  • Example 117 may include the subj ect matter of any one of Examples 112-1 16, wherein the UE is to identify the preferred mode based at least in part on an encoded tracking area (TA) identifier (ID).
  • TA encoded tracking area
  • Example 119 may include the subject matter of any one of Examples 112-1 14, wherein the UE is to transmit the indication of the selected LTE connection mode with an initial direct transfer message.
  • Example 120 may include the subject matter of any one of Examples 112-1 19, wherein the UE is also to identify an indication from the wireless network that a change of connection mode has been performed in response to the UE moves from a first region that supports LTE but not eLTE to a second region that supports both LTE and eLTE.
  • Example 121 may include the subject matter of any one of Examples 112-1 19, wherein the UE is also to identify an indication from the wireless network that a change of connection mode has been performed in response to the UE moves from a first region that supports LTE and eLTE to a second region that does not support eLTE.
  • Example 122 may include the subject matter of any one of Examples 120-121 , wherein the UE is to identify the indication that a change of connection mode has been performed in a paging message.
  • Example 123 may include the subject matter of any one of Examples 120-121 , wherein the UE is to identify the indication that a change of connection mode has been performed in an updated system information block (SIB).
  • SIB system information block
  • Example 124 may include the subject matter of any one of Examples 112-1 19, wherein the UE is also to identify an indication of a connection to a core network in response to the transmitted indication of the selected LTE connection mode or the eLTE connection mode.
  • Example 125 may include the subject matter of Example 124, wherein the core network is a first core network, the selected LTE connection mode or eLTE connection mode is a first connection mode, and the UE is further to: identify an indication that the connection to the first core network has been released; identify a request in a transmission from the wireless network to perform an attach in a second connection mode different from the first connection mode; perform an attach in the second connection mode; and identify an indication of a connection to a second core network different from the first core network in a transmission from the wireless network in response to the attach.
  • Example 126 may include the subject matter of any one of Examples 120-121 , wherein the UE is in a connected mode when the UE moves from the first region to the second region.
  • Example 127 may include the subject matter of Example 126, wherein the UE is to identify the indication that a change of connection mode has been performed as part of an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 128 may include the subject matter of Example 124, wherein: the core network is a first core network; the UE is further to transmit a request to change a connection mode to the wireless network; and the UE is to identify an indication of a connection to a second core network different from the first core network in response to the transmitted request.
  • Example 129 may include the subject matter of Example 128, wherein the request is a one bit indication.
  • Example 130 may include the subject matter of Example 128, wherein the request indicates a change from LTE to eLTE, or from eLTE to LTE.
  • Example 131 may include an apparatus comprising: processing circuitry to:
  • Example 132 may include the subject matter of Example 131 , wherein the processing circuitry is to identify the preferred mode based at least in part on a transmission received from the wireless network.
  • Example 133 may include the subject matter of Example 132, wherein the transmission from the wireless network is directed specifically to the apparatus.
  • Example 134 may include the subject matter of Example 132, wherein the transmission from the wireless network is a broadcast transmission.
  • Example 135. The apparatus of any one of Examples 131 -134, wherein the processing circuitry is to generate the first message for transmission via radio resource control (RRC).
  • RRC radio resource control
  • Example 136 may include the subject matter of Example 135, wherein the processing circuitry is to generate the first message for transmission via RRC message 5.
  • Example 137 may include the subject matter of any one of Examples 131-134, wherein the processing circuitry is to generate the first message for transmission via message 1 or message 3.
  • Example 138 may include the subject matter of any one of Examples 131-137, wherein the processing circuitry is to identify the preferred mode based at least in part on an encoded tracking area (TA) identifier (ID).
  • TA encoded tracking area
  • Example 140 may include the subject matter of any one of Examples 131-134, wherein the processing circuitry is to generate the first message for transmission with an initial direct transfer message.
  • Example 141 may include the subject matter of any one of Examples 131-140, wherein the processing circuitry is also to identify an indication from the wireless network that a change of connection mode has been performed in response to the apparatus moves from a first region that supports LTE but not eLTE to a second region that supports both LTE and eLTE.
  • Example 142 may include the subject matter of any one of Examples 131-140, wherein the processing circuitry is also to identify an indication from the wireless network that a change of connection mode has been performed in response to the apparatus moves from a first region that supports LTE and eLTE to a second region that does not support eLTE.
  • Example 143 may include the subject matter of any one of Examples 141-142, wherein the processing circuitry is to identify the indication that a change of connection mode has been performed in a paging message.
  • Example 144 may include the subject matter of any one of Examples 141-142, wherein the processing circuitry is to identify the indication that a change of connection mode has been performed in an updated system information block (SIB).
  • SIB system information block
  • Example 145 may include the subject matter of any one of Examples 131-140, wherein the processing circuitry is also to identify an indication of a connection to a core network in response to the first message.
  • Example 146 may include the subject matter of Example 145, wherein the core network is a first core network, the selected LTE connection mode or eLTE connection mode is a first connection mode, and the processing circuitry is further to: identify an indication that the connection to the first core network has been released; identify a request in a transmission from the wireless network to perform an attach in a second connection mode different from the first connection mode; perform an attach in the second connection mode; and identify an indication of a connection to a second core network different than the first core network in a transmission from the wireless network in response to the attach.
  • Example 147 may include the subject matter of any one of Examples 141-142, wherein the apparatus is in a connected mode when the apparatus moves from the first region to the second region.
  • Example 148 may include the subject matter of Example 147, wherein the processing circuitry is to identify the indication that a change of connection mode has been performed as part of an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 149 may include the subject matter of Example 145, wherein the core network is a first core network and the processing circuitry is further to: generate a request to change a connection mode for transmission to the wireless network; and identify an indication of a connection to a second core network different from the first core network in response to the request.
  • Example 150 may include the subject matter of Example 149, wherein the request includes a one bit indication.
  • Example 151 may include the subject matter of Example 149, wherein the request indicates a change from LTE to eLTE, or from eLTE to LTE.
  • Example 152 may include an apparatus comprising: means for identifying a preferred mode; means for selecting a long term evolution (LTE) connection mode or an evolved (e) LTE connection mode based at least in part on the identified preferred mode; and means for generating a message to provide an indication of the selected LTE connection mode or the eLTE connection mode to a wireless network.
  • LTE long term evolution
  • e evolved
  • Example 153 may include the subject matter of Example 152, wherein the means for identifying the preferred mode is to identify the preferred mode based at least in part on a transmission from the wireless network.
  • Example 154 may include the subject matter of Example 153, wherein the transmission from the wireless network is directed specifically to the apparatus.
  • Example 155 may include the subject matter of Example 153, wherein the transmission from the wireless network is a broadcast transmission.
  • Example 156 may include the subject matter of any one of Examples 152-155, wherein the means for generating the message is to generate the message for transmission via radio resource control (RRC).
  • RRC radio resource control
  • Example 157 may include the subject matter of Example 156, wherein the means for generating the message is to generate the message for transmission via RRC message 5.
  • Example 158 may include the subject matter of any one of Examples 152-155, wherein the means for identifying the preferred mode is to identify the preferred mode based at least in part on an encoded tracking area (TA) identifier (ID).
  • TA encoded tracking area
  • Example 160 may include the subject matter of any one of Examples 152-155, wherein the means for generating the message is to generate the message for transmission with an initial direct transfer message.
  • Example 161 may include the subject matter of any one of Examples 152-160, further comprising means for identifying an indication from the wireless network that a change of connection mode has been performed in response to the apparatus moves from a first region that supports LTE but not eLTE to a second region that supports both LTE and eLTE.
  • Example 162 may include the subject matter of any one of Examples 152-160, further comprising means for identifying an indication from the wireless network that a change of connection mode has been performed in response to the apparatus moves from a first region that supports LTE and eLTE to a second region that does not support eLTE.
  • Example 163 may include the subject matter of any one of Examples 161-162, wherein the means for identifying an indication from the wireless network that a change of connection mode has been performed is to identify the indication that a change of connection mode has been performed in a paging message.
  • Example 164 may include the subject matter of any one of Examples 161-162, wherein the means for identifying an indication from the wireless network that a change of connection mode has been performed is to identify the indication that a change of connection mode has been performed in an updated system information block (SIB).
  • SIB system information block
  • Example 165 may include the subject matter of any one of Examples 152-160, further comprising means for identifying an indication of a connection to a core network in response to the message to provide the indication of the selected LTE connection mode or the eLTE connection mode.
  • Example 166 may include the subject matter of Example 165, wherein the core network is a first core network, the selected LTE connection mode or eLTE connection mode is a first connection mode, and the apparatus further includes: means for identifying an indication that the connection to the first core network has been released; means for identifying a request in a transmission from the wireless network to perform an attach in a second connection mode different from the first connection mode; means for performing an attach in the second connection mode; and means for identifying an indication of a connection to a second core network different from the first core network in a transmission from the wireless network in response to the attach.
  • Example 167 may include the subject matter of any one of Examples 161-162, wherein the apparatus is in connected mode when the apparatus moves from the first region to the second region.
  • Example 168 may include the subject matter of Example 167, wherein the apparatus includes means for identifying an indication that a change of connection mode has been performed as part of an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 169 may include the subject matter of Example 165, wherein: the core network is a first core network; the apparatus further includes means for generating a request to change a connection mode for transmission to the wireless network; and the means for identifying an indication of a connection to a second core network different from the first core network is to identify an indication of a connection to a second core network different from the first core network in response to the request.
  • Example 170 may include the subject matter of Example 169, wherein the request includes a one bit indication.
  • Example 171 may include the subject matter of Example 169, wherein the request indicates a change from LTE to eLTE, or from eLTE to LTE.
  • Example 172 may include a method comprising: identifying a preferred mode; selecting a long term evolution (LTE) connection mode or an evolved (e) LTE connection mode based at least in part on the identified preferred mode; and generating a message to provide an indication of the selected LTE connection mode or the eLTE connection mode to a wireless network.
  • LTE long term evolution
  • e evolved
  • Example 173 may include the subject matter of Example 172, wherein identifying the preferred mode includes identifying the preferred mode based at least in part on a transmission from the wireless network.
  • Example 174 may include the subject matter of Example 173, wherein the transmission from the wireless network is directed specifically to a user equipment (UE).
  • UE user equipment
  • Example 175 may include the subject matter of Example 173, wherein the transmission from the wireless network is a broadcast transmission.
  • Example 176 may include the subject matter of any one of Examples 172-175, wherein generating the message includes generating the message for transmission via radio resource control (RRC).
  • RRC radio resource control
  • Example 177 may include the subject matter of Example 176, wherein generating the message includes generating the message for transmission via RRC message 5.
  • Example 178 may include the subject matter of any one of Examples 172-177, wherein identifying the preferred mode includes identifying the preferred mode based at least in part on an encoded tracking area (TA) identifier (ID).
  • TA encoded tracking area
  • Example 180 may include the subject matter of any one of Examples 172-175, wherein generating the message includes generating the message for transmission with an initial direct transfer message.
  • Example 181 may include the subject matter of any one of Examples 172-180, further comprising identifying an indication from the wireless network that a change of connection mode has been performed in response to a UE moves from a first region that supports LTE but not eLTE to a second region that supports both LTE and eLTE.
  • Example 182 may include the subject matter of any one of Examples 172-180, further comprising identifying an indication from the wireless network that a change of connection mode has been performed in response to a UE moves from a first region that supports LTE and eLTE to a second region that does not support eLTE.
  • Example 183 may include the subject matter of any one of Examples 181-182, wherein the method includes identifying the indication that a change of connection mode has been performed in a paging message.
  • Example 184 may include the subject matter of any one of Examples 181-182, wherein the method includes identifying the indication that a change of connection mode has been performed in an updated system information block (SIB).
  • SIB system information block
  • Example 185 may include the subject matter of any one of Examples 172-180, further comprising identifying an indication of a connection to a core network in response to the message to provide the indication of the selected LTE connection mode or the eLTE connection mode.
  • Example 186 may include the subject matter of Example 185, wherein the core network is a first core network, the selected LTE connection mode or eLTE connection mode is a first connection mode, and the method further includes: identifying an indication that the connection to the first core network has been released; identifying a request in a transmission from the wireless network to perform an attach in a second connection mode different from the first connection mode; performing an attach in the second connection mode; and identifying an indication of a connection to a second core network different than the first core network in a transmission from the wireless network in response to the attach.
  • Example 187 may include the subject matter of any one of Examples 181-182, wherein the UE is in a connected mode when the UE moves from the first region to the second region.
  • Example 188 may include the subject matter of Example 187, wherein the method includes identifying the indication that a change of connection mode has been performed as part of an inter-mode handover (HO) procedure.
  • HO inter-mode handover
  • Example 189 may include the subject matter of Example 185, wherein: the core network is a first core network; the method further includes generating a request to change a connection mode for transmission to the wireless network; and identifying an indication of a connection to a second core network different from the first core network in response to the request.
  • Example 190 may include the subject matter of Example 189, wherein the request is a one bit indication.
  • Example 191 may include the subject matter of Example 189, wherein the request indicates a change from LTE to eLTE, or from eLTE to LTE.
  • Example 192 may include it is up to the network to decide which mode of operation to use for a particular UE.
  • Example 193 may include when attaching for the first time in a cell that supports LTE and eLTE connection modes, UE selects a preferred mode.
  • the preferred mode could be specified or broadcast.
  • Example 194 may include the signaling of the network of which mode to support can be via message 5.
  • Example 195 may include the signaling of the network of which mode to support can be encoded in the tracking area ID.
  • Example 196 may include the same broadcast TA ID in SIB2 should be used for both LTE and eLTE modes.
  • Example 197 may include the LTE and eLTE modes can be broadcast in different SIB.
  • Example 198 may include the change of mode between LTE and eLTE is supported at crossing a LTE/eLTE border (TA border) for UEs in Idle mode and is done by performing as part of TA update procedure.
  • TA border LTE/eLTE border
  • Example 199 may include the change of mode of the UE in idle mode can be done via paging.
  • Example 200 may include the change of mode of the UE in idle mode can be done in SIB updated.
  • Example 201 may include in another embodiment, the network can release the connection to the UE and request the UE to perform an Attach in the other mode. This can be done using an indication in an equivalent of RRC connection release message.
  • Example 202 may include UE shall indicate to the network what mode it is operating in before or along with the initial direct transfer message to the CN or when data is sent.
  • Example 203 may include UE selects one mode based on network support, network can reconfigure the mode.
  • Example 204 may include change of mode between LTE and eLTE can be supported using an inter-mode HO procedure for UEs in Connected mode.
  • Example 205 may include Inter-mode HO for UEs in Connected mode can be used for change of mode between LTE and eLTE in the same cell.
  • Example 206 may include the UE can change mode within a TA boundary when the network signals to do so.
  • Example 207 may include signaling a "change of mode" to indicate to the UE a change of mode operation. This can be a change from LTE to eLTE or eLTE to LTE.
  • Example 208 may include signaling a "change of mode request" to indicate from the UE to the network to request a change of mode. This can be a 1 bit indication of a change of mode or detail an indication from LTE to eLTE or eLTE to LTE.
  • Example 209 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1 -208, or any other method or process described herein.
  • Example 210 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1 -208, or any other method or process described herein.
  • Example 21 1 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1 - 208, or any other method or process described herein.
  • Example 212 may include a method, technique, or process as described in or related to any of examples 1-208, or portions or parts thereof.
  • Example 213 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1 -208, or portions thereof.
  • Example 214 may include a method of communicating in a wireless network as shown and described herein.
  • Example 215 may include a system for providing wireless communication as shown and described herein.
  • Example 216 may include a device for providing wireless communication as shown and described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente invention peuvent comprendre : l'identification d'un mode préféré ; la sélection d'un mode de connexion d'évolution à long terme (LTE) ou d'un mode de connexion LTE évolué (eLTE) sur la base, au moins en partie, du mode préféré identifié ; et la transmission d'une indication du mode de connexion sélectionné à un réseau sans fil. Un appareil peut comprendre une mémoire pour stocker une indication d'un mode de connexion préféré, et un montage de circuits de traitement utilisé pour générer un premier message contenant une indication d'un mode de connexion préféré, traiter un second message contenant une indication d'un mode de connexion sélectionné par un premier UE en réponse à l'indication du mode de connexion préféré, et faciliter une connexion du premier UE à un réseau central sur la base, au moins en partie, de l'indication du mode de connexion sélectionné. L'invention concerne également d'autres modes de réalisation.
PCT/US2017/060033 2016-11-04 2017-11-03 Sélection d'accès initial et de mode dans des réseaux d'évolution à long terme (lte) évolués WO2018085713A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662417597P 2016-11-04 2016-11-04
US62/417,597 2016-11-04

Publications (2)

Publication Number Publication Date
WO2018085713A2 true WO2018085713A2 (fr) 2018-05-11
WO2018085713A3 WO2018085713A3 (fr) 2018-06-14

Family

ID=60409398

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/060033 WO2018085713A2 (fr) 2016-11-04 2017-11-03 Sélection d'accès initial et de mode dans des réseaux d'évolution à long terme (lte) évolués

Country Status (1)

Country Link
WO (1) WO2018085713A2 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180376384A1 (en) * 2017-01-09 2018-12-27 Lg Electronics Inc. Method for interworking between networks in wireless communication system and apparatus thereof
CN110519074A (zh) * 2018-05-22 2019-11-29 华为技术有限公司 一种服务区域管理方法及装置
WO2020033356A1 (fr) * 2018-08-09 2020-02-13 Google Llc Procédé et équipement utilisateur pour reprendre une connexion sans fil
JP2020523807A (ja) * 2018-05-18 2020-08-06 株式会社Ｎｔｔドコモ コアリソースの分配
CN111757428A (zh) * 2018-05-18 2020-10-09 Oppo广东移动通信有限公司 信息处理方法、网络设备、终端设备
WO2022199338A1 (fr) * 2021-03-22 2022-09-29 华为技术有限公司 Procédé et appareil de transmission de données
US12028926B2 (en) 2022-03-24 2024-07-02 Google Llc Handling an attempt to resume a wireless connection using a base station that supports a different core-network type

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11184808B2 (en) 2017-01-09 2021-11-23 Lg Electronics Inc. Method for interworking between networks in wireless communication system and apparatus thereof
US20180376384A1 (en) * 2017-01-09 2018-12-27 Lg Electronics Inc. Method for interworking between networks in wireless communication system and apparatus thereof
US10524166B2 (en) * 2017-01-09 2019-12-31 Lg Electronics Inc. Method for interworking between networks in wireless communication system and apparatus thereof
CN111757428B (zh) * 2018-05-18 2022-02-18 Oppo广东移动通信有限公司 信息处理方法、网络设备、终端设备
JP2020523807A (ja) * 2018-05-18 2020-08-06 株式会社Ｎｔｔドコモ コアリソースの分配
CN111757428A (zh) * 2018-05-18 2020-10-09 Oppo广东移动通信有限公司 信息处理方法、网络设备、终端设备
CN110519074B (zh) * 2018-05-22 2022-04-12 华为技术有限公司 一种服务区域管理方法及装置
US11252020B2 (en) 2018-05-22 2022-02-15 Huawei Technologies Co., Ltd. Service region management method and apparatus
CN110519074A (zh) * 2018-05-22 2019-11-29 华为技术有限公司 一种服务区域管理方法及装置
WO2020033356A1 (fr) * 2018-08-09 2020-02-13 Google Llc Procédé et équipement utilisateur pour reprendre une connexion sans fil
US11330662B2 (en) 2018-08-09 2022-05-10 Google Llc Handling an attempt to resume a wireless connection using a base station that supports a different core-network type
WO2022199338A1 (fr) * 2021-03-22 2022-09-29 华为技术有限公司 Procédé et appareil de transmission de données
US12028926B2 (en) 2022-03-24 2024-07-02 Google Llc Handling an attempt to resume a wireless connection using a base station that supports a different core-network type

Also Published As

Publication number Publication date
WO2018085713A3 (fr) 2018-06-14

Similar Documents

Publication Publication Date Title
US10880814B2 (en) Apparatuses to authorize and enable/disable enhanced coverage functionality
EP3451553B1 (fr) Mécanismes pour surveiller un canal de commande physique de liaison descendante comportant un espace de recherche commun et un espace de recherche spécifique d'un équipement utilisateur dans un système à formation de faisceau
US11800407B2 (en) Flexible scope of packet filters for reflective quality of service
WO2018085187A1 (fr) Interréseautage entre un réseau central de nouvelle génération et un réseau central en mode paquet évolué
US10979958B2 (en) Systems, methods, and apparatuses for providing and obtaining scheduling information for SIB1-BR during handover
US11115947B2 (en) Vehicle to everything synchronization reference selection and reselection
WO2018085713A2 (fr) Sélection d'accès initial et de mode dans des réseaux d'évolution à long terme (lte) évolués
CN110582121A (zh) 用于ue请求ue策略初始配给或更新的解决方案
US11838839B2 (en) V2X policy and parameters provisioning to user equipment by a policy and control function
WO2018089879A1 (fr) Configuration de mesurage de gestion de ressources radio
US20210297192A1 (en) Enhanced harq feedback for reliable communications
WO2019032532A1 (fr) Nouvelle gestion d'enregistrement radio
WO2018031802A1 (fr) Optimisations de radiomessagerie à base de réseau d'accès radioélectrique
US11375524B2 (en) Time advance adjustment delay for shortened transmission time interval under carrier aggregation or dual connectivity
WO2020048479A1 (fr) Appareil et procédé pour prendre en charge un transfert intercellulaire avant l'arrêt (mbb) dans un réseau d'accès radio de prochaine génération (ng-ran)
EP3646637B1 (fr) Gestion améliorée d'expiration de temporisateur pour csfb mt
EP3834484A1 (fr) Procédés pour améliorer la gestion de transfert de session d'unité de données de protocole dans un réseau d'accès radio de prochaine génération
EP3462770A1 (fr) Procédés et appareil pour de multiples associations tnl entre ran et amf pour des déploiements virtualisés
US20190044810A1 (en) Channel whitelist and flexible frame design for enhanced machine-type communications systems in unlicensed spectrum
WO2018063943A1 (fr) Configuration de mesure de liaison montante (ul)
US20190372690A1 (en) User equipment hysteresis for signal blockage detection

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17801195

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17801195

Country of ref document: EP

Kind code of ref document: A2