EP1013115B1 - Data transmission method in gprs - Google Patents
Data transmission method in gprs Download PDFInfo
- Publication number
- EP1013115B1 EP1013115B1 EP98943921A EP98943921A EP1013115B1 EP 1013115 B1 EP1013115 B1 EP 1013115B1 EP 98943921 A EP98943921 A EP 98943921A EP 98943921 A EP98943921 A EP 98943921A EP 1013115 B1 EP1013115 B1 EP 1013115B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- rlc
- llc
- data block
- data
- mac
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/14—Backbone network devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/02—Inter-networking arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/24—Interfaces between hierarchically similar devices between backbone network devices
Definitions
- the invention relates to a data transmission method between a network part of a General Packet Radio Service and a subscriber terminal comprising: an RLC/MAC (Radio Link Control / Medium Access Control) protocol layer and an LLC (Logical Link Control) protocol layer employing the services of the RLC/MAC protocol layer as data link layers; in data transmission an LLC frame of the LLC layer is placed in an RLC data block of the RLC/MAC layer.
- RLC/MAC Radio Link Control / Medium Access Control
- LLC Logical Link Control
- a problem with the above arrangement is that it is not optimal.
- prior art LLC frames are not necessarily equally divided into RLC data blocks but one LLC frame may require more than one RLC data block so that the entire LLC frame can be transmitted over the radio path.
- An LLC frame can also be shorter than one RLC data block, therefore depending on the situation one RLC data block could hold several LLC frames.
- two LLC frames can at the most be placed in an RLC data block. Then, if the RLC data block could in principle have held more than two LLC frames, e.g. three LLC frames, the unused capacity is lost according to prior art as it cannot be used.
- the invention further relates to a cellular network using a general packet radio service comprising: a network part and at least one subscriber terminal, data transmission between the network part and the subscriber terminal, the network part and the subscriber terminal being arranged to perform data transmission using a protocol stack where an RLC/MAC (Radio Link Control / Medium Access Control) protocol layer and an LLC (Logical Link Control) protocol layer employing the services of the RLC/MAC protocol layer act as data link layers, the network part and the subscriber terminal being arranged to use transmission units for data transmission in such a manner that an LLC frame of the LLC layer is placed in an RLC data block of the RLC/MAC layer.
- RLC/MAC Radio Link Control / Medium Access Control
- LLC Logical Link Control
- the cellular network is in accordance with the invention characterized by the network part and the subscriber terminal being arranged to locate more than two LLC frames in one RLC data block so that the network part and the subscriber terminal are arranged to locate a mechanism in the RLC data block indicating the length of the LLC frame included in the RLC data block and information about whether another LLC frame will follow said LLC frame or not.
- the invention is based on the idea that no limit is artificially set on how many LLC frames can be placed in one RLC data block.
- the method and system of the invention provide several advantages.
- a valuable transmission capacity of the radio path is optimally utilized, since the data transmission capacity of the RLC data blocks is fully utilized in such situations where one RLC data block holds more than two LLC frames.
- the data transmission rate at the radio interface increases and the use of radio resources decreases.
- the cellular network typically comprises a fixed network infrastructure, i.e. a network part, and subscriber terminals 150 which can be fixedly mounted, vehicle-mounted or hand-held portable terminals.
- the network part comprises base stations 100.
- Several base stations 100 are, in turn, controlled in a centralized manner by a base station controller 102 communicating with them.
- the base station 100 comprises transceivers 114, typically one to sixteen transceivers 114.
- One transceiver 114 offers radio capacity to one TDMA frame i.e. typically to eight time slots.
- connection from the transceivers 114 of the base station 100 to an antenna unit 112 implementing a bi-directional radio connection 170 to a subscriber terminal 150 There is a connection from the transceivers 114 of the base station 100 to an antenna unit 112 implementing a bi-directional radio connection 170 to a subscriber terminal 150.
- the structure of the frames to be transmitted also on the bi-directional radio connection 170 is accurately determined and referred to as an air interface.
- the subscriber terminal 150 can be, for example, a standard GSM mobile phone to which a laptop computer 152, which can be used in packet transmission for ordering and processing packets, can for instance be connected using an additional card. Protocol processing can be placed in the subscriber terminal 150 and/or in the computer 152 connected to the subscriber terminal 150.
- a control unit 214 decides whether the bit stream is signalling information transmitted to a control unit 214, or speech transmitted to a speech codec 122 of the base station controller 102.
- the channel codec 216 also performs error correction.
- the control unit 214 performs internal control functions by controlling various units.
- a burst former 228 adds a training sequence and a tail to the data arriving from the channel codec 216.
- a multiplexer 226 indicates to each burst its time slot.
- a modulator 224 modulates digital signals to a radio frequency carrier. This function is of analogue nature and therefore a digital-to-analogue converter 222 is needed to perform it.
- a transmitter 220 comprises a filter limiting the bandwidth. In addition, the transmitter 220 controls the output power of the transmission.
- the transmission units 164, 166 communicate through a message bus with a control unit 162, through which the connections to the packet transmission network 142 are handled. Furthermore, the control unit 162 processes, for example, traffic statistics, billing data collection and location and space of the subscriber terminal 150.
- the functions of the transmission unit 164 include: encryption and decryption of user data, compression and decompression of user data, cancellation of user data from the LLC frames and location of user data in the LLC frames.
- the packet transmission network 142 is typically a private network using an Internet protocol carrying signalling and tunnelled user data.
- the structure of the network 142 may vary operator-specifically concerning the architecture and protocols below the Internet protocol layer.
- FIG. 1B Let us next take a look how packet data is transmitted in Figure 1B. All structure parts described in Figure 1B are found and explained in connection with Figure 1A, and therefore not described herein.
- a laptop computer 152 is now connected to the subscriber terminal 150.
- a bold line describes how data to be transferred is carried from the laptop computer 152 to the server computer 148. Data can naturally also be transferred in the opposite direction too, from the server computer 148 to the laptop computer 152.
- Data is carried through the system at the air interface 170, from the antenna 112 to the transceiver 114 and from there multiplexed in the multiplexer 116 along the data link 160 to the group switching field 120, where a connection is established to the output of the support node 140.
- data is carried through the transmission unit 164 and the control unit 162, from the support node 140 data is applied along the packet transmission network 142 through the gateway node 144 and is connected to the server computer 148 connected to the public packet transmission network 146.
- Such a network can also be constructed, where circuit-switched data is not transferred at all, only packet data. Then the structure of the network can be simplified.
- connection does not need to be bi-directional either; the invention enables bi-directional connections but a connection can also be uni-directional broadcast where the transmitter does not receive any acknowledgement from the receiver concerning the reception of the transmission. Different combinations are also possible, such as point-to-multipoint broadcast.
- the GPRS transmission path protocol model is also constructed on the basis of an OSI (Open Systems Interconnection) protocol model of the International Standardisation Organisation.
- OSI Open Systems Interconnection
- the base station 100 and the base station controller 102 are not described separately since no interface is determined between the two.
- the protocol processing determined for the base station arrangement 168 can thus in principle be freely divided between the base station 100 and the base station controller 102, however, in practice not to the transcoder 122 though it is included in the base station arrangement 168.
- Different network elements are divided by interfaces Um, Gb, Gn and Gi between them.
- the protocol layers have an application level APPL. It shows user applications employing the GPSR system for data transmission. These applications are often ordinary programs intended for Internet use, like e-mail programs and world wide web.
- IP/X.25 offers a connection to the Internet and other external data networks.
- IP/X.25 uses a normal Internet IP protocol.
- a GPRS tunnelling protocol GTP tunnels user data and signalling along the frame network between different GSNs.
- the GTP can, if desired, implement flow control between the SGSN 140 and the GGSN 144.
- a TCP Transmission Control Protocol
- a UDP User Datagram Protocol
- a TCP transfers the data packets of the GTP layer whose protocol does not need a reliable link, for example, when using the Internet protocol IP.
- IP Internet Protocol
- TCP produces flow control, and protection against disappearance and corruption for the packets to be transferred.
- the UDP correspondingly produces protection against packet corruption only.
- the IP is the frame network protocol of the GPRS, the functions of which include routing of user data and control data.
- the IP can be based on an IPv4 protocol, but a shift to use an IPv6 protocol will later take place.
- SNDCP layer Subnetwork Dependent Convergence Protocol
- PDPs Packet Data Protocol
- SNDCP Segment Data Protocol
- LLC layer Logical Link Control
- the LLC layer implements a reliable encrypting logical link between the SGSN 140 and the MS 150.
- the LLC is independent and does not depend on lower layers so that the air interface change would affect the network part of the mobile network as little as possible.
- the LLC supports data frames of varying sizes, transmission of acknowledged and non-acknowledged data and data transmission from the SGSN 140 to several MSs 150 using the same physical radio channel.
- the LLC allows different priorities for the data so that higher priority data is transferred to the subscriber terminal before lower priority data.
- the information to be transferred and the user data are protected by encryption. Between Um and Gb interfaces the LLC data is transferred at an LLC-Relay level.
- a BSSGP level (Base Station Subsystem GPRS Protocol) carries information associated with routing and service quality between the BSS 168 and the SGSN 140. This information is physically delivered by an FR level (Frame Relay).
- FR level Framework Relay
- the RLC level On the basis of a BCS (Block Check Sequence) of a CRC (Code Redundancy Check) calculated by the physical level the RLC level produces retransmission procedures of erroneous data.
- the physical level is implemented at Um interface on a radio connection, for example, at the determined air interface of the GSM. Modulation of the carrier wave, interleaving and error correction on the data to be transmitted, synchronization and transmitter power control are examples of functions performed at the physical level.
- FIGs 4A and 4B illustrate the structure of a radio block.
- the radio block refers to a structure used at the RLC/MAC protocol layer.
- the LLC frames are carried in the RLC data block and in the radio block of Figure 4B the RLC/MAC signalling is carried in the RLC/MAC control block.
- the radio block is formed of a MAC header field MAC HEADER, an RLC data block RLC DATA BLOCK and a block check sequence BCS.
- the MAC header includes a USE (Uplink State Flag), a T (an indicator of radio block type) and a PC (Power Control).
- the RLC data block is formed of an RLC header field RLC HEADER and an RLC data field RLC DATA.
- the invention relates to the RLC data blocks in particular where the LLC frames are transparently transferred at the air interface 170 between the base station 100 and the subscriber terminal 150.
- the data included in one LLC frame is placed in three radio blocks according to Figure 4A, each radio block being placed in four normal radio bursts of the radio path 170.
- the LLC frame is formed in accordance with the Figure from a frame header FH, information INFO to be transferred and a frame check sequence FCS.
- the radio block consists of a block header BH, information INFO to be transferred and a block check sequence BCS,
- the BH corresponds to the MAC header field MAC HEADER and the RLC header field RLC HEADER in Figure 4A.
- the aim of the RLC/MAC protocol layer is thus to divide the LLC frames into smaller blocks so that they can be physically conveyed in the radio blocks over the radio path.
- the length of one LLC frame can be up to about 1600 octets.
- the LLC frame can also be very short, in which case the procedure of the invention can be used so that the transmission capacity of the radio block will be efficiently utilized.
- FIG. 6 shows in greater detail the structure of the RLC data block which is interesting for the invention.
- Bits 1-8 forming one octet are shown in the horizontal plane.
- Octets 1-N are shown in the vertical plane.
- Octet 1 comprises a MAC header field so that bits 8-5 include a PC, bit 4 a T and bits 3-1 a USF.
- Octets 2-4 comprise an RLC header field so that bits 8-2 of octet 2 include a TFI (Temporary Flow Identity) and bit 1 an S/P (Supplementary/Polling Bit), bits 8-2 of octet 3 include a BSN (Block Sequence Number) and bit 1 an E (Extension Bit) and octet 4 an optional extension field OPT EXT FIELD.
- Octets 5-N comprise information RLC INFO to be transferred, i.e. the LLC frame data to be transferred.
- the TFI is used to identify to which temporary block flow the RLC data block belongs.
- the network part determines an identifier for each temporary block flow.
- the S/P is used for control and monitoring signalling.
- the BSN is used to show the radio block sequence, where the collected blocks form one LLC frame.
- the E is used to indicate whether the optional extension field is included or not. If the extension bit is not switched on, then all the following information to be transferred is included in one LLC frame. If the extension bit is switched on, then the extension field is included and belongs to the RLC header field.
- the length of the extension field is thus one octet.
- the first 6 bits form a length indicator LI indicating how many octets from an RLC INFO field belong to the prevailing LLC frame.
- the last byte in the LLC frame can be placed in the middle of the RLC data field, the LI then informing about the location of the last byte of the LLC frame.
- extension field comprises two bits, the combination of which informs about the contents of a possibly incomplete RLC data field,
- One bit (M) shows whether the same radio block includes another LLC frame. If this is the case, then another bit (C) shows whether the entire second LLC frame is in this radio block or whether it continues in the following radio block.
- the base station 100 should upon receiving such a radio block transmit, to be sure, all remaining octets in the RLC data block to the SGSN 140 to ensure that the SGSN 140 is able to receive all the octets belonging to the second LLC frame.
- Figure 7A shows how only a first LLC frame 700 and a second LLC frame can be placed in the first radio block.
- the first radio block has enough space for the third LLC frame 704, but since there is no mechanism to indicate the presence of a third LLC frame in the first radio block, the third LLC frame 704 cannot be placed in the RLC data block of the first radio block.
- the third LLC frame 704 is transferred using the RLC data block of the second radio block and the capacity of the RLC data block not used by the first radio block is therefore lost.
- FIG. 7B shows a procedure of the invention. All three LLC frames 700, 702, 704 can be placed in the RLC data block of one radio block, and the capacity of the RLC data block will be entirely utilized as shown in the Figure.
- the procedure in Figure 7B can be implemented in such a manner that the RLC data block includes a mechanism accurately indicating the length of the LLC frame included in each RLC data block and the information on whether another LLC frame will follow after said LLC frame.
- Figure 7B illustrates a way to implement the mechanism.
- the octet of the RLC data block, in which the preceding LLC frame ends is always followed by a corresponding extension field than what is determined in accordance with prior art, if a new LLC frame is to be transmitted.
- This new extension field determines whether there is a next LLC frame in the same RLC data block.
- the extension field determines the length of said LLC frame and whether said LLC frame can fit into the current RLC data block or whether it continues to the next RLC data block.
- the mechanism described can be applied until the entire RLC data block is filled with LLC frame data and thus the data stream of the LLC frames can be a continuous octet-shaped LLC data stream independent of the RLC data block limits.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Communication Control (AREA)
- Telephonic Communication Services (AREA)
- Transition And Organic Metals Composition Catalysts For Addition Polymerization (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephone Function (AREA)
- Measuring Or Testing Involving Enzymes Or Micro-Organisms (AREA)
- Investigating Or Analysing Biological Materials (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
- The invention relates to a data transmission method between a network part of a General Packet Radio Service and a subscriber terminal comprising: an RLC/MAC (Radio Link Control / Medium Access Control) protocol layer and an LLC (Logical Link Control) protocol layer employing the services of the RLC/MAC protocol layer as data link layers; in data transmission an LLC frame of the LLC layer is placed in an RLC data block of the RLC/MAC layer.
- A problem with the above arrangement is that it is not optimal. According to prior art LLC frames are not necessarily equally divided into RLC data blocks but one LLC frame may require more than one RLC data block so that the entire LLC frame can be transmitted over the radio path. An LLC frame can also be shorter than one RLC data block, therefore depending on the situation one RLC data block could hold several LLC frames. However, according to prior art two LLC frames can at the most be placed in an RLC data block. Then, if the RLC data block could in principle have held more than two LLC frames, e.g. three LLC frames, the unused capacity is lost according to prior art as it cannot be used.
- It is an object of the present invention to provide a method and equipment implementing the method so as to solve the above problem. This is achieved with the type of method presented in the preamble characterized by placing more than two LLC frames in one RLC data block so that the RLC data block includes a mechanism indicating the length of the LLC frame included in the RLC data block and information on whether another LLC frame will follow said LLC frame or not.
- The invention further relates to a cellular network using a general packet radio service comprising: a network part and at least one subscriber terminal, data transmission between the network part and the subscriber terminal, the network part and the subscriber terminal being arranged to perform data transmission using a protocol stack where an RLC/MAC (Radio Link Control / Medium Access Control) protocol layer and an LLC (Logical Link Control) protocol layer employing the services of the RLC/MAC protocol layer act as data link layers, the network part and the subscriber terminal being arranged to use transmission units for data transmission in such a manner that an LLC frame of the LLC layer is placed in an RLC data block of the RLC/MAC layer.
- The cellular network is in accordance with the invention characterized by the network part and the subscriber terminal being arranged to locate more than two LLC frames in one RLC data block so that the network part and the subscriber terminal are arranged to locate a mechanism in the RLC data block indicating the length of the LLC frame included in the RLC data block and information about whether another LLC frame will follow said LLC frame or not.
- The preferred embodiments of the invention are disclosed in the dependent claims.
- The invention is based on the idea that no limit is artificially set on how many LLC frames can be placed in one RLC data block.
- The method and system of the invention provide several advantages. A valuable transmission capacity of the radio path is optimally utilized, since the data transmission capacity of the RLC data blocks is fully utilized in such situations where one RLC data block holds more than two LLC frames. Thus, the data transmission rate at the radio interface increases and the use of radio resources decreases.
- In the following the invention will be described in greater detail in connection with the preferred embodiments with reference to the accompanying drawings, in which:
- Figure 1A is a block diagram showing a cellular network,
- Figure 1B shows circuit-switched data transmission,
- Figure 2 shows the structure of one transceiver,
- Figure 3 shows protocol stacks of the system,
- Figure 4A shows a radio block, in which an RLC data block carrying LLC frames is placed,
- Figure 4B shows a radio block in which an RLC/MAC control block carrying RLC/MAC signalling is placed,
- Figure 5 shows by way of example how LLC frames are placed in radio blocks and radio bursts,
- Figure 6 shows the structure of an RLC data block,
- Figure 7A shows how two LLC frames can, at the most, be placed in one RLC data block in accordance with prior art,
- Figure 7B illustrates how more than two, e.g. three, LLC frames can be placed in one RLC data block in accordance with the invention.
-
- With reference to Figure 1A a typical cellular network structure of the invention is described and its interfaces to a fixed telephone network and a packet transmission network. Figure 1A includes only the blocks essential for describing the invention, but for those skilled in the art it is obvious that a conventional cellular network also includes other functions and structures, which need not be described here in greater detail. The invention is applicable to be used in basic GSM cellular networks and in networks further developed therefrom, like GSM1800 and GSM1900 systems. The invention is preferably used in a 2+- phase packet transmission of the GSM system, i.e. in the GPRS (General Packet Radio Service). Additional information on GPRS and the protocols used therein can be obtained, if needed, from ETSI (European Telecommunications Standards Institute) GPRS specifications, like ETSI GSM 03.60 and ETSI GSM 04.64.
- The cellular network typically comprises a fixed network infrastructure, i.e. a network part, and
subscriber terminals 150 which can be fixedly mounted, vehicle-mounted or hand-held portable terminals. The network part comprisesbase stations 100.Several base stations 100 are, in turn, controlled in a centralized manner by abase station controller 102 communicating with them. Thebase station 100 comprisestransceivers 114, typically one to sixteentransceivers 114. Onetransceiver 114 offers radio capacity to one TDMA frame i.e. typically to eight time slots. - The
base station 100 comprises acontrol unit 118 controlling the operation of thetransceivers 114 and amultiplexer 116. Themultiplexer 116 locates traffic and control channels used byseveral transceivers 114 to asingle data link 160. The structure of thedata link 160 is accurately determined and referred to as an Abis interface. Thedata link 160 is typically implemented using a 2 Mbit/s link, or a PCM link (Pulse Coded Modulation) offering a 31 x 64 kbit/s transmission capacity, while time slot 0 is allocated for synchronization. - There is a connection from the
transceivers 114 of thebase station 100 to anantenna unit 112 implementing abi-directional radio connection 170 to asubscriber terminal 150. The structure of the frames to be transmitted also on thebi-directional radio connection 170 is accurately determined and referred to as an air interface. - The
subscriber terminal 150 can be, for example, a standard GSM mobile phone to which alaptop computer 152, which can be used in packet transmission for ordering and processing packets, can for instance be connected using an additional card. Protocol processing can be placed in thesubscriber terminal 150 and/or in thecomputer 152 connected to thesubscriber terminal 150. - Figure 2 shows the structure of one
transceiver 114 in greater detail. Areceiver 200 comprises a filter blocking frequencies outside a desired frequency band. Then a signal is converted to an intermediate frequency or directly to baseband, in which form the signal is sampled and quantized in an analogue-to-digital converter 202. Anequalizer 204 compensates for interference caused by multipath propagation, for example. Ademodulator 206 takes from the equalized signal a bit stream that is transmitted to ademultiplexer 208. Thedemultiplexer 208 separates the bit stream from different time slots into its logical channels. Achannel codec 216 decodes the bit stream of different logical channels, i.e. decides whether the bit stream is signalling information transmitted to acontrol unit 214, or speech transmitted to aspeech codec 122 of thebase station controller 102. Thechannel codec 216 also performs error correction. Thecontrol unit 214 performs internal control functions by controlling various units. A burst former 228 adds a training sequence and a tail to the data arriving from thechannel codec 216. Amultiplexer 226 indicates to each burst its time slot. Amodulator 224 modulates digital signals to a radio frequency carrier. This function is of analogue nature and therefore a digital-to-analogue converter 222 is needed to perform it. Atransmitter 220 comprises a filter limiting the bandwidth. In addition, thetransmitter 220 controls the output power of the transmission. Asynthesizer 212 arranges the necessary frequencies for different units. Thesynthesizer 212 includes a clock that may be controlled locally or in a centralized manner from somewhere else, for example, from thebase station controller 102. Thesynthesizer 212 creates the necessary frequencies, for example, by a voltage-controlled oscillator. - The
base station controller 102 comprises agroup switching field 120 and acontrol unit 124. Thegroup switching field 120 is used to switch speech and data and to connect signalling circuits. Thebase station 100 and thebase station controller 102 form a base station subsystem also comprising a transcoder, also known as a speech codec, or a TRAU (Transcoder and Rate Adapter Unit) 122. Thetranscoder 122 is generally placed as close as possible to a mobileservices switching centre 132, since speech can then be transferred in cellular network form between thetranscoder 122 and thebase station controller 102 saving transmission capacity. - The
transcoder 122 converts different digital coding forms of speech used between a public switched telephone network and a cellular network to suit one another, for example, from the 64 kbit/s fixed network form to another cellular network form (e.g. 13 kbit/s) and vice versa. Thecontrol unit 124 performs call control, mobility management, statistical data collection and signalling. - As Figure 1A shows the
group switching field 120 can perform switching (indicated by black spots) to a public switched telephone network (PSTN) 134 through themobile switching centre 132 and to apacket transmission network 142. Atypical terminal 136 in the public switchedtelephone network 134 is an ordinary or an ISDN (Integrated Services Digital Network) phone. - The connection between the
packet transmission network 142 and thegroup switching field 120 is established by a support node (SGSN = Serving GPRS Support Node) 140. The aim of thesupport node 140 is to transfer packets between the base station system and a gateway node (GGSN = Gateway GPRS Support Node) 144, and to keep record of the location of thesubscriber terminal 150 within its area. The support node comprisesseveral transmission units transmission unit 164 is connected to thebase station controller 102. Depending on the need of capacity asecond transmission unit 166 could also be connected to the samebase station controller 166 or to another base station controller. This connection is, however, not described in Figure 1A. Thetransmission units control unit 162, through which the connections to thepacket transmission network 142 are handled. Furthermore, thecontrol unit 162 processes, for example, traffic statistics, billing data collection and location and space of thesubscriber terminal 150. The functions of thetransmission unit 164 include: encryption and decryption of user data, compression and decompression of user data, cancellation of user data from the LLC frames and location of user data in the LLC frames. - The
gateway node 144 connects a publicpacket transmission network 146 and thepacket transmission network 142. An Internet protocol or an X.25 protocol can be used at the interface. Thegateway node 144 encapsules the internal structure of thepacket transmission network 142 from the publicpacket transmission network 146, so for the publicpacket transmission network 146 thepacket transmission network 142 resembles a sub-network, the public packet transmission network being able to address packets to thesubscriber terminal 150 placed therein and to receive packets therefrom. - The
packet transmission network 142 is typically a private network using an Internet protocol carrying signalling and tunnelled user data. The structure of thenetwork 142 may vary operator-specifically concerning the architecture and protocols below the Internet protocol layer. - The public
packet transmission network 146 may be, for example, a global Internet network, to which asubscriber terminal 148, for example a server computer, with a connection thereto wants to transfer packets to thesubscriber terminal 150. - At the
air interface 170 time slots not allocated to circuit-switched transmission are used for packet transmission. Capacity is dynamically allocated for packet transmission, i.e. when a data transmission request arrives any free channel can be allocated to be used in packet transmission. The arrangement is flexible, circuit-switched connections taking priority over packet data links. When necessary, circuit-switched transmission cancels out packet-switched transmission, i.e. a time slot engaged in packet transmission is passed on to circuit-switched transmission. This is possible, since packet transmission endures such interruptions well; the transmission is proceeded in another time slot allocated for use. The arrangement can also be implemented in such a manner that no definite priority is given to circuit-switched transmission, but both circuit-switched and packet-switched transmission requests are served in their order of arrival. - Let us next take a look how packet data is transmitted in Figure 1B. All structure parts described in Figure 1B are found and explained in connection with Figure 1A, and therefore not described herein. A
laptop computer 152 is now connected to thesubscriber terminal 150. A bold line describes how data to be transferred is carried from thelaptop computer 152 to theserver computer 148. Data can naturally also be transferred in the opposite direction too, from theserver computer 148 to thelaptop computer 152. Data is carried through the system at theair interface 170, from theantenna 112 to thetransceiver 114 and from there multiplexed in themultiplexer 116 along the data link 160 to thegroup switching field 120, where a connection is established to the output of thesupport node 140. In thesupport node 140 data is carried through thetransmission unit 164 and thecontrol unit 162, from thesupport node 140 data is applied along thepacket transmission network 142 through thegateway node 144 and is connected to theserver computer 148 connected to the publicpacket transmission network 146. - Such a network can also be constructed, where circuit-switched data is not transferred at all, only packet data. Then the structure of the network can be simplified.
- The invention is preferably implemented by software. The invention then requires relatively simple software changes within a strictly restricted area in the
control unit 118 of thebase station 100 and/or in thecontrol unit 124 of thebase station controller 102. The software can thus be divided in different ways between the above-mentioned control units depending on how the protocol processing is divided between different parts. Correspondingly thesubscriber terminal 150 and/or thecomputer 152 connected thereto also require software changes in order to implement the protocol processing of the invention. - Although the examples show only a point-to-point packet data link between two parties, the invention is not restricted thereto, but it is obvious for those skilled in the art how the described arrangement can also be used, for example, in point-to-multipoint connections, where one party simultaneously transmits data to several other parties. The connection does not need to be bi-directional either; the invention enables bi-directional connections but a connection can also be uni-directional broadcast where the transmitter does not receive any acknowledgement from the receiver concerning the reception of the transmission. Different combinations are also possible, such as point-to-multipoint broadcast.
- In the following a closer look is taken with reference to Figure 3 at how protocol stacks used in the arrangement are formed. Like the conventional GSM arrangement, the GPRS transmission path protocol model is also constructed on the basis of an OSI (Open Systems Interconnection) protocol model of the International Standardisation Organisation.
- As to each protocol element Figure 3 shows which protocol parts said network element processes. The network elements are: the mobile station (MS) 150, 152, the base station subsystem (BSS) 168, the support node (SGSN = Serving GPRS Support Node) 140 and the gateway node (GGSN = Gateway GPRS support node) 144. The
base station 100 and thebase station controller 102 are not described separately since no interface is determined between the two. The protocol processing determined for thebase station arrangement 168 can thus in principle be freely divided between thebase station 100 and thebase station controller 102, however, in practice not to thetranscoder 122 though it is included in thebase station arrangement 168. Different network elements are divided by interfaces Um, Gb, Gn and Gi between them. - As the top level the protocol layers have an application level APPL. It shows user applications employing the GPSR system for data transmission. These applications are often ordinary programs intended for Internet use, like e-mail programs and world wide web.
- IP/X.25 offers a connection to the Internet and other external data networks. For the external networks it uses a normal Internet IP protocol.
- A GPRS tunnelling protocol GTP tunnels user data and signalling along the frame network between different GSNs. The GTP can, if desired, implement flow control between the
SGSN 140 and theGGSN 144. - A TCP (Transmission Control Protocol) transfers the data packets of the GTP layer along the frame network to the protocols that need a reliable data link, for example, when using an X.25 protocol. A UDP (User Datagram Protocol) in turn transfers the data packets of the GTP layer whose protocol does not need a reliable link, for example, when using the Internet protocol IP. Through the IP the TCP produces flow control, and protection against disappearance and corruption for the packets to be transferred. The UDP correspondingly produces protection against packet corruption only.
- The IP is the frame network protocol of the GPRS, the functions of which include routing of user data and control data. The IP can be based on an IPv4 protocol, but a shift to use an IPv6 protocol will later take place.
- The most important functions of an SNDCP layer (Subnetwork Dependent Convergence Protocol) are: multiplexing several PDPs (Packet Data Protocol) into one SNDCP connection, compression and decompression of user data and compression and decompression of protocol control information. In addition, the SNDCP segments the data in higher network protocol form into lower LLC layer (Logical Link Control) form and vice versa.
- The LLC layer implements a reliable encrypting logical link between the
SGSN 140 and theMS 150. The LLC is independent and does not depend on lower layers so that the air interface change would affect the network part of the mobile network as little as possible. In addition, the LLC supports data frames of varying sizes, transmission of acknowledged and non-acknowledged data and data transmission from theSGSN 140 toseveral MSs 150 using the same physical radio channel. The LLC allows different priorities for the data so that higher priority data is transferred to the subscriber terminal before lower priority data. The information to be transferred and the user data are protected by encryption. Between Um and Gb interfaces the LLC data is transferred at an LLC-Relay level. - In addition to the higher layer data, a BSSGP level (Base Station Subsystem GPRS Protocol) carries information associated with routing and service quality between the
BSS 168 and theSGSN 140. This information is physically delivered by an FR level (Frame Relay). - There are two separate functions at the RLC/MAC level: MAC (Medium Access Control) and RLC (Radio Link Control). The MAC is responsible for performing the following functions: multiplexing data and signalling on uplink (from the subscriber terminal to the network part) and downlink (from the network part to the subscriber terminal) connections, management of uplink resource requests and division and timing of downlink traffic resources. This level also includes management of traffic prioritization. The RLC attends to the transmission of LLC-level data, or LLC frames, to the MAC level; the RLC divides the LLC frames into RLC data blocks and transmits them to the MAC layer. In the uplink direction the RLC builds LLC frames from RLC data blocks which are transferred to the LLC layer. On the basis of a BCS (Block Check Sequence) of a CRC (Code Redundancy Check) calculated by the physical level the RLC level produces retransmission procedures of erroneous data. The physical level is implemented at Um interface on a radio connection, for example, at the determined air interface of the GSM. Modulation of the carrier wave, interleaving and error correction on the data to be transmitted, synchronization and transmitter power control are examples of functions performed at the physical level.
- Figures 4A and 4B illustrate the structure of a radio block. The radio block refers to a structure used at the RLC/MAC protocol layer. In the radio block of Figure 4A the LLC frames are carried in the RLC data block and in the radio block of Figure 4B the RLC/MAC signalling is carried in the RLC/MAC control block.
- In Figure 4A the radio block is formed of a MAC header field MAC HEADER, an RLC data block RLC DATA BLOCK and a block check sequence BCS.
- The MAC header includes a USE (Uplink State Flag), a T (an indicator of radio block type) and a PC (Power Control). The RLC data block is formed of an RLC header field RLC HEADER and an RLC data field RLC DATA. The invention relates to the RLC data blocks in particular where the LLC frames are transparently transferred at the
air interface 170 between thebase station 100 and thesubscriber terminal 150. - The radio block in Figure 4B is formed of a MAC header field, an RLC/MAC control block and a block check sequence BCS. The RLC/MAC signalling is transferred only between the
subscriber terminal 150 and thebase station system 168. Signalling is used for maintaining a physical radio resource. - In Figure 5 the data included in one LLC frame is placed in three radio blocks according to Figure 4A, each radio block being placed in four normal radio bursts of the
radio path 170. The LLC frame is formed in accordance with the Figure from a frame header FH, information INFO to be transferred and a frame check sequence FCS. The radio block consists of a block header BH, information INFO to be transferred and a block check sequence BCS, The BH corresponds to the MAC header field MAC HEADER and the RLC header field RLC HEADER in Figure 4A. - The aim of the RLC/MAC protocol layer is thus to divide the LLC frames into smaller blocks so that they can be physically conveyed in the radio blocks over the radio path. The length of one LLC frame can be up to about 1600 octets. The LLC frame can also be very short, in which case the procedure of the invention can be used so that the transmission capacity of the radio block will be efficiently utilized.
- Figure 6 shows in greater detail the structure of the RLC data block which is interesting for the invention. Bits 1-8 forming one octet are shown in the horizontal plane. Octets 1-N are shown in the vertical plane.
Octet 1 comprises a MAC header field so that bits 8-5 include a PC, bit 4 a T and bits 3-1 a USF. Octets 2-4 comprise an RLC header field so that bits 8-2 ofoctet 2 include a TFI (Temporary Flow Identity) andbit 1 an S/P (Supplementary/Polling Bit), bits 8-2 ofoctet 3 include a BSN (Block Sequence Number) andbit 1 an E (Extension Bit) and octet 4 an optional extension field OPT EXT FIELD. Octets 5-N comprise information RLC INFO to be transferred, i.e. the LLC frame data to be transferred. - The TFI is used to identify to which temporary block flow the RLC data block belongs. The network part determines an identifier for each temporary block flow.
- The S/P is used for control and monitoring signalling.
- The BSN is used to show the radio block sequence, where the collected blocks form one LLC frame.
- The E is used to indicate whether the optional extension field is included or not. If the extension bit is not switched on, then all the following information to be transferred is included in one LLC frame. If the extension bit is switched on, then the extension field is included and belongs to the RLC header field.
- The length of the extension field is thus one octet. The first 6 bits form a length indicator LI indicating how many octets from an RLC INFO field belong to the prevailing LLC frame.
- The last byte in the LLC frame can be placed in the middle of the RLC data field, the LI then informing about the location of the last byte of the LLC frame.
- In addition the extension field comprises two bits, the combination of which informs about the contents of a possibly incomplete RLC data field,
- One bit (M) shows whether the same radio block includes another LLC frame. If this is the case, then another bit (C) shows whether the entire second LLC frame is in this radio block or whether it continues in the following radio block.
- Four different states can be indicated by the M and C bits:
- 1. A second LLC frame is found in the same RLC data field, and the entire second LLC frame is in said RLC data field.
- 2. A second LLC frame is found in the same RLC data field and this second LLC frame continues in the RLC data field of the following radio block.
- 3. A second LLC frame is not found in the same radio block but a temporary block flow continues.
- 4. A second LLC frame is not found in the same radio block and the temporary block flow ends.
-
- This prior art definition has several weaknesses:
- In the case of
state 1 the length of the second LLC frame is not defined. Therefore in order to accomplish an operative system thebase station 100 should upon receiving such a radio block transmit, to be sure, all remaining octets in the RLC data block to theSGSN 140 to ensure that theSGSN 140 is able to receive all the octets belonging to the second LLC frame. - In the case of
state 1 unnecessary octets, which do not include any payload associated with the LLC frame, are carried in the uplink direction at the interface between thebase station 100 and thebase station controller 102 and/or at the interface between thebase station controller 102 and theSGSN 140. The capacity of Abis and/or Gb interfaces is thus unnecessarily used. A solution to the problem is to include functions in thebase station system 168 by which the contents of the LLC frame are examined and unnecessary octets are removed from the LLC frame. This is, however, difficult to carry out and does not really fit into the GPRS specifications since the LLC protocol is placed in theSGSN 140 and not in thebase station system 168. - There is such a version of the
state 1 case that the second LLC frame does not entirely fill the RLC data block, in which case the end transmitting the LLC frames cannot entirely utilize the transmission capacity, since there is no mechanism to inform that one or more LLC frames are found in said RLC data block. Valuable radio capacity is thus not fully utilized. - Figure 7A shows how only a
first LLC frame 700 and a second LLC frame can be placed in the first radio block. However, the first radio block has enough space for thethird LLC frame 704, but since there is no mechanism to indicate the presence of a third LLC frame in the first radio block, thethird LLC frame 704 cannot be placed in the RLC data block of the first radio block. Thethird LLC frame 704 is transferred using the RLC data block of the second radio block and the capacity of the RLC data block not used by the first radio block is therefore lost. - Figure 7B shows a procedure of the invention. All three
LLC frames - The procedure in Figure 7B can be implemented in such a manner that the RLC data block includes a mechanism accurately indicating the length of the LLC frame included in each RLC data block and the information on whether another LLC frame will follow after said LLC frame. Figure 7B illustrates a way to implement the mechanism. There, the octet of the RLC data block, in which the preceding LLC frame ends, is always followed by a corresponding extension field than what is determined in accordance with prior art, if a new LLC frame is to be transmitted. This new extension field determines whether there is a next LLC frame in the same RLC data block. Furthermore the extension field determines the length of said LLC frame and whether said LLC frame can fit into the current RLC data block or whether it continues to the next RLC data block. The mechanism described can be applied until the entire RLC data block is filled with LLC frame data and thus the data stream of the LLC frames can be a continuous octet-shaped LLC data stream independent of the RLC data block limits.
- The mechanism presented above is only one example of how more than two LLC frames can, if needed, be placed in one RLC data block. Even though the invention has been described above with reference to the example of the accompanying drawings, it is obvious that the invention is not restricted thereto but can be modified in various ways within the scope of the invention according to the attached claims.
Claims (2)
- A data transmission method between a network part (140, 142, 144, 168) of a General Packet Radio Service and a subscriber terminal (150, 152) comprisingan RLC/MAC (Radio Link Control / Medium Access Control) protocol layer and an LLC (Logical Link Control) protocol layer employing the services of the RLC/MAC protocol layer as data link layers;in data transmission an LLC frame of the LLC layer is placed in an RLC data block of the RLC/MAC layer,
- A cellular network using a general packet radio service comprising:a network part (140, 142, 144, 168) and at least one subscriber terminal (150, 152);data transmission between the network part and the subscriber terminal;the network part and the subscriber terminal being arranged to perform data transmission using a protocol stack where an RLC/MAC (Radio Link Control / Medium Access Control) protocol layer and an LLC (Logical Link Control) protocol layer employing the services of the RLC/MAC protocol layer act as data link layers;the network part and the subscriber terminal being arranged to use transmission units for data transmission in such a manner that an LLC frame of the LLC layer is placed in an RLC data block of the RLC/MAC layer, characterized by the network part and the subscriber terminal being arranged to locate more than two LLC frames (700, 702, 704) in one RLC data block so that the network part and the subscriber terminal are arranged to locate a mechanism in the RLC data block indicating the length of the LLC frame included in the RLC data block and information about whether another LLC frame will follow said LLC frame or not.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DK04103974T DK1489793T3 (en) | 1997-09-12 | 1998-09-11 | Power supply and subscriber terminal from mobile networks using GPRS |
EP04103974A EP1489793B1 (en) | 1997-09-12 | 1998-09-11 | Network part and subscriber terminal of cellular network using GPRS |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FI973681 | 1997-09-12 | ||
FI973681A FI106088B (en) | 1997-09-12 | 1997-09-12 | Method of transmitting data between the network portion of a General Packet Radio Service and a subscriber terminal |
PCT/FI1998/000713 WO1999014963A2 (en) | 1997-09-12 | 1998-09-11 | Data transmission method in gprs |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP04103974A Division EP1489793B1 (en) | 1997-09-12 | 1998-09-11 | Network part and subscriber terminal of cellular network using GPRS |
EP04103974.4 Division-Into | 2004-08-19 |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1013115A2 EP1013115A2 (en) | 2000-06-28 |
EP1013115B1 true EP1013115B1 (en) | 2004-11-17 |
Family
ID=8549525
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP98943921A Expired - Lifetime EP1013115B1 (en) | 1997-09-12 | 1998-09-11 | Data transmission method in gprs |
EP04103974A Expired - Lifetime EP1489793B1 (en) | 1997-09-12 | 1998-09-11 | Network part and subscriber terminal of cellular network using GPRS |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP04103974A Expired - Lifetime EP1489793B1 (en) | 1997-09-12 | 1998-09-11 | Network part and subscriber terminal of cellular network using GPRS |
Country Status (13)
Country | Link |
---|---|
US (1) | US6671287B1 (en) |
EP (2) | EP1013115B1 (en) |
JP (1) | JP3676977B2 (en) |
CN (1) | CN1145383C (en) |
AT (2) | ATE282931T1 (en) |
AU (1) | AU745814C (en) |
DE (2) | DE69827648T2 (en) |
DK (1) | DK1489793T3 (en) |
ES (2) | ES2268576T3 (en) |
FI (1) | FI106088B (en) |
NO (1) | NO326391B1 (en) |
PT (1) | PT1489793E (en) |
WO (1) | WO1999014963A2 (en) |
Families Citing this family (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000021220A1 (en) * | 1998-10-06 | 2000-04-13 | Nokia Networks Oy | Radio link protocol with reduced signaling overhead |
EP1059741A1 (en) * | 1999-06-09 | 2000-12-13 | Lucent Technologies Inc. | Multi-user time-slots for TDMA |
KR100378115B1 (en) * | 1999-07-10 | 2003-03-29 | 삼성전자주식회사 | Apparatus and method for releasing common channel in cdma communication system |
US6865609B1 (en) * | 1999-08-17 | 2005-03-08 | Sharewave, Inc. | Multimedia extensions for wireless local area network |
EP1087570B1 (en) * | 1999-09-22 | 2009-06-24 | Sony Corporation | Data transmission with error correction code and effective transmission time |
FI109438B (en) * | 1999-10-15 | 2002-07-31 | Nokia Corp | A method for transmitting information on a packet data channel |
US6683866B1 (en) * | 1999-10-29 | 2004-01-27 | Ensemble Communications Inc. | Method and apparatus for data transportation and synchronization between MAC and physical layers in a wireless communication system |
US6879599B1 (en) * | 2000-01-31 | 2005-04-12 | Telefonaktlebolaget Lm Ericsson (Publ) | Mapping of transcoder/rate adaptor unit protocols onto user datagram protocols |
US6678281B1 (en) * | 2000-03-08 | 2004-01-13 | Lucent Technologies Inc. | Hardware configuration, support node and method for implementing general packet radio services over GSM |
KR100374337B1 (en) * | 2000-05-24 | 2003-03-04 | 삼성전자주식회사 | Call billing in voice over inter protocol |
US6879573B1 (en) * | 2000-09-15 | 2005-04-12 | Lucent Technologies Inc. | Channel sharing by diverse multiframes in a wireless communications network |
DE10054473A1 (en) * | 2000-11-03 | 2002-05-08 | Siemens Ag | Method for exchanging data packets between two service providers of a radio transmission system |
US6847654B2 (en) * | 2000-11-06 | 2005-01-25 | Symbol Technologies, Inc. | Wireless device which uses an upper MAC and lower MAC interface |
US7092381B2 (en) * | 2000-12-29 | 2006-08-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Delivery of broadcast teleservice messages over packet data networks |
US7136363B2 (en) * | 2001-01-09 | 2006-11-14 | Nokia Corporation | Method and apparatus for improving radio spectrum usage and decreasing user data delay when providing packet PSI status |
WO2002069519A1 (en) * | 2001-02-23 | 2002-09-06 | Nokia Inc. | System and method for fast gprs for ipv6 communications |
US6961349B2 (en) * | 2001-05-30 | 2005-11-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Handling TCP protocol for connections transmitted in parallel over radio link |
EP1267512A1 (en) * | 2001-06-15 | 2002-12-18 | Ascom AG | Transmission quality determination |
KR100389819B1 (en) * | 2001-07-09 | 2003-07-02 | 삼성전자주식회사 | Method for transmitting packet data in cdma wireless communication system |
US7142591B2 (en) * | 2001-10-11 | 2006-11-28 | Utstarcom, Inc. | Method and system for oversubscribing a pool of modems |
US7142590B2 (en) * | 2001-10-11 | 2006-11-28 | Utstarcom Inc. | Method and system for oversubscribing a DSL modem |
KR100842651B1 (en) * | 2002-02-05 | 2008-06-30 | 삼성전자주식회사 | Data block sending/receiving method for radio link control of general packet radio service |
US20040097267A1 (en) * | 2002-11-18 | 2004-05-20 | Pecen Mark E. | Method and apparatus for virtual bearer |
RU2364025C2 (en) * | 2002-11-18 | 2009-08-10 | Моторола, Инк. | Method and device for virtual unidirectional channel |
JP2005064961A (en) * | 2003-08-15 | 2005-03-10 | Sony Ericsson Mobilecommunications Japan Inc | Radio communication system and repeater |
US7391758B2 (en) * | 2004-09-29 | 2008-06-24 | Intel Corporation | UMTS radio link control with full concatenation |
WO2007001204A1 (en) * | 2005-06-29 | 2007-01-04 | Intel Corporation | Wireless data transmission methods, devices, and systems |
GB2435153A (en) | 2006-02-08 | 2007-08-15 | Nec Corp | Modified connection setup for E-UTRA radio resource control |
CN101127145B (en) * | 2006-08-16 | 2010-07-14 | 北京车灵通科技发展有限公司 | Alarm system and vehicle alarming method based on the alarm system |
EP2174516B1 (en) | 2007-05-15 | 2015-12-09 | Broadcom Corporation | Transporting gsm packets over a discontinuous ip based network |
WO2012018225A2 (en) * | 2010-08-03 | 2012-02-09 | Samsung Electronics Co., Ltd. | Method and apparatus of communicating packet data units in a wireless network environment and system using thereof |
US8938551B2 (en) * | 2012-04-10 | 2015-01-20 | Intel Mobile Communications GmbH | Data processing device |
CN103974359B (en) * | 2013-02-05 | 2017-12-05 | 英特尔公司 | With LTE and the CDMA 1X devices to communicate and method |
US10154540B2 (en) * | 2013-03-29 | 2018-12-11 | Intel Corporation | LTE-1x hybrid device and system |
RU2639951C1 (en) * | 2015-01-27 | 2017-12-25 | Телефонактиеболагет Лм Эрикссон (Пабл) | Transmitter, receiver, control unit and related methods for transmitting unit to receiver |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5533021A (en) * | 1995-02-03 | 1996-07-02 | International Business Machines Corporation | Apparatus and method for segmentation and time synchronization of the transmission of multimedia data |
JP3139737B2 (en) * | 1996-07-31 | 2001-03-05 | 日本電気株式会社 | Data communication system |
US6031832A (en) * | 1996-11-27 | 2000-02-29 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for improving performance of a packet communications system |
FI104874B (en) * | 1997-03-27 | 2000-04-14 | Nokia Networks Oy | Procedure for controlling packet traffic |
FI104877B (en) * | 1997-03-27 | 2000-04-14 | Nokia Networks Oy | Resource reservation mechanism in a packet radio network |
US6608832B2 (en) * | 1997-09-25 | 2003-08-19 | Telefonaktiebolaget Lm Ericsson | Common access between a mobile communications network and an external network with selectable packet-switched and circuit-switched and circuit-switched services |
FI105760B (en) * | 1997-10-30 | 2000-09-29 | Nokia Mobile Phones Ltd | Cellular Subnet Dependent Convergence Protocol |
FI109317B (en) * | 1998-04-17 | 2002-06-28 | Nokia Corp | A method for determining billing information in a mobile communication system and a mobile station |
US6320873B1 (en) * | 1998-08-27 | 2001-11-20 | Qualcomm Incorporated | CDMA transmission of packet-switched data |
FI107425B (en) * | 1999-03-16 | 2001-07-31 | Nokia Mobile Phones Ltd | Method and arrangement for transporting multimedia-related information in a cellular radio network |
SE515456C2 (en) * | 1999-12-16 | 2001-08-06 | Ericsson Telefon Ab L M | Configuration method for interface of serving general packet radio service (GPRS) supports node and base station system using transmitted cancellation signal to update data structures in serving GPRS support node |
FI109863B (en) * | 2000-01-26 | 2002-10-15 | Nokia Corp | Locating a subscriber terminal in a packet switched radio system |
-
1997
- 1997-09-12 FI FI973681A patent/FI106088B/en not_active IP Right Cessation
-
1998
- 1998-09-11 PT PT04103974T patent/PT1489793E/en unknown
- 1998-09-11 AU AU91647/98A patent/AU745814C/en not_active Expired
- 1998-09-11 DK DK04103974T patent/DK1489793T3/en active
- 1998-09-11 DE DE69827648T patent/DE69827648T2/en not_active Expired - Lifetime
- 1998-09-11 AT AT98943921T patent/ATE282931T1/en not_active IP Right Cessation
- 1998-09-11 ES ES04103974T patent/ES2268576T3/en not_active Expired - Lifetime
- 1998-09-11 EP EP98943921A patent/EP1013115B1/en not_active Expired - Lifetime
- 1998-09-11 WO PCT/FI1998/000713 patent/WO1999014963A2/en active IP Right Grant
- 1998-09-11 AT AT04103974T patent/ATE333740T1/en active
- 1998-09-11 CN CNB988090341A patent/CN1145383C/en not_active Expired - Lifetime
- 1998-09-11 EP EP04103974A patent/EP1489793B1/en not_active Expired - Lifetime
- 1998-09-11 ES ES98943921T patent/ES2232019T3/en not_active Expired - Lifetime
- 1998-09-11 DE DE69835307T patent/DE69835307T2/en not_active Expired - Lifetime
- 1998-09-11 JP JP2000512369A patent/JP3676977B2/en not_active Expired - Lifetime
-
2000
- 2000-03-07 US US09/519,971 patent/US6671287B1/en not_active Expired - Lifetime
- 2000-03-10 NO NO20001284A patent/NO326391B1/en not_active IP Right Cessation
Also Published As
Publication number | Publication date |
---|---|
FI973681A (en) | 1999-03-13 |
EP1489793A1 (en) | 2004-12-22 |
DE69835307T2 (en) | 2007-07-19 |
FI106088B (en) | 2000-11-15 |
DE69827648T2 (en) | 2005-11-10 |
CN1270743A (en) | 2000-10-18 |
JP2001517045A (en) | 2001-10-02 |
ES2268576T3 (en) | 2007-03-16 |
PT1489793E (en) | 2006-10-31 |
DE69827648D1 (en) | 2004-12-23 |
AU745814C (en) | 2002-11-28 |
FI973681A0 (en) | 1997-09-12 |
NO20001284L (en) | 2000-03-10 |
CN1145383C (en) | 2004-04-07 |
EP1013115A2 (en) | 2000-06-28 |
ATE282931T1 (en) | 2004-12-15 |
NO20001284D0 (en) | 2000-03-10 |
WO1999014963A3 (en) | 1999-05-06 |
DK1489793T3 (en) | 2006-10-02 |
US6671287B1 (en) | 2003-12-30 |
AU9164798A (en) | 1999-04-05 |
EP1489793B1 (en) | 2006-07-19 |
ES2232019T3 (en) | 2005-05-16 |
ATE333740T1 (en) | 2006-08-15 |
DE69835307D1 (en) | 2006-08-31 |
JP3676977B2 (en) | 2005-07-27 |
WO1999014963A2 (en) | 1999-03-25 |
NO326391B1 (en) | 2008-11-24 |
AU745814B2 (en) | 2002-04-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1013115B1 (en) | Data transmission method in gprs | |
US7193988B2 (en) | Allocating Abis interface transmission channels in packet cellular radio network | |
CA2318480C (en) | Method for connection reconfiguration in cellular radio network | |
AU752200B2 (en) | Methods and apparatus for improved base station transceivers | |
EP1692818B1 (en) | Access to cdma/umts services over a wlan access point, using a gateway node between the wlan access point and the service providing network | |
US6879599B1 (en) | Mapping of transcoder/rate adaptor unit protocols onto user datagram protocols | |
US6813280B2 (en) | Method for connection establishment in a radio system relaying packet-switched traffic | |
US6826168B2 (en) | System and method relating to digital mobile communication systems | |
US20050013247A1 (en) | Method for controlling data transmission, and data transmission system | |
FI105985B (en) | The method identifies an air interface network layer protocol information unit in a cellular radio network | |
EP2237605B1 (en) | Transmitting service information without establishing a connection | |
FI104875B (en) | Data communication method in a base station system in a cellular radio network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20000303 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA CORPORATION |
|
17Q | First examination report despatched |
Effective date: 20031202 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20041117 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20041117 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: NV Representative=s name: ICB INGENIEURS CONSEILS EN BREVETS SA Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REF | Corresponds to: |
Ref document number: 69827648 Country of ref document: DE Date of ref document: 20041223 Kind code of ref document: P |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20050217 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20050217 |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: TRGR |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2232019 Country of ref document: ES Kind code of ref document: T3 |
|
ET | Fr: translation filed | ||
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20050911 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20050912 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20050930 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20050930 |
|
26N | No opposition filed |
Effective date: 20050818 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20050417 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: CH Payment date: 20100914 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: SE Payment date: 20100913 Year of fee payment: 13 Ref country code: IT Payment date: 20100918 Year of fee payment: 13 Ref country code: FR Payment date: 20100921 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20100908 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20100910 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20100908 Year of fee payment: 13 Ref country code: BE Payment date: 20100915 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20101018 Year of fee payment: 13 |
|
BERE | Be: lapsed |
Owner name: *NOKIA CORP. Effective date: 20110930 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: V1 Effective date: 20120401 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20110911 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110911 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20120531 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110930 |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: EUG |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 69827648 Country of ref document: DE Effective date: 20120403 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20120401 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110930 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110930 Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20120403 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110930 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110911 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FD2A Effective date: 20130417 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110912 Ref country code: SE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110912 |