TWI444025B - Protocol engine for processing data in a wireless transmit/receive unit - Google Patents

Description

Protocol engine for processing data in the wireless transmit/receive unit

The present invention relates to processing data in a wireless transmit/receive unit (WTRU) (in other words, a mobile station). More particularly, the invention relates to a protocol engine (PE) for processing data in a wireless transmit/receive unit (WTRU).

A protocol stack in a wireless communication system such as the Global System for Mobile Communications (UMTS) Frequency Division Multiplexing (FDD) system is a collection of internally related system components. The agreement stacks the data (application data or network data), reformats and encapsulates it for transmission through the empty mediation plane, and reconstructs the data on the receiving side of the empty mediation side. The agreement stack is also responsible for the control, configuration and maintenance of the null interface parameters. For example, the protocol stack controls parameters related to data speed, physical channel configuration, clock, data connection delivery, and the like.

As an example, the access layer (AS) portion 100 of the Global System for Mobile Communications (UMTS) Frequency Division Multiplexing (FDD) protocol stack is shown in FIG. As shown in FIG. 1, the Global System for Mobile Communications (UMTS) Access Layer (AS) 100 includes Radio Resource Control (RRC) 102, Radio Access Bearer Management (RABM)/Packet Data Aggregation Protocol (PDCP). 104. Wide/Multi-Block Control (BMC) 106, Radio Link Control (RLC) 108 and Media Access Control (MAC) 110.

The Radio Resource Control (RRC) 102 performs initial cell selection and reselection (mobility), Radio Resource Control (RRC) associated with the Global System for Mobile Communications (UMTS) Universal Terrestrial Radio Access Network (UTRAN). Letter) establishment, maintenance and release, radio bearer, transmission channel (TrCH) and physical channel establishment, maintenance and release (in other words, wireless transmit/receive unit (WTRU) according to Universal Land Radio Access Network (UTRAN) commands) Layer 2 and Layer 1 configurations) include control and measurement returns for High Speed Uplink Packet Access (HSUPA) and High Speed Uplink Packet Access (HSUPA) channels.

The Radio Access Bearer Management (RABM)/Packet Data Aggregation Protocol (PDCP) 104 is based on the Internet Engineering Task Force (IETF) Request for Correction (RFC) 2507 and Request for Correction (RFC) 3095, Lossless Service Radio Network. Road Controller (SRNC) Relocation, Netscape Server Application Development Interface (NSAPI)/Packet Data Protocol (PDP) file management of Radio Access Bearer (RAB) channel mapping, implementation of Internet Protocol (IP) Header compression, which includes Quality of Service (QoS) management and Radio Access Bearer (RAB) re-establishment (in other words, Radio Access Bearer Management (RABM) functionality).

The Broadcast/Multi-Block Control (BMC) 106 performs the delivery of cell-wide information to the non-access stratum (NAS) (in other words, the upper layer), the cell-wide scheduling estimation, and the cell-wide distribution service (CBS). ) configuration for discontinuous reception.

The Radio Link Control (RLC) 108 performs the automatic forwarding of application data units (in other words, Service Data Units (SDUs)) between the airborne active transmission blocks in the air and data planes (in other words, segmentation and concatenation) ), network configuration retransmission, and data unit order delivery according to a particular mode (in other words, an acknowledgment mode (RM), a non-acknowledgment mode (UM), and a transparent mode (TM)).

The medium access control (MAC) 110 performs logical channel mapping of the transmission channel, selects an appropriate uplink transmission format combination according to the instantaneous data rate in the WTRU, and media access control - e/es (MAC-e/es) protocol high-speed uplink packet access (HSUPA) implementation, and media access control-hs (MAC-hs) protocol high-speed downlink packet access (HSDPA) implementation, including media access Control-hs (MAC-hs) reordering, media access control - hs (MAC-hs) protocol data unit (PDU) multiplexing, and so on. The implementation of the Media Access Control-e/es (MAC-e/es) protocol includes scheduling grant processing, buffer occupancy calculation, speed request mechanism, transport format combination (TFC) recovery and elimination, and media access control - e/es (MAC-e/es) protocol data unit (PDU) construction.

A physical layer (PHY) 112 extracts the implementation of a specific Global System for Mobile Communications (UMTS) layer 1 from the Global System for Mobile Communications (UMTS) Access Layer (AS) stack so that the stack can be simply converted into an alternative Global Mobile Communications System (UMTS) Layer 1.

Traditional protocol stacking is implemented on standard processors and standard real-time operating systems as all software implementations. As wireless communication standards evolve to higher data speeds, the need to place them on the protocol stacking software increases. With the emergence of high data speed services such as High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), and Mobile Multicast Service (MBMS), protocol stacking in software on standard processors Implementation, will require a large amount of computer power. The power requirements of such standard processors have become an excessively expensive expense for battery power devices and cannot be implemented. Accordingly, there is a need to find an alternative way of implementing the stack of agreements.

The present invention is related to a protocol engine (PE) for data processing in a wireless transmit/receive unit (WTRU) protocol stack. The contract engine performs decision making and control operations. The data processing and reformatting actions performed by the traditional protocol stack are removed from the protocol stack and executed by the contract engine (PE). The protocol stack publishes control characters for processing data, and the protocol engine (PE) performs data processing based on the control characters. Preferably, the wireless transmit/receive unit (WTRU) includes a shared memory and a second memory. The shared memory is used as a data block placement saver to transfer data among processing entities. For the transfer process, the agreement engine (PE) retrieves the source material from the second memory, and moves the data to the shared memory according to the control character while processing the data. For the receiving process, the agreement engine (PE) retrieves the received data from the shared memory and moves the data to the second memory while processing the data. Alternatively, two separate processors can be used, one for the transfer process and the other for the receive process.

When referring to the term "wireless transmit/receive unit (WTRU)", it includes but is not limited to a user equipment (UE), mobile station, laptop portable computer, personal data assistant (PDA), a fixed type. Or mobile subscriber unit, pager, base station, Node B, location controller, access point, or any other form of device that can operate in a wireless environment.

Features of the invention may be integrated into an integrated circuit (IC) or in a circuit comprising a plurality of interconnected components.

In accordance with the present invention, a protocol engine (PE) is provided among the protocol stacks of a wireless transmit/receive unit (WTRU). Traditional protocol stacking operations can be divided into two categories: 1) decision and control operations, and 2) data movement and reformatting operations. Decision and control operations are related to the maintenance, control, and configuration of the radio link. These operations are generally complex decision making processes and require design and implementation flexibility. However, decision and control operations do not use the significant processing power of a standard processor. Data movement and reformatting operations are related to moving data between protocol stacks and for data reformatting during processing. While data movement and reformatting operations are highly straightforward and associated with very few decision points, these operations require significant processing power and increase the required processing power as data speed increases. The protocol engine (PE) handles the data movement and reformatting operations, while those data movement and reformatting operations are removed from the traditional protocol stack.

The protocol engine (PE) is implemented by a simple (low complexity, low power consumption) programmable processor that interprets the received data packet header on the receiving side and is generated on the transmitting side. The data packet header. The protocol engine (PE) is enhanced by means of instructions that optimize the bit field extraction and insertion from a received stream or generated bit, as will be explained in more detail later. The data stream is preferably maintained in a shared memory. The protocol engine (PE) is a function of the control data path, which is published in the co-pending U.S. Patent Application No. 10/878,729, which is incorporated herein by reference.

Thereafter, the Global System for Mobile Communications (UMTS) Access Layer (AS) will be used as an example. However, the invention is also applicable to any other protocol stack, including an access layer (AS) in the network side, a non-access stratum (NAS) in the network side of the WTRU, and others. Any wireless communication standard, including but not limited to, for Global System for Mobile Communications (GSM), Integrated Packet Radio Service Technology, Enhanced Global System for Mobile Communications (GSM) Data Rate Evolution (EDGE), Code Division Multiple Access 2000 (CDMA) 2000) and Institute of Electrical and Electronics Engineers Standard 802.xx (EEE 802.xx) and so on.

2 is a block diagram of the overall system architecture of a wireless transmit/receive unit (WTRU) 200, including a protocol engine (PE) 210, in accordance with the present invention. The wireless transmit/receive unit (WTRU) 200 preferably includes a share memory 220 to reduce the number of memories. A plurality of physical layer entities and processors access the shared memory 220 through a shared memory arbiter (SMA) 221 as a data block placement saver for data transfer among the processing entities. By utilizing a single shared memory 220, the wafer size of a special purpose ultra large integrated circuit (ASIC) can be reduced. A very fast memory such as static random access memory (SRAM) is generally used as the shared memory 220.

The WTRU 200 also includes a second memory 222 that is processed by the processing entity (such as Media Access Control - d (MAC-d) 232, Media Access Control - hs (MAC-hs). 234, media access control - e (MAC-e) 236, radio link control (RLC) 238 or radio access bearer management (RABM) / packet data aggregation protocol (PDCP) 240) used to store a large number data of. The second memory 222 can also be used to prepare for reordering of processed data and other buffer storage.

The protocol engine (PE) 210, which may also be referred to as a data mover, is configured to move data between the shared memory 220 and the second memory 222 and reformat the data while moving the data. The information in the stack of the agreement is usually transmitted in the form of a data packet (in other words, a Service Data Unit (SDU) or a Protocol Data Unit (PDU)). The Service Data Unit (SDU) and Protocol Data Unit (PDU) contain a header, body and an optional fill. This header contains all the information needed about the format of the packet. The blanking is a selection field that does not contain data values, but rather makes the packet length a certain length.

In order to transmit a data packet, the protocol stack (eg, media access control-d (MAC-d) 232, media access control-hs (MAC-hs) 234, media access control-e (MAC-e) 236 , Radio Link Control (RLC) 238, Radio Resource Control (RRC) 239 or Radio Access Bearer Management (RABM) / Packet Data Aggregation Protocol (PDCP) 240) transmitting control characters describing the requirements for data packet construction to The agreement engine (PE) 210. The control character contains information that the protocol engine (PE) 210 determines (directly or through the indicator) to use the source location in the second memory 222. The protocol engine (PE) 210 retrieves source data from the second memory 222 based on the control character and generates a protocol data unit (PDU) containing a header, a body, and a white fill (if needed). The protocol engine (PE) 210 then places the protocol data unit (PDU) in the shared memory 220 based on the control character. The protocol data unit (PDU) is then processed by a transport frame hardware 246 and a transport wafer speed hardware 248 for transmission. Selecting the protocol engine (PE) 210 can construct the particle to fill the packet with a particular data stream, which is included directly or indirectly (through the indicator) in the control character. The selective fill can be a watermark information for security considerations.

In order to receive a data packet, the received data is processed by the receiving wafer speed hardware 242 and the receiving frame hardware 244. The processing data (in other words, the receiving packet) is placed in the sharing memory 220. The protocol engine (PE) 210 receives a control character from the protocol stack and retrieves the packet from the shared memory 220. The contract engine (PE) 210 takes a header from the packet and interprets the header. The protocol engine (PE) 210 then performs the partitioning of the packet and generates and places a service data unit (SDU) in the location of the second memory 222 based on control characters from the protocol stack. With each control character, the complete information or part of the information of the header is passed to the protocol stack. The fill is discarded. If you select other information (such as watermark information) in the fill, you can retrieve the complete or partial information of the fill and place it in the memory location specified by the control character.

Figures 3 and 4 show the implementation of the agreement engine 210 in the downlink and uplink links, respectively, in accordance with the present invention. As stated above, the protocol stack 310 performs control operations, and the contract engine 210 performs data processing and reformatting processing. The control operations performed by the protocol stack 310 include, but are not limited to, Radio Access Bearer Management (RABM) Radio Access Bearer (RAB) setup and maintenance (in other words, Radio Access Bearer (RAB) removal and re-routing) Established), Packet Data Aggregation Protocol (PDCP) Service Radio Network Subsystem (SRNS) relocation, Radio Link Control (RLC) delivery protocol, including subsequent delivery (Radio Link Control (RLC) Acknowledgement Mode (AM) and non-confirmation) Mode (UM) and Radio Link Control (RLC) Protocol Data Unit (PDU) Recovery Protocol (Radio Link Control (RLC) Acknowledgement Mode (AM)), Media Access Control (MAC) Transport Format (TF) Selection ( Media Access Control-d (MAC-d), Media Access Control-c (MAC-c), Media Access Control-e/es (MAC-e/es), and Media Access Control-hs (MAC) -hs) Reorder processing.

The data processing and reformatting operations performed by the contract engine 210 include, but are not limited to, Packet Data Aggregation Protocol (PDCP) Internet Protocol (IP) header compression and decompression, Radio Link Control (RLC) services. Data Unit (SDU) / Protocol Data Unit (PDU) Segmentation and Concatenation, Radio Link Control (RLC) Header Insertion, Media Access Control - d (MAC-d), Media Access Control - c (MAC- c), media access control - e / es (MAC-e / es) header insertion, radio link control (RLC) header capture and interpretation, and media access control - d (MAC-d), media Access control -c (MAC-c), media access control - e / es (MAC-e / es) header capture, write and processing.

As shown in Figures 3 and 4, the contract engine 210 performs data plane operations while controlling characters (such as Internet Protocol (IP) header compression/decompression, radio based on the stack 310 from the protocol. Link Control (RLC) Service Data Unit (SDU) / Protocol Data Unit (PDU) Segmentation / Concatenation, Media Access Control (MAC) Header Insertion / Capture, and Media Access Control - hs (MAC-hs The sequence is maintained, etc.), and the data is moved to or removed from the shared memory 220. These operations will be described in detail with reference to Figures 5 to 10B.

5 is a block diagram of a Global System for Mobile Communications (UMTS) Access Stratum (AS) protocol stack 500, including a protocol engine (PE) 210, in accordance with the present invention. The Global System for Mobile Communications (UMTS) Access Stratum (AS) protocol stack 500 includes a Radio Resource Control (RRC) layer 510, a Radio Access Bearer Management (RABM)/Packet Data Aggregation Protocol (PDCP) layer 512, and a A Radio Link Control (RLC) layer 514, a Media Access Control (MAC) layer 516, and a Protocol Engine (PE) 210. The medium access control (MAC) layer 516 includes media access control (MAC-c) 522, media access control-d (MAC-d) 524, media access control-hs (MAC-hs) 526, and media storage. Take control -e/es(MAC-e/es) 528. Figure 5 shows an example of a High Speed Up Packet Access (HSUPA) operation using the Protocol Engine (PE) 210. All High Speed Uplink Packet Access (HSUPA) control functions are in the Global System for Mobile Communications (UMTS) Access Layer (AS) protocol stack 500 (in other words, the Radio Resource Control (RRC) layer 510, Radio Access Bearer Management) (RABM)/Packet Data Aggregation Protocol (PDCP) layer 512, Radio Link Control (RLC) layer 514, and the Medium Access Control (MAC) layer 516), while data processing is performed by the Protocol Engine (PE) 210 Executed.

The Radio Resource Control (RRC) 510 configures the Radio Link Control (RLC) layer 514, the Medium Access Control (MAC) layer 516, and the physical layer 518 by transmitting configuration, reconfiguration, and reset signals. For High Speed Uplink Packet Access (HSUPA), the Radio Resource Control (RRC) 510 handles High Speed Up Packet Packet Access (HSUPA) capabilities reported from WTRUs, configuring Media Access Control -d (MAC) -d) Traffic over Enhanced Dedicated Channels (E-DCH), Control High Speed Uplink Packet Access (HSUPA) Start and Revocation, and Configure Physical Channel and Media Access Control for High Speed Uplink Packet Access (HSUPA) -e /es(MAC-e/es)528.

The Media Access Control-e/es(MAC-e/es) 528 performs High Speed Uplink Packet Access (HSUPA) scheduling and speed calculation, Enhanced Dedicated Channel (E-DCH) Transport Format Combination (E-TFC) restrictions and Selection, media access control -d (MAC-d) traffic multiplexing, etc., and transmitting control parameters to the protocol engine (PE) 210. The Radio Link Control (RLC) 514 also transmits control parameters to the Protocol Engine (PE) 210 for connection delivery and retransmission control.

After receiving the control parameter from the media access control-e/es (MAC-e/es) 528 and the radio link control (RLC) 514, the protocol engine (PE) 210 immediately processes the control from the radio link. (RLC) 514 receives dedicated control channel (DCCH) and dedicated traffic channel (DTCH) data. The process includes a Media Access Control (MAC) service data unit from service data units (SDUs) received from the Radio Link Control (RLC) 514 through the Dedicated Control Channel (DCCH) and the Dedicated Traffic Channel (DTCH). (SDUs) Radio Link Control (RLC) Protocol Data Unit (PDU) construction (in other words, the Service Data Unit (SDU) becomes a segment of the Protocol Data Unit (PDU) and the Radio Link Control (RLC) header insertion), And constructing media access control-e/es (MAC-e/es) protocol data units (PDUs) according to control parameters received from the media access control-e/es (MAC-e/es) 528 (in other words, Media Access Control - e/es (MAC-e/es) header insertion). The contract engine (PE) 210 also performs scheduled work for a protocol data unit (PDU) specific timer. The protocol engine (PE) 210 generates the media access control-e/es (MAC-e/es) protocol data units (PDUs) and associates the media access control-e/es (MAC-e/es) protocol Data units (PDUs) are moved to the shared memory 220 for processing by the physical layer 518.

Figure 6 shows the processing for protocol data unit (PDU) decomposition in the downlink processing in the protocol engine (PE) 210 in accordance with the present invention. In the downlink processing, the protocol engine (PE) 210 performs two operations: a protocol data unit (PDU) decomposition and a service data unit (SDU) generation. The received media access control-hs (MAC-hs) protocol data units (PDUs) 612 (in other words, transport blocks) are delivered from the physical layer through the transport channel and placed in the shared memory 220. The High Speed Downlink Packet Access (HSDPA) channel data is delivered every 2 microseconds, while the dedicated channel (DCH) data is delivered every 10 microseconds, 20 microseconds, or 40 microseconds. The data stored in the shared memory 220 must be removed as quickly as possible to limit the size of the shared memory 220.

The protocol engine (PE) 210 retrieves the media access control-hs (MAC-hs) protocol data unit (PDUs) 612 from the shared memory 220 and moves it to the second memory 222 while Media Access Control-hs (MAC-hs) Protocol Data Units (PDUs) 612 are decomposed into Complex Media Access Control (MAC) Service Data Units (SDUs) 614. The protocol stack interprets the Media Access Control-hs (MAC-hs) header of each Media Access Control (MAC) Service Profile (SDU) 614 and sets the Protocol Engine (PE) 210. The protocol engine (PE) 210 can perform encryption while moving the media access control-hs (MAC-hs) protocol data units (PDUs) 612. After decomposing according to the control character, the protocol engine (PE) 210 places the decomposed medium access control (MAC) service data unit (SDUs) 614 at the location of the second memory 222 specified by the control character. Among them. The Media Access Control (MAC) Service Data Units (SDUs) 614 may not have reached the appropriate sequence yet. The contract engine (PE) 210 performs reordering of the media access control (MAC) service data units (SDUs) 614 when sufficient continuous medium access control (MAC) service data units (SDUs) 614 have arrived. And serially connecting the media access control (MAC) service data unit (SDUs) 614 to a service data unit (SDU) 616, and placing the generated service data unit (SDU) 616 according to the control character. The position of the second memory 222.

Figure 7 shows the processing for the protocol data unit (PDU) generation in the uplink processing in the protocol engine (PE) 210 in accordance with the present invention. The protocol stack establishes a media access control (MAC) header 718 and a radio link control (RLC) header 720 and transmits a control character to the protocol engine (PE) 210, as in the third and fourth Shown in the figure. The control character contains information required to generate a Media Access Control (MAC) Protocol Data Unit (PDU) 730, which includes an indicator of the Service Data Unit (SDU) material 710 in the second memory 222 (in other words , a header 712, service data unit (SDUs) 714, a state 716). The protocol engine (PE) 210 collects the service data unit (SDU) material 710 and utilizes the combined service data unit (SDU) data 710, the media access control (MAC) header 718, and the radio link control (RLC). The header 720 and padding 722 (if needed) generate a Media Access Control (MAC) Protocol Data Unit (PDU) 730. The protocol engine (PE) 210 then places the generated media access control (MAC) protocol data unit (PDU) 730 in the shared memory 220 based on the control character. The protocol engine (PE) 210 can also perform encryption while generating the media access control (MAC) protocol data unit (PDU) 730, if desired.

Figure 8 shows in more detail the processing for protocol data unit (PDU) decomposition in the downlink processing in the protocol engine (PE) in accordance with the present invention. The topmost column represents the shared memory 220 with 32-bit characters. The second column represents a Media Access Control-hs (MAC-hs) Protocol Data Unit (PDU) 810 (in other words, a transport block). The Media Access Control-hs (MAC-hs) Protocol Data Unit (PDU) 810 is placed in the shared memory 220 after processing at the physical layer. The media access control-hs (MAC-hs) protocol data unit (PDU) 810 includes a media access control-hs (MAC-hs) header 812 and a plurality of media access control-hs (MAC-hs) service profiles. Units (SDUs) 814. Up to 70 Media Access Control-hs (MAC-hs) Service Data Units (SDUs) 814 may be included in a Single Media Access Control-hs (MAC-hs) Protocol Data Unit (PDU) 810. Each Media Access Control-hs (MAC-hs) Service Profile (SDU) 814 is a Media Access Control (MAC-d) Protocol Data Unit (PDU) containing a Media Access Control (MAC) Header 822 (optional) and a Media Access Control (MAC) Service Profile Unit (SDU) 824. The Media Access Control (MAC) Service Profile (SDU) 824 includes a Radio Link Control (RLC) header 826 and a data payload 828. The Media Access Control (MAC) header 822 and the Radio Link Control (RLC) header 826 contain the bit fields that need to be retrieved. The protocol engine (PE) 210 retrieves the media access control-hs (MAC-hs) header 812, the media access control (MAC) header 822, and the radio link control (RLC) label from the shared memory 220. Header 826 moves the data payload 828 from the shared memory 220 to the second memory 222 while decomposing it into complex Media Access Control (MAC) Service Data Units (SDUs) 814. A decryption action can be performed if needed.

The data in the shared memory 220 is indicated by a stream indicator. The indicator will automatically update after a data capture, move or insert operation. For example, prior to moving the data load 828, the serial indicator indicates location A in the shared memory 220. After the protocol engine (PE) 210 moves the data payload 828, the serial indicator will indicate the location B in the shared memory 220.

It should be noted that the downlink link processing of the High Speed Downlink Packet Access (HSDPA) channel data described in FIG. 8 is merely exemplary. However, the present invention can also be applied to both downlink links and uplink links, and can also be applied to other forms of channel data such as dedicated channel data, high speed downlink packet access (HSDPA) channel data, and the like.

Figures 9A and 9B show the operation of the stream capture (n) function in accordance with the present invention. After defining the "input stream indicator", the protocol engine (PE) extracts 1 to 32 bits from an input stream and updates a stream indicator. Fig. 9A shows a case where 9 bits are extracted from a single character, and Fig. 9B shows a case where 5 bits are extracted from two characters. The stream capture (n) function returns 1 to 32 bits from the data stream in the shared memory.

Figures 10A and 10B show the operation of the stream insertion (d, s) function in accordance with the present invention. After defining the "output stream indicator", the protocol engine (PE) inserts 1 to 32 bits into an output stream and updates the stream indicator. Fig. 10A shows the case where 9 bits are inserted into a single character, and Fig. 10B shows the case where 5 bits are inserted into two characters. The stream insertion (d, s) function inserts 1 to 32 bits into the data stream of the shared memory. The data stream is indexed by the indicator and updated after insertion.

Figure 11 is a flow diagram of a process 1100 for receiving processing in accordance with the present invention. This process 1100 is also described with reference to Figures 6, 8, 9a and 9b. The protocol engine (PE) 210 receives a signal from a source indicating a received data block (e.g., media access control-hs (MAC-hs) protocol data units (PDUs) 612, 810, which may be used for subsequent disassembly. Action (step 1102). The signal is included in the data block address in the shared memory 220. The protocol engine (PE) 210 performs a stream capture indication to access the bit field in the source stream of the shared memory 220 (step 1104). Each stream capture indicates that the number of bit requests from the source stream is returned to a particular record. After the field is retrieved as shown in Figures 9A and 9B, the stream indicator is updated to index the bit. The protocol engine (PE) 210 interprets the media access control-hs (MAC-hs) header 812 bit field from the source stream (step 1106). After the media access control-hs (MAC-hs) header 812 is interpreted, subsequent information about the Media Access Control-hs (MAC-hs) Service Data Units (SDUs) 814 is collected.

After the media access control-hs (MAC-hs) header 812 has been read, the source stream indicator should refer to the first bit of the first media access control (MAC) header. The protocol engine (PE) 210 continues to utilize the stream capture indication to retrieve and interpret the media access control (MAC) header 822 and the radio link control (RLC) header 826. When the Radio Link Control (RLC) header 826 has been interpreted, the source stream indicator should refer to the first bit of the first Media Access Control (MAC) Service Data Unit (SDU) 824 data payload 828. .

The agreement engine (PE) 210 is now ready to process the data load 828. The protocol engine (PE) 210 begins pushing the data 828 through a data path (in other words, generating media access control (MAC) service data units (SDUs) while moving the data payload 828 to the second memory 222) (Step 1108). If configured, the profile 828 can be pushed through an encryption logic. The formed data is merged into a data writing buffer and written to the appropriate destination address space in the second memory.

The protocol engine (PE) 210 receives a signal from a source indicating that sufficient media access control (MAC) service data units (SDUs) 614, 824 have been received, and establishes a service data unit (SDU) 616 (step 1110). The protocol engine (PE) 210 accesses the control characters established by the protocol stack (in other words, layer 2/3), which acknowledges the block addresses that have been merged. Each address contains a start bit address and length in the second memory 222. The control character is also included in the destination address in the second memory 222. The agreement engine (PE) 210 retrieves the information specified by the source address and merges it into the appropriate data compilation buffer (step 1112). The merged data is then written to the appropriate destination address space of the second memory 222. The contract engine (PE) 210 then joins the data payload until all sources have been processed and a complete service data unit (SDU) 616 is established.

Figure 12 is a flow diagram of a process 1200 for transfer processing in accordance with the present invention. This process 1200 is also described with reference to Figures 7, 8, 10a and 10b. The protocol engine (PE) 210 receives a signal from a source indicating that the material is ready to be formatted as a set of transport blocks (in other words, a medium access control (MAC) protocol data unit (PDU)) (step 1202). Using the information from the protocol stack (layer 2/3), the protocol engine (PE) 210 generates a header field (in other words, a media access control (MAC) header 718 and a radio link control (RLC) header 720). For data translation (step 1204). The protocol engine (PE) 210 performs a stream insertion indication for the domain located in each header. The stream insertion indicates the presentation material and the bit length. The Contract Engine (PE) 210 is therefore a programmable processor that utilizes its own resources (eg, records, memory, etc.) that can keep track of the number of blocks and the like. The contract engine (PE) 210 performs appropriate branch and merge operations to place a particular number of bits in the output bit stream. The protocol engine (PE) 210 continues to utilize the stream insertion indication until a complete header is established. When the headers 712, 720 are completed, the output stream indicator should be referred to as the next available bit position, as shown in Figures 10A and 10B.

For the data load (in other words, the service data unit (SDU) data 710), using the information from the layer 2/3, the agreement engine (PE) 210 obtains data from the source stream of the second memory 222, And if there is a configuration, push it through the encryption logic (step 1206). The contract engine (PE) 210 merges the formed data into the data authoring buffer and writes it to the appropriate destination address in the shared memory 220 (step 1208). The protocol engine (PE) 210 continues to add header information (through the stream insertion indication) and adds the data payload until a complete packet 730 is established.

Although the features and elements of the present invention have been described in a particular combination in a particular embodiment, each feature or element may be used alone or in combination with other features and elements of other preferred embodiments. Components, together or individually, are combined differently.

100. . . Global mobile communication system access layer

200. . . Wireless transmission/reception unit

500. . . Global System of Mobile Communications Access Layer Agreement Stack

616. . . Service data unit

710. . . Service data unit data

722. . . Fill in white

Figure 1 shows a conventional wireless transmit/receive unit (WTRU) access layer (AS) protocol stack.

2 is a block diagram of the overall system architecture of a wireless transmit/receive unit (WTRU) in accordance with the present invention, including a protocol engine.

Figure 3 shows the implementation of the contract engine in the downlink link in accordance with the present invention.

Figure 4 shows the implementation of the contract engine in the uplink link in accordance with the present invention.

Figure 5 is a block diagram of a Global System for Mobile Communications (UMTS) Access Stratum (AS) protocol stack, including a contracting engine, in accordance with the present invention.

Figure 6 shows the processing for protocol data unit (PDU) decomposition in the downlink processing in the protocol engine in accordance with the present invention.

Figure 7 shows the processing for the protocol data unit (PDU) generation in the uplink processing in the protocol engine in accordance with the present invention.

Figure 8 shows in more detail the processing for protocol data unit (PDU) decomposition in the downlink processing in the protocol engine in accordance with the present invention.

Figures 9A and 9B show the operation of the stream acquisition function in accordance with the present invention.

Figures 10A and 10B show the operation of the stream insertion function in accordance with the present invention.

Figure 11 is a flow chart showing the process for receiving processing in accordance with the present invention.

Figure 12 is a flow chart showing the processing for the transfer process in accordance with the present invention.

Claims (22)

A wireless transmit/receive unit (WTRU) comprising: a first memory; a second memory; a protocol stack processor including a media access control (MAC) layer and a radio link control (RLC) layer And configured to issue a control character to process the data, wherein the control character includes a method for reformatting the material when the material is transferred between the first memory and the second memory in the WTRU And a protocol engine configured to reformat the data when the data is transferred between the first memory and the second memory in accordance with an instruction including the control character, wherein the protocol engine is based on the Control characters generate MAC Protocol Data Units (PDUs) from RLC Service Data Units (SDUs) for transmission processing and generate RLC SDUs from the MAC PDUs for reception processing based on the control characters. The wireless transmitting/receiving unit of claim 1, wherein: the control character includes an instruction to construct a data packet, and the protocol engine is further configured to: fetch source data from the second memory; And using the source material to generate the data packet according to an instruction containing the control character. The wireless transmitting/receiving unit of claim 2, wherein: the control character comprises a location for storing the generated data packet in the first memory, and the protocol engine is further configured to store The information generated is enclosed in the instructions The location in the first memory in the instruction. The wireless transmitting/receiving unit of claim 3, further comprising a transfer processing circuit configured to process the data packet for transmission. The wireless transmitting/receiving unit of claim 1, further comprising a receiving processing circuit configured to receive, process and store a data packet in the first memory. The wireless transmitting/receiving unit of claim 5, wherein the agreement engine is further configured to fetch the received data packet from the first memory, and receive the received data according to the instruction included in the control character. Data packets capture information. The wireless transmitting/receiving unit of claim 6, wherein the information extracted from the received data packet is at least one of header information and specific information included in a blank area of the data packet. . The wireless transmitting/receiving unit of claim 6, wherein the agreement engine is further configured to generate and store an SDU in the second memory using the received data packet according to the instruction included in the control character. a position. The WTRU of claim 1, wherein the control character designation parameter is used for radio access bearer (RAB) setup and maintenance, Serving Radio Network Subsystem (SRNS) relocation, RLC Delivery Protocol, MAC Transport Format Selection, MAC Reordering, High Speed Up Packet Access (HSUPA) Scheduling and Speed Calculation, Enhanced Dedicated Channel (E-DCH) Transport Format Combination (E-TFC) Restriction and Selection and Dedicated At least one of channel MAC (MAC-d) traffic multiplexes. The wireless transmitting/receiving unit of claim 1, wherein the agreement engine is further configured to perform a Packet Data Aggregation Protocol (PDCP) Internet when transmitting data between the first and the second memory Network Protocol (IP) header compression and decompression, RLC SDU PDU segmentation and concatenation, RLC header insertion, MAC header insertion, RLC header capture and interpretation, and MAC headers Capture and add at least one of them. An agreement engine for processing data according to a control character issued by a protocol stack in a wireless transmit/receive unit (WTRU), the protocol engine comprising: at least one input configuration to receive at least one control character, the at least a control character element for transmitting data between a first memory and a second memory, and for reformatting when the material is transferred between the first memory and the second memory An instruction of the material; and a processor configured to reformat the data when the data is transferred between the first memory and the second memory in accordance with an instruction included in the control character, wherein the protocol An engine generates media access control (MAC) protocol data units (PDUs) from radio link control (RLC) service data units (SDUs) for transmission processing based on the control character and generates from the MAC PDUs based on the control character RLC SDUs are used for receiving processing. A method for processing data using a protocol engine in a wireless transmit/receive unit (WTRU) including a protocol engine, a protocol stack, a first memory and a second memory, the method comprising: the protocol engine Receiving at least one control character, the at least one control character comprising: for transferring data between the first memory and the second memory and when the data is between the first memory and the second memory An instruction to reformat the data when transmitted; and the protocol engine reformats the data when the data is transferred between the first memory and the second memory based on an instruction included in the control character And wherein the protocol engine generates media access control (MAC) protocol data units (PDUs) from the radio link control (RLC) service data unit (SDUs) for transmission processing based on the control character and based on the control character The MAC PDUs generate RLC SDUs for receiving processing. The method of claim 12, wherein: the control character includes an instruction to construct a data packet, and The method further includes: the data engine fetching the source material from the second memory; and the agreement engine uses the source material to generate the data packet according to an instruction included in the control character. The method of claim 13, wherein: the control character includes an instruction to store the generated data packet at a location of the first memory, and the method further includes the agreement engine storage The data is encapsulated at the location of the first memory indicated in the instruction. The method of claim 14, further comprising the wireless transmitting and receiving unit transmitting the data packet. The method of claim 12, further comprising receiving, processing, and storing a data packet in the first memory by the wireless transmission receiving unit. The method of claim 16, further comprising the agreement engine fetching the received data packet from the first memory, and extracting information from the received data packet according to the instruction included in the control character. The method of claim 17, wherein the information extracted from the received data packet is at least one of header information and specific information included in a blank area of the data packet. The method of claim 17, further comprising the agreement engine generating and storing an SDU in a location of the second memory using the received data packet according to the instruction included in the control character. The method of claim 12, wherein the control character designation parameter is used for radio access bearer (RAB) setup and maintenance, Serving Radio Network Subsystem (SRNS) relocation, RLC delivery protocol, MAC Transport format selection, MAC reordering, high speed uplink packet access (HSUPA) scheduling and speed calculation, enhanced dedicated channel (E-DCH) transport format combination (E-TFC) restriction and selection, and dedicated channel MAC (MAC) -d) Traffic to multiplex One of them is less. The method of claim 12, further comprising the agreement engine, performing a Packet Data Aggregation Protocol (PDCP) Internet Protocol (IP) when transferring data between the first and the second memory At least one of header compression and decompression, RLC SDU PDU segmentation and concatenation, RLC header insertion, MAC header insertion, RLC header capture and interpretation, and MAC header capture and addition. An integrated circuit (IC) comprising: a protocol stacking processor comprising a media access control (MAC) layer and a radio link control (RLC) layer, and configured to issue a control character to process data, wherein The control character includes instructions for reformatting the data when the data is transferred between a first memory and a second memory in a wireless transmitting/receiving unit; and a protocol engine configured to The instruction included in the control character reformats the data when the material is transferred between the first memory and the second memory, wherein the protocol engine controls from the radio link based on the control character ( The RLC) Service Data Units (SDUs) generate MAC Protocol Data Units (PDUs) for transmission processing and generate RLC SDUs from the MAC PDUs for reception processing based on the control characters.