TW200522578A - Outer coding methods for broadcast/multicast content and related apparatus - Google Patents

Abstract

Transmission techniques are provided that improve service continuity and reduce interruptions in delivery of content that can be caused by transitions that occur when the User Equipment (UE) moves from one cell to the other, or when the delivery of content changes from a Point-to-Point (PTP) connection to a Point-to-Multipoint (PTM) connection in the same serving cell, and vice-versa. Such transmission techniques enable seamless delivery of content across cell borders and/or between different transmission schemes such as Point-to-Multipoint (PTM) and Point-to-Point (PTP). Mechanisms for adjusting different streams and for recovering content from each data block during such transitions are also provided so that data is not lost during a transition. In addition, mechanisms for realigning data during decoding at a receiving terminal are also provided.

Description

200522578 IX. Description of the invention: [Technical field to which the invention belongs] The present invention relates generally to communication systems, and more specifically, to the transmission of broadcast and multicast content. [Prior art] Wireless communication systems have traditionally been used to carry voice traffic and non-voice traffic with low data rates. Today's wireless communication systems are designed to carry high-speed data rate (HDR) multimedia traffic, such as video, data, and other types of streams. Multimedia broadcast and multicast service (Mbms) channels can be used to stream audio, audio, and video sources, such as radio, television, and other types of audio or video content. Streaming data sources can tolerate delays and specific loss or bit error numbers because these data sources are sometimes intermittent and are often compressed. In this regard, the transmission data rate to the radio access network (RAN) may vary significantly. Because application buffers are usually limited, MBMS transmission mechanisms are required to support variable data source data rates. [Summary of the Invention] The base station usually provides such multimedia traffic services to user stations by transmitting a signal k number which is often organized into a plurality of packets. A packet may be a group of bytes that can be configured into a specific format, which contains data (payload) and controls TL elements. For example, the control elements may include a preamble and a “buzz degree” setting, and the quality metric may include a cyclic redundancy check code (CRC), (one or more) parity bits, and other types of metric. The packets are usually formatted into a message according to a communication channel structure. The 95692.doc 200522578 information will be transmitted between the originating terminal and the destination terminal, and may be affected by the characteristics of the communication channel, such as signal-to-noise ratio, signal-to-signal crossover, and other similar characteristics. These characteristics may have different effects on modulated signals in different channels. In other considerations, a modulated information signal on a wireless communication channel upload wheel must choose the correct method to protect the information in the modulated signal. These methods include, for example, the 'encoding method, the symbol repetition method, the interleaving method, and other methods well known to those skilled in the art. However, these methods will increase the additional data. Therefore, the design project must make a compromise between the reliability of information transmission and the amount of additional data. The operator usually selects a point-to-point (ρτρ) connection or a point-to-multipoint (PTM) connection on a cell basis depending on the number of user stations or users interested in receiving the MBMS content. Point-to-point (PTP) transmissions use dedicated channels to send the service to remote users in the coverage area. "Exclusive" channels carry information to / from a single user station. In point-to-point (PTP) transmission, a separate channel can be used to transmit to each mobile station. For example, dedicated user traffic for one of the user services may be sent in a forward link or a downlink direction through a logical channel called a dedicated traffic channel (DTCH). For example, point-to-point (PTP) communication services are usually the most effective if there are not enough users in the coverage area to require a specific multimedia broadcast and multicast service (MBMS). In these cases, point-to-point (PTP) transmission can be used, where the base station transmits the service only to the specific user who requested the service. For example, in a WCDMA system, it is more effective to use a dedicated channel or point-to-point (ρτρ) transmission before exceeding a preset number of mobile stations 95692.doc 200522578. "Broadcast communication" or "point-to-multipoint (PTM) communication" is to communicate with a plurality of mobile stations on a common communication channel. _ "Common" channel will contain information from / from multiple subscriber stations and can be used by several terminals simultaneously. In point-to-multipoint (PTM) communication services, if the number of users requiring the service in the coverage area of the base station exceeds a preset critical number, the cellular base station can broadcast multimedia traffic on the common channel service. In the CDMA 2000 system, the PtP transmission is usually replaced by broadcast or point-to-multipoint (ρ top) transmission, because the PtM radio bearer is almost the same as the ⑽ radio bearer. A common channel transmission from a particular base station need not be synchronized with a common channel transmission from another base station. In a typical broadcast system, first and middle school, there will be more than one central station to serve a user broadcast network. The (etc.) central station can transmit information to all subscriber stations or to a specific group of subscriber stations. Each user station participating in the broadcast service will monitor the same number as the link. Point-to-multipoint (ptm) transmissions may be on downlink or forward common channels. This co-broadcast forward link signal is usually broadcast on a unidirectional channel (such as a common traffic channel (CTCH) in the forward link or "downlink" direction). Because this channel is unidirectional, the subscriber station usually does not communicate with the base station, because allowing all subscriber units to communicate with the base station in the reverse direction may overload the communication system. Therefore, in the context of point-to-multipoint (PTM) communication services, when there is an error in the information received by such subscriber stations, the subscriber stations may not be able to communicate with the base station in the reverse direction. Therefore, we may need other methods of information protection. 95692.doc 200522578 In the CDMA 2000 system, soft combining is performed during the transmission. Even if + is taken; ° the status of the PTM channel can still protect the information signal, which means that the destination station cannot decode part of the packets on the channel that are being transferred. In these cases, the first solution is to retransmit these undecoded packets to the origin (base) station by the destination (user) station. Retransmission helps to ensure the transmission of the data packet-right ..., if the data is transmitted correctly, the transmitting RLC user can be informed. The subscriber station usually transmits in several scenarios. These transmissions can be categorized in different ways. For example, transmissions can be classified as "cross-over transmission" and direct transmission. Transmissions can also be classified as "intercellular" transmissions and "intracellular" transmissions. Migration between cells or transport architectures can lead to undesired service interruptions. When the user station or user equipment (UEm where one cell moves to another cell) or when the multimedia broadcast and multicast service (MBMS) content transmission in the serving cell changes from one mode to another Problems may occur. The transmission of adjacent cells may be time-shifted from each other. Moreover, additional delay may be caused during the transfer because the mobile station must determine the system information in the target cell. This decision The operation requires a certain amount of processing time at t2. The data strings transmitted by different cells (or point-to-point (PTP) / point-to-multipoint (PTM) of different transmission channel types) can offset each other. Therefore, different 'Point of mobile's point-to-multipoint (PTM) transmission' The mobile station may or may receive the same block of content twice 'or the inner valley block of the crotch may be lost, these are the quality of service 95692.doc 200522578 Undesirable conditions. Depending on the duration of the transfer and the delay or misalignment between transmissions, the transfer between cells and / or point-to-point (PTP) transmissions and point-to-multipoint (PTM) transmissions Can cause service interruption. So 'The transmission technology required by this technology will provide service continuity and reduce migration when user equipment (UE) moves from one cell to another or when the same service cell Disruption of content delivery caused by migration when content delivery changes from a point-to-point (ρτρ) connection to a point-to-multipoint (PTM) connection (and vice versa). These transmission technologies are better at multiple cell boundaries And / or different transmission architectures (such as point-to-multipoint (pTM) and point-to-point (PTP)) to provide seamless transmission. At the same time, it is hoped that different data strings can be adjusted during these migrations and from each data area The mechanism of restoring the content in the block, so that no data is lost during the transfer. In addition, it is desirable to provide a mechanism at the receiving terminal that can rearrange the data during decoding. [Embodiment] The term "refers to as a Examples, examples

As used herein, "exemplary" or description. This article is used as a "model

User Unit "," Terminal ", and" User Equipment (UE is changed and this article represents a network that can be connected to an access network (such as UTRAN)) … In the UMTS system, the components of the user's UMTS network services, the USIM of the user's subscription information.

It may be mobile or static 95692.doc 200522578, and usually contains any force. It can communicate through wireless channels or wired: Shell: 7 ", or terminal. Mobile stations can be specified in devices including, but not limited to, using optical fiber or coaxial iron wire, external or internal modems, or two or a small flash memory ^… wire or wire telephone such as "connection setting state" Acting on behalf of the state of a mobile station is establishing an active traffic channel connection with a base cr. The “traffic state” is a state where the mobile station has established an active traffic channel with the base station. The "communication channel" used in this article refers to the physical channel or logical channel according to this article. 'The term' physical channel 'as used herein refers to a channel containing user data or control information that can be communicated over the air interface. The physical channel is a "transmission medium" that provides the radio platform. Information is actually transmitted through the platform 'and the physical channel can be used to carry signaling and user data for communication in the air interface. -The physical channel is generally a combination of frequency scrambling channelization codes. Relative phase may also be included in the upward link direction. Depending on what the mobile station is trying to do, several different physical channels may be used in the uplink direction. In the UMTS system, the term physical channel may also mean different types of bandwidth assigned for different uses on the Uu interface. These physical channels will constitute the physical existence of the Uu interface between the user equipment (UE) domain and the network access domain. Physical channels can be defined using physical mappings and attributes used to transmit data in the air interface. The term "transmission channel" used in this article refers to the communication path used for data transmission between simultaneous entities 95692.doc -11-200522578. The transmission channel is related to the information transmission method. -In general, there are two types of transmission channels, a common transmission channel and a dedicated transmission channel. It can be used to transmit materials on the air interface of the physical layer and what characteristics are used for transmission (for example, 'whether to use a dedicated or common physical channel or whether to multiplex logical channels). Channel. The transport channel serves as a service access point (APS) for this physical layer. In addition, the transmission channel will describe how to transmit logical channels such as " Hai, etc., and map this information stream to the physical channel. The transport channel can be used to carry L7 and user data between the media access control (MAC) layer and the physical layer. Radio network control (rnc) will refer to the transmission channel. Information is transmitted from the MAC layer to the physical layer on any of several transmission channels that can be mapped to the physical channel. The word "logical channel" used in this article represents the transmission of a specific type of information or an information string specific to the radio interface. Logical channels are related to the information being transmitted. A logical channel can be defined by what type of information (e.g., signaling or user data) is transmitted and can be understood as different tasks that the network and the terminal should perform at different points in time. Logical channels may be mapped to transmission channels that perform actual information transmission for the mobile station domain and the access domain. Information is transmitted through logical channels that can be mapped via a transmission channel (which is mapped to a physical channel). The term "exclusive channel" as used in this article refers to a channel that is usually dedicated to or reserved for a specific user, and will carry funds to a special mobile station, user unit, or use Other devices, or from a special automation station, user unit, or user equipment to carry information. 95692.doc -12- 200522578 An exclusive channel usually carries information targeted at a given user, which contains data about the actual service and higher-level control information. A specific channel can be identified by a specific code on a specific frequency of 2. — Exclusive channels may be bi-directional to allow feedback. The term "common channel" as used herein refers to a transmission channel that carries information to / from multiple mobile stations. In Common = Road, information will be shared by all mobile stations. A shared channel can be split between all users within a cell or a group of users. As used herein, the term "point-to-point (PTP) communications" refers to communications that can be transmitted to a single mobile station on a dedicated, actual communication channel. The terms "broadcast communication" or "point-to-multipoint (PTM) communication" as used herein refer to a common communication channel and multiple mobile stations. The "reverse link or uplink link" used in this article is the term used by the mobile station to send a signal to a communication channel / link of a base station through the link in a radio access network. This channel can also be used to transmit signals from a mobile station to a mobile base station or from a mobile base station to a base station. As used herein, the term "forward link or downlink" refers to a radio access network transmitting a signal to a communication channel / link of a mobile station. As used in this paper, the "transmission time interval ㈢"-the term represents the time interval from the higher layer to the physical layer. The transmission time interval ⑽ may represent the time between the arrival of the system-transport block set (TBS), and is equivalent to the period of the TBS upload round of the physical layer on the radio interface. The materials transmitted on the second 95692.doc 200522578 transmission channel during TTI may be encoded and interlaced. A TT! Can extend multiple radio frames and may be a multiple of the minimum interleaving period. The start position of τΉ for different pass channels with single-connection multiplexed in-must be time-aligned. Multiple TTIs will have a common starting point. The media access control is transmitted in each TTI-the block set is transmitted to the body layer. Different transmission channels of the same-to-physical layer may have different transmission time interval (TTI) durations, and multiple PDUs can be sent in ττι. As used herein, the "packet" -word represents the group_group bit, which contains data or payload and control elements configured in a specific format. These control elements may include, for example, the foregoing, the product f metric, and other elements well known to those skilled in the art. For example, quality metrics include cyclic redundancy check (CRC), parity, and other types of metrics known to those skilled in the art. As used herein, the term "access network" refers to the equipment required to access the network. The access network may include multiple base stations (BS) and more than one base station controller (BSC). A collection or network. The access network can transmit data packets between multiple subscriber stations. The access network may be further connected to additional networks other than the access network, such as a company intranet or the Internet, and may be between a plurality of access terminals and these external networks Transmission of data packets. In UMTS systems, this access network may be referred to as the UMTS Terrestrial Radio Access Network (UTRAN). The term "core network" as used herein refers to a connection to the public switched telephone network (PSTN) (for circuits in the Circuit Switched (CS) domain 95692.doc -14- 200522578 switched calls) or Switching or routing functions for any of the Packet Data Network (PSDN) (for packet switching calls in the packet switching (ps) domain). The term “core network” also refers to the routing function for mobile capabilities and user location management, and the routing function for authentication services. The core network contains the network elements necessary for switching and user control. The term "base station" as used in this article refers to a "origin station" that contains hardware that can communicate with a mobile station. In the UMTS system, the term "node B" can be used instead of the term "base station". A base station may be fixed or mobile. The term "cell" as used in this article means either hardware or geographical coverage, depending on the context in which the term is used. The term "service data unit (SDU)" as used herein refers to a unit of data that can be exchanged using a protocol that is above the protocol of interest. As used herein, the term "payload data unit (PDU)" refers to a unit of data that can be exchanged using a protocol located below the protocol of interest. If the agreement of interest cannot be clearly identified, then specific mentions will be made by name. For example, the FEC-PDU is a PDU at the FEC layer. The term "soft handover" as used in this paper refers to a cell between a subscriber station and two or more segments, in which the parent and child segments belong to different cells. Reverse link communication can be received by two sectors, and forward link communication can be carried on the forward links of more than two sectors at the same time. The term "softer delivery" as used herein refers to communication between a user station and more than two segments, where each segment belongs to the same cell. The reverse link communication can be received by two sectors, and the forward link 95692.doc -15- 200522578 message can be carried on one of the forward links of two or more sectors simultaneously. The word "Division J" used in this paper indicates that it is impossible to confirm a certain information and can also be used to represent a group of bits that may be lost in decoding time. The term "transfer and transfer" can be defined as a transfer from point-to-point (PTP) transmission to point-to-multipoint (PTM) transmission, or vice versa. There are four possible transfers: transfer from point-to-point (PTP) transmission in cell A to point-to-multipoint (PTM) transmission in cell B, and transfer from point-to-multipoint (PTM) transmission in cell A Go to point-to-point (ρτρ) transmission in Asuka, transfer from point-to-point (ρτρ) transmission in cell A to point-to-multipoint (PTM) transmission in cell 4, and point-to-night point in cell A (PTM) transmission is transferred to point-to-point (ρΤρ) transmission in cell a. The term "direct transfer" can be defined as a transfer from point-to-point transmission to another point-to-point transmission and a point-to-multipoint transmission to another point-to-multipoint transmission. There are two possible direct transfers: transfer from point-to-point (ρτρ) transmission in cell A to point-to-point (PTP) transmission in cell B, and transfer from point-to-multipoint (PTM) transmission to cell 8 Point-to-multipoint (ρτM) transmission in B. The term "intercellular migration" stands for migration across cell boundaries. There are four types of cell-to-cell transfers: · Transfer from point-to-point (ρΤρ) transfer in cell A to point-to-point (PTP) transfer in cell B, transfer from point-to-multipoint (PTM) transfer in cell A To point-to-multipoint (pTM) transmission in cell B, transfer from point-to-point (PTP) transmission in cell a to point-to-multipoint (pTM) transmission in cell a, and point-to-multipoint transmission in cell A (PTM) transmission migrates to point-to-point (PTP) transmission in cell A. In general, the most common migrations are cell-to-multipoint (PTM) transmissions that move across cell boundaries to point-to-multipoint (PTM) transmissions. 95692.doc -16- 200522578 The term "intracellular migration" refers to the migration from one mode to another in a cell. There are two possible intracellular migrations: migration from point-to-point (PTP) transmission in cell A to point-to-multipoint (PTM) transmission in cell A, and point-to-multipoint (PTM) transmission in cell A Transfer to point-to-point (PTP) transmission in cell A. The term "radio bearer" refers to the services provided by layer 2 to transfer user data between user equipment (UE) and UMTS terrestrial radio access network (UTRAN). Specific embodiments of the invention will now be discussed in which the ideas discussed above can be implemented in a WCDMA or UMTS communication system. Figures 1-5C explain some of the views of a conventional UMTS or WCDMA system, in which the views of the present invention described in this specification that can be applied to this description are for illustrative and limiting purposes only. It should be understood that the idea of the present invention can also be applied to other systems that carry both voice and data, such as the GSM system and CDMA 2000 system that meet the following standards: "3rd Generation Partnership Project" (3GPP), which The kit is now in the file group containing the following document numbers: 30 D 325.21 B 30 D 325.212, 3G TS 25.213 and 3G TS 25.214 (W-CDMA standard); or "TR-45_5 cdma 2000 spread spectrum system physical layer standard" Standard (IS-2000 standard); and GSM specifications, such as TS 04.08 (Mobile Radio Interface Layer 3 Specification), TS 05.08 (Radio Subsystem Link Control), and TS 05.01 (Physical Layer on the Radio Path (General Description) ).

For example, although the description specifies that the radio access network 20 may be implemented using the Universal Terrestrial Radio Access Network (UTRAN) air interface, in a GSM / GPRS system, the radio access network 20 may be a GSM / EDGE 95692. doc 17 200522578 Radio Access Network (GERAN), even in the case of systems, may include cells of the UTRAN air interface and cells of the GSM / EDGE air interface. UMTS network topology Figure 1 is a block diagram of a communication system based on a UMTS network topology. A UMTS system includes a user equipment (UE) 10, an access network 20, and a core network 30. The UE 10 is coupled to the access network, and the access network is coupled to the core network 30. The core network 30 may be coupled to an external network. The UE 10 includes a mobile device 12 and a Universal Subscriber Identity Module (USIM) 14, which contains user subscription information. Cu interface (not shown) is an electrical interface between USIM 14 and the mobile device 12. UE 10 is usually a component that allows users to access UMTS network services. The UE 10 may be a mobile component (such as a cell phone), a fixed station, or other data terminal. For example, the mobile device may be a radio terminal used for radio communications over an air interface (Uu). The UE can access the fixed part of the system via the Uu interface. The USIM is typically an application program that resides on a "smart card" or other logic card containing a microprocessor. The smart card retains the identity of the user, can implement an authentication algorithm, and uses an encryption key to store the authentication signal and the ordering information required at the terminal. The access network 20 contains radio equipment for accessing the network. In a WCDMA system, the access network 20 is a Universal Terrestrial Radio Access Network (UTRAN) air interface. UTRAN includes at least one Radio Network Subsystem (RNS), which includes at least one base station or "Node B" 22, which is 95692. doc -18- 200522578 is coupled to at least one radio network controller (RNC) 24. The RNC will control the radio resources of the UTRAN. The RNCs 24 accessing the network 20 communicate with the core network 30 through the Iu interface. The Uu interface, Iu interface 25, Iub interface, and Iur interface allow devices from different vendors to be networked, and they are all specified in the 3GPP standard. The design method of the radio network controller (rnC) is different for each Weishang company, so it will be described below in general. The Radio Network Controller (RNC) 24 is used as the switching and control element of the UMTS Terrestrial Radio Access Network (UTRAN), and is located between the iub interface and the Iu interface 25. The RNC can serve as a service access point for all services provided by the UTRAN to the core network 30, for example, to manage connection with the user equipment. Iub interface 23 connects Node B 22 and Radio Network Controller (RNC) 24. The Iu interface will connect UTRAN to the core network. The radio network controller (RNC) will provide a switching point between the I1 carrier and the base stations. The user equipment (UE) 10 may have several radio bearers between itself and the radio network controller (RNC) 24. The radio bearer is related to the user equipment (UE) content, which is a set of defined values required by the Iub to arrange the common connection between the user equipment (UE) and the radio network controller (RNC) and Dedicated connection. The individual RNCs 24 can communicate with each other on an optional Iur interface, which allows soft handover between cells connected to different nodes 22. Therefore, the Iur interface allows inter-RNC connections. In these cases, a serving MC will maintain the Iu 25 connection to the core network 30 and implement selector and external loop power control functions. At the same time, a drift RNC will be available through more than one base station 22 95692. doc -19- 200522578 The frame exchanged on the Iur interface is transmitted to the mobile station. The RNC that controls a node B22 can be called the control RNc of node B, and controls the load and congestion of its own cells. At the same time, it also performs admission control and code assignment for new radio links to be established in those cells. The RNC and the base station (node B) can be connected through the Iub interface 23 and communicate with each other on the " surface. These RNCs will control the use of these non-radio and power resources by each base station 22 that is coupled to a special%, which is obstructive. Each base station 22 controls more than one cell and provides a radio link to the mobile station. The base station can implement interface processing, such as channel coding and interleaving processing, rate adaptation and expansion processing. The base station will also perform basic radio resource management operations, such as inter-loop power control. The base station 22 will convert the data streams between ⑽ and Xian interface 23 and 26. The base station 22 will also participate in radio resource management. The air interface Uu 26 will couple each base station 22 to the mobile station 10. Base stations such as 1¾ may be responsible for the radio transmission operation of more than one cell to the mobile station 10, and responsible for the transmission from the mobile station 10 to more than one cell. Radio reception operation. The core network 30 includes all switching and routing functions to perform the following tasks: (1) if a circuit switching call exists, to connect to the PSTN42, or if a packet switching call exists, to connect to the packet data network (PDN); (2) implementation of mobile capability and user location management; and (3) implementation of authentication services. The core network 30 may include a location registrar (HlR) 32, a mobile switching service center / visitor location registrar (MSC / VLR) 34, a gateway subscription switching center (GMSC) 36, and a service general packet radio service A support node (SGSN) 38 and a gateway GpRS support node (GGSN) 40. 95692. doc • 20- 200522578 If a circuit-switched call exists, the core network 30 may be coupled to an external circuit-switched (CS) network 42 (such as a public switched telephone network (PSTN) or (ISDN)) to provide the circuit Switch connection; if a packet switch call exists, it can be coupled to a PS network 44 (such as the Internet) to provide a packet data service connection. UMTS signaling protocol stack FIG. 2 is a block diagram of the UMTS signaling protocol stack 110. The UMTS signaling protocol stack 110 includes an access hierarchy and a non-access hierarchy (NAS). The access hierarchy typically includes a physical layer 120; a layer 2 130, which includes a media access control (MAC) layer 140 and a radio link control (RLC) layer 150; and a radio resource control (RRC) layer 160. The layers of the access hierarchy are explained in more detail below. The UMTS non-access hierarchy is basically the same as the upper GSM layer and can be divided into a circuit switching section 170 and a packet switching section 180. The circuit switching section 170 includes a connection management (CM) layer 172 and a mobile capability management (MM) layer 178. The CM layer 172 handles circuit switching calls and contains sublayers. The call control (CC) sublayer 174 performs functions such as setup and release. The supplementary services (SS) sublayer 176 performs functions such as call forwarding and three-way calling. The short message service (SMS) sublayer 177 performs short message services. The MM layer 178 handles the location update and authentication operations of the circuit switching call. The packet switching section 1 80 includes a conversation management (SM) sublayer 182 and a GPRS mobility management (GMM) sublayer 184. The conversation management (SM) sublayer 182 handles packet switching calls by performing functions such as setup and release, and also includes a short message service (SMS) section 183. The GMM sublayer 184 handles location updates and 95692 for packet switching calls. doc -21-200522578 Certification. FIG. 3 is a block diagram of a user plane for packet switching in a UMTS protocol stack. The stack includes an access hierarchy (AS) layer and a non-access hierarchy (NAS) layer. The NAS layer includes an application layer 80 and a packet data protocol (PDP) layer 90. The application layer 80 is located between the user equipment (UE) 10 and the remote user 42. The PDP layer 90 (e.g. IP or PPP) is located between the GGSN 40 and the user equipment (UE) 10. The lower layer packet protocol (LLPP) 39 is located between the remote user 42 and the SGSN 38. The Iu interface protocol 25 is located between the radio network controller (RNC) 24 and the SGSN 38, and the Iub interface protocol is located between the radio network controller (RNC) 24 and the node B 22. The rest of the AS layer is explained below. Access Hierarchy (AS) Layer Figure 4 is a block diagram of the access hierarchy part of the UMTS signaling protocol stack. The conventional access layer includes a physical layer (L1) 120; a data link layer (L2) 130, which includes the following sublayers: a media access control (MAC) layer 140, a radio link control (RLC) layer 150, and packet data convergence A protocol (PDCP) layer 156, a broadcast / multicast control (BMC) layer 158; and a radio resource control (RRC) layer 160. These layers are explained in more detail below. The radio bearer carries user data 163 between the application layer and layer 2 (L2) 130. The control plane signaling 161 can be used as all UMTS-specific control signaling, and includes application protocols in the signaling bearer to transmit such application protocol information. This application protocol can be used to establish a bearer to the UE 10. The user plane transmits all user plane information 1 63 sent and received by the user, such as encoded voice in a voice call or a packet in an Internet connection. User plane information 163 will carry data strings and 95692 of those data strings. doc -22- 200522578 data bearing. Each data string is characterized by more than one frame protocol specified by the interface. The radio resource control (RRC) layer 160 can be used as the overall control of the access hierarchy and organizes all other layers in the access hierarchy. The RPC layer 160 generates control plane signaling 161, which can control the radio link control unit 152, the physical layer (L 1) 120, the media access control (MAC) layer 140, the radio link control (RLC) layer 150, and packet data convergence Protocol (PDCP) layer 156, and broadcast / multicast control (BMC) layer 158. The radio resource control (RRC) layer 160 determines the type of measurement and reports these measurement results. The RPC layer 160 can also be used as a non-access level control and signaling interface. More specifically, the RRC layer 160 broadcasts system information information, which includes both the access hierarchy and non-access hierarchy information elements of all user equipment (UE) 10. The RRC layer 160 establishes, maintains, and releases a radio resource control (RRC) connection between the UTRAN 20 and the UE 10. The UE RRC will request the connection, and the UTRAN RRC will establish and release the connection. The RRC layer 160 also establishes, reassembles, and releases radio bearers between UTRAN 20 and UE 10. The UTRAN 20 initiates these operations. The RRC layer 160 also handles the various characteristics of the mobile device's (UE) 10 mobile capabilities. These procedures depend on the UE status (whether the call is a circuit-switched call or a packet-switched call) and the radio access technology (RAT) of the new cell. The RRC layer 160 will also page UE 10. Regardless of whether the UE is listening to the paging channel or the outgoing indication channel, the UTRAN RRC will paging the UE. The RRC of the UE notifies the upper layer of the core network (CN) 30. The data link layer (L2) 130 includes a media access control (MAC) sublayer 95692. doc -23- 200522578 40, a radio link control (rlc) sublayer 150, a packet data convergence protocol (PDCP) sublayer 156, and a broadcast / multicast control (BMC) sublayer 158. The Broadcast and Multicast Control Protocol (BMC) 158 communicates information from the cell broadcast center on the radio interface by adapting broadcast / multicast services from the broadcast domain on the radio interface. The BMC Agreement 158 provides services called "radio bearers" and exists in the user plane. The BMC protocol 158 and RNC will store the cell broadcast information received on the scheduled CBC-RNC interface for transmission. On the UTRAN side, the BMC protocol 158 will calculate the necessary transmission rate of the cell broadcast service based on the information that can be received on the CBC-RNC interface (not shown), and request the appropriate CTCH / FACH from the RRC Resources. The BMC protocol 158 will also receive schedule information and broadcast information for each cell on the CBC-RNC interface. The BMC will generate scheduled information based on the scheduling information on the UTRAN side and generate a scheduled BMC information sequence accordingly. On the user device side, the BMC evaluates the scheduling information and indicates the scheduling parameters to the RRC. The RRC can then use the parameters to organize the lower layers for discontinuous reception. The BMC also transmits BMC information according to a certain schedule, such as schedule information and cell broadcast information. The undamaged cell broadcast information can be transmitted to the upper layer. Part of the control signaling between UE 10 and UTRAN 20 may be radio resource control (RRC) 160 information, which will carry all necessary parameters for establishing, modifying, and releasing layer 2 protocol 130 entities and layer 1 protocol I20 entities. RRC information carries all higher-level signaling in its payload. Radio Resource Control (RRC) controls the user in connected mode by sending measurement results, handover signals, and cell update signals. 95692. doc -24- 200522578 The mobility of the device. The Packet Data Convergence Protocol (PDCP) 156 exists in the user plane of services originating from the ps domain. The services provided by PDCP can be called radio bearers. The Packet Data Convergence Protocol (PDCP) provides header compression services. The Packet Data Convergence Protocol (PDCP) 156 contains a compression method that provides better spectrum service efficiency for transmitting IP packets over the air. Any header compression algorithm can be used. The PDCP compresses redundant protocol information at the transmitting entity and decompresses it at the receiving entity. The header compression method may be specific to a special network layer, transport layer, or a combination of upper layer protocols (for example, TCP / IP and RTP / UDP / IP). PDCP also transmits the user data it receives in the form of PDCP Service Data Units (SDUs) from the non-access hierarchy, and forwards it to the RLC entity; it can also do the reverse. PDCP will also support lossless SRNS relocation. When PDCP uses acknowledged mode (AM) RLC in sequential transmission, a PDCP entity that can be configured to support lossless RSRNS relocation will have a protocol data unit (PDU) sequence number, which can be used along with an unconfirmed PDCP packet Passed to new SRNC before relocation. The RLC layer 150 provides services to the higher layers (for example, the non-access layer) through higher-layer protocols in the UE side and service access points (SAPS) that can be used by the IUNAP protocol in the UTRAN side. The service access point (SAPS) will describe how the RLC layer processes the data packets. All higher-level signaling (such as mobility management, call control, conversation management, etc.) can be encapsulated in the RLC information transmitted by the radio interface. The RLC layer 150 contains various radio link control entities 152, and these radio link control entities will carry a letter 95692. doc -25- 200522578 enables the logical channel of information and user data to be coupled to the MAC layer 140. On the control plane 161, the RLC layer can use these RLC services for signal transmission. On the user plane 163, these RLC services can be used by the service specific protocol layer PDCP or BMC, or by other higher-level user plane functions. For services that do not use PDCP 156 or user plane agreements, such RLC services may be referred to as the signaling radio bearer in the control plane 161 and the radio bearer in the user plane 163. In other words, if the service cannot use the PDCP and BMC protocols, the RLC layer 150 can provide a service called signaling radio bearer (SRB) in the control plane 161 and a redundant bearer (rb) in the user plane 163 ) Services. Otherwise, the PDCP layer 156 or the BMC layer 158 can provide the RB service. The radio link control (RLC) layer 150 implements a framing function on the user and control data, which includes split / concatenation and padding functions. The RLC layer 150 typically provides segmentation and retransmission services for the radio resource control (RRC) 160 layer of control data in the control plane 161 and the application layer of user data in the user plane 163. The RLC layer usually divides a variable-length higher-layer protocol data unit (PDU) into a plurality of smaller RLC protocol data units (PDUs) or recombines a plurality of smaller RLC protocol data units (PDUs) into a variable Length higher layer protocol data unit (PDU). A radio link control (RLC) protocol data unit (PDU) typically carries a PDU. For example, the radio link control (RLC) can be used to set the radio link control (RLC) PDU size based on the minimum possible bit rate of the service. As will be discussed below, for variable-rate services, as long as the bit rate is higher than the lowest one used, the number of transmissions during a transmission time interval (TTI) is 95692. doc -26- 200522578 Radio Link Control (RLC) PDUs. The RLC transmission entity also performs the concatenation operation. If the contents of a Radio Link Control (RLC) Service Data Unit (SDU) cannot fill an integer number of Radio Link Control (RLC) PDUs, the first segment of the next Radio Link Control (RLC) SDU can be placed Into the Radio Link Control (RLC) PDU, it is used to concatenate the last segment content of the previous RLC SDU. The RLC transport entity usually also implements padding functions. When the remaining data to be transmitted cannot fill the entire Radio Link Control (RLC) PDU of a certain size, then the remaining data fields can be filled with padding bits. For example, from the perspective of this issue discussed below with reference to Figures 11-13, this article will provide techniques for reducing or omitting the amount of padding used. The RLC receiving entity will detect the copy of the received Radio Link Control (RLC) PDU and ensure that the results in the higher layer PDU will be transmitted to the upper layer only once. The RLC layer also controls the rate at which the PRLC transmitting entity can send information to an RLC receiving entity. FIG. 5A is a block diagram of a data transmission mode used in the Radio Link Control (RLC) layer of the UMTS signaling protocol stack, and also shows possible mappings of logical channels, transmission channels, and physical UMTS channels related to the access layer . Those skilled in the art will find that it is not necessary to define all mappings for a specific user equipment (UE) at the same time, and there will be multiple instances of some mappings at the same time. For example, a voice call might use three dedicated traffic channel (DTCH) logical channels mapped to three dedicated channel (DCH) transmission channels. Furthermore, some channels (such as CPICH, SCH, DPCCH, AICH, and PICH) shown in Figure 5 exist at the physical layer 95692. doc • 27- 200522578 is in the scene ’and does not carry higher-level signaling or user data. The content of these channels may be defined in the physical layer 120 (L1). Each RLC instance in the Radio Link Control (RLC) layer can be configured using the Radio Resource Control (RRC) layer 160 to operate in one of three modes: transparent mode (TM), unacknowledged mode (UM) Or i mode (AM), which will be described in detail below with reference to FIG. 5B. The three types of data transmission instructions indicate the mode in which the radio link control (RLC) is configured for a certain logical channel. RLC entities in transparent and unconfirmed mode will be defined as one-way, while entities in confirmed mode will be defined as two-way. Generally, for all RLQ modes, a CRC error check is performed on the physical layer, and the CRC check result is transmitted to the Rlc together with the real data. Depending on the special requirements of each mode, these modes will implement some or all of the functions of the rlc layer 150. These functions include segmentation, reassembly, concatenation, padding, retransmission control, data flow control, copy detection, Sequential delivery, bugfixes, and encryption. These functions will be described in more detail below with reference to Figs. 5B and 5C. According to the viewpoint of the present invention discussed herein, the present invention can provide a new radio link control (RLC) data transmission mode. The AC layer 140 will provide services to the RLC layer 150 using logical channels characterized by the type of data being transmitted. The media access control (MAC) layer 14 maps the edit channels to the transmission channels. The MAC layer 14 will identify the user equipment (UE) on the common channel. The MAC layer 140 also multiplexes higher-layer PDUs into multiple transmission blocks for transmission to the physical layer on the common transmission channel or from multiple transmission area ghosts transmitted from the physical layer on the common transmission channel to solve the problem. More pDUs in the same layer. This MAC handles 95692 for common transmission channels. doc -28- 200522578 serves multiple jobs because the job cannot be done at the entity level. When a common transmission channel carries data from a dedicated logical channel, the Media Access Control (MAC) header will contain the ue identification symbol. The MAC layer will also multiplex the PDU into multiple transmission block sets for transmission to the physical layer on the dedicated transmission channel or a plurality of transmission block sets transmitted from the physical layer on the dedicated transmission channel. Multiplex higher layer PDU. The MAC layer 140 receives a plurality of RLC PDUs and status information. The number is equal to the amount of data in the RLC transmission buffer. The MAC layer 14 will compare the amount of data corresponding to the transmission channel with the threshold set by the RRC layer 160. If the data volume is too high or too low, the MAC will send a measurement report related to the traffic status to the rRC. The RRC layer 160 may also require the MAC layer 160 to send these measurements periodically. The RRC layer will use these reported values to trigger the reconfiguration of these radio bearers and / or transmission channels. The MAC layer also depends on the instantaneous source rate of the logical channels to select an appropriate transmission format (TF) for each transmission channel. The MAC layer 14 will provide different processing priorities for data streams by selecting the "high bit rate" and "low bit rate" transmission formats (TF). The packet of packet switching (ps) data is burst data, so the amount of data that can be sent will change with the message. When more data is available, the MAC layer 140 can choose one of the more direct data rates; however, when both signaling and user data are available, the MAC layer 140 will choose between them to maximize The amount of data sent by the prioritized channel. The transmission mode (TF) can be selected from the transmission format combination (TFC) defined by the admission control of each connection. Some body access control (mac) layer also applies encryption. 95692 per radio. doc 200522578 ^. On 3GPP TS 33. The encryption details are described in 102. In a system such as / MA, three transmission frequencies can be used to transfer round packets: material. These channels are common transmission channels, exclusive transmission channels, and prostitution transmission channels. In the next ;; check 4 taxis,, and order the order, the packet scheduling algorithm will select the channel packet data. In Bu Bing, Zha Shishi + ^ ^, Shanglian,, and Zhongzhong, the mobile station 10 will select the transmission channel based on the parameters set by the packet scheduling algorithm. /. For example, the common channel may be the random access channel RACH of the uplink link and the forward access channel fach in the downlink. Both carry plant materials and user data. The common channel has a very low settling time. Because the common channel can be used to send a message before the winter connection is established, the common channel can be used to send packets immediately without requiring a long settling time. Each sector will usually have a few RACI ^ FACH. The common channel does not have a feedback channel, so open loop power control or fixed power is usually used. Moreover, common channels cannot use soft delivery. Therefore, the link level performance of a common channel may be worse than the link level performance of a dedicated channel, and it may cause more interference than a dedicated channel. Therefore, the common channel is more suitable for transmitting small individual packets. Applications used in common channels may be applications such as short message services and short text messages. Sending a single request to a webpage is also very suitable for the concept of a common channel. However, in the case of a large amount of data, the common channel may be deteriorated due to poor radio performance. Dedicated channels can use fast power control and soft handoff features to improve radio performance, and often produce less interference than common channels. However, it takes 95692 more time to set up a dedicated channel than to access a common channel. doc -30- 200522578 ranges from thousands of speeds per second. The rate used to assign downlink channels during transmission can take a considerable amount of time. Dedicated channels have variable bit rates ranging from 2 bytes to 2 million bytes per second. Because the bits are malformed ', the orthogonal code must be set based on the southernmost bit. Therefore, the variable bit rate is exclusively used to concatenate the orthogonal code space. The physical layer (L1) 120 will be coupled to the page 80 layer 14 through a plurality of transmission channels carrying signaling information and user data. The physical layer 12 will provide services to the MAC layer through a plurality of transmission # channels through which the characteristics of the basin are used to transmit data and which characteristics are used to transmit data. w The physical layer αυΐ20 will receive signaling and user data on the radio company through multiple physical channels. The physical layer (L1) usually implements multiplexing and channel coding, which includes plan #, forward error correction (fec), rate matching, interleaved channel data, multiplexed channel data, and other physical layer procedures ( Such as access, access, paging, and radio link establishment / stomach failure). The physical layer (u) may also be responsible for unrolling and scrambling processing, modulation measurements, multi-passing sets, power weighting, handover, compression mode, and power throttling. FIG. 5B is a block diagram of the architecture of the radio link control (RLC) layer. As described above, each RLC entity or example 152 in the Radio Link Control (RLC) layer 15 can be configured using the #, wire power resource control (state.) Layer_ to operate in the following two lean transmission modes Among them: transparent mode (TM), unconfirmed mode (abdomen), or confirmed mode (AM). The service quality ^ > S) setting value can be used to control the data transmission mode of user data. It is unidirectional and contains a transmitting TM entity, 52 8 and a receiving entity 95692. doc 200522578 1 52B. In the transparent mode, no protocol commands are added to the higher-level data. Incorrect protocol data units (PDUs) can be discarded or mislabeled. Streaming transmission can be used, in which the higher-level data is usually not divided, but in special cases, the transmission of limited division / reassembly functions can be completed. When splitting / regrouping is used, negotiation can be done in the radio bearer establishment procedure. UM is also unidirectional and includes a transmitting UM entity 152C and a receiving UM entity 152D. The reason a UM RLC entity is defined as one-way is because there is no need for any association between the uplink and the downlink. Data transmission is not guaranteed in UM. For example, UM can be used in specific RRC signaling procedures that are not part of acknowledgement and retransmission. Examples of user services that use unconfirmed mode RLC are cell broadcast services and voice over IP. Depending on the configuration, erroneous data received can be marked or discarded. A timer-type drop function without explicit signaling can be applied. Therefore, RLC PDUs that cannot be transmitted within a specified time can be removed from the transmission buffer. In the unconfirmed data transmission mode, the PDU structure includes a plurality of serial numbers, and serial number checking can be implemented. The serial number check helps to ensure the integrity of the reorganized PDU, and can provide a detection component to check the radio link control (RLC) when the radio link control (RLC) PDU is reorganized into a radio link control (RLC) SDU Sequence number in the PDU to detect a broken Radio Link Control (RLC) SDU. Any damaged Radio Link Control (RLC) SDU can be discarded. Split and serial functions are also available in unconfirmed mode (UM). In the confirmed mode, the RLC AM real system is bi-directional and capable of shipping the opposite 95692. doc -32- 200522578 Link status indication signal in the direction of user data. FIG. 5C is a block diagram of an entity for a Radio Link Control (RLC) Confirmed Mode (AM) entity and shows how to construct an AMPDU. Data packets (RLC SDU) received from higher layers via AM-SAP can be split and / or concatenated 514 into a plurality of fixed-length protocol data units (pDUs). The length of the agreement data unit is a semi-static value determined in the establishment of the radio bearer and can be changed by the RRC radio bearer reconfiguration procedure. For concatenation or filling purposes, a multiple bit containing information related to the length and extension may be inserted into the beginning of the last agreed data unit, or data from an SDU may be included. If several SDUs are placed in a pDUi, they can be connected in series, and multiple correct length indicator symbols (LI) are inserted in the beginning of the PDU. These pDUs can then be placed in the transmission buffer 520, which is also responsible for retransmission management. The monthly PDU is constructed as follows: take a PDU from the transmission buffer 52 and add a header to it; if the data in the PMJ cannot fill the entire PDU, you can add _fill block or negative state information. The typed status information may originate from the receiving end or from the transmitting end to indicate an RLC SDU discard situation. This header contains the RLC pDu sequence number (SN);-polling bit _), which can be used to request status from peer entities: and optional length indicator ⑽, if SDU concatenation, padding, or push occurs in the RLC PDU This indicator can be used for negative PDUs. Acknowledged mode (AM) is usually used for packet-type services, such as Internet browsing and email download. In confirmed mode, an error can be corrected using the automatic repeat request (ARQ) mechanism. Any received packets with errors 95692. doc 200522578 can be retransmitted. The configuration of the number of retransmissions provided by the RLC can be used to control the quality and delay performance of the RLC by using RRC. For example, if the RLC does not transmit data correctly, if the maximum number of retransmissions has been reached or the transmission time has been exceeded, the upper layer will be notified and the radio link control (RLC) SDU will be discarded. It is also possible to notify the peer entity of the SDU discarding job by sending a mobile receive window command in the status information, so that the receiver will also remove all PDUs belonging to the discarded Radio Link Control (RLC) SDU. The RLC can be organized for sequential and out-of-order transmissions. With sequential transmission, the higher order of PDy can be maintained; conversely, out-of-order transmission will be immediately forwarded when the higher-level PDU is fully received. The RLC layer can sequentially transmit higher-level PDUs. This function preserves the order in which these RLCs transmit higher layer PDUs. If this function is not used, it can provide out-of-order transmission. In addition to data PDU transmission, status and reset control procedures can also be sent between peer RLC entities. These control procedures may even use a separate logical channel, so an AM RLC entity may use one or two logical channels. Encryption can be implemented in the RLC layer for both confirmed and unconfirmed RLC modes. In FIG. 5C, the AMRLCPDU is encrypted 540, which excludes the first two bits containing the PDU sequence number and polling bits. The PDU sequence number is one of the input parameters of the encryption algorithm and must be readable by a peer entity in order to perform the encryption operation. 3GPP specification TS33. 102 describes the encryption process. The PDU can then be forwarded to the MAC layer 140 through a plurality of logical channels. A dashed line is used in Figure 5C to represent the additional logical channel 95692. doc -34- 200522578 (DCCH / DTCH), the dashed lines illustrate that an RLC entity can be configured to send the control PDU and data PDU using different logical channels. The receiving end 530 of the AM entity receives a plurality of RLC AM PDUs from the MAC layer through one of the logical channels. The CRC calculated for the entire RLC PDU in the physical layer can be used to check for errors. The actual CRC check may be implemented at the entity layer, and the RLC entity will receive the result of the CRC check and the data generated after encrypting the entire header, and may extract possible piggyback status information from the RLC PDU. If the received PDU is a strong message or if the status information is carried on an AM PDU, the control information (status information) can be transmitted to the transmitting end, and the transmitting end will compare the received information with the received one. Status information to check its retransmission buffer. The number of PDUs originating from the RLC header is used for decryption 550 and for storing encrypted PDUs in the receive buffer. Once all PDUs belonging to a complete SDU are located in the receive buffer, the SDU can be reassembled. Although not shown in the figure, sequential transmission check and copy detection can then be performed before the RLC SDU is transmitted to a higher layer. When the user equipment (UE) or mobile station moves between PTM transmission and point-to-point (PTP) transmission or changes cells, the RLC entity 152 is re-initialized. This may unfortunately result in the loss of data in the Radio Link Control (RLC) buffer. As mentioned above, when the mobile station moves from one cell to another or when the delivery of multimedia broadcast and multicast service (MBMS) content in the serving cell changes from a point-to-point (PTP) transmission mode to a point-to-multipoint (PTM) ) Problems may occur during transmission mode. We want to do both point-to-point (PTP) transmission and point-to-multipoint (PTM) transmission 95692. doc -35- 200522578 during transfer or between different cells (such as handover) preserves the continuity of multimedia broadcast and multicast service (MBMS), and avoids submitting copies of information. To preserve the continuity of the MBMS service and avoid handing out duplicate information, layer 2 150 should be able to rearrange the data from these two streams. The physical layer cannot provide this synchronization because the network termination point may be different in each mode. If forward error correction (FEC) is implemented below the RLC layer 150 as in the case of 3GPP2, data may be lost during the migration from point-to-multipoint (PTM) transmission to point-to-point (PTP) transmission, instead The same goes for migration. In addition, for example, multiple cells with a common schedule may need to perform physical layer synchronization and share the same media access control (MAC). In this regard, these assumptions do not apply to 3GPP2, which may cause problems. Point-to-point (PTP) transmission Assuming the application has significant delay tolerance, the most effective data transmission mode for point-to-point (PTP) transmission is the radio link control (RLC) acknowledged mode (AM). For example, RLC acknowledged mode (AM) is usually used for packet switching data transmission on a dedicated logical channel (PTP). The RLC operates in an acknowledged mode (AM) on a dedicated logical channel. As shown in FIG. 5A, the dedicated user traffic of one of the user services in the downlink direction can be sent via a logical channel called a dedicated traffic channel (DTCH). In the confirmed mode (AM), if the data is wrong, the reverse link can be used for retransmission. The RLC transmits multiple service data units (SDUs) and uses retransmissions to ensure that it can be correctly transmitted to its peers. If the RLC cannot transmit the information correctly, it will notify 95692. doc -36- 200522578 The user of the RLC at the output. Operation in RLC AM usually must introduce additional delays in exchange for greater power efficiency. Point-to-multipoint (PTM) transmission The common traffic channel (CTCH) is a unidirectional channel that exists in the downlink direction, and it can be used when transmitting information to all terminals or a specific terminal group. Both of these data transmission modes use a one-way common channel, which does not have a backlink channel creation operation. We want to provide an architecture that allows MBMS services to transparently switch between a point-to-point (PTP) transmission mode and a point-to-multipoint (PTM) transmission mode. In order to obtain good performance when transferring between point-to-point (PTP) transmission mode and point-to-multipoint (PTM) transmission mode, we also hope to provide a framework that allows switching between different radio link control (RLC) modes. For example, this approach can help reduce power requirements. Various aspects of the present invention will now be explained with reference to the specific embodiments shown and described with reference to Figs. Among other features, these features can take advantage of a new forward error correction (FEC) layer to help preserve service continuity during these migrations. Figure 6 is a schematic diagram of a modified UMTS protocol stack with a forward error correction (FEC) layer, which can operate in the forward error correction (FECd) mode and in the forward error correction (FECc) mode. The Forward Error Correction (FEC) layer allows the underlying Radio Link Control (RLC) entity 152 to change from one of the types when the user equipment (UE) changes from point-to-point (PTP) transmission to point-to-multipoint (PTM) transmission. Radio Link Control (RLC) data transmission mode is changed to another Radio Link Control (RLC) data transmission mode, which can maintain 95692. doc -37- 200522578 supports service continuity. According to this embodiment, the FEC layer may operate in a first mode (FECc) or a second mode (FECd). In one implementation, the first mode (FECc) can use parity blocks, while the second mode (FECd) does not require any parity blocks. The impact of changes between the FECd mode and the FECc mode may be much lower than the changes between the RLC modes, and may be seamless, so that no data is lost during the migration. Forward Error Correction (FECc) mode uses external coding techniques to protect user data. This is particularly effective on common channels. The forward error correction (FECc) mode usually allows the functions found in the unconfirmed mode (UM) to be performed above the radio link control (RLC) layer, such as sub-frame (split and concatenation) and serial number addition functions. Therefore, the radio link control (RLC) layer can use transparent mode (TM) for point-to-multipoint (PTM) transmissions, as traditional unacknowledged mode (UM) functions may be in the forward error correction (FEC) Layers are implemented. Although this feature may be repeated in Radio Link Control (RLC) Confirmed Mode (AM), the gain caused by ARQ can compensate for this duplication effect. By placing the forward error correction (FEC) layer or external coding layer on top of the radio link control (RLC) layer, the sequence number can be added to a layer unrelated to the radio link control (RLC). Using additional additional data (such as serial numbers), then unacknowledged transmissions can be used to unalign the protocol data units (PDUs) to an encoder packet (EP) during the asynchronous transmission of MBMS data. The serial numbers are forced into the layer above the radio link control (RLC), so these serial numbers are point-to-point (PTP) transmission and point-to-multiple 95692. doc -38- 200522578 Both point-to-point (PTM) transmissions are common, so when moving from point-to-multipoint (PTM) transmissions to point-to-point (PTP) transmissions, serial number continuity can be maintained. This allows the data to be rearranged so that duplicate data and / or lost data can be avoided. External coding can also be used in point-to-point (PTP) transmission, which can increase part of the power gain of the system and / or reduce retransmission delay. Multimedia broadcast and multicast service (MBMS) data can tolerate some delay. A feedback path is provided in point-to-point (PTP) transmission. This method will make the use of Radio Link Control (RLC) Confirmed Mode (AM) more daunting due to the use of ARQ retransmission. Generally speaking, when ARQ retransmission is required, its radio efficiency will be better than FEC architecture To be effective, because FEC technology will definitely send an additional plurality of parity blocks. In this regard, it is not necessary to add multiple parity blocks to the MBMS payload data on a dedicated logical channel (for example, point-to-point (PTP)). 7A and 7B are specific embodiments of the protocol structure of the access layer in which a forward error correction (FEC) layer 157 is placed on the radio link control (RLC) layer 150. A specific embodiment of the forward error correction (FEC) layer will now be described with reference to FIG. The forward error correction (FEC) layer 157 directly receives user plane information 163 on the user plane radio bearers. Because the forward error correction (FEC) layer is at the top of the radio link control (RLC) layer, the FEC protocol data unit (PDU) corresponds to the RLC service data unit (SDU). The FEC layer preferably supports arbitrary SDU sizes (which are limited to multiples of 8 bits), variable rate data sources, out-of-order reception of packets from the lower layer, and from 95692. doc -39- 200522578 Replica packets are received in the lower layer. FEC? 1) The 11+ limit may be a multiple of 8 bits. As will be described in more detail below with reference to FIG. 9-8, the FEC layer 157 divides and concatenates higher-level user data blocks (such as SDU) into the same size. Each row can also be called an internal block. . Each protocol data unit (PDU) may contain additional data. The additional information may include a length indicator (I) to indicate that lean material that does not originate from a particular user data block (such as a service data unit (SDU)) can be placed at the beginning of the last _ agreement data unit . Collecting multiple PDUs will form an encoder packet (Ep) or "encoder ring". The number of PDUs contained in the Encoder Packet (EP) depends on, among other factors, the external code used. Encapsulating each of the "Flat Code Matrix" columns into a separate or separate transmission time interval (TTI) can enhance the performance of the physical layer. To mitigate buffering negative #, a shorter transmission time interval (TTI) duration can be used. In order to generate the equivalent bit sequence, the encoder packet (Ep) is transmitted by an external code encoder. As will be described in more detail below with reference to FIG. 9A, the FEC ^ 157 can be implemented by the Reed-Solomon_Code H function provided in the UMTS Terrestrial and Wireless Access Network (UTRAN) 2G to implement external W coding Moreover, external decoding can be implemented by providing a Reed Solomon decoder function in the user equipment (ue) i 〇. The equivalent bit sequence generated by the external encoder can be added to the encoder packet (EP), and can be placed in a transmission buffer as a group of internal blocks. Each internal block has additional information that is used to generate a _1 data unit (PDU). These pmj groups can then be transmitted. , 95692. doc -40- 200522578 The FEC layer 157 also said that the data of a single £ P was restored, that is, different cells received different internal blocks. This is accomplished by transmitting the sequence number (SN) in the header of each agreed data unit (PDU). In one embodiment, the system frame number (SFN) helps maintain data alignment according to the encoder packet (EP). The serial numbers will be discussed in more detail herein with reference to Figures 10A and 10B. The FEC layer 157 can also perform padding and reassembly, user data transmission, and sequential transmission of upper-layer PDUs, copy detection, and serial number checking. In the specific embodiments of FIGS. 6 to 7A, the forward error correction (FEC) layer 157 is located between the packet data convergence protocol (PDCP) layer 156 and the radio link control (RLC) layer 150 (for example, the BMC layer and the BMC layer). At the same level and below the Packet Data Convergence Protocol (PDCP) layer). By placing a forward error correction (FEC) layer 157 above the radio link control (RLC) layer 150, the performance of the external code can be optimized, as the internal block size can match those intended to be in the air. The "golden" packet size of the packet being sent. However, we should find that the forward error correction (FEC) layer in this figure is for illustration purposes only and is not restrictive. For its header compression, a packet data convergence protocol (PDCP) layer 156 can be used on top of the forward error correction (FEC) layer 157. It should be noted that the packet data convergence protocol (PDCP) layer 156 is currently defined for point-to-point (PTP) transmission using a dedicated logical channel. As shown in FIG. 7B, the forward error correction (FEC) layer may be provided within the access layer on the radio link control (RLC) layer or anywhere in the application layer. The forward error correction (FEC) layer may be located below or above the packet data convergence protocol (PDCP) layer. If FEC is implemented in the application layer 80, 95692. doc -41-200522578 Even if GSM and WCDMA have different "golden" packet sizes, they can be applied to GSM and WCDMA.

External Code Design This new Forward Error Correction (FEC) layer enables external coding of user plane information. FIG. 8 is a schematic diagram of an information block 91 and an external code block 95. The diagram is a concept illustrating the structure of an external block code. FIG. 9A is a schematic diagram of an example of how to apply an external code block structure to multimedia broadcast and multicast service (MBMS) data 91. When broadcasting a tolerable delay within the entire cell

In addition, external coding can improve the performance of the physical layer. For example, the outer code helps to avoid losing data during the migration between cells and between the point-to-point (ρτρ) transmission mode and the point-to-multipoint (PTM) transmission mode. The outer code block 95 can be represented in the form of a matrix, which contains k agreement sheets 7G 91 and N-k parity columns 93. In the external block encoding, by dividing, concatenating, and filling the data (including inserting additional

Data) By organizing user data into k payload rows, the data can be composed into a large encoder packet or information block 9 and then the generated asset ghost 1 can be processed and flattened to generate N_k pieces. The parity column M can be added to the information block 91 in order to produce an external code block 95. The: rank 93 will add redundant information to the information block. Then, the individual columns of the external code block can be transmitted in a single or multiple transmission time intervals (TT1). Even if some of the protocol data units (PDUs) are lost during transmission, the redundant information of the group of protocol data units (pDUs) can still be used. τ 里 漫 原图 Figure 9A is a schematic diagram of an exemplary external code region called Reed Solomon_block code 95692.doc -42- 200522578 block. Reed-Solomon (RS) codes can be used to detect and correct channel errors. The external code shown in FIG. 9A is a systematic (n, k) block code, where each Reed-Solomon (RS) code symbol includes an information byte defined by a column and a row. Each line includes a Reed-Solomon (RS) code block. If n missing blocks are to be restored, then at least n parity blocks are needed. In this regard, the amount of memory required will increase as the number of co-located blocks increases. In Reed-Solomon (RS) coding, N-k parity symbols can be added to k systematic symbols to generate a codeword group. In other words, a Reed-Solomon (RS) [N, k] codeword group has solid information or "systematic" symbols and N-k identical symbols to you. N is the length of the code, and & is the dimension of the code. For every k poor-sense bytes, the code will generate n coding symbols, and the first k symbols may be exactly the same as the information symbols. Each column can be called an "internal block" and represents the payload of each transmission time interval (ττι). For example, in a normal WCDMA system, transmission can be performed on the basic WCDM A structure of a 20 frame (TTI). The equivalent bit symbol can be derived from these systematic symbols using the generator matrix GkxN defined below: Equation (1)

mlxk # GkxN = CixN Equation (2) Equation (3) mixk = Information word group = [m〇m! _. · mk l] ClXN = Code word group Cl ··· .Cn 」] where Ci belongs to an arbitrary Galois Field. For example, if the symbol of a Reed_Solomon (RS) codeword is a one-bit unit, then the Galois Field (GF (2)) of dimension 2 can be used to describe the decoding operation. In one of the embodiments, if the symbol is an octet, then the gamma of the dimension W 95692.doc -43- 200522578 Luohua domain GF (256) can be used to describe the decoding operation. In this case, each white line is composed of 1 byte per column. Each information line can be encoded using the [N, k] Reed-Solomon code on the Galois Field GF (256) of the dimension. If there are M bytes in each column, the external block has to encode money. Therefore, each external block 95 will have N * M bytes. Delete calcite horse This external code structure allows domain correction. If the decoding stomach already knows that I5 symbols are wrong, then reconstructing the wrong systemic symbols requires only a very small amount of calculation. -Encoding 11 packets or matrix represents the entire data at the output of the external encoder. 7 times >-The leaves were taken, and more than one message was taken from each column in a vertical row, and each column transmitted was

A CRC is attached at the back, which must be checked to confirm the vessel3

Is the material sent correctly? In the case of MBMS transmission, a CRC can be used in each round channel channel block to indicate whether an internal block 91 is incorrect and ^ > If the CRC check fails, α can be set All of you ^ Ding Ding in this block are wrong. In a specific implementation column, ‘right 'assumes that an internal block 97 7 group αα has ^, then all bits of the block can be deleted. "Deleting a call ^ 所 # belongs to a τ whose failed CRC check failed each pass τ. The non-deleted symbols can be assumed to be correct. Ignore errors not detected by the CRC > Ratio, and money rate, then, each Νχ 1 仃 white contains correct and deleted symbols. The received vector r can be written as:. · Cn-1 Equation (4) ΓΐχΝ = [c〇ee c3 c4 e c6 where e stands for deletion. Deletion decoding allows corrections up to N_k $ determined delivery. Because the non-deleted character 95692.doc -44- 200522578 can be false and correct again, so the error correction characteristics of the § code will be much better Standard horse ### Correction characteristics. The size used in each internal block should be sufficient to ensure that the probability of undetected errors does not exceed the probability of remaining external blocks. For example, %%, 4 w Α

Mu Yeyou uses a 16-bit CRC in the internal block of the temple, so the lower limit of the residual external block error rate will be 2_16 = 1. There are no wrong words in the k internal blocks on 1J on the right of 5 · 10. Then, it is not because 'the systematic symbols are equal to the information symbols. After receiving the k blocks with good CRC, Erzhuangxin can implement the decoding of the external block without waiting for receiving all the N internal blocks. In order to implement deletion decoding, all rows corresponding to a plurality of deletion characters or unnecessary blocks can be removed, so as to derive a generator matrix modified from the generator matrix GkxN, for example, Only the first well-received symbol can be used to represent the modified generator matrix ^. The following information can be used to restore the original information block m: kxk], k in equation ⑺ f is to use the previous _good The modified receive vector obtained by the symbol. Therefore, the deletion decoding complexity can be reduced to the complexity of the matrix. Therefore, using RS deletion decoding can greatly simplify the computational complexity of side decoding. Data packet performance for external codes Impact 2 = With reference to the discussion in Figure I13, if the special external encoding structure limits the amount of padding and additional data, the external encoding can be used in conjunction with a variable rate data source without causing excessive additional data In the external code architecture discussed above, the data can be packaged to a specific size 95692. doc -45- 200522578 J, and you can perform shortened Reed-Solomon horses to v on these blocks. There are two different ways to pass the encoded packet data into multiple TTIs. Now Description will be made with reference to FIGS. Fig. 9B is a schematic diagram of the outer code block structure of Fig. 9A, in which multiple columns are transmitted in each transmission time interval (TTI). According to another aspect of the present invention, the point of view 'will transmit data from one of the columns in a single TTI. In another specific example, the data from an encoder packet queue is placed in a TTI so that each TTI contains the data from the encoder packet (. In this regard, it can be used in- Each W column is transmitted in a separate WCDMA frame or round time interval (TTI). Each column in one of the ττι will provide better performance. In Figure 9B, ... must be divided by each The number of columns is ，, and the errors in a certain column can be completely correlated. In this way—observing the relationship between the EP error rate and the TTI error rate, a significant difference can be produced. Where each—multiple TTIts are sent. It should be understood that although FIG. 9c sends per-column encoder packets (Eρ) in four ^ (TTI0-TTI3), * yes, each-column on p Send in any number of TTIs. Since each _ ^ is an external code codeword group, each of these four ㈣ transmission wheels: σ ™-™) is combined to form an independent external code. In order to restore the entire packet, all of these independent codes must be decoded correctly. Fig. 10A is a schematic diagram of blocks generated for the forward error correction layer. The V ^ / order mode can be used for common or point-to-multipoint (on the logical logic channel, by adding the parity column or block% in MBMS payload data 9ΐφ + λ 戟 卄 91) to construct outside 95692. doc -46- 200522578 code block 95. Each external block 95 contains a plurality of internal blocks 91, 93 ° The order of identifying internal blocks and their position relative to the encoder packet can place each available internal block in the correct position, so that Can be correctly 70% external decoding. In one embodiment, each internal block includes a header 94, which can use the number of internal blocks m and the number of external blocks n to identify the " Heinet σ 卩 block. For example, the external block n includes a data portion 91 having m multimedia broadcast and multicast service (MBMS) payload blocks, and a redundant portion 93 having an internal parity block. According to this specific example, the serial number space can be optimized for MBMS, and several different serial numbers (for example, 0 to 127) are used to define the serial number space. This sequence number space should be large enough that the same sequence number does not appear after the reception gap caused by any transfer type. Even if some internal blocks are missing, the receiving UE should still be able to determine the order of these internal blocks. If the UEm loses more internal blocks than the entire sequence space can recognize, the UE will not be able to reorder the internal blocks correctly. The sequence numbers of the same internal blocks spanning these FECd blocks and FECC blocks are exactly the same. These blocks do not include the redundant part 93 used in these FECc blocks. FECd shells and FECc entities can use the same bit rate in the air. The transmission end forward error correction (FEC) entity 410 includes a service data unit (SDU) buffer 412 to receive the SDU; a segmentation and concatenation unit 414; an external encoder 416 to implement Reed -Solomon (RS) encoding; a serial number generator 418 to add a serial number to the encoded Pdus; a transmission buffer 420 to transmit the 95692 on the logical channels 406. doc-47-200522578 PDU; and a scheduling unit 422. The service data unit (SDU) buffer 412 receives the user data (FEC SDU) in the form of a service data unit (SDU) on the radio bearer 402 as shown by the arrow, and stores the FEC SDU from a higher layer. The receiving buffer 412 notifies the scheduling unit 422 how much data will be transmitted. As discussed above, the amount of time it takes to fill an encoder packet (Ep) usually varies, because the data source rate usually varies. As explained with reference to Fig. 13, by flexibly deciding when to start packing the data, the frame filling efficiency can be improved. Based on the jitter tolerance of the receiving FEC entity 430, delaying the manufacturing time of the Ep as much as possible can reduce the amount of padding introduced. The scheduling entity 422 may decide when to start coding. The scheduler 422 preferably determines the length of time that a packet must be dedicated based on the qOS curve of the special service. Once the scheduler 422 determines that sufficient data has been accumulated, or the maximum acceptable packet transmission delay has been exhausted ', the scheduler will trigger the generation of an encoder packet (Ep) 9 丨. The dividing and concatenating unit 414 may divide the service data unit (SDU) into columns and generate a length indicator (LI). The scheduling unit 422 preferably determines the optimal column size of the Ep or Protocol Data Unit (pDU), so that the SDUs can be placed in the number of columns (for example, '12 columns). Alternatively, the scheduler 422 will select a FEC PDU size from the fec pDu size organized by the RRC, which will result in the least possible padding operation 'and requires the segmentation and concatenation function 414 to format the Sdus into a size of PDU-size-FEC-Header-size block. This format job 95692. doc • 48- 200522578 can be changed. Examples of different formatting types are discussed below with reference to Figures 12-13. The total amount of data considered should include additional data that will be incorporated by the concatenation and split function 414. To generate the encoder packet (p), the scheduler 422 will request the concatenation and segmentation function 414 to generate k PDUs of this size. This size contains reorganization information. In one specific embodiment, the sizes of the PDUs are multiples of 8 bits and are continuous! > 〇11's data should match different symbols in the codeword group. These k PDU blocks can then pass through an external encoder 416 that implements Reed-Solomon (RS) encoding. The external encoder 416 generates redundant or parity information and appends it to the encoder packet (Ep) matrix to generate an external code block to encode the data in the encoder packet (Ep) matrix. In a specific practical example, Yanhai's external stone horse can assume that (n, k) deletes the decoded block code 'and that the external encoder will produce parity blocks. The encoder encodes information of equal length in k columns and sends it to n co-data units (pDU) of the sub-layer under the same size. The old blocks will be the same as the blocks they receive, while the next n_k blocks will correspond to the parity information. The scheduler 422 also monitors the time alignment or relative timing of the PTM strings and implements transmissions to adjust the alignment of different logical strings. For example, during reconfiguration, you can adjust ρτρ to align the surname T with the time between logical strings to facilitate service continuity. The best performance is obtained when these data strings are fully synchronized. Different base stations (or different transmission modes ρτρ, point pair (PTM)) will transmit the same content. π ° hai search content string may not be able to ^ encoder packets of the right and other shell material string ⑽) the same format 95692. doc -49- 200522578:, then the information on each data string is exactly the same. Adding a serial number to each outer π block allows the user equipment (gang to combine the two data strings' because the user equipment (UE) will know the relationship between the two data strings. The serial number generates theft 41 8 An order 諕 is added in front of each block to generate pDu in the same order as used in the encoder 416. For example, ^ in a specific embodiment, the sequence number generator Add an eight-digit serial number in front of the block to generate ugliness. You can also add additional additional information to the external code block. The serial number space should be enough to accommodate the worst time difference between the data strings. So, in another In a specific embodiment, a serial number space with a size of 20 can be used, and at least 5 bits can be reserved for the serial number in each header. The header can be appended after Reed Solomon (rs) encoding is implemented To the external code block, so this "external" header does not protect the external code. It is better to add serial numbers to the parity blocks, even if the serial numbers may not be transmitted. One specific embodiment In this case, the serial phase of the serial number can be used to define the encoder packet boundary. A serial number advance indicates that a new encoder packet has been received. The forward error correction (FEC) header format is as described above. The serial number can achieve the purpose of data string synchronization. In addition to reordering and copy detection, the serial number can also rearrange data from individual data sources contained in an encoder packet. This serial number can clearly indicate each The order in which packets should be considered. This sequence number can constitute a "FEC header", which can be added to the information payload unit (pDU) and the parity block at the same time after the encoding is performed. The order is 95692. doc -50- 200522578 should not be protected by this external code, because the serial number must be used for decoding. FIG. 14 is a schematic diagram of a specific example of a forward error correction (FEC) header format. To help align the data with the encoder packet (EP), the serial number can be divided to include a reserved portion (R) 402;-the encoder packet (EP) portion 404 to find the EP (EPSN) And an internal encoder packet for finding the location of a special internal block in the encoder packet (IEPSN) 406. We hope that the FEC layer 400 can operate in exchange with all radio link control (RLC) modes. Because both Radio Link Control (RLC) AM and Radio Link Control (RLC) UM require the size of the service data unit (SDU) to be a multiple of 8 bits, we hope that the FEC layer 400 can also support this requirement. Because the outer code of the FEC layer 400 operates in a way of increasing the size of the lean bit group by 70, the encoder packet (EP) column size must also be an integer number of bytes. Therefore, the FEC header size 401 should also be a multiple of 8 bits in order to allow the radio link control (RLC) to accept the feC protocol data unit (PDU) size. In the specific embodiment in which the forward error correction (FEC) header 401 can be a byte, the reserved portion (R) 402 includes a single bit to identify the EP (EPSN) 404. The IEP part includes 3 bits, and the IEP part used to find the position of the PDU in the encoder packet (IEPSN) 406 includes 4 bits. In this specific embodiment, an 8-bit serial number is used because we expect that a pdu will be sent in each TTI and because we do not want the transmission timing of different cells to drift more than 100 ms. The transmission buffer 420 stores these PDUs until a data frame of 95692 is accumulated. doc -51-200522578. When these PDUs are requested, the transmission buffer 42 will transmit the frames to the MAC layer one by one on the radio interface (Uu) through a logical channel. Then, the MAC layer sends the PDUs to the physical layer through a plurality of transmission channels. Finally, the physical layer sends the pDUs to the UE. 10 The receiver continues to examine Figure 11 to receive forward error correction. (FEC) entity 430 includes a receiving buffer / reordering / copy detection unit 438;-a serial number removal unit 436;-an external decoder 434, which can implement Reed-Solomon (RS) decoding; and a reassembly unit / Service Data Unit (SDU) transmission buffer 432. The information column of the EP matrix corresponds to a plurality of Pdu. To support external encoding, the receiving forward error correction (FEC) entity 43 will accumulate several FEC PDUs before triggering external decoding. In order to achieve the purpose of continuous reception, even if multiple encoder packets need to be decoded, the user equipment (UE) will still buffer the incoming protocol data units (pDU) at the same time when decoding is performed. The receive buffer 438 can accumulate a plurality of PDUs until the entire encoder packet (EP) is received or until the scheduling unit (not shown) meets the condition that the encoder packet (EP) will not be transmitted again. Once it is determined that no more data is received from a particular encoder packet, the missing PDU can be considered as deleted data. In other words, a delete symbol can be used in the decoding process to replace a PDU that fails the CRC test. Because some blocks will be lost during transmission, and because different data strings may have different delay relationships, the receive forward error correction (FEC) entity 430 will test the receive buffer / reorder / copy 95692 in Unit 438. The received block of doc -52- 200522578 implements copy detection and reordering can be performed. This sequence can be used in each FEC protocol data unit (PDU) to assist in reordering / copy detection. This serial number can be used in the receive buffer 438 to reorder out-of-order received data. Once the pDUs are reordered, the duplicate detection unit will detect the duplicate PDUs in the encoder packet (E p) based on its serial number and eliminate any duplicate data. These numbers can then be removed. The sequence number removing unit 436 can remove the sequence number from the encoder packet (EP) because the sequence number is not part of a block to be sent to the Reed-Solomon (RS) decoder. The predicate data can then be sent to the external decoding function 434 to restore the missing information. The external decoder 434 receives the encoder packet (Ep) and, if necessary, can also use parity information to regenerate any error or missing columns in order to implement Reed Solomon (RS) on the encoder packet (EP) decoding. For example, if all the k protocol data units (PDUs) containing information are not received correctly, or if less than k of the n PDUs are not received correctly, then the protocol data can be Units (PDUs) implement external decoding (the number of which is up to the size of the equivalent bit PDU) in order to restore the lost information pDU. When external decoding is implemented, 'at least one co-located PDu will be available at the receiver. If all the k protocol data units (pdu) containing information are received correctly, or if less than k of the n PDUs are received correctly, then it is not necessary to implement the solution. These information protocol data units (PDUs) can then be transmitted to the reorganization function 432. Regardless of whether the external decoding is successful or not, the information columns can be transmitted to the reorganization unit / function 432. The recombination unit 432 uses the length indicator (u) 95692. doc -53- 200522578 to reorganize or reconstruct the SDU from the information row of the encoder packet (EP) matrix. Once the SDUs are successfully put together, the service data unit (SDU) transmission buffer 432 will transmit the service data unit (SDU) on the radio bearer 440 to transmit the SDUs to higher layers. . At the receiving forward error correction (FEC) entity 430, allowing the UE to delay decoding with time compensation between different logical strings, the system can fully utilize potentially out-of-order received data because the logical strings do not need to be synchronized. the benefits of. This will make the service smoother during delivery and during the transfer of PTP and PTM. In the following, an algorithm for delaying decoding by the UE with time-stamp compensation between different logical strings will be discussed with reference to FIG. 15. Encoder packet (EP) options: fixed or variable row size. This FEC or external code entity has the flexibility to decide when to construct protocol data units (PDUs), because these protocol data units (PDUs) do not have to be in each transmission time interval ( TTI). This results in better frame filling efficiency and less additional data. When necessary, the external code entity may generate a payload at each transmission time interval (TTI). A protocol data unit (PDU) can be constructed immediately when a service data unit (SDU) is received from a higher layer. If there is not enough data to establish a protocol data unit (PDU), the RLC can add padding information. Fixed Column Size Encoder Packet (EP) When encoding SDU 201-204, we would like to minimize the amount of padding that will be transmitted. In a specific embodiment, the column size of the encoder packet (EP) matrix 205 may be a fixed size. It is known in advance that the columns of the encoder packet (EP) matrix 205 are large 95692. doc -54- 200522578 Small: This information can be aligned with the original configuration. Because the column size of the developed SDU 201-204 is known in advance, the data can be transmitted immediately after receiving the data, without waiting to see how much data will be sent. FIG. 12A is an example of an encoding process used to generate an outer code block 214 from a plurality of data units 201-200. The outer size of the outer code block 214 may be fixed. In this example, the user data is in the form of a plurality of service data units (SDU) 201-204, which contains a bit block of any size. Its size is related to special applications (video, voice, etc.). In order to be able to transmit FECSDUs of any size, segmentation, concatenation, and padding operations can be implemented in the FEC stage. Although the serial connection operation is not absolutely necessary, if it is not performed, the higher-level data processing capacity will be seriously damaged. These higher layer SDUs 201-204 can be formatted to this fixed pDU size first. In this specific embodiment, the split / concatenation function can generate a plurality of internal blocks of a fixed size exclusive to the user unit. At step 22, the group of internal blocks can be divided and connected in series to make it part of an encoder packet matrix 205. The encoder packet matrix 205 contains a plurality of internal blocks; necessary padding information 208 ; And a length indicator (LI) 206, which can indicate the end of these service data units (SDUs) 201-204 by indicating how many SDUs are in a particular column of the EP. The external encoder discussed below will use these internal blocks to generate multiple redundant blocks. In radio link control (RLC), the length indicator (LI) indicates the end of each service data unit (SDU) found in accordance with the protocol data unit (PDU), rather than in accordance with the service data unit (SDU) . This helps reduce additional data because the PDU size is usually smaller than the service data unit (sdu) 95692. doc -55- 200522578. For example, the length indicator (LI) may be used to indicate the last eight bits of each FEC service data unit (SDU) ending in the payload data unit (PDU). The "length indicator" may be set to the number of octets between the end of the FEC header and the last octet of a FEC SDU segment. The length indicator (LI) is preferably included in the PDUs to which the length indicator (LI) refers. In other words, the better length indicator (LI) refers to the same payload data unit (PDU), and the better system has the same order as the FEC SDU to which the length indicator (LI) refers. When the external block is received, information (such as the length indicator (LI)) can be used to let the broken receiver know the start and end positions of the service data unit (SDU) and / or padding information. Because it is not possible to use a bit in the FEC header to indicate the presence of a length indicator (LI), the FEC layer will add a fixed header to the payload to indicate that there are multiple length indicators (LI) presence. The internal header or LI will provide all the information needed to rebuild these SDUs 201-204. LI may be included in the RLC-PDU to which it refers. The flag included in the serial number header of the RLC-PDU can be used to indicate the existence of the first LI. One bit in each LI can be used to indicate its extension. In order to allow the length of the length indicator (LI) to change with the size of the FEC PDU, a new special value can be introduced for the length indicator (LI) of the one-tuple, which represents the length of one of the The previous SDU at the end, unless the last PDU is filled. Such length indicator (LI) presence bits can be implemented in various ways, two of which are discussed below. In one specific embodiment, it can be in each protocol data unit (PDU) 95692. A length indicator (LI) presence bit is provided in doc -56- 200522578. For example, a byte can be added at the beginning of each encoder packet (EP) column, and a bit in the byte can indicate that the LI exists. The entire first byte of each protocol data unit (PDU) is reserved for this "presence bit". To accommodate this presence bit, the length indicator data can be shortened by one bit. By providing a presence bit in each protocol data unit (PDU), the SDU can still be decoded when the EP decoding fails, even if the first PDU is missing. This can lead to lower residual error rates. Providing a presence bit in each PDU also allows for instant concatenation / splitting operations. In another embodiment, a length indicator (LI) presence bit may be provided in the first PDU. In the specific embodiment, the additional data is not added at the beginning of each PDU. Instead, the existence bits of all k information PDUs can be added at the beginning of the first PDU of the EP. When there are large SDUs and / or small PDUs, providing this presence bit at the beginning of the encoder packet (EP) can result in less additional data. After segmentation and concatenation, a number of rows in EP 205 will be occupied by at least one of the plurality of service data units (SDUs) 201-204 and padding blocks. The column size of an external block can be designed to be transmitted at a peak data rate during a transmission time interval (TTI). The service data unit (SDU) is usually not aligned with the amount of data sent during a transmission time interval (TTI). Therefore, as shown in FIG. 11, the second and fourth SDUs 202 and 204 cannot be placed in the transmission time interval (TTI) of the first and second columns of the EP. In this example, the EP has 12 rows for data use, and the four SDUs 201-204 can be packed in the first three rows of the 12 rows. The EP 205 of 95692. The remaining columns of doc -57- 200522578 will be occupied by padding block 208. Therefore, the second SDu 202 can be divided, so that the first part of the second service data unit (SDU) 202 starts in the first column of the "information block", and the second part of the second SDU2002 The serving ends in the second column. Likewise, the third SDU must be split such that the first part of the third service data unit (SDU) 203 starts in the second column and the second part of the third 203 ends in the third column. The fourth service data unit (sdu) 204 can be placed in the third column, and the padding block 208 can be used to fill the rest of the third column. In this example, most of the encoder packet (Ep) 213 is composed of padding information 208. The encoder uses the EP to generate redundant or parity information. At step 24o, an encoder encodes the encoded intermediate packet matrix 205 by adding a plurality of outer parity blocks 214 to generate an outer code block 213 with a length of j 6 blocks. The encoder takes 8 bits of data from each row of each block to generate the final data 21o. A Reed-Solomon (rs) encoder can encode this last data 210 to obtain four rows of redundant or parity information 212. The parity information 212 can be used to generate a plurality of external parity blocks 214, and these blocks can be appended to the ep matrix 205 to generate 16-block external code blocks 2 1 3. Figure 12B is an example of information transmitted over the air in the example discussed above. In step 260, after adding additional additional data with a serial number to each column of EP 205, a plurality of protocol data units (PDu) 2 and 14 can be used to transmit the 16-block external code block 2 丨 3 in the air. . All or the entire Encoder Packet (EP) 213 will not be transmitted in the Protocol Data Units (PDu) 2 14 sent in the downlink. Rather, the agreement information sheet 95692. The doc -58- 200522578 element (PDU) contains the information bits 201 -204 of the encoder packet (EP) 213 and the length indicator (LI) 206. Because the encoder packet (^! ≫) 213 column size is fixed and the receiver knows the size value, it is not necessary to actually transmit the padding information 208 over the air. Because the padding values are known, the padding information 208 is not required to be transmitted, so the padding information 208 is not transmitted on the downlink connection. For example, if a known bit sequence (such as all 0s, all 1s, or an interlaced pattern of 0s and 丨 s) can be used to form the fill-in poor signal, the receiver can then The agreement data sheet s (pDu) 2i4 is padded to the length of the nominal encoder packet (ep) 213 rows. Therefore, during transmission, the ^ PDU size is not selected to be equal to the EP column size. Instead, the smallest available EP size that carries all the information bits 20 丨 _204 and the restructured additional data (u) 206 is used. Although the size of the encoder matrix row is fixed, the size of the FEC pDU can be selected from a given set in each transmission, so that each can include all the information part of an encoder matrix row (filling information Excluded). When receiving a pDu that is smaller than the size of the encoder matrix column, ue can fill the size of the encoder matrix column with a known bit sequence. This maintains a fixed internal block size without increasing the load on the air interface. Therefore, using a fixed column size encoder packet (EP) 213, there is no need to wait to receive all the data before starting to transmit the protocol data unit (PDU), and it is not necessary to send padding information. If the above algorithm is designed to handle variable rate transmission, then = 2 rate equalization architecture is used, in which all the encoder packet matrix columns are /, 疋 is large. § 95692 can be used when filling the information component PDU. doc 200522578 Small PDU. The padding information may be composed of a specific bit sequence, and may be located at each end position of the data. At the receiver, the size of the blocks received from the lower layer can be equalized to the baseline size by adding padding information at the end position. ; If the preset bit sequence can be used as the padding information, this padding information will not be transmitted over the air. Unless the receiver needs to perform external decoding, the receiver does not need to know the actual encoder packet column size. Basic SDy reorganization does not need to know the number of padding information at the end of the first position. 1 ° If all PDUs with _ information from the previous k column encoder packet (Ep) column have been received, then no external implementation is necessary. decoding. Conversely, if at least one PD ^ containing information from the previous k-th column of Encoder Packet (EP) columns is missing, then at least one of the PDUs including the name derived from the co-located data will be required. Since the parity column is usually not padded ', its size can be used as a hypothetical reference value for the actual encoder packet size. Variable column size encoder packet (Ep) FIG. 13 is an encoding process for generating an outer code block 3i3 with a variable column size. This point of view this month is about flexible external block coding of data transmitted over the air interface. This encoding process only transmits a small amount of padding information, so the frame filling efficiency will be improved. These encoder packet (EP) 305 columns are OK. The size of the interleaving is different, and external blocks of different sizes can be sent for each transmission time interval (TTI). A better system, encoder packet (EP) 305.  The column size can be changed so that these SDUs can be reliably placed in the encoder packet 95692. doc -60- 200522578 (EP) Among the number of columns (for example, 12 columns) of matrix 305. In this specific embodiment, the FEC layer must wait until all data is available before constructing the EP. Therefore, the FEC layer can determine the optimal column size. The row size can be selected from several different sizes based on the amount of available data in order to limit padding information. The column size of this encoder packet (Ep) may be linked to the PDU size set configured for S-CCPCH. Depending on the amount of data available when the encoder packet 305 is generated, a row size can be selected that will result in least padding. Reduce the size of the external block 313 so that the block size in each frame becomes smaller, then data can be sent at a lower transmission rate 'because less data has been sent in the same TTI duration. Utilizing the variable column size of the encoder packet (EP) 305 helps to stabilize the power requirements in the overall transmission of the encoder packet (EP) and also allows for less parity additional information 314. This specific embodiment is applicable to point-to-multipoint (PTM) transmission in a WcDma system, and the basic wireless protocol in the system allows different sizes of transmission blocks to be transmitted in each transmission time interval (TTI). In step 320, a plurality of service data units (SDUs) 201-204 may be divided and connected to generate an encoder packet (Ep) matrix 305, where the length indicator (U) 206 may be used to refer to these End position of Service Information Unit (SDU) 201-204. The length indicator (LI) may be included in the last column of each service unit (SDU) terminated. In step 330, 8-bit data can be taken from each data block, and redundant or parity information can be generated on the basis of the row, and the final data 31 can be sent to a Reed_Solomon (RS) encoder. To get parity information 312. Because the encoder packet (EP) matrix 305 has fewer columns, it can produce more than 95692. doc -61-200522578 less redundant information. The encoding will continue in step 340, because the parity information 312 will be used to generate a plurality of external parity blocks 3 14. These external parity blocks 3 14 can be appended to the encoder packet (Ep) of the twelve blocks. In matrix 305, an external code block with a length of 16 blocks is generated in this example. This specific embodiment can avoid the transmission of padding information, thereby improving the transmission efficiency, because the entire outer code block 313 is occupied by 8011, the length indicator (1 ^ 1) 206, and / or the redundant information 314. In this particular example, no padding information is needed. However, it should be understood that in some cases, because the number of configuration sizes of the PDU will be limited, some padding information may be required, but the amount of padding information is quite small. This results in greater frame filling efficiency and maintains a more constant power throughout the encoder packet (Ep). This is a welcome feature of CDMA systems using power control architectures. Although not shown in the figure, the manner of transmitting PDUs over the air is the same as that discussed above with reference to step 260 of FIG. FIG. 11 is a specific embodiment of an external coding or forward error correction (FEC) layer 400 above the radio link control (RLC) layer, which has a _RLC unacknowledged mode (UM) + entity (RLCUM +). Generally, Radio Link Control (RLC) provides framed processing for higher layers. Here, the frame processing is performed by the FEC layer located above the radio link control (RLC). The external coding layer 400 includes a transmission forward error correction (FEC) entity 410, which can transmit through a plurality of logical channels 406 on a radio interface (Uu) 404 and a reception forward error correction (FEC) entity 430. For communication. 95692. doc -62- 200522578 Reordering / Copy Detection Figure 15 is a schematic diagram of a reordering protocol or algorithm that allows the mobile station 10 to use time compensation between different logical strings to delay decoding. The receiving forward error correction (FEC) entity 430 uses the sequence number to determine the position of a particular PDU within the EP matrix. For example, a partial sequence number (PSN) can identify the position of the PDU in the encoder packet (EP). This algorithm assumes that data from at most two encoder packets (EP) will be received before decoding can begin. In the following description, the encoder packet (EPd) is the next encoder packet (EP) to be decoded in sequence, and the encoder packet (EPb) is the encoder packet (EP) being buffered. The encoder packet (EPb) follows the encoder packet (EPd). A UE design that requires full encoder packet transmission time to implement RS decoding will need to implement double buffering in order to be able to decode multiple consecutive packets. Therefore, the UE stores at least n + k columns in the largest column of the encoder matrix, where k and η are the number of information columns and the total number of columns including parity information, respectively. UEs with faster decoding engines can reduce this requirement, however, it cannot be lower than n + 1. For example, if the specific buffer space (XtraBffr) of the UE exceeds the number required to receive consecutive packets based on its decoding capability, and if a 64k bps data string is assumed, then the decoding is delayed by 100 ms without If you increase the computational requirements, you need to increase the buffer size of 800 bytes. At step 1410, it is determined whether a new forward error correction (FEC) protocol data unit (PDU) is received. If a new forward error correction (FEC) protocol data unit (PDU) is not received, the process will restart at step 1410. If a new forward error correction (FEC) agreement is received 95692. doc -63- 200522578 unit (PDU), then it will be judged at step 1420 whether the new forward error correction (FEC) protocol data unit (pDU) belongs to the next encoder packet to be decoded in order. (EPd). If the forward error correction (FEC) protocol data unit (PDU) does not belong to the next encoder packet (EP) to be decoded in sequence, then the forward error correction (FEC) is determined at step 1421. ) Whether the protocol data unit (PDU) belongs to the encoder packet (Epb) to be buffered. If the forward error correction (FEC) protocol data unit (pdu) does not belong to the encoder packet (EPb) to be buffered, the protocol data unit (PDU) is discarded at step 1440.荄 If the forward error correction (FEC) protocol data unit (PDU) belongs to an encoder packet (EPb) to be buffered, then at step 1423, the protocol data unit (PDU) will be added in the relevant position. Into EPb's buffer. At step 1425, it is judged whether the data amount of EPb exceeds XtraBffr. If it is determined at step 1426 that the data amount of EPb does not exceed XtraBffr, the program will restart at step 1410. If the amount of EPb data exceeds XtraBffr, then at step 1428, the transmitting entity will attempt to transmit the complete SDU from the EPd. Then at step 1430, the remaining EPd can be forcibly evicted from the buffer, and EPb is set to EPd at step 1434. If it is determined at step 1420 that the forward error correction (FEC) protocol data unit (PDU) belongs to EPd, then at step 422, the protocol data unit (PDU) can be added to the EPd in the relevant position. In the buffer. At block 1424, it can be determined whether the buffer has k individual PDUs of EPd. If the buffer does not have k individual PDUs for EPd, then 95692. doc -64 · 200522578 At step 1426, the program will restart at step 1410. If the buffer has k individual PDUs of EPd, then at step 1427, the decoder will perform external decoding for EPd, and then at step 1428, the transmitting entity will attempt to transmit a complete SDU from the EPd. Then at step 1430, the remaining EPd can be forcibly evicted from the buffer, and EPb is set to EPd at step 1434. Figure 16 shows the external code area received by a mobile station when it moves between receiving a point-to-multipoint (PTM) transmission from cell A 99 and receiving a point-to-multipoint (PTM) transmission from cell B 99. Diagram of time between blocks. Griin et al., US Patent Applications Nos. US-2004-0037245-A and US-2004-0037246-A1, filed on August 21, 2002, and Willeneggei: et al. A partial discussion of FIG. 16 is further discussed in US Patent Application No. US-2003-0207696-A1, which is incorporated herein by reference in its entirety. The situation in the figure assumes specific UMTS Terrestrial Radio Access Network (UTRAN) 20 and User Equipment (UE) 10 regulations. For example, if UTRAN 20 uses the same external block code to send content in multiple cells, the blocks carrying the same data or payload in adjacent cells should use the same number. Very accurate time calibration must be performed when transmitting external blocks of the same number. The maximum alignment deviation for PTM transmissions across these cells is controlled by the Radio Network Controller (RNC) 24. UTRAN 20 controls the delay jitter at point-to-multipoint (PTM) across cells. The UE 10 should be able to decode an external block at the same time when receiving the next external block. Therefore, the better buffer space in the UE should be 95692. doc -65- 200522578 can hold at least two external blocks 95 A-95C, because one external block of memory is needed to accumulate the current external block. If there are such external blocks during the Reed-Solomon decoding, the memory should also be able to accumulate internal blocks of the "plural sequence" and compensate for inaccuracies in the time alignment across the multiple base stations 22. In cell A 98, during the transmission of the external block η 95A, the transfer occurs during the transmission of the second internal multimedia broadcast and multicast service (MBMS) payload block. The slope of arrow 96 (which is illustrated by the user equipment (UE) transition from cell A 98 to cell b 99) is non-horizontal because some time will elapse during the migration. The fifth block of multimedia broadcast and multicast service (MBMS) payload data was being transmitted just before the read user equipment (UE) 10 arrived at cell 3 99. In this regard, the user equipment (UE) 10 will lose the second to fourth blocks due to the time alignment deviation of the individual transmissions and the relationship of time lapse during the transfer. If enough blocks are received in cell B 99, then the external block η 95A does not need to be decoded, because the parity blocks can be used to reconstruct the lost blocks. After the term 'During the transmission of external block n + 2 95C, the user equipment (UE) 10 will undergo another transfer from cell B 99 to cell A 98. This transfer occurred in external block n + 2 95C's fifth internal multimedia broadcast and multicast service (MBMS) payload block. In this case, fewer internal blocks will be lost during the transfer, and these external blocks can still be restored. Using external code blocks can help reduce the possibility of any service interruption. To ensure error recovery, the same blocks should be sent on the same transmission path, which means that the same 95692 should be used in each transmission path. doc -66- 200522578 to construct this parity block. (Because it is a broadcast transmission, the multimedia broadcast and multicast service (Ms) in each path) The payload block must be the same. ) The implementation of forward error correction (fec) at the upper application layer 80 helps to ensure that the parity zone in the material transmission path is the same, because the encoding is performed in the forward error correction (FEC) layer 157 Therefore, the encoding method of each external block is the same. Conversely, if encoding is performed in a lower layer (for example, an individual Radio Link Control (RLC) entity 152), then a specific coordination operation must be performed, because each transmission path claims the equivalent bit block Not the same. Point-to-multipoint (PTM) transfer to point-to-point (ρτρ) Figure 17 shows the external code area received when a mobile station 10 moves between point-to-multipoint (ρτΜ) transmission and point-to-point (PTP) transmission. Diagram of time between blocks. For example, the architecture shown in FIG. 17 can be applied to systems using point-to-point (ρτρ) transmissions, such as WCDMA and GSM systems. One aspect of the present invention relates to forward error correction by adding parity information or blocks to internal "payload" or data blocks during PTM transmission. Each external code block transmitted in a PTM transmission includes at least one internal payload block and at least one internal parity block. The error correction capability of the external code block can be transferred (for example, when the UE is moved from one cell to another; or in the same service cell, the content transmission is changed from PTM connection to PTP connection, or vice versa (Change) period is greatly reduced and tends to be free of any MBMS content or "payload". As mentioned above, a specific cell can be transmitted to a subscriber station 10 using a PTP or PTM transmission architecture. For example, a normal transmission in a PTM transmission mode 95692. doc -67- 200522578 The cell broadcasting service can choose to establish a dedicated channel when the demand for the cell is below a certain threshold and transmit it in PTP mode (only transmitted to a specific user station 10) . Similarly, cells transmitting content to individual subscriber stations on a dedicated channel (PTP) can also decide to broadcast the inner valley to multiple users on a common channel. In addition, a specific cell can transmit content in a PTP transmission mode, while another cell can transmit the same content in a PTM transmission mode. Migration occurs when the mobile station 10 moves from one cell to another or the number of users in a cell changes to cause the transmission architecture to change from FT? To PTM or vice versa. During the point-to-multipoint (PTM) transmission in the external area 埤 95A, the transfer occurs during the transmission of the fourth internal multimedia broadcast and multicast service (MBMS) payload block. The slope of arrow 101 (which is illustrated by the user equipment (ue) transitioning from point-to-multipoint (PTM) transmission to point-to-point (ρτρ) transmission) is non-horizontal because some time will elapse during the migration. When migrating from PTM 101 to ptp, it will maintain approximately the same bit rate in the air. The bit error rate for point-to-point (ρτρ) transfers is usually less than one percent (for example, during transmission, there will be only one or less errors per 100 payload blocks). Conversely, bit-to-multipoint (PTM) transmissions may have higher bit error rates. For example, prior to one of the specific embodiments, the base station generates an external block every 16 transmission time zones / (ττι), and twelve m of it will be occupied by the payload block and four TTI will be Occupied by co-located blocks. The maximum tolerable and block error number should be 4/16 internal blocks of 12 (12 basic blocks + 4 parity blocks). In this regard, the maximum tolerable block error rate is " 4. When the mobile station transitioned from point-to-multipoint (PTM) transmission to point-to-point 95692. doc -68- 200522578 (PTP) transmission, some internal blocks may be lost. Assuming point-to-multipoint (PTM) transmission and point-to-point (ρτρ) transmission at the physical layer, have approximately the same bit rate of 7L, then 'ρτρ transmission will allow the rate at which these payload blocks are sent. On average, the percentage of retransmitted blocks is usually lower than the percentage of co-located blocks. In other words, point-to-point (PTP) transmission is usually much faster than point-to-multipoint (PTM) transmission, because statistically, the number of co-located blocks is much larger than the number of radio link control (RLC) transmissions (Re-Tx). Because moving from point-to-multipoint (PTM) transmission to 101 to point-to-point (ptp) transmission is usually very fast, when the user equipment (ue)] 0 to 101-to-point (PTP) transmission, it will be transmitting The first block of multimedia broadcast and multicast service (MBMS) payload information. In this regard, the time alignment deviation of individual transmissions and the time lapse during the transfer 101 will not cause any block loss. Therefore, when moving from a point-to-multipoint (PTM) transmission to a point-to-point (PTP) transmission, once After the pTp link is established on the target cell, the lost payload block can be constructed by simply restarting from the beginning of the current external block. The network can be compensated by starting a PTP transmission from the beginning of the same external block (that is, using the first internal block). The network can then restore the delay caused by the transfer due to the faster transfer of complete external blocks. Reducing the loss of data during the migration can reduce the interruption of MBMS content transmission due to these migrations. Later, during the PTP transmission of the external block η + 2, the user equipment (UE) 10 is in the process of transferring to another point-to-multipoint (PTM) transmission mode 103. In Figure 12, the transfer from point-to-point (PTP) transmission 103 to point-to-multipoint (PTM) transmission takes place in the last internal multimedia of external block η + 2 -69- 95692. doc 200522578 Broadcast and Multicast Service (MBMS) Payload Division. In this case, in the external block n + 2, except for the last internal block, most of the internal multimedia broadcast and multicast service (MBMS) payload blocks have been transmitted. FEC is often used in situations where feedback cannot be used. Because ρτρ transmission will use a dedicated channel with a feedback function on the reverse link, there is no benefit in using FEC. In order to minimize or eliminate data loss during interleaved transfers, the UMTS Terrestrial Radio Access Network (UTRAN) 20 better depends on the low residual block error rate of the RLC acknowledged mode (AM) in ρτρ transmission, Used to restore all internal blocks that may be lost during migration to PTM transmission. In other words, normal Layer 2 retransmissions can be used to retransmit any packets that had detected errors in the original transmission. Therefore, as shown in Fig. 17, no co-located block is required in ρτρ transmission. However, if an error occurs in these payload blocks during a point-to-point (PTP) transmission, the external block will still be decoded because the radio link control (RLC) layer will require any error blocks to be transmitted again = That is, when an error occurs during ρτρ transmission, the mobile station 10 may request re-transmission (re-Tx); or when all blocks are correct, no re-transmission will be performed and transmission can be used Format zero (TF0). External coding: It is better to complete in layer 2 of the M stack, so that the size of each internal block 97 can be reliably placed in the special input time interval (ΤΤΙ), because this makes the moonlight upward coding effectiveness. If forward error correction (FEC) external coding is done in the upper layer (such as application layer) of the protocol stack, then no matter what kind of transmission (point-to-point (PTP) or point-to-multipoint (PTM)), The parity block 1 will be sent. Therefore, the parity block will also be attached to the point-to-point (ρτρ) pass. 95692. doc -70- 200522578 As mentioned above, it is not necessary to use parity blocks in PTP transmission because a more efficient retransmission architecture can be used instead of forward error correction. Because it is advisable not to transmit co-located blocks during PTP transmission, if it is assumed that the bit rate in the air is the same, then transmitting a complete external block will on average be faster than PTM. In this way, the UE can compensate for the interruption caused by the point-to-multipoint (PTM) migration to the point-to-point (PTP), because the ρΤρ transmission may lead the PTM transmission. The user equipment (UE) can correctly restore the external block by the following data: (1) the internal block received in the point-to-point (PTP) transmission, received in a new cell or after the transfer The internal blocks received are (2) the internal blocks received in the point-to-multipoint (PTM) transmission, and the internal blocks received in the old cell or before the transfer. The user equipment (UE) can combine the internal blocks received before the transfer and the internal blocks received after the transfer, which belong to the same external block. For example, the user equipment (UE) 10 may combine the internal multimedia broadcast and multicast service (MBMS) payload block in the external block η + 2 received through point-to-point (PTP) transmission and through point-to-multiple The internal multimedia broadcast and multicast service (MBMS) payload block and co-located block in the external block η + 2 received by the point (PTM) transmission. The UMTS Terrestrial Radio Access Network (UTRAN) 20 can assist this method with external block transfers that are intended to be sent to all users who receive MBMS content from the PTP link to "lead" over the ptm link. Because this UTRAN can lead PTM transmission for external block transmission, it can achieve the "seamless" transfer result from PTP to PTM. Therefore, transmitting MBMS content across cell boundaries and / or between different transport architectures (such as PTM and PTP) can be "seamless." This `` time lead '' can be expressed as 95692. doc -71-200522578 The number of internal blocks. When the user equipment (UE) 10 is transferred to PTM transmission, 'even if no communication link exists during the transfer, the user equipment (UE) 10 may still lose up to the "time lead" number of internal areas Block, but it does not impair the QoS of MBMS reception. If the UE starts MBMS reception directly in PTP, the UTRAN can immediately apply the "time lead" when PTP transmission is started, because UTRAN 20 can slow down by avoiding empty internal blocks (TF 0). Slowly lead the transfer of external blocks until you reach the necessary number of internal blocks of "time lead". Since

From the beginning, UTRAN can maintain a fixed "time lead in point-to-many beer (PTM) and cannot rely on UE-specific feedback information available in radio link control (RLC). In point-to-point (ρτρ) transmission, this ue ι〇

The RNC may be notified so that it knows the number of the last external block that was correctly received before the transfer. This should be applied to any transfer that becomes ρτρ (from PTM or 疋 from PTP to Pτρ). If this feedback is considered unacceptable, UTRAN 20 can predict the last external block most likely to be received by the user equipment (UE) 10 before the state shift #. This prediction operation can be implemented based on the maximum time inaccuracies that can be predicted between different transmissions and the external block in the target cell that is currently being transmitted or will be transmitted. / To implement forward error correction (FEC) in order to restore any blocks lost during the transfer. Reducing the likelihood that content will be lost during the transition and enabling seamless migration. " This architecture assumes that when transferring from point-to-point (㈣) to point-to-point (PTM) transmission, the same external source is transmitted from each data source to an external Kun Ghost whose book system takes place in an external block with respect to the duration of the transfer. Time is known. Second Note, Day 1 95692.doc -72- 200522578 The amount of memory in UE 10 will involve the time alignment accuracy of PTM transmissions across neighboring cells. Relaxing the memory requirements in the user equipment (UE) 10 can improve the time accuracy of PTM UTRAN 20 transmissions. Figure 18 shows a mobile station moving or relocating between point-to-point (PTP) transmissions originating from Radio Network Controller (RNC) A and point-to-point (PTP) transmissions originating from Radio Network Controller (RNC) B The time relationship diagram between the received external code blocks. RNC—The word is interchangeable with "base station controller (BSC)". During the "relocation", the user equipment (UE) 10 will transfer from a point-to-point (PTP) transmission of a content string in the area controlled by the first RNC A 124 to the area controlled by the second RNC B 224 Point-to-point (PTP) transmission of the same content string in. Re-transmission (re-Tx) can be used to compensate for any lost MBMS payload blocks. The direct transfer from point-to-point (PTP) transmission to point-to-multipoint (PTM) transmission between cells can be implemented in the same way as Release '99 soft or hard delivery. Even if there is no coordination between the two RNCs A and B, the target RNC A 124 should still be able to calculate the last complete external block received by the UE 10. This prediction can be implemented based on the timing of MBMS content received by the RNC 124 on the Iu interface 25. When using PTP transmission, the RNC 124 can constitute the initial delay, and no part of the MBMS content will be lost even if no missing SRNS relocation is needed. Those skilled in the art will find that although the flowcharts shown in the figure are drawn in order for easy understanding, in a real implementation, specific steps can be performed at the same time. Moreover, unless specifically stated otherwise, method steps may be interchanged with one another without departing from the scope of the invention. Those skilled in the art should understand that any of the different technologies and techniques can be used to represent 95692.doc -73- 200522578 to represent Bei Xun and #bluff. For example, the information, instructions, commands, Besson, signals, bits, symbols, and chips that may be mentioned in the above description can use voltage, packet current, electromagnetic waves, magnetic fields or magnetic particles, light fields or magnetic particles, or any other Combined representation. Those skilled in the art should better understand the various explanatory logic blocks, modules, circuits, and algorithm steps described in the specific embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. achieve. To clearly illustrate this interoperability of hardware and software, the above generally describes various illustrative components, blocks, modules, circuits, and steps in terms of their functionality. Whether such functions are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art can use various methods to implement the functions described for each particular application, but the decision of such a current-only method should not be interpreted as causing a departure from the scope of the present invention. In combination with the various illustrative logical blocks, modules, and circuits described in the specific embodiments disclosed herein, a general-purpose processor, a digital signal processor (DSP), a special application integrated circuit (ASIC), a field A programmable gate array (FPGA) or other programmable logic device, discrete gate or electrical logic, discrete hardware components, or any combination of functions designed to perform the functions described herein are implemented or performed. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of multiple private devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, more than one microprocessor with a DSP core, or 95692.doc 200522578 Any other such configuration. The specific practices disclosed in this article are described in the following examples, steps, methods, or algorithms, which can be implemented in the following ways: directly using software modules that use hardware and are executed by processors. , Or a combination of both. The number ^ software board can reside in RAM memory, flash memory, ROM but 愔 舻 gt > τ ^

° Hidden body, EPROM memory, EEPR0M memory, scratchpad, hard disk, extractable disk ★ Removable disk, CD-ROM, or any of its reading and storage towels known in the art. The μ material can be integrated into the processing & so that the judgment can read the information from the storage medium or write the information to the storage medium. In the alternative, the storage medium may be integrated with the test device. The processor and the storage medium may reside in an ASIC. The ASIC can reside in a __ user terminal. In the alternative, the processor and the storage medium may be stored in a user terminal in the form of separate components. The previous description of these disclosed specific embodiments is for anyone skilled in the art to make or use the invention. Those skilled in the art will appreciate various modifications to these specific embodiments, and the general principles defined herein may also be applied to other specific embodiments without departing from the spirit or scope of the invention. For example, although it is stipulated in the Ming Dynasty that the universal terrestrial radio access network (UTRAN) air interface can be used to implement the radio access network 20, the radio access network 20 may be a A GSM / EDGE radio access network (GERAN), even in the case of inter-systems, 'may include cells of the UTRAN air interface and cells of the GSM / EDGE air interface. Therefore, the present invention is not intended to be limited to the specific embodiments shown herein, but rather, it is intended to conform to the widest category consistent with the principles and novel features disclosed in this 95692.doc -75- 200522578 article. Part of this patent document discloses that it contains copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent file or the disclosure of this patent in a patent file or record, but reserves all copyright rights. [Schematic description] Figure 1 is a schematic diagram of a communication system. Figure 2 is a block diagram of a UMTS signaling protocol stack. FIG. 3 is a block diagram of a user plane for packet switching in a UMTS protocol stack. FIG. 4 is a block diagram of an access hierarchy portion of a UMIS signaling protocol stack. Figure 5A is a block diagram of the data transmission mode used in the radio link control call stack of the UMTS signaling protocol stack and the various channels used in each layer. FIG. 5B is a block diagram of an architecture of a radio link control (RLC) layer including various RLC data transmission modes. FIG. 5C is a block diagram of an entity for implementing a radio link control (rlc) confirmed mode (A%). Figure 6 is a schematic diagram of a simplified protocol stack with a directional error correction layer. Fig. 7A is a specific embodiment of a structure of an access hierarchy including a forward error correction (fec) layer. Fig. 7B is another specific embodiment of the structure of the access hierarchy including a forward error correction (fec) layer. Figure 8 shows the intent of the capital block and the external code block corresponding to the information block. 95692.doc -76- 200522578 FIG. 9A is a schematic diagram of an external code block structure applicable to multimedia broadcast and multicast service (mbms) data. Fig. 9B is a schematic diagram of the outer code block structure of Fig. 9A, in which multiple columns are transmitted in each transmission time interval (TTI). Figure 9C is a schematic diagram of the external block structure of Figure 9A, where each column is sent in multiple TTIs. 10A and 10B are schematic diagrams of external code blocks generated by the forward error correction layer. FIG. 11 is a specific embodiment of a forward error correction (FEC) layer used in the RLC-UM + entity. Fig. 12A is an encoding process for generating an external code block from a plurality of data units, wherein the column size of the external code block is relatively large. FIG. 12B is an example of the information transmitted over the air in FIG. 12A. Fig. 13 is an encoding process for generating an outer code block having a variable column size. 14 is a schematic diagram of a specific example of a forward-error-error correction (fec) header format. FIG. 15 is a schematic diagram for a mobile station to delay decoding by using time compensation between different logics. Figure 16 shows when a certain action, σk ,,, and T cell A receive a point-to-multipoint (ρτM) transmission and receive from cell B_ 科 # 一 * Receiving point-to-multipoint (PTM) transmission Time relationship diagram between external code blocks received by the mobile station. FIG. 17 is a time relationship diagram between external code blocks received when a mobile station moves between point-to-multipoint (PTM) rounds and point-to-point 95692.doc -77- 200522578 (PTP) transmissions. Figure 18 shows when a mobile station transfers or re-routes between point-to-point (PTP) transmissions originating from Radio Network Controller (RNC) A and point-to-point (PTP) transmissions originating from Radio Network Controller (RNC) B. Time relationship diagram between external code blocks received during positioning. [Description of main component symbols]

10 User equipment 12 Mobile equipment 14. Universal subscriber identity module 20 Access network 22 Base station 23 Iub interface 24 Radio network controller 25 Iu interface 26 Uu interface 30 Core network 32 Home location register 34 Mobile switching service Center / Visitor Location Register 36 Gateway Action Switching Center 38 Service General Packet Radio Service Support Node 39 Lower Packet Agreement 40 Gateway GPRS Support Node 42 (Figure 1) PSTN / ISDN 95692.doc -78- 200522578 42 (Figure 3) Remote user 44 Internet 80 Application layer 90 Packet data protocol layer 91 Information block 93 Parity block 94 Header 95 External code block 96 Transfer 97 One transfer 98 Cell A 99 Cell B 110 UMTS signaling protocol Stack 120 physical layer 124 radio network controller A 130 layer 2 140 media access control layer 150 radio link control layer 152 radio link control unit 152A transmitting TM entity 152B receiving TM entity 152C transmitting UM entity 152D receiving UM entity 152E AM entity 95692 .doc -79- 200522578 156 Packet data convergence protocol layer 157 Forward error correction (FEC) layer 158 broadcast / multicast control layer 160 radio resource control layer 161 control plane signaling 163 user plane information 170 circuit switching part 172 connection management layer 174 call control sublayer 176 __ supplementary service sublayer 177 SMS service sublayer 178 Mobility management layer 180 Packet switching part 182 Conversation management sublayer 183 SMS service sublayer 184 GPRS mobility management sublayer 201 data unit 202 data unit 203 data unit 204 data unit 205 encoder packet matrix 206 length indicator 208 padding Data 210 Yuan data 95692.doc -80- 200522578 212 Parity information 213 External code block 214 External parity block 224 Radio network controller B 305 Encoder packet matrix 310 Last data 311 (undefined) 312 Parity information 313 External Code block 314 _ Parity additional information 400 Forward error correction layer 401 Forward error correction header size 402 Radio bearer 404 Encoder packet part 406 Encoder packet 408 (undefined) 410 Transmission forward error correction entity 412 Service Information Unit Buffer 41 4 Division and concatenation unit 416 External encoder 418 Serial number generator 420 Transmission buffer 422 Scheduling unit 430 Receive forward error correction entity 95692.doc -81-200522578 432 434 436 438 440 510 520 530 538 Reorganization unit / service Data unit transmission buffer external decoder serial number removal unit receiving buffer / reordering / copy detection unit radio bearer transmitting end transmitting buffer receiving end receiving buffer 95692.doc -82-

Claims (1)

200522578 10. Scope of patent application: External code above 1 · A radio link control (RLC) layer 'which includes: a destination station containing a receiver; and-a source station containing-a transmitter, which can be transmitted through A common logic communicates with the receiver on the radio interface. 2. The external encoding entity as claimed in claim 1, wherein the transmitter includes: a first buffer for storing a plurality of user information; a scheduling unit, which can complete the following tasks: double input one external if needed A maximum duration is determined before the code block, and the optimal information block size that allows the user information rows to occupy the information blocks is determined according to the amount of user information stored in the first buffer, so as to reduce The unfilled information block portion, and a request is generated to start encoding the user information rows; a segmentation and concatenation unit that can respond to the request from the scheduling unit to segment the user information Row, used to place it into an information block with the best size, and a plurality of length fingers are used in each information block to indicate the user information row relative to the information block. End position; and an external encoder, which can use the information blocks to generate a plurality of redundant blocks, the redundant blocks will be added to the information blocks to generate an external block Ministry block. 3 _If the external encoding entity of item 2, in which when the amount of user plane information is accumulated, the scheduling unit will start encoding. 95692.doc 200522578 4. 5. 6 · 7. 8. 9. 10 If the external encoding layer of claim 2 ′ is used, when the packet transmission delay time is exceeded, the scheduling unit will start encoding. For example, the external encoding entity of claim 2, wherein the transmitter further includes: a sequence of benefits, which will add a header outside each information block, where the header contains a serial number 'used to identify each The order in which the information blocks are set. If the external encoding entity of item 5 is specified, the serial number includes a part identifying the outer 4 horse block and a part identifying the position of each information block in the external code block. If an external encoding entity is required, the transmitter further includes: a transmission buffer H, which stores data blocks, and transmits the information areas on the radio interface through a channel. The block is transmitted to a MAC layer. For example, the external encoding entity of claim 5, which contains the information block of the user information from the k-th string of the first information source and the same user of the second logical string from the first source The information block of the information has the same serial number, and /, the middle 4th row unit will monitor the serial number of the first logical string information block = and " The logical string information block is time-aligned with the second logical string information block. Results so that the first and second logic strings can be time aligned. For example, if the external encoding entity of item 2 is required, the column size of these user information columns can be changed according to the application. If the external encoding entity of claim 2, the scheduling unit will determine the column size of the external 95692.doc 200522578 code block. The column size is fixed, so that the peak data rate can be used during a transmission time interval (TTI). To transmit each row, and before transmitting all the user information, the information block and length indicator can be transmitted. 11. If the external encoding entity of claim 10, wherein the segmentation and concatenation will divide the user information row 'place it into a fixed size external code block row' place the user information row These external code block rows are used to generate a plurality of information blocks, and padding information is used to fill any unoccupied external code block rows, and at least one length indicator is added to each external code block row. , Used to indicate the end position of a certain user information row or padding information in the external code block row occupied by the information block. 12. If the external encoding entity of claim 11, one of the encoder packets includes such information blocks, padding information blocks, and a plurality of length indicators', and wherein the external encoder will take out each of the encoder packets. A part of the acquisition information is obtained, the acquired information is encoded to generate a complex sequence of redundant information, and the redundant information sequences are added to the encoder packet to generate an external code with a fixed row size. Block. 13. If the external encoding entity of claim 2, wherein the column size of the external code block is variable, and once all the user information columns are received, the scheduling unit will use the received The size of the external code blocks is determined by the amount of information, and the size of the external code blocks transmitted during the transmission time interval can be changed according to the size of the external code blocks. 95692.doc 200522578 14 · If the external encoding entity of claim 13, wherein the segmentation and concatenation unit will divide a plurality of columns of user information and place them into a variable size external code block sequence, causing such use The user information column can completely occupy the plural external code block columns, and the user information columns are placed in the plural external code block columns to generate a plurality of information blocks. Occupied external code block rows, and at least one length indicator is added to each external code block row to indicate that a certain user information is listed in the external code block row occupied by the information block. End position. 15. If the external encoding entity of the item ^, an encoder packet includes the tribute block and a plurality of length indicators, and wherein the external encoder will take a part of each encoder packet to obtain a capture Take the information, encode the extracted I information to generate a redundant sequence of redundant information, and add the redundant information rows to the encoder packet to generate an outer code block with a variable row size. 16. If the external and coding entity of claim 2 is used, once the entire user information row is received or the external code block is determined to be generated, the scheduling unit will start from the amount of user information received. Several preset external codes: determined in block row size-a variable external code block row size, which allows minimizing the portion of the external code block occupied by non-user information, thereby allowing the user information rate to be reduced. 17. If the external encoding entity of claim 2, in which once the entire user information is received at 彳 1 ', the scheduling unit will determine a variable external β according to the amount of user information received. & The size of the block sequence of the Bunch code, which allows the 95692.doc 200522578 user information column to completely occupy the encoder packet, wherein the size of the external code block transmitted during the transmission time interval can be according to the external code The block column size changes. 18. The external encoding entity as claimed in claim 1, wherein the receiver includes: a receiving buffer that accumulates information blocks until a certain condition is satisfied, wherein the serial number identifies the external code to which each information block belongs Block, and the position of the information block within the external code block; a reordering unit that uses the sequence number in each information block to reorder any information blocks that are out of order: any information block received; and a copy The detection unit, once the information blocks are reordered, it will use the serial number in each information block to detect duplicate information and delete any duplicate information blocks, and when a specific external code block is full; ^ After this condition, the test unit of the copy will replace any message blocks that fail the cyclic redundancy test with a delete symbol, and generate a request to start external decoding. The condition is that after receiving the external encoding entity as in item 18, the entire external code block is included. The outer code block performs any retransmission. Among them, the condition is no longer for the 2 1 Remove the serial number from the block; and it will receive the external code block an external decoder, 95692.doc 200522578 22. 23. 24. 25. 26. 27. when using the redundant blocks to decode the external code area Any deletion number in the block is used to regenerate the missing information block. > If the external encoding entity of claim 21, further comprising: a reorganization unit, which uses the information blocks and the length indicators to reconstruct a plurality of rows of user information; and a transmission buffer for The user information columns are transmitted on the radio bearer, and the user information columns are transmitted to a higher layer. For example, if the external encoding entity of item 21 is used, the receiving buffer will store a block of other incoming information being received while the previously received information block is being decoded to allow continuous reception of the information block during decoding. . For example, if the external encoding entity of item 18 is requested, the reordering unit delays the decoding time compensation value between the first and second logical strings, and waits to receive two external code blocks before starting decoding. For example, if the external encoding entity of claim 18 is used, the receiving buffer will receive an external code block containing a plurality of columns of information blocks, each of which includes at least a part of the user information column. The size of each column of information blocks is fixed and will occupy a transmission time interval (TTI). As the external encoding entity of item 21, the external decoder will use the redundant information of the complex sequence to decode the external code block. , Used to generate a complete encoder packet containing a plurality of information blocks and a plurality of length indicator symbols, wherein the information blocks have no errors. For example, if the external encoding entity of item 22 is used, the reorganization unit will use at least one length indicator in each information block to determine a certain row of user 95692.doc 200522578 information in the external code block row occupied by the information block. Within the end position, and divide the information blocks into a plurality of rows of user information. 28. The external encoding entity of claim 18, wherein the receiving buffer will receive an external code block containing a plurality of columns of information blocks, where each column of the information block columns contains at least part of the user information Rows, where the size of each row of information blocks is variable and the user information rows will completely occupy the plurality of rows of information blocks. 29 · —The origin station, which includes: a first buffer for storing a plurality of rows of user information; a schedule ... element, which can complete the following tasks: determine a maximum duration before an external code block needs to be transmitted Time, according to the amount of user information stored in the first buffer, the optimal information block size that allows the user information columns to occupy the information blocks is determined to reduce unfilled information areas Block, generates a request to start encoding the user information columns; the segmentation and concatenation unit, which can respond to the request from the scheduling unit to divide the user information columns]] These user information columns are used to It is placed in the alum block with the best size, and a plurality of lengths are generated in each information block, which is used to indicate the end position of a user information row relative to the information block; And an external encoder, which receives a plurality of information blocks before the radio link control (RLC) layer, and uses the information blocks to generate a plurality of redundant blocks, the redundant blocks will Such information is added to generate a block outer code block. 95692.doc 200522578 30. For example, if the origin station of item 29 is cleared, Jt will tell you to answer the question. "When Jiatian accumulates the amount of user plane information, the scheduling unit will start coding. 31. If requested The origin station of 29, where the scheduling unit will start encoding when the packet transmission delay time is exceeded. 32. If the origin station of item 29 is requested, the transmitter further includes: a serial number generator, which A header is added outside each information block, and the header contains a serial number, which is used to identify the order in which each information block is set. 33. If the origin station of claim 32 ', the serial number includes an identification of the external code Part of the block_ and a part identifying the location of each information block within the external code block. 34. The origin station of claim 32, wherein the transmitter further includes: a transmission buffer, The information blocks are stored and transmitted on the radio interface through a common logical channel. 35. The origin station of claim 32, which contains the first logical string from the first information source The information block of the user information and the information block containing the same user information in the second logical string from the second information source have the same sequence number, and the remote private unit will monitor the first logical string information area The serial number of the block and the serial number of the second logical string information block, and adjust the time alignment result of the first logical string information block relative to the second logical string information block, so that the first and second logical blocks Strings can be time aligned. 36. If the origin station of item 29 is requested, the column size of the user information columns may be changed according to the application. 95692.doc 200522578 37. If the origin station of item 29 is requested, where the schedule The unit determines the column size of the external code block. The size of the column is fixed, so that each column can be transmitted at a peak time data rate during a transmission time interval (Ding Ding 1), and all user information is received. These information blocks and length indicators can be transmitted before. 38. Ruoqiu seeks the origin station of item 37, where the segmentation and concatenation will split the user information queue, It is placed in a fixed-size external code block row, and user information rows such as 忒 are placed in these external code block rows to generate a plurality of information blocks, using padding information to fill any unoccupied External code area-block row, and at least one length finger is added to each external code block row to indicate a certain user information row or padding information in the external code block occupied by the information block The end position in the column. 39. If the origin station of claim 38, one of the encoder packets includes such information blocks, fills the poor block information, and a plurality of length indicator symbols, and wherein the external encoder will take out A part of each encoder packet is used to obtain the captured information, the captured information is encoded to generate a plurality of columns of multiple resources Λ, and the redundant information rows are added to the encoder packet to generate a External code block with fixed column size. 40. If the origin station of claim 29, wherein the column size of the external code block is variable, and once all the user information columns are received, the scheduling unit will use the received The size of the external code blocks is determined by the amount of information, and the size of the external code blocks transmitted during the transmission time interval can be changed according to the size of the external code blocks. 95692.doc 200522578 4i • If the origin station of item 40 is requested, the segmentation and concatenation unit will divide a plurality of rows of user information 'and place them in a variable size external code block row, causing these users The information columns may occupy all of the plural external code block columns. The user information columns are placed in the plural external code block columns to generate a plurality of information blocks. Occupied external code block row, and at least one length indicator is added to each external code block row to indicate that a certain user information is listed in the external code block row occupied by the information block End position. 42. If the origin station of claim 4Q, one of the encoder packets includes these information blocks and a plurality of length indicators, and the external encoder will take a part of each encoder packet to obtain the captured information. , Encode the fetched information to generate a complex number of redundant information, and add the redundant information columns to the encoder packet to generate an outer code block with a variable column size. 43. If the origin station of claim 29, in which once all the user information rows are received or the external code block is determined to be generated, the scheduling unit will change the number of users based on the amount of user information received. The preset external code block row size determines a variable external code block row size, which allows minimizing the external code block portion occupied by non-user information, thereby allowing the user information rate to be reduced. 44. If the origin station of claim 29, wherein once all the user information rows are received, the scheduling unit will determine a variable external code block row size based on the amount of user information received, It allows the users 95692.doc -10- 200522578 information column to completely occupy the encoder packet, wherein the size of the external code block transmitted during the round time interval can be changed according to the external exhaustion block column size. 45. —Destination station, which includes a receiving buffer that accumulates information blocks until a certain condition is met, a serial number identifying the external code block to which each information block belongs, and each information The position of the block within the external code block; a reordering unit that uses the sequence number in each information block to reorder any information blocks that were received out of order; and a copy detection unit, After the information blocks are reordered, they will use the serial number in each information block to detect duplicate information and delete any duplicate information blocks, and after the special external code block meets this condition, the duplicate The detection unit replaces any information block that fails the cyclic redundancy test with a delete symbol, and generates a request to start external decoding. 46. If the target station of item 45 is requested, the condition is that a complete external code block is received. 47. If the destination station of item 45 is requested, the condition is that no retransmission of the external code block is required. 48. The station of claim 45, further comprising: a sequence number removing unit for removing a sequence number from each information block of the external code block; and an external decoding H, which The block arrives at the radio link 95692.doc -11-200522578 The control layer previously received the external code block, and used these more than q blocks to decode any erasure punctuation in the external code block if necessary to Regenerate lost information blocks. 49. The station of claim 48, further comprising: a reorganization unit that uses the information blocks and the length indicators to reconstruct a plurality of rows of user information; and a transmission buffer for use in the The radio bearer comes up to transmit these user information columns, and transmits these user information columns to higher layers. 50. If the destination station of item 48 is requested, the receiving buffer will store other incoming information blocks while the previously received information area is being decoded to allow continuous reception of information blocks during decoding. . 5 1 · If the target station of item 45 is explicitly requested, the reordering unit will delay the decoding time compensation value between the first and second logical strings, and wait to receive two external code blocks before starting decoding. 52. The external encoding entity of claim 45, wherein the receiving buffer will receive an external code block containing a plurality of columns of information blocks, where each column of the information block columns contains at least part of the user information Columns, where the size of each block is fixed and occupies a transmission time interval (TTI). 53. If the external encoding entity of claim 48, the external decoder will use the redundant information of the complex sequence to decode The external code block is used to generate a complete encoder packet including a plurality of lean blocks and a plurality of length indicator symbols, wherein the information blocks are free of any errors. 54. If the external encoding entity of claim 49, wherein the reorganization unit will use at least one length indicator in each 95692.doc 200522578 information block to determine a certain row of users > information outside the occupied by the information block The end position in the code block row, and divides these information blocks into a plurality of rows of user information. 55. 56. If the external encoding entity of claim 45, the receiving buffer will receive an external code block containing a plurality of columns of information blocks, where each column of the information block columns contains at least a part of the use Information columns, where the size of each column of information blocks is variable and the user information columns will completely occupy the plurality of information blocks. A method for manufacturing a fixed column size external code block with a plurality of columns, comprising: receiving user information on a radio bearer, wherein the size of the user information columns can be changed according to applications; and determined according to channel conditions A fixed external code block row size, which allows each row to be transmitted at a peak data rate during a transmission time interval (TTI); segment and concatenate multiple series of user information to place it into a fixed size external code block In the block row; 1. Putting these user information rows into a plurality of external code block rows to generate a plurality of information blocks, and any unoccupied external block rows will be filled with padding information; ,, Add at least one length indicator to the parent external code block row to indicate the end position of a user information row or padding information occupied by the information block in the external code block row, and _ The encoder seals 0, including poor blocks such as edges, padding information, and length indicators; 95692.doc -13- 200522578 begins to transmit before receiving all user information The information blocks and length indicators; take a part of each encoder packet to obtain the captured information; encode the 3 captured information to generate a complex number of redundant information; and the redundant information columns The encoder packet is added to generate an outer code block with a fixed column size. 57. A method of manufacturing a variable row size external code block having a plurality of rows, comprising: receiving a plurality of rows of user information on a radio bearer, wherein the size of the user information rows can be changed according to the application; Once all the user information rows are received, a variable external code block row size is determined based on the amount of user information received, and the size of the external code blocks transmitted during the transmission time interval It can be changed according to the size of the external code block sequence; Divide and concatenate the user information of a plurality of columns into a variable size external code block column; Place these user information columns into a complex 餮 external code In the block column, it is used to generate a plurality of information blocks. At least one length indicator is added to each external code block column. ~ 'Is used to indicate that a certain user information column is occupied by the information block. The end position in the external Shima block row, where the user information row will be completed ^ ττ5 According to the plural external code block rows, and one of the encoder packets includes And other information blocks and length indicators; take a part of each encoder packet to obtain the retrieved information; 95692.doc -14- 200522578 encode the retrieved information to generate a complex sequence of redundant information; The redundant information columns are added to the encoder packet to generate an outer code block with a variable column size; and the encoder packet is transmitted. 5 8. The method of expressing item 57, wherein determining a variable external code block row size based on the amount of user information received includes: Once all user information rows are received or it is determined that the After the external code block, a variable external code block row size is determined from a number of preset external code block row sizes according to the amount of user information received, which allows; minimizing the non-use The external code block portion occupied by the user information allows the user information rate to be reduced. 59. The method of claim 57, wherein determining a variable external code block row size based on the amount of user information received includes: Once all user information rows have been received, The amount of user information determines a variable external code block row size, which allows these user information rows to completely occupy the encoder packet. The size of the external code block transmitted during the transmission time interval can be determined according to The outer code block column size changes. 60_ —A method for receiving user information, including: receiving an external code block containing a plurality of columns of information blocks, wherein each of the poor-sense block columns includes at least a part of the user information columns, wherein The size of each column of information blocks is fixed and occupies a transmission time interval (TTI); the redundant code block is used to decode the external code block to generate 95692.doc -15- 200522578 61. 62. A complete encoder packet including a plurality of information blocks and a plurality of length indicators, wherein the information blocks are free of any errors; and at least one length indicator in each information block is used to determine a certain row of user information in The end position in the external code block row occupied by the information block, and the information blocks are divided into a plurality of rows of user information. A method for receiving user information, comprising: receiving an external code block containing a plurality of rows of information blocks, wherein each row of the information block rows contains at least a part of the user information row, wherein the parent row information The size of the block is variable and the user information columns will completely occupy the information blocks of the plural series. The redundant code information is used to decode the external code block to generate a block containing multiple information. And a complete encoder packet including a plurality of length indicators, wherein the information blocks are free of any errors; and at least one length indicator in each information block is used to determine a certain row of user information in the information area. The end position in the external code block row occupied by the block; and dividing the information blocks into a plurality of rows of user information. A point-to-multipoint (ptm) transmission, which can perform variable-rate transmission, out-of-order reception, and point-to-multipoint (PTM) transmission that divides and concatenates a variable-rate information source, including: a network, It includes a receiving buffer for storing a plurality of forward error correction (F Service Data Unit (SDU); a split and concatenation entity 'for splitting a plurality of FEC SDUs and concatenating 95692.doc -16- 200522578 Connected to an information column in an encoder matrix, in which the transmission time interval of the encoder; a complex number column, the matrix includes a first number, each column in the matrix will be occupied-unique 2 only schedule body, prepared in one Printed after receiving the preset amount of data to generate a ~ command to start encoding, which reduces the padding information in the adder packet during encoding from the opening of the girl; the mother 歹 1i 编 石 I 5 乂 Μ coded state 'It will respond to this The start command uses ^ several encoders to seal the direction, i / / 生生 潜-the parent encoder packet includes the first-Yuandi-number of parity columns, and for the encoding, the end of the packet: padding Information; — Sequencer Xiao M Yubei After external encoding, add an external header containing-serial number in each column of the encoder packet; and, σ transmission buffer $, which will receive such encoded packets and format the miscellaneous packets into multiple Synthetic code blocks, and transmitting the synthetic code blocks on the interface.…, Line f 63. The system of claim 62, further comprising: A terminal, which will receive the synthesized code blocks, includes: a receiving unit that accumulates the encoder packet sequence and delays the decoding by a _compensation value between different logical strings; wherein the receiving unit will respond to the sequence To determine the encoder packet to which each forward error correction (FEC) pDU belongs and the position of each forward error correction (ec) pdu in the encoder packet, so that the receiving unit can use the serial number to implement the copy Detect and reorder the received blocks; a removal unit will remove the serial numbers; 95692.doc • 17- 200522578 external decoder, which will decode these information columns; and pass buffer Device, which reorganizes these columns of information. 64. The system of Shiming seeking item 63, in which the sequencer will add an internal header, and Hai Jishuo will provide information to reconstruct the SDUs, where the header will be encoded into the RLC-PDU to which it refers The plurality of length indicator symbols () included in the sequence number header of the RLC-PDU has a flag indicating the existence of the first LI. 65. The system of claim 64, wherein the internal header is added at the beginning of each of the EPs. The system of term 65-month and month, wherein the internal header is added at the beginning of each column of encoder packets. 67. The system of Ruming Item 62, wherein each column of the encoder packet includes a forward error correction (FEC) protocol data unit (PDU), a parity block, and / or padding information. 68. If μ is the system or system of term 62, the% size of these encoder packets is variable. The system of the term 62, wherein the column size of the encoder packets has a constant size. 70. The system according to item 62, wherein the serial number can identify the special encoder packet (EP) and the PDU in the EP. 95692.doc -18-