Method for formating signal in mobile communication system
11 claims: 2 independent, 9 dependent
- 1A method for formatting a medium access control protocol data unit MAC-PDU at a medium access control MAC layer of a mobile terminal in a mobile communication system, the method comprising:receiving at least one medium access control-service data unit MAC-SDU through a logical channel;forming a MAC-PDU by appending a medium access control MAC header to the at least one MAC SDU;and transferring the MAC-PDU to a physical layer through a transport channel, characterized in that the MAC header comprises a mobile identifier adapted to identify the mobile terminal and a medium access control-service access point MAC-SAP identifier adapted to identify the logical channel, wherein the logical channel is a dedicated control channel DCCH or a dedicated traffic channel DTCH.
Independent claims2
65 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
Field of the Invention
0001The present invention relates in general to a mobile communication system, and more particularly to a method for formatting a signal in a mobile communication system.
Description of the Prior Art
0002A conventional method for formatting a signal in a mobile communication system will hereinafter be described with reference to <figref idref="f0001">Figs. 1a</figref> and <figref idref="f0002">1b</figref>.
0003<figref idref="f0001">Fig. 1a</figref> is a view illustrating a data flow for a non-automatic repeat request (ARQ)-type radio access bearer service to which the conventional signal formatting method is applied, and <figref idref="f0002">Fig. 1b</figref> is a view illustrating a data flow for an ARQ-type radio access bearer service to which the conventional signal formatting method is applied.
0004A medium access control (MAC) sublayer of a mobile station utilizes a MAC-protocol data unit (PDU) for peer-to-peer communication with a peer MAC sublayer of a network.
0005The MAC-PDU contains fields necessary to the execution of a MAC function.
0006In radio link control-user/control plane (RLC-U/C) layers, data transferred from upper layers is segmented into payload units (PUs) and then reassembled.
0007The PU is defined as a unit for the resending of an ARQ-type service, and it is dimensioned to be suitable to the lowest data rate in connection.
0008The RLC-U/C layers append headers for segmentation information and acknowledgment information respectively to the PUs and transfer the resultant RLC-U/C PDUs to the MAC sublayer.
0009The MAC sublayer, in turn, appends information multiplexing headers respectively to the RLC-U/C PDUs from the RLC-U/C layers and produces the resultant MAC-PDUs.
0010The MAC-PDU has a size corresponding to that of a transport block to a layer 1.
0011On the other hand, a non-ARQ-type variable rate service, the MAC-PDU is mapped into a transport block to be transferred to the layer 1, the size of which is variable.
0012As a result, in the non-ARQ-type variable rate service, the MAC-PDU is variable in size. As shown in <figref idref="f0001">Fig. 1a</figref>, the MAC-PDU includes a plurality of MAC-service data units(SDUs).
0013In an ARQ-type fixed rate service, the MAC-PDU is determined in size according to the size of a transport block where the PU is fixed in size. As a result, the MAC-PDU includes only one MAC-SDU, as shown in <figref idref="f0002">Fig. 1b</figref>
0014As shown in <figref idref="f0001">Fig. 1a</figref>, a physical layer transforms one multiplexing header and one MAC-SDU or one multiplexing header and a plurality of MAC-SDUs from the MAC sublayer into a transport block with a predetermined size. Also, as shown in <figref idref="f0002">Fig. 1b</figref>, the physical layer transforms one multiplexing header and one MAC-SDU from the MAC sublayer into a transport block with a predetermined size. Then, the physical layer sends the resultant transport block to the network through a physical channel.
0015Upon receiving the transport block sent from the mobile station through the physical channel, the network performs the opposite procedure to that of the mobile station to separate the received transport block into one MAC header and one or more MAC-SDUs and perform the associated signal processing.
SUMMARY OF THE INVENTION
0016General aspects of the invention are set force in the independent claims. Further aspects of the invention are set force in the dependent claims, the following description and the drawings.
0017Therefore, the present invention has been made for the effective implementation of a medium access control sublayer function, and it is an object of the present invention to provide a method for formatting a signal in a mobile communication system, in which a medium access control sublayer formats medium access control-protocol data units according to transport channel characteristics in peer-to-peer communication in such a manner that the protocol data units can have different formats with respect to different transport channels.
0018Objects of the present invention are achieved by subject matters of the independent claims.
0019Preferably, in accordance with one aspect of the present invention, a method for formatting a signal in a mobile communication system by appending a plurality of medium access control headers to a plurality of medium access control-service data units for data transfer between a mobile station and network in the mobile communication system, comprises the first step of, if the service data units have the same characteristics, forming a medium access control-protocol data unit by successively coupling the service data units to any one of the medium access control headers; and the second step of transforming the formed protocol data unit into a transport block with a predetermined size.
0020Preferably, the protocol data unit may include a plurality of fill bits.
0021Further, preferably, each of the medium access control headers may include a mobile identifier region for in-band identification; a medium access control-service access point identifier region for multiplexing a logical channel for service data with a corresponding one of the medium access control headers; a radio link control-user plane identifier region for multiplexing a radio link control-user entity; a medium access control-service data unit length region and a medium access control-service data unit extension region or a medium access control-service data unit number region for cooperating to send the service data; and a frame format identifier region for transfer of information to a higher layer and contention resolution.
0022Further, preferably, the frame format identifier region may include an information format for transferring the information to the higher layer; and a command format or a response format for the contention resolution.
0023Preferably, in accordance with another aspect of the present invention, there is provided a method for formatting a signal in a mobile communication system by appending a plurality of medium access control headers to a plurality of medium access control-service data units for data transfer between a mobile station and network in the mobile communication system, comprising the first step of, if the service data units have different characteristics, forming a medium access control-protocol data unit by sequentially coupling each of the service data units and each of the medium access control headers; and the second step of transforming the formed protocol data unit into a transport block with a predetermined size.
0024Preferably, the first step may include the step of sequentially forming the medium access control headers and then appending each of the service data units to a corresponding one of the medium access control headers subsequently thereto.
0025Preferably, in accordance with yet another aspect of the present invention, there is provided a method for formatting a signal in a mobile communication system by appending a plurality of medium access control headers to a plurality of medium access control-service data units for data transfer between a mobile station and network in said mobile communication system, comprising the first step of, if said service data units have the same characteristics, forming a medium access control-protocol data unit by successively coupling said service data units to any one of said medium access control headers; the second step of, if said service data units have different characteristics, forming said protocol data unit by sequentially coupling each of said service data units and each of said medium access control headers; and the third step of transforming the formed protocol data unit into a transport block with a predetermined size.
0026In a feature of the present invention, a medium access control sublayer formats medium access control-protocol data units according to transport channel characteristics in peer-to-peer communication in such a manner that the protocol data units can have different formats with respect to different transport channels. This makes it possible to provide more efficient functions.
BRIEF DESCRIPTION OF THE DRAWINGS
0027The above and other objects, features and advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which: <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">Fig. 1a</figref> is a view illustrating a data flow for a non-ARQ-type radio access bearer service to which a conventional method for formatting a signal in a mobile communication system is applied;</li><li><figref idref="f0002">Fig. 1b</figref> is a view illustrating a data flow for an ARQ-type radio access bearer service to which the conventional signal formatting method is applied;</li><li><figref idref="f0003">Fig. 2</figref> is a view illustrating a data flow based on a method for formatting a signal in a mobile communication system in accordance with the preferred embodiment of the present invention; and</li><li><figref idref="f0004">Fig. 3</figref> is a view showing a header format based on the signal formatting method in accordance with the preferred embodiment of the present invention.</li></ul>
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
0028A method for formatting a signal in a mobile communication system in accordance with the preferred embodiment of the present invention will hereinafter be described with reference to <figref idref="f0003">Figs. 2</figref> and <figref idref="f0004">3</figref>.
0029<figref idref="f0003">Fig. 2</figref> is a view illustrating a data flow based on the signal formatting method in accordance with the preferred embodiment of the present invention, and <figref idref="f0004">Fig. 3</figref> is a view showing a header format based on the signal formatting method in accordance with the preferred embodiment of the present invention.
0030In peer-to-peer communication between a mobile station and a network in a mobile communication system, first, an upper layer, or a radio resource control (RRC) layer, of the mobile station transfers data to a MAC sublayer through logical channels, or a synchronization control channel (SCCH) (time division duplexer (TDD)), a broadcast control channel (BCCH), a paging control channel (PCCH) and a common control channel (CCCH); and service access points (SAPs), as shown in <figref idref="f0003">Fig. 2</figref>.
0031An RLC-C layer of the mobile station transfers service data from the RRC layer to the MAC sublayer through a logical channel, or a dedicated control channel (DCCH), and an SAP.
0032An RLC-U layer of the mobile station transfers service data from a link access control (LAC) layer to the MAC sublayer through a logical channel, or a dedicated traffic channel (DTCH), and an SAP.
0033As stated previously with reference to <figref idref="f0001">Figs. 1a</figref> and <figref idref="f0002">1b</figref>, the RLC-U/C layers receive service data composed of a plurality of PUs through the associated logical channels and SAPs and append segmentation and reassembly headers respectively to the received service data to segment it into parts of a size suitable to a sending rate and reassemble the segmented parts. Then, the RLC-U/C layers transfer the resultant RLC-U/C PDUs to the MAC sublayer. The MAC sublayer appends multiplexing headers respectively to the RLC-U/C PDUs from the RLC-U/C layers to multiplex them to transport channels and produces the resultant MAC-PDUs.
0034The MAC-PDU is composed of a MAC header, a MAC-SDU and fill bits, which are used to fit the size of a transport block. The MAC-PDU may have a plurality of MAC-SDUs in a non-ARQ-type service. The following tables 1, 2a and 2b show MAC-PDU formats in the non-ARQ-type service. <tables id="tabl0001" num="0001"><table frame="all"><title>[TABLE 1]</title><tgroup cols="5" rowsep="0"><colspec colnum="1" colname="col1" colwidth="22mm" /><colspec colnum="2" colname="col2" colwidth="21mm" /><colspec colnum="3" colname="col3" colwidth="21mm" /><colspec colnum="4" colname="col4" colwidth="21mm" /><colspec colnum="5" colname="col5" colwidth="16mm" /><tbody><row rowsep="1"><entry align="center">MAC header</entry><entry align="center">MAC-SDU</entry><entry align="center">MAC-SDU</entry><entry align="center">MAC-SDU</entry><entry align="center">Fill bits</entry></row></tbody></tgroup></table></tables><tables id="tabl0002" num="0002"><table frame="all"><title>[TABLE 2a]</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="22mm" /><colspec colnum="2" colname="col2" colwidth="22mm" /><colspec colnum="3" colname="col3" colwidth="22mm" /><colspec colnum="4" colname="col4" colwidth="21mm" /><colspec colnum="5" colname="col5" colwidth="21mm" /><colspec colnum="6" colname="col6" colwidth="21mm" /><tbody><row rowsep="1"><entry align="center">MAC header</entry><entry align="center">MAC header</entry><entry align="center">MAC header</entry><entry align="center">MAC-SDU</entry><entry align="center">MAC-SDU</entry><entry align="center">MAC-SDU</entry></row></tbody></tgroup></table></tables><tables id="tabl0003" num="0003"><table frame="all"><title>[TABLE 2b]</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="22mm" /><colspec colnum="2" colname="col2" colwidth="21mm" /><colspec colnum="3" colname="col3" colwidth="22mm" /><colspec colnum="4" colname="col4" colwidth="21mm" /><colspec colnum="5" colname="col5" colwidth="22mm" /><colspec colnum="6" colname="col6" colwidth="21mm" /><tbody><row rowsep="1"><entry align="center">MAC header</entry><entry align="center">MAC-SDU</entry><entry align="center">MAC header</entry><entry align="center">MAC-SDU</entry><entry align="center">MAC header</entry><entry align="center">MAC-SDU</entry></row></tbody></tgroup></table></tables>
0035In an ARQ-type service, the MAC-PDU includes only one MAC-SDU and only one MAC header.
0036In the non-ARQ-type service, the transport block is variable in size because the data rate is variable, too.
0037The PU has a size corresponding to that of the smallest transport block, and a plurality of MAC-SDUs and a plurality of MAC headers may be present in one MAC-PDU.
0038The above table 1 shows that one MAC-PDU contains only one MAC header. Here, the MAC header may be either fixed or not in size, and all MAC-SDUs in the MAC-PDU are limited to have the same characteristics.
0039However, the presence of a plurality of MAC-SDUs in the above table 1 makes it possible to minimize overhead radio.
0040The above tables 2a and 2b show that MAC headers are present for a plurality of MAC-SDUs in one MAC-PDU, respectively. Here, each of the MAC headers may be either fixed or not in size, and the MAC-SDUs in the MAC-PDU have different characteristics such as, for example, different MAC-SAPs. <tables id="tabl0004" num="0004"><table frame="all"><title>[TABLE 3]</title><tgroup cols="8"><colspec colnum="1" colname="col1" colwidth="22mm" /><colspec colnum="2" colname="col2" colwidth="35mm" /><colspec colnum="3" colname="col3" colwidth="36mm" /><colspec colnum="4" colname="col4" colwidth="12mm" /><colspec colnum="5" colname="col5" colwidth="12mm" /><colspec colnum="6" colname="col6" colwidth="24mm" /><colspec colnum="7" colname="col7" colwidth="14mm" /><colspec colnum="8" colname="col8" colwidth="12mm" /><thead valign="top"><row><entry namest="col1" nameend="col2" morerows="1" align="center">PDU field</entry><entry morerows="1" align="center">Functions (Services) associated</entry><entry namest="col4" nameend="col8" align="center">Transport Channels</entry></row><row><entry align="center">BCH</entry><entry align="center">PCH</entry><entry align="center">FACH /RACH</entry><entry align="center">DSCH</entry><entry align="center">DCH</entry></row></thead><tbody><row><entry morerows="5" align="center">MAC header</entry><entry align="center">Mobile identifier</entry><entry align="center">In-band identification</entry><entry /><entry /><entry align="center">•</entry><entry align="center">•</entry><entry /></row><row><entry align="center">MAC-SAPs identifier</entry><entry align="center">Multiplexing logical channels</entry><entry /><entry /><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry></row><row><entry align="center">RLC-Us identifier</entry><entry align="center">Multiplexing multiple RLC-Us</entry><entry /><entry /><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry></row><row><entry align="center">Length of MAC-SDU</entry><entry align="center">Data transfer</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry></row><row><entry align="center">Extension of MAC-SDU (Number of MAC-SDU)</entry><entry align="center">Data transfer</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry></row><row><entry align="center">Frame format identifier</entry><entry align="center">Contention resolution</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry></row><row><entry namest="col1" nameend="col2" align="center">MAC-SDU</entry><entry align="center">Data transfer</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry></row><row><entry namest="col1" nameend="col2" align="center">Fill bits</entry><entry align="center">Fitting the transport block size</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry><entry align="center">•</entry></row></tbody></tgroup></table></tables>
0041As stated above, the MAC-PDU is composed of a MAC header, a MAC-PDU and fill bits. As seen from the above table 3, the MAC header has different contents according to transport channels.
0042For example, in-band identification and MAC-SAP identifier functions of the MAC sublayer are not executed in transport channels, or a broadcast channel (BCH) and a paging channel (PCH).
0043As shown in the above table 3, the MAC header is composed of a plurality of regions, or mobile identifier, MAC-SAPs identifier, RLC-Us identifier, frame format identifier, extension of MAC-SDU(number of MAC-SDU) and length of MAC-SDU regions.
0044The mobile identifier region is used for in-band identification for a specific mobile station when the specific mobile station is addressed through a common downlink channel or it uses a random access channel. The responsibility for user identification lies with the MAC sublayer. Mobile identification becomes a radio network temporary identity when a RRC connection is present and a random radio network temporary identity when no RRC connection is present.
0045The MAC-SAPs identifier region is used to demultiplex transport blocks which the MAC sublayer receives from a layer 1 through transport channels, to corresponding MAC-SAPs.
0046For example, transport blocks received through transport channels, or a downlink shared channel (DSCH) and a dedicated channel (DCH), may be routed to a DCCH-SAP or a DTCH-SAP.
0047The RLC-Us identifier region indicates that a plurality of RLC-U entities are present for the DTCH-SAP and the MAC sublayer should demultiplex transport blocks transferred from a physical layer respectively to the RLC-U entities. An RLC-U identifier in the MAC-PDU indicates an RLC-U entity to which the MAC-PDU is to be routed.
0048The MAC-SDU length region indicates that the MAC-SDU is varied in length. The length of the MAC-SDU must definitely be represented.
0049The MAC-SDU number region (MAC-SDU extension region) is used when the MAC-PDU includes a plurality of MAC-SDUs.
0050Namely, the MAC-SDU number region indicates that only one MAC header is used for a plurality of MAC-SDUs as shown in the table 1, and the MAC-SDU extension region indicates whether the subsequent MAC-SDU is present and that each MAC-SDU has an MAC header as shown in the tables 2a and 2b. These regions are not required in a ARQ-type service where a plurality of MAC-SDUs are not present.
0051The frame format identifier region is composed of three formats, or an information format, a command format and a response format, as seen from the below table 4.
0052When the MAC sublayer receives an information format, it transfers a MAC-SDU directly to a higher layer entity.
0053The command format and response format are used for contention resolution. <tables id="tabl0005" num="0005"><table frame="all"><title>[TABLE 4]</title><tgroup cols="3"><colspec colnum="1" colname="col1" colwidth="32mm" /><colspec colnum="2" colname="col2" colwidth="68mm" /><colspec colnum="3" colname="col3" colwidth="67mm" /><thead valign="top"><row><entry align="center">Format Type</entry><entry align="center">Function</entry><entry align="center">MAC-SDU from where</entry></row></thead><tbody><row><entry align="center">Information Format</entry><entry align="center">Normal transmission</entry><entry align="center">RLC-U/C PDU from higher layer</entry></row><row><entry align="center">Command Format</entry><entry align="center">Command requiring the response for contention resolution</entry><entry align="center">RLC-U/C PDU from higher layer</entry></row><row><entry align="center">Response Format</entry><entry align="center">Response for command</entry><entry align="center">RLC-U/C PDU received from peer MAC entity</entry></row></tbody></tgroup></table></tables>
0054If the MAC sublayer receives a command format contained in a MAC-SDU from a peer entity, then it has to transfer a response format with the same value as that of the received command format to the peer entity.
0055The BCH, PCH, a forward access channel (FACH), a random access channel (RACH), the DSCH and DCH are transport channels. In the above table 3, "•" represents ones of the transport channels to which the regions of the MAC header are applicable.
0056<figref idref="f0004">Fig. 3</figref> shows a PDU format of the RACH or FACH, which includes all of the regions of the MAC-PDU as mentioned above.
0057The RACH or FACH can be mapped to a logical channel, or the CCCH, DCCH or DTCH. The MAC-PDU must have an RLC-U identifier and a MAC-SAP identifier. A contention resolution function can be executed through the RACH or FACH.
0058In this connection, the MAC-PDU includes a frame format identifier. Also, a mobile identifier is included in the MAC-PDU for in-band user identification for the RACH or FACH.
0059As a result, the MAC sublayer formats a MAC header in the above manner, selects a transport channel according to regions of the resultant MAC header and transforms the MAC header and service data into a transport block with a size receivable by a physical layer. Then, the MAC sublayer sends the resultant transport block to the network through any one of physical channels, or a synchronization channel (SCH), a primary common control physical channel (CCPCH), a secondary CCPCH, a physical random access channel (PRACH) and a dedicated physical data channel (DPDCH).
0060Upon receiving the transport block sent from the mobile station through the physical channel, the network performs the opposite procedure to that of the mobile station to separate the received transport block into one or more MAC headers and a plurality of MAC-SDUs and perform the associated signal processing.
0061Further, for communication between the network and mobile station in the mobile communication system, the network performs the same procedure as that of the mobile station to format a signal according to a transport channel and send the resultant transport block with a predetermined size through a physical channel. Then, the mobile station receives the transport block sent from the network and performs the opposite procedure to that of the network to separate the received transport block into one or more MAC headers and a plurality of MAC-SDUs and perform the associated signal processing.
0062As apparent from the above description, according to the present invention, the MAC sublayer formats MAC-PDUs according to transport channel characteristics in peer-to-peer communication in such a manner that the MAC-PDUs can have different formats with respect to different transport channels. Therefore, the present invention has the effect of providing more efficient functions.
0063Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope of the invention as disclosed in the accompanying claims.
Contents4
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| EP0482773A | Cites | European Patent Office (EPO) |
| ROOBOL C ET AL: "A proposal for an RLC/MAC protocol for wideband CDMA capable of handling real time and non-real time services" VEHICULAR TECHNOLOGY CONFERENCE, 1998. VTC 98. 48TH IEEE OTTAWA, ONT., CANADA 18-21 MAY 1998, NEW YORK, NY, USA,IEEE, US, 18 May 1998 (1998-05-18), pages 107-111, XP010287797 ISBN: 0-7803-4320-4 | Non-patent | – |
37 members in 6 offices
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 9841483 | Republic of Korea | – | |
| 19980041483 | Republic of Korea | A | |
| 99119365 | European Patent Office (EPO) | A |
Members37
| Document | Office | Kind | |
|---|---|---|---|
| EP0991208A2 | European Patent Office (EPO) | A2 | |
| KR20000024790A | Republic of Korea | A | |
| EP0991208A3 | European Patent Office (EPO) | A3 | |
| US6791963B1 | United States of America | B1 | |
| US2005013272A1 | United States of America | A1 | |
| EP0991208B1 | European Patent Office (EPO) | B1 | |
| AT288638T | Austria | T | |
| ATE288638T1 | Austria | T1 | |
| DE69923513D1 | Germany | D1 | |
| EP1538763A2 | European Patent Office (EPO) | A2 | |
| DE69923513T2 | Germany | T2 | |
| US2006092911A1 | United States of America | A1 | |
| KR20060069378A | Republic of Korea | A | |
| KR20060079784A | Republic of Korea | A | |
| KR100622108B1 | Republic of Korea | B1 | |
| KR100640938B1 | Republic of Korea | B1 | |
| KR100619598B1 | Republic of Korea | B1 | |
| US2007086342A1 | United States of America | A1 | |
| US2007091931A1 | United States of America | A1 | |
| EP1538763A3 | European Patent Office (EPO) | A3 | |
| EP2017979A1 | European Patent Office (EPO) | A1 | |
| EP2023510A1 | European Patent Office (EPO) | A1 | |
| US7545807B2 | United States of America | B2 | |
| US7792149B2 | United States of America | B2 | |
| US2010290423A1 | United States of America | A1 | |
| EP1538763B1This record | European Patent Office (EPO) | B1 | |
| AT541366T | Austria | T | |
| ATE541366T1 | Austria | T1 | |
| ES2376872T3 | Spain | T3 | |
| US8179893B2 | United States of America | B2 | |
| US8204059B2 | United States of America | B2 | |
| US8401011B2 | United States of America | B2 | |
| US2013148606A1 | United States of America | A1 | |
| EP2017979B1 | European Patent Office (EPO) | B1 | |
| EP2023510B1 | European Patent Office (EPO) | B1 | |
| ES2431674T3 | Spain | T3 | |
| US9019966B2 | United States of America | B2 |
66 legal events, as 10 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Announcement of lapse in spainLapsedFD2A | FD2A | ES | |
| Ep patent has lapsedLapsedEUG | EUG | SE | |
| Change of ownershipPD | PD | NL | |
| Patent expired because of reaching the maximum lifetime of a patentExpiredMK | MK | NL | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Change of representativeR082 | R082 | DE | |
| Expiry of rightR071 | R071 | DE | |
| Change of ownershipPD | PD | NL | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Change of representativeR082 | R082 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Transfer of patentPC2A | PC2A | ES | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent lapsedLapsedMM4A | MM4A | IE | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Definitive protectionFG2A | FG2A | ES | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| Translation of granted ep patentGrantedTRGR | TRGR | SE | |
| Translation files for an european patent granted for nl, confirming art. 52 par. 1 or 6 of the patents act 1995GrantedT3 | T3 | NL | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| Reference to at number (ep patent enters austrian national phase)REF | REF | AT | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Divisional application: reference to earlier applicationAC | AC | EP | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Designation fees paidAKX | AKX | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | EP | |
| Divisional application: reference to earlier applicationAC | AC | EP | |
| Designated contracting statesAK | AK | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 1538763
- Application
- 40308280
Titles3
- German
- Verfahren zur Daten Formatierung in einem mobilen Kommunikationssystem
- English
- Method for formating signal in mobile communication system
- French
- Méthode de formattage de signaux dans un système de communication mobile
Classification
- CPC, 8
- H04B7/26
- H04W28/06
- H04W72/044
- H04L1/1867
- H04W28/065
- H04W80/00
- H04W80/02
- H04B1/66
- IPC, 3
- H04B7 26
- H04L12 56
- H04B1 66
Designated states19
- Contracting states, 19
- Austria
- Belgium
- Switzerland
- Cyprus
- Germany
- Denmark
- Spain
- Finland
- France
- United Kingdom
- Greece
- Ireland
- Italy
- Liechtenstein
- Luxembourg
- Monaco
- Netherlands (Kingdom of the)
- Portugal
- Sweden
