WO2009049549A1 - Method and device for validity negotiation of management information transport - Google Patents

Abstract

A method and a device for validity negotiation of management information transport. During establishment of the management connection, a user terminal (506) transmits validity information of the management connection to a network side device (502), the network side device (507) confirms validity parameters of the management connection according to the received validity information of the management connection (503), and returns the validity parameters to the user terminal (504), the user terminal confirms validity mechanism of the management connection according to the received validity parameters of the management connection (505). Using the invention, the user terminal and the network side device can transport various information on the management connection supporting the validity mechanism, therefore, the validity of the management information transport is improved.

Description

 Method and apparatus for managing information transmission validity negotiation

 Embodiments of the present invention relate to information transmission technologies, and in particular, to a method and apparatus for managing information transmission validity negotiation. Background technique

 The Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, also known as the IEEE Wireless MAN air interface standard, is an air interface specification for 2 to 66 GHz. It stipulates that the wireless access system can cover up to 50km, so the 802.16 system is mainly used in the metropolitan area network, which is one of the "last mile" broadband access solutions.

In the IEEE 802.16 standard, communication information is mainly classified into data information and management information. Data information is transmitted over unmanaged connections, and management information is transmitted over management connections. When the user terminal (SS) is initially accessed, the Media Access Control (MAC) layer of the SS establishes two management connections: Basic Connection and Primary Management Connection. The basic connection is used by the MAC layer of the base station (BS) and the MAC layer of the SS to exchange short, delay-sensitive MAC layer management information; the primary management connection is used by the MAC layer of the BS and the MAC layer of the SS for long exchanges, MAC layer management information that can tolerate a certain time delay. The SS and BS transmit various management information on the management connection. Summary of the invention

 Embodiments of the present invention provide methods and apparatus for managing information transmission validity negotiation. The method for managing the validity negotiation of the information transmission according to the embodiment of the present invention includes: sending management connection validity information to the network side device;

 Receiving a management connection validity parameter sent by the network side device;

 A validity mechanism for managing the connection is determined according to the management connection validity parameter. The device for managing the validity of the information transmission according to the embodiment of the present invention includes: a sending module, configured to send the management connection validity information to the network side device; and a receiving module, configured to receive the management connection validity sent by the network side device a parameter setting module configured to set a validity mechanism for managing the connection according to the management connection validity parameter.

 A method for negotiating validity of management information transmission according to another embodiment of the present invention includes: receiving management connection validity information sent by a user terminal;

 Determining a management connection validity parameter according to the management connection validity information; and transmitting the management connection validity parameter to the user terminal.

 An apparatus for managing information transmission validity negotiation according to another embodiment of the present invention includes:

 a receiving module, configured to receive management connection validity information sent by the user terminal, and a selecting module, configured to determine a management connection validity parameter according to the management connection validity information;

And a sending module, configured to send the management connection validity parameter to the user terminal. It can be seen from the above technical solution that the present invention establishes a management connection compared to the prior art. In the process, the management connection validity parameter is determined by sending the management connection validity information, thereby determining the validity mechanism of the management connection. Therefore, an effective mechanism is established on the management connection, so that the user terminal and the network side device can transmit various management information on the management connection supporting the validity mechanism, without using the method of waiting for the corresponding timer of the management information to expire. Ensure the correct transmission of management information, which greatly improves the effectiveness of management information transmission and saves access time. DRAWINGS

 FIG. 1 is a schematic diagram of a process of establishing a management connection in the prior art.

 FIG. 2 is a schematic structural diagram of a system for improving the effectiveness of management information transmission in the present invention. Fig. 3 is a schematic view showing the structure of a user terminal for improving the effectiveness of management information transmission in the present invention.

 FIG. 4 is a schematic structural diagram of a network side device for improving the effectiveness of management information transmission in the present invention.

 FIG. 5 is a schematic flowchart of a negotiation management connection validity mechanism in the present invention.

 FIG. 6 is a schematic flowchart of a mechanism for negotiating a basic connection ARQ according to Embodiment 1 of the present invention. FIG. 7 is a schematic flowchart of a mechanism for negotiating a basic connection ARQ according to Embodiment 8 of the present invention. detailed description

 The present invention will be further described in detail below with reference to the drawings and specific embodiments.

Basic connection and primary management connection by Ranging Request (RNG-REQ) information and ranging The response (RNG-RSP) information handshake is established. Referring to Figure 1, Figure 1 is a schematic diagram of the process of establishing a management connection. The process includes the following steps:

 Step 101: The SS sends the RNG-REG information to the BS, where the information includes the negotiation parameters of the SS establishing the basic connection and the primary management connection.

 Step 102: The BS returns the RNG-RSP information to the SS, where the information includes feedback parameters that the BS establishes a basic connection and a primary management connection to the SS.

 After the above process ends, the SS and BS transmit various management information on the newly created management connection.

 During the Negotiate Basic Capabilities of the Initialization phase, the SS sends management information such as a basic capability request (SBC-REQ) to the BS through the management connection, and waits for the BS to respond to the basic capability response through the management connection ( Management information such as SBC-RSP). The basic capability request information and the basic capability response information are information transmitted through the basic connection. In the original standard, the SS determines whether the SBC-RSP information of the BS response is received within a specified long period of time by starting the timer corresponding to the management information, and uses the cyclic redundancy check code (CRC) to determine the received SBC- Is the RSP information correct? If the SS does not receive the SBC-REQ message, or the received SBC-REQ message is incorrect, the SS must wait for the timer to expire before the SS can resend the SBC-REQ message.

 Referring to Figure 2, Figure 2 is a block diagram showing the structure of a system for improving the effectiveness of management information transmission in the present invention. As can be seen from FIG. 2, the system includes: a user terminal 201 and a network side device 202.

The user terminal 201 is configured to generate management connection validity information, send the information to the network side device 202, and receive the management connection validity parameter returned by the network side device 202. According to this parameter, the effectiveness mechanism of managing the connection is set.

 The network side device 202 is configured to receive the management connection validity information sent by the user terminal 201, determine the validity parameter used for managing the connection, and return the determined management connection validity parameter to the user terminal 201.

 Referring to FIG. 3, FIG. 3 is a schematic structural diagram of a user terminal for improving the effectiveness of management information transmission in the present invention. As shown in FIG. 3, the user terminal includes: a generating module 301, a type length value (TLV) encoding module 302, a sending module 303, a receiving module 304, a TLV decoding module 305, and a setting module 306.

 The generating module 301 is configured to generate management connection validity information.

 The TLV encoding module 302 is configured to encode the management connection validity information generated by the generating module 301 in a TLV manner, and carry the encoded management connection validity information in a TLV encoding information field of the RNG-REQ information, and transmit the information to the sending. Module 303.

 The sending module 303 is configured to send the management connection validity information output by the TLV encoding module 302 to the network side device.

 The receiving module 304 is configured to receive a management connection validity parameter sent by the network side device.

The TLV decoding module 305 is configured to receive the RNG-RSP information returned by the network side device from the receiving module 304, extract the management connection validity parameter from the TLV encoding information field of the RNG-RSP information, and use the management connection validity. The parameters are decoded in the TLV manner, and then the decoded management connection validity information is sent to the setting module 306.

The setting module 306 is configured to set a validity mechanism of the SS new management connection according to the management connection validity parameter. In practical applications, the TLV encoding module 302 and the TLV decoding module 305 may not be provided. In this case, the sending module 303 directly receives the management connection validity information generated by the generating module 301 and sends the information to the network measuring device, and the setting module 305 directly receives the management connection validity parameter from the receiving module 304, and sets the SS according to the parameter. New effectiveness mechanism for managing connections.

 Referring to FIG. 4, FIG. 4 is a schematic structural diagram of a network side device for improving the effectiveness of management information transmission in the present invention. As shown in FIG. 4, the network side device includes: a receiving module 401, a TLV decoding module 402, a selecting module 403, a TLV encoding module 404, and a sending module 405.

 The receiving module 401 is configured to receive management connection validity information sent by the user terminal.

 The TLV decoding module 402 is configured to receive the RNG-REQ information sent by the SS from the receiving module 401, extract the management connection validity information from the TLV encoding information field of the RNG-REQ information, and use the management connection validity information to The TLV method performs decoding, and then the decoded management connection validity information is sent to the selection module 403.

 The selection module 403 is configured to determine the management connection validity parameter used according to the management connection validity information output by the TLV decoding module 402.

 The TLV encoding module 404 is configured to encode the management connection validity parameter determined by the selecting module 403 in a TLV manner, and carry the encoded management connection validity parameter in a TLV encoding information field of the RNG-RSP information, and send the same to the TLV encoding information field. Module 405.

 The sending module 405 is configured to send the management connection validity parameter output by the TLV encoding module 404 to the user terminal.

In practical applications, the TLV decoding module 402 and the TLV encoding mode may not be set. Block 404. In this case, the selection module 403 directly receives the management connection validity information from the receiving module 401, and the transmitting module 405 directly receives the management connection validity parameter from the selection module 403, and transmits the parameter to the user terminal.

 Referring to FIG. 5, FIG. 5 is a schematic flow chart of a negotiation management connection validity mechanism in the present invention. As can be seen from Figure 5, the process includes the following steps:

 Step 501: The user terminal generates management connection validity information.

 Step 502: The user terminal sends the management connection validity information to the network side device.

 Step 503: The network side device determines, according to the received management connection validity information, the used management connection validity parameter.

 Step 504: The network side device sends the management connection validity parameter to the user terminal.

 Step 505: The user terminal sets a validity mechanism for managing the connection according to the received management connection validity parameter.

 After the foregoing process ends, the user terminal sets a validity mechanism for managing the connection according to the received management connection validity parameter, and transmits various management information to the network side device according to the selected effective mechanism on the newly created management connection.

 For the network side, the validity negotiation method is:

 Receiving management connection validity information sent by the user terminal;

 Determining a management connection validity parameter according to the management connection validity information; and transmitting the management connection validity parameter to the user terminal.

The effectiveness mechanism includes but is not limited to: basic connection ARQ mechanism, basic connection The fragmentation mechanism or the packaging mechanism of the basic connection; and the ARQ mechanism that mainly manages the connection. Hereinafter, a method for negotiating management information transmission validity provided by the present invention will be described in detail by way of embodiments.

 Embodiment 1

 The IEEE 802.16 standard specifies that the basic connection is established by the RNG-REG and RNG-RSP information handshake during the Ranging phase of the initial SS access. The RNG-REQ information structure is shown in Table 1, and the RNG-RSP information structure is shown in Table 2.

Table 2 This embodiment negotiates an automatic retransmission request (ARQ) mechanism of a basic connection by adding management connection validity information and managing connection validity parameters. Specifically, in this embodiment, the basic connection validity information or the basic connection validity parameter encoded by the TLV method is added to the TLV Encoded Information field of the RNG-REQ or RNG-RSP information, respectively. Negotiate the ARQ mechanism of the basic connection.

 ARQ refers to the method by which the receiving device monitors errors and requests retransmissions. When the receiver detects an error in the packet through the CRC, it will automatically request the sender to resend the packet. The process continues until the packet error is released, or the error continues to exceed the predetermined transmission value.

 As shown in Table 3, the basic connection validity information added in the RNG-REQ information and the basic connection validity parameters added in the RNG-RSP information include: ARQ capability (ARQ support) information and basic connected ARQ parameters. (ARQ parameters for basic connection ).

 table 3

Among them, ARQ capability information: encoded in TLV mode. When the SS sends the parameter to the BS, it is used by the SS to inform the BS whether it supports the ARQ mechanism; the BS sends the parameter to the SS. When the number is used, the BS is used to inform the SS whether the ARQ mechanism is successfully negotiated. The RNG-REQ or RNG-RSP message type of this parameter is 39 and the length is 1 byte. When the SS sends the parameter to the BS, when the parameter is 1, it indicates that the SS supports the ARQ mechanism. When the parameter is 0, it indicates that the SS does not support the ARQ mechanism. When the BS sends the parameter to the SS, when the parameter is 1, the ARQ mechanism negotiates successfully. When the parameter is 0, the ARQ mechanism negotiation fails.

 Basically connected ARQ parameters: Encoded in TLV mode to determine various Service Flow parameters that are basically connected to the ARQ mechanism. The RNG-REQ or RNG-RSP message type of the basic connected ARQ parameter is 34, and the length is variable, which is determined according to the specific service flow. The parameter values include the following service flow parameters:

 ARQ Enabled TLV: It is encoded in TLV mode to determine whether to apply for the ARQ mechanism when the connection is established. This parameter has a service flow type of 18 and a length of 1 byte. When this parameter is set to 1, it indicates that the connection request uses ARQ; when this parameter is set to 0, it indicates that the connection request does not use ARQ.

 2. ARQ window size (ARQ_Window_Size) TLV: Encoded in TLV mode to determine the maximum size of the ARQ window. The parameter has a service flow type of 19 and a length of 1 byte. The value of this parameter ranges from 0 to ARQ and the block number coefficient is divided by 2 (ARQ BSN MODULUS/2). Where ARQ BSN MODULUS and block number

The value of (BSN) is equal, and the value range of BSN is 1 ~ 2048. The value of this parameter ranges from 0 to 1024.

3. ARQ Retry Waiting Interval - Transmitter Delay (ARQ_RETRY_TIMEOUT - Transmitter Delay) TLV: Encoded in TLV mode to determine the transmission management information Delay, including transmission delay and reception management information delay, and other related processing delays. The parameter has a service flow type of 20 and a length of 2 bytes. The value ranges from 0 to 6553500μ _δ (with a granularity of 100 μ _δ ). If this parameter is 0, the time to continue to manage the ARQ data block is infinite.

4. ARQ Retry Waiting Interval - Receiver Delay (ARQ_RETRY_TIMEOUT - Receiver Delay) TLV: Encoded in TLV mode to determine the delay of receiving management information, including receiving delay and sending management information delay, and Other related processing delays. The parameter has a service flow type of 21 and a length of 2 bytes. The value ranges from 0 to 6553500μ _δ (with a granularity of 100 μ _δ ). If this parameter is 0, the time to continue to manage the ARQ data block is infinite.

5. ARQ BLOCK LIFETIME TLV: Encoded in TLV mode to determine the maximum time that the ARQ state machine of the transmitting end can continue to manage the data block after the first transmission of an ARQ block. The parameter has a service flow type of 22 and a length of 2 bytes. The value ranges from 0 to 6553500μ _δ (with a granularity of 100 μ _δ ). If this parameter is 0, the time to continue to manage the ARQ data block is infinite.

6. ARQ Synchronization Hold Time (ARQ_SYNC_LOSS_TIMEOUT) TLV: Encoded in TLV mode to determine the synchronization time of the sender and receiver state machines when transmitting and receiving data transmission. The parameter has a service stream type of 23 and a length of 2 bytes. The value ranges from 0 to 6553500μ _δ (with a granularity of 100 μ _δ ). If this parameter is 0, the synchronization time is infinite.

7. Data block sequential transmission switch (ARQ DELIVER IN ORDER) TLV: Encoded in TLV mode to determine whether the data is received by the receiving MAC in the order in which it was originally transmitted. The layer is sent to the client application layer. The parameter has a service flow type of 24 and a length of 2 bytes. If this parameter is 0, it is not sent in the original sending order; if this parameter is 1, it is sent in the original sending order.

8. Receive Wait Interval (ARQ_RX_PURGE_TIMEOUT) TLV: Encoded in TLV mode to determine the waiting time interval before the receiver receives a data block after successfully receiving a data block. The parameter has a service flow type of 25 and a length of 2 bytes. The value ranges from 0 to 6553500μ _δ (variable by 100). If this parameter is 0, the interval is infinite.

 9. ARQ BLOCK SIZE TLV: Encoded in TLV mode, used to determine the size of the ARQ data block before transmission. This parameter has a service stream type of 26 and a length of 2 bytes. When the SS sends this parameter to the BS, the bit of the parameter (Bit) 0-3 is used to propose the minimum ARQ block size parameter M, and Bit 4-7 is used to suggest the maximum ARQ block size parameter N, Bit 8-15 is reserved and Set to 0 (M≤6, N<6, M≤N), so the BS knows that the minimum size of the SS recommended ARQ block is, and the maximum size is . When the BS sends this parameter to the SS, Bit 0-3 of the parameter is used to determine the final ARQ block size parameter P, Bit 4-15 is reserved and set to 0 (P≤6, M<P<N), so the SS It will be known that the BS determines the final value of the ARQ block size.

10. ARQ processing time ( RECEIVER - ARQ - ACK - PROCESSING - TIME ) TLV: Encoded in TLV mode, this parameter is used to determine that the ARQ receiver processes the received ARQ block and the feedback acknowledges the received/not received (ACK/NAK) ) The time interval between messages, which is an optional parameter. The service stream type of this parameter is 27 and the length is 1 byte. The value ranges from 0 to 255. (Time granularity is determined by the device manufacturer).

 Referring to FIG. 6, FIG. 6 is a schematic flowchart of a mechanism for negotiating a basic connection ARQ according to Embodiment 1 of the present invention. As can be seen from Figure 6, the process includes the following steps:

 Step 601: The SS generates basic connection validity information, encodes the generated basic connection validity information in a TLV manner, and carries the encoded basic connection validity information in a TLV Encoded Information field of the RNG-REQ information.

 Step 602: The SS sends the RNG-REQ information to the BS.

 Step 603: The BS receives the RNG-REQ information sent by the SS, extracts the encoded basic connection validity information from the TLV Encoded Information field of the information, and decodes the basic connection validity information by using a TLV method to solve the basic connection validity information. Determining the basic connection validity parameter used according to the basic connection validity information and the type of the management connection, and then encoding the parameter in a TLV manner, and carrying the encoded basic connection validity parameter in the RNG - The RTP information in the TLV Encoded Information field.

The method for determining the validity parameter is determined by the type of management connection: for basic connections, the processing delay of the ARQ should be as small as possible, so the size of the ARQ block should be slightly smaller, and other validity parameters should also be reduced by ARQ. The delay is the principle. For the main management connection, the processing time of the ARQ is not very strict, and the size of the ARQ block can be slightly larger. When the BS considers that the validity parameter of the SS transmission is unreasonable, then the BS will adjust the parameter. For example, when determining the basic connection validity parameter, if the negotiated ARQ size sent by the SS is large, the BS will adjust the parameter to a reasonable value. When the BS considers that the parameters of the negotiated ARQ sent by the SS are appropriate, the BS will return the parameter as it is. SS.

 In this embodiment, the management connection type is a basic connection, so the validity parameter determination should be based on the principle of reducing the processing delay of the ARQ.

 Step 604, the BS sends the RNG-RSP information to the SS.

 Step 605: The SS receives the RNG-RSP information returned by the BS, extracts the encoded basic connection validity parameter from the TLV Encoded Information field of the information, and decodes the basic connection validity parameter by using a TLV method to solve the basic connection validity parameter. The validity mechanism of the basic connection is determined according to the basic connection validity parameter.

 After the foregoing process ends, the SS sets the basic connection ARQ mechanism according to the received basic connection validity parameter, and transmits various management information to the BS according to the selected ARQ mechanism on the newly established basic connection.

 In this embodiment, the ARQ mechanism of the connection is negotiated during the basic connection establishment process. Through the mechanism, when the CRC check is performed on the management information transmitted on the basic connection, once the transmission error is found, the transmitter can be automatically requested to retransmit the error information without waiting for the timer of the control management information to retransmit, thereby saving the error. Retransmission wait time improves the effectiveness of management information transmission.

 Embodiment 2

This embodiment negotiates a fragmentation mechanism of a basic connection by adding management connection validity information and managing connection validity parameters. Specifically, in this embodiment, the basic connection validity information or the basic connection validity parameter encoded in the TLV manner is added to the TLV Encoded Information field of the RNG-REQ or RNG-RSP information to negotiate the basic connection score. Slice mechanism. Fragmentation is the process of dividing MAC management information into one or more fragments.

 This embodiment is the same as the first embodiment. As shown in Table 4, the basic connection validity information added in the RNG-REQ information, and the basic connection validity parameters added in the RNG-RSP information include: a fragment parameter for basic connection .

 Table 4

 The fragmentation parameter of the basic connection mainly refers to the fragment serial number size (FSN size). Slice serial number size: Encoded in TLV mode to determine the size of the slice serial number. The RNG-REQ or RNG-RSP message type of this parameter is 40 and the length is 1 byte. When this parameter is set to 1, it indicates that the slice serial number is 3 bits; when this parameter is set to 0, it indicates that the slice serial number is 11 bits.

 In this embodiment, during the basic connection establishment process, the fragmentation mechanism of the connection is negotiated. Through this mechanism, the management information transmitted on the basic connection can be fragmented. When the management information to be transmitted is relatively large, the management information can be divided into a plurality of small pieces, and the small pieces are transmitted in other management information packets, thereby saving the transmission time of the management information and improving the effectiveness of the management information transmission.

 Embodiment 3

In this embodiment, by adding management connection validity information and managing connection validity parameters, To negotiate the packaging mechanism of the basic connection. Specifically, in this embodiment, the basic connection validity packet or the basic connection validity parameter encoded in the TLV manner is added to the TLV Encoded Information field of the RNG-REQ or RNG-RSP information to negotiate the basic connection packing. mechanism.

 Packaging is the process of wrapping multiple MAC management information into one MAC Protocol Data Unit (PDU). This embodiment is the same as the first embodiment.

 As shown in Table 5, the basic connection validity information added in the RNG-REQ information, and the basic connection validity parameters added in the RNG-RSP information include: acking parameters for basic connection.

其中，基本连接的打包参数用于协商基本连接打包机制的各种服 务流参数。 基本连接的打包参数的 RNG-REQ或 RNG-RSP消息类型 为 41 , 长度为 2字节。 该参数值包括以下服务流参数：

The packet parameters of the basic connection are used to negotiate various service flow parameters of the basic connection packing mechanism. The RNG-REQ or RNG-RSP message type of the basic connection packing parameter is 41 and the length is 2 bytes. The parameter values include the following service flow parameters:

 1. Fixed-Length Versus Variable-Length SDU Indicator parameter:

TLV mode coding, used to determine whether the packaged management information is fixed length or variable length. The service stream type of this parameter is 15 and the length is 1 byte. When this parameter is set to 1, it is expressed as a fixed length; when this parameter is set to 0, it is expressed as a variable length. 2. SDU Size parameter: Encoded in TLV format to determine the size of fixed length management information. This parameter has a service flow type of 16 and a length of 1 byte. In this embodiment, during the basic connection establishment process, the packaging mechanism of the connection is negotiated. Through this mechanism, management information transmitted on the basic connection can be packaged. When the management information to be transmitted is relatively small, several management information can be sent into one packet for transmission, thereby saving the transmission time of the management information and improving the effectiveness of the management information transmission. Embodiment 4 This embodiment negotiates the validity mechanism of the basic connection by adding management connection validity information and managing connection validity parameters. Specifically, in this embodiment, the basic connection validity information or the basic connection validity parameter encoded in the TLV manner is respectively added in the TLV Encoded Information field of the RNG-REQ or RNG-RSP information to negotiate the validity of the basic connection. Sexual mechanism. This embodiment is the same as the first embodiment. As shown in Table 6, the basic connection validity information added in the RNG-REQ information and the basic connection validity parameters added in the RNG-RSP information include: ARQ capability information, basic connected ARQ parameters, and basic connectivity. The fragmentation parameters and the packaging parameters of the basic connection. Length Applicable Name Type Value (variable length)

 ( bytes )

 0: no ARQ capability SCa,

ARQ capability information 39 1 1: ARQ capable OFDM,

2-255: The 34 variable composite value SCa of the OFDMA basic connection is reserved, ARQ parameter OFDM,

 OFDMA

SC,

0: 3-bit slice number

 Basically connected SCa,

 40 1 1 : 11 -bit fragment number

 Slice serial number size OFDM,

 Default = 1

 OFDMA

SC, basically connected SCa,

 41 2 composite value

 Packing parameters OFDM,

 OFDMA

Table 6 This embodiment negotiates the validity mechanism of the connection during the basic connection establishment process. With this mechanism, the basic connection can support ARQ, fragmentation, and packaging mechanisms. Therefore, the sender may divide each MAC management information into a series of ARQ fragments with consecutive sequence numbers according to the ARQ block size parameter, or package several small MAC management information into one ARQ fragment, each ARQ fragments are transmitted to the receiver separately. When the ARQ fragment transmitted on the basic connection performs the CRC check, once the transmission error is found, the transmitter can be automatically requested to retransmit the erroneous ARQ fragment without waiting for the timer of the control management information retransmission to expire, thereby saving the loyalty. Retransmission waiting time improves the effectiveness of management information transmission. For example, in the SS initialization phase, the SS sends a relatively large message, such as an SBC-REQ message, which can be split into multiple small pieces, once a certain bit of information in a certain piece of the message is erroneous or not successfully transmitted. When you only need to resend the small piece using the ARQ mechanism. This effectively ensures the management of the transmission on the basic connection. Successful reception of interest. Embodiment 5

The IEEE 802.16 standard specifies that the primary management connection is established by the RNG-REG and RNG-RSP information handshake during the measurement phase of the initial SS access. In this embodiment, the ARQ mechanism of the primary management connection is negotiated by adding management connection validity information and managing connection validity parameters. Specifically, in this embodiment, the primary management is negotiated by adding the primary management connection validity information or the primary management connection validity parameter encoded in the TLV mode to the TLV Encoded Information field of the RNG-REQ or RNG-RSP information. The ARQ mechanism of the connection. This embodiment is the same as the first embodiment except that the basic connection validity information and the basic connection validity parameter are replaced with the primary management connection validity information and the primary management connection validity parameter. As shown in Table 7, the main management connection validity information added in the RNG-REQ information, and the main management connection validity parameters added in the RNG-RSP information include: ARQ capability information and ARQ parameters of the main management connection ( ARQ parameters for primary connection ). Length Applicable Name Name Value (variable length)

 ( bytes )

 0: no ARQ capability SCa,

ARQ capability letter

 39 1 1: ARQ capable OFDM, interest

 2-255: Keep OFDMA main management with SCa,

 35 variable composite value

Connected ARQ to OFDM, Number OFDMA

 Table 7

 The ARQ capability information used in the first embodiment is consistent with the ARQ capability information in the first embodiment.

 ARQ parameters for primary management connections: Coded in TLV mode to determine the various service flow parameters that are primarily responsible for managing the ARQ mechanism. The RNG-REQ or RNG-RSP message type that mainly manages the connected ARQ parameters is 35, and the length is variable, which is determined according to the specific service flow. The parameter value includes the service flow parameter that is consistent with the basic connected ARQ parameter in the first embodiment.

 In this embodiment, the ARQ mechanism of the connection is negotiated during the establishment of the primary management connection. Because of the IEEE 802.16 standard, the main management connection fragmentation and packaging mechanism. Therefore, the sender may divide each MAC management information into a series of ARQ fragments with consecutive sequence numbers according to the ARQ block size parameter, or package several small MAC management information into one ARQ fragment, each ARQ fragments are transmitted to the receiver separately. When the ARQ fragment of the management information transmitted on the connection is mainly used for CRC check, once the transmission error is found, the sender can automatically request the transmitter to retransmit the error ARQ fragment without waiting for the timer of the control management information retransmission to expire. The retransmission waiting time improves the effectiveness of management information transmission.

For example, in the SS initialization phase, when the SS sends a relatively large message, the message can be divided into multiple small pieces. If a certain bit of information in a certain piece of the message is erroneous or not successfully transmitted, only the ARQ needs to be utilized. The mechanism can resend the small piece. This effectively ensures successful receipt of management messages transmitted over the primary management connection. Though However, it mainly manages management messages transmitted on the connection, such as dynamic service (DSx) messages, with a three-way handshake process of request/response/acknowledgement (REQ/RSP/ACK) during transmission, with ACK message for acknowledgement protection, but three-way handshake The process is that the protection mechanism above the MAC layer does not conflict with the ARQ mechanism of the MAC layer.

 Embodiment 6

 Since in most cases the information transmitted by the basic connection and the primary management connection is equally important, we generally want to enable the ARQ mechanism on both the basic connection and the primary management connection. Therefore, this embodiment simultaneously negotiates the validity mechanisms of the basic connection and the primary management connection by adding management connection validity information and managing connection validity parameters. Specifically, in this embodiment, the basic connection is negotiated by adding the management connection validity information or the management connection validity parameter encoded by the TLV method in the TLV Encoded Information field of the RNG-REQ or RNG-RSP information. Validity mechanisms (including: ARQ, fragmentation, and packaging mechanisms), and ARQ mechanisms that primarily manage connections.

 This embodiment is identical to the first embodiment except that the basic connection validity information and the basic connection validity parameter are replaced with the management connection validity information and the management connection validity parameter.

0: 无 ARQ能力 SCa ,As shown in Table 8, the management connection validity information added in the RNG-REQ information and the management connection validity parameters added in the RNG-RSP information include: ARQ capability information, basic connected ARQ parameters, and basic connection The fragmentation parameters and the packaging parameters of the basic connection, as well as the ARQ parameters of the primary management connection.

0: No ARQ capability SCa,

ARQ capability letter

 39 1 1 : ARQ capable OFDM, interest

 2-255: Reserved OFDMA

SCa, basically connected

 34 variable composite value OFDM, ARQ parameters

 OFDMA

SCa, main management connection

 35 variable composite value OFDM, ARQ parameters

 OFDMA

SC,

0: 3-bit slice number

 Basically connected SCa,

 40 1 1 : 11 -bit fragment number

 Slice serial number size OFDM, preset = 1

 OFDMA

SC, basically connected SCa,

 41 2 composite value

 Packing parameters OFDM,

 OFDMA

Table 8 This embodiment negotiates the validity mechanism of the connection during the establishment of the basic connection and the primary management connection. With this mechanism, the basic connection can support ARQ, fragmentation, and packaging mechanisms. The main management connection can support the ARQ mechanism and improve the effectiveness of management information transmission. Embodiment 7 When the ARQ parameters of the basic connection and the primary management connection are the same, the embodiment combines the ARQ parameters of the basic connection and the primary management connection into one based on the sixth embodiment. The ARQ parameter is used to reduce the overhead for negotiating the ARQ mechanism in RNG-REQ and RNG-RSP.

 As shown in Table 9, the management connection validity information added in the RNG-REQ information and the management connection validity parameters added in the RNG-RSP information include: ARQ capability information, ARQ parameters, and basic connection fragmentation parameters. And the packaging parameters of the basic connection.

 Table 9

The ARQ capability information used in the first embodiment and the ARQ capability information in the first embodiment are an ARQ parameter: encoded in a TLV manner for determining a basic connection and a primary management connection. Various service flow parameters connected to the ARQ mechanism. The RNG-REQ or RNG-RSP message type of the ARQ parameter is 42 and the length is variable, which is determined according to the specific service flow. The parameter value includes the service flow parameter that is consistent with the basic connected ARQ parameter in the first embodiment.

 It can be seen that the embodiment further saves the overhead of negotiating ARQ parameters on the basis of the sixth embodiment, and makes the transmission of management information more efficient.

 In all of the above embodiments, the ARQ, fragmentation, or packing mechanism is controlled based on a single connection, which is an optional function of the MAC layer. During the connection establishment process, you can specify or negotiate whether to use ARQ, fragmentation or packaging mechanism for a connection. A connection cannot have both ARQ, fragmented or packetized traffic, and non-ARQ, fragmentation or packing mechanisms. The feedback information for establishing an ARQ, fragmentation or packing mechanism can be transmitted as a separate MAC layer management message on the basic connection or piggybacked to the receiving end on the existing connection. All ARQ-enabled connections use a 32-bit CRC to detect possible errors in the PDU. After the ARQ mechanism for managing the connection is established, the ARQ feedback information used to feedback whether the ARQ block is correctly transmitted cannot be fragmented.

 Example eight

 In this embodiment, the ARQ mechanism of the primary management connection is negotiated by adding the management connection validity information and the management connection validity parameter. Specifically, in this embodiment, the main management is negotiated by adding the main management connection validity information or the main management connection validity parameter encoded by the TLV method in the TLV Encoded Information field of the SBC-REQ or SBC-RSP information. The ARQ mechanism of the connection.

This embodiment is the same as the fifth embodiment except that RNG-REQ and RNG-RSP are replaced with SBC-REQ and SBC-RSP. FIG. 7 is a main management unit of negotiation in the eighth embodiment of the present invention; A schematic diagram of the process of connecting the ARQ mechanism. The SBC-REQ is information that the user terminal sends to the network side device, and the SBC-RSP is information that the network side device sends to the user terminal.

 As shown in Table 10, the main management connection validity information added in the SBC-REQ information, and the main management connection validity parameters added in the SBC-RSP information include: ARQ capability information and ARQ parameters of the main management connection ( ARQ parameters for primary connection ).

 Table 10

 The ARQ capability information used in the first embodiment is consistent with the ARQ capability information in the first embodiment.

 ARQ parameters for primary management connections: Coded in TLV mode to determine the various service flow parameters that are primarily responsible for managing the ARQ mechanism. The SBC-REQ or SBC-RSP message type that mainly manages the connected ARQ parameters is 206, and the length is variable, which is determined according to the specific service flow. The parameter value includes the service flow parameter that is consistent with the basic connected ARQ parameter in the first embodiment.

In this embodiment, during the establishment of the primary management connection, the connected ARQ machine is negotiated. System. Due to the IEEE 802.16 standard, the main connection fragmentation and packing mechanism is managed. Therefore, the sender may divide each MAC management information into a series of ARQ fragments with consecutive sequence numbers according to the ARQ block size parameter, or package several small MAC management information into one ARQ fragment, each ARQ fragments are transmitted to the receiver separately. When the ARQ fragment of the management information transmitted on the connection is mainly used for CRC check, once the transmission error is found, the sender can automatically request the transmitter to retransmit the error ARQ fragment without waiting for the timer of the control management information retransmission to expire. The retransmission waiting time improves the effectiveness of management information transmission.

 For example, in the SS initialization phase, when the SS sends a relatively large message, the message can be divided into multiple small pieces. If a certain bit of information in a certain piece of the message is erroneous or not successfully transmitted, only the ARQ needs to be utilized. The mechanism can resend the small piece. This effectively ensures successful receipt of management messages transmitted over the primary management connection. Although the management message transmitted on the connection is mainly managed, such as Dynamic Service (DSx) message, the three-way handshake process with request/response/acknowledgement (REQ/RSP/ACK) during transmission, there is ACK message for acknowledgement protection, but three-way handshake The process is that the protection mechanism above the MAC layer does not conflict with the ARQ mechanism of the MAC layer.

The above embodiments only discuss several application modes of the present invention. Of course, in practical applications, depending on the specific situation, we can also perform any combination of the basic connection ARQ, the fragmentation, the packaging mechanism, or the ARQ mechanism of the main management connection. Negotiation, for example: We can negotiate the ARQ and fragmentation mechanism of the basic connection separately, or negotiate the ARQ of the basic connection and the ARQ mechanism of the main management connection separately. We can also negotiate the ARQ mechanism of the main management connection separately. The above-mentioned "validity information," and "validity parameters" are merely used to better understand the above embodiments of the present invention, and other terms may be used by those skilled in the art.

 The term "receiving" in this embodiment may be understood as actively acquiring information from other modules or receiving information sent by other modules. The above modules may be distributed in one device or distributed in multiple devices. Combined into one module, it can be further split into multiple sub-modules.

 Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform, and the technical solution of the present invention. It can be embodied in the form of a software product that can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for making a computer device (may It is a personal computer, a server, or a network device, etc.) that performs the methods described in various embodiments of the present invention.

 In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request A method for managing the validity of the information transmission, the method comprising: sending the management connection validity information to the network side device;  Receiving a management connection validity parameter sent by the network side device;  A validity mechanism for managing the connection is determined according to the management connection validity parameter. 2. The method according to claim 1, wherein the transmitting the management connection validity information to the network side device comprises: the management connection validity information is encoded by a type length value TLV mode, and the coded management is performed. The connection validity information is carried in the ranging request information, and the ranging request information is sent to the network side device;  The management connection validity parameter sent by the receiving network side device includes: receiving ranging response information sent by the network side device, extracting a management connection validity parameter from the ranging response information, and extracting the extracted management connection validity parameter Decoding in TLV mode.  The method according to claim 1 or 2, wherein the management connection validity parameter comprises: a base connection fragmentation parameter and/or a basic connection packing parameter.  The method according to claim 1 or 2, wherein the management connection validity information or the management connection validity parameter is one of the following cases:  ARQ capability information and automatic retransmission request for basic connection ARQ parameters, or  ARQ capability information and ARQ parameters of the main management connection,  Or ARQ capability information and basic connection ARQ parameters and ARQ parameters for primary management connections Number.  The method according to claim 4, wherein the ARQ information of the basic connection and the ARQ parameter of the primary management connection are merged into a group of ARQ parameters.  The method according to claim 1, wherein the transmitting the management connection validity information to the network side device comprises: encoding the generated management connection validity information by a type length value TLV method, and encoding the encoded The management connection validity information is carried in the basic capability request information, and the basic capability request information is sent to the network side device; the management connection validity parameter sent by the receiving network side device includes: receiving basic capability response information sent by the network side device And extracting a management connection validity parameter from the basic capability response information, and decoding the extracted management connection validity parameter in a TLV manner.  The method according to claim 6, wherein the management connection validity information or the management connection validity parameter is: ARQ capability information and an ARQ parameter of a primary management connection.  A device for managing the validity of the information transmission, comprising: a sending module, configured to send the management connection validity information to the network side device; and a receiving module, configured to receive the management connection sent by the network side device a validity parameter; a setting module, configured to set a validity mechanism for managing the connection according to the management connection validity parameter. 9. The apparatus according to claim 8, further comprising: a type length value TLV encoding module, configured to encode the management connection validity parameter in a TLV manner, and to validate the encoded management connection Parameters carried in the distance measurement please In the request information, transmitted to the sending module;  The TLV decoding module is configured to receive the ranging response information sent by the network side device from the receiving module, extract the management connection validity parameter from the ranging response information, and decode the management connection validity parameter by using a TLV manner. Send to the setup module.  The method according to claim 8 or 9, wherein the management connection validity information or the management connection validity parameter comprises: a base connection fragmentation parameter and/or a basic connection packing parameter.  The method according to claim 8 or 9, wherein the management connection validity parameter is one of the following conditions: ARQ capability information and an automatic retransmission request of the basic connection, an ARQ parameter,  Or  ARQ capability information and ARQ parameters of the main management connection,  Or  ARQ capability information and basic connection ARQ parameters and ARQ parameters of the main management connection.  12. The apparatus according to claim 8, further comprising: a type length value TLV encoding module, configured to use the management connection validity information The TLV method performs coding, and carries the encoded management connection validity information in the basic capability request information, and sends the information to the sending module; The TLV decoding module is configured to receive basic capability response information sent by the network side device from the receiving module, extract the management connection validity parameter from the basic capability response information, and decode the management connection validity parameter by using a TLV manner. Send to settings Module.  The device according to claim 12, wherein the management connection validity information or the management connection validity parameter is: ARQ capability information and an ARQ parameter of a primary management connection.  A method for managing validity negotiation of information transmission, comprising: receiving management connection validity information sent by a user terminal;  Determining a management connection validity parameter according to the management connection validity information; and transmitting the management connection validity parameter to the user terminal.  The method according to claim 14, wherein the receiving the management connection validity information sent by the user terminal comprises: receiving the ranging request information sent by the user terminal, and extracting the ranging request information sent by the user terminal. The connection validity parameter is managed, and the extracted management connection validity parameter is decoded in a TLV manner;  Determining the management connection validity parameter according to the management connection validity information includes: determining the management connection validity parameter according to the management connection validity information sent by the user terminal, and the type to which the management connection belongs;  The sending the management connection validity parameter to the user terminal includes: encoding the determined management connection validity parameter in a TLV manner, carrying the encoded management connection validity parameter in the ranging response information, and transmitting the ranging response Information to the user terminal.  The method according to claim 14 or 15, wherein the management connection validity information or the management connection validity parameter comprises: a base connection fragmentation parameter and/or a basic connection packing parameter. 17. The method of claim 14 or 15, wherein said management company The validity parameter is one of the following:  ARQ capability information and automatic retransmission request for basic connection ARQ parameters,  Or  ARQ capability information and ARQ parameters of the main management connection,  Or  ARQ capability information and basic connection ARQ parameters and ARQ parameters of the main management connection.  The method according to claim 17, wherein the basic connected ARQ information and the primary management connection ARQ parameters are the same when combined into a set of ARQ parameters.  The method according to claim 14, wherein the receiving the management connection validity information sent by the user terminal comprises: receiving the basic capability request information sent by the user terminal, and extracting the basic capability request information sent by the user terminal. The connection validity parameter is managed, and the extracted management connection validity parameter is decoded in a TLV manner;  Determining the management connection validity parameter according to the management connection validity information includes: determining the management connection validity parameter according to the management connection validity information sent by the user terminal, and the type to which the management connection belongs;  The sending the management connection validity parameter to the user terminal includes: encoding the determined management connection validity parameter in a TLV manner, carrying the encoded management connection validity parameter in the basic capability response information, and transmitting the basic capability response Information to the user terminal. 20. The method according to claim 19, wherein the management connection validity information or the management connection validity parameter is: ARQ capability information and a primary management connection. ARQ parameters.  An apparatus for managing information transmission validity negotiation, comprising: a receiving module, configured to receive management connection validity information sent by a user terminal; and a selecting module, configured to determine management according to the management connection validity information Connection validity parameter;  And a sending module, configured to send the management connection validity parameter to the user terminal.  The device of claim 21, further comprising: a type length value TLV decoding module, configured to receive, from the receiving module, the ranging request information sent by the user terminal, and manage the connection validity parameter from the ranging Extracting the request information, decoding the management connection validity parameter in a TLV manner, and transmitting the decoded management connection validity information to the selection module;  The TLV coding module is configured to encode the management connection validity parameter determined by the selection module in a TLV manner, and carry the encoded management connection validity parameter in the ranging response information, and send the signal to the sending module.  The method according to claim 21 or 22, wherein the management connection validity information or the management connection validity parameter comprises: a base connection fragmentation parameter and/or a basic connection packing parameter.  The method according to claim 21 or 22, wherein the management connection validity parameter is one of the following conditions: ARQ capability information and an automatic retransmission request of the basic connection, an ARQ parameter,  Or ARQ capability information and ARQ parameters of the main management connection, or  ARQ capability information and basic connection ARQ parameters and ARQ parameters of the main management connection.  The device according to claim 21, further comprising: a type length value TLV decoding module, configured to receive basic capability request information sent by the user terminal from the receiving module, and manage the connection validity parameter from the basic capability Extracting the request information, decoding the management connection validity parameter in a TLV manner, and transmitting the decoded management connection validity information to the selection module;  The TLV coding module is configured to encode the management connection validity parameter determined by the selection module in a TLV manner, and carry the coded management connection validity parameter in the basic capability response information, and send the data to the sending module.  The device according to claim 25, wherein the management connection validity information or the management connection validity parameter is: ARQ capability information and an ARQ parameter of a primary management connection.