CN1449614A - Method and apparatus for a mobile station application to identify specified status messages - Google Patents
Method and apparatus for a mobile station application to identify specified status messages Download PDFInfo
- Publication number
- CN1449614A CN1449614A CN01807775A CN01807775A CN1449614A CN 1449614 A CN1449614 A CN 1449614A CN 01807775 A CN01807775 A CN 01807775A CN 01807775 A CN01807775 A CN 01807775A CN 1449614 A CN1449614 A CN 1449614A
- Authority
- CN
- China
- Prior art keywords
- mobile radio
- radio station
- described mobile
- station application
- application interface
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- 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/02—Terminal devices
Abstract
The present invention discloses a method and apparatus for a mobile station application to identify specified status messages in a wireless communication system. The present invention includes an application program interface (API) that facilitates communications between a mobile station communication protocol stack, which communicates with a communication network, and a mobile station application. The mobile station application calls a function. The API selects at least one of specified status messages based on its state and the function called. The API then reports to the mobile station application the selected specified status messages.
Description
Background of invention
1. invention field
The present invention relates to wireless communication field.The invention particularly relates to the method and apparatus that in wireless communication system, makes mobile radio station use the novelty that to discern designated state message.
2. description of Related Art
A. wireless communication system
Recent innovation in radio communication and the technology relevant with computer, and the unprecedented growth of internet subscriber has been paved road for mobile computing.In fact, mobile computing popularizes the bigger demand proposed current the Internet infrastructure so that more support to be provided to the mobile subscriber.The lifeline of this foundation structure provides the Internet protocol (IP) towards grouping of various services, comprises the addressing and the route of the grouping (datagram) between local and Wide Area Network (LAN and WAN).At the Internet Standard (draft) 791 (RFC) in September, 1981, defined the IP agreement in " INTERNET PROTOCOL DARPA INTERNETPROGRAM PROTOCOL SPECIFICATION " by name.
Described IP agreement is a network layer protocol, becomes the IP grouping to be used for transmission data encapsulation.Addressing and routing iinformation invest the stem of described grouping.For example, the IP stem comprises the 32-bit addresses that identification sent and received main frame.Use these addresses by intermediate router, be path that leads to the final destination at place, plan address by network of this minute group selection.Thereby the grouping that described IP agreement allows any the Internet nodes in the world to send is routed to any in the world other the Internet nodes.On the other hand, use transport layer to be engaged in application-specific, described transport layer comprises transmission control protocol (TCP) or User Datagram Protoco (UDP) (UDP).
Mobile subscriber's current trend is together with the Wireless Telecom Equipment such as Cellular Networks or pocket telephone, uses the mobile computer access the Internet such as on knee or palmtop computer.That is to say, as the user use routinely " wired " communication equipment with its computer with land-based network is connected, the mobile subscriber is commonly referred to use " mobile radio station " Wireless Telecom Equipment (MS) and moves it terminal and be connected with such network.As used herein, described mobile radio station or MS refer to any subscriber station in the public radio net.
Fig. 1 (prior art) has illustrated the high level block diagram of wireless data communication system, and wherein mobile radio station 110 is communicated by letter with IWF (IWF) 108 by (BS/MSC) 106 of base station/mobile switching centre.Described IWF108 is as the access points of internet.IWF108 is coupled to BS/MSC106, and is in same place with it usually, and such as known in the art described BS/MSC 106 can be conventional wireless base station.Another standard agreement of being devoted to wireless data communication system is that the 3rd generation partner plans 2 (" 3GPP2 "), " the WIRELESS IP NETWORK STANDARD " by name that announces in December, 1999.For example described the 3rd generation the Wireless IP network standard comprise packet data serving node (" PDSN "), similar described IWF108 on its function.
Between described MS110 and described IWF108, there is the variety of protocol of being devoted to data communication.For example, the interim standard I S-95 of Telecommunications Industries Association (TIA)/electron trade association (EIA), " the MOBILE STATION-BASE STATION COMPATIBILITYSTANDARD FOR DUAL-MODE WIDESPREAD SPECTRUM CELLULARSYSTEM " by name that announces in July, 1993 provides the standard that is used for broadband spectrum spread wireless communication system widely.And, the TIA/EIA IS-707.5 standard of " the DATA SERVICE OPTIONS FOR WIDEBAND SPREADSPECTRUM SYSTEMS:PACKET DATA SERVICES " by name that announces in February, 1998 has defined in the packet data bearer service of supporting the requirement of packet data transmission ability in the TIA/EIA IS-95 system and having stipulated to be used for to communicate by letter by described BS/MSC106 between described MS110 and described IWF108.Similarly, the TIA/EIA IS-707-A.5 standard of " the DATA SERVICE OPTIONS FORSPREAD SPECTRUM SYSTEMS:PACKET DATA SERVICES " by name that announces in March, 1999 and the TIA/EIA IS-707-A.9 standard of " DATA SERVICE OPTIONS FOR SPREAD SPECTRUMSYSTEMS:HIGH-SPEED PACKET DATA SERVICES " by name have also defined the requirement of supporting packet data transmission in TIA/EIA IS-95 system.In addition, another is devoted to the TIA/EIA IS-2000 standard that described MS110 and the standard agreement of communicating by letter between described IWF108 are " the INTRODUCTION TO CDMA 2000 STADARDS FOR SPREADSPECTRUM SYSTEMS " by name that announce in July, 1999.
IS-707.5 has introduced the communication protocol preference pattern of (L interface) between (Um Interface) between described MS110 and described BS/MSC106 and described BS/MSC106 and described IWF108.For example, there is the situation of peer-peer protocol (PPP) link in the representative of relaying model on the Um Interface between described MS110 and described IWF108.At Internet Standard (draft) 1661 (RFC1661), describe described ppp protocol in detail in " THE POINT-TO-POINT PROTOCOL (PPP) " by name.
Fig. 2 (prior art) is the figure of the protocol stack in each entity in the described IS-707.5 relaying model.The high order end of this figure is the communication protocol stack that shows with conventional vertical format, shows the protocol layer that moves on described MS110.Illustrated that described MS110 protocol stack is connected with BS/MSC106 protocol stack logic by described Um Interface.Illustrated that then described BS/MSC106 protocol stack is connected with IWF108 protocol stack logic by described L interface.
The operation of describing among Fig. 2 is as follows: the top layer entity 200 of the application program of all operations of MS110 as described need send data on the internet.Representative application can be that the web browser program is (as Netscape Navigator
TM, Microsoft Internet Explorer
TM).Described web browse request universal resource locator (url), as hyperlink "
Http:// www.Qualcomm.com".Same domain name system (DNS) in described top-level protocol 200 converts the text host name numeric IP addresses of 32-bit to by using domain name mapping, and this domain name mapping converts name in the internet address.The HTTP(Hypertext Transport Protocol) that is described top-level protocol 200 equally is that the URL structure of being asked obtains message, and specifies TCP will be used to send this message and be used for HTTP and operate.Transport layer 202 uses port well known in the art 80 as destination interface, and the HTTP operation is sent to application.
Be opened to by the connection of the IP address of DNS appointment and send application layer HTTP as the Transmission Control Protocol of transport layer protocol 202 and obtain message.Described Transmission Control Protocol has stipulated that the IP agreement will be used for transmission of messages.The IP agreement of described network layer protocol 204 sends the TCP grouping to the IP address of appointment.Encode described IP grouping and they are sent to relay layer protocol 208 of the PPP of link layer protocol 206.An example of described relay layer protocol 208 is TIA/EIA-232F standards of explanation, the definition in " the INTERFACE BETWEEN DATA TERMINAL EQUIPMENT AND DATACIRCUIT-TERMINATING EQUIPMENT EMPLOYING SERIAL MINARYDATA INTERCHANGE " by name that announce in October, 1997 of this standard.It is to be understood that and to use other standard known to a person of ordinary skill in the art or agreement to define the transmission of crossing over layer.For example, other available agreement can comprise " UNIVERSAL SERIAL BUS (USB) SPECIFICATION, Revision 1.1 " that announce in December, 1998 and " the BLUETOOTHSPECIFICATION VERSION 1.0A CORE " that announces in July, 1999.At last, described relay layer protocol 208 is given the PPP packet delivery radio link protocol (RLP) 210 and is passed to IS-95 agreement 212 then, is used on Um Interface to Bs/MSC 106 transmission.In the IS-707.2 standard of announcing in February, 1998 that is called " DATA SERVICEOPTIONS FOR WIDEBAND SPREAD SPECTRUM SYSTEMS:RADIO LINKPROTOCOL ", define described RLP agreement 210, and defined described IS-95 agreement in the IS-95 standard that identifies in the above.
The relay layer protocol 220 of the complementation on the described BS/MSC106 also receives the PPP grouping by RLP layer 216 subsequently by IS-95 layer 218 on described Um Interface.Described relay layer protocol 220 is in the relay layer protocol 228 of on the L interface these packet delivery being given on the described IWF108.Ppp protocol link layer 226 on the described IWF108 receives described PPP grouping from described relay layer protocol 228, and stops described MS110 and be connected with PPP between described IWF108.The described IWF108 of being grouped in upward is delivered to IP layer 224 from described PPP layer 226 and is used to check described IP packet header to make last Route Selection, and this is in the case
Www.Qualcomm.com
The final destination of supposing the IP grouping that produced by described MS110 is not described IWF108, just by network layer protocol 224 and link layer protocol 225 described grouping is sent to next router (not shown) on the internet.So, according to described IS-707.5 standard relaying model, will arrive its final purpose ground from the IP packet delivery of described MS110 by described BS/MSC106 and described IWF108.
Before described MS110 grouping arrives its final destination, must at first set up data link and connect.As illustrating among the RFC1661, this requires each end of described point-to-point link (being described ppp protocol 206 and 226) at first to send ppp link control protocol (LCP) grouping, to set up, to dispose and to test this data link and be connected.After LCP had set up this link, described ppp protocol 206 can send Network Control Protocol (NCP) grouping then to dispose described network layer protocol 204 and 224.The NCP that is used for IP in the ppp link is IP control protocol (IPCP).In the Internet Standard of announcing in May, 1992 (draft) 1332 (RFC1332) that is called " THEPPP INTERNET PROTOCOL CONTROL PROTOCOL (IPCP) ", describe IPCP in detail.Yet, before ipcp negotiation, may need Qualify Phase.Disposed described network layer protocol each after, send grouping on can the link between them from each network layer protocol.
B. application programming interfaces
Support the great majority processing (even not being whole) of the communication protocol stack on the described MS110 to carry out by application program.Usually, the conventional data network application program using application programming interfaces (API) to make on a computer, to move can with the interapplication communications that on another computer, moves.Described API utilizes " Coupling ", and it makes calls the difference of using the agreement of avoiding bottom-layer network.In order to realize network interconnection communication, API comprises the function that allows for example to open Coupling, sends data, receives data and close the application of Coupling from network to network.The common network routine interface is included in Unix
TMBerkeley system development (BSD) the Coupling interface that moves under the operating system and at Windows
TMThe Windows that moves under the operating system
TMCoupling interface (WinSock
TM).
Because BSD Coupling or WinSock
TMDo not support the communication protocol stack (see figure 2) on the described wireless MS110, just need to support the new API of such stack.Especially, required is a kind of method and apparatus that is used for the novelty of mobile station application to identify specified status messages in wireless communication system.
Summary of the invention
The needs of determining above the present invention is devoted to provide a kind of method and apparatus that is used for mobile station application to identify specified status messages in wireless communication system.In one implementation, the present invention includes application programming interfaces (API), made things convenient for and the mobile station communicate protocol stack of communication and communicating by letter between mobile radio station is used.Described mobile radio station application call one function.Described API selects at least one designated state message according to its state and the function that is called.Then, described API is to the selected designated state message of described mobile radio station application report.
The accompanying drawing summary
Fig. 1 (prior art) is the high level block diagram in the wireless communication system, and wherein mobile radio station is connected to the internet.
Fig. 2 (prior art) has schematically described the protocol stack in each entity of TIA/EIA IS-707.5 relaying model.
Fig. 3 has schematically described the characteristics of embodiments of the invention.
Fig. 4 and Fig. 5 are the flow charts that detects allocate event.
Fig. 6 is a calcspar of describing asynchronous connection.
Fig. 7 is a calcspar of describing asynchronous Coupling input.
Fig. 8 to Figure 10 is the state diagram of embodiments of the invention.
Describe in detail
Embodiments of the invention can be realized with various implementations, comprise software, firmware and/or hardware.Therefore, operation of the present invention and performance be will describe and software coding or hardware composition will not be specifically related to.Understand basis the explanation here, those of ordinary skill in the art can design the software and/or the hardware that make the mobile radio station application can discern designated state message and realize the present invention.
Fig. 3 has described the application 260 among the MS110, communication protocol stack 280 and API270.The function call that application 260 and communication protocol stack 280 (being protocol layer 202,204,206,208,210,212) provide by API270 communicates.In other words, API270 allow to use 260 and moves on different processors and operating system with communication protocol stack 280 and do not damage functional.The various names that those skilled in the art will appreciate that the function of being called are possible and do not deviate from scope of the present invention.
Should be noted that communication protocol stack 280 comprises the transmit queue of a plurality of storage data and receives formation.Output function is from using 260 memory read data, with this storage among a transmit queue of communication protocol stack 280.Input function receives the formation reading of data from one of communication protocol stack 280, with this storage in using 260 memory.
For description operation, described MS110 receives the IP grouping.280 pairs of described IP groupings of the communication protocol stack of described MS110 remove encapsulation, and they are delivered to transport layer 202 (see figure 3)s.This transmission is indicated in the territory of the stem of described IP grouping, can be TCP or UDP.According to designated destination port numbers in the described transport layer stem, described data are routed to the suitable reception formation of communication protocol stack 280, this formation is corresponding to a certain Coupling.Can be sent to these data then and use 260.
In some cases, need reduce the stand-by period effect with the division operation of each layer of walking around described protocol stack 280.Such grouping comprises the original packet data that lacks destination information (being the destination port numbers), divides into groups as initial IP.So, from this initial IP grouping, can not determine the purpose application.For example under these circumstances, communication protocol stack 280 can be supported the initial IP grouping that the Coupling transmission of described IP agreement receives to all registrations.This allows effective load data to be sent to the destination application.Internet control messages agreement (ICMP) analysis engine of response IP grouping also can receive described original packet data.In RFC792 " INTERNET CONTROL MESSAGE PROTOCOL " by name, defined famous ICMP analysis engine.Should be clear that from this specification for example, communication protocol stack 280 upwards is delivered to along stack in the grouping that will receive and handles described grouping before using 260, this reduced use 260 carry out go the amount that encapsulates.
On the contrary, can transmit original packet data by using described Coupling to use 260 on Um Interface, this will promote communication protocol stack 280 and use 260 communicate by letter.In addition, use 260 and can on described Um Interface, transmit original packet data.For example communication protocol stack 280 will divide into groups successively or original packet data be packaged into IP grouping and on described Um Interface, transmit them.In this example, communication protocol stack 280 provides IP stem and verification and to produce described IP grouping.On the other hand, for ICMP, the protocol type of appointment will be replicated among the into described IP stem.
As indicated in top, use 260 and can create a Coupling, allow at least one protocol layer 202,204,206,208,210,212 and use 260 data communication, with in the use that reduces communication protocol stack 280 intrinsic wait time-delay.That is to say, use 260 and can create the Coupling of walking around described transport layer 202, described network layer 204 and described link layer 206, thereby allow application 260 to send the Payload data or receive the Payload data from it to RLP layer 210.Similarly, using 260 can create and allow to use 260 and send the Payload data or receive the Coupling of Payload data from it to IS-95 layer 212.
In one embodiment, use 260 call function open_netlib () and open communication protocol stack 280 and dispensing applications identifier.Described application identities symbol allows a plurality of application and communication protocol stack 280 to communicate (being multitasking).For example, as the part that function open_netlib () calls, use 260 pointers of having stipulated to point to the pointer of network call back function and having pointed to the Coupling call back function.No matter when (or enabling) incident such as the network subsystem appointment of reading, writing and closing traffic channel (being Um) and/or link layer (being PPP206) takes place, and calls described network call back function and uses 260 with notice.No matter when (or enabling) taking place such as the Coupling allocate event that reads, writes and close transport layer (being TCP), calls described Coupling call back function and use 260 with notice.For those of ordinary skill in the art, communication network comprises that at least one in described traffic channel, described link layer, the described transport layer should be conspicuous.
In case opened communication protocol stack 280, call function pppopen () comes initialization to comprise that the network subsystem of described traffic channel and described link layer is connected.This is not based on calling in the whole range of application of indivedual Couplings.Yet it requires described application identities symbol.One when network subsystem connection foundation or failure, calls described network call back function the allocate event notice is provided.For example, if do not set up traffic channel, described network subsystem failure.The characteristic of described network subsystem can be set with net_ioctl () function call in addition.For example this calls the data rate that can stipulate described Coupling.
In case set up the network subsystem connection, can create and Coupling of initialization (or a plurality of Coupling) by socket () function call.Yet before can using described Coupling function, described socket () function call is returned the Coupling descriptor.Then, use 260 and can register allocate event to receive asynchronous notifications by call function async_select ().Use 260 parts that can be used as described function call and realize this registration, the Coupling descriptor of the described allocate event that the regulation request is notified and bit-masks (be a plurality of incident OR ' ed together).For example, if allocate event (promptly enabling) takes place and detect, call described Coupling call back function asynchronous notifications is provided by communication protocol stack 280 or API270.Described call back function can comprise that the message on the remote procedure call (RPC) or signal, the message informing of hardware or software interrupt use 260 described allocate events by use.
In case notice is used 260 described allocate events, so call function getnextevent () is determined the allocate event that to serve.This function is the mask that described given set fitting descriptor returns the allocate event of described generation.And it removes the bit in the mask of allocate event of described generation.Thereby application 260 can no longer receive the notice of the allocate event of forbidding.Use 260 and must re-register (promptly reactivating) these allocate events by async_select () function call subsequently.
In addition, application 260 can change the allocate event of registration by corresponding bit in the bit-masks of removing allocate event.If remove the bit in the described bit-masks already, so just ignore this request simply.Briefly, for example can be with the mode disable events notice of every incident by async_deselect () function call.
Fig. 4 and Fig. 5 are the flow charts that is used to detect described allocate event.For example, as shown in Figure 4, communication protocol stack 280 is waited for and is used 260 registration allocate events in piece 400.After having registered allocate event, communication protocol stack 280 poll memories in piece 402.In piece 404, can detect described allocate event according to the polling message of piece 402.In piece 406, for example the memory (being described transmit queue) when described communication protocol stack 280 when can be used for accepting the data of q.s, just detects the incident of writing.Can send data from using 260.The polling message of if block 404 undesirable (described allocate event does not promptly take place), so as in piece 402, communication protocol stack 280 continues the described memory of poll.
In Fig. 5, as described in piece 500, communication protocol stack 280 is waited for and is used 260 registration allocate events.During this period of time, can the disable interrupts notice.So, described interrupt notification can not trigger or be triggered.As shown in piece 500, after having registered allocate event, in piece 502, can trigger interrupt notification according to the appearance of described fixed time.For example, when the memory that data is write communication protocol stack 280 (being described reception formation) is middle, read incident.Thereby in piece 504, when receiving described interrupt notification, communication protocol stack 280 detects the described incident of reading.The described data that are stored in the memory of communication protocol stack 280 can be from communication network.In addition, for the described incident of reading, the data of described storage can be sent to and use 260.
At last, when because for example such as the data link connection termination of transport layer and Coupling can reuse the time detects close event.
The asynchronous connection (see figure 6) below providing and the example of asynchronous input (Fig. 7) illustrate the use of asynchronous event notice.
With reference to figure 6,, entered communication protocol stack 280 and stipulated call back function by open_netlib () function call.The described network subsystem of described pppopen () function call (A) initialization connects (B).After having set up described network subsystem connection, call the availability that (C) described call back function is reported described network subsystem.
Suppose to open and distributed Coupling, connect () function call initialization TCP connects (E).Further, use 260 call function async_select () and (F) register allocate event with reception notification.In this example, the allocate event of being concerned about is once the incident of writing when the generation that connects.
One when having set up connection, if registered described allocate event in mask, just calls described call back function.If like this, call described call back function (G) so asynchronous notifications be provided.Use 260 in case notified, its call function getnextevent () (H) determines to have taken place which allocate event (I).Similarly, this calls the bit (promptly writing incident) of removing the incident in the described mask (J).Application 260 must re-register the notice of allocate event subsequently by async_select () function call.
In Fig. 7, provided the explanation that asynchronous Coupling is read.For initialization is read, use 260 and send read () function call (A).Suppose to lack read data, use 260 call function async_select () (B) registered events (corresponding bit promptly is set in described mask) with reception notification.In this example, the allocate event of being concerned about is the incident of reading that just takes place when the data that application 260 will be read.
One works as storage in described reception formation, if specified the incident of reading just to call described call back function in described mask.If like this, so just call described call back function (C) asynchronous notifications be provided.Use 260 in case notified, its call function getnextevent () (D) determines to have taken place which allocate event (E).Similarly, this calls the bit of removing the incident in the described mask (F).Application 260 must re-register the notice of allocate event subsequently by async_select () function call.At last, in order to read the data that are stored in the described reception formation, use 260 and must send read () function call (G).
In Fig. 8 to Figure 10, the state machine of embodiments of the invention has been described.In Fig. 8-9, suppose communication protocol stack 280 unlatchings and set up network subsystem connection (being that traffic channel and link layer (if necessary)-original Coupling can be walked around described network subsystem).Those of ordinary skill in the art will appreciate that the various names of state are possible and do not deviate from scope of the present invention.
The state machine of asynchronous conversion control (promptly enable or forbid) described allocate event between state is as reading and writing with close.Can forbid described allocate event and enable the state that this allocate event helps use 260 identification MS110 in the beginning of operation at predetermined state.
And, the type function report designated state message that API270 calls according to state and the application 260 of API270, this message is application 260 peculiar (promptly being not only general).Described designated state message can reflect the state of bottom communication network.For example the parameter with function call reports to application 260 with described status message.
For example in Fig. 8, the state diagram of the TCP Coupling of API270 has been described.The Coupling of no initializtion is with 800 beginnings of " sky " state.Because unallocated, described Coupling is " existence " not.Can set up and the described Coupling of initialization by socket () function call, this calls and returns the Coupling descriptor that is used for the relevant function of Coupling.After socket () function call, described state machine is transformed into " initialization " state 805.
In init state 805, no matter when since close () function call and may stop TCP and connect the time described state machine be converted back to described dummy status 800.Described close () function call discharges the relevant resource of all Couplings.On the other hand, connect () function call initialization TCP connects and described state machine is transformed into " unlatching " state 810.
In described opening 810, when (1) generation network subsystem fault, when (2) set up the IP address of described TCP connection failure or (3) change, described state machine was transformed into " closing " state 815.And after the close () function call that stops described TCP connection, described state machine is transformed into " closing " state 820 and the start-stop process with described Coupling.At last, one when having set up the TCP connection, and described state machine is transformed into " opening " state 825.
In described open mode 825, open described Coupling and read and write.In particular, enable the described incident of writing at once, and enable the described incident of reading whether be stored in the memory of described communication protocol stack 280 according to data among.When the network subsystem fault takes place (1); (2) set up described TCP connection failure; (3) attempt to stop TCP and connect, as the TCP that initiates by the webserver reset, TCP interrupts or TCP closes and during the change of (4) IP address, described state machine is transformed into described closed condition 815.Such as the TCP connection termination of initiating state machine is transformed into closed condition 820 by the application of close () function call.
In described closed condition 815, described reading and writing and close event have taken place.After the close () function call that stops described TCP connection, described state machine is transformed into described dummy status 800 with described Coupling, discharges described Coupling and it can be reused.
In off position in 820, when network failure takes place (1); (2) attempt to stop TCP and connect, reset or TCP closes as the TCP that initiates by the webserver; (3) timer expires and during the change of (4) IP address, described state machine is transformed into " wait is closed " state 830.In order to prevent to stop the delay of TCP in connecting, described API270 uses once the timer that begins startup when described TCP connection termination.As can be seen, the expiration of described timer is transformed into described wait closed condition 830 with described state machine.
In described wait closed condition 830, close () function call stops described TCP connection and described state machine is transformed into described dummy status 800.Described close event has taken place in this state 830.
Table 1-3 has illustrated the designated state message that API270 supports.In described dummy status (not shown among the table 1-3), the designated state message of description " not having extra resource to use " can report to uses 260.
Table 1
| State | The designated state message of contiguous function type |
| Initialization | If this is to block function call, described Operation would block |
| Open | During connection is carried out |
| Open | Set up connection |
| Close | Attempt or connect to attempt failing causing the TCP connection not exist owing to lacking initiation |
| Wait is closed | Initiate to attempt or connect to attempt failure owing to lack; Or general network mistake; Or bottom-layer network is unavailable and cause TCP to connect not exist |
| Close | General network mistake; Bottom-layer network is unavailable; Refusal connects trial because server resets; Ongoing connection is overtime; Or because the heavy IP address modification that causes TCP to connect the network layer that resets synchronously of PPP |
Table 2
| State | The designated state message of I/O type function |
| Initialization | Attempt or connect to attempt failing causing the TCP connection not exist owing to lacking initiation |
| Open | If this is to block function call, described Operation would block |
| Open | If this is to block function call, described Operation would block (byte number of read/write) |
| Close | Attempt or connect to attempt failing causing the TCP connection not exist owing to lacking initiation |
| Wait is closed | Initiate to attempt or connect to attempt failure owing to lack; Or general network mistake; Or bottom-layer network is unavailable and cause TCP to connect not exist |
| Close | General network mistake; Bottom-layer network is unavailable; The server connection that resets; Receiving server resets; Owing to connecting, overtime or other reason TCP interrupt; Attempt or connect to attempt failing causing the TCP connection not exist owing to lacking initiation |
Table 3
| State | Close the designated state message of type function |
| Initialization | Success-reported the zero defect state |
| Open | If this is to block function call, described Operation would block |
| Open | If this is to block function call, described Operation would block |
| Close | If this is to block function call, described Operation would block |
| Wait is closed | Success-reported the zero defect state |
| Close | Success-reported the zero defect state |
The state diagram of UDP Coupling that Fig. 9 has exemplified API270.The Coupling of no initializtion starts from " sky " state 900.As top about as described in as described in the dummy status 800 the elaboration because unallocated, described Coupling is " existence " not.Can set up and the described Coupling of initialization by socket () function call, this calls and returns the Coupling descriptor that is used for the relevant function of Coupling.After socket () function call, described state machine is transformed into " opening " state 905.
In described open mode 905, open described Coupling and read and write.In particular, enable the described incident of writing at once, and enable the described incident of reading whether be stored in the memory of described communication protocol stack 280 according to data among.Described state machine is transformed into " closing " state 910 when the network subsystem fault takes place.Such as the UDP connection termination of initiating state machine is transformed into dummy status 900 by the application of close () function call.
In described closed condition 910, enable described reading and writing and close event.After the close () function call that stops described UDP connection, described state machine is transformed into described dummy status 900 with described Coupling, discharges described Coupling and it can be reused.
Table 4-6 has illustrated the designated state message that API270 supports.In described dummy status (not shown among the table 1-3), state that as top the designated state message of " not having extra resource to use " can report to uses 260.
Table 4
| State | The designated state message of contiguous function type |
| Open | Success-reported the zero defect state |
| Close | General network mistake; Bottom-layer network is unavailable |
Table 5
| State | The designated state message of I/O type function |
| Open | If this is to block function call, described Operation would block (byte number of read/write) |
| Close | General network mistake; Bottom-layer network is unavailable |
Table 6
| State | Close the designated state message of type function |
| Open | Success-reported the zero defect state |
| Close | Success-reported the zero defect state |
Figure 10 has illustrated the state diagram of the network subsystem of control such as traffic channel (being Um) and link layer (being PPP206).Open_netlib () function call is opened described network subsystem, and Coupling is initialized to " closing " state 1000.The described network subsystem of pppopen () function call initialization connects, and described Coupling is transformed into " unlatching " state 1005.Call out the paging to MS110 of sending by input PPP and also described Coupling is transformed into described opening.In two kinds of situations, one ought successfully consult, and described MS110 attempts by traffic channel synchronously and set up RLP and PPP.
In described opening 1005, one when having set up the network subsystem connection, and described Coupling is transformed into " opening " state 1010.On the other hand, do not connect if set up described network subsystem, described Coupling just is converted back to described closed condition 1000.
In described open mode 1010, call call back function identification and use 1060 allocate events of enabling, as reading and writing with close.Carve at this moment, described MS110 can pass through traffic channel communication.Yet described Coupling is transformed into described closed condition 1000 when the network subsystem fault takes place, and this has called described call back function.Such as the network subsystem connection termination of initiating described Coupling is transformed into " closing " state 1015 by the application of close () function call.
In described closed condition 1015, described Coupling is transformed into described closed condition 1000 when described network subsystem connection termination.In described closed condition 1000, call described call back function identification and use 260 allocate events of enabling.
The designated state message of calling corresponding to specific function that table 7 has illustrated that API270 supports.
Table 7
| Function call (and explanation) | Designated state message |
| Socket () creates Coupling and returns the Coupling descriptor | The address is not supported; Invalid application identities symbol; For Coupling protocol type mistake; Invalid or be not supported Coupling parameter; Agreement is not supported; Or there is not more Coupling resource to use |
| Connect () initialization TCP connects | If this is to block function call, described Operation would block; Invalid Coupling descriptor; Reset and refuse connect to attempt owing to receiving server; Connect overtime; Application buffer is not the part of effective address space; Big or small invalid for address size or message-length regulation; The TCP that causes synchronously connects the network layer IP address modification that resets because PPP is heavy; During connection is carried out; |
| The Coupling descriptor that has connected; General network mistake; Bottom-layer network is unavailable; Specify invalid server address; The address in use; Perhaps require destination address | |
| Pppopen () sets up network and connects | If this is to block function call, described Operation would block; Specify invalid application identities symbol; Perhaps stopping ongoing network connects |
| Net_ioctl () is provided with network characteristic | Specify invalid application identities symbol; Invalidation request or parameter; Set up the network connection; During perhaps the network connection is carried out |
| Open_netlib () open communication protocol stack | Do not use available-surpassed and opened the maximum quantity of using |
| Close_ntlib () communication close protocol stack | Specify invalid application identities symbol; There is the Coupling that distributes; Perhaps network connects still foundation |
| Bind () invests this Coupling for client's Coupling with local address and port value | Specify invalid Coupling descriptor; Specify invalid or unsupported operation; The address in use; Invalid operation; Perhaps specify invalid address parameter |
| Close () closes Coupling, discharges it so that reuse | Specify invalid Coupling descriptor; If perhaps this is to block function call, described Operation would block; |
| Pppclose () closes network and connects | If this is to block function call, described Operation would block; Specify invalid application identities symbol; Perhaps stopping ongoing network connects |
| The state that netstatus () reporting ent connects | Specify invalid application identities symbol; Bottom-layer network is unavailable; Network connects foundation and available; During the network connection is carried out; Stopping ongoing network connects; No CDMA (being traffic channel) service is available; The base station does not support service option to initiate to fail but CDMA service is available; But the perhaps available initiation failure of CDMA service; Yet this is not because this service option is not supported in the base station |
| Async_select () is to specific Coupling registration allocate event | Specify invalid Coupling descriptor |
| Getnextevent () obtains next Coupling descriptor and event | Specify invalid Coupling descriptor; Perhaps specify invalid application identities symbol |
| Write () writes byte-continuous or discrete buffer of specified quantity | Specify invalid Coupling descriptor; Do not exist TCP to connect; The server TCP that resets connects; Because connecting, overtime or other fault TCP interrupts; The TCP that causes synchronously connects the network layer IP address modification that resets because PPP is heavy; The TCP connection closed; Network is unavailable; Application buffer is not the live part of address space; Perhaps there is not free-buffer to be used to write |
| Read () read the byte of specified quantity-continuous or | Specify invalid Coupling descriptor; Do not exist TCP to connect; Server service TCP connects; |
| Discrete buffer | Because connecting, overtime or other fault TCP interrupts; The TCP that causes synchronously connects the network level IP address modification that resets because PPP is heavy; The TCP connection closed; Network is unavailable; Application buffer is not the live part of address space; There is not free-buffer to be used to read; Perhaps receive end of file sign |
| Sendto () sends the byte of specified quantity | Specify invalid Coupling descriptor; Address family is not supported; There is not free-buffer to be used to write; Network is unavailable; Application buffer is not the live part of address space; The option of appointment is not supported; Perhaps ask destination address |
| Recvfrom () reads the byte of specified quantity | Specify invalid Coupling descriptor; Address family is not supported; There is not free-buffer to be used to write; Network is unavailable; Application buffer is not the live part of address space; The option of appointment is not supported |
In another embodiment, a kind of machine is can read machine readable comprises medium such as the coded message of encoding software code, so that above-mentioned processing can make mobile station application to identify specified status messages.Described machine-readable medium can be from accepting coded message such as the memory device of memory or memory disk or from described communication network.When making described medium, can also programme with coded message to described machine-readable medium.Described machine can comprise at least one of application 260, communication protocol stack 280 and API270, and described machine-readable medium can comprise memory or memory disk.
Though show the present invention about some embodiment, should not think that it is so restriction.On the contrary, the present invention is only by additional claim and related request restriction thereof.
Claims (12)
1. one kind is used for the method that mobile radio station is used a plurality of designated state message of identification, it is characterized in that described method comprises:
Between mobile station communicate protocol stack and communication network, communicate by letter;
Described mobile station communicate protocol stack with communicate by letter by the mobile radio station application interface between described mobile radio station is used;
By described mobile radio station application call function;
Select at least one designated state message by described mobile radio station application interface according to described mobile radio station application interface state and the function that is called;
By described mobile radio station application interface to described mobile radio station application report at least one designated state message.
2. the method for claim 1 is characterized in that described mobile radio station uses with the function parameters called to described mobile radio station application report at least one designated state message.
3. the method for claim 1 is characterized in that described application mobile radio station application interface comprises a plurality of states.
4. method as claimed in claim 3 is characterized in that the asynchronous conversion between state of described mobile radio station application interface.
5. one kind is used for the device that mobile radio station is used a plurality of designated state message of identification, it is characterized in that described device comprises:
Mobile station communicate protocol stack with communication;
The mobile radio station of call function is used;
Select the mobile radio station application interface of at least one designated state message according to described mobile radio station application interface state and the function that will call,
Wherein said mobile radio station application interface be adapted to allow described mobile radio station use with described mobile station communicate protocol stack between communicate by letter, and
Wherein said mobile radio station application interface is adapted to described mobile radio station application report at least one designated state message.
6. device as claimed in claim 5 is characterized in that described mobile radio station application interface is adapted to the function parameters called to described mobile radio station application report at least one designated state message.
7. device as claimed in claim 5 is characterized in that described mobile radio station application interface comprises a plurality of states.
8. device as claimed in claim 5 is characterized in that described mobile radio station application interface is adapted to asynchronous conversion between state.
9. machine-readable medium that comprises coded message is characterized in that causing following processing when being read by machine:
Between mobile station communicate protocol stack and communication network, communicate by letter;
Described mobile station communicate protocol stack with communicate by letter by the mobile radio station application interface between described mobile radio station is used;
By described mobile radio station application call function;
Select at least one designated state message by described mobile radio station application interface according to described mobile radio station application interface state and the function that is called;
By described mobile radio station application interface to described mobile radio station application report at least one designated state message.
10. machine-readable medium as claimed in claim 9 is characterized in that described mobile radio station uses with the function parameters called to described mobile radio station application report at least one designated state message.
11. machine-readable medium as claimed in claim 9 is characterized in that described mobile radio station application interface comprises a plurality of states.
12. machine-readable medium as claimed in claim 11 is characterized in that described mobile radio station application interface is adapted to asynchronous conversion between state.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US53949700A | 2000-03-30 | 2000-03-30 | |
| US09/539,497 | 2000-03-30 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2004100898482A Division CN1620157A (en) | 2000-03-30 | 2001-03-29 | Method and apparatus for a mobile station application to identify specified status messages |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1449614A true CN1449614A (en) | 2003-10-15 |
Family
ID=24151469
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2004100898482A Pending CN1620157A (en) | 2000-03-30 | 2001-03-29 | Method and apparatus for a mobile station application to identify specified status messages |
| CN01807775A Pending CN1449614A (en) | 2000-03-30 | 2001-03-29 | Method and apparatus for a mobile station application to identify specified status messages |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2004100898482A Pending CN1620157A (en) | 2000-03-30 | 2001-03-29 | Method and apparatus for a mobile station application to identify specified status messages |
Country Status (9)
| Country | Link |
|---|---|
| EP (1) | EP1273150A2 (en) |
| JP (1) | JP2004500785A (en) |
| KR (1) | KR20040007214A (en) |
| CN (2) | CN1620157A (en) |
| AU (1) | AU2001251106A1 (en) |
| CA (1) | CA2403813A1 (en) |
| IL (1) | IL151707A0 (en) |
| MX (1) | MXPA02009507A (en) |
| WO (1) | WO2001076279A2 (en) |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100901715B1 (en) | 2003-03-12 | 2009-06-08 | 엘지전자 주식회사 | Layer architecture for interfacing personal digital assistant and wireless communication module |
| KR100539903B1 (en) | 2004-01-17 | 2005-12-28 | 삼성전자주식회사 | Method for processing vod data in the mobile terminal |
| US7742444B2 (en) | 2005-03-15 | 2010-06-22 | Qualcomm Incorporated | Multiple other sector information combining for power control in a wireless communication system |
| US8750908B2 (en) | 2005-06-16 | 2014-06-10 | Qualcomm Incorporated | Quick paging channel with reduced probability of missed page |
| US9055552B2 (en) | 2005-06-16 | 2015-06-09 | Qualcomm Incorporated | Quick paging channel with reduced probability of missed page |
| US8856311B2 (en) | 2005-06-30 | 2014-10-07 | Nokia Corporation | System coordinated WLAN scanning |
| CA2513018A1 (en) | 2005-07-22 | 2007-01-22 | Research In Motion Limited | Method for training a proxy server for content delivery based on communication of state information from a mobile device browser |
| CA2513016A1 (en) | 2005-07-22 | 2007-01-22 | Research In Motion Limited | A secure method of synchronizing cache contents of a mobile browser with a proxy server |
| CA2513022A1 (en) | 2005-07-22 | 2007-01-22 | Research In Motion Limited | System and method for communicating state management between a browser user-agent and a mobile data server |
| US20090207790A1 (en) | 2005-10-27 | 2009-08-20 | Qualcomm Incorporated | Method and apparatus for settingtuneawaystatus in an open state in wireless communication system |
| KR100973456B1 (en) | 2005-10-27 | 2010-08-02 | 퀄컴 인코포레이티드 | A method and apparatus for attempting access in wireless communication systems |
| EP2120404A1 (en) * | 2006-12-20 | 2009-11-18 | NEC Corporation | Communication terminal, terminal, communication system, communication method, and program |
| CN101222443B (en) * | 2008-01-30 | 2012-04-25 | 杭州华三通信技术有限公司 | Method and network appliance for processing packet |
| CN103582170B (en) | 2012-07-23 | 2018-08-10 | 百度在线网络技术（北京）有限公司 | The method and apparatus of communication connection is provided for multiple candidate applications in a mobile device |
| CN112637329B (en) * | 2020-12-21 | 2022-08-23 | 网络通信与安全紫金山实验室 | Identification method, device, equipment and storage medium of multiple application programs |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6016511A (en) * | 1997-09-12 | 2000-01-18 | Motorola Inc. | Apparatus and method for interfacing protocol application data frame operation requests with a data frame input/output device |
-
2001
- 2001-03-29 WO PCT/US2001/010144 patent/WO2001076279A2/en not_active Application Discontinuation
- 2001-03-29 IL IL15170701A patent/IL151707A0/en unknown
- 2001-03-29 CN CNA2004100898482A patent/CN1620157A/en active Pending
- 2001-03-29 CN CN01807775A patent/CN1449614A/en active Pending
- 2001-03-29 JP JP2001573821A patent/JP2004500785A/en not_active Withdrawn
- 2001-03-29 EP EP01924455A patent/EP1273150A2/en not_active Withdrawn
- 2001-03-29 CA CA002403813A patent/CA2403813A1/en not_active Abandoned
- 2001-03-29 AU AU2001251106A patent/AU2001251106A1/en not_active Abandoned
- 2001-03-29 KR KR1020027013065A patent/KR20040007214A/en not_active Application Discontinuation
- 2001-03-29 MX MXPA02009507A patent/MXPA02009507A/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| JP2004500785A (en) | 2004-01-08 |
| EP1273150A2 (en) | 2003-01-08 |
| WO2001076279A3 (en) | 2002-03-14 |
| WO2001076279A2 (en) | 2001-10-11 |
| AU2001251106A1 (en) | 2001-10-15 |
| IL151707A0 (en) | 2003-04-10 |
| CN1620157A (en) | 2005-05-25 |
| MXPA02009507A (en) | 2003-05-14 |
| CA2403813A1 (en) | 2001-10-11 |
| KR20040007214A (en) | 2004-01-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1199420C (en) | Method and apparatus for detecting specified events in mobile station | |
| CN1186912C (en) | IP mobility support using proxy mobile node registration | |
| CN1449614A (en) | Method and apparatus for a mobile station application to identify specified status messages | |
| CN1422482A (en) | Method and apparatus for a mobile station application to identify specified events | |
| US6862276B1 (en) | Method and apparatus for a mobile station application to receive and transmit raw packetized data | |
| CN1653773A (en) | PPP link negotiation in mobile IP systems | |
| CN1422481A (en) | Method and apparatus for notifying a mobile station application of specified events | |
| NZ521602A (en) | Accessing private wireless internet packet data communication system using PDCC,PDTC and PDMA | |
| AU2001251105A1 (en) | Method and apparatus for a mobile station application to receive and transmit raw packetized data | |
| KR100604531B1 (en) | Mobile Packet Data Servicing method for mobile communication system | |
| CN1439215A (en) | Method and apparatus for servicing specified events by a mobile station application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: WD Ref document number: 1056804 Country of ref document: HK |