Method and apparatus for performing hybrid per station and per flow uplink allocations
Abstract
This record has no abstract on file.
Term
4.4 yearsleft in the term
Expires 28 February 2031.
- Priority
- Filed
- Granted
- Today
- Expires
20 claims: 3 independent, 17 dependent
- 1ハイブリッド式の局ごとおよびフローごと に アップリンク割り当てを実行するための方法であって、 少なくとも1つのフローに関するアップリンクリソース割り当てを要求するステップと、 アップリンクリソース割り当てを受信するステップと、 前記 割り当てられたアップリンクリソースに関する意図され た フロー情報 の 利用可能 性 を判定するステップと、 前記意図され た フロー情報が利用可能である という条件で 、 前記 割り当てられたアップリンクリソースに関する利用可能な 前記 意図され た フロー情報 の 適用可能 性 を判定するステップと、 前記意図され た フロー情報が適用可能である という条件で 、前記意図され た フロー情報の適用 の上で 、前記割り当てられたアップリンクリソースを用いてデータを送信するステップであって、前記割り当てられたアップリンクリソースの使用は、 基地局決定である 、ステップと、 前記意図され た フロー情報が利用不可能である という条件で 、前記割り当てられたアップリンクリソースを用いてデータを送信するステップであって、前記割り当てられたアップリンクリソースの使用は、局 決定 である、ステップと を含むことを特徴とする方法。
- 2前記意図され た フロー情報の 前記 適用は、前記割り当てられたアップリンクリソースの使用に関して、意図され た フローに優先度を割り振ることを特徴とする請求項1に記載の方法。
- 3前記割り当てられたアップリンクリソースは、アップリンクの永続的割り当てリソースまたはアップリンクのグループリソース割り当てリソースのうちの少なくとも1つであることを特徴とする請求項1に記載の方法。
- 4少 なくとも1つの 前記 フローは、グループに関連付けられることを特徴とする請求項3に記載の方法。
- 5前記意図され た フロー情報の 前記 適用は、 前記 意図され た フローを 供給 した後、残ったアップリンクリソースを用い て その他のフローの送信を許すことを特徴とする請求項1に記載の方法。
- 6前記意図され た フロー情報の 前記 適用は、少なくとも1つのその他のフローからの緊急のデータの送信を許すことを特徴とする請求項1に記載の方法。
- 7前記意図され た フロー情報は、永続的割り当て情報要素の巡回冗長検査を局の識別情報およびフローの識別情報を用いてマスクすることによって与えられることを特徴とする請求項3に記載の方法。
- 8前記意図され た フロー情報は、フローとアップリンクの永続的割り当てリソースとの間で割り当て周期性または割り当てサイズのうちの少なくとも1つをマッチングすることによって決定される前記アップリンクの永続的割り当てリソースに関することを特徴とする請求項1に記載の方法。
- 9ハイブリッド式の局ごとおよびフローごとのアップリンク割り当てを実行するための無線送受信ユニット(WTRU)であって、 送信機と、 受信機と、 前記受信機および前記送信機と通信 す るプロセッサとを備え、 前記プロセッサは、少なくとも1つのフローに関するアップリンクリソース割り当てを要求するように構成され、 前記受信機は、アップリンクリソース割り当てを受信するように構成され、 前記プロセッサは、 前記 割り当てられたアップリンクリソースに関する意図され た フロー情報 の 利用可能 性 を判定するように構成され、 前記意図されたフロー情報が利用可能であるという条件で、 前記プロセッサは 、 割り当てられたアップリンクリソースに関する利用可能な 前記 意図され た フロー情報 の 適用可能 性 を判定するように構成され、 前記意図されたフロー情報が適用可能であるという条件で、 前記送信機は 、 前記意図され た フロー情報の適用 の上で 、前記割り当てられたアップリンクリソースを用いてデータを送信するように構成され、前記割り当てられたアップリンクリソースの使用は、 基地局決定 であり、 前記意図されたフロー情報が利用不可能であるという条件で、 前記送信機は 、 前記割り当てられたアップリンクリソースを用いてデータを送信するように構成され、前記割り当てられたアップリンクリソースの使用は、局 決定 であることを特徴とする無線送受信ユニット(WTRU)。
- 10前記意図され た フロー情報の 前記 適用は、前記割り当てられたアップリンクリソースの使用に関して、意図され た フローに優先度を割り振ることを特徴とする請求項 9 に記載のWTRU。
- 11前記緊急のデータは、緊急媒体アクセス制御(MAC)メッセージであることを特徴とする請求項6に記載の方法。
- 12前記緊急のデータは、救急サービスデータであることを特徴とする請求項6に記載の方法。
- 13前記割り当てられたアップリンクリソースは、アップリンクの永続的割り当てリソースまたはアップリンクのグループリソース割り当てリソースのうちの少なくとも1つであることを特徴とする請求項9に記載のWTRU。
- 14少なくとも1つの前記フローは、グループに関連付けられることを特徴とする請求項13に記載のWTRU。
- 15前記意図されたフロー情報の前記適用は、前記意図されたフローを供給した後、残ったアップリンクリソースを用いてその他のフローの送信を許すことを特徴とする請求項9に記載のWTRU。
- 16前記意図されたフロー情報の前記適用は、少なくとも1つのその他のフローからの緊急のデータの送信を許すことを特徴とする請求項9に記載のWTRU。
- 17前記緊急のデータは、緊急媒体アクセス制御(MAC)メッセージであることを特徴とする請求項16に記載のWTRU。
- 18前記緊急のデータは、救急サービスデータであることを特徴とする請求項16に記載のWTRU。
- 19前記意図されたフロー情報は、永続的割り当て情報要素の巡回冗長検査を局の識別情報およびフローの識別情報を用いてマスクすることによって与えられることを特徴とする請求項13に記載のWTRU。
- 20前記意図されたフロー情報は、フローとアップリンクの永続的割り当てリソースとの間で割り当て周期性または割り当てサイズのうちの少なくとも1つをマッチングすることによって決定される前記アップリンクの永続的割り当てリソースに関することを特徴とする請求項9に記載のWTRU。
Independent claims20
160 paragraphs, as filed
[Cross-reference to related applications] This application claims the benefit of US Patent Provisional Application No. 61 / 309,135 filed on March 1, 2010, the content of which provisional application is by reference. Incorporated herein.
This application relates to wireless communication.
Connection-based quality of service (QoS) management using a scheduling-based medium access control mechanism can be provided in wireless communications. For example, in the Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16 medium access control (MAC) can provide connection-based QoS management using a scheduling-based medium access control mechanism. With respect to uplinks (UL), subscribers can signal their subscribers' UL resource needs for each UL connection / service flow, and base stations can grant UL resources to subscribers. it can. However, the granting of base stations may not correspond to each individual connection / service flow. In other words, UL resource requests can be per connection and UL resource allocation can be per subscriber station. This is an allocation map Map) (MAP) To minimize resource allocation overhead by having the Information Element (IE) allocate resources for multiple subscriber connections, and / or streamline the UL resources allocated by the subscriber. It can be done to provide flexibility for effective and effective use. For example, this can allow subscribers to meet allocated resources by concatenating MAC data from multiple connections, allowing subscribers to perform real-time adjustments. You can also do it.
There can be some cases where per-connection (also called per-flow) UL allocations can be beneficial. For example, an advanced base station (ABS) has UL resources advanced mobile. station) (AMS) based on the base station's knowledge of the UL traffic needs of its active connection in the WTRU, such as the amount of data, delay tolerance, etc., and the base station's real-time UL traffic load. Can be assigned. With respect to UL assignments, a base station may have its own intent on how UL assignments should be distributed among WTRU's active connections. However, with the typical 802.16 per-station UL assignment, the intended information of the base station may not be available in the WTRU. Therefore, it is desirable to provision such information to the AMS to help the AMS achieve better synchronization with the base station for bandwidth requirements and grants for each connection. This can reduce the probability of fragmentation and aggregate bandwidth to self-correct in the UL bandwidth request / grant process. You can also reduce the need to send request). Therefore, control overhead and processing load can be reduced, and as a result, system efficiency can be improved.
Methods for making per-flow / connection and per-station UL allocations may be needed to improve the efficiency of UL control and to further improve the utilization of UL resources.
Methods and devices for performing hybrid station-by-station and per-flow / connection uplink assignments are described. The device can implement hybrid flow / connection and station-by-station uplink (UL) resource allocation to improve UL control efficiency and UL resource utilization. The device may be configured to send or receive UL resource allocation in a signal with explicit or implicit instructions indicating the intended flow information.
A detailed understanding can be obtained from the following description given as an example along with the accompanying drawings.
<figref num="1A">FIG. 5 is a system diagram of an exemplary communication system in which one or more disclosed embodiments may be implemented.</figref><figref num="1B">FIG. 5 is a system diagram of an exemplary wireless transmit / receive unit (WTRU) that can be used in the communication system shown in FIG. 1A.</figref><figref num="1C">FIG. 5 is a system diagram of an exemplary radio access network and an exemplary core network that can be used within the communication system shown in FIG. 1A.</figref><figref num="2">An exemplary hybrid flow-by-flow and station-by-station UL resource allocation mechanism high-level flow diagram.</figref><figref num="3">Illustrative hybrid flow-by-flow and per-station UL group resource allocation where intended flow information can be signaled by group configuration messages when radio transmit / receive unit flows can be allocated to groups. ) (GRA) High-level flow diagram of the mechanism.</figref><figref num="4">Illustrative hybrid flow-by-flow and station-by-station UL GRA mechanism high-level flow diagrams where intended flow information can be signaled explicitly or implicitly when WTRUs can be assigned to groups. is there.</figref>
FIG. 1A is a diagram illustrating an exemplary communication system 100 capable of implementing one or more disclosed embodiments. The communication system 100 can be a multiple access system that provides content such as voice, data, video, messaging, and broadcasting to a plurality of wireless users. Communication system 100 allows multiple wireless users to access such content by sharing system resources, including radio bandwidth. For example, the communication system 100 is one of code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), and the like. Multiple channel access methods can be used.
As shown in FIG. 1A, the communication system 100 includes radio transmission / reception units (WTRU) 102a, 102b, 102c, 102d, radio access network (RAN) 104, core network 106, public switched telephone network (PSTN) 108, Internet 110, And other networks 112 may be included. It will be appreciated that in the disclosed embodiments, any number of WTRUs, base stations, networks, and / or network elements can be used. Each of the WTRU102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. As an example, WTRU102a, 102b, 102c, 102d can be configured to transmit and / or receive radio signals, such as user equipment (UE), mobile stations, subscribers, subscriber stations, advanced mobile stations ( AMS), fixed or mobile subscriber units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, touchpads, wireless sensors, household appliances, etc. may be included.
Communication system 100 may also include base station 114a and base station 114b. Each of the base stations 114a, 114b is of WTRU102a, 102b, 102c, 102d to facilitate access to one or more communication networks such as core network 106, internet 110, and / or network 112. It could be any type of device configured to interface wirelessly with at least one. As an example, base stations 114a and 114b are wireless base stations (BTS), advanced base stations (ABS), Node-B, eNodeB, home Node B (Home Node B), home eNodeB (Home eNode B), site controller, and access. It could be a point (AP), wireless router, etc. Although base stations 114a and 114b are shown as single elements, respectively, it is understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements. There will be.
Base station 114a can be part of RAN104, which is other base stations and / or network elements such as BSC (base station controller), RNC (radio network controller), relay nodes (not shown). ) Can also be included. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals within a particular area called a cell (not shown). The cell can be further divided into sectors of the cell. For example, the cell associated with base station 114a can be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e. one transceiver for each sector of the cell. In another embodiment, base station 114a can use multi-input multi-output (MIMO) technology and therefore may utilize multiple transceivers for each sector of the cell.
Base stations 114a, 114b are radios (s) of any suitable radio communication link (eg, radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). It can communicate with one or more of the WTRU102a, 102b, 102c, 102d via interface 116. The radio interface 116 can be established using any suitable radio access technology (RAT).
More specifically, as mentioned above, communication system 100 can be a multiple access system and uses one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. there is a possibility. For example, base stations 114a in RAN104 and WTRU102a, 102b, 102c can establish a radio interface 116 using wideband CDMA (WCDMA), such as UMTS (Universal Mobile Telecommunications System) UTRA (Terrestrial Radio Access). The technology can be implemented. WCDMA may include communication protocols such as HSPA (High-Speed Packet Access) and / or HSPA + (Evolved HSPA). HSPA may include HSDPA (High-Speed Downlink Packet Access) and / or HSUPA (High-Speed Uplink Packet Access).
In another embodiment, base stations 114a and WTRU102a, 102b, 102c can establish a radio interface 116 using LTE (Long Term Evolution) and / or LTE-Advanced (LTE-A) E-UTRA ( Radio technologies such as Evolved UMTS Terrestrial Radio Access) can be implemented.
In other embodiments, the base stations 114a and WTRU102a, 102b, 102c are IEEE802.16 (ie, WiMAX (Worldwide Interoperability for Microwave Access)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, IS-2000 (Interim Standard 2000). ), IS-95 (Interim Standard 95), IS-856 (Interim Standard 856), GSM (Registered Trademark) (Global System for Mobile communications), EDGE (Enhanced Data rates for GSM Evolution), GERAN (GSM EDGE), etc. Wireless technology can be implemented.
In other embodiments, base stations 114a and WTRU102a, 102b, 102c can implement any combination of the radio technologies described above. For example, base stations 114a and WTRU102a, 102b, 102c are dual, such as UTRA and E-UTRA, which can simultaneously establish one radio interface using WCDMA and one radio interface using LTE-A, respectively. Each can implement wireless technology.
Base station 114b in Figure 1A could be, for example, a wireless router, home NodeB, home eNodeB, or access point, facilitating wireless connectivity in local areas such as offices, homes, vehicles, and campuses. Any suitable RAT for this can be utilized. In one embodiment, base stations 114b and WTRU102c, 102d can implement wireless technologies such as IEEE 802.11 for establishing a wireless local area network (WLAN). In another embodiment, base stations 114b and WTRU102c, 102d can implement wireless technologies such as IEEE 802.11 for establishing a wireless personal area network (WPAN). In yet another embodiment, base stations 114b and WTRU102c, 102d can utilize cellular-based RATs (eg, WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish picocells or femtocells. .. As shown in FIG. 1A, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not be required to access Internet 110 via core network 106.
RAN104 may be communicating with core network 106, which may be voice, data, application, and / or VoIP (voice over internet) to one or more of WTRU102a, 102b, 102c, 102d. protocol) Can be any type of network configured to provide services. For example, core network 106 may provide call control, billing services, mobile location-based services, prepaid phones, internet connectivity, video distribution, and / or perform high-level security functions such as user authentication. it can. Although not shown in Figure 1A, the RAN104 and / or core network 106 may be communicating directly or indirectly with the same RAT as the RAN104, or with other RANs that use a different RAT. Will be understood. For example, in addition to being connected to a RAN 104 that may be using E-UTRA radio technology, the core network 106 is also communicating with another RAN (not shown) that uses GSM radio technology. there is a possibility.
The core network 106 can also act as a gateway for the WTRU102a, 102b, 102c, 102d to access the PSTN108, the Internet 110, and / or other networks 112. PSTN108 may include a circuit-switched telephone network that provides a POTS (plain old telephone service). Internet 110 is an interconnected computer network and device that uses common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) of the TCP / IP Internet Protocol Suite. Can include a worldwide system of. The network 112 may include a wired or wireless communication network owned and / or operated by other service providers. For example, network 112 may include another core network connected to one or more RANs that may use the same RAT as the RAN 104, or a different RAT.
Some or all of WTRU102a, 102b, 102c, 102d of communication system 100 may include multimode functionality, i.e., WTRU102a, 102b, 102c, 102d communicate with different wireless networks over different wireless links. May include multiple transceivers to do. For example, the WTRU102c shown in FIG. 1A may be configured to communicate with base station 114a, which can use cellular-based radio technology, and base station 114b, which can use IEEE802 radio technology.
FIG. 1B is an exemplary WTRU102 system diagram. As shown in Figure 1B, the WTRU102 has a processor 118, transceiver 120, transmit / receive element 122, speaker / microphone 124, keypad 126, display / touchpad 128, non-removable memory 130, removable memory. It may include 132, power supply 134, GPS (global positioning system) chipset 136, and other peripherals 138. It will be appreciated that WTRU102 may include any partial combination of the above elements while remaining compliant with the embodiment.
Processor 118 is a general purpose processor, a dedicated processor, a regular processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, and an application specific integrated circuit. It could be an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, and so on. Processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other function that allows the WTRU102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, and transceiver 120 can be coupled to transmit / receive element 122. Although Figure 1B shows the processor 118 and transceiver 120 as separate components, it will be appreciated that the processor 118 and transceiver 120 can be integrated together in an electronic package or chip.
The transmit / receive element 122 may be configured to transmit a signal to or receive a signal from a base station (eg, base station 114a) via the radio interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In another embodiment, the transmit / receive element 122 may be, for example, an emitter / detector configured to transmit and / or receive an IR, UV, or visible light signal. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and receive both RF and optical signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of radio signals.
In addition, although the transmit / receive element 122 is shown as a single element in FIG. 1B, the WTRU102 may include any number of transmit / receive elements 122. More specifically, the WTRU102 can use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (eg, a plurality of antennas) to transmit and receive radio signals over the radio interface 116.
The transceiver 120 may be configured to modulate the signal that will be transmitted by the transmit / receive element 122 and demodulate the signal that will be received by the transmit / receive element 122. As mentioned above, the WTRU102 may have multi-mode capabilities. Thus, the transceiver 120 may include a plurality of transceivers to allow the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.
The WTRU102 processor 118 can be coupled to a speaker / microphone 124, keypad 126, and / or display / touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). , User input data can be received from them. Processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. In addition, processor 118 can access information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132, and store data in that memory. The non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identification module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, processor 118 can access information from memory that is not physically located in WTRU102, such as a server or home computer (not shown), and store the data in that memory.
Processor 118 can be configured to receive power from power supply 134, distribute power to other components within WTRU102, and / or control that power. The power supply 134 may be any suitable device for powering the WTRU102. For example, the power supply 134 may include one or more dry batteries (eg, nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc. Can include.
The processor 118 can also be coupled to the GPS chipset 136, which may be configured to provide location information (eg, longitude and latitude) regarding the current position of the WTRU102. In addition to the information from the GPS chipset 136, or instead of the information from the GPS chipset 136, the WTRU102 receives location information from a base station (eg, base stations 114a, 114b) via wireless interface 116, The position of the WTRU102 can be determined based on the timing of signals received from and / or two or more neighboring base stations. It will be understood that the WTRU102 can acquire the position information by any suitable position determination method while conforming to the embodiment.
Processor 118 may be further coupled to other peripherals 138, which may be one or more software and / or software that provides additional features, functionality, and / or wired or wireless connectivity. Or it may include a hardware module. For example, peripherals 138 include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos or videos), USB (universal serial bus) ports, vibrating devices, television transceivers, hands-free handsets, Bluetooth® modules, etc. It may include FM (frequency modulated) radio units, digital music players, media players, video game player modules, internet browsers, etc.
FIG. 1C is a system diagram of the RAN 104 and the core network 106 according to one embodiment. The RAN104 may be an ASN (access service network) that communicates with WTRU102a, 102b, 102c over wireless interface 116 using IEEE 802.16 radio technology. Communication links between different functional entities in WTRU102a, 102b, 102c, RAN104, and core network 106 can be defined as reference points, as discussed further below.
As shown in FIG. 1C, RAN104 may include base stations 140a, 140b, 140c, and ASN gateway 142, but RAN104 may include any number of base stations and ASN gateways while remaining compliant with embodiments. Will be understood to include. Base stations 140a, 140b, 140c can be associated with specific cells (not shown) of RAN104, respectively, and one or more transceivers for communicating with WTRU102a, 102b, 102c via wireless interface 116. Each can include. In one embodiment, base stations 140a, 140b, 140c can implement MIMO technology. Therefore, the base station 140a can transmit a radio signal to the WTRU102a and receive the radio signal from the WTRU102a using, for example, a plurality of antennas. Base stations 140a, 140b, 140c can also provide mobility management functions such as handoff triggering, tunnel establishment, radio resource management, traffic classification, and quality of service (QoS) policy enforcement. The ASN gateway 142 can act as a traffic aggregation point and can be responsible for paging, caching subscriber profiles, routing to the core network 106, and so on.
The radio interface 116 between WTRU102a, 102b, 102c and RAN104 can be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of WTRU102a, 102b, 102c can establish a logical interface (not shown) with the core network 106. The logical interface between WTRU102a, 102b, 102c and core network 106 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and / or mobility management.
The communication link between each of the base stations 140a, 140b, 140c can be defined as an R8 reference point that includes a protocol for facilitating WTRU handover and data transfer between base stations. The communication link between base stations 140a, 140b, 140c and ASN gateway 215 can be defined as an R6 reference point. The R6 reference point may include a protocol to facilitate mobility management based on the mobility event associated with each of the WTRU102a, 102b, 100c.
As shown in FIG. 1C, the RAN 104 may be connected to the core network 106. The communication link between the RAN 104 and the core network 106 can be defined, for example, as an R3 reference point containing protocols to aid in data transfer and mobility management functions. The core network 106 may include a mobile IP home agent (MIP-HA) 144, an authentication, authorization, accounting (AAA) server 146, and a gateway 148. Each of the above elements is shown as part of core network 106, but any element of these elements may be owned and / or operated by an entity other than the core network operator. Will be understood.
MIP-HA can be responsible for managing IP addresses and allow WTRU102a, 102b, 102c to roam between different ASNs and / or different core networks. The MIP-HA144 can allow WTRU102a, 102b, 102c to access packet-switched networks such as the Internet 110, facilitating communication between WTRU102a, 102b, 102c and IP-enabled devices. AAA server 146 can be responsible for user authentication and user service support. Gateway 148 can facilitate network connections with other networks. For example, gateway 148 can allow WTRU102a, 102b, 102c to access circuit-switched networks such as PSTN108, facilitating communication between WTRU102a, 102b, 102c and conventional fixed-line telephone line communication devices. In addition, gateway 148 can allow WTRU102a, 102b, 102c to access network 112, which may include other wired or wireless networks owned and / or operated by other service providers.
Although not shown in Figure 1C, it will be appreciated that the RAN104 may be connected to other ASNs and the core network 106 may be connected to other core networks. .. The communication link between the RAN104 and the other ASN can be defined as an R4 reference point that may contain a protocol for coordinating the mobility of the WTRU102a, 102b, 102c between the RAN104 and the other ASN. The communication link between the core network 106 and the other core networks can be defined as an R5 reference that may include protocols to facilitate internetwork connections between the home core network and the core network in which it resides.
For purposes of illustration, various embodiments are shown in the context of the Institute of Electrical and Electronics Engineers (IEEE) 802.16, but the various embodiments can be implemented in any wireless communication technology. Some exemplary types of wireless communication technology are WiMAX (Worldwide Interoperability for Microwave Access), 802.xx, GSM (Global System for Mobile communications), Code Division Multiple Access (CDMA2000), UMTS (Universal Mobile Telecommunications System). , LTE (Long Term Evolution), or any future technology, but not limited to these. For simplicity, the embodiment is an IEEE 802.16 advanced wireless interface (Advanced Air). Shown in relation to the Advanced Broadband Wireless System (A-BWS), which uses medium access control based on scheduling for wireless links, such as Interface) (802.16m). In particular, embodiments may be applied to uplink (UL) resource allocation for subscriber stations with multiple service flows / connections in an 802.16m system.
The term connection and service flow or flow can refer to a logical channel over a wireless link between a base station and a WTRU. The radio link between the base station and the subscriber station may include one or more connections or flows. Each connection or flow can be the smallest logical unit for quality of service (QoS) provisioning and security attribute association. In this sense, these two concepts, connections and flows, can be used interchangeably. In addition, in the 802.16m example, a WTRU, subscriber station, or station may be referred to as an Advanced Mobile Station (AMS), and per station may mean per WTRU. ..
The term or concept of a connection may be used primarily in 802.16, where a connection may have a 16-bit identifier called the Connection Identification (ID) (CID). The concept of service flow or flow can be used in both 802.16 and 802.16m. A service flow or flow can be uniquely identified by an identifier within the subscriber in both 802.16 and 802.16m, but the flow identifier used may have different sizes and different relationships with the concept of connection. There is. For example, in 802.16, the flow identifier can be called the Service Flow ID (SFID), and the size of the flow identifier can be 32 bits, 16 bits for the allowed service flow. May have a one-to-one correspondence with the CID. In 802.16m, the flow identifier is the flow ID (Flow). Sometimes called ID) (FID), the size of the flow identifier can be 4 bits, a 16 bit CID is a 12 bit station ID (STID) and a 4 bit FID May be equal to the combination of.
In 802.16m, UE bandwidth requesting and granting procedures may follow per-connection / service flow requests and per-WTRU allocations. There can be some cases where per-connection (also called per-flow) UL allocations can be beneficial. For example, a base station transfers UL resources to the WTRU, the base station's knowledge of the UL traffic needs of its active connection in the WTRU, such as the amount of data, delay tolerance, etc., and the base station's real-time UL traffic. Can be assigned based on the load of. With respect to UL assignments, a base station may have its own intent on how UL assignments should be distributed among WTRU's active connections. However, with the typical 802.16 per-station UL assignment, the intended information of the base station may not be available in the WTRU. Therefore, it is desirable to provision such information to the WTRU to help the WTRU achieve better synchronization with the base station for bandwidth requirements and grants for each connection. This can reduce the probability of fragmentation and also reduce the need to send a total bandwidth request for self-correction in the UL bandwidth request / grant process. Therefore, control overhead and processing load can be reduced and system efficiency can be improved.
Some allocation mechanisms may be based on specific traffic patterns. A typical example could be a Persistent Allocation (PA) mechanism that can be designed to reduce allocation overhead for periodic traffic patterns of relatively constant payload size. Note that traffic patterns are application specific and can be, for example, flow / connection specific. Therefore, PA allocations may clearly target those particular connections. In addition to PA, 802.16m group resource allocation (GRA) can also be used to allocate periodic resources that may be targeted to some specific applications with periodic traffic patterns.
However, based on 802.16m, the UL basic allocation and the UL PA allocation can be station-by-station allocations. There may not be any mechanism to support provisioning the flow information intended for the WTRU with respect to UL's basic allocation or UL's PA allocation. On the other hand, simply having the resources allocated by the PA and GRA, which should be per connection, is otherwise due to the higher system efficiency where the relatively constant size payload of the intended connection is required. It may not be a sufficient solution as it may leave the UL resources allocated by the PA / GRA available for the connection completely unutilized. In some cases, it may be related to some flexibility in using PA / GRA assignments, such as sending some emergency medium access control (MAC) control signals to the WTRU, and / or emergency services. It may be desirable to allow such things as sending emergency real-time data.
Methods and devices for making UL allocations per hybrid flow / connection and per WTRU to improve the efficiency of UL control and further improve the utilization of UL resources are described herein. To. An exemplary hybrid flow-by-flow and per-WTRU UL resource allocation mechanism high-level flow Figure 200 is shown in Figure 2. A base station can grant a UL resource to a WTRU based on the WTRU's (s) UL resource request (205). The presence or absence of intended flow information can determine whether the granted UL resource can be applied (210). For example, in the absence of specific control information, such as intended flow information, the default mode for UL allocation may be per WTRU, eg, per WTRU at 802.16m (215).
The base station can signal the WTRU with the intended flow information regarding UL allocation (220). Such signals may be given explicitly or implicitly for each UL assignment, for the type of UL assignment, or for a set of UL assignments. Examples of such signaling mechanisms are: a) Circular redundancy check (CRC) code or sequence of UL Allocation Information Elements (IE) with intended flow information, such as a flow identifier or a predefined flow indicator. And b) including the intended flow information, such as a flow identifier or a predefined flow indicator, in the UL Assignment Information Element (IE), and c) including a particular type of flow in a particular UL. To associate with allocation mechanisms such as Persistent Allocation (PA), Group Resource Allocation (GRA), etc., such association is connection management such as AAI_DSx for Advanced Radio Interface (AAI) in 802.11m systems. It can include associating, which can be established by using MAC control messages.
Predefined flow indicators can be defined to represent a particular flow or group of flows, either explicitly with MAC control messages, for example, or implicitly with flow parameters. Can be defined in. When the intended flow information is available for UL allocation, the WTRU or subscriber station assigns the intended flow information a higher priority, eg, to one or more intended flows. , Can be taken into account in the UL transmission of that WTRU or subscriber station in a given UL assignment (225). WTRU may be allowed to send data for other flows in UL allocation after processing one or more intended flows. In addition, the WTRU can use the allocated UL resources to send some urgent MAC control data, urgent user data, and so on.
In addition, the base station may include an exclusive flag in the UL assignment IE to give further instructions on how a given UL assignment can be used. For example, the exclusive flag may indicate that the UL assignment can be used for one or more intended flows and not for other flows. .. Alternatively, the exclusive flag is used to indicate that the UL assignment can be used for one or more intended flows and any other flow with a higher priority. Can be done. That is, the exclusion flag may allow the use of allocated resources for flows with higher priority. The remaining resources may be allowed to be used for other flows regardless of the exclusive flag.
With respect to traffic pattern oriented UL allocation mechanisms, such as PA and GRA, the intended flow information about the allocated resources can be given explicitly or implicitly to the WTRU.
Presented herein are additional explanations and examples of applying the general method described above to an 802.16m system. In particular, methods for applying the hybrid per-connection / flow and per-WTRU UL allocation mechanism to UL basic allocation, UL permanent allocation, and UL group allocation are described.
In an 802.16m system, there may be four different allocation mechanisms for UL resources. The first allocation mechanism, type 1, may be allocated or reserved for UL control signals. This mechanism provides specific UL assignments for specific UL control signals A-field (A) -MAP IE (A-field (A) -MAP IE), for example UL Sounding Command A-MAP IE (UL Sounding Command A- UL resources that are either reserved or allocated by MAP IE), CDMA Allocation A-MAP IE, Feedback Polling A-MAP IE (Feedback Polling A-MAP IE), etc. can be used. The second allocation mechanism, type 2, may be the basic allocation of UL. This type of UL allocation allows a one-time unicast generic UL resource to be allocated to a WTRU. UL basic assignment A-MAP IE (UL basic assignment A-MAP There can be two UL assignments A-MAP IE for this type of UL assignment, such as IE) and UL subband assignment A-MAP IE (UL subband assignment A-MAP IE). The third allocation mechanism, type 3, may be a permanent allocation of UL. This type of UL allocation can allocate UL resources that are periodic, unicast, and specific to the traffic pattern, and the intended traffic pattern can be a periodic pattern with a relatively constant payload size. There is. UL Permanent Assignment (PA) A-MAP IE can be designed for this type of UL assignment. The fourth allocation mechanism, type 4, may be a UL group assignment. This type of UL allocation allows UL resources to be allocated to a group of users by using a single Group Resource Allocation (GRA) A-MAP IE in UL, and each user can be assigned a unicast UL allocation. .. One GRA A-MAP IE can allocate one-time UL resources. However, GRA can be used cyclically with the periodicity specified in the group configuration, so this GRA allocation mechanism is to support periodic traffic patterns with a relatively constant payload size. Can be used.
The hybrid per-connection and per-WTRU UL resource allocation mechanisms described herein may be compatible with Type 2, 3, and 4 allocations, but Type 1 UL resources have a WTRU specific UL control. It may not fit into Type 1 assignments as it can be reserved or assigned by using certain UL assignments A-MAP IE to send the signal. The intent of this type of UL resource can be clearly specified.
In 802.16m, BE (best effort), nrtPS (non-real-time polling service), rtPS (real-time polling service), ertPS (extended rtPS), UGS (unsolicited grant service), and aGP (adaptive granting and) There are six types of UL grant scheduling, including polling service). Based on 802.16m, UL connections can be associated with a single UL scheduling service type.
In particular, with respect to the type of UL grant scheduling for BE, the base station or ABS may not guarantee any UL grant for BE connections / flows. The base station can meet the UL bandwidth requirements of the BE connection with best effort. With respect to the type of UL grant scheduling for nrtPS, base stations can provide opportunities for bandwidth requests for nrtPS connections, typically at intervals of about 1 second or less. With respect to the type of UL grant scheduling for rtPS, the base station can provide the opportunity for a real-time, periodic unicast bandwidth request for the WTRU to send a bandwidth request for the rtPS connection / flow. With respect to the type of UL grant scheduling for ertPS, a base station can grant a real-time, periodic unicast UL to a WTRU without the need for the WTRU to send a bandwidth request. The UL grant size is the default setting and is the maximum sustained traffic rate for the connection. It can be determined by rate) and can be dynamically modified by a bandwidth modification request sent by the WTRU to the base station. Regarding the type of UL grant scheduling of UGS, the base station can periodically grant a certain size of UL in real time without being based on a request. For example, the WTRU may not need to send UL bandwidth requests for UGS connections / flows. With respect to the type of UL grant scheduling for aGP, the base station can grant the WTRU a periodic unicast UL in real time on a non-request basis. Periodicity and allocation size can be determined by QoS parameters. There may be two sets of QoS parameters for aGP connections / flows, called the primary set and the secondary set. AGP connections / flows can be allowed based on their primary QoS parameters, and during service the aGP connections / flows can be switched to secondary QoS parameters or individually modified. it can. When both the primary and secondary QoS parameter sets are defined, the primary QoS parameter set can have more stringent QoS requirements than the secondary QoS requirements. Admission control can be performed by considering the tighter QoS requirements defined by the primary QoS parameters. Secondary QoS parameters may be the minimum QoS guarantee that a scheduling service can provide.
Based on 802.16m, two UL A-MAP IEs, UL Basic Allocation IE and UL Subband Allocation IE, can be used to allocate UL basic allocations. UL's basic allocation may be station-by-station allocation. Presented herein is a method for applying a hybrid per-connection / flow and per-WTRU UL allocation mechanism to the basic UL allocation.
The hybrid per-WTRU and per-connection / flow UL mechanism for UL basic allocation may include a default mode for UL basic allocation, per WTRU. The base station can signal the WTRU with the intended flow information regarding the basic allocation of UL. Examples of such signaling mechanisms are a) combining the STID of the WTRU with the intended flow information to mask the CRC of the UL Basic Allocation IE, including the UL Basic Allocation IE and the UL Subband Allocation IE. And b) UL basic allocation A-MAP including UL basic allocation IE and UL subband allocation IE for the intended flow information It can include inclusion in IE and c) representing the intended flow information with a FID and / or a predefined flow indicator. An example of such a predefined flow indicator is given below. When the intended flow information is available with respect to UL's basic allocation, the WTRU will assign the intended flow information to, for example, one or more intended flows with a higher priority. It can be taken into account in the transmission of the UL of that WTRU in the basic allocation of the corresponding UL. In addition, the WTRU is allowed, for example, to process one or more flows as intended and then use any remaining resources to send data for other connections with UL's basic allocation. there is a possibility. The WTRU also uses some urgent UL data, such as urgent MAC control data, urgent user data, with available UL basic assignments that have information on the intended (s) flows. Etc. can be sent.
Shown herein are flow indicators that can be used to implement UL's basic assignments. An exemplary flow indicator can be used to indicate the intended one or more flows for the basic assignment of UL.
The exemplary flow indicator can be a 1-bit flow indicator. This 1-bit flow indicator is a flow parameter, UL Grant Scheduling Service, as shown below. Can be defined based on Type). If the intended flow indicator = 0b0, this assignment may cover all flows. That is, the intended flow indicator can signal the allocation per WTRU. If the intended flow indicator = 0b1, this assignment may be for one particular flow or multiple flows. For example, its intended flow indicator is real-time traffic identified by a flow parameter, UL Grand Scheduling Service Type, using one of the following types: UGS, ertPS, rtPS, and aGP: The accompanying flow can be signaled. The values of the intended flow indicators used in the examples herein are exemplary and other values may be defined or used without departing from the present disclosure.
Another exemplary flow indicator could be a 2-bit flow indicator. This 2-bit flow indicator can be defined based on the flow parameters, UL grant scheduling service type, as follows: If the intended flow indicator = 0b00, this assignment may cover all flows. That is, the intended flow indicator can signal the allocation per WTRU. If the intended flow indicator = 0b01, this assignment may be for real-time flows, such as UGS, rtPS, ertPS, aGP. If the intended flow indicator = 0b10, this assignment may be for ertPS and aGP flows. If the intended flow indicator = 0b11, this assignment may be for aGP flows that can have secondary QoS parameters defined.
In this example flow indicator, the group 0b11 defined as "aGP flow that defines secondary QoS parameters" is defined in the secondary QoS parameter set of the aGP flow where this assignment can define secondary QoS parameters. It can be used to indicate that it may be intended to meet the minimum QoS guarantees made. This mechanism can allow a base station to reduce the load on the base station by dealing with groups of flows and lowering the requirements to meet the minimum QoS guarantee. Similarly, the group 0b10 defined for ertPS and aGP flows is intended for aGP flows so that this allocation meets the QoS guarantee defined by the primary QoS parameter set for the aGP flow. Can be used to indicate potential.
Another exemplary flow indicator could be a 2-bit parameter called the UL Allocation Intended Flow Indicator (UAIFI) that can be assigned to flows and UL assignments. Flows can be assigned UAIFI values by including UAIFI as a flow parameter in the flow management MAC control message, AAI_DSx. UL basic allocations can be assigned UAIFI values by including UAIFI in UL basic allocation IEs such as UL Basic Allocation IE or UL Subband Allocation IE. This can be included in IE by masking that UAIFI with an IE CRC or by including UAIFI in IE as an information field. The default value for UAIFI can be set to, for example, 0b00. That is, if UAIFI does not exist, UAIFI = 0b00.
A comparison between the UAIFI value of a flow and the UAIFI value of a UL assignment can indicate whether the flow is the intended flow of the UL assignment. If the UL assignments have that UAIFI = a, then the flows with UAIFI a may be the intended flows for these UL assignments. For example, a UL allocation with UAIFI = 0b00 may indicate that the UL allocation is for all flows, i.e. per WTRU. A UL allocation with UAIFI = 0b01 may indicate that the UL allocation targets a flow with UAIFI 0b01. A UL allocation with UAIFI = 0b10 may indicate that the UL allocation targets a flow with UAIFI 0b10. A UL assignment with UAIFI = 0b11 may indicate that the UL assignment targets a flow with UAIFI = 0b11.
In one example, both the FID and the flow indicator can be signaled. This capability can be useful in specifying that a particular assignment is preferably used for a particular flow, eg, a MAC control flow. With respect to this mode of operation, the WTRU may use the allocated resource for the flow indicated by the FID, or use the resource for other flows depending on the control information of the flow indicator. Is either possible. For example, a base station, in addition to a FID, whether the allocation is for that FID only, or WTRU resources resources for certain types of flows, such as UGS, ertPS, rtPS, and aGP for real-time flows. A 1-bit flow indicator that can be used to indicate that it can also be used for transmission. Which flows are allowed to use the resource can be determined in advance or signaled by the base station. In another example, the base station, in addition to the FID, has a flow with a real-time rank above a certain threshold that may be allocated solely for that FID or depending on the indicator, eg, BE. And a 2-bit flow indicator can also be sent that can indicate if it is for all flows except the nrtPS flow. In another example, UAIFI can be signaled in addition to FID. A value of a = 0 can indicate that only flows for which allocations have been shown are targeted, and a value of a> 0 can indicate the use of bandwidth for flows with UAIFI a.
Based on 802.16m, UL PA can be summarized for UL PA allocation, UL PA change, UL PA deallocation, and UL PA hybrid automatic repeat request (HARQ). For example, UL PA assignments can be assigned by UL PA A-MAP IE and the STID of WTRU can be masked using the CRC of UL PA A-MAP IE. That is, UL PA assignments can be assigned to stations. UL PA changes can occur when UL PA assignments are changed by sending another UL PA A-MAP IE to the WTRU for the same AAI subframe. That is, a new PA assignment in the same AAI subframe can overwrite an existing PA assignment in WTRU. UL PA deallocation can occur when UL PA allocation is deallocated by sending a UL PA A-MAP IE with the deallocation flag for the same AAI subframe. UL PA HARQ can be similar to basic UL allocation and may include UL synchronous HARQ (UL synchronous HARQ). If the PA allocation interval is not long enough to allow maximum HARQ retransmissions, HARQ retransmissions can be modified by sending a UL basic allocation A-MAP IE. In addition, the number of HARQ channel IDs (HARQ channel IDs), N_ACID, can be specified for PA allocation in the PA allocation IE. If the retransmission process for the previous HARQ burst is not completed before a new HARQ burst with the same ACID is sent, the retransmission process for the previous HARQ burst can be terminated and the new HARQ burst is its retransmission process. Can be overwritten.
The maximum number of UL PA allocations for a WTRU can be one per subframe or per TTI, and UL PA allocations consist of a series of periodic UL bursts allocated by UL PA A-MAP IE. May contain UL resources allocated by one UL PA A-MAP IE.
To avoid conflicts between multiple PA assignments to a WTRU, the maximum number of UL PA assignments per WTRU is due to the nature of the periodic assignments that are repeated if the periodicity can be defined in frames. Can be limited by the maximum number of UL PA allocations per frame. That is, given a maximum of one UL PA allocation per TTI per WTRU, the maximum number of UL PA allocations per WTRU can be determined by the maximum UL TTI per frame. For example, the maximum number of UL PA allocations per WTRU in different duplex modes and different TTIs could be: For Frequency Division Duplex (FDD) with 1 subframe TTI, the maximum number of UL PA allocations per WTRU can be 8. For FDDs with 4 subframe TTIs, the maximum number of UL PA allocations per WTRU can be 2. UL per WTRU for Time Division Duplex (TDD) using 1 subframe TTI The maximum number of PA allocations can be the number of UL subframes in a frame. For long TTIs, i.e. TDDs that use all UL subframes in the UL of a frame, the maximum number of UL PA allocations per WTRU can be 1.
PA assignments can be identified with respect to WTRU. One method could be, for example, to identify UL PA allocations by UL subframes where UL PA allocated resources can be allocated when multiple UL PA allocations can exist for a WTRU. There is sex.
The hybrid per-flow / connection and per-WTRU UL PA allocation mechanism can be implemented as follows: The base station can explicitly or implicitly provide the flow information intended for the WTRU with respect to UL PA allocation. The WTRU can take into account the available information of the intended PA flow when the WTRU sends data for that WTRU using the UL PA's allocated resources. For example, the WTRU can assign a higher priority to the intended flow than any other flow. WTRU may be allowed to send data for other flows with UL PA's allocated resources by using the remaining resources after processing one or more intended flows. is there. In addition, WTRU can transmit emergency MAC control data, emergency user data, etc. using UL PA's allocated resources. WTRU can also send data for one or more flows that are subject to UL PA allocation with other UL allocations.
When a WTRU has one UL PA assignment, the following mechanism can be used to inform the WTRU of the intended one or more flows of the UL PA assignment. One FID or multiple FIDs are intended, for example, to mask the CRC of UL PA A-MAP IE with STID (Station ID) combined with one FID or multiple FIDs. By including one or more FIDs in the UL PA A-MAP IE, it can be used to indicate the intended one or more flows of UL PA allocation. A pre-defined indicator is, for example, a UL PA A-MAP IE CRC with one or more pre-defined indicators intended for STID. By masking and / or including a predefined indicator or indicators in UL PA A-MAP IE that can indicate one or more intended flows. It can be used to indicate one or more flows intended for PA allocation. One flow parameter or multiple flow parameters can be used to indicate whether a flow is the intended flow for UL PA allocation for WTRU. For example, flow parameters such as PA-intended indicators can be added to be used in the flow management MAC control message AAI_DSx. Existing flow parameters such as UL Grant Scheduling Service Type, Unsolicited Grant Interval, Primary / Secondary Grant Size, or Primary / secondary GPI may also be used.
When a WTRU has multiple PA assignments, the flow can be shown as the intended flow for a particular UL PA assignment of the WTRU, for a subset of UL PA assignments, or for all UL PA assignments. Shown herein are examples of signaling mechanisms that can be used for WTRUs with multiple PA assignments.
The following mechanisms can be used to indicate a flow as the intended flow for a particular UL PA assignment in WTRU. For example, the FID can be used to indicate the flow by masking the CRC of UL PA A-MAP IE with a FID or flow indicator, or by including the FID or flow indicator in UL PA A-MAP IE. .. A plurality of PA allocation, for example, periodic, as may be distinguished by the existing flow parameters, such as allocation size, flow trough the flow flows that are intended regarding PA assigned with the closest periodicity and allocation size to Ikkupatan Can be implied as. Flow parameters can be added to identify PA assignments. For example, an index of UL PA-assigned subframes, or a bitmap for identifying UL PA-assigned subframes, can be added to flow management MAC control messages, such as AAI_DSx messages.
The following mechanism can be used to indicate a flow as the intended flow of a group of UL PA assignments for WTRU. The FID or flow indicator may be used in a group of UL PA A-MAP IEs and either masked with CRC or included in IE. Parameters such as periodicity, allocation size, etc. can be matched between PA allocation and flow traffic patterns. New flow parameters may be added to identify a subset of PA allocations. For example, in flow management MAC control messages such as the AAI_DSx message, for example, a list of indexes for UL PA-assigned subframes, or bitmaps for identifying UL PA-assigned subframes may be used.
The following mechanism can be used to show the UL flow as the intended flow for all UL PA assignments in WTRU. For example, a FID or flow indicator can be used in all UL PA A-MAP IEs and either masked in CRC or included in IE. Alternatively, flow parameters such as PA intended indicators that can be included in the flow management MAC control message may be used. Some existing flow parameters, such as UL grant scheduling service type, non-request based grant interval, primary / secondary grant size, and / or primary / secondary GPI, can be used to indicate UL flow.
UL PA assignments can have more than one intended flow, as mentioned above. An exemplary signaling mechanism may include CRC of UL PA A-MAP IE masked with multiple FIDs or flow indicators of multiple intended flows. Another signaling mechanism may have UL PA A-MAP IE with multiple FIDs or flow indicators for multiple intended flows. Multiple flows have flow parameters for those flows, such as PA intended indicator, PA subframe index information, UL grant scheduling type, non-request-based grant interval, primary / secondary grant size, primary / secondary GPI, etc. Can be identified as the intended flow of the same UL PA assignment.
Shown herein is an example of signaling WTRU information about one or more flows intended for UL PA allocation by using UL flow parameters, such as UL flow parameters at 802.16 m. is there.
In the example of PA signaling, the UL flow parameter, UL Grant Scheduling Service Type, can be used to indicate that the flow may be the intended flow for UL PA allocation in WTRU. The UL Grant Scheduling service type may be an existing UL flow parameter. In this example, the UL Flow is a WTRU where the UL Grant Scheduling service type requires the base station to provide real-time periodic unicast UL grants, such as UGS, ertPS, rtPS, and aGP. It may be the intended flow of UL PA allocation. The flow can be one, all, or any combination of these scheduling service types.
In another example of PA signaling, the UL flow parameter, the indicator for which PA is intended, can be used to indicate that the flow may be the intended flow for UL PA assignment of the WTRU. The indicator for which PA is intended may be a UL flow parameter. The indicator intended for PA may be a 1-bit flag that can indicate whether the flow is the intended flow for PA. For example, if the PA is the intended indicator = 0b0, the flow may not be the PA intended flow. If the PA is the intended indicator = 0b1, the flow may be the PA intended flow. That is, the flow may be the intended flow for WTRU's UL PA assignment. The parameter, the indicator intended for PA, can be used in flow management MAC control messages, such as AAI_DSx messages.
In another example of PA signaling, UL flow parameters such as UL grant scheduling service type, indicator the PA is intended for, non-request based grant interval, primary / secondary grant size, primary / secondary GPI, etc. UL of WTRU that may have matching allocation periodicity and / or allocation size It can be used to indicate that it may be the intended flow for PA allocation. In this example, UL flow parameters, UL grant scheduling service types and / or indicators intended for PA can be used to indicate whether a UL flow is a flow intended for PA. If the flow is the flow for which the PA is intended, additional flow parameters of the WTRU are based on the matching allocation periodicity and / or allocation size between the flow and one PA assignment or multiple PA assignments. It can be used to further identify a particular PA assignment or multiple PA assignments. Table 1 below shows examples of UL flow parameters that can be used to determine allocation periodicity and size based on its UL grant scheduling service type.
<tables num="1"><img file="JP5508552B2_D0001.tif" /></tables>
Matching allocation periodicity and / or allocation size between flows and PA allocations may not have exactly the same values and can be understood to mean "close to each other". Then, "how close means a match" can be defined by different system designs, for example, "match" means the "closest" PA assignment of all WTRU PA assignments. May, or match, may mean "the difference is less than 10%, less than 20%, and so on." These are exemplary definitions and other definitions may be used without departing from the present disclosure.
In another example of PA signaling, a flow parameter, such as an indicator for which a PA is intended, a UL grant scheduling service type, a UL PA subframe indicator, etc., is such that the flow has a specific UL PA assignment or multiple ULs in the WTRU. It may be used to indicate that it may be the intended flow for PA assignments, and a particular UL PA assignment or multiple UL PA assignments may be one UL PA subframe or multiple. Can be identified by UL PA subframes. In this example, UL flow parameters, UL grant scheduling service types and / or indicators intended for PA can be used to indicate whether a UL flow is a flow intended for PA. If the flow is the flow for which PA is intended, another UL flow parameter, such as the UL PA subframe indicator, is used to identify a particular UL PA assignment or multiple UL PA assignments for a UL flow. obtain. In one implementation, the WTRU has a UL with subframe information about the WTRU. You may have up to one UL PA assignment per UL subframe so that it can be used to uniquely identify the PA assignment.
In another example, a bitmap can be used to indicate one UL PA assignment or multiple UL PA assignments for a flow. In one implementation, the maximum subframe in a frame can be 8, and the maximum UL subframe in a frame in an FDD system can also be 8. Bitmaps of 8-bit UL PA subframes can be used as UL flow parameters, and each bit may correspond to a subframe within the frame. If bit i of the bitmap is set to 1, it can indicate that the UL flow is the intended flow for UL PA allocation in subframe i. Using a bitmap of such UL PA subframes as a UL flow parameter establishes that a UL flow may be the intended flow for a particular UL PA assignment or multiple UL PA assignments. Can be shown as a target. UL When a PA subframe bitmap can be used in a flow / connection management MAC control message, eg, an AAI_DSx message, in establishing or modifying a flow / connection, the overhead introduced can be trivial.
An alternative to UL PA subframe bitmaps is to use a list of 3-bit UL PA subframe indexes as UL flow parameters to identify one UL PA assignment or multiple UL PA assignments. there is a possibility. When compared to the bitmap mechanism, this mechanism may save a few bits when only one or two UL PA allocations intended for the flow may exist. However, on the other hand, this mechanism may introduce variable length parameters and may pay a higher overhead cost when the number of UL PA allocations is 3 or greater.
In another example of PA signaling, the PA intended indicator can be used to indicate that the flow may be the intended flow for a particular UL PA assignment of the WTRU. A particular UL PA assignment can be identified by a parameter, a UL PA subframe encoded in a PA indicator. For example, the PA indicator can be defined as a 4-bit flow parameter shown in Table 2 below.
<tables num="2"><img file="JP5508552B2_D0002.tif" /></tables>
In some examples, it may be useful to signal both the specific FID for PA allocation and the PA usage indicator information. For example, a base station, in addition to a FID, indicates whether the allocation may be for that FID only, or a 1-bit PA usage indicator that the WTRU may use resources for other flows. Can also be sent. If a resource is allowed to be used to send UL data for other flows, the WTRU can determine which resource to use based on the PA signaling example above.
Based on 802.16m, UL Group Resource Allocation (GRA) can be summarized as follows: A GRA A-MAP IE with a group ID associated with the UL indicator can indicate a UL GRA assignment. UL GRA assignments allow you to assign a set of one-time unicast UL assignments to selected WTRUs in a preset group of WTRUs, assigning one UL assignment for each selected WTRU. Can be done. The selected WTRU is GRA A-MAP Can be identified by user bitmap fields in IE. A preconfigured group of WTRUs can be configured by AAI_GRP-CFG, a group configuration MAC control message that can be sent from the base station to the WTRU to add or remove specific flows of the WTRU. A particular flow can be identified by the FID field in the message. AAI_GRP-CFG can also be sent to a group of WTRUs to inform the WTRU about the configuration of the group of WTRUs. The WTRU group configuration can include the periodicity of the allocation of this group by a parameter called "periodicity" in AAI_GRP-CFG. Its parameters can specify the periodicity at which GRA A-MAP IEs in this group can be sent. In this way, GRA allocation can also be used to support periodic traffic patterns of relatively constant payload size. Base stations may have multiple groups of WTRUs to make GRA assignments. Each group can be identified by a 12-bit group ID. GRA A-MAP IE can be directed to a group of WTRUs by masking the group ID information in the CRC of A-MAP IE. Within GRA A-MAP IE, a user bitmap field can identify one WTRU or multiple WTRUs to which resources can be allocated by that GRA A-MAP IE.
UL GRA can be considered per flow, as group configuration messages can allocate WTRU flows to groups. That is, it is possible that it is not just the WTRU that can be associated with the group, but the flow of the WTRU. UL GRA, on the other hand, can be considered per WTRU, as allocations can be given by GRA A-MAP IE, which is directed to WTRU rather than flow. For clarity purposes, UL GRA assignments for groups of WTRUs may refer to UL resources that can be assigned by a single GRA A-MAP IE in UL. UL GRA assignment to WTRU is assigned to WTRU by one GRA A-MAP IE in UL with the corresponding bit of the user bitmap field set to indicate that WTRU is given UL assignment by GRA A-MAP IE. May refer to possible UL resources. A set of UL GRA assignments to a group of WTRUs is a set of GRAs in UL with the periodicity given in the user group settings. A-MAP May refer to UL resources that can be assigned to user groups by IE. A set of UL GRA assignments to a WTRU is assigned to a WTRU by a set of GRA A-MAP IEs with the corresponding bits in the user bitmap field set to indicate that the WTRU is given a UL assignment by the GRA A-MAP IE. May refer to possible UL resources. A set of UL GRA assignments for a WTRU may not always be set to the corresponding bit in the user bitmap field of a set of GRA A-MAP IEs for a group of WTRUs, so a parameter for setting a group of WTRUs. , May not have the same periodicity as indicated by periodicity.
Figure 3 shows an exemplary hybrid flow-by-flow and station-by-station UL GRA allocation mechanism 300. The WTRU can send UL resource requests (305). The base station can allocate the WTRU flow to the WTRU group by including the FID in the group configuration message (310), so the intended flow information is signaled for UL GRA allocation through the group configuration. .. The base station allocates UL resources to WTRU by using UL GRA allocation (315). The WTRU can then determine the intended flow information received from the base station (320), then the UL. Information on one or more intended flows can be taken into account when sending data for that WTRU using GRA's allocated resources (325). For example, the WTRU can assign a higher priority to one or more intended flows than other flows. After processing one or more intended flows, the WTRU can use the remaining resources to send data for other flows with GRA's allocated resources. In addition, the WTRU can send some urgent MAC control data, urgent user data, etc. using UL GRA assignments with the intended flow information. WTRU can send data for one or more flows for GRA allocation with other UL allocations.
In addition to including the FID field in the group configuration MAC control message, the following exemplary signaling mechanism can be used to signal the WTRU with the intended flow information regarding GRA allocation. In an exemplary signaling mechanism, flow parameters in a flow management MAC control message can be used to indicate that a flow may be the intended flow for GRA allocation. For example, the flow management MAC control message can be an AAI_DSx message. The flow parameter is an existing flow parameter, such as the UL Grant Scheduling Service type, or a GRA intended indicator to indicate that the flow may be the GRA intended flow for the WTRU GRA assignment. It may be a new flow parameter such as (GRA-intended indicator).
With respect to the flow for which GRA is intended, some existing flow parameters may be used to further indicate which one or more user groups the flow may target. This can be based, for example, on matching allocation periodicity and / or allocation size between the flow and one user group or multiple user groups. Table 1 shows some examples of flow parameters that can be used to determine allocation periodicity and size. With respect to the flow for which the GRA is intended, one flow parameter or multiple flow parameters may be added to further indicate which one user group or multiple user groups the flow may target. For example, a group ID field, a list of group IDs, a group indicator, a list of group indicators, etc. may be used.
Another exemplary hybrid flow-by-flow and per-station UL GRA allocation mechanism 400 is described herein for UL GRA allocation to WTRU when a WTRU is added to a group, as shown in FIG. The stated explicit or implicit intended flow information may be used. For example, a WTRU can send a UL resource request (410). Base stations can assign WTRUs to groups (420). The base station can make a UL assignment to the WTRU by using the UL GRA assignment, and the intended flow information can be provided to the WTRU, either explicitly or implicitly (425). The WTRU then determines the intended flow information (430). The intended flow information available is used by the WTRU to determine the data to be sent with a given UL GRA assignment (435).
Another exemplary signaling mechanism may be applicable when multiple flows of the same WTRU are allowed to join the same group for UL GRA. For example, a base station can allocate each of a plurality of flows to a group by transmitting a plurality of group setting MAC control messages for each flow. Alternatively, it can be signaled by including multiple flow information in one group configuration MAC control message. For example, it can be signaled by a list of FIDs or by a (s) FID indicators that can identify multiple flows.
Embodiment 1. A method for performing hybrid station-by-station and flow-by-flow uplink allocation, comprising requesting uplink resource allocation for at least one flow.
2. The method according to any of the above embodiments, further comprising the step of receiving an uplink resource allocation.
3. The method of any of the above embodiments, further comprising the step of determining if the intended flow information for the allocated uplink resource is available.
4. The method of any of the above embodiments, further comprising the step of determining whether the available intended flow information for the allocated uplink resource is applicable.
5. The method of any of the above embodiments, further comprising the step of transmitting data using the allocated uplink resources as soon as the intended flow information has been applied.
6. The application of the intended flow information is the method of any of the above embodiments that assigns priority to the intended flow with respect to the use of the allocated uplink resources.
7. The method according to any of the above embodiments, wherein the allocated uplink resource is a persistently allocated resource for the uplink.
8. The method according to any of the above embodiments, wherein the allocated uplink resource is an uplink group resource allocated resource.
9. At least one flow is the method according to any of the above embodiments associated with a group.
10. The method according to any of the above embodiments, wherein the application of the intended flow information allows the transmission of other flows using the remaining uplink resources after processing the intended flow.
11. The application of the intended flow information is the method of any of the above embodiments that allows the transmission of urgent data from at least one other flow.
12. The method according to any of the above embodiments, wherein the urgent data is an urgent medium access control (MAC) message.
13. The method described in any of the above embodiments, where the emergency data is emergency service data.
14. The method according to any of the above embodiments, wherein the intended flow information is provided by masking the cyclic redundancy check of the persistent allocation information element with station identification information and flow identification information.
15. The method described in any of the above embodiments where the intended flow information is given in the permanent allocation information element.
16. Intended flow information is about the uplink's persistently allocated resource, which is determined by matching at least one of the allocation periodicity or allocation size between the flow and the uplink's persistently allocated resource. The method according to any of the above embodiments.
17. A method for performing hybrid station-by-station and flow-by-flow uplink allocations, including the step of receiving an uplink resource allocation request for at least one flow.
18. The method of embodiment 17, further comprising the step of allocating at least one of the flows or radio transmit / receive units (WTRUs) to a group for scheduling resource allocation.
19. The method according to any of embodiments 17-18, further comprising the step of transmitting a flow indicator to indicate allocation to at least one flow or group of WTRUs.
20. Group resource allocation is the method described in any of embodiments 17-19 used for flows.
21. The method according to any of embodiments 17-20, wherein the flow parameters in a flow management medium access control (MAC) control message are used to indicate that the flow is the intended flow for group resource allocation. ..
22. The intended flow information is described in any of embodiments 17-21 for group allocation resources determined by matching at least one of the allocation periodicity or allocation size between the flow and the group. Method.
23. A method of allocating resources for use in wireless communication that includes the step of receiving a signal that includes an indicator that indicates the intended flow information.
24. The method of embodiment 23, wherein the intended flow information includes an uplink (UL) assignment.
25. The method described in any of embodiments 23-24, wherein the intended flow information includes the type of uplink (UL) assignment.
26. The method according to any of embodiments 23-25, wherein the intended flow information includes a set of uplink (UL) assignments.
27. The method according to any of embodiments 23-26, wherein the signal is received implicitly or explicitly.
28. The method of any of embodiments 23-27, wherein the intended flow information comprises a masked cyclic redundancy cycle (CRC) of the uplink (UL) allocation information element (IE).
29. IE is the method according to any of embodiments 23-28, which includes a flow identifier.
30. IE is the method according to any of embodiments 23-29, which comprises a predefined flow indicator.
31. The method according to any of embodiments 23-30, further comprising associating a flow type with an uplink (UL) allocation mechanism.
32. The method according to any of embodiments 23-31, wherein the UL allocation mechanism is a permanent allocation or a group resource allocation.
33. The method according to any of embodiments 23-32, wherein the association is established by using a connection management medium access control (MAC) control message.
34. The method according to any one of embodiments 23 to 33, which is an AAI_DSx message, for the connection management MAC control message.
35. The method of any of embodiments 23-34, wherein the predefined flow indicator represents a flow or group of flows.
36. The method according to any of embodiments 23-35, wherein the predefined flow indicator is explicitly defined by a medium access control (MAC) control message.
37. The method according to any of embodiments 23-36, wherein the predefined flow indicator is implicitly defined by the flow parameters.
38. The method of any of embodiments 23-37, further comprising the step of assigning a higher priority to one or more intended flows.
39. The allocation step is the method according to any of embodiments 23-38 based on UL transmission in the uplink (UL) allocation.
40. The method of any of embodiments 23-39, further comprising the step of transmitting data for another flow in an uplink (UL) assignment.
41. The method of any of embodiments 23-40, wherein the data is transmitted using the remaining resources after processing one or more intended flows.
42. The method of any of embodiments 23-41, wherein the data is transmitted using emergency medium access control (MAC) data.
43. The method according to any of embodiments 23-42, wherein the data is transmitted with urgent data.
44. The method according to any of embodiments 23-43, wherein the indicator is an uplink (UL) Assignment Information Element (IE).
45. UL Allocation IE is the method according to any of embodiments 23-44, including the exclusive flag.
46. The method of any of embodiments 23-45, wherein the exclusive flag comprises instructions on how the UL assignment should be used.
47. The method of any of embodiments 23-46, indicating that the exclusive flag should only be used for one or more flows for which UL allocation is intended.
48. The method according to any of embodiments 23-47, wherein the exclusive flag does not indicate bandwidth stealing.
49. The exclusive flag of embodiments 23-48 indicates that the UL assignment should be used for one or more flows intended and for another flow with a higher priority. The method described in either.
50. The method of any of embodiments 23-49, further comprising a step that allows bandwidth stealing for flows with higher priority.
51. The method of any of embodiments 23-50, indicating that the intended flow indicator covers all flows.
52. The method of any of embodiments 23-51, indicating that the intended flow indicator is intended for real-time flows.
53. The real-time flow is one of UGS (Unsolicited Grant Service), rtPS (real-time Polling Service), ertPS (extended rtPS), or aGP (adaptive Granting and Polling service). The method described in any of.
54. The method according to any of embodiments 23-53, indicating that the intended flow indicator targets an ertPS (extended rtPS) flow and an aGP (adaptive Granting and Polling service) flow.
55. The intended flow indicator is described in any of embodiments 23-54, indicating that the allocation targets an adaptive granting and polling service (aGP) flow that defines secondary quality of service (QoS) parameters. Method.
56. The method of any of embodiments 23-55, further comprising receiving a flow identifier (FID) and a flow indicator.
57. The method according to any of embodiments 23-56, wherein the flow indicator is a 1-bit indicator indicating whether the allocation allows stealing.
58. The method according to any of embodiments 23-57, wherein the flow indicator is a 1-bit indicator indicating the type of flow for which stealing is permitted.
59. The type of flow is one of UGS (Unsolicited Grant Service), rtPS (real-time Polling Service), ertPS (extended rtPS), or aGP (adaptive Granting and Polling service). The method described in any of.
60. The method of any of embodiments 23-59, wherein the flow indicator is a 2-bit indicator indicating whether the allocation is for a flow having a real-time rank above a threshold.
61. The method according to any of embodiments 23-60, wherein the flow indicator is the intended flow indicator (UAIFI) for uplink (UL) assignment.
62. The method according to any of embodiments 23-61, wherein the maximum number of uplink (UL) permanent allocations (PAs) is independent of the frames received.
63. A wireless transmit / receive unit configured to perform any one of the methods 1-62.
64. A base station configured to perform any one of the methods 1-62.
65. Advanced Mobile Station (AMS) configured to perform any one of the methods 1-62.
66. Advanced Base Station (ABS) configured to perform any one of the methods 1-62.
67. An eNB (evolved Node-B) configured to perform any one of the methods of embodiments 1-62.
Although features and elements are described above in particular combinations, those skilled in the art will appreciate that each feature or element can be used alone or in any combination with other features and elements. Let's do it. In addition, the methods described herein can be implemented in computer programs, software, or firmware embedded in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, internal hard disks and magnetic media such as removable disks, optomagnetic media, and CD-. Includes, but is not limited to, optical media such as ROM disks and digital versatile disks (DVDs). Software-related processors can be used to implement radio frequency transceivers for use with WTRUs, UEs, terminals, base stations, RNCs, or any host computer.
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2009089388A | Cites | Japan |
| WO2010008146A2 | Cites | World Intellectual Property Organization (WIPO) |
| Park, A.H.,QoS guaranteed IPTV service over Wireless Broadband network ,Advanced Communication Technology, The 9th International Conference on (Volume:2 ),2007年 2月12日,pp.1077-1080,URL,http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4195346 | Non-patent | – |
| Lei Wang,Intended Flow Information for UL PA Allocations (16.2.7),IEEE C802.16m-10/0098,2010年 3月 6日,URL,http://www.ieee802.org/16/tgm/contrib/C80216m-10_0098.doc | Non-patent | – |
26 members in 9 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 30913510 | United States of America | P | |
| 30913510 | United States of America | P | |
| 61309135 | United States of America | – | |
| 2011026467 | United States of America | W | |
| 2011026467 | United States of America | W | |
| 2010309135 | – | – | – |
| 2011026467 | – | – | – |
| US20100309135P | – | – | – |
| WO2011US26467 | – | – | – |
Members26
| Document | Office | Kind | |
|---|---|---|---|
| US2011211447A1 | United States of America | A1 | |
| WO2011109290A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW201218826A | Taiwan Province of China | A | |
| CN102783237A | China | A | |
| EP2543224A1 | European Patent Office (EPO) | A1 | |
| KR20130019386A | Republic of Korea | A | |
| JP2013522939A | Japan | A | |
| RU2012141562A | Russian Federation | A | |
| JP5508552B2This record | Japan | B2 | |
| JP2014143730A | Japan | A | |
| US8891366B2 | United States of America | B2 | |
| US2015078305A1 | United States of America | A1 | |
| TWI520646B | Taiwan Province of China | B | |
| CN105704831A | China | A | |
| JP2016184952A | Japan | A | |
| US9521687B2 | United States of America | B2 | |
| US2017048843A1 | United States of America | A1 | |
| BR112012022206A2 | Brazil | A2 | |
| KR101864457B1 | Republic of Korea | B1 | |
| US10111209B2 | United States of America | B2 | |
| RU2015134604A | Russian Federation | A | |
| RU2015134604A3 | Russian Federation | A3 | |
| RU2684634C2 | Russian Federation | C2 | |
| JP2019165480A | Japan | A | |
| JP2021013199A | Japan | A | |
| EP3787364A1 | European Patent Office (EPO) | A1 |
19 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 5508552
- Publication, DOCDB
- 5508552
- Publication, EPODOC
- JP5508552B
- Application
- 2012556136
- Application, DOCDB
- 2012556136
- Application, EPODOC
- JP20120556136
Titles2
- Japanese
- ハイブリッド式の局ごとおよびフローごとのアップリンク割り当てを実行するための方法および装置
- English
- Methods and equipment for performing hybrid station-by-station and flow-by-flow uplink assignments
Classification
- CPC, 5
- H04W72/569
- H04W72/23
- H04W72/20
- H04W88/08
- H04W72/0446
- IPC, 2
- H04W72 12
- H04W72 14