JP5539520B2 - Technology for negotiating capabilities between networked devices - Google Patents

Description

  The subject matter disclosed herein generally relates to techniques in which a mobile station negotiates capabilities with a base station.

  IEEE Std 802.16-2009 describes a capability negotiation procedure in which mobile stations and base stations exchange MAC management messages during network entry and re-join. IEEE Std. 802.16-2009 section 6.3.2.3.23 states that mobile stations use variable length messages to request capabilities, and that base stations use variable length messages to indicate capability responses. It is described. Immediately after the completion of ranging, the mobile station transmits the SBC-REQ message (SS basic capability request) with each of its capabilities set to “on”, thereby setting the mobile station's basic capabilities to the base station. (Figure 75 of IEEE Std 802.16-2009). The base station responds with an SBC-RSP message (SS basic capability response) in which the common part of the capability of the mobile station and the base station is set to “on” (FIGS. 76 and 77 of IEEE Std 802.16-2009).

  However, there are various potential problems with the IEEE Std 802.16-2009 capability negotiation procedure. The capability negotiation MAC management message is very large. The resulting MAC message is often split into multiple MAC Protocol Data Units (MAC PDUs), which can be very error prone in severe channel conditions, especially for cell edge users, and further network Incurs join / rejoin delay and high control plane latency.

Wireless communication system involved in capability configuration session according to an embodiment Diagram showing the order of capability classes from class 0 to higher class number N (N ≧ 0) SBC-REQ message from IEEE Std 802.16-2009 SBC-RSP message from IEEE Std 802.16-2009 Process for negotiating capabilities between a mobile station and a base station according to an embodiment System according to an embodiment

  Embodiments of the present invention will be described by way of example and not by way of example in the drawings. In the drawings, like reference numerals indicate like elements.

  Reference to “one embodiment” or “an embodiment” throughout this specification means that the particular function, structure, or feature described with respect to the embodiment is included in at least one embodiment of the invention. Thus, the appearance of the terms “one embodiment” or “an embodiment” in various places throughout the specification is not necessarily referring to the same embodiment. Furthermore, the particular functions, structures or features may be combined in one or more embodiments.

  Embodiments of the present invention may be used in a variety of applications. Certain embodiments of the present invention may include various devices and systems (eg, transmitters, receivers, transceivers, transceivers, wireless communication stations, wireless communication devices, wireless access points (APs), modems, wireless modems. Personal computer (PC), desktop computer, mobile computer, laptop computer, notebook computer, tablet computer, server computer, handheld computer, handheld device, personal digital assistant (PDA) device, handheld PDA Device, network, wireless network, local area network (LAN), wireless LAN (WLAN), metropolitan area network (MAN: Metropolitan A) rea Network), Wireless MAN (WMAN: Wireless MAN), Wide Area Network (WAN), Wireless WAN (WWAN: Wireless WAN), existing IEEE 802.11, 802.11a, 802.11b, 802.11e, 802.11g, Devices that operate in accordance with the 802.11h, 802.11i, 802.11n, 802.16, 802.16d, 802.16e, 802.16m or 3GPP standard and / or future versions and / or derivatives thereof and / or the aforementioned standard LTE (Long Term Evolution) And / or network, personal area network (PAN), wireless PAN (WPAN), unit and / or device that is part of the aforementioned WLAN and / or PAN and / or WPAN network, one-way And / or two-way wireless communication system, cellular wireless telephone communication system, cellular telephone, wireless telephone, personal communication system (PCS) device, wireless communication device Embedded PDA device, Multiple Input Multiple Output (MIMO) transceiver or device, Single Input Multiple Output (SIMO) transceiver or device, Multiple Input Single Output (MISO) transceiver or device, Multi Receiver Chain (MRC) transceiver or device, “Smart” May be used in conjunction with "antenna" technology or transceivers or devices with multiple antenna technology, etc.).

  Certain embodiments of the present invention may include one or more types of wireless communication signals and / or systems (eg, Radio Frequency (RF), Infra Red (IR), Frequency Division Multiplexing (FDM)). Division Multiplexing, Orthogonal FDM (OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA) Multiple Access), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), Extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA2000, MDM ( (Multi-Carrier Modulation), DMT (Discrete Multi-Tone), Bluetooth (RTM), ZigBee (TM), etc.). Embodiments of the invention may be used in various other apparatuses, devices, systems and / or networks. IEEE 802.11x may indicate any existing IEEE 802.11 specification, including but not limited to 802.11a, 802.11b, 802.11e, 802.11g, 802.11h, 802.11i, and 802.11n.

  Various embodiments use a given capability class and capability class index to indicate capabilities, so that mobile stations (MS) and base stations (BS) can join between network joins / rejoins or handovers. Provide capability negotiations between. TLV (Type / Length / Value) encoded or ASN.1 (Abstract Syntax Notation One) encoded MAC management messages are exchanged during capability negotiation as described on pages 333-336 of IEEE Std 802.16-2009. May be. Capability negotiations may be performed regardless of the capabilities of the desired mobile station or base station to ensure proper interoperability. Successful capability class negotiation involves the mobile station and base station supporting a common set of functions or capabilities.

  In various embodiments, Type / Length / Value may be defined using several “reserved value” fields of MAC management messages compliant with IEEE Std 802.16-2009. TLV coding may be used to convey capability index values in SBC-REQ and SBC-RSP messages. An IEEE 802.16m MAC management message is distinguished from its conventional counterpart by an “AAI” prefix indicating an “Advanced Air-Interface” message. Therefore, these MAC management messages are indicated by AAI_SBC-REQ and AAI_SBC-RSP of the IEEE 802.16m specification.

  Various embodiments allow capability signaling using a small number of bits and a fallback mechanism in case of system failure. Thus, problems with additional network join / rejoin delay and high control plane latency resulting from large capability negotiation MAC management messages can be mitigated. Various embodiments reduce the amount of bandwidth used to negotiate capabilities. Communication interruptions are unlikely to interfere with capability negotiation.

  FIG. 1 shows a wireless communication system involved in a capability configuration session according to an embodiment. The mobile station 110 transmits a capability request message indicated as SBC-REQ to the base station 120. The base station 120 indicates the capability to the mobile station 110 using the SBC-RSP message. The radio interface between the mobile station 110 and the base station 120 may be compliant with IEEE 802.16m specified in the latest approved version of the IEEE 802.16m standard (assumed in 2010). Other wireless communication protocols such as but not limited to 3GPP LTE and LTE-Advanced may be used. In various embodiments, capabilities may be indicated using a capability class index.

  FIG. 2 shows the order of capability classes from class 0 to higher class number N (N ≧ 0). A capability class is defined as a unique set of functions, configuration parameters, radio interface protocol versions and / or services that can uniquely describe a mobile station's implementation or configuration while operating in a cellular network. As shown in FIG. 2, capability classes may be nested such that capability class i + 1 includes all the functions and parameters of capability class i (i ≧ 0). In some cases, capability classes i and j (i ≠ j) may be mutually exclusive if the functions and parameters specified in capability class i are completely or partially independent of capability class j. In various embodiments, increasing class numbers correspond to increasing or improving device capabilities. In various embodiments, the higher the capability index number, the better functionality is supported.

  The entire set of features or configuration parameters supported by a standard or system profile (eg, both mandatory and optional features) may be categorized into different capability classes. For example, “capability class 0” indicates an initial setting configuration corresponding to “CAPABILITY_INDEX = 0”. The “CAPABILITY_INDEX” value ranges from 0 to N, and the number of function divisions and capability classes depends on the device class and other considerations to be considered when developing a system profile or actual specification. The functions and configuration parameters included in the base class may be sufficient to meet the minimum performance requirements of applicable wireless communication standards.

  For example, capability class 0 indicates a default capability index and basic feature set or configuration parameters and need not be signaled. The mobile station, by default, supports a basic set of functions or configuration parameters (as defined in the system profile or standard specification itself) or a revision of the radio interface protocol. In such cases, there is no need to negotiate and configure basic capabilities. Thus, by default, the base station may assume that the mobile station supports basic capabilities, and MAC management messages are not exchanged when the mobile station or base station operates based on the basic capability feature set. .

  A mobile station can be supported by a mobile station if it can support a higher revision of the radio interface (physical layer (PHY) or medium access control (MAC) layer) protocol and uses improved features A MAC management message is sent to the base station using the SBC-REQ indicating the highest capability index. As an example, capability class 0 may include parameters related to basic antenna configuration in downlink and uplink, basic multi-antenna mode, minimum transmission bandwidth, other parameters described in section 11 of IEEE Std. 802.16-2009, or WMF. -T23-001-R015v01 MSP-Common-Part, WMF-T23-002-R015v01, MSP-TDD and other parameters specified in the WMF-T23-002-R015v01 MSP-FDD system profile may be included. Capability class 1 may include all the functions included in capability class 0 and further functions such as higher multi-antenna mode and minimum transmission bandwidth.

  In response to receiving a MAC management message (eg, SBC-REQ or AAI_SBC-REQ) that includes a capability index from the mobile station, the base station can support the requested feature set or MAC and / or PHY protocol revisions It is determined whether or not. If the base station supports or allows the use of the improved features, the base station responds with a MAC management message using SBC-RSP (or AAI_SBC-RSP) and informs the mobile station of the determination. The base station signals a capability index that is less than or equal to that requested by the mobile station.

  In the event of a failure at any stage of operation, the mobile station and base station fall back to “capability class 0” and resume negotiation of a new “capability class” as necessary.

  The capabilities of each capability class may be identified or communicated to the mobile station and base station during initial device setup by an operator or vendor, or the device may be programmed or updated over the air interface.

  3 and 4 show the SBC-REQ and SBC-RSP message formats from IEEE Std 802.16-2009, respectively. In various embodiments, variable size fields (TLV Encoded Information in SBC-REQ and TLV Encoded Attributes in SBC-RSP) are used to indicate the capability index of each mobile station and base station.

  FIG. 5 illustrates a process for negotiating capabilities between a mobile station and a base station according to an embodiment.

  Block 502 includes the mobile station selectively transmitting a capability class index if the requested capability is above the system default. For example, variable size TLV Encoded Information of SBC-REQ (or AAI_SBC-REQ) may be used to transmit the capability class index from the mobile station.

  Block 504 includes the base station indicating the capability class using the index. The indicated capability class is less than or equal to the requested capability class of the mobile station. For example, a variable size TLV Encoded Attributes field of SBC-RSP (or AAI_SBC-RSP) may be used to transmit the capability class index from the base station.

  FIG. 6 shows a system according to an embodiment. Computer system 600 may include a host system 602 and a display 622. The computer system 600 may be implemented on a handheld personal computer, mobile phone, set-top box or any computing device. The host system 602 may include a chipset 605, a processor 610, a host memory 612, a storage device 614, a graphics subsystem 615, and a radio 420. Chipset 605 may provide intercommunication between processor 610, host memory 612, storage device 614, graphics subsystem 615, and radio 420. For example, chipset 605 may include a storage device adapter (not shown) that can provide intercommunication with storage device 614. For example, the storage device adapter may be able to communicate with the storage device 614 according to any of the following protocols: SCSI (Small Computer Systems Interface), FC (Fiber Channel) and / or S-ATA (Serial Advanced Technology Attachment).

  The processor 610 may be implemented as a CISC (Complex Instruction Set Computer) or RISC (Reduced Instruction Set Computer) processor, multi-core, or other microprocessor or central processing unit.

  The host memory 612 is implemented as a volatile memory device such as, but not limited to, a random access memory (RAM), a dynamic random access memory (DRAM), or a static RAM (SRAM). May be. Storage device 614 is implemented as, but not limited to, a magnetic disk drive, optical disk drive, tape drive, internal storage device, attached storage device, flash memory, battery-backed SDRAM (synchronous DRAM) and / or network accessible storage device. May be.

  The graphics subsystem 615 may perform processing of images such as still images for display or video. An analog or digital interface may be used to communicatively couple graphics subsystem 615 and display 622. For example, the interface may be any one of HDMI (High-Definition Multimedia Interface), a display port, wireless HDMI and / or wireless HD compliant technology. Graphics subsystem 615 may be integrated into processor 610 or chipset 605. Graphics subsystem 615 may be a stand-alone card that is communicatively coupled to chipset 605.

  Radio 620 may include one or more radios capable of transmitting and receiving signals in accordance with applicable radio standards such as, but not limited to, any version of IEEE 802.11 and IEEE 802.16. In various embodiments, the radio 620 performs the techniques described with respect to FIG. 1 to negotiate capabilities with the base station. For example, the radio 620 may include at least a physical layer interface and a medium access controller.

  Embodiments of the present invention include one or more microchips or integrated circuits interconnected using a motherboard, logic by wiring, software stored by a memory device and executed by a microprocessor, firmware, and application specific integration. It may be implemented as any one or combination of a circuit (ASIC: application specific integrated circuit) and / or a field programmable gate array (FPGA). The term “logic” may include, by way of example, software or hardware and / or a combination of software and hardware.

  Embodiments of the present invention, for example, when performed by one or more machines (such as a computer, a network of computers or other electronic devices) perform one or more operations according to embodiments of the present invention. It may be provided as a computer program product that may include one or more machine-readable media having machine-executable instructions stored thereon. Machine-readable media include, but are not limited to, floppy (registered trademark) disks, optical disks, CD-ROM (Compact Disc-Read Only Memory), magneto-optical disks, ROM (Read Only Memory), RAM (Random Access Memory), EPROM ( May include Erasable Programmable Read Only Memory (EEPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic or optical card, flash memory, or other types of media / machine readable media suitable for storing machine-executable instructions .

  The drawings and the foregoing description give examples of the invention. Although shown as multiple separate functional items, those skilled in the art will recognize that one or more of such elements may be suitably combined into a single functional element. Alternatively, the specific element may be divided into a plurality of functional elements. Elements from one embodiment may be added to other embodiments. For example, the order of the processes described here may be changed and is not limited to the method described here. Furthermore, the operations of any of the flowcharts need not be performed in the order shown. Also, not all operations need to be performed. In addition, operations that do not depend on other operations may be executed in parallel with other operations. However, the scope of the present invention is not limited to these specific examples. Several variations are possible, such as differences in structure, size and material usage, whether or not explicitly indicated in the specification. The scope of the invention is as broad as at least given by the claims.

Claims (22)

Logic for storing the capabilities of the mobile station, the capabilities being at least related to downlink and uplink basic antenna configurations, basic multi-antenna mode, and minimum transmission bandwidth;
In response to the capability of the mobile station being above the initial setting level, the capability index code is used to selectively negotiate the capability with the base station, and the capability of the mobile station is at the initial setting level. Te is a logic that does not exhibit a capability index code to the base station, the capability index code, table a plurality of capabilities of said mobile station, said index code capability class i + 1 is capability class i ( logic representing a capability class including all functions and parameters of i ≧ 0) ;
Logic for selectively accessing a second capability index code from the base station in response to receiving a second capability index code from the base station, wherein the second capability index code is the base station Logic that represents multiple capabilities of
Logic for selectively applying capabilities based in part on the received capabilities of the base station in response to negotiations with the base station, or at least the capabilities of the mobile station are at the initial setting level Depending on the situation, a mobile station having logic to selectively apply capabilities at an initial setting level.   The mobile station according to claim 1, wherein the capability index code defines a function, a configuration parameter, a radio protocol interface revision or a set of services that may describe the configuration of the mobile station.   The mobile station according to claim 1, wherein the capability classes i and j are i ≠ j, and the functions and parameters defined in the capability class i are completely or partially independent of the capability class j.   The logic that selectively negotiates capabilities with the base station using the capability index code is based on the TLV (Type / Length / Value) Encoded Information field of the AAI-SBC-REQ (Advanced Air Interface SS basic capability request) message format. The mobile station according to claim 1, wherein the code is used to transmit the code.   The logic further comprises receiving the second capability index code using a TLV (Type / Length / Value) Encoded Attributes field of an AAI-SBC-RSP (Advanced Air Interface SS basic capability response) message format. The mobile station described in 1. Logic for storing the capabilities of the base station, the capabilities being at least related to downlink and uplink basic antenna configurations, basic multi-antenna mode, and minimum transmission bandwidth;
Logic for selectively accessing capabilities from a mobile station based on a capability index code, wherein the code from the mobile station represents a plurality of capabilities of the mobile station above a default capability of the mobile station. the code represents the capability class containing all the functions and parameters of the capability class i + 1 is capability class i (i ≧ 0), the base station, the capability of the system initialization capabilities of the base station Negotiating capabilities if higher, and the base station communicates capabilities even when the capabilities of the base station are the default capabilities of the system ; and
In response to receiving the capability from the mobile station, a logic that selectively transmits the capability of the base station to the mobile station using a second capability index code, wherein the second capability index code is And a base station having logic indicating capabilities supported by the base station. The base station according to claim 6 , wherein the capability index code defines a function, configuration parameter, radio protocol interface revision or set of services that may describe a mobile station configuration. The base station according to claim 6 , further comprising logic to access the capability index code from TLV (Type / Length / Value) encoded information of an AAI-SBC-REQ (Advanced Air Interface SS basic capability request) message format. The selectively transmitting logic transmits the second capability index code using a TLV (Type / Length / Value) Encoded Attributes field of an AAI-SBC-RSP (Advanced Air Interface SS basic capability response) message format. The base station according to claim 6 . A system for setting capabilities,
A display device;
A memory configured to store the capabilities of the mobile station, the capability being at least related to downlink and uplink basic antenna configurations, a basic multi-antenna mode, and a minimum transmission bandwidth;
A processor communicatively coupled to the display device and the memory;
The processor is
In response to the capability of the mobile station being above an initial setting level, a capability index code is used to selectively initiate capability negotiation with a base station, provided that the capability index code is Wherein the code represents a capability class in which capability class i + 1 includes all functions and parameters of capability class i (i ≧ 0);
In response to receiving a second capability index code from the base station, the second capability index code from the base station is selectively accessed, provided that the second capability index code is stored in the base station. Represents multiple capabilities,
In response to negotiations with the base station, selectively applying capabilities based in part on the received capabilities of the base station, or at least in the absence of capability negotiations with the base station System configured to selectively apply default level capabilities. The system according to claim 10 , wherein the capability index code is transmitted using a TLV (Type / Length / Value) Encoded Information field of an AAI-SBC-REQ (Advanced Air Interface SS basic capability request) message format. The second capability index code is received using AAI-SBC-RSP (Advanced Air Interface SS basic capability response) message format TLV (Type / Length / Value) Encoded Attributes field, according to claim 10 System. A computer-implemented method for setting capabilities, comprising:
Selectively transmitting an AAI-SBC-REQ message to a base station in response to the mobile station having capabilities that operate above a default capability class, wherein the AAI-SBC-REQ message is the capability class of the mobile station includes a table to index, the capability class, table a plurality of capabilities of said mobile station, the index, all the functions of the capability class i + 1 is capability class i (i ≧ 0) And representing a capability class including parameters ,
Selectively accessing an AAI-SBC-RSP message received from the base station, wherein the AAI-SBC-RSP message includes a capability index of the base station, and the AAI-SBC-RSP message includes the Transmitting a capability index of a numerical value below the capability class;
Selectively applying capabilities based in part on the capability index of the base station in response to at least the mobile station not transmitting capabilities that operate above a default capability class;
Selectively applying capabilities based in part on the capability index of the base station in response to receiving the capability index of the base station. 14. The method of claim 13 , wherein the capability class defines a function, configuration parameters, a revised version of a radio protocol interface or a specific set of services that can describe a mobile station configuration. 14. The method according to claim 13 , wherein the capability classes i and j are i ≠ j, and the functions and parameters defined in the capability class i are completely or partially independent of the capability class j. 14. The method of claim 13 , wherein selectively transmitting an AAI-SBC-REQ message to the base station comprises transmitting the code using a TLV Encoded Information field. The method of claim 13 , further comprising receiving an AAI-SBC-RSP message from the base station using a TLV Encoded Attributes field. Capabilities indicated by the capability class i is a basic antenna configuration of the downlink and uplink, is selected from the group comprising a basic multi-antenna mode, the parameters related to the minimum transmission bandwidth, according to claim 13 Method. Capability indicated by the capability index code of the (i + 1) is provided with all functions included in capability classes i, is selected from the group having a higher multi-antenna mode and higher minimum transmission bandwidth, according to claim 18 The method described in 1. The method according to claim 13 , further comprising the step of causing the mobile station and base station to identify the capabilities of each capability class during initial device configuration. The method of claim 13 , wherein sending an AAI-SBC-REQ message to the base station comprises sending an AAI-SBC-REQ message to the base station during network join, network rejoin or network handover. . The method of claim 13 , wherein sending an AAI-SBC-REQ message to a base station comprises sending a highest capability index supported by the mobile station.

Images