WO2018085727A1 - Bidiffusion d'informations à un équipement utilisateur d'un réseau de télécommunication sans fil - Google Patents

Bidiffusion d'informations à un équipement utilisateur d'un réseau de télécommunication sans fil Download PDF

Info

Publication number
WO2018085727A1
WO2018085727A1 PCT/US2017/060055 US2017060055W WO2018085727A1 WO 2018085727 A1 WO2018085727 A1 WO 2018085727A1 US 2017060055 W US2017060055 W US 2017060055W WO 2018085727 A1 WO2018085727 A1 WO 2018085727A1
Authority
WO
WIPO (PCT)
Prior art keywords
user data
copy
node
ran node
redundant copies
Prior art date
Application number
PCT/US2017/060055
Other languages
English (en)
Inventor
Candy YIU
Kyeongin Jeong
Yujian Zhang
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
Priority to DE112017005578.4T priority Critical patent/DE112017005578T5/de
Publication of WO2018085727A1 publication Critical patent/WO2018085727A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/026—Multicasting of data during hand-off

Definitions

  • Wireless telecommunication networks may include User Equipment (UE), Radio Access Networks (RANs), and a core network.
  • a UE may include a wireless device (e.g., smartphone, tablet computers, laptop computers, etc.) that communicates with wireless access nodes of the RANs (e.g., a base station, Wi-Fi access point, etc.).
  • the UE may connect to the wireless telecommunication network by communicating with a wireless access node and registering with the core network.
  • a connection between the UE and the wireless access node may be created by the network allocating certain wireless resources to the UE.
  • the wireless resources may include one or more carriers (e.g., a main carrier and one or more subcarriers) corresponding to one or more radio frequency bands.
  • the UE and the wireless access node may use beamforming to implement the carriers with directional specificity (referred to herein as a "beam") such that multiple beams are used to enable communications between the UE and wireless access node.
  • Fig. 1 illustrates an architecture of a system of a network in accordance with some embodiments
  • Fig. 2 is a flowchart of an example process for supporting bi-casting services in a wireless telecommunication network
  • Fig. 3 is a sequence flow diagram of an example for determining the bi-casting capabilities of a User Equipment (UE);
  • Fig. 4 is a sequence flow diagram of an example for configuring a UE for bi-casting;
  • Fig. 5 is a sequence flow diagram of an example for transitioning from bi-casting to unicasting;
  • UE User Equipment
  • Figs. 6-7 are sequence flow diagrams of an example for implementing bi-casting during a HO procedure
  • Fig. 8 illustrates example components of a device in accordance with some embodiments
  • Fig. 9 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • Fig. 10 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.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • a HO procedure may include transferring a UE from one access node (referred to herein as a "source node") to another access node (referred to herein as a "target node").
  • An access node as described herein, may include a small cell device, enhanced NodeB (eNB), next Generation NodeB (gNB), etc.
  • the UE may be accessing a network service (e.g., a voice call, streaming video, etc.) that involves user plane data being provided to the UE from the source node.
  • a network service e.g., a voice call, streaming video, etc.
  • part of the HO procedure may include determining how the ongoing user plane data is to be provided to the UE (e.g., which user plane data will be provided by the source and target nodes).
  • the network may implement a unicasting service, which may include identifying the user plane data to be provided during the HO procedure and determining which node is to communicate which portions of the data to the UE, such that only one copy of the identified user plane data is sent to the UE by a combination of the source node and the target node.
  • the network may implement a bi-casting service that may include redundant copies of the identified user plan data being sent by each of the source node and the target node.
  • a benefit of sending redundant copies may include increasing the reliability with which information is successfully transmitted to a UE during a HO procedure.
  • Bi-casting may be applied to scenarios in which a UE is capable of supporting multiple beams.
  • a beam may include one or more carriers (e.g., a main carrier and one or more subcarriers) that have been designated, allocated, or otherwise set aside, for communications between a UE and an access node (e.g., small cell, enhanced NodeB (eNB), next Generation NodeB (gNB), etc.) of a wireless telecommunication network.
  • the access node may use signal processing techniques, such as beamforming, to implement wireless resources with directional specificity.
  • a UE capable of receiving bi-casted information may be capable of maintaining multiple, simultaneous beams (which may correspond to the same or distinct access nodes).
  • unicasting may be applied to UEs capable of only supporting one beam.
  • a UE may indicate whether the UE is able to support unicasting and/or bi-casting.
  • the access node may setup a connection (with the UE) that uses only a single beam to communicate information to the UE.
  • the access node may determine whether bi-casting should be enabled for the UE, which may involve a variety of factors, such as device type of the UE, the data being sent to the UE, services being provided to the UE, the availability of wireless resources, a level of congestion, etc.
  • the access node may use unicasting to communicate information to the UE.
  • the access node may cause bi-casting to be used to communicate information to the UE.
  • the bi-casting may be performed by the access node and/or one or more other access nodes. Additionally, in some embodiments, bi-casting previously enabled for a particular UE may later be disabled by the access node, in which case the access node may being communicating with the UE via unicasting.
  • bi-casting services may be enabled for a particular network event, such as a handover (HO) procedure.
  • a handover (HO) procedure For example, an access node (e.g., a source node) may determine that a particular UE is to be handed over to another access node (e.g., a target node).
  • the source node may determine whether to enable bi-casting for the handover procedure, such that data sent from the network to the UE during the handover procedure, may be sent from both the source node and the target node.
  • the source node may send a request to the target node that bi-casting has been enabled for the HO procedure, and the target node may, in response, accept or reject the request.
  • unicasting may be used to perform the HO procedure, such that information is only sent to the UE by the source node or the target node.
  • the HO procedure may be performed using bi- casting such that duplicate copies of the information are sent by each access node.
  • bi-casting services may also, or alternatively, be requested by the target node and accepted/rejected by the source node.
  • the copies of information sent by both access nodes may be encrypted by only the source node.
  • the copy of the information sent by the source node may be encrypted by the source node, and the copy of the information sent by the target node may be encrypted by the target node.
  • an access node may include a base station, e B, g B, Next Radio
  • an access node may correspond to a cell or coverage area of the network that includes multiple small cell devices, one or more of which may function as a Transition and Reception Points (TRP) for the access node.
  • TRP Transition and Reception Points
  • a connection between a UE and an access node may include one or more beams between the UE and TRPs managed or controlled by the access node.
  • all of the TRPs of the access node may correspond to one network cell. In other embodiments, different TRPs of the access node may correspond to different network cells.
  • FIG. 1 illustrates an architecture of a system 100 of a network in accordance with some embodiments.
  • the system 100 is shown to include UE 101 and a UE 102.
  • the UEs 101 and 102 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.
  • smartphones e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks
  • 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 101 and 102 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to- machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • 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 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110—
  • the RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 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 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 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 102 is shown to be configured to access an access point (AP) 106 via connection
  • AP access point
  • the connection 107 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 106 would comprise a wireless fidelity (Wi-Fi®) router.
  • Wi-Fi® wireless fidelity
  • the AP 106 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 110 can include one or more access nodes that enable the connections 103 and
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, 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 112.
  • BSs base stations
  • NodeBs 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 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, 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),
  • any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 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 101 and 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 111 and 112 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink
  • OFDM Orthogonal Frequency-Division Multiplexing
  • OFDM 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 111 and 112 to the UEs 101 and 102, 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 may carry user data and higher-layer signaling to the UEs 101 and 102.
  • 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 101 and 102 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 111 and 112 based on channel quality information fed back from any of the UEs 101 and 102.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101 and 102.
  • 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 110 is shown to be communicatively coupled to a core network (CN) 120— via an SI interface 113.
  • the CN 120 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 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.
  • S-GW serving gateway
  • MME SI -mobility management entity
  • the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124.
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter- 3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the EPC network 123 and external networks such as a network including the application server 130 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the application server 130 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 123 is shown to be communicatively coupled to an application server 130 via an IP communications interface 125.
  • the application server 130 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 101 and 102 via the CN 120.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Connectivity Access Network
  • HPLMN Home PCRF
  • V-PCRF Visited PCRF
  • VPN Visited Public Land Mobile Network
  • the PCRF 126 may be communicatively coupled to the application server 130 via the P-GW 123.
  • the application server 130 may signal the PCRF 126 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • QoS Quality of Service
  • the PCRF 126 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 130.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • system 100 may include additional devices and/or networks; fewer devices and/or networks; different devices and/or networks; or differently arranged devices and/or networks than illustrated in Fig. 1.
  • environment 100 may include devices that facilitate or enable communication between various components shown in environment 100, such as routers, modems, gateways, switches, hubs, etc.
  • one or more of the devices of system 100 may perform one or more functions described as being performed by another one or more of the devices of system 100.
  • the devices of system 100 may interconnect with each other and/or other devices via wired connections, wireless connections, or a combination of wired and wireless connections.
  • one or more devices of system 100 may be physically integrated in, and/or may be physically attached to, one or more other devices of system 100.
  • direct connections may be shown between certain devices in Fig. 1, some of said devices may, in practice, communicate with each other via one or more additional devices and/or networks.
  • Fig. 2 is a flowchart of example process 200 for supporting bi-casting services in a wireless telecommunication network.
  • Process 200 may be implemented by an access node (e.g., macro RAN node 1 1 1, LP RAN node 1 12, AP 106, eNB, gNB, small cell device, etc.).
  • an access node e.g., macro RAN node 1 1 1, LP RAN node 1 12, AP 106, eNB, gNB, small cell device, etc.
  • one or more of the operations described in Fig. 2 may be performed in whole, or in part, by another device, such as MME 121.
  • Fig. 2 is described below with reference to Figs. 3 and 4.
  • process 200 may include receiving capability information regarding unicast and bi-cast capabilities of UE 101 (block 210).
  • an access node may send a request to UE 101 for capability information, and in response to the request, receive capability information from UE 101.
  • the request from the access node and/or the response from UE 101 may each include RRC messages.
  • the access node may receive the capability information as part of an initial registration procedure involving UE 101.
  • Fig. 3 is a sequence flow diagram of an example for determining the bi-casting capabilities of UE 101, such as is performed in block 210.
  • the example of Fig. 3 may include UE 101 and an access node.
  • the example of Fig. 3 is provided as a non-limiting example.
  • the example of Fig. 3 may include fewer, additional, alternative, operations or functions. Additionally, one or more of the operations or functions of Fig. 3 may be performed by fewer, additional, or alternative devices, which may include one or more of the devices described above with reference to Fig. 1.
  • UE 101 may be in an RRC connected mode of operation with respect to the access node (block 310).
  • the access node may send a message to UE 101 requesting information describing the capabilities of UE 101 (line 320).
  • the message may include a UE Capability Enquiry (e.g., a ueCapabilityEnquiry message) that requests information indicating whether UE 101 is capable of supporting unicast and/or bi-cast communications.
  • UE 101 may provide the access node with the requested information (line 330).
  • UE 101 may provide the information as part of a UE Capability Information message (e.g., a ueCapabiiltylnformation).
  • process 200 may include determining whether to bi-cast or unicast to UE 101 (block 220). For instance, the access node may determine whether to bi-cast or unicast to UE 101 based on the capabilities of UE 101. When UE 101 is capable of supporting bi- casting services, the access node may determine to enable bi-casting for UE 101. By contrast, when UE 101 is not capable of supporting bi-casting services, the access node may determine that bi-casting is not to be enabled for UE 101. In some embodiments, the access node may determine whether to enable bi-casting for UE 101 based on one or more additional (or alternative factors).
  • Such factors may include an availability of wireless resources of the access node and/or one or more other access nodes (e.g., another base station, small cell device, etc., to participate in the bi-casting of information to UE 101).
  • Other factors may include one or more network conditions, such as a quantity of active UEs 101 in a coverage area of the network, a level of congestion, signal interference, etc.
  • Such factors may include a device type corresponding to UE 101 (such as whether UE 101 is capable of, or configured for, Ultra-Reliable Low Latency Communication (URLLC)), a quantity of UEs 101 already receiving bi-casting services in one or more cells, a type of information and/or service to be provided to, or otherwise associated with, UE 101 (e.g., high- value information, time-sensitive information, information with a particular QoS, etc.).
  • a device type corresponding to UE 101 such as whether UE 101 is capable of, or configured for, Ultra-Reliable Low Latency Communication (URLLC)
  • URLLC Ultra-Reliable Low Latency Communication
  • a type of information and/or service to be provided to, or otherwise associated with, UE 101 e.g., high- value information, time-sensitive information, information with a particular QoS, etc.
  • the access node may determine whether to enable bi-casting services based on whether it is desirable (and/or how desirable (e.g., above a desirability threshold) to ensure/increase a level of reliability associated with providing a service and/or information to a particular UE 101 and/or type of UE 101.
  • process 200 may include unicasting information to UE 101 (block 240). For example, when UE 101 is not capable of supporting bi-casting services, the access node may cause information to be sent, from the network to UE 101, via unicasting. The beam used for unicasting may be setup and configured by the access node.
  • process 200 may include configuring UE 101 and/or the network for bi- casting (block 250).
  • the access node may communicate configuration information, regarding the bi-casting service, to UE 101.
  • the configuration information may indicate how (e.g., which carriers, bands, access device, etc.) UE 101 is to receive the bi-casting services.
  • the configuration information may describe one or more Signaling Radio Bearers (SRB) and/or Dedicated Radio Bearers (DRB) to be associated with the bi-casting service.
  • SRB Signaling Radio Bearers
  • DRB Dedicated Radio Bearers
  • Fig. 4 is a sequence flow diagram of an example for configuring a UE for bi-casting.
  • the example of Fig. 4 may include UE 101 and an access node.
  • the example of Fig. 4 is provided as a non-limiting example.
  • the example of Fig. 4 may include fewer, additional, alternative, operations or functions. Additionally, one or more of the operations or functions of Fig. 4 may be performed by fewer, additional, or alternative devices, which may include one or more of the devices described above with reference to Fig. 1.
  • UE 101 may be in an RRC connected mode with respect to the access node (block 410).
  • the access node may determine whether to enable bi-casting for UE 101 (block 420).
  • the access node may be configured to enable bi-casting for all UEs 101, such that the access node may not determine whether to enable bi-casting.
  • the access node may send configuration information to UE 101 in order to, for example, notify UE 101 of the bi-casting service and/or to enable UE 101 receive the bi-casting service (line 430).
  • the information may be sent as a RRC message, such as an RRC Connection Reconfiguration message).
  • UE 101 may determine whether to accept the bi-casting service. Additionally, or alternatively, UE 101 may respond to the access node by indicating that the configuration information has been received and/or that UE 101 accepts, or agrees to receive, the bi-casting service (line 440). In some embodiments, UE 101 may send the response in an RRC message, such as an RRC Connection Reconfiguration Complete message.
  • RRC message such as an RRC Connection Reconfiguration Complete message.
  • process 200 may include causing information to be bi-casted to
  • the access node may respond to the message from UE 101 by causing information to be bi-casted to UE 101.
  • the access node may setup and support all of the beams used to bi-cast to UE 101.
  • some or all of the beams used to bi-cast to UE 101 may be setup and supported by one or more other access nodes (e.g., e Bs, g Bs, small cell devices, APs 106, etc.).
  • the access node may provide instructions and configuration information for the other access nodes setup and support the beams and bi-cast information to UE 101.
  • the access node may provide copies of the information and/or indicate which information (e.g., the identity and location of the information) to be bi-casted to UE 101.
  • Fig. 5 is a sequence flow diagram of an example for configuring a UE for bi-casting.
  • the example of Fig. 5 may include UE 101 and an access node.
  • the example of Fig. 5 is provided as a non-limiting example.
  • the example of Fig. 5 may include fewer, additional, alternative, operations or functions. Additionally, one or more of the operations or functions of Fig. 5 may be performed by fewer, additional, or alternative devices, which may include one or more of the devices described above with reference to Fig. 1.
  • UE 101 may be in an RRC connected mode and communicating with one or more access nodes via bi-casting (block 510).
  • the access node may determine whether to continue bi-casting information to UE 101 (block 520).
  • the access node may determine whether to continue bi-casting information based on one or more of the factors that the access node may have used to begin bi-casting information to UE 101. As mentioned above, such factors may include congestions levels, an availability of wireless resources, a quantity of UEs 101 located in a coverage area of the access node, etc.
  • access node may also, or alternatively, determine whether to continue bi-casting information based on expiry of a timer, whether a procedure (e.g., a HO procedure) for which the bi-casting was enabled has been completed, etc.
  • a procedure e.g., a HO procedure
  • the access node may refrain from changing the way in which the current bi-casting service is being provided.
  • the access node may communicate a message to UE 101 indicating that the bi-casting service is to be terminated or discontinued and/or that the access node is to transition into unicasting to UE 101 (line 530).
  • the access node may notify UE 101 via an RRC message.
  • the access node may provide UE with configuration information for the unicast service, which may include an indication of the carriers, frequencies, and/or devices to be used to unicast information to UE 101.
  • UE 101 may communicate an acknowledgement message to the access node (line 540), and upon receiving the acknowledgement message, the access node may begin communicating with the UE via the unicast service (block 550).
  • the acknowledgement may include an RRC message, such as an RRCReconfigurationComplete Message.
  • Figs. 6-7 are sequence flow diagrams of an example for implementing bi-casting during a HO procedure.
  • the example of Figs. 6-7 may include UE 101, a source access node, and a target access node (referred to as "source node” and "target node,” respectively).
  • the example of Figs. 6-7 is provided as a non-limiting example.
  • the example of Figs. 6-7 may include fewer, additional, alternative, operations or functions.
  • one or more of the operations or functions of Figs. 6-7 may be performed by fewer, additional, or alternative devices, which may include one or more of the devices described above with reference to Fig. 1.
  • UE 101 may be in an RRC connected mode with respect to the source node (block 610).
  • the source node may send a request to UE 101 for UE capability information, which may include an indication of whether UE 101 is capable of receiving information from the network via a bi-cast service, and in response, UE 101 may provide the source node with the capability information (line 620).
  • UE 101 may periodically take measurements of RAN conditions and communicate a measurement report to the source node (line 630).
  • the source node may initiate a HO procedure for UE 101 (block 640).
  • the HO procedure may be an inter-cell HO procedure or an intra-cell HO procedure. For purposes of describing the example of Figs. 6-7, assume that the HO procedure is an inter-cell HO. However, the techniques described herein may also be applied to intra-cell HO procedures.
  • the source node may determine whether to enable bi-casting for the HO procedure (block 650). As described above, the source node may make this determination based on one or more factors, such as whether UE 101 is capable of supporting bi-casting services, wireless resource availability, network conditions pertaining to the source and/or target nodes, a device type of UE 101 (e.g., a URLLC device), a type of information to be sent to UE 101 during the HO procedure (e.g., time-sensitive information), a service being provided to UE 101 (e.g., a call service), etc.
  • a device type of UE 101 e.g., a URLLC device
  • time-sensitive information e.g., time-sensitive information
  • a service being provided to UE 101 e.g., a call service
  • the source node may generate and communicate a HO request message to the target node (line 660).
  • the HO request message may include a request for a bi-casting service to be provided to UE 101 during the HO procedure.
  • the HO request message may also, or alternatively, include an indication that the source node has determined to enable bi- casting services for UE 101.
  • the target node may receive the message and determine whether to support the bi-casting service request or indicated by the source node (block 670).
  • the target node may make this determination based on one or more factors, such as network conditions, availability of network resources, device type of UE 101, a service type being provided to UE, data type corresponding to the information to be bi-casted, etc.).
  • the request from the source node may include synchronization information, whereby the source node and the target node may bi-cast information to UE 101 in a synchronized manner (e.g., at the same time, over the same time period, etc.).
  • some or all of the information upon which the source node may make this determination may be monitored and collected by the target node and/or received from the source node (in the HO request message or another message).
  • the target node may respond to the source node with an indication of whether the target node is to support the bi-casting service (block 670). As shown, this indication may part of an acknowledgement message corresponding to the previous HO request message. For purposes of describing Figs. 6-7, assume that the target node determines that bi-casting is to be provided to UE 101.
  • the source node may send a message to the target node to indicate information for the HO procedure, such as an uplink Packet Data Convergence Protocol (PDCP) SN receiver status and a downlink PDCP SN transmitter status of E-UTRAN Radio Access Bearers (E-RABs) for which PDCP status preservation may apply (e.g., for Radio Link Control (RLC) Acknowledged Mode (AM)).
  • PDCP Packet Data Convergence Protocol
  • E-RABs E-UTRAN Radio Access Bearers
  • RLC Radio Link Control
  • AM Access Mode
  • the source node may provide a copy of the information to be bi-casted to UE 101 during the HO procedure (line 720). As shown, the copy of the bi-cast information may or may not be encrypted by the source node. The significance of whether the source node encrypts the bi-cast information is described in detail below with reference to block 780.
  • the source node may also, or alternatively, communicate HO configuration information to UE 101 (line 730).
  • This may include an RRC Connection Reconfiguration message, which may include a notification of bi-casting being enabled for the HO procedure and/or configuration information to enable UE 101 to participate in the bi-casting service (e.g., to enable UE 101 to receive redundant copies of information from the source and target nodes).
  • the source node may also, or alternatively, communicate a copy of the information being bi-casted to UE 101 (block 740).
  • the source node may provide this information at another time during the HO procedure. For example, UE 101 may maintain a beam established between UE 101 the source node even after the HO procedure is complete, and the source node may use the beam to send a copy of the bi-casted data to UE 101. Once the data is received, UE 101 and the source node may no longer maintain the connection.
  • the source node may communicate the copy of the information to UE 101 at another time. For example, the source node may communicate the information to the UE 101 at the same time as the target node (see, e.g., line 790).
  • the source node may provide the target node with timing and other types of configuration information for the bi- cast procedure, and each node (the source node and the target node) may communicate copies of the information to UE 101 in accordance with the timing and configuration information.
  • the source node may provide the timing and other configuration information in the HO request (see, line 660), the sequence number (SN) status transfer (see, line 710), with the copy of the bi-cast data (see, line 720), or at another time.
  • the timing and configuration information received by the target node may be used by the target node to determine whether to participate in the bi-cast procedure (see, block 670).
  • UE 101 may engage in and complete a Random Access Procedure involving the target node (line 750). After completing the Random Access Procedure, UE 101 may send a message to the target node, indicating that the HO procedure has been completed (line 670). As shown, this may include an RRC Connection Reconfiguration Complete message. As shown, the target node may (optionally) encrypt the copy of bi-cast information previously received from the source node (block 780).
  • the copy of bi-cast information provided to the target node may or may not have already been encrypted by the source node.
  • the target node may communicate the information to UE 101 without having to re-encrypt the information.
  • UE 101 may only use one encryption key (e.g., an RRC encryption key, user plane key, etc.) to decrypt both copies of the information.
  • the source node does not encrypt the copy of the bi-cast information sent to the target node (line 720)
  • the target node may encrypt the information before communicating it to UE 101 (line 790).
  • UE 101 since each copy of the bi-casted information is encrypted by different access nodes, UE 101 may use a different encryption key to decrypt each copy of bi-casted information.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide thedescribed functionality.
  • ASIC Application Specific Integrated Circuit
  • 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.
  • Fig. 8 illustrates example components of a device 800 in accordance with some embodiments.
  • the device 800 may include application circuitry 802, baseband circuitry 804, Radio Frequency (RF) circuitry 806, front-end module (FEM) circuitry 808, one or more antennas 810, and power management circuitry (PMC) 812 coupled together at least as shown.
  • the components of the illustrated device 800 may be included in a UE or a RAN node.
  • the device 800 may include less elements (e.g., a RAN node may not utilize application circuitry 802, and instead include a processor/controller to process IP data received from an EPC).
  • the device 800 may include 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 802 may include one or more application processors.
  • the application circuitry 802 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 800.
  • processors of application circuitry 802 may process IP data packets received from an EPC.
  • the baseband circuitry 804 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 804 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806.
  • Baseband processing circuity 804 may interface with the application circuitry 802 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806.
  • the baseband circuitry 804 may include a third generation (3G) baseband processor 804 A, a fourth generation (4G) baseband processor 804B, a fifth generation (5G) baseband processor 804C, or other baseband processor(s) 804D 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 804 e.g., one or more of baseband processors 804 A-D
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • baseband processors 804 A-D may be included in modules stored in the memory 804G and executed via a Central Processing Unit (CPU) 804E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • signal modulation/demodulation e.g., a codec
  • encoding/decoding e.g., a codec
  • radio frequency shifting e.g., radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 804 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 804 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 804 may include one or more audio digital signal processor(s) (DSP) 804F.
  • the audio DSP(s) 804F 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 804 and the application circuitry 802 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 804 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 804 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks WMA ), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMA wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 806 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 806 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 806 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 804.
  • RF circuitry 806 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 804 and provide RF output signals to the FEM circuitry 808 for transmission.
  • the receive signal path of the RF circuitry 806 may include mixer circuitry 806a, amplifier circuitry 806b and filter circuitry 806c.
  • the transmit signal path of the RF circuitry 806 may include filter circuitry 806c and mixer circuitry 806a.
  • RF circuitry 806 may also include synthesizer circuitry 806d for synthesizing a frequency for use by the mixer circuitry 806a of the receive signal path and the transmit signal path.
  • the mixer circuitry 806a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806d.
  • the amplifier circuitry 806b may be configured to amplify the down-converted signals and the filter circuitry 806c 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 804 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 806a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 806a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 806d to generate RF output signals for the FEM circuitry 808.
  • the baseband signals may be provided by the baseband circuitry 804 and may be filtered by filter circuitry 806c.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a 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 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 804 may include a digital baseband interface to communicate with the RF circuitry 806.
  • 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 806d 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 806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 806d may be configured to synthesize an output frequency for use by the mixer circuitry 806a of the RF circuitry 806 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 806d 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 804 or the applications processor 802 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 802.
  • Synthesizer circuitry 806d of the RF circuitry 806 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
  • 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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
  • synthesizer circuitry 806d 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 806 may include an IQ/polar converter.
  • FEM circuitry 808 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 806 for further processing.
  • FEM circuitry 808 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 806 for transmission by one or more of the one or more antennas 810.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 806, solely in the FEM 808, or in both the RF circuitry 806 and the FEM 808.
  • the FEM circuitry 808 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 806).
  • the transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 810).
  • PA power amplifier
  • the PMC 812 may manage power provided to the baseband circuitry 804.
  • the PMC 812 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 812 may often be included when the device 800 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 812 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • Fig. 8 shows the PMC 812 coupled only with the baseband circuitry 804.
  • the PMC 812 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 802, RF circuitry 806, or FEM 808.
  • the PMC 812 may control, or otherwise be part of, various power saving mechanisms of the device 800. For example, if the device 800 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 800 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the device 800 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.
  • DRX Discontinuous Reception Mode
  • the device 800 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 800 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.
  • 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 802 and processors of the baseband circuitry 804 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 804 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 804 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.
  • Fig. 9 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 804 of Fig. 8 may comprise processors 904A-904E and a memory 904G utilized by said processors.
  • Each of the processors 904A-904E may include a memory interface, 804A-804E, respectively, to send/receive data to/from the memory 904G.
  • the baseband circuitry 904 may further include one or more interfaces to
  • a memory interface 912 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 804
  • an application circuitry interface 914 e.g., an interface to send/receive data to/from the application circuitry 802 of Fig. 8
  • an RF circuitry interface 916 e.g., an interface to send/receive data to/from RF circuitry 806 of Fig. 8
  • a wireless hardware connectivity interface 918 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 e.g., Wi-Fi® components
  • power management interface 920 e.g., an interface to send/receive power or control signals to/from the PMC 812.
  • Fig. 10 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.
  • Fig. 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory/storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040.
  • a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/ sub-slices to utilize the hardware resources 1000
  • the processors 1010 e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof
  • the processors 1010 e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex
  • the memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1020 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory
  • DRAM dynamic random-access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 1030 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 via a network 1008.
  • the communication resources 1030 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 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein.
  • the instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor's cache memory), the memory/ storage devices 1020, or any suitable combination thereof.
  • any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory/storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.
  • apparatus of a Radio Access Network (RAN) node may comprise: a first interface to application circuitry; a second interface to radio frequency (RF) circuitry; and one or more processors that are controlled to: receive, via the first interface, user data for a User Equipment (UE) connected to the base station; determine, prior to causing the user data to be transmitted to the UE via the RF circuitry, to initiate a handover (HO) procedure involving the UE and a target RAN node; determine to cause redundant copies of the user data to be provided to the UE as part of the HO procedure; cause a first copy of the user data to be sent to the UE via the RF circuitry; and cause a second copy of the user data to be sent to the UE via the target RAN node.
  • UE User Equipment
  • HO handover
  • the one or more processors are controlled to: communicate, with the UE, to verify that the UE is capable of receiving the redundant copies of the user data from distinct RAN nodes.
  • the one or more processors are controlled to: communicate, with the target RAN node, to verify that the target RAN node is capable of providing the second copy of the user data to the UE.
  • example 4 the subject matter of example 1, or any of the examples herein, wherein, in response to determining to cause the redundant copies of the user data to be provided to the UE, the one or more processors are further controlled to: notify the UE that the redundant copies of the user data are to be provided to the UE.
  • the one or more processors are controlled to: determine wireless resources currently available for communicating the first copy of the user data to the UE.
  • example 6 the subject matter of example 1, or any of the examples herein, wherein: the first copy of the user data is encrypted by the RAN node; and the second copy of the user data is encrypted by the target RAN.
  • example 7 the subject matter of example 1, or any of the examples herein, wherein the first copy of the user data and the second copy of the user data are encrypted by the RAN node.
  • example 8 the subject matter of example 1, or any of the examples herein, wherein the one or more processors are further controlled to: communicate a request for capability information to the UE; receive, in response to the request, an indication of whether the UE is capable of simultaneously receiving redundant copies of user data from distinct RAN nodes; and determine, based on the indication, to cause the redundant copies of the user data to be simultaneously provided to the UE.
  • an apparatus of a Radio Access Network (RAN) node may comprise: an interface to radio frequency (RF) circuitry; and one or more processors that are controlled to: receive, from a source RAN node, a request to engage in a handover (HO) procedure involving a
  • RF radio frequency
  • UE User Equipment
  • the request including an inquiry about whether the RAN node is capable of participating in a bi-cast procedure that includes the RAN node and the source RAN transmitting redundant copies of user data to the UE; process the request to determine that the RAN is capable of participating in the bi-cast procedure and, in response to the request, confirm to the source RAN node that the RAN node is capable of participating in the bi-cast procedure; receive, from the source RAN node, a copy of the user data corresponding to the bi-cast procedure; and send, via the RF circuitry, the copy of the user data to the UE in accordance with the bi-cast procedure
  • UE User Equipment
  • the one or more processors are further controlled to: determine that the UE has successfully received the copy of the user data via a first connection between the RAN and the UE; establish a second connection with the UE; terminate the first connection with the UE; and communicate with the UE using the different connection.
  • example 12 the subject matter of example 1 or 9, or any of the examples herein, wherein the copy of the user data transmitted to the UE is encrypted by the RAN node.
  • apparatus of a User Equipment comprising: an interface to radio frequency (RF) circuitry; and one or more processors that are controlled to: receive, as part of a handover (HO) procedure involving a source Radio Access Network (RAN) node and a target RAN node, an indication that the HO procedure is to include the source RAN node and the target RAN node providing redundant copies of user data to the UE as part of the HO procedure; establish, in accordance with the HO procedure, a connection with the target RAN node; receive, via the interface, a first copy of the user data from the source RAN node and a second copy of the user data from the target RAN node; and merge the first copy of the user data and the second copy of the user data to create a single copy of user data.
  • HO handover
  • RAN Radio Access Network
  • example 14 the subject matter of example 13, or any of the examples herein, wherein the one or more processors are further controlled to: receive a request for UE capability information from the source RAN node; and communicate, in response to the request for UE capability information an indication that the UE is capable of receiving redundant copies of user data from distinct RAN nodes as part of a HO procedure.
  • example 15 the subject matter of example 13, or any of the examples herein, wherein the first copy of the user data and the second copy of the user data are each encrypted by the source RAN node.
  • example 16 the subject matter of example 13, or any of the examples herein, wherein the first copy of the user data is encrypted by the source RAN node and the second copy of the user data in encrypted by the target RAN node.
  • computer-readable medium containing program may comprise instructions to cause one or more processors, associated with User Equipment (UE), to: receive user data for a User Equipment (UE) connected to the base station; determine, prior to causing the user data to be transmitted to the UE, to initiate a handover (HO) procedure involving the UE and a target RAN node; determine to cause redundant copies of the user data to be provided to the UE as part of the HO procedure; cause a first copy of the user data to be sent to the UE; and cause a second copy of the user data to be sent to the UE via the target RAN node
  • UE User Equipment
  • the one or more processors are to: communicate, with the UE, to verify that the UE is capable of receiving the redundant copies of the user data from distinct RAN nodes.
  • the one or more processors are to: communicate, with the target RAN node, to verify that the target RAN node is capable of providing the second copy of the user data to the UE.
  • the one or more processors are further to: notify the UE that the redundant copies of the user data are to be provided to the UE.
  • the one or more processors are to: determine wireless resources currently available for communicating the first copy of the user data to the UE.
  • example 22 the subject matter of example 17, or any of the examples herein, wherein: the first copy of the user data is encrypted by the RAN node; and the second copy of the user data is encrypted by the target RAN.
  • example 24 the subject matter of example 17, or any of the examples herein, wherein the first copy of the user data and the second copy of the user data are encrypted by the RAN node.
  • processors are further to:
  • determining to cause redundant copies of the user data to be provided to the UE includes:
  • determining to cause redundant copies of the user data to be provided to the UE includes:
  • example 28 the subject matter of example 25, or any of the examples herein, further comprising: in response to determining to cause the redundant copies of the user data to be provided to the UE, notifying the UE that the redundant copies of the user data are to be provided to the UE.
  • determining to cause redundant copies of the user data to be provided to the UE includes:
  • example 30 the subject matter of example 25, or any of the examples herein, wherein: the first copy of the user data is encrypted by the RAN node; and the second copy of the user data is encrypted by the target RAN.
  • example 31 the subject matter of example 25, or any of the examples herein, wherein the first copy of the user data and the second copy of the user data are encrypted by the RAN node.
  • example 32 the subject matter of example 25, or any of the examples herein, further comprising: communicating a request for capability information to the UE; receiving, in response to the request, an indication of whether the UE is capable of simultaneously receiving redundant copies of user data from distinct RAN nodes; and determining, based on the indication, to cause the redundant copies of the user data to be simultaneously provided to the UE.
  • an apparatus of a Radio Access Network (RAN) node may comprise: means for receiving user data for a User Equipment (UE) connected to the base station; means for determining, prior to causing the user data to be transmitted to the UE, to initiate a handover (HO) procedure involving the UE and a target RAN node; means for determining to cause redundant copies of the user data to be provided to the UE as part of the HO procedure; means for causing a first copy of the user data to be sent to the UE; and means for causing a second copy of the user data to be sent to the UE via the target RAN node
  • UE User Equipment
  • HO handover
  • example 34 the subject matter of example 33, or any of the examples herein, wherein the means for determining to cause redundant copies of the user data to be provided to the UE includes: means for communicating, with the target RAN node, to verify that the target RAN node is capable of providing the second copy of the user data to the UE.
  • example 35 the subject matter of example 33, or any of the examples herein, wherein the means for determining to cause redundant copies of the user data to be provided to the UE includes: in response to determining to cause the redundant copies of the user data to be provided to the UE, means for notifying the UE that the redundant copies of the user data are to be provided to the UE.
  • example 36 the subject matter of example 33, or any of the examples herein, wherein the means for determining to cause redundant copies of the user data to be provided to the UE includes: means for determining wireless resources currently available for communicating the first copy of the user data to the UE.
  • example 37 the subject matter of example 33, or any of the examples herein, wherein: the first copy of the user data is encrypted by the RAN node; and the second copy of the user data is encrypted by the target RAN.
  • example 38 the subject matter of example 33, or any of the examples herein, wherein the first copy of the user data and the second copy of the user data are encrypted by the RAN node.
  • example 39 the subject matter of example 33, or any of the examples herein, further comprising: means for communicating a request for capability information to the UE; means for receiving, in response to the request, an indication of whether the UE is capable of

Landscapes

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

Abstract

Les techniques décrites dans la présente invention peuvent servir à bidiffuser des informations à un équipement utilisateur (UE). Un nœud source (par exemple une station de base) peut déterminer qu'un UE doit faire l'objet d'un transfert intercellulaire à un nœud cible. Le nœud source peut également déterminer que la procédure de transfert intercellulaire (HO) doit comprendre une procédure de bidiffusion, de sorte que des copies redondantes de données d'utilisateur actuellement stockées par le nœud source doivent être transmises à l'UE par les nœuds source et cible. Cette détermination peut être basée sur des facteurs tels que les capacités de l'UE, les capacités du nœud cible et les conditions du réseau (par exemple encombrement, disponibilité des ressources, etc.). Le nœud source peut communiquer à l'UE et au nœud cible des instructions de participation à la procédure de bidiffusion. Sur la base des instructions, les nœuds source et cible peuvent fournir des copies redondantes des données d'utilisateur à l'UE à titre de partie de la procédure HO.
PCT/US2017/060055 2016-11-04 2017-11-03 Bidiffusion d'informations à un équipement utilisateur d'un réseau de télécommunication sans fil WO2018085727A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
DE112017005578.4T DE112017005578T5 (de) 2016-11-04 2017-11-03 Bicasten von informationen zu einer teilnehmervorrichtung eines drahtlosen telekommunikationsnetzwerks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662418133P 2016-11-04 2016-11-04
US62/418,133 2016-11-04

Publications (1)

Publication Number Publication Date
WO2018085727A1 true WO2018085727A1 (fr) 2018-05-11

Family

ID=60484468

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/060055 WO2018085727A1 (fr) 2016-11-04 2017-11-03 Bidiffusion d'informations à un équipement utilisateur d'un réseau de télécommunication sans fil

Country Status (2)

Country Link
DE (1) DE112017005578T5 (fr)
WO (1) WO2018085727A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11570665B2 (en) 2018-06-25 2023-01-31 Huawei Technologies Co., Ltd. Communication method and communications apparatus

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006118540A2 (fr) * 2005-05-04 2006-11-09 Telefonaktiebolaget Lm Ericsson (Publ) Procede et dispositif dans un systeme mobile
EP1928133A1 (fr) * 2006-12-01 2008-06-04 Electronics And Telecommunications Research Institute Procédé de transmission de données par transfert entre des stations de base dans un système de communication sans fil
US8406764B1 (en) * 2006-08-25 2013-03-26 Apple Inc. Bicasting traffic data during a handover
WO2016078699A1 (fr) * 2014-11-18 2016-05-26 Telefonaktiebolaget L M Ericsson (Publ) Flux de données dupliqué sur un dispositif mobile à double sim

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006118540A2 (fr) * 2005-05-04 2006-11-09 Telefonaktiebolaget Lm Ericsson (Publ) Procede et dispositif dans un systeme mobile
US8406764B1 (en) * 2006-08-25 2013-03-26 Apple Inc. Bicasting traffic data during a handover
EP1928133A1 (fr) * 2006-12-01 2008-06-04 Electronics And Telecommunications Research Institute Procédé de transmission de données par transfert entre des stations de base dans un système de communication sans fil
WO2016078699A1 (fr) * 2014-11-18 2016-05-26 Telefonaktiebolaget L M Ericsson (Publ) Flux de données dupliqué sur un dispositif mobile à double sim

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11570665B2 (en) 2018-06-25 2023-01-31 Huawei Technologies Co., Ltd. Communication method and communications apparatus

Also Published As

Publication number Publication date
DE112017005578T5 (de) 2019-08-29

Similar Documents

Publication Publication Date Title
US10771214B2 (en) System and method for uplink power contrl framework
US10986548B2 (en) Enhanced conditional handover
US12101153B2 (en) Group based beam reporting and channel state information reference signal configuration in new radio systems
US10886993B2 (en) Inter-cell beam management
US11240692B2 (en) Measurement design for next radio (NR) and long term evolution (LTE)
US11265091B2 (en) Apparatus and method for RSRP measurement and allocation of downlink transmission resources
US11824814B2 (en) Physical resource block indexing for coexistence of narrow band, carrier aggregation, and wide band user equipment in new radio
US11445564B2 (en) Apparatuses to switch between LTE rat and NR rat during transition from inactive state to active state
US10812169B2 (en) User equipment measurements for new radio
US11284362B2 (en) Synchronization signal block for unlicensed carrier, and listen before talk strategies for initial access
US11082901B2 (en) Signaling of support for network controlled small gap, NCSG, for interruption control
WO2018085374A1 (fr) Informations de système spécifiques à un point d'émission/réception
CN112602374B (zh) 在下一代无线接入网(ng-ran)中支持先接后断(mbb)切换的装置和方法
US20190373497A1 (en) Measurement gap configuration for new radio (nr) systems
US20210243766A1 (en) Bandwidth Part Switching Delay for Uplink Transmission
WO2018144936A1 (fr) Attribution de ressources de liaison montante sur la base de classes de puissance d'équipement utilisateur
WO2018085723A1 (fr) Systèmes et procédés pour optimiser la notification de paramètres de capacité physique dans un réseau de télécommunication
US11902803B2 (en) Physical-layer cell identifier (PCI) configuration and mobility robustness optimization for fifth generation self-organizing networks (5G SON)
US12052597B2 (en) Reference timing for target data measurement in unlicensed spectrum for new radio
WO2018063943A1 (fr) Configuration de mesure de liaison montante (ul)
WO2018085727A1 (fr) Bidiffusion d'informations à un équipement utilisateur d'un réseau de télécommunication sans fil
US12075330B2 (en) Access control
US20240155471A1 (en) Enhancement for SMTC Configuration for New Radio
US20240187916A1 (en) Configured grant enhancement
US20230092295A1 (en) Smtc2-lp based rrm enhancement

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: 17805336

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17805336

Country of ref document: EP

Kind code of ref document: A1