Data transmission method and arrangement
Claim Score by NHIP
Abstract
The invention relates to implementing data transmission between at least two sets of software used in one or more devices which comprise means for establishing a connection to a telecommunications system. The communication is partly carried out with method calls including a service request. A service broker supplies the service request included in the method call to indicated server, which responds to the method call by sending required information back to the sender of the method call via the service broker. At least some of the programs participating in data transmission are implemented with a script-based programming language in the devices. The arrangement comprises an application which transmits service requests and responses to the requests between the service broker and the software that needs data transmission, and renders data transmission requests and responses to the requests compatible between script-based software and another system.

Term
Term ended
Projected expiry passed 14 July 2023, 3.2 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
8 claims: 2 independent, 6 dependent
- 1Broadest claimClaim Score 43, average(NHIP)An arrangement for implementing data transmission between at least two sets of software which are used in one or more devices which comprise means for establishing a connection to a telecommunications system, in which arrangement at least a portion of a connection between two different devices is implemented with a wireless connection, and in which arrangement at least part of the communication between the devices is carried out by method calls, each of which includes a service request, and the system comprising one or more service brokers which supply the service request included in the method call to the server indicated, which is arranged to respond to the method call according to the service needed by sending information required by the service to the service broker, which is arranged to send the information to the sender of the method call, and a server that offers the service request being defined during the communication, and in which arrangement at least some of the programs used in the devices and participating in data transmission are implemented with a script-based programming language, where in the arrangement comprises an application which transmits service requests and responses to the requests between the service broker and the software that needs data transmission and renders data transmission requests and responses to the requests compatible between script-based software and another system.
- 5A method of implementing data transmission between at least two sets of software which are used in one or more devices which are able to establish a connection to a telecommunications system, the method comprising implementing at least a portion of a connection between two different devices with a wireless connection, carrying out at least part of the communication between the sets of software by means of method calls, each of which includes a service request, supplying said method call to a service broker of the system which supplies the service request included in the method call to the server indicated, which responds to the method call according to the service needed by sending the information required by the service to the service broker which sends the information to the sender of the method call, defining the server that offers the service request during the communication, implementing with a script-based programming language at least some of the programs used in the devices and participating in data transmission, sending the method calls to a certain application by the program used in the device employing wireless connections, the application transmitting service requests and responses to the requests between the service broker and the software that needs data transmission by the application and the application rendering data transmission requests and responses to the requests compatible between script-based software and another system.
Independent claims2
46 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
P-0001[0001] The invention relates to a data transmission method and arrangement in which data are transmitted between a wireless system and another system. The invention particularly relates to systems in which data are transmitted between sets of software in different devices.
BACKGROUND OF THE INVENTION
P-0002[0002] In the design and maintenance of telecommunications systems attention has been paid to establishment of connections between different systems and to smooth operation. Separate systems have often been implemented using quite a few different methods and various apparatuses which are incompatible. It has been difficult and time consuming to make different systems compatible, if at all possible.
P-0003[0003] For this reason several producers of devices and systems have developed a common architecture called CORBA (Common Object Request Broker Architecture), which allows computer systems of different types implemented with different programming languages to communicate with one another without difficulty. CORBA defines a GIOP protocol (General Inter-ORB protocol) which enables communication between devices of different types and programs programmed with different languages. The GIOP protocol is a common protocol of which a version called IIOP (Internet Inter-ORB Protocol) has been developed particularly for the Internet environment. Further information on CORBA can be obtained e.g. from the specification published by the OMG (Object Management Group) which created this architecture: The Common Object Request Broker: Architecture and Specification, Revision 2.0, Chapter 2: CORBA Overview. The specification is also available at the address www.omg.org.
P-0004[0004] CORBA has been developed for systems which have a fixed connection to one another via an unspecified network. When the protocol was designed, hardly any attention was paid to the possible capacity of the transmission path, but the emphasis was on the creation of a flexible and secure protocol. Since the proportion of wireless communication has increased strongly during the past few years, data systems and different software are also increasingly used in computers and devices from which the only or the main connection to other networks is a wireless network, such as the GSM, GPRS or UMTS. The data transmission capacity of wireless networks is, however, considerably smaller than that of fixed wired networks. For this reason CORBA has not been commonly applied to wireless systems. Transmission of CORBA over a wireless transmission path has proven to be very slow due to the large amount of signalling and data to be transmitted.
P-0005[0005] In wireless devices software applications have usually defined their own interfaces and connection protocol which have been directly involved in the actual data transmission. This is illustrated in FIG. 1. The figure shows three software applications <b>100</b> to <b>104</b> which run in a device employing a wireless connection. Each software application has a connection protocol <b>106</b> to <b>110</b> of its own which it uses to communicate with a transmission layer <b>112</b>, which transmits data using a wireless connection. In this solution the applications need to communicate with the transmission layer, which makes development of the application difficult.
BRIEF DESCRIPTION OF THE INVENTION
P-0006[0006] An object of the invention is to provide a method and an arrangement implementing the method to alleviate the above-mentioned problems. This is achieved with a method of implementing data transmission between at least two sets of software used in one or more devices which are able to establish a connection to a telecommunications system, the method comprising implementing at least a portion of a connection between two different devices with a wireless connection and carrying out at least part of the communication between the sets of software by method calls, each of which includes a service request, the method call being supplied to a service broker of the system, which supplies the service request included in the method call to the server indicated, which responds to the method call according to the service requested by sending the information required by the service to the service broker, which sends the information to the sender of the method call, and the method comprising defining the server that offers the service request during the communication, and at least some of the programs used in the devices and participating in data transmission being implemented with a script-based programming language.
P-0007[0007] In the method according to the invention the program used in a device employing wireless connections sends method calls to a certain application, which transmits service requests and responses to the requests between the service broker and the software that needs data transmission and renders the data transmission requests and responses to the requests compatible between script-based software and another system.
P-0008[0008] The invention also relates to an arrangement for implementing data transmission between at least two sets of software used in one or more devices which comprise means for establishing a connection to a data transmission system, where at least a portion of a connection between two different devices is implemented with a wireless connection and at least part of the communication between the devices is carried out by method calls, each of which includes a service request, the system comprising one or more service brokers which supply the service request included in the method call to the server indicated, which is arranged to respond to the method call according to the service needed by sending the information requested by the service to the service broker, which is arranged to send the information to the sender of the method call, the server that offers the service request being defined during the communication and at least some of the programs used in the devices and participating in data transmission being implemented with a script-based programming language.
P-0009[0009] The arrangement of the invention comprises an application which transmits service requests and responses to the requests between the service broker and the software requiring data transmission and renders the data transmission requests and responses to the requests compatible between script-based software and another system.
P-0010[0010] The dependent claims disclose the preferred embodiments of the invention.
P-0011[0011] The invention is based on implementing software in wireless devices which adapt the requests needed by the services used by the sets of software in the wireless devices and responses to the requests between a wireless device and another external system so that various sets of software can use the same protocol and the same messages. The wireless device comprises an application of its own which converts the request generated by the software in the wireless device into a format compatible with another system, and in the other direction a response received from the system is converted into a format understood by the software in the wireless device. The application may convert a protocol used in a fixed network, e.g. a GIOP protocol, into a format that can be transmitted better on a wireless transmission path.
P-0012[0012] The method and arrangement of the invention provide several advantages. Since the invention enables use of the same protocol in several software applications in wireless devices, the protocol not being dependent on the transmission layer and having a basic structure similar to that in a fixed network, the development of software and implementation of communication will become considerably simpler, without causing too much load on the transmission path or without rendering the connection impractically slow.
BRIEF DESCRIPTION OF THE DRAWINGS
P-0013[0013] The invention will be described in greater detail by means of preferred embodiments with reference to the accompanying drawings, in which
P-0014[0014]FIG. 1 illustrates prior art application protocols described above,
P-0015[0015]FIG. 2 illustrates the structure of a mobile communications system used as an example,
P-0016[0016]FIG. 3 illustrates the structure of the mobile communications system used as an example in greater detail,
P-0017[0017]FIG. 4 illustrates CORBA architecture at a general level,
P-0018[0018]FIG. 5 illustrates a solution according to a preferred embodiment of the invention,
P-0019[0019]FIG. 6 illustrates the function of a solution according to a preferred embodiment of the invention,
P-0020[0020]FIG. 7 illustrates a solution according to another preferred embodiment of the invention, and
P-0021[0021]FIG. 8 illustrates the structure of a device suitable for use in an arrangement according to the invention.
DETAILED DESCRIPTION OF THE INVENTION
P-0022[0022] The present invention can be applied in various radio systems where the terminals have different radio path properties. It does not matter which multiple access method the system employs. For example, the CDMA, WCDMA and TDMA can be used as the multiple access method. Furthermore, the system can support both circuit-switched and packet-switched connections.
P-0023[0023] The structure of a mobile communications system according to an embodiment of the invention used as an example will be described with reference to FIG. 2. This is only one possible alternative, which is obvious to a person skilled in the art. The main parts of the mobile communications system are a core network CN, an overground radio access network BSS and a subscriber terminal MS. The interface between the CN and the BSS is called a Gb interface in this example, and the air interface between the BSS and the MS a UM interface.
P-0024[0024] The radio access network consists of radio network subsystems RNS. Each radio network subsystem RNS consists of a radio network controller RNC and a base station B comprising one or more transceivers. The interface between the radio network controller and the base station is called a lub interface. The coverage area of the base station, i.e. a cell, is denoted by C in FIG. 1.
P-0025[0025] The illustration in FIG. 2 is rather abstract, and thus it will be clarified in FIG. 3 with a more detailed example of a cellular radio system. FIG. 3 includes only the most essential blocks, but it is obvious to a person skilled in that art that a conventional cellular radio network also comprises other functions and structures that need not be discussed more closely in this context. It should also be noted that FIG. 3 exemplifies only one possible structure. In systems according to the invention the details may differ from those shown in FIG. 3 but these differences are irrelevant to the invention.
P-0026[0026] The cellular radio network typically comprises the infrastructure of a fixed network, i.e. a network part <b>300</b> and subscriber terminals <b>302</b> which can be fixed, placed in a vehicle or portable. The network part <b>300</b> comprises base stations <b>304</b>. The base station corresponds to node B in the preceding figure. Several base stations <b>304</b> are controlled centrally by a radio network controller <b>306</b> which communicates with the base stations. A base station <b>304</b> comprises transceivers <b>308</b> and a multiplexer unit <b>312</b>.
P-0027[0027] The base station <b>304</b> also comprises a control unit <b>310</b> which controls the function of the transceivers <b>308</b> and the multiplexer <b>312</b>. The multiplexer <b>312</b> is used for arranging the traffic and control channels used by several transceivers <b>308</b> on one transmission connection <b>314</b>. The transmission connection <b>314</b> constitutes the lub interface.
P-0028[0028] There is a connection from the transceivers <b>308</b> of the base station <b>304</b> to an antenna unit <b>318</b> which establishes a bi-directional radio connection <b>316</b> to the subscriber terminal <b>302</b>. The structure of the frames to be transmitted on the bi-directional radio connection <b>316</b> is system-specific and called an air interface Um.
P-0029[0029] The radio network controller <b>306</b> comprises a group switching field <b>320</b> and a control unit <b>322</b>. The group switching field <b>320</b> is used for switching speech and data and for connecting signalling circuits. The radio network subsystem <b>332</b> formed by the base station <b>304</b> and the radio network controller <b>306</b> also includes a transcoder <b>324</b>. The transcoder <b>324</b> is usually located as close to a mobile services switching centre <b>328</b> as possible because this saves transmission capacity when speech is transmitted in the format of a cellular radio network between the transcoder <b>324</b> and the radio network controller <b>306</b>.
P-0030[0030] The transcoder <b>324</b> converts the different digital speech encoding formats used between the public switched telephone network and the radio telephone network into a compatible format, e.g. from the format of the fixed network into a format of the cellular radio network, and vice versa. The control unit <b>322</b> is responsible for call controlling, mobility management, collection of statistics and signalling.
P-0031[0031]FIG. 3 further illustrates a mobile services switching centre <b>328</b> and a gateway mobile services switching centre <b>330</b> which is responsible for external connections of the mobile communications system, in this case for the connection to the public switched telephone network <b>336</b>.
P-0032[0032] As is seen in FIG. 3, the group switching field <b>320</b> can establish connections both to the public switched telephone network (PSTN) <b>336</b> via the mobile services switching centre <b>328</b> and to a packet transmission network <b>342</b>.
P-0033[0033] The connection between the packet transmission network <b>342</b> and the group switching field <b>320</b> is established by a support node <b>340</b> (SGSN =Serving GPRS Support Node). The function of the support node <b>340</b> is to transmit packets between the base station system and a gateway node (GGSN=Gateway GPRS Support Node) <b>344</b> and keep a record of the location of the subscriber terminal <b>302</b> in its area.
P-0034[0034] The gateway node <b>344</b> connects a public packet transmission network <b>346</b> and the packet transmission network <b>342</b>. An Internet protocol or an X.25 protocol can be used at the interface. The gateway node <b>344</b> hides the internal structure of the packet transmission network <b>342</b> from the public packet transmission network <b>346</b> by encapsulating the structure, and thus the public packet transmission network <b>346</b> regards the packet transmission network <b>342</b> as a sub-network which comprises a subscriber terminal <b>302</b> to which the public packet transmission can send packets and receive packets from it.
P-0035[0035] The packet transmission network <b>342</b> is typically a private network which utilizes the Internet protocol and carries signalling and tunnelled user data. The structure of the network <b>342</b> may vary according to the operator in respect of its architecture and protocols below the Internet protocol layer.
P-0036[0036] The public packet transmission network <b>346</b> may be e.g. the worldwide Internet network.
P-0037[0037] Typically time slots not involved in circuit-switched transmission are used for packet transmission at the air interface <b>316</b>. The capacity is reserved dynamically for packet transmission, i.e. as a data transmission request is received, any free channel can be allocated to packet transmission. The arrangement is flexible, which means that circuit-switched connections have priority over packet transmission connections. If necessary, circuit-switched transmission overrides packet-switched transmission, i.e. the time slot used by packet-switched transmission is allocated to circuit-switched transmission. This can be done because packet-switched transmission withstands such interruptions well: transmission is continued using another allocated time slot. The arrangement can also be implemented so that no absolute priority is given to circuit-switched transmission but both circuit-switched and packet-switched transmission requests are served in their order of arrival. These arrangements are not, however, relevant to the present invention.
P-0038[0038] In the following, data transmission according to the CORBA architecture will be described at a general level by means of FIG. 4. FIG. 4 shows a wireless device <b>400</b> with an ongoing software application <b>402</b>. The application needs a service, e.g. information from a database, and it sends a method call in which this service is defined. The device comprises another service broker application which is called an ORB (Object Request Broker) <b>404</b> and processes method calls from different applications. The ORB searches for the address of the service provider (suitable server) by sending a call to a CORBA name server <b>412</b>. Having received a response, the ORB transmits the call to the server in question. In the case of FIG. 4 a suitable server is not found under the same ORB and thus the call is forwarded to a service broker application <b>408</b> of another device <b>406</b>, which transmits the call to a suitable server <b>410</b> with which it communicates, the server being typically another software application. This server supplies a response which is transmitted to the original software application <b>402</b>. The software application <b>402</b> does not know the actual location of the server, but receives information only on the surrounding environment through method calls. The service brokers and the sets of software can be implemented with different programming languages and in different apparatuses. During data transmission protection procedures related to the parties to data transmission are carried out in accordance with the CORBA architecture.
P-0039[0039]FIG. 5 illustrates a solution according to a preferred embodiment of the invention. The figure illustrates a device <b>500</b> which utilizes a wireless connection. An application <b>502</b> which is able to communicate is running in the device. The application is implemented by means of a script-based programming language, such as JavaScript or WMLScript. The application typically functions under browser software utilizing Internet connections. The device also typically comprises one or more service brokers <b>504</b> which supply a service request included in a method call to the indicated server, which is arranged to respond to the method call. The indicated server may be in another device. If the application needs a service, it sends a method call. The device comprises an adapter application <b>506</b> which recognizes method call parameters in a script-based method call. The application generates the method call in a format understood by the service broker and transmits it to the service broker <b>504</b>. If necessary, the service broker forwards the call to software <b>508</b> to be run in another device <b>510</b>. The software performs the desired service and returns a response via its own object adapter <b>518</b>. The object adapter belongs to the CORBA architecture and adapts the method messages of the server for the service broker. Transmission takes place by means of communication devices <b>512</b> and <b>514</b> on a transmission path <b>516</b>. The transmission path may be a radio path of a cellular radio system, another radio link such as Bluetooth, a link implemented by means of packet-switched traffic (GPRS) or an infrared link.
P-0040[0040] The application <b>506</b> is preferably implemented by a library application. The library application provides the necessary functions for a script-based application for sending method calls. The functions convert outgoing method calls into a general format understood by the service broker and in the other direction the messages entering the application are converted into script calls.
P-0041[0041] The function of the application is shown in FIG. 6, which schematically illustrates a library application <b>506</b>. A method call <b>600</b> sent by the script software is converted into a general message format <b>602</b> by a library function, whereas a message <b>604</b> entering the script software is converted into a script call <b>606</b> by the library function. This can be implemented e.g. by tabulating method calls and their parameters and response values. The library recognizes the correct message formats in the outgoing messages by means of the table. Incoming messages <b>604</b> typically include the name of the function, which makes conversion easy.
P-0042[0042]FIG. 7 illustrates another preferred embodiment of the invention. The figure is similar to FIG. 5, except that in this embodiment the adapter application is integrated into the communication devices, preferably forming part of the control software of the communication devices. This solution has the advantage that the complexity and memory need of the device decrease.
P-0043[0043]FIG. 8 illustrates the structure of a wireless system in which the solution according to the preferred embodiments of the invention can be implemented. The device comprises an antenna <b>818</b> for transmitting and receiving signals. From the antenna a signal is supplied to a duplex filter which separates the signals of the transmission direction from the signals of the reception direction. The receiver <b>800</b> comprises a filter which prevents frequencies outside the desired frequency band. After this, the signal is converted into an intermediate frequency or directly into the baseband in which form a signal is sampled and quantized in an analogue/digital converter <b>802</b>. An equalizer <b>804</b> compensates for interference, e.g. interference caused by multi-path propagation. A demodulator <b>806</b> picks up a bit flow from an equalized signal and transmits the flow to a demultiplexer <b>808</b>. The demultiplexer <b>808</b> separates the bit flow from different time slots into separate logical channels. A channel codec <b>816</b> decodes the bit flow of different logical channels, i.e. decides whether the whole bit flow consists of signalling information which is transmitted to a control unit <b>814</b>, or whether the bit flow consists of speech which is forwarded <b>840</b> e.g. to a speech decoder. The channel codec <b>816</b> also corrects errors. The control unit <b>814</b> performs internal control tasks by controlling different units. A burst generator <b>828</b> adds a training sequence and tail bits to the data received from the channel codec <b>816</b>. A multiplexer <b>826</b> indicates a time slot for each burst. A modulator <b>824</b> modulates digital signals to a radio-frequency carrier wave. This function is analogue and thus a digital/analogue converter <b>822</b> is needed to perform it. A transmitter <b>820</b> comprises a filter for limiting the band width. The transmitter <b>820</b> also controls the output power of transmission. A synthesizer <b>812</b> provides different units with the necessary frequencies. The clock of the synthesizer <b>812</b> may be controlled locally. The synthesizer <b>812</b> generates the necessary frequencies e.g. by a voltage-controlled oscillator.
P-0044[0044] As illustrated in FIG. 8, the structure of a transceiver can be further divided into radio frequency parts <b>830</b> and a digital signal processing processor with software <b>832</b>. The radio frequency parts <b>830</b> comprise the receiver <b>800</b>, transmitter <b>820</b> and synthesizer <b>812</b>. The digital signal processing processor and its software <b>832</b> include the equalizer <b>804</b>, demodulator <b>806</b>, demultiplexer <b>808</b>, channel coded <b>816</b>, control unit <b>814</b>, burst generator <b>828</b>, multiplexer <b>826</b> and modulator <b>824</b>. The analogue/digital converter <b>802</b> is needed to convert an analogue radio signal into a digital radio signal and the digital/analogue converter <b>822</b> is needed to convert a digital signal into an analogue signal.
P-0045[0045] The device may also comprise user interface parts, such as a display, keyboard, earpiece and microphone. These are not shown in the figure. The control unit <b>814</b> of the device is typically implemented with a microprocessor and memory elements, including the necessary software. The control unit can be used for performing sets of software that need different services, as described above.
P-0046[0046] Even though the invention has been described with reference to the examples according to the accompanying drawings, it is clear that the invention is not limited thereto but may be modified in various ways within the inventive concept disclosed in the appended claims.
Contents5
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US7499455B2 | Cited by | United States of America | Search report |
| US9754303B1 | Cited by | United States of America | Applicant |
| US8341281B2 | Cited by | United States of America | Applicant |
| US8131845B1 | Cited by | United States of America | Search report |
| US7668144B2 | Cited by | United States of America | Search report |
| KR101114175B1 | Cited by | Republic of Korea | Search report |
| US9590872B1 | Cited by | United States of America | Applicant |
| US2002191574A1 | Cited by | United States of America | Pre-grant |
| US7792981B2 | Cited by | United States of America | Applicant |
| US2005213583A1 | Cited by | United States of America | Pre-grant |
| US2005005022A1 | Cited by | United States of America | Pre-grant |
| US9612815B1 | Cited by | United States of America | Search report |
| US2011004694A1 | Cited by | United States of America | Pre-grant |
| US2001034771A1 | Cites | United States of America | Pre-grant |
| US2004111730A1 | Cites | United States of America | Pre-grant |
| US5754774A | Cites | United States of America | Pre-grant |
| US6032199A | Cites | United States of America | Pre-grant |
| US6134559A | Cites | United States of America | Pre-grant |
| US6282581B1 | Cites | United States of America | Pre-grant |
| US6330598B1 | Cites | United States of America | Pre-grant |
| US6425017B1 | Cites | United States of America | Pre-grant |
| US6510550B1 | Cites | United States of America | Pre-grant |
| USH1964H | Cites | United States of America | Pre-grant |
7 members in 4 offices
Priority claims1
| Document | Office | Kind | Date |
|---|---|---|---|
| 20001617 | Finland | A |
Members7
| Document | Office | Kind | |
|---|---|---|---|
| FI20001617A0 | Finland | A0 | |
| FI20001617A | Finland | A | |
| US2002004818A1 | United States of America | A1 | |
| WO0205090A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU8216501A | Australia | A | |
| WO0205090A8 | World Intellectual Property Organization (WIPO) | A8 | |
| US6842771B2 | United States of America | B2 |
36 transactions on the USPTO file
Allowed without a rejection on record.
- Non-final rejections
- 0
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Request to Make of Record Noted Concerns in Granted PatentC/MK | C/MK | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Receipt into PubsR1021 | R1021 | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Receipt into PubsR1021 | R1021 | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail-Petition Decision - GrantedMPTGR | MPTGR | |
| Receipt into PubsR1021 | R1021 | |
| Petition EnteredPET. | PET. | |
| Workflow - File Sent to ContractorSENT | SENT | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Mail Examiner's AmendmentMEX.A | MEX.A | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment Communication | – | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) Filed | – | |
| Information Disclosure Statement (IDS) Filed | – | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Correspondence Address ChangeC.AD | C.AD | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) Filed | – | |
| Information Disclosure Statement (IDS) Filed | – | |
| IFW Scan & PACR Auto Security Review | – | |
| Request for Foreign Priority (Priority Papers May Be Included)RQPR | RQPR | |
| Preliminary AmendmentA.PE | A.PE | |
| Initial Exam Team nnIEXX | IEXX |
5 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Lapse for failure to pay maintenance feesLapsedLAPS | LAPS | |
| Maintenance fee reminder mailedREMI | REMI | |
| AssignmentAS | AS |
Numbers
- Application
- 89816901
Titles
- English
- Data transmission method and arrangement
Patent term adjustment
- A delay
- +741 daysthe office missed an examination deadline
- Net adjustment
- 741 days
Classification
- CPC, 5
- H04L67/02
- H04L67/04
- H04L69/08
- H04L67/562
- H04L67/565
- IPC, 2
- H04L29 06
- H04L29 08