WO2010125460A1 - Systems, methods, and apparatuses for facilitating multicarrier and multicast and broadcast service coordination - Google Patents

Systems, methods, and apparatuses for facilitating multicarrier and multicast and broadcast service coordination Download PDF

Info

Publication number
WO2010125460A1
WO2010125460A1 PCT/IB2010/001005 IB2010001005W WO2010125460A1 WO 2010125460 A1 WO2010125460 A1 WO 2010125460A1 IB 2010001005 W IB2010001005 W IB 2010001005W WO 2010125460 A1 WO2010125460 A1 WO 2010125460A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
terminal
broadcast service
base station
service content
Prior art date
Application number
PCT/IB2010/001005
Other languages
French (fr)
Inventor
Jan Erik Suumaki
Roberto Albanese
Andrea Bacioccola
Zexian Li
Original Assignee
Nokia 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 Nokia Corporation filed Critical Nokia Corporation
Publication of WO2010125460A1 publication Critical patent/WO2010125460A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/30Resource management for broadcast services

Definitions

  • Embodiments of the present invention relate generally to communication technology and, more particularly, relate to systems, methods, and apparatuses for facilitating multicarrier and multicast and broadcast service coordination.
  • Broadband wireless access networks may be deployed on a community-wide, or metropolitan-wide, level and are sometimes referred to as wireless metropolitan area networks (WMANs) as opposed to wireless local area networks (WLANs) that may cover a more localized area, such as a home or business. Accordingly, a broadband wireless access network may allow a user to wirelessly access a network with a terminal throughout the coverage area of the network by accessing the network through one or more base stations that provide wireless access to the network.
  • WMANs wireless metropolitan area networks
  • WLANs wireless local area networks
  • a broadband wireless access network may allow a user to wirelessly access a network with a terminal throughout the coverage area of the network by accessing the network through one or more base stations that provide wireless access to the network.
  • One broadband wireless access network standard being deployed is the Worldwide
  • WiMAX Interoperability for Microwave Access
  • IEEE Institute of Electrical and Electronics Engineers
  • 802.16m version of the standard is in development.
  • 802.16m is being designed to support multicarrier operation such that communication between a terminal and serving base station may occur over multiple radio frequency (RF) carriers, also referred to as carriers.
  • RF radio frequency
  • 802.16 provides support for multicast and broadcast services (MBS).
  • MBS may be used to efficiently transport video and/or audio to multiple user terminals simultaneously and may, for example, be used to transmit an Internet radio broadcast, a television broadcast, and/or the like.
  • Some example embodiments provide terminals configured to provide information about MBS content being received by the terminal to a base station in response to occurrence of an event affecting MBS content received by the terminal.
  • the MBS content may comprise multicast and/or broadcast service content, and as such MBS may be used herein to refer interchangeably to multicast and/or broadcast services.
  • Some example embodiments further provide base stations configured to assign one or more carriers to a terminal based at least in part upon information about MBS content being received by the terminal that is provided to the base station by the terminal.
  • a method which comprises detecting, at a terminal, an occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal over a multicarrier broadband wireless access network.
  • the broadband wireless access network may comprise a Worldwide Interoperability for Microwave Access (WiMAX) network operating in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
  • WiMAX Worldwide Interoperability for Microwave Access
  • IEEE Institute of Electrical and Electronics Engineers 802.16m standards.
  • the method of this embodiment further comprises causing, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the terminal to be provided to a base station providing access to the broadband wireless access network.
  • the information may comprise one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
  • the method of this embodiment additionally comprises receiving, from the base station, an assignment of one or more carriers to the terminal, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
  • the event may comprise a handover of the terminal from a serving base station to a target base station.
  • Causing the information to be provided may comprise causing the information to be provided to the target base station during network re-entry.
  • the method may further comprise receiving an assignment of a paging carrier, wherein the base station assigned the paging carrier based at least in part upon the provided information.
  • a computer program product includes at least one computer-readable storage medium having computer- readable program instructions stored therein.
  • the computer-readable program instructions may include a plurality of program instructions.
  • the program instructions of this embodiment comprise program instructions configured to detect an occurrence of an event affecting one or more of multicast or broadcast service content received by a terminal over a multicarrier broadband wireless access network.
  • the program instructions of this embodiment further comprise program instructions configured to cause, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the terminal to be provided to a base station providing access to the broadband wireless access network.
  • the program instructions of this embodiment also comprise program instructions configured to cause an assignment to the terminal of one or more carriers to be received, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
  • an apparatus comprising at least one processor and at least one memory storing computer program code, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to cause the apparatus to at least detect an occurrence of an event affecting one or more of multicast or broadcast service content received by the apparatus over a multicarrier broadband wireless access network.
  • the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus of this embodiment to cause, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the apparatus to be provided to a base station providing access to the broadband wireless access network.
  • the at least one memory and stored computer program code are configured, with the at least one processor, to additionally cause the apparatus of this embodiment to cause an assignment to the apparatus of one or more carriers to be received, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
  • an apparatus which comprises means for detecting an occurrence of an event affecting one or more of multicast or broadcast service content received by the apparatus over a multicarrier broadband wireless access network.
  • the apparatus of this embodiment further comprises means for causing, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the apparatus to be provided to a base station providing access to the broadband wireless access network.
  • the apparatus of this embodiment additionally comprises means for receiving, from the base station, an assignment to the apparatus of one or more carriers, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
  • a method comprises receiving, at a base station providing access to a multicarrier broadband wireless access network, information about one or more of multicast or broadcast service content being received by a terminal over the broadband wireless access network in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal.
  • the broadband wireless access network may comprise a Worldwide Interoperability for Microwave Access (WiMAX) network operating in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
  • WiMAX Worldwide Interoperability for Microwave Access
  • IEEE Institute of Electrical and Electronics Engineers
  • the method of this embodiment further comprises assigning one or more carriers to the terminal based at least in part upon the received information.
  • the method of this embodiment additionally comprises causing the assignment of the one or more carriers to be sent to the terminal.
  • the method may further comprise causing the received information to be transferred to a target base station in response to handover of the terminal from the base station to the target base station.
  • the method may further comprise assigning a paging carrier to the terminal based at least in part upon the received information and causing the assignment of the paging carrier to be sent to the terminal.
  • a computer program product in another example embodiment, includes at least one computer-readable storage medium having computer-readable program instructions stored therein.
  • the program instructions of this embodiment comprise program instructions configured to cause information about one or more of multicast or broadcast service content being received by a terminal over a broadband wireless access network to be received at a base station providing access to the multicarrier broadband wireless access network.
  • the information is received in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal.
  • the program instructions of this embodiment further comprise program instructions configured to assign one or more carriers to the terminal based at least in part upon the received information.
  • the program instructions of this embodiment additionally comprise program instructions configured to cause the assignment of the one or more carriers to be sent to the terminal.
  • an apparatus comprising at least one processor and at least one memory storing computer program code, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to cause the apparatus to at least receive information about one or more of multicast or broadcast service content being received by a terminal over a broadband wireless access network, wherein the apparatus is configured to provide access to the multicarrier broadband wireless access network.
  • the information is received in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal.
  • the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus of this embodiment to assign one or more carriers to the terminal based at least in part upon the received information.
  • the at least one memory and stored computer program code are configured, with the at least one processor, to additionally cause the apparatus of this embodiment to cause the assignment of the one or more carriers to be sent to the terminal.
  • an apparatus which includes means for receiving, following occurrence of an event affecting one or more of multicast or broadcast service content received by a terminal over a broadband wireless access network, information about the one or more of multicast or broadcast service content, wherein the apparatus is configured to provide access to the multicarrier broadband wireless access network.
  • the apparatus of this embodiment further comprises means for assigning one or more carriers to the terminal based at least in part upon the received information.
  • the apparatus of this embodiment additionally comprises means for causing the assignment of the one or more carriers to be sent to the terminal.
  • FIG. 1 illustrates a system for facilitating multicarrier and multicast and broadcast service coordination according to an example embodiment of the present invention
  • FIG. 2 is a schematic block diagram of a mobile terminal according to an example embodiment of the present invention.
  • FIG. 3 illustrates a timing diagram of MBS transmission to a terminal in sleep mode according to an example embodiment of the present invention
  • FIG. 4 illustrates a time domain diagram of a base station acting as both an 802.16e and
  • FIGs. 5-6 illustrate flowcharts according to example methods for facilitating multicarrier and multicast and broadcast service coordination according to example embodiments of the invention.
  • FIG. 1 illustrates a block diagram of a system 100 for facilitating multicarrier and multicast and broadcast service coordination according to an example embodiment of the present invention. It will be appreciated that the scope of the invention encompasses many potential embodiments in addition to those illustrated and described herein. As such, while FIG. 1 illustrates one example of a configuration of a system for facilitating multicarrier and multicast and broadcast service coordination, numerous other configurations may also be used to implement embodiments of the present invention. Further, it will be appreciated that where references herein are made to specific multicarrier broadband wireless access network specifications, such as, for example, WiMAX, 802.16e, 802.16m, or the like, it is merely for purposes of example and other network specifications may benefit from embodiments of the invention.
  • WiMAX wireless access network specifications
  • the system 100 includes a terminal 102 and base station 104 configured to communicate over the communications link 108.
  • the base station 104 may reside on a network 106 and may be configured to provide access to the network 104 to one or more terminals 102.
  • the network 106 may comprise a broadband wireless access network and may comprise a network operating at least partially in accordance with 802.16m standards.
  • the terminal 102 may be embodied as a desktop computer, laptop computer, mobile terminal, mobile computer, mobile phone, mobile communication device, game device, digital camera/camcorder, audio/video player, television device, radio receiver, digital video recorder, positioning device, any combination thereof, and/or the like that is configured to access the network 106 via the base station 104.
  • the terminal 102 is embodied as a mobile terminal, such as that illustrated in FIG. 2.
  • FIG. 2 illustrates a block diagram of a mobile terminal 10 representative of one embodiment of a terminal 102 in accordance with embodiments of the present invention.
  • the mobile terminal 10 illustrated and hereinafter described is merely illustrative of one type of terminal 102 that may implement and/or benefit from embodiments of the present invention and, therefore, should not be taken to limit the scope of the present invention.
  • While several embodiments of the electronic device are illustrated and will be hereinafter described for purposes of example, other types of electronic devices, such as mobile telephones, mobile computers, portable digital assistants (PDAs), pagers, laptop computers, desktop computers, gaming devices, televisions, and other types of electronic systems, may employ embodiments of the present invention.
  • PDAs portable digital assistants
  • the mobile terminal 10 may include an antenna 12 (or multiple antennas 12) in communication with a transmitter 14 and a receiver 16.
  • the mobile terminal may also include a controller 20 or other processor(s) that provides signals to and receives signals from the transmitter and receiver, respectively.
  • These signals may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wireless- Fidelity (Wi-Fi), wireless local access network (WLAN) techniques such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, and/or the like.
  • these signals may include speech data, user generated data, user requested data, and/or the like.
  • the mobile terminal may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. More particularly, the mobile terminal may be capable of operating in accordance with various first generation (IG), second generation (2G), 2.5G, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., session initiation protocol (SIP)), and/or the like. For example, the mobile terminal may be capable of operating in accordance with 2G wireless communication protocols IS- 136 (Time Division Multiple Access (TDMA)), Global System for Mobile communications (GSM), IS-95 (Code Division Multiple Access (CDMA)), and/or the like.
  • IG first generation
  • 2G second generation
  • 2.5G third-generation
  • 3G third-generation
  • 4G fourth-generation
  • IMS Internet Protocol Multimedia Subsystem
  • SIP session initiation protocol
  • the mobile terminal may be capable of operating in accordance with 2G wireless communication protocols IS- 136 (Time Division Multiple Access (
  • the mobile terminal may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the mobile terminal may be capable of operating in accordance with 3G wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The mobile terminal may be additionally capable of operating in accordance with 3.9G wireless communication protocols such as Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access Network (E- UTRAN) and/or the like. Additionally, for example, the mobile terminal may be capable of operating in accordance with fourth-generation (4G) wireless communication protocols and/or the like as well as similar wireless communication protocols that may be developed in the future.
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data GSM Environment
  • 3G wireless communication protocols such as
  • NAMPS Narrow-band Advanced Mobile Phone System
  • TACS Total Access Communication System
  • mobile terminals may also benefit from embodiments of this invention, as should dual or higher mode phones (e.g., digital/analog or TDMA/CDMA/analog phones).
  • the mobile terminal 10 may be capable of operating according to Wireless Fidelity (Wi-Fi) or Worldwide Interoperability for Microwave Access (WiMAX) protocols.
  • Wi-Fi Wireless Fidelity
  • WiMAX Worldwide Interoperability for Microwave Access
  • the controller 20 may comprise circuitry for implementing audio/video and logic functions of the mobile terminal 10.
  • the controller 20 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and/or the like. Control and signal processing functions of the mobile terminal may be allocated between these devices according to their respective capabilities.
  • the controller may additionally comprise an internal voice coder (VC) 20a, an internal data modem (DM) 20b, and/or the like.
  • the controller may comprise functionality to operate one or more software programs, which may be stored in memory.
  • the controller 20 may be capable of operating a connectivity program, such as a web browser.
  • the connectivity program may allow the mobile terminal 10 to transmit and receive web content, such as location-based content, according to a protocol, such as Wireless
  • the mobile terminal 10 may be capable of using a Transmission Control Protocol/Internet Protocol (TCP/IP) to transmit and receive web content across the internet or other networks.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • the mobile terminal 10 may also comprise a user interface including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and/or the like, which may be operationally coupled to the controller 20.
  • the mobile terminal may comprise a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output.
  • the user input interface may comprise devices allowing the mobile terminal to receive data, such as a keypad 30, a touch display (not shown), a joystick (not shown), and/or other input device.
  • the keypad may comprise numeric (0-9) and related keys (#, *), and/or other keys for operating the mobile terminal.
  • the mobile terminal 10 may also include one or more means for sharing and/or obtaining data.
  • the mobile terminal may comprise a short-range radio frequency (RF) transceiver and/or interrogator 64 so data may be shared with and/or obtained from electronic devices in accordance with RF techniques.
  • the mobile terminal may comprise other short-range transceivers, such as, for example, an infrared (IR) transceiver 66, a BluetoothTM (BT) transceiver 68 operating using BluetoothTM brand wireless technology developed by the BluetoothTM Special Interest Group, a wireless universal serial bus (USB) transceiver 70 and/or the like.
  • IR infrared
  • BT BluetoothTM
  • USB wireless universal serial bus
  • the BluetoothTM transceiver 68 may be capable of operating according to ultra-low power BluetoothTM technology (e.g., WibreeTM) radio standards.
  • the mobile terminal 10 and, in particular, the short-range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within a proximity of the mobile terminal, such as within 10 meters, for example.
  • the mobile terminal may be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including Wireless Fidelity (Wi-Fi), WLAN techniques such as IEEE 802.1 1 techniques, IEEE 802.16 techniques, and/or the like.
  • Wi-Fi Wireless Fidelity
  • WLAN techniques such as IEEE 802.1 1 techniques, IEEE 802.16 techniques, and/or the like.
  • the mobile terminal 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), and/or the like, which may store information elements related to a mobile subscriber.
  • SIM subscriber identity module
  • R-UIM removable user identity module
  • the mobile terminal 10 may include volatile memory 40 and/or non-volatile memory 42.
  • volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off- chip cache memory, and/or the like.
  • RAM Random Access Memory
  • Non-volatile memory 42 which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices (e.g., hard disks, floppy disk drives, magnetic tape, etc.), optical disc drives and/or media, non- volatile random access memory (NVRAM), and/or the like. Like volatile memory 40 nonvolatile memory 42 may include a cache area for temporary storage of data.
  • the memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the mobile terminal for performing functions of the mobile terminal.
  • the memories may comprise an identifier, such as an international mobile equipment identification (FMEI) code, capable of uniquely identifying the mobile terminal 10.
  • FMEI international mobile equipment identification
  • the terminal 102 includes various means, such as one or more of a processor 110, memory 112, communication interface 114, user interface 116, or carrier coordination unit 118 for performing the various functions herein described.
  • These means of the terminal 102 as described herein may be embodied as, for example, hardware elements (e.g., a suitably programmed processor, combinational logic circuit, and/or the like), a computer program product comprising computer-readable program instructions (e.g., software or firmware) stored on a computer-readable medium (e.g. memory 112) that is executable by a suitably configured processing device (e.g., the processor 110), or some combination thereof.
  • the processor 110 may, for example, be embodied as various means including one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or FPGA (field programmable gate array), or some combination thereof. Accordingly, although illustrated in FIG. 1 as a single processor, in some embodiments the processor 110 comprises a plurality of processors. The plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of the terminal 102 as described herein.
  • the processor 1 10 is configured to execute instructions stored in the memory 112 or otherwise accessible to the processor 110. These instructions, when executed by the processor 110, may cause the terminal 102 to perform one or more of the functionalities of the terminal 102 as described herein. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 110 may comprise an entity capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor 110 is embodied as an ASIC, FPGA or the like, the processor 110 may comprise specifically configured hardware for conducting one or more operations described herein. Alternatively, as another example, when the processor 110 is embodied as an executor of instructions, such as may be stored in the memory 112, the instructions may specifically configure the processor 110 to perform one or more algorithms and operations described herein.
  • the memory 112 may include, for example, volatile and/or non-volatile memory. Although illustrated in FIG. 1 as a single memory, the memory 112 may comprise a plurality of memories. The memory 112 may comprise volatile memory, non-volatile memory, or some combination thereof. In this regard, the memory 112 may comprise, for example, a hard disk, random access memory, cache memory, flash memory, a compact disc read only memory (CD- ROM), digital versatile disc read only memory (DVD-ROM), an optical disc, circuitry configured to store information, or some combination thereof. The memory 112 may be configured to store information, data, applications, instructions, or the like for enabling the terminal 102 to carry out various functions in accordance with example embodiments of the present invention.
  • the memory 112 is configured to buffer input data for processing by the processor 110.
  • the memory 1 12 is configured to store program instructions for execution by the processor 110.
  • the memory 112 may store information in the form of static and/or dynamic information. This stored information may be stored and/or used by the carrier coordination unit 1 18 during the course of performing its functionalities.
  • the communication interface 114 may be embodied as any device or means embodied in hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., the memory 112) and executed by a processing device (e.g., the processor 110), or a combination thereof that is configured to receive and/or transmit data from/to the base station 104 over the communication link 108.
  • the communication interface 114 is at least partially embodied as or otherwise controlled by the processor 110.
  • the communication interface 114 may be in communication with the processor 110, such as via a bus.
  • the communication interface 114 may include, for example, an antenna, a transmitter, a receiver, a transceiver and/or supporting hardware or software for enabling communications with the base station 104.
  • the communication interface 114 may be configured to receive and/or transmit data using any protocol that may be used for communications between entities of the system 100. Accordingly, the communication interface 114 may be configured to receive and/or transmit data over the communications link 108 in accordance with the standards of a broadband wireless access network implemented on the network 106, such as, for example, in accordance with the standards of an 802.16 network.
  • the communication interface 114 may additionally be in communication with the memory 112, user interface 116, and/or carrier coordination unit 118, such as via a bus.
  • the user interface 116 may be in communication with the processor 110 to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user.
  • the user interface 116 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, and/or other input/output mechanisms.
  • the user interface 116 may provide an interface allowing a user to subscribe/unsubscribe to MBS content, initiate/stop reception of MBS content, and/or the like.
  • the user interface 116 may be in communication with the memory 112, communication interface 1 14, and/or carrier coordination unit 118, such as via a bus.
  • the carrier coordination unit 118 may be embodied as various means, such as hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., the memory 112) and executed by a processing device (e.g., the processor 110), or some combination thereof and, in one embodiment, is embodied as or otherwise controlled by the processor 110.
  • the carrier coordination unit 118 may be embodied separately from the processor 110, the carrier coordination unitl 18 may be in communication with the processor 110.
  • the carrier coordination unit 118 may further be in communication with the memory 112, communication interface 114, and/or user interface 116, such as via a bus.
  • the carrier coordination unit 118 is configured to perform at least some of the functionality of one or more of an MBS client entity, multicarrier management entity, idle mode management entity, or sleep mode management entity.
  • the base station 104 includes various means, such as one or more of a processor 120, memory 122, communication interface 124, or carrier assignment unit 126 for performing the various functions herein described.
  • These means of the base station 104 as described herein may be embodied as, for example, hardware elements (e.g., a suitably programmed processor, combinational logic circuit, and/or the like), a computer program product comprising computer-readable program instructions (e.g., software or firmware) stored on a computer-readable medium (e.g. memory 122) that is executable by a suitably configured processing device (e.g., the processor 120), or some combination thereof.
  • the processor 120 may, for example, be embodied as various means including one or more microprocessors with accompanying digital signal processors), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or FPGA (field programmable gate array), or some combination thereof. Accordingly, although illustrated in FIG. 1 as a single processor, in some embodiments the processor 120 comprises a plurality of processors. The plurality of processors may be embodied on a single computing device or distributed among a plurality of computing devices, which may be collectively configured to function as a base station 104.
  • the plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of the base station 104 as described herein.
  • the processor 120 is configured to execute instructions stored in the memory 122 or otherwise accessible to the processor 120. These instructions, when executed by the processor 120, may cause the base station 104 to perform one or more of the functionalities of the base station 104 as described herein.
  • the processor 120 may comprise an entity capable of performing operations according to embodiments of the present invention while configured accordingly.
  • the processor 120 when the processor 120 is embodied as an ASIC, FPGA or the like, the processor 120 may comprise specifically configured hardware for conducting one or more operations described herein.
  • the processor 120 is embodied as an executor of instructions, such as may be stored in the memory 122, the instructions may specifically configure the processor 120 to perform one or more algorithms and operations described herein.
  • the memory 122 may include, for example, volatile and/or non-volatile memory. Although illustrated in FIG. 1 as a single memory, the memory 122 may comprise a plurality of memories. The memory 122 may comprise volatile memory, non-volatile memory, or some combination thereof. In this regard, the memory 122 may comprise, for example, a hard disk, random access memory, cache memory, flash memory, a compact disc read only memory (CD- ROM), digital versatile disc read only memory (DVD-ROM), an optical disc, circuitry configured to store information, or some combination thereof. The memory 122 may be configured to store information, data, applications, instructions, or the like for enabling the base station 104 to carry out various functions in accordance with example embodiments of the present invention.
  • the memory 122 is configured to buffer input data for processing by the processor 120. Additionally or alternatively, in at least some embodiments, the memory 122 is configured to store program instructions for execution by the processor 120.
  • the memory 122 may store information in the form of static and/or dynamic information. This stored information may be stored and/or used by the carrier assignment unit 126 during the course of performing its functionalities.
  • the communication interface 124 may be embodied as any device or means embodied in hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., the memory 122) and executed by a processing device (e.g., the processor 120), or a combination thereof that is configured to receive and/or transmit data from/to a terminal 102 over the communication link 108.
  • the communication interface 124 is at least partially embodied as or otherwise controlled by the processor 120.
  • the communication interface 124 may be in communication with the processor 120, such as via a bus.
  • the communication interface 124 may include, for example, an antenna, a transmitter, a receiver, a transceiver and/or supporting hardware or software for enabling communications with a terminal 102.
  • the communication interface 124 may be configured to receive and/or transmit data using any protocol that may be used for communications between entities of the system 100. Accordingly, the communication interface 124 may be configured to receive and/or transmit data over the communications link 108 in accordance with the standards of a broadband wireless access network implemented on the network 106, such as, for example, in accordance with the standards of an 802.16 network.
  • the communication interface 124 may additionally be in communication with the memory 122 and/or carrier assignment unit 128, such as via a bus.
  • the carrier assignment unit 126 may be embodied as various means, such as hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., the memory 122) and executed by a processing device (e.g., the processor 120), or some combination thereof and, in one embodiment, is embodied as or otherwise controlled by the processor 120. In embodiments wherein the carrier assignment unit 126 is embodied separately from the processor 120, the carrier assignment unit 126 may be in communication with the processor 120. The carrier assignment unit 126 may further be in communication with the memory 122 and/or communication interface 124, such as via a bus. In some embodiments, the carrier coordination unit 118 is configured to perform at least some of the functionality of one or more of an MBS agent entity, multicarrier management entity, idle mode management entity, or sleep mode management entity.
  • the terminal 102 and base station 104 may, via the communication interfaces 114 and 124, transmit/receive data using one or more carriers over the communication link 108.
  • the base station 104 may be configured to support multicarrier operation. Communication between the terminal 102 and base station 104 may occur on multiple radio frequency carriers simultaneously, which is referred to as carrier aggregation, or aggregate mode of multicarrier operation.
  • carrier aggregation the communication interface 114 may have multiple radios.
  • the carrier coordination unit 118 in combination with the communication interface 114 may be configured to maintain the physical layer connection of the terminal 102 and monitor the control information on the primary carrier even while using other radios for secondary carriers.
  • the terminal 102 and base station 104 may communicate using carrier switching mode, wherein the terminal 102 may alternate between multiple RF carriers but not use any two carriers simultaneously. Accordingly, when operating in carrier switching mode, the carrier combination unit 118 in combination with the communication interface 114 may be configured to switch the physical layer connection of the terminal 102 from the primary carrier to a secondary carrier according to instructions received from the base station 104.
  • a primary carrier is always fully configured.
  • all of the control channels including synchronization, broadcast, multicast, and unicast control signaling may be configured.
  • Information and parameters regarding multi- carrier operation and other carriers may be transmitted in the control channels of a fully configured carrier.
  • a secondary carrier may be either fully configured or partially configured. In this regard, a secondary carrier may be more or less just a data pipe and may be used for MBS content transmission.
  • some or all the control channels are omitted, but one or more control channels may be configured to support traffic exchanges during multi -carrier operation.
  • a partially configured carrier may, for example, comprise a downlink only carrier used for MBS content transmission.
  • a terminal 102 may have one primary carrier and, optionally, one or more secondary carriers assigned to it by the base station 104.
  • Some example embodiments facilitate multicarrier and MBS coordination through the provision of information about MBS content being received by the terminal 102 to the base station 104. These example embodiments may, for example, provide an enhancement to the MBS Application track for WiMAX systems.
  • the carrier coordination unit 1 18 may be configured to detect an occurrence of an event affecting MBS content received by the terminal 102 over the network 106.
  • the terminal 102 may receive the MBS control signaling at an application layer, such as in accordance with the MBS Application Track for WiMAX systems.
  • An event affecting MBS content may comprise, for example, the terminal 102 joining an MBS service, the terminal 102 leaving an MBS service, the terminal 102 initiating MBS service reception, the terminal 102 stopping MBS service reception, a handover of the terminal 102 from a first base station 104 to a second base station 104, network re-entry, idle mode selection of a base station 104, initial network entry and/or the like.
  • the terminal 102 may be receiving MBS content from a radio access transmission other than from a broadband wireless access network.
  • the terminal 102 may be receiving MBS content from a wireless local area network operating in accordance with IEEE 802.11 standards over an 802.11 radio of the communication interface 114.
  • the terminal 102 may switch to a broadband wireless access network radio and make an initial network entry to the base station 104. This event of initial network entry may thus affect MBS content received by the terminal 102.
  • the carrier coordination unit 118 may be configured to provide information about MBS content being received by the terminal 102 to a base station 104.
  • the carrier coordination unit 118 may be configured to provide the information in a dedicated management message or as an added attribute or parameter of a message, such as, for example, a Ranging Request message (RNG-REQ).
  • the information provided to the base station 104 may, for example, comprise a multicast and broadcast service zone identification (MBS-Zone ID), one or more identifiers for MBS content (e.g., multicast connection identifiers (MCIDs), and/or the like.
  • MBS-Zone ID multicast and broadcast service zone identification
  • MCS-Zone ID multicast and broadcast service zone identification
  • MCS-Zone ID multicast and broadcast service zone identification
  • MCS-Zone ID multicast and broadcast service zone identification
  • MCS-Zone ID multicast and broadcast service zone identification
  • MCS-Zone ID multicast and broadcast service zone identification
  • MIDs multicast connection identifiers
  • Carrier 2 Mixed unicast and MBS content with MCIDs 1-5
  • Carrier 3 Dedicated MBS carrier: MCIDs 6-15
  • Carrier 4 Unicast only
  • the carrier assignment unit 126 may configure a carrier for a specific type of data content, such as unicast only, mixed unicast and MBS content, dedicated MBS content, and/or the like. Further, for a carrier configured for transmission of MBS content, the carrier assignment unit 126 may configure the carrier for specific multicasts and/or broadcast content (e.g., only MCIDs 1-5 on carrier 2 and MCIDs 6-15 on carrier 3).
  • the carrier assignment unit 126 may be configured to assign appropriate carriers to the terminal (e.g., for MBS content and/or unicast data). For example, if the terminal 102 is receiving MBS content with MCID 4, then using the above example carrier configuration, the carrier assignment unit 126 may assign to the terminal 102 at least carrier 2 either as a primary or secondary carrier. In another example, if the terminal 102 is receiving MBS content with MCIDs 3 and 8, the carrier assignment unit 126 may assign carrier 3 to the terminal as a secondary carrier (dedicated MBS carrier cannot be a primary carrier) and carrier 2 as either a primary or secondary carrier. The carrier assignment unit 126 may further assign one or more other carriers to the terminal 102 for unicast data exchange if needed.
  • the carrier assignment unit 126 may be configured to send the assignment to the terminal 102.
  • the carrier assignment unit 126 may be further configured to store the assignment in the memory 122.
  • the carrier coordination unit 118 may be configured to receive the assignment sent by the base station 104.
  • the carrier coordination unit 118 may use the one or more assigned carriers in accordance with any restrictions imposed on their usage by the base station 104. In this regard, the carrier coordination unit 118 may use an appropriately configured assigned carrier for MBS content reception.
  • the carrier coordination unit 1 18 may be configured to further store information about the one or more assigned carriers in the memory 112.
  • the carrier assignment unit 126 may be configured to generate a resource allocation (e.g., a MAP, MBS-MAP, and/or the like) defining when MBS content is scheduled and/or on what carrier it is to be transmittedlO2. The scheduling may be common across an entire MBS zone, and not just to a single base station 104.
  • the carrier assignment unit 126 may send the resource allocation to the terminal 102.
  • the carrier coordination unit 118 may be configured to receive a resource allocation sent by the base station 104 and may use information included in the resource allocation to schedule receipt of MBS content on appropriate carrier(s).
  • the carrier coordination unit 118 may further store the received resource allocation in the memory 112.
  • the carrier assignment unit 126 of the serving base station 104 may be configured to transfer MBS information about MBS content the terminal 102 is receiving to the target base station 104.
  • the carrier assignment unit 126 may be configured to transfer the information over an access service network (ASN) interface between the serving base station 104 and target base station 104.
  • ASN access service network
  • the carrier assignment unit 126 of the target base station 104 may assign one or more carriers to the terminal 102 based at least in part upon the transferred MBS information. Accordingly, interruption time for MBS reception during handover may be reduced.
  • the carrier coordination unit 118 may be configured to provide information about MBS content being received by the terminal 102 to the target base station 104 during network re-entry.
  • the carrier assignment unit 126 of the target base station 104 may be configured to map MBS content information provided by the terminal 102 to derive identifications for MBS content that are applicable to the MBS zone of the target base station 104.
  • the mapping may be static and thus may be preconfigured for the target base station 104 and stored in the memory 122.
  • the carrier assignment unit 126 may then send the derived mapping to the terminal 102 and the carrier coordination unit 118 may update the local MBS content identifications for the terminal 102. If a static mapping is not stored in the memory 122 and the carrier assignment unit 126 cannot otherwise generate a mapping, the carrier assignment unit 126 may be configured to acquire the mapping from an MBS server/controller providing MBS content to the terminal 102.
  • the carrier coordination unit 118 may be configured to perform an MBS location update or network re-entry and provide information about MBS content being received by the terminal 102 to the preferred target base station 104.
  • the carrier coordination unit 118 may include the MBS-Zone ID for the MBS zone of the terminal's previous serving base station and current identifiers for MBS content (e.g., MCIDs or the like) 104 in the information provided to the preferred target base station 104 and may provide the information as one or more parameters to a RNG-REQ message.
  • the carrier assignment unit 126 may further perform a mapping and provide the terminal 102 with MBS content identifications appropriate for the MBS zone of the target base station 104.
  • the carrier coordination unit 1 18 may be configured to acquire new identifications for MBS content for the MBS zone of the target base station 104 through passive listening to broadcast messages, such as, for example, Mobile
  • MBS-NBR_ADV Neighbor Advance
  • the carrier coordination unit 118 may additionally or alternatively be configured to acquire MBS content identifications for the new MBS zone from an MBS server/controller. Additionally, MBS information transfer between the terminal 102 and target base station
  • MBS zone switching may be used also for other purposes, such as, for example, triggering initiation of dynamic MBS content in new MBS zone (dynamic content is sent within MBS zone only if one or more terminals 102 will request it).
  • the carrier assignment unit 126 is configured to assign a paging carrier to a terminal 102 based at least in part upon terminal-provided information about MBS content being received by the terminal 102.
  • the carrier assignment unit 126 may use one or more criteria in making the assignment of a paging carrier. For example, in the case of a terminal 102 having multiple radios and operating in aggregate mode, it may simplify paging operation or MBS reception if paging carrier is different than the carrier(s) used for MBS reception. Then the base station 104 and terminal 102 may handle MBS transmission and paging independently.
  • the terminal 102 when the terminal 102 is operating in carrier switching mode, it may aid paging operation if the same carrier is used for both paging and MBS reception to reduce carrier switching.
  • paging may have higher priority and MBS reception may suffer if they are in different carriers and those operations happens at the same time.
  • MBS reception may be assigned to a dedicated carrier and thus the carrier assignment unit 126 cannot assign the dedicated carrier as the paging carrier.
  • the terminal 102 may receive MBS content via a secondary carrier during sleep mode.
  • the carrier coordination unit 118 may be configured to manage MBS operation independent of sleep mode operation because MBS content scheduling may not be aligned to the terminal's sleep operation intervals, as MBS is often sent to multiple terminals.
  • the carrier assignment unit 126 may be configured to assign a secondary carrier for MBS only transmission and thus the terminal 102 may not need to consider the secondary carrier during sleep mode.
  • the terminal 102 and base station 104 may switch temporarily from the primary carrier to a secondary carrier.
  • the base station 104 may explicitly signal through the primary carrier to the terminal 102 to switch to a secondary carrier and may include a parameter in the signaling message indicating how long the terminal 102 is to use the secondary carrier.
  • MBS scheduling timing and interval may not depend on sleep mode and sleep mode listening interval lengths and timing may not be constant, collision between MBS reception and sleep mode operation may occur.
  • FIG. 3 illustrates a timing diagram of MBS transmission to a terminal in sleep mode according to an example embodiment.
  • a first carrier 302 (carrier 1) comprises a primary carrier used for unicast.
  • a second carrier 304 (Carrier 2) comprises a secondary carrier used for MBS reception. Carrier switching is made to receive MBS data from the carrier 304.
  • both the carrier coordination unit 118 and carrier assignment unit 126 may be configured to determine whether the beginning of the next listening interval when the terminal 102 is to switch to the primary carrier will collide with a scheduled reception of MBS data 306. If so, the carrier coordination unit 118 and carrier assignment unit 126 may be configured to extend the preceding sleep window 310 by the sleep window extension 312 so that the collision is avoided.
  • the base station 104 may then send the unicast or signaling data 308 (e.g., a Mobile Traffic Indication (MOB_TRF-IND), which may be used to inform the terminal
  • MOB_TRF-IND Mobile Traffic Indication
  • the base station 104 may be configured to provide access to the network 106 in accordance with multiple broadband wireless access standards.
  • the base station 104 may be configured to implement a mixed mode deployment wherein it acts as both an 802.16e and an 802.16m base station with modes separated in the time domain as illustrated in FIG. 4 In this regard, operation of the base station
  • An LZone comprises a legacy zone over the period(s) of time when the base station 104 acts as an 802.16e base station.
  • the MZone comprises the period(s) of time when the base station 104 acts as an 802.16m base station.
  • the respective zones may be further separated in the time domain into downlink (DL) and uplink (UL) zones. Accordingly, the operation of the base station 104 may be divided into an LZone UL zone
  • the carrier coordination 118 may be configured to receive MBS content from LZone by using 802.16e methods, such as with the assistance of an MBS map. Accordingly, synchronization between .16e and .16m systems may not be needed because the carrier coordination unit 118 may listen passively and maintain (broadcasted) system information from both systems.
  • the carrier assignment unit 126 may be configured in some embodiments to transmit all MBS content in the 802.16e zone of the time domain to enable terminals that are not configured for operation under the 802.16m standard to receive MBS data.
  • the carrier assignment unit 126 when operating in the MZone, is configured to broadcast high level MBS control information for LZone MBS reception.
  • the Super Frame Header (SFH) of MZone may be configured to carry MBS Zone ID list for LZone. Also this MBS Zone ID list may have additional information (e.g. one bit) to indicate that MBS Zone ID is located in LZone.
  • Such embodiments may enhance MBS operation during and/or following a handover because the terminal 102 may not need to decode a downlink channel descriptor (DCD) or a Mobile Neighbor Advance (MOB_NBR-ADV) in LZone. Further, since in such embodiments only high level MBS control information is sent through MZone, overhead due to duplicate MBS control information being sent also through LZone to support legacy terminals may be insignificant.
  • DCD downlink channel descriptor
  • MOB_NBR-ADV Mobile Neighbor Advance
  • FIG. 5 illustrates a flowchart according to an example method for facilitating multicarrier and multicast and broadcast service coordination according to an example embodiment of the invention.
  • the method may include the carrier coordination unit 118 detecting an occurrence of an event affecting MBS content received by the terminal 102 over a multicarrier broadband wireless access network, such as the network 106, at operation 500.
  • Operation 510 may comprise the carrier coordination unit 118 providing, in response to detection of the event, information about MBS content being received to the base station 104.
  • the carrier coordination unit 118 may receive an assignment of one or more carriers at operation 520.
  • the base station 104 may have assigned the one or more carriers based at least in part upon the provided information.
  • FIG. 6 illustrates a flowchart according to an example method for facilitating multicarrier and multicast and broadcast service coordination according to an example embodiment of the invention.
  • the method may include the carrier assignment unit 126 receiving information about MBS content being received by a terminal 102 following occurrence of an event affecting MBS content received by terminal 102, at operation 600.
  • Operation 610 may comprise the carrier assignment unit 126 assigning one or more carriers to the terminal 102 based at least in part upon the received information.
  • the carrier assignment unit 126 may send the assignment to the terminal 102, at operation 620.
  • FIGs. 5-6 are flowcharts of a system, method, and computer program product according to example embodiments.
  • each block of the flowcharts, and combinations of blocks in the flowcharts may be implemented by various means, such as hardware and/or a computer program product comprising one or more computer-readable mediums having computer readable program instructions stored thereon.
  • one or more of the procedures described herein may be embodied by computer program instructions of a computer program product.
  • the computer program product(s) which embody the procedures described herein may be stored by one or more memory devices of a mobile terminal, server, or other computing device and executed by a processor in the computing device.
  • the computer program instructions comprising the computer program product(s) which embody the procedures described above may be stored by memory devices of a plurality of computing devices.
  • any such computer program product may be loaded onto a computer or other programmable apparatus to produce a machine, such that the computer program product including the instructions which execute on the computer or other programmable apparatus creates means for implementing the functions specified in the flowchart block(s).
  • the computer program product may comprise one or more computer-readable memories on which the computer program instructions may be stored such that the one or more computer- readable memories can direct a computer or other programmable apparatus to function in a particular manner, such that the computer program product comprises an article of manufacture which implements the function specified in the flowchart block(s).
  • the computer program instructions of one or more computer program products may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus implement the functions specified in the flowchart block(s).
  • blocks of the flowcharts support combinations of means for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer program product(s). The above described functions may be carried out in many ways.
  • any suitable means for carrying out each of the functions described above may be employed to carry out an embodiment.
  • a suitably configured processor may provide all or a portion of the elements.
  • all or a portion of the elements may be configured by and operate under control of a computer program product.
  • the computer program product for performing the methods of example embodiments includes a computer-readable storage medium, such as the non-volatile storage medium, and computer-readable program code portions, such as a series of computer instructions, embodied in the computer-readable storage medium.
  • Some example embodiments provide several advantages to computing devices and network operators.
  • Some example embodiments provide terminals configured to provide information about MBS content being received by the terminal to a base station upon occurrence of an event affecting MBS content received by the terminal.
  • Some example embodiments further provide base stations configured to assign one or more carriers to a terminal based at least in part upon information about MBS content being received by the terminal that is provided to the base station by the terminal. Accordingly, some example embodiments provide coordination of MBS content and carriers in a multicarrier broadband wireless access network.

Abstract

Systems, methods, and apparatuses are provided for facilitating multicarrier and multicast and broadcast service coordination. A method may include detecting an occurrence of an event affecting one or more of multicast or broadcast service content received by a terminal over a multicarrier broadband wireless access network. The method may further include providing, in response to detection of the event, information about multicast and broadcast service content being received by the terminal to a base station providing access to the broadband wireless access network. The method may additionally include receiving, from the base station, an assignment to the terminal of one or more carriers, wherein the base station assigned the one or more carriers based at least in part upon the information about received multicast and broadcast service content. Corresponding systems and apparatuses are also provided.

Description

SYSTEMS, METHODS, AND APPARATUSES FOR FACILITATING MULTICARRIER AND MULTICAST AND BROADCAST SERVICE COORDINATION
TECHNOLOGICAL FIELD
Embodiments of the present invention relate generally to communication technology and, more particularly, relate to systems, methods, and apparatuses for facilitating multicarrier and multicast and broadcast service coordination.
BACKGROUND
The modern communications era has brought about a tremendous expansion of wireline and wireless networks. Computer networks, television networks, and telephony networks are experiencing an unprecedented technological expansion, fueled by consumer demand. Wireless and mobile networking technologies have addressed related consumer demands, while providing more flexibility and immediacy of information transfer and providing convenience to users.
One such networking technology that is being deployed on a broader scale is broadband wireless access network technology. Broadband wireless access networks may be deployed on a community-wide, or metropolitan-wide, level and are sometimes referred to as wireless metropolitan area networks (WMANs) as opposed to wireless local area networks (WLANs) that may cover a more localized area, such as a home or business. Accordingly, a broadband wireless access network may allow a user to wirelessly access a network with a terminal throughout the coverage area of the network by accessing the network through one or more base stations that provide wireless access to the network. One broadband wireless access network standard being deployed is the Worldwide
Interoperability for Microwave Access (WiMAX) standard governed by the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard ("802.16"). Currently, the 802.16m version of the standard is in development. In this regard, 802.16m is being designed to support multicarrier operation such that communication between a terminal and serving base station may occur over multiple radio frequency (RF) carriers, also referred to as carriers. Further, 802.16 provides support for multicast and broadcast services (MBS). MBS may be used to efficiently transport video and/or audio to multiple user terminals simultaneously and may, for example, be used to transmit an Internet radio broadcast, a television broadcast, and/or the like.
BRIEF SUMMARY
Systems, methods, apparatuses, and computer program products are herein provided for facilitating multicarrier and multicast and broadcast service coordination. In this regard, systems, methods, apparatuses, and computer program products are provided that may provide several advantages to computing devices and network operators. Some example embodiments provide terminals configured to provide information about MBS content being received by the terminal to a base station in response to occurrence of an event affecting MBS content received by the terminal. The MBS content may comprise multicast and/or broadcast service content, and as such MBS may be used herein to refer interchangeably to multicast and/or broadcast services. Some example embodiments further provide base stations configured to assign one or more carriers to a terminal based at least in part upon information about MBS content being received by the terminal that is provided to the base station by the terminal. Accordingly, some example embodiments provide coordination of MBS content and carriers in a multicarrier broadband wireless access network. In a first example embodiment, a method is provided, which comprises detecting, at a terminal, an occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal over a multicarrier broadband wireless access network. The broadband wireless access network may comprise a Worldwide Interoperability for Microwave Access (WiMAX) network operating in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards. The method of this embodiment further comprises causing, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the terminal to be provided to a base station providing access to the broadband wireless access network. The information may comprise one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content. The method of this embodiment additionally comprises receiving, from the base station, an assignment of one or more carriers to the terminal, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
The event may comprise a handover of the terminal from a serving base station to a target base station. Causing the information to be provided may comprise causing the information to be provided to the target base station during network re-entry.
The method may further comprise receiving an assignment of a paging carrier, wherein the base station assigned the paging carrier based at least in part upon the provided information. In another example embodiment, a computer program product is provided. The computer program product includes at least one computer-readable storage medium having computer- readable program instructions stored therein. The computer-readable program instructions may include a plurality of program instructions. The program instructions of this embodiment comprise program instructions configured to detect an occurrence of an event affecting one or more of multicast or broadcast service content received by a terminal over a multicarrier broadband wireless access network. The program instructions of this embodiment further comprise program instructions configured to cause, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the terminal to be provided to a base station providing access to the broadband wireless access network. The program instructions of this embodiment also comprise program instructions configured to cause an assignment to the terminal of one or more carriers to be received, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
In another example embodiment, an apparatus is provided. The apparatus of this embodiment comprises at least one processor and at least one memory storing computer program code, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to cause the apparatus to at least detect an occurrence of an event affecting one or more of multicast or broadcast service content received by the apparatus over a multicarrier broadband wireless access network. The at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus of this embodiment to cause, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the apparatus to be provided to a base station providing access to the broadband wireless access network. The at least one memory and stored computer program code are configured, with the at least one processor, to additionally cause the apparatus of this embodiment to cause an assignment to the apparatus of one or more carriers to be received, wherein the base station assigned the one or more carriers based at least in part upon the provided information. In another example embodiment, an apparatus is provided, which comprises means for detecting an occurrence of an event affecting one or more of multicast or broadcast service content received by the apparatus over a multicarrier broadband wireless access network. The apparatus of this embodiment further comprises means for causing, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the apparatus to be provided to a base station providing access to the broadband wireless access network. The apparatus of this embodiment additionally comprises means for receiving, from the base station, an assignment to the apparatus of one or more carriers, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
In another example embodiment, a method is provided, which comprises receiving, at a base station providing access to a multicarrier broadband wireless access network, information about one or more of multicast or broadcast service content being received by a terminal over the broadband wireless access network in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal. The broadband wireless access network may comprise a Worldwide Interoperability for Microwave Access (WiMAX) network operating in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards. The method of this embodiment further comprises assigning one or more carriers to the terminal based at least in part upon the received information. The method of this embodiment additionally comprises causing the assignment of the one or more carriers to be sent to the terminal.
The method may further comprise causing the received information to be transferred to a target base station in response to handover of the terminal from the base station to the target base station.
The method may further comprise assigning a paging carrier to the terminal based at least in part upon the received information and causing the assignment of the paging carrier to be sent to the terminal.
In another example embodiment, a computer program product is provided. The computer program product of this embodiment includes at least one computer-readable storage medium having computer-readable program instructions stored therein. The program instructions of this embodiment comprise program instructions configured to cause information about one or more of multicast or broadcast service content being received by a terminal over a broadband wireless access network to be received at a base station providing access to the multicarrier broadband wireless access network. In this embodiment, the information is received in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal. The program instructions of this embodiment further comprise program instructions configured to assign one or more carriers to the terminal based at least in part upon the received information. The program instructions of this embodiment additionally comprise program instructions configured to cause the assignment of the one or more carriers to be sent to the terminal.
In another example embodiment, an apparatus is provided. The apparatus of this embodiment comprises at least one processor and at least one memory storing computer program code, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to cause the apparatus to at least receive information about one or more of multicast or broadcast service content being received by a terminal over a broadband wireless access network, wherein the apparatus is configured to provide access to the multicarrier broadband wireless access network. In this embodiment, the information is received in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal. The at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus of this embodiment to assign one or more carriers to the terminal based at least in part upon the received information. The at least one memory and stored computer program code are configured, with the at least one processor, to additionally cause the apparatus of this embodiment to cause the assignment of the one or more carriers to be sent to the terminal.
In another example embodiment, an apparatus is provided, which includes means for receiving, following occurrence of an event affecting one or more of multicast or broadcast service content received by a terminal over a broadband wireless access network, information about the one or more of multicast or broadcast service content, wherein the apparatus is configured to provide access to the multicarrier broadband wireless access network. The apparatus of this embodiment further comprises means for assigning one or more carriers to the terminal based at least in part upon the received information. The apparatus of this embodiment additionally comprises means for causing the assignment of the one or more carriers to be sent to the terminal.
The above summary is provided merely for purposes of summarizing some example embodiments of the invention so as to provide a basic understanding of some aspects of the invention. Accordingly, it will be appreciated that the above described example embodiments are merely examples and should not be construed to narrow the scope or spirit of the invention in any way. It will be appreciated that the scope of the invention encompasses many potential embodiments, some of which will be further described below, in addition to those here summarized.
BRIEF DESCRIPTION OF THE DRAWING(S)
Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
FIG. 1 illustrates a system for facilitating multicarrier and multicast and broadcast service coordination according to an example embodiment of the present invention;
FIG. 2 is a schematic block diagram of a mobile terminal according to an example embodiment of the present invention;
FIG. 3 illustrates a timing diagram of MBS transmission to a terminal in sleep mode according to an example embodiment of the present invention; FIG. 4 illustrates a time domain diagram of a base station acting as both an 802.16e and
802.16m base station according to an example embodiment of the present invention; and
FIGs. 5-6 illustrate flowcharts according to example methods for facilitating multicarrier and multicast and broadcast service coordination according to example embodiments of the invention.
DETAILED DESCRIPTION
Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout.
FIG. 1 illustrates a block diagram of a system 100 for facilitating multicarrier and multicast and broadcast service coordination according to an example embodiment of the present invention. It will be appreciated that the scope of the invention encompasses many potential embodiments in addition to those illustrated and described herein. As such, while FIG. 1 illustrates one example of a configuration of a system for facilitating multicarrier and multicast and broadcast service coordination, numerous other configurations may also be used to implement embodiments of the present invention. Further, it will be appreciated that where references herein are made to specific multicarrier broadband wireless access network specifications, such as, for example, WiMAX, 802.16e, 802.16m, or the like, it is merely for purposes of example and other network specifications may benefit from embodiments of the invention.
In at least some embodiments, the system 100 includes a terminal 102 and base station 104 configured to communicate over the communications link 108. The base station 104 may reside on a network 106 and may be configured to provide access to the network 104 to one or more terminals 102. The network 106 may comprise a broadband wireless access network and may comprise a network operating at least partially in accordance with 802.16m standards.
The terminal 102 may be embodied as a desktop computer, laptop computer, mobile terminal, mobile computer, mobile phone, mobile communication device, game device, digital camera/camcorder, audio/video player, television device, radio receiver, digital video recorder, positioning device, any combination thereof, and/or the like that is configured to access the network 106 via the base station 104. In an example embodiment, the terminal 102 is embodied as a mobile terminal, such as that illustrated in FIG. 2.
In this regard, FIG. 2 illustrates a block diagram of a mobile terminal 10 representative of one embodiment of a terminal 102 in accordance with embodiments of the present invention. It should be understood, however, that the mobile terminal 10 illustrated and hereinafter described is merely illustrative of one type of terminal 102 that may implement and/or benefit from embodiments of the present invention and, therefore, should not be taken to limit the scope of the present invention. While several embodiments of the electronic device are illustrated and will be hereinafter described for purposes of example, other types of electronic devices, such as mobile telephones, mobile computers, portable digital assistants (PDAs), pagers, laptop computers, desktop computers, gaming devices, televisions, and other types of electronic systems, may employ embodiments of the present invention.
As shown, the mobile terminal 10 may include an antenna 12 (or multiple antennas 12) in communication with a transmitter 14 and a receiver 16. The mobile terminal may also include a controller 20 or other processor(s) that provides signals to and receives signals from the transmitter and receiver, respectively. These signals may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wireless- Fidelity (Wi-Fi), wireless local access network (WLAN) techniques such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, and/or the like. In addition, these signals may include speech data, user generated data, user requested data, and/or the like. In this regard, the mobile terminal may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. More particularly, the mobile terminal may be capable of operating in accordance with various first generation (IG), second generation (2G), 2.5G, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., session initiation protocol (SIP)), and/or the like. For example, the mobile terminal may be capable of operating in accordance with 2G wireless communication protocols IS- 136 (Time Division Multiple Access (TDMA)), Global System for Mobile communications (GSM), IS-95 (Code Division Multiple Access (CDMA)), and/or the like. Also, for example, the mobile terminal may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the mobile terminal may be capable of operating in accordance with 3G wireless communication protocols such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The mobile terminal may be additionally capable of operating in accordance with 3.9G wireless communication protocols such as Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access Network (E- UTRAN) and/or the like. Additionally, for example, the mobile terminal may be capable of operating in accordance with fourth-generation (4G) wireless communication protocols and/or the like as well as similar wireless communication protocols that may be developed in the future.
Some Narrow-band Advanced Mobile Phone System (NAMPS), as well as Total Access Communication System (TACS), mobile terminals may also benefit from embodiments of this invention, as should dual or higher mode phones (e.g., digital/analog or TDMA/CDMA/analog phones). Additionally, the mobile terminal 10 may be capable of operating according to Wireless Fidelity (Wi-Fi) or Worldwide Interoperability for Microwave Access (WiMAX) protocols.
It is understood that the controller 20 may comprise circuitry for implementing audio/video and logic functions of the mobile terminal 10. For example, the controller 20 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and/or the like. Control and signal processing functions of the mobile terminal may be allocated between these devices according to their respective capabilities. The controller may additionally comprise an internal voice coder (VC) 20a, an internal data modem (DM) 20b, and/or the like. Further, the controller may comprise functionality to operate one or more software programs, which may be stored in memory. For example, the controller 20 may be capable of operating a connectivity program, such as a web browser. The connectivity program may allow the mobile terminal 10 to transmit and receive web content, such as location-based content, according to a protocol, such as Wireless
Application Protocol (WAP), hypertext transfer protocol (HTTP), and/or the like. The mobile terminal 10 may be capable of using a Transmission Control Protocol/Internet Protocol (TCP/IP) to transmit and receive web content across the internet or other networks.
The mobile terminal 10 may also comprise a user interface including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and/or the like, which may be operationally coupled to the controller 20. Although not shown, the mobile terminal may comprise a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output. The user input interface may comprise devices allowing the mobile terminal to receive data, such as a keypad 30, a touch display (not shown), a joystick (not shown), and/or other input device. In embodiments including a keypad, the keypad may comprise numeric (0-9) and related keys (#, *), and/or other keys for operating the mobile terminal.
As shown in FIG. 2, the mobile terminal 10 may also include one or more means for sharing and/or obtaining data. For example, the mobile terminal may comprise a short-range radio frequency (RF) transceiver and/or interrogator 64 so data may be shared with and/or obtained from electronic devices in accordance with RF techniques. The mobile terminal may comprise other short-range transceivers, such as, for example, an infrared (IR) transceiver 66, a Bluetooth™ (BT) transceiver 68 operating using Bluetooth™ brand wireless technology developed by the Bluetooth™ Special Interest Group, a wireless universal serial bus (USB) transceiver 70 and/or the like. The Bluetooth™ transceiver 68 may be capable of operating according to ultra-low power Bluetooth™ technology (e.g., Wibree™) radio standards. In this regard, the mobile terminal 10 and, in particular, the short-range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within a proximity of the mobile terminal, such as within 10 meters, for example. Although not shown, the mobile terminal may be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including Wireless Fidelity (Wi-Fi), WLAN techniques such as IEEE 802.1 1 techniques, IEEE 802.16 techniques, and/or the like.
The mobile terminal 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), and/or the like, which may store information elements related to a mobile subscriber. In addition to the SEvI, the mobile terminal may comprise other removable and/or fixed memory. The mobile terminal 10 may include volatile memory 40 and/or non-volatile memory 42. For example, volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off- chip cache memory, and/or the like. Non-volatile memory 42, which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices (e.g., hard disks, floppy disk drives, magnetic tape, etc.), optical disc drives and/or media, non- volatile random access memory (NVRAM), and/or the like. Like volatile memory 40 nonvolatile memory 42 may include a cache area for temporary storage of data. The memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the mobile terminal for performing functions of the mobile terminal. For example, the memories may comprise an identifier, such as an international mobile equipment identification (FMEI) code, capable of uniquely identifying the mobile terminal 10.
Returning to FIG. 1, in an example embodiment, the terminal 102 includes various means, such as one or more of a processor 110, memory 112, communication interface 114, user interface 116, or carrier coordination unit 118 for performing the various functions herein described. These means of the terminal 102 as described herein may be embodied as, for example, hardware elements (e.g., a suitably programmed processor, combinational logic circuit, and/or the like), a computer program product comprising computer-readable program instructions (e.g., software or firmware) stored on a computer-readable medium (e.g. memory 112) that is executable by a suitably configured processing device (e.g., the processor 110), or some combination thereof. The processor 110 may, for example, be embodied as various means including one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or FPGA (field programmable gate array), or some combination thereof. Accordingly, although illustrated in FIG. 1 as a single processor, in some embodiments the processor 110 comprises a plurality of processors. The plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of the terminal 102 as described herein. In an example embodiment, the processor 1 10 is configured to execute instructions stored in the memory 112 or otherwise accessible to the processor 110. These instructions, when executed by the processor 110, may cause the terminal 102 to perform one or more of the functionalities of the terminal 102 as described herein. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 110 may comprise an entity capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor 110 is embodied as an ASIC, FPGA or the like, the processor 110 may comprise specifically configured hardware for conducting one or more operations described herein. Alternatively, as another example, when the processor 110 is embodied as an executor of instructions, such as may be stored in the memory 112, the instructions may specifically configure the processor 110 to perform one or more algorithms and operations described herein.
The memory 112 may include, for example, volatile and/or non-volatile memory. Although illustrated in FIG. 1 as a single memory, the memory 112 may comprise a plurality of memories. The memory 112 may comprise volatile memory, non-volatile memory, or some combination thereof. In this regard, the memory 112 may comprise, for example, a hard disk, random access memory, cache memory, flash memory, a compact disc read only memory (CD- ROM), digital versatile disc read only memory (DVD-ROM), an optical disc, circuitry configured to store information, or some combination thereof. The memory 112 may be configured to store information, data, applications, instructions, or the like for enabling the terminal 102 to carry out various functions in accordance with example embodiments of the present invention. For example, in at least some embodiments, the memory 112 is configured to buffer input data for processing by the processor 110. Additionally or alternatively, in at least some embodiments, the memory 1 12 is configured to store program instructions for execution by the processor 110. The memory 112 may store information in the form of static and/or dynamic information. This stored information may be stored and/or used by the carrier coordination unit 1 18 during the course of performing its functionalities.
The communication interface 114 may be embodied as any device or means embodied in hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., the memory 112) and executed by a processing device (e.g., the processor 110), or a combination thereof that is configured to receive and/or transmit data from/to the base station 104 over the communication link 108. In at least one embodiment, the communication interface 114 is at least partially embodied as or otherwise controlled by the processor 110. In this regard, the communication interface 114 may be in communication with the processor 110, such as via a bus. The communication interface 114 may include, for example, an antenna, a transmitter, a receiver, a transceiver and/or supporting hardware or software for enabling communications with the base station 104. The communication interface 114 may be configured to receive and/or transmit data using any protocol that may be used for communications between entities of the system 100. Accordingly, the communication interface 114 may be configured to receive and/or transmit data over the communications link 108 in accordance with the standards of a broadband wireless access network implemented on the network 106, such as, for example, in accordance with the standards of an 802.16 network. The communication interface 114 may additionally be in communication with the memory 112, user interface 116, and/or carrier coordination unit 118, such as via a bus.
The user interface 116 may be in communication with the processor 110 to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user. As such, the user interface 116 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, and/or other input/output mechanisms. The user interface 116 may provide an interface allowing a user to subscribe/unsubscribe to MBS content, initiate/stop reception of MBS content, and/or the like. The user interface 116 may be in communication with the memory 112, communication interface 1 14, and/or carrier coordination unit 118, such as via a bus.
The carrier coordination unit 118 may be embodied as various means, such as hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., the memory 112) and executed by a processing device (e.g., the processor 110), or some combination thereof and, in one embodiment, is embodied as or otherwise controlled by the processor 110. In embodiments wherein the carrier coordination unit 118 is embodied separately from the processor 110, the carrier coordination unitl 18 may be in communication with the processor 110. The carrier coordination unit 118 may further be in communication with the memory 112, communication interface 114, and/or user interface 116, such as via a bus. In some embodiments, the carrier coordination unit 118 is configured to perform at least some of the functionality of one or more of an MBS client entity, multicarrier management entity, idle mode management entity, or sleep mode management entity.
In an example embodiment, the base station 104 includes various means, such as one or more of a processor 120, memory 122, communication interface 124, or carrier assignment unit 126 for performing the various functions herein described. These means of the base station 104 as described herein may be embodied as, for example, hardware elements (e.g., a suitably programmed processor, combinational logic circuit, and/or the like), a computer program product comprising computer-readable program instructions (e.g., software or firmware) stored on a computer-readable medium (e.g. memory 122) that is executable by a suitably configured processing device (e.g., the processor 120), or some combination thereof.
The processor 120 may, for example, be embodied as various means including one or more microprocessors with accompanying digital signal processors), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or FPGA (field programmable gate array), or some combination thereof. Accordingly, although illustrated in FIG. 1 as a single processor, in some embodiments the processor 120 comprises a plurality of processors. The plurality of processors may be embodied on a single computing device or distributed among a plurality of computing devices, which may be collectively configured to function as a base station 104. The plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of the base station 104 as described herein. In an example embodiment, the processor 120 is configured to execute instructions stored in the memory 122 or otherwise accessible to the processor 120. These instructions, when executed by the processor 120, may cause the base station 104 to perform one or more of the functionalities of the base station 104 as described herein. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 120 may comprise an entity capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor 120 is embodied as an ASIC, FPGA or the like, the processor 120 may comprise specifically configured hardware for conducting one or more operations described herein. Alternatively, as another example, when the processor 120 is embodied as an executor of instructions, such as may be stored in the memory 122, the instructions may specifically configure the processor 120 to perform one or more algorithms and operations described herein.
The memory 122 may include, for example, volatile and/or non-volatile memory. Although illustrated in FIG. 1 as a single memory, the memory 122 may comprise a plurality of memories. The memory 122 may comprise volatile memory, non-volatile memory, or some combination thereof. In this regard, the memory 122 may comprise, for example, a hard disk, random access memory, cache memory, flash memory, a compact disc read only memory (CD- ROM), digital versatile disc read only memory (DVD-ROM), an optical disc, circuitry configured to store information, or some combination thereof. The memory 122 may be configured to store information, data, applications, instructions, or the like for enabling the base station 104 to carry out various functions in accordance with example embodiments of the present invention. For example, in at least some embodiments, the memory 122 is configured to buffer input data for processing by the processor 120. Additionally or alternatively, in at least some embodiments, the memory 122 is configured to store program instructions for execution by the processor 120. The memory 122 may store information in the form of static and/or dynamic information. This stored information may be stored and/or used by the carrier assignment unit 126 during the course of performing its functionalities.
The communication interface 124 may be embodied as any device or means embodied in hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., the memory 122) and executed by a processing device (e.g., the processor 120), or a combination thereof that is configured to receive and/or transmit data from/to a terminal 102 over the communication link 108. In at least one embodiment, the communication interface 124 is at least partially embodied as or otherwise controlled by the processor 120. In this regard, the communication interface 124 may be in communication with the processor 120, such as via a bus. The communication interface 124 may include, for example, an antenna, a transmitter, a receiver, a transceiver and/or supporting hardware or software for enabling communications with a terminal 102. The communication interface 124 may be configured to receive and/or transmit data using any protocol that may be used for communications between entities of the system 100. Accordingly, the communication interface 124 may be configured to receive and/or transmit data over the communications link 108 in accordance with the standards of a broadband wireless access network implemented on the network 106, such as, for example, in accordance with the standards of an 802.16 network. The communication interface 124 may additionally be in communication with the memory 122 and/or carrier assignment unit 128, such as via a bus.
The carrier assignment unit 126 may be embodied as various means, such as hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (e.g., the memory 122) and executed by a processing device (e.g., the processor 120), or some combination thereof and, in one embodiment, is embodied as or otherwise controlled by the processor 120. In embodiments wherein the carrier assignment unit 126 is embodied separately from the processor 120, the carrier assignment unit 126 may be in communication with the processor 120. The carrier assignment unit 126 may further be in communication with the memory 122 and/or communication interface 124, such as via a bus. In some embodiments, the carrier coordination unit 118 is configured to perform at least some of the functionality of one or more of an MBS agent entity, multicarrier management entity, idle mode management entity, or sleep mode management entity.
The terminal 102 and base station 104 may, via the communication interfaces 114 and 124, transmit/receive data using one or more carriers over the communication link 108. In this regard, the base station 104 may be configured to support multicarrier operation. Communication between the terminal 102 and base station 104 may occur on multiple radio frequency carriers simultaneously, which is referred to as carrier aggregation, or aggregate mode of multicarrier operation. In carrier aggregation, the communication interface 114 may have multiple radios. The carrier coordination unit 118 in combination with the communication interface 114 may be configured to maintain the physical layer connection of the terminal 102 and monitor the control information on the primary carrier even while using other radios for secondary carriers. Alternatively, the terminal 102 and base station 104 may communicate using carrier switching mode, wherein the terminal 102 may alternate between multiple RF carriers but not use any two carriers simultaneously. Accordingly, when operating in carrier switching mode, the carrier combination unit 118 in combination with the communication interface 114 may be configured to switch the physical layer connection of the terminal 102 from the primary carrier to a secondary carrier according to instructions received from the base station 104.
In some example embodiments, a primary carrier is always fully configured. In a fully configured carrier, all of the control channels, including synchronization, broadcast, multicast, and unicast control signaling may be configured. Information and parameters regarding multi- carrier operation and other carriers may be transmitted in the control channels of a fully configured carrier. A secondary carrier may be either fully configured or partially configured. In this regard, a secondary carrier may be more or less just a data pipe and may be used for MBS content transmission. In a partially configured carrier, some or all the control channels are omitted, but one or more control channels may be configured to support traffic exchanges during multi -carrier operation. A partially configured carrier may, for example, comprise a downlink only carrier used for MBS content transmission.
A terminal 102 may have one primary carrier and, optionally, one or more secondary carriers assigned to it by the base station 104.
Facilitating Multicarrier and MBS Coordination through Provision of Information to Base Station Some example embodiments facilitate multicarrier and MBS coordination through the provision of information about MBS content being received by the terminal 102 to the base station 104. These example embodiments may, for example, provide an enhancement to the MBS Application track for WiMAX systems.
The carrier coordination unit 1 18 may be configured to detect an occurrence of an event affecting MBS content received by the terminal 102 over the network 106. The terminal 102 may receive the MBS control signaling at an application layer, such as in accordance with the MBS Application Track for WiMAX systems. An event affecting MBS content may comprise, for example, the terminal 102 joining an MBS service, the terminal 102 leaving an MBS service, the terminal 102 initiating MBS service reception, the terminal 102 stopping MBS service reception, a handover of the terminal 102 from a first base station 104 to a second base station 104, network re-entry, idle mode selection of a base station 104, initial network entry and/or the like. In an example scenario of an event affecting MBS content, the terminal 102 may be receiving MBS content from a radio access transmission other than from a broadband wireless access network. For example, the terminal 102 may be receiving MBS content from a wireless local area network operating in accordance with IEEE 802.11 standards over an 802.11 radio of the communication interface 114. The terminal 102 may switch to a broadband wireless access network radio and make an initial network entry to the base station 104. This event of initial network entry may thus affect MBS content received by the terminal 102.
In response to detection of such an event, the carrier coordination unit 118 may be configured to provide information about MBS content being received by the terminal 102 to a base station 104. The carrier coordination unit 118 may be configured to provide the information in a dedicated management message or as an added attribute or parameter of a message, such as, for example, a Ranging Request message (RNG-REQ). The information provided to the base station 104 may, for example, comprise a multicast and broadcast service zone identification (MBS-Zone ID), one or more identifiers for MBS content (e.g., multicast connection identifiers (MCIDs), and/or the like. The carrier assignment unit 126 may be configured to receive information provided by the terminal 102 about MBS content being received by the terminal 102. The carrier assignment unit 126 may be further configured to assign to the terminal 102 one or more carriers for receipt of the MBS content based at least in part upon the received information. For example, a carrier configuration may resemble the following: Carrier 1 : Unicast only
Carrier 2: Mixed unicast and MBS content with MCIDs 1-5 Carrier 3: Dedicated MBS carrier: MCIDs 6-15 Carrier 4: Unicast only
Accordingly, the carrier assignment unit 126 may configure a carrier for a specific type of data content, such as unicast only, mixed unicast and MBS content, dedicated MBS content, and/or the like. Further, for a carrier configured for transmission of MBS content, the carrier assignment unit 126 may configure the carrier for specific multicasts and/or broadcast content (e.g., only MCIDs 1-5 on carrier 2 and MCIDs 6-15 on carrier 3).
Based at least in part upon the information provided by the terminal 102, the carrier assignment unit 126 may be configured to assign appropriate carriers to the terminal (e.g., for MBS content and/or unicast data). For example, if the terminal 102 is receiving MBS content with MCID 4, then using the above example carrier configuration, the carrier assignment unit 126 may assign to the terminal 102 at least carrier 2 either as a primary or secondary carrier. In another example, if the terminal 102 is receiving MBS content with MCIDs 3 and 8, the carrier assignment unit 126 may assign carrier 3 to the terminal as a secondary carrier (dedicated MBS carrier cannot be a primary carrier) and carrier 2 as either a primary or secondary carrier. The carrier assignment unit 126 may further assign one or more other carriers to the terminal 102 for unicast data exchange if needed.
The carrier assignment unit 126 may be configured to send the assignment to the terminal 102. The carrier assignment unit 126 may be further configured to store the assignment in the memory 122.
The carrier coordination unit 118 may be configured to receive the assignment sent by the base station 104. The carrier coordination unit 118 may use the one or more assigned carriers in accordance with any restrictions imposed on their usage by the base station 104. In this regard, the carrier coordination unit 118 may use an appropriately configured assigned carrier for MBS content reception. The carrier coordination unit 1 18 may be configured to further store information about the one or more assigned carriers in the memory 112. The carrier assignment unit 126 may be configured to generate a resource allocation (e.g., a MAP, MBS-MAP, and/or the like) defining when MBS content is scheduled and/or on what carrier it is to be transmittedlO2. The scheduling may be common across an entire MBS zone, and not just to a single base station 104. The carrier assignment unit 126 may send the resource allocation to the terminal 102. The carrier coordination unit 118 may be configured to receive a resource allocation sent by the base station 104 and may use information included in the resource allocation to schedule receipt of MBS content on appropriate carrier(s). The carrier coordination unit 118 may further store the received resource allocation in the memory 112.
In the event of a handover of the terminal 102 from a serving base station 104 to a target base station 104, the carrier assignment unit 126 of the serving base station 104 may be configured to transfer MBS information about MBS content the terminal 102 is receiving to the target base station 104. The carrier assignment unit 126 may be configured to transfer the information over an access service network (ASN) interface between the serving base station 104 and target base station 104. The carrier assignment unit 126 of the target base station 104 may assign one or more carriers to the terminal 102 based at least in part upon the transferred MBS information. Accordingly, interruption time for MBS reception during handover may be reduced. Alternatively, in the event of a handover of the terminal 102 from a serving base station 104 to a target base station 104, the carrier coordination unit 118 may be configured to provide information about MBS content being received by the terminal 102 to the target base station 104 during network re-entry.
When the terminal 102 is handed over to a target base station 104 belonging to a different MBS zone than the serving base station 104, current identifications for MBS content (e.g., MCIDs or the like) being received by the terminal 102 may not be applicable in the target base station 104. Accordingly, the carrier assignment unit 126 of the target base station 104 may be configured to map MBS content information provided by the terminal 102 to derive identifications for MBS content that are applicable to the MBS zone of the target base station 104. The mapping may be static and thus may be preconfigured for the target base station 104 and stored in the memory 122. The carrier assignment unit 126 may then send the derived mapping to the terminal 102 and the carrier coordination unit 118 may update the local MBS content identifications for the terminal 102. If a static mapping is not stored in the memory 122 and the carrier assignment unit 126 cannot otherwise generate a mapping, the carrier assignment unit 126 may be configured to acquire the mapping from an MBS server/controller providing MBS content to the terminal 102.
When the terminal 102 is in idle mode and selects a new preferred target base station 104 in another MBS zone, the carrier coordination unit 118 may be configured to perform an MBS location update or network re-entry and provide information about MBS content being received by the terminal 102 to the preferred target base station 104. The carrier coordination unit 118 may include the MBS-Zone ID for the MBS zone of the terminal's previous serving base station and current identifiers for MBS content (e.g., MCIDs or the like) 104 in the information provided to the preferred target base station 104 and may provide the information as one or more parameters to a RNG-REQ message. The carrier assignment unit 126 may further perform a mapping and provide the terminal 102 with MBS content identifications appropriate for the MBS zone of the target base station 104. Alternatively, the carrier coordination unit 1 18 may be configured to acquire new identifications for MBS content for the MBS zone of the target base station 104 through passive listening to broadcast messages, such as, for example, Mobile
Neighbor Advance (MOB-NBR_ADV) messages, which may be used to transmit neighboring base station information to the terminal 102, containing MBS content identification information. The carrier coordination unit 118 may additionally or alternatively be configured to acquire MBS content identifications for the new MBS zone from an MBS server/controller. Additionally, MBS information transfer between the terminal 102 and target base station
104 during MBS zone switching may be used also for other purposes, such as, for example, triggering initiation of dynamic MBS content in new MBS zone (dynamic content is sent within MBS zone only if one or more terminals 102 will request it).
In some embodiments, the carrier assignment unit 126 is configured to assign a paging carrier to a terminal 102 based at least in part upon terminal-provided information about MBS content being received by the terminal 102. In this regard, the carrier assignment unit 126 may use one or more criteria in making the assignment of a paging carrier. For example, in the case of a terminal 102 having multiple radios and operating in aggregate mode, it may simplify paging operation or MBS reception if paging carrier is different than the carrier(s) used for MBS reception. Then the base station 104 and terminal 102 may handle MBS transmission and paging independently. In another example criterion, when the terminal 102 is operating in carrier switching mode, it may aid paging operation if the same carrier is used for both paging and MBS reception to reduce carrier switching. In this regard, paging may have higher priority and MBS reception may suffer if they are in different carriers and those operations happens at the same time. In still a further example criterion, MBS reception may be assigned to a dedicated carrier and thus the carrier assignment unit 126 cannot assign the dedicated carrier as the paging carrier.
Facilitating Multicarrier and MBS Coordination during Simultaneous Multicarrier and Sleep Mode Operation The terminal 102 may receive MBS content via a secondary carrier during sleep mode.
The carrier coordination unit 118 may be configured to manage MBS operation independent of sleep mode operation because MBS content scheduling may not be aligned to the terminal's sleep operation intervals, as MBS is often sent to multiple terminals. In some embodiments, the carrier assignment unit 126 may be configured to assign a secondary carrier for MBS only transmission and thus the terminal 102 may not need to consider the secondary carrier during sleep mode.
When the terminal 102 is operating in carrier switching mode, the terminal 102 and base station 104 may switch temporarily from the primary carrier to a secondary carrier. In this regard, the base station 104 may explicitly signal through the primary carrier to the terminal 102 to switch to a secondary carrier and may include a parameter in the signaling message indicating how long the terminal 102 is to use the secondary carrier. As MBS scheduling timing and interval may not depend on sleep mode and sleep mode listening interval lengths and timing may not be constant, collision between MBS reception and sleep mode operation may occur. To avoid collision, the terminal 102 and/or base station 104 may switch to the secondary carrier on which MBS data is received just before reception of MBS data and return to primary carrier following reception of MBS data but before any signaling is received on the primary carrier (e.g., following a listening interval). FIG. 3 illustrates a timing diagram of MBS transmission to a terminal in sleep mode according to an example embodiment. In FIG. 3, a first carrier 302 (carrier 1) comprises a primary carrier used for unicast. A second carrier 304 (Carrier 2) comprises a secondary carrier used for MBS reception. Carrier switching is made to receive MBS data from the carrier 304. In order to avoid collision, both the carrier coordination unit 118 and carrier assignment unit 126 may be configured to determine whether the beginning of the next listening interval when the terminal 102 is to switch to the primary carrier will collide with a scheduled reception of MBS data 306. If so, the carrier coordination unit 118 and carrier assignment unit 126 may be configured to extend the preceding sleep window 310 by the sleep window extension 312 so that the collision is avoided. The base station 104 may then send the unicast or signaling data 308 (e.g., a Mobile Traffic Indication (MOB_TRF-IND), which may be used to inform the terminal
102 about pending data) on the primary carrier 302 after the terminal 102 has switched back to the primary carrier 302 after the sleep window extension 312.
Facilitating Multicarrier and MBS Coordination for a Base Station Deploying Multiple Network Specifications
In some embodiments, the base station 104 may be configured to provide access to the network 106 in accordance with multiple broadband wireless access standards. By way of example, but not by limitation, the base station 104 may be configured to implement a mixed mode deployment wherein it acts as both an 802.16e and an 802.16m base station with modes separated in the time domain as illustrated in FIG. 4 In this regard, operation of the base station
104 may be divided into multiple zones. An LZone comprises a legacy zone over the period(s) of time when the base station 104 acts as an 802.16e base station. The MZone comprises the period(s) of time when the base station 104 acts as an 802.16m base station. The respective zones may be further separated in the time domain into downlink (DL) and uplink (UL) zones. Accordingly, the operation of the base station 104 may be divided into an LZone UL zone
(802.16e UL zone), LZone DL zone (802.16e DL zone), MZone UL zone (802.16m UL zone), and MZone DL zone (802.16m DL zone). It may be desirable in this situation to avoid sending the same MBS content in both the LZone and the MZone. In some embodiments, when the base station 104 is operating in MZone, the carrier coordination 118 may be configured to receive MBS content from LZone by using 802.16e methods, such as with the assistance of an MBS map. Accordingly, synchronization between .16e and .16m systems may not be needed because the carrier coordination unit 118 may listen passively and maintain (broadcasted) system information from both systems.
The carrier assignment unit 126 may be configured in some embodiments to transmit all MBS content in the 802.16e zone of the time domain to enable terminals that are not configured for operation under the 802.16m standard to receive MBS data. In some embodiments, when operating in the MZone, the carrier assignment unit 126 is configured to broadcast high level MBS control information for LZone MBS reception. For example, the Super Frame Header (SFH) of MZone may be configured to carry MBS Zone ID list for LZone. Also this MBS Zone ID list may have additional information (e.g. one bit) to indicate that MBS Zone ID is located in LZone. Such embodiments may enhance MBS operation during and/or following a handover because the terminal 102 may not need to decode a downlink channel descriptor (DCD) or a Mobile Neighbor Advance (MOB_NBR-ADV) in LZone. Further, since in such embodiments only high level MBS control information is sent through MZone, overhead due to duplicate MBS control information being sent also through LZone to support legacy terminals may be insignificant.
Flowcharts According to Example Embodiments for Facilitating Multicarrier and MBS Coordination
FIG. 5 illustrates a flowchart according to an example method for facilitating multicarrier and multicast and broadcast service coordination according to an example embodiment of the invention. In this regard, FIG. 5 illustrates operations that may occur at the terminal 102. The method may include the carrier coordination unit 118 detecting an occurrence of an event affecting MBS content received by the terminal 102 over a multicarrier broadband wireless access network, such as the network 106, at operation 500. Operation 510 may comprise the carrier coordination unit 118 providing, in response to detection of the event, information about MBS content being received to the base station 104. The carrier coordination unit 118 may receive an assignment of one or more carriers at operation 520. The base station 104 may have assigned the one or more carriers based at least in part upon the provided information.
FIG. 6 illustrates a flowchart according to an example method for facilitating multicarrier and multicast and broadcast service coordination according to an example embodiment of the invention. In this regard, FIG. 6 illustrates operations that may occur at the base station 104. The method may include the carrier assignment unit 126 receiving information about MBS content being received by a terminal 102 following occurrence of an event affecting MBS content received by terminal 102, at operation 600. Operation 610 may comprise the carrier assignment unit 126 assigning one or more carriers to the terminal 102 based at least in part upon the received information. The carrier assignment unit 126 may send the assignment to the terminal 102, at operation 620. FIGs. 5-6 are flowcharts of a system, method, and computer program product according to example embodiments. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by various means, such as hardware and/or a computer program product comprising one or more computer-readable mediums having computer readable program instructions stored thereon. For example, one or more of the procedures described herein may be embodied by computer program instructions of a computer program product. In this regard, the computer program product(s) which embody the procedures described herein may be stored by one or more memory devices of a mobile terminal, server, or other computing device and executed by a processor in the computing device. In some embodiments, the computer program instructions comprising the computer program product(s) which embody the procedures described above may be stored by memory devices of a plurality of computing devices. As will be appreciated, any such computer program product may be loaded onto a computer or other programmable apparatus to produce a machine, such that the computer program product including the instructions which execute on the computer or other programmable apparatus creates means for implementing the functions specified in the flowchart block(s). Further, the computer program product may comprise one or more computer-readable memories on which the computer program instructions may be stored such that the one or more computer- readable memories can direct a computer or other programmable apparatus to function in a particular manner, such that the computer program product comprises an article of manufacture which implements the function specified in the flowchart block(s). The computer program instructions of one or more computer program products may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus implement the functions specified in the flowchart block(s). Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer program product(s). The above described functions may be carried out in many ways. For example, any suitable means for carrying out each of the functions described above may be employed to carry out an embodiment. In one embodiment, a suitably configured processor may provide all or a portion of the elements. In another embodiment, all or a portion of the elements may be configured by and operate under control of a computer program product. The computer program product for performing the methods of example embodiments includes a computer-readable storage medium, such as the non-volatile storage medium, and computer-readable program code portions, such as a series of computer instructions, embodied in the computer-readable storage medium.
As such, then, some embodiments provide several advantages to computing devices and network operators. Some example embodiments provide terminals configured to provide information about MBS content being received by the terminal to a base station upon occurrence of an event affecting MBS content received by the terminal. Some example embodiments further provide base stations configured to assign one or more carriers to a terminal based at least in part upon information about MBS content being received by the terminal that is provided to the base station by the terminal. Accordingly, some example embodiments provide coordination of MBS content and carriers in a multicarrier broadband wireless access network. Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the embodiments of the invention are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

WHAT IS CLAIMED IS:
1. A method comprising: detecting, at a terminal, an occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal over a multicarrier broadband wireless access network; causing, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the terminal to be provided to a base station providing access to the broadband wireless access network; and receiving an assignment of one or more carriers to the terminal, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
2. The method of Claim 1, wherein the broadband wireless access network comprises a Worldwide Interoperability for Microwave Access (WiMAX) network configured to operate in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
3. The method of any of Claims 1-2, wherein the information comprises one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
4. The method of any of Claims 1-3, wherein the event comprises a handover of the terminal from a serving base station to a target base station.
5. The method of Claim 4, wherein causing the information to be provided comprises causing the information to be provided to the target base station during network reentry.
6. The method of any of Claims 1-5, further comprising receiving an assignment of a paging carrier, wherein the base station assigned the paging carrier based at least in part upon the provided information.
7. The method of any of Claims 1 -6, further comprising: receiving a resource allocation defining one or more of when one or more of multicast or broadcast service content is scheduled to be transmitted or on what channel one or more of multicast or broadcast service content is to be transmitted; and using the resource allocation to schedule receipt of one or more of multicast or broadcast service content.
8. The method of any of Claims 1-7, further comprising: determining, when in sleep mode, whether switching to an assigned primary carrier for a next listening interval will result in a collision with one or more of multicast or broadcast service content scheduled to be transmitted on an assigned secondary carrier; extending a sleep window by a sufficient sleep window extension interval to avoid the collision when it is determined that a collision will result; and switching to the primary carrier following the sleep window extension interval.
9. An apparatus comprising at least one processor and at least one memory storing computer program code, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to cause the apparatus to at least: detect an occurrence of an event affecting one or more of multicast or broadcast service content received by the apparatus over a multicarrier broadband wireless access network; cause, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the apparatus to be provided to a base station providing access to the broadband wireless access network; and receive an assignment of one or more carriers to the apparatus, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
10. The apparatus of Claim 9, wherein the broadband wireless access network comprises a Worldwide Interoperability for Microwave Access (WiMAX) network configured to operate in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
11. The apparatus of any of Claims 9-10, wherein the information comprises one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
12. The apparatus of any of Claims 9-11, wherein the event comprises a handover of the apparatus from a serving base station to a target base station.
13. The apparatus of Claim 12, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to cause the apparatus to cause the information to be provided to the target base station during network re-entry.
14. The apparatus of any of Claims 9-13, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus to receive an assignment of a paging carrier, wherein the base station assigned the paging carrier based at least in part upon the provided information.
15. The apparatus of any of Claims 9-14, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus to: receive a resource allocation defining one or more of when one or more of multicast or broadcast service content is scheduled to be transmitted or on what channel one or more of multicast or broadcast service content is to be transmitted; and use the resource allocation to schedule receipt of one or more of multicast or broadcast service content.
16. The apparatus of any of Claims 9-15, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus to: determine, when in sleep mode, whether switching to an assigned primary carrier for a next listening interval will result in a collision with one or more of multicast or broadcast service content scheduled to be transmitted on an assigned secondary carrier; extend a sleep window by a sufficient sleep window extension interval to avoid the collision when it is determined that a collision will result; and switch to the primary carrier following the sleep window extension interval.
17. The apparatus of any of Claims 9-16, wherein the apparatus comprises or is embodied on a mobile phone, the mobile phone comprising user interface circuitry and user interface software stored on one or more of the at least one memory; wherein the user interface circuitry and user interface software are configured to: facilitate user control of at least some functions of the mobile phone through use of a display; and cause at least a portion of a user interface of the mobile phone to be displayed on the display to facilitate user control of at least some functions of the mobile phone.
18. A computer program product comprising at least one tangible computer-readable storage medium having computer-readable program instructions stored therein, the computer- readable program instructions comprising: program instructions configured to detect an occurrence of an event affecting one or more of multicast or broadcast service content received by a terminal over a multicarrier broadband wireless access network; program instructions configured to cause, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the terminal to be provided to a base station providing access to the broadband wireless access network; and program instructions configured to cause receipt of an assignment of one or more carriers to the terminal, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
19. The computer program product of Claim 18, wherein the broadband wireless access network comprises a Worldwide Interoperability for Microwave Access (WiMAX) network configured to operate in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
20. The computer program product of any of Claims 18-19, wherein the information comprises one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
21. The computer program product of any of Claims 18-20, wherein the event comprises a handover of the terminal from a serving base station to a target base station.
22. The computer program product of any of Claims 18-21, wherein the program instructions configured to cause the information to be provided comprise program instructions configured to cause the information to be provided to the target base station during network reentry.
23. The computer program product of Claim 22, further comprising program instructions configured to cause receipt of an assignment of a paging carrier, wherein the base station assigned the paging carrier based at least in part upon the provided information.
24. The computer program product of any of Claims 18-23, further comprising: program instructions configured to cause receipt of a resource allocation defining one or more of when one or more of multicast or broadcast service content is scheduled to be transmitted or on what channel one or more of multicast or broadcast service content is to be transmitted; and program instructions configured to use the resource allocation to schedule receipt of one or more of multicast or broadcast service content.
25. The computer program product of any of Claims 18-24, further comprising: program instructions configured to determine, when in sleep mode, whether switching to an assigned primary carrier for a next listening interval will result in a collision with one or more of multicast or broadcast service content scheduled to be transmitted on an assigned secondary carrier; program instructions configured to extend a sleep window by a sufficient sleep window extension interval to avoid the collision when it is determined that a collision will result; and program instructions configured to switch to the primary carrier following the sleep window extension interval.
26. An apparatus comprising: means for detecting an occurrence of an event affecting one or more of multicast or broadcast service content received by the apparatus over a multicarrier broadband wireless access network; means for causing, in response to detection of the event, information about one or more of multicast or broadcast service content being received by the apparatus to be provided to a base station providing access to the broadband wireless access network; and means for receiving, from the base station, an assignment of one or more carriers to the apparatus, wherein the base station assigned the one or more carriers based at least in part upon the provided information.
27. The apparatus of Claim 26, wherein the broadband wireless access network comprises a Worldwide Interoperability for Microwave Access (WiMAX) network configured to operate in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
28. The apparatus of any of Claims 26-27, wherein the information comprises one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
29. The apparatus of any of Claims 26-28, wherein the event comprises a handover of the terminal from a serving base station to a target base station.
30. The apparatus of Claim 29, wherein the means for causing the information to be provided comprises means for causing the information to be provided to the target base station during network re-entry.
31. The apparatus of any of Claims 26-30, further comprising means for receiving an assignment of a paging carrier, wherein the base station assigned the paging carrier based at least in part upon the provided information.
32. The apparatus of any of Claims 26-31 , further comprising: means for receiving a resource allocation defining one or more of when one or more of multicast or broadcast service content is scheduled to be transmitted or on what channel one or more of multicast or broadcast service content is to be transmitted; and means for using the resource allocation to schedule receipt of one or more of multicast or broadcast service content.
33. The apparatus of any of Claims 26-32, further comprising: means for determining, when in sleep mode, whether switching to an assigned primary carrier for a next listening interval will result in a collision with one or more of multicast or broadcast service content scheduled to be transmitted on an assigned secondary carrier; means for extending a sleep window by a sufficient sleep window extension interval to avoid the collision when it is determined that a collision will result; and means for switching to the primary carrier following the sleep window extension interval.
34. A method comprising: receiving, at a base station configured to provide access to a multicarrier broadband wireless access network, information about one or more of multicast or broadcast service content being received by a terminal over the broadband wireless access network in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal; assigning one or more carriers to the terminal based at least in part upon the received information; and causing the assignment of the one or more carriers to be sent to the terminal.
35. The method of Claim 34, wherein the broadband wireless access network comprises a Worldwide Interoperability for Microwave Access (WiMAX) network configured to operate in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
36. The method of any of Claims 34-35, wherein the information comprises one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
37. The method of any of Claims 34-36, further comprising causing the received information to be transferred to a target base station in response to handover of the terminal from the base station to the target base station.
38. The method of any of Claims 34-37, further comprising: assigning a paging carrier to the terminal based at least in part upon the received information; and causing the assignment of the paging carrier to be sent to the terminal.
39. The method of any of Claims 34-38, further comprising: causing a resource allocation to be sent to the terminal, the resource allocation defining one or more of when one or more of multicast or broadcast service content is scheduled to be transmitted or on what channel one or more of multicast or broadcast service content is to be transmitted.
40. The method of any of Claims 34-39, further comprising: determining, when the terminal is in sleep mode, whether transmission of data on a primary carrier assigned to the terminal during a next listening interval will result in a collision with one or more of multicast or broadcast service content scheduled to be transmitted on a secondary carrier assigned to the terminal; extending a sleep window by a sufficient sleep window extension interval to avoid the collision when it is determined that a collision will result; and causing transmission of data on the primary carrier following the sleep window extension interval.
41. The method of any of Claims 34-40, wherein the base station is configured to provide access to the multicarrier broadband wireless access network in accordance with a first protocol during a first time segment and in accordance with a second protocol during a second time segment, the method further comprising: causing, in the first time segment, broadcast of control information for content reception in the second time segment.
42. An apparatus comprising at least one processor and at least one memory storing computer program code, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to cause the apparatus to at least: receive information about one or more of multicast or broadcast service content being received by a terminal over a broadband wireless access network in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal; assign one or more carriers to the terminal based at least in part upon the received information; and cause the assignment of the one or more carriers to be sent to the terminal.
43. The apparatus of Claim 42, wherein the broadband wireless access network comprises a Worldwide Interoperability for Microwave Access (WiMAX) network configured to operate in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
44. The apparatus of any of Claims 42-43, wherein the information comprises one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
45. The apparatus of any of Claim 42-44, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus to cause the received information to be transferred to a target base station in response to handover of the terminal from the apparatus to the target base station.
46. The apparatus of any of Claims 42-45, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus to: assign a paging carrier to the terminal based at least in part upon the received information; and cause the assignment of the paging carrier to be sent to the terminal.
47. The apparatus of any of Claims 42-46, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus to: cause a resource allocation to be sent to the terminal, the resource allocation defining one or more of when one or more of multicast or broadcast service content is scheduled to be transmitted or on what channel one or more of multicast or broadcast service content is to be transmitted.
48. The apparatus of any of Claims 42-47, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to cause the apparatus to: determine, when the terminal is in sleep mode, whether transmission of data on a primary carrier assigned to the terminal during a next listening interval will result in a collision with one or more of multicast or broadcast service content scheduled to be transmitted on a secondary carrier assigned to the terminal; extend a sleep window by a sufficient sleep window extension interval to avoid the collision when it is determined that a collision will result; and cause transmission of data on the primary carrier following the sleep window extension interval.
49. The apparatus of any of Claims 42-48, wherein the at least one memory and stored computer program code are configured, with the at least one processor, to further cause the apparatus to: control access to the multicarrier broadband wireless access network in accordance with a first protocol during a first time segment and in accordance with a second protocol during a second time segment; and cause, in the first time segment, broadcast of control information for content reception in the second time segment.
50. A computer program product comprising at least one tangible computer-readable storage medium having computer-readable program instructions stored therein, the computer- readable program instructions comprising: program instructions configured to cause receipt of information about one or more of multicast or broadcast service content being received by a terminal over a broadband wireless access network in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal; program instructions configured to assign one or more carriers to the terminal based at least in part upon the received information; and program instructions configured to cause the assignment of the one or more carriers to be sent to the terminal
51. The computer program product of Claim 50, wherein the broadband wireless access network comprises a Worldwide Interoperability for Microwave Access (WiMAX) network configured to operate in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
52. The computer program product of any of Claims 50-51 , wherein the information comprises one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
53. The computer program product of any of Claims 50-52, further comprising program instructions configured to cause the received information to be transferred to a target base station in response to handover of the terminal to the target base station.
54. The computer program product of any of Claims 50-53, further comprising: program instructions configured to assign a paging carrier to the terminal based at least in part upon the received information; and program instructions configured to cause the assignment of the paging carrier to be sent to the terminal.
55. The computer program product of any of Claims 50-54, further comprising: program instructions configured to cause a resource allocation to be sent to the terminal, the resource allocation defining one or more of when one or more of multicast or broadcast service content is scheduled to be transmitted or on what channel one or more of multicast or broadcast service content is to be transmitted.
56. The computer program product of any of Claims 50-55, further comprising: program instructions configured to determine, when the terminal is in sleep mode, whether transmission of data on a primary carrier assigned to the terminal during a next listening interval will result in a collision with one or more of multicast or broadcast service content scheduled to be transmitted on a secondary carrier assigned to the terminal; program instructions configured to extend a sleep window by a sufficient sleep window extension interval to avoid the collision when it is determined that a collision will result; and program instructions configured to cause transmission of data on the primary carrier following the sleep window extension interval.
57. The computer program product of any of Claims 50-56, further comprising: program instructions configured to control access to the multicarrier broadband wireless access network in accordance with a first protocol during a first time segment and in accordance with a second protocol during a second time segment; and program instructions configured to cause, in the first time segment, broadcast of control information for content reception in the second time segment.
58. An apparatus comprising: means for receiving information about one or more of multicast or broadcast service content being received by a terminal over a broadband wireless access network in response to occurrence of an event affecting one or more of multicast or broadcast service content received by the terminal; means for assigning one or more carriers to the terminal based at least in part upon the received information; and means for causing the assignment of the one or more carriers to be sent to the terminal.
59. The apparatus of Claim 58, wherein the broadband wireless access network comprises a Worldwide Interoperability for Microwave Access (WiMAX) network configured to operate in accordance with Institute of Electrical and Electronics Engineers (IEEE) 802.16m standards.
60. The apparatus of any of Claims 58-59, wherein the information comprises one or more of a multicast and broadcast service zone identification, one or more multicast connection identifiers (MCIDs), or one or more identifiers corresponding to one or more of received multicast or broadcast service content.
61. The apparatus of any of Claims 58-60, further comprising means for causing the received information to be transferred to a target base station in response to handover of the terminal to the target base station.
62. The apparatus of any of Claims 58-61 further comprising: means for assigning a paging carrier to the terminal based at least in part upon the received information; and means for causing the assignment of the paging carrier to be sent to the terminal.
63. The apparatus of any of Claims 58-62, further comprising: means for causing a resource allocation to be sent to the terminal, the resource allocation defining one or more of when one or more of multicast or broadcast service content is scheduled to be transmitted or on what channel one or more of multicast or broadcast service content is to be transmitted.
64. The apparatus of any of Claims 58-63, further comprising: means for determining, when the terminal is in sleep mode, whether transmission of data on a primary carrier assigned to the terminal during a next listening interval will result in a collision with one or more of multicast or broadcast service content scheduled to be transmitted on a secondary carrier assigned to the terminal; means for extending a sleep window by a sufficient sleep window extension interval to avoid the collision when it is determined that a collision will result; and means for causing transmission of data on the primary carrier following the sleep window extension interval.
65. The apparatus of any of Claims 58-64, further comprising: means for controlling access to the multicarrier broadband wireless access network in accordance with a first protocol during a first time segment and in accordance with a second protocol during a second time segment; and means for causing, in the first time segment, broadcast of control information for content reception in the second time segment.
PCT/IB2010/001005 2009-05-01 2010-05-03 Systems, methods, and apparatuses for facilitating multicarrier and multicast and broadcast service coordination WO2010125460A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US17468009P 2009-05-01 2009-05-01
US61/174,680 2009-05-01

Publications (1)

Publication Number Publication Date
WO2010125460A1 true WO2010125460A1 (en) 2010-11-04

Family

ID=43031759

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2010/001005 WO2010125460A1 (en) 2009-05-01 2010-05-03 Systems, methods, and apparatuses for facilitating multicarrier and multicast and broadcast service coordination

Country Status (1)

Country Link
WO (1) WO2010125460A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007149349A2 (en) * 2006-06-19 2007-12-27 Lucent Technologies Inc. Method for coordinated control of radio resources for multicasting in a distributed wireless system
US20080037460A1 (en) * 2006-08-14 2008-02-14 Muthaiah Venkatachalam Broadband wireless access network and method for providing multicast broadcast services within multicast broadcast service zones
WO2008024214A2 (en) * 2006-08-21 2008-02-28 Interdigital Technology Corporation Multi-cell coordination for multimedia broadcast multicast services in a wireless communication system
WO2008109568A1 (en) * 2007-03-02 2008-09-12 Zte (Usa) Inc. Wimax multicast broadcast network system architecture
US20080259835A1 (en) * 2007-04-20 2008-10-23 Muthaiah Venkatachalam Locating content in broadband wireless access networks
US20090041045A1 (en) * 2007-08-09 2009-02-12 Industrial Technology Research Institute System and method for providing multicast/broadcast services in a wireless network

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007149349A2 (en) * 2006-06-19 2007-12-27 Lucent Technologies Inc. Method for coordinated control of radio resources for multicasting in a distributed wireless system
US20080037460A1 (en) * 2006-08-14 2008-02-14 Muthaiah Venkatachalam Broadband wireless access network and method for providing multicast broadcast services within multicast broadcast service zones
WO2008024214A2 (en) * 2006-08-21 2008-02-28 Interdigital Technology Corporation Multi-cell coordination for multimedia broadcast multicast services in a wireless communication system
WO2008109568A1 (en) * 2007-03-02 2008-09-12 Zte (Usa) Inc. Wimax multicast broadcast network system architecture
US20080259835A1 (en) * 2007-04-20 2008-10-23 Muthaiah Venkatachalam Locating content in broadband wireless access networks
US20090041045A1 (en) * 2007-08-09 2009-02-12 Industrial Technology Research Institute System and method for providing multicast/broadcast services in a wireless network

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ETEMAD K. ET AL: "Multicast and broadcast multimedia services in mobile WiMax networks", COMMUNICATIONS MAGAZINE, IEEE, vol. 47, no. 10, October 2009 (2009-10-01), pages 84 - 91, XP011283320, Retrieved from the Internet <URL:http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5273813&isnumber=5273796> *
GUR G. ET AL: "On the use of WiMAX as the terrestrial segment for DVB-SH networks", SATELLITE AND SPACE COMMUNICATIONS, 2008. IWSSC 2008. IEEE INTERNATIONAL WORKSHOP ON, 1 October 2008 (2008-10-01) - 3 October 2008 (2008-10-03), pages 326 - 330, XP031352199, Retrieved from the Internet <URL:http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4656824&isnumber=4656720> *
NING LIAO ET AL.: "Optimized Multicast Service Management in a Mobile WiMAX TV System", 6TH IEEE CONSUMER COMMUNICATIONS AND NETWORKING CONFERENCE, 2009. CCNC 2009., 10 January 2009 (2009-01-10) - 13 January 2009 (2009-01-13), pages 1 - 5, XP031425415, Retrieved from the Internet <URL:http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4784709&isnumber=4784684> *

Similar Documents

Publication Publication Date Title
US11172525B2 (en) Method and apparatus for transmitting and receiving signal in communication system supporting device to device scheme
US10674380B2 (en) On-demand system information for wireless terminal in connected state
US8374625B2 (en) Neighborhood paging group design for wireless networks
US8705488B2 (en) Method for supporting idle mode in wireless local area network system
US8432870B2 (en) Handover techniques between legacy and updated wireless networks
EP2293605B1 (en) Method of handling multimedia broadcast and multicast service transmission and reception and related communication device
CN108055681B (en) Method of mobility management in cellular system and apparatus therefor
WO2017193380A1 (en) Communication method and device
US10334660B2 (en) Signalling about on-going and starting broadcast-service sessions on other frequency carriers
JP2020074540A (en) Techniques for transmitting data over unlicensed radio frequency spectrum band in accordance with agreement between operators
US8743766B2 (en) Method and system for network discovery and selection in wireless network systems
US9049687B2 (en) System and method for providing multicast and/or broadcast services
WO2010068454A2 (en) Mobility management method and system for multicast and broadcast services
EP2975885A1 (en) Method and apparatus for wireless communication
WO2016141752A1 (en) Cell selection method, anr configuration method, device and computer storage medium
US8738070B2 (en) Wireless communication system, wireless base station, wireless communication method, and program
US20160157281A1 (en) Consolidation of management communications in a network environment
US8743827B2 (en) Switching method and apparatus in broadband wireless communication system
US9392506B2 (en) Method of transmitting cell identity information
WO2023024836A1 (en) Uplink synchronization method, terminal, and storage medium
WO2016058499A1 (en) System and method for reducing communications overhead
US20150139189A1 (en) Method and apparatus for managing information in a communication system
WO2010125460A1 (en) Systems, methods, and apparatuses for facilitating multicarrier and multicast and broadcast service coordination
US20130315123A1 (en) Method and Apparatus for Cellular Signaling
WO2014056173A1 (en) Cellular assisted non-cellular access point discovery

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10769388

Country of ref document: EP

Kind code of ref document: A1