TWI353142B - Packet data services using version and capability - Google Patents

Description

Γ 353142 IX. Inventor's Note: This application requires the priority of the provisional application No. 60/493'G69, which was issued in August 2003. The title of the interim request is “Msp Qing version/characteristic indication”. The present invention has been assigned to the assignee of the present invention and is hereby incorporated by reference in its entirety. TECHNICAL FIELD OF THE INVENTION The present invention relates generally to wireless communications, and more particularly to packet data services within a wireless communication system. [Prior Art] Wireless communication systems are used in many applications, including, for example, paging, wireless zone loops (wis ss loeal 1 〇〇p; WLL), network access, internet telephony, wireless telephony, and satellites. Communication Systems. An exemplary application for network access is to access a packet data network, such as the Internet, using a wireless communication device (WCD) (e.g., a cellular mobile phone). Standards have been developed to define the requirements for wireless packet data network access. One such standard is the interim standard issued by the Telecommunications Industry Association, TIA/IS-835, entitled "C (jma2〇〇〇 Wireless IP Network Standard), which is incorporated in this article. Since the beginning, IS has been issued Different versions of -835,

Namely IS-835, IS-83 5-A, IS-835-B and IS-83 5-C. Currently, IS-835-D is in development. Each version is backward compatible with earlier versions and adds new features. Therefore, devices having different versions of the standard and corresponding different features in the configured network can communicate with each other. As indicated by the title, the IS-835 standard series specifies support for data services in the Cdma200 system package 95324.doc 1353142. Specifically, the IS-835 series specifies the requirements and selective features of the Mobile Station (MS) to establish and network the Packet Data Serving Node (PDSN).

An Internet Protocol (IP) connection provides MS access to packet data services, such as Internet access. As mentioned above, devices with different versions of the IS-835 standard are widely used, so that different versions of the standard can be used to operate the PDSN and its services. In addition, the dish 3 can be changed from one pDsN to a standard version different from the original PDSN. To operate another Lu PDSN. Since different features and capabilities are available for the MS and the pDSN with which it communicates, the communication efficiency between the various devices may be lower than the specific function of the MS with which it communicates, » for example, if PDSN support is not available 'if one device attempts to perform it needs to be The operation of a particular function supported by a device may result in the exchange of unwanted signal messages for bribes. Therefore, the device's capabilities are generally efficient. More efficient communication of device capabilities can improve device improvements. Therefore, the present technology requires access to packet data networks by supporting different features and capabilities. [Summary of the Invention]

95324.doc W is the above-mentioned need to support access to different features and capabilities. A first aspect is to communicate the version and capability indications of the mobile packet data standard between the mobile station and the wireless network infrastructure to the wireless network infrastructure. The station communicates the version and capability indications of the 1353142 network layer wireless packet data standard supported by the network infrastructure. The packet data is then communicated between the mobile station and the wireless network infrastructure based on individual versions and capability indications. Later, individual capabilities can be better used to communicate between the two. The wireless packet data standard for mobile stations and wireless network infrastructure is available in IS-835. Similarly, the over-the-air communication connection can be a radio channel, such as a CDMA channel. Communication of the version of the mobile station and infrastructure and selective feature capability indications may be performed during the data session initiation process between the mobile station and the infrastructure or after the completion of the data session. The steering station can include a transmitter </ RTI> configured to communicate a version and capability indication of the network layer wireless packet data standard supported by the mobile station to the wireless network infrastructure on the physical layer. The mobile station also includes a receiver configured to receive, at the physical layer, a version and capability indication of the network layer wireless packet data standard supported within the wireless network infrastructure. The mobile station's processor adjusts the mobile station's operation based on the version and capabilities of the mobile station and wireless network infrastructure. The wireless network infrastructure can include a receiver configured to receive, at the physical layer, a version and capability of the network layer wireless packet data standard supported by the mobile station. The wireless network infrastructure can include a transmitter configured to communicate to the mobile station at the physical layer a version and capability indication of the network layer wireless packet data standard supported within the wireless network infrastructure. The processor in the wireless infrastructure adjusts the operation of the wireless network infrastructure based on the version and capabilities of the mobile and wireless network infrastructure. Exemplary features of the present invention will be apparent from the following description of the exemplary embodiments of the invention. [Embodiment] The term "exemplary" as used herein means "serving as an example, instance or description." Any specific embodiment described herein as "exemplary" is not necessarily to be construed as a preferred embodiment or preferred embodiment. Figure 1 shows a communication system 1 constructed in accordance with the present invention. The communication system 1 includes an infrastructure 101, a plurality of wireless communication devices (WCDs) 1〇4 and 1〇5, and inland communication devices 122 and 124. WCD is also known as a mobile station or mobile device. In general, WCD can be mobile or fixed. Infrastructure 101 also includes other components, such as base station 2, base station controller 106, mobile switching center 1, 8, switching network 12, and the like. In a specific yoke example, the base station 1 〇 2 is integrated with the base station controller i 〇 6 . In other specific embodiments, the base station and the base station controller 丨〇 6 are separate components. Different types of switching networks 120 can be used to transmit signals within the communication system 1 . For example, the switching network 12 can be a public switched telephone network (PSTN).

The term "forward link" refers to the signal path from infrastructure 1.1 to WCD, and the term "reverse link" refers to the signal path from the WCD to the infrastructure. As shown in the figure, WCDs 104 and 1-5 receive signals 132 and 136 on the forward link and transmit signals 134 and 138 on the reverse link. In general, signals transmitted from wcd 1〇4 and 105 are received by another communication device, such as another remote unit or inland communication devices 122 and 124, and transmitted over the switching network 12A. For example, if the signal 134 transmitted from the originating WCD 104 is to be received by the destination WCD 95324.doc 1353142 105, the signal is transmitted through the infrastructure 101 and the signal 136 is transmitted on the forward link to the destination WCD 105. Typically, a communication device, such as a WCD or inland communication device, can be the originating and destination of the signal. Examples of WCD 104 include cellular mobile phones, personal computers that actuate wireless communications, and personal digital assistants (PDAs), as well as other wireless devices. Communication system 100 can be designed to support one or more wireless standards. For example, such standards may include standards such as TIA/EIA-95-B (IS-95), TIA/EIA-98-C (IS-98), cdma2000, Wideband CDMA (WCDMA), and the like. Figure 2 illustrates components of an exemplary wireless network that can communicate access to a packet data network via the system shown in Figure 1. As shown in FIG. 2, the wireless network infrastructure may include a packet data network 202, a packet data service node (PDSN) 206, and a base station controller/packet control function (BSC/PCF) 208. And a subscriber WCD, such as a mobile station (MS) 210. Packet data network 202 typically communicates with PDSN 206, PDSN 206 transmits packet data to BSC/PCF 208, and BSC/PCF '208 selects a physical layer connection to establish communication with the MS, such as a type of radio channel (typically a shared radio channel) ) and send the packet data on the selected radio channel. The MS 210 receives the expected packet data carried on the radio channel. Similarly, the MS 210 can transmit the packet information on the radio channel to the BSC/PCF 208, which transmits the packet data to the PDSN 206 which communicates the packet data to the packet data network. The MS and PDSN need to indicate to each other the individual versions and capabilities of the network layer wireless packet data standards they support, for example to avoid unwanted signaling exchanges between the MS and the PDSN in the IP connection establishment process 95324.doc 10 1353142 . For example: If the MS does not support Simple IPv4 and Mobile IPv4, the PDSN can avoid initiating IPCP negotiation with the MS. MSIf the MS does not support Easy Ipv6, PDSN·5: Avoid starting the negotiation with the MSiIPv6 Control Protocol (IPv6CP). MS If the MS only uses Mobile IPv4, the PDSN can avoid the Challenge Handshake Authentication Protocol (CHP) in the Link Control Protocol (LCP) negotiation, which can save one LCP message exchange. 〇 If the MS is always on but does not support the 3GPP2 vendor-specified Max PPP inactivity timer value packet, the PDSN can avoid transmitting unneeded vendor-specific packets to the MS. PD If the PDSN does not support multiple service instances, the MS can avoid transmitting unsolicited signaling for process mapping/processing and OTA signaling for initiating the secondary service instance. 〇If the Resource Authorization Extension (DAE) supports HA resource management via the Mobile IP Revocation or Dynamic Authorization Extension (DAE), the MS can avoid transmitting an IP registration request with zero lifetime to be logged out during power down. PD If the PDSN is an earlier version (ie, version C or earlier), the MS can avoid transmitting a message for each version of the D feature (eg, DHCP). The recommendations of the North Generation Road Corporation for the 3rd Generation Partnership Project 2 (3GPP2) (titled "Capability Guidance Support") are incorporated herein by reference. Point-to-Point Protocol (PPP) is proposed for MS and PDSN. 95324.doc 1353142 The vendor-specified packets indicate each other a list of their respective support features. The Support Features list can be longer, occupying bandwidth and making this technology unsuitable for wireless transmission. The recommendations made by Mobile Research Corporation for 3GPP2 (titled "PDSN Agreement Revision Support") are incorporated herein by reference, which teaches that the PDSN indicates its agreement revision number to the MS via the PPP provider-specified packet. The agreement revision number does not convey information about whether the PDSN supports specific selective features. For example, the Robust Header Compression (ROHC) technology developed by the Network Engineering Task Force's ROHC Working Group (all incorporated herein) is supported within the IS-835-B. The revision number itself does not indicate whether or not to support ROHC features. The common limitation of these two recommendations is that MS and PDSN operating with earlier versions of IS-835 (which is IS-83 5-C and earlier) do not support the use of PPP vendors to specify packet indication versions/capabilities. Therefore, these recommendations do not support MS and PDSN operating using the standards of these earlier versions. For example, in these recommendations, if the serving PDSN operates on an earlier version of the IS-83 5 standard, the MS that complies with the IS-835-D cannot know which version the serving PDSN is operating. Therefore, if the MS and PDSN have different versions/capabilities, an uneconomical exchange of calls can occur. The following description describes the techniques by which the MS and PDSN exchange capability indication information for the agreed version, as well as a list of supported selective features. One aspect of these technologies is that in addition to PPP, the over-the-air (OTA) physical layer connection signaling mechanism can also communicate capability indications. Version/Capability Indication In a specific embodiment, the PDSN or MS indicates a list of its agreed versions and any supported selective features. Figure 3 is a diagram showing the coding capability referred to as 95324.doc -12- 1353142 = shows: 5 protocol version 3〇2. For example, the 'available' byte represents the IS_835 standard version that ms〇dsn conforms to. A specific I only s: the money can be G, Bu 2, 3 or 4, which correspond to IS·835 '

-_A, iS-835-B, iS-835^IS_835_De For example, if pDSN 曰 = as a protocol; t version number, the PDSN supports all mandatory PDSN requirements specified in IS_835B. Additional optional features supported by the sender can be in the message. The other part of 3() 4 is represented by ^. ❹' can be a list of selected points for each (four) milk standard. For example, one or more tuples can be used to represent the selective features. In addition, if a particular feature is supported as a group, for example, if a feature is supported and other features of the group must be supported, then the group can be represented as a single feature rather than individually. The advantage of this technique is that it avoids the PDSNstMS having to transmit a long list of capability indications over the air. In addition, the technology has the flexibility to communicate the selective features supported. This technique is also independent of the transport mechanism. Therefore, the technique can be used to send a packet via the PPP provider specified above or via the following 〇TA. OTA Transmitter Emperor Figure 4 is a call flow diagram illustrating an example of using MS to send a version/capability to indicate MS and network. As shown in Figure 4, MS4〇2 transmits the origination message to the base station controller (base stati011 controller; bsc) 4〇6 to start the data session. Initiating message 404 establishes an air connection to support communication between Ms 4〇2 and BSC 406, for example, to transfer data 95324.doc 1353142 traffic between the MS and the BSC. The version/capability indication of the MS 402 included in the initiation message 404. Only the information specifying the IS-83 5 standard version and any optional features supported are shown. After the message is initiated, the BSC 406 applies the packet control function (Packet).

Control Function; PCF) 410 Transfer A9-Set-A8 Message 408. A9- Sets the capability indication of the MS 402 included in the -A8 message. PCF 410 selects PDSN 412 for MS 402. It should be noted that the version/capability of the MS 402 may be a standard for selecting the PDSN 412 for the MS 402. After the PCF 410 selects the PDSN 412, the PCF 410 transmits an All Registration Request message 414' for establishing an A10 connection to transmit the data traffic for the MS 402 between the PCF 410 and the PDSN 412. The version/capability indication of the MS 402 included in the All Registration Request message 414. Additional details on the traditional A10 and A11 interfaces can be found in document 3GPP2 A.S0017-0, version 2.0, entitled "Interoperability Specifications for cdma2000 Access Network Interface (IOS) - Part 7 (A10 and All) The interface (3G-I〇Sv4.2))"' date is May 2002, which is incorporated herein in its entirety. Upon successful establishment of the A10 connection, the PDSN 412 responds to the PCF 410 with the All Registration Reply message 416. The PDSN 412 can register a reply message 416 at All including its version/capability indication. This may be used for newer versions of PDSN 412, such as PDSN 412 operating with IS-835-D and future releases, may not be available for earlier versions of PDSN 412, such as using IS-835-0 and earlier. PPDSN 412. As an acknowledgment of the A9-Set-A8 message 408, the PCF transmits a "A9-Connect-A8 message 418" to the BSC 406. If the version/capability indication of the PDSN 412 is received in the All Registration Reply message 416, the PCF 410 forwards the capability indication to the BSC 406 in the A9-Connect-A8 message 418. If the PDSN 412 version/capability indication is not 95324.doc -14-1353142 received in the All Registration Reply message 416, but the PCF 410 knows the PDSN version/capability (eg, if configured by the network operator), the pCF 410 may be in eight The 9-Connect-Eight 8 message 418 includes an indication of the capabilities of the 63〇406. 83 € 406 transmits a service connection message 420 to the river 8 402. The BSC 406 may include a PDSN 412 version/capability indication for the MS 402 within the service connection message 420. Alternatively, after transmitting the service connection message 420, the BSC 406 can forward a capability indication, such as a network version/capability message, to the MS 402 within the dedicated messaging message. The advantage of using OTA signaling is that if the MS can indicate its version/capability, PCF_ can indicate the selected PDSN version/capability, then the MS will know the supported PDSN version/capability. Therefore, if the PDSN does not support a specific version/capability, the MS can avoid unwanted signaling exchanges with the PDSN. For example, if the MS knows that the serving PDSN is operating with an earlier version of IS-835, such as version c or earlier, the MS may avoid transmitting a message for features that are only supported by newer version specifications, such as version D features 'eg Dynamic Host Configuration Agreement (Dynamic Host

Configuration Protocol; DHCP). Similarly, if the MS knows that the Home Agent (HA) support is abolished (ie, identifies the component that terminates the IPv4 address of the A10-connected PDSN), the MS can avoid transmitting a registration request (RRQ) with zero lifetime to facilitate Log out when the power is off. The MS may not directly know the abort capability of the HA, but the MS may know indirectly, for example from the PDSN. The PDSN can also utilize the version/capability knowledge of the MS. For example, if the pdSN knows that the MS does not support ROHC before the Internet Protocol Control Protocol (IPCP) starts, the PDSN can exclude the ROHC capability indication in the initial IPCP configuration-request sent to the MS, even if the PDSN supports ROHC » This avoids additional signaling of IPCP Control Message 95324.doc 15 1353142 during IPCP negotiation. Other advantages of OTA technology include notifying users or facilitating network operations. For example, if the MS knows that the PDSN supports the prepaid feature, the MS can notify the user of this feature. Therefore, the user can supplement the existing account or open a new prepaid account. If two MSs communicate with the same PDSN, the first MS only supports mobile IPv4.

I The second MS supports both Simple IPv4 and Mobile IPv4, which illustrates another example of how MS version/capability knowledge can benefit network operations. If two MSs transmit RRQs to request a mobile IP service, but the foreign agent (FA) within the PDSN is close to its capacity, it cannot support two MS requests for mobile IPv4. After understanding the MS capabilities, the PDSN can grant the Mobile IP service to the first MS without granting the second MS, thereby effectively forcing the second MS to retreat to Simple IPv4. In this way, although the second MS operates below its full capabilities, it supports two MS requests instead of only one of the two MS requests. The PDSN and MS may also indicate the earlier version of IS-835 and the selected features (mandatory and selective) from the newer version of IS-835. This provides the carrier with the flexibility to additionally configure the desired features of the newer version based on earlier versions of IS-835. For example, if the bearer needs to be configured to operate IS-835 version A and another PDSN that supports dynamic home agent (DHA) and version/capability indication, the PDSN may indicate to M3 that it supports IS835 version A and DHA. Exemplary Version/Capability Packet Format The version/capability information can be conveyed by different types of data packets. For example, a PPP provider that can be called a version/capability packet specifies a packet-transporting version/capable 95324.doc 16 1353142 Force Information. The general format of a PPP vendor-specified packet in RFC 2153 is defined as 3GPP2', which is incorporated herein in its entirety. Figure 5 is a diagram illustrating an exemplary version/capability packet format. As shown in FIG. 5, the package 500 includes a code column 502, an identification item field 504, a length field 506, a "magic number" field 508, a 3GPP2 Organizationally Unique Identifier (OUI) column 510, a category column 512, and a version column. 514 and support feature list column 516. The contents of the code block 502, the identification item field 504, the length field 506, and the "magic number" column 508 are defined in RFC 2135, and a detailed description of the columns is also included. The OUI column 5 10 identifies the organization that specifies the format and format of the packet in this PPP provider. The organization within this situation is 3GPP2. The category block 512 identifies the packet type. For example, the category code "2" can be used to identify the version/capability indication packet '3' can be used to identify the version/capability reply packet. If the category value is "2", the version/capability indication packet includes a version column and a capability list. If the category value is "3", the version/capability reply packet does not include the version column and the capability list. The list of version blocking capabilities is defined as follows. The version column 514 is used to identify the IS-835 version that the communication source is using. For example, 'Version Bar 1, 2, 3 or 4 can be used to represent is-835 versions A, B, C and D, respectively. In this example, the version is 8-bit, so it can be used to represent 256 different versions. The version field 514 indicates that the sender, ]\43 or 卩〇81^, supports all mandatory requirements that are part of the wireless IP network standard IS-835 identification version. For example, if the PDSN indicates "4" as the version value, it means that the pDSN supports all mandatory ms requests specified in the version D. The Support Feature List field 516 indicates which selective features are supported by the packet 500 transmitter. For example, the support feature list column 516 can include a flag, each flag generation 95324.doc 1353142 table version 514 selects a version of the selective feature to mandatory feature. The &apos;Support Feature List Bar 516 may include a flag (optional or mandatory) that represents additional features supported by a newer version (a version identified within the version 514). For example, if the PDSN complies with all mandatory pdsn requirements in IS-835 Release A and supports Dynamic Local Agent (DHA), the PDSN indicates "i" (indicating version A) in version barrier 514 and flags the flag to support features. The dha feature in the list block 516. In this example, the PDSN does not support all other additional mandatory features of IS-835 Revision B, such as IPv6, so it is not possible to indicate "2" in the version column 514 of the corresponding IS_835 Revision B. This example assumes that the pDSN is operated with IS_835 version A and that the PDSN also supports PPP version/capability packets.

One aspect of this technique is to define flags only for features that are available to the receiver, but not for other features. For example, the version/capability packet transmitted from the PDSN to Ms does not include a flag identifying the PDSN to obtain an option for the Internet Key Exchange (IKE) pre-shared key (used to establish a secure connection with HA) This is because there is no difference between the MS and the pDSN using its options. Therefore, before defining the flag included in the support feature list block 516, it is determined which features are associated with the list. IULL: MS and PDSN master connection. Six; ^丨f In this example, the support capability list contains support for Ms&amp; PDSN2 capabilities. Table 1 below identifies this force that can be used to reduce undesirable telecommunications exchanges or to facilitate network operations. For each capability listed in the first (left) row, the table identifies whether the indication of this capability is available to the receiver (middle row) and which device needs to transmit the finger (right hand row). This table lists examples of capabilities that are not exhaustive. Similarly, the capabilities based on IS-835 version D are not listed in the table and can be added to the list when using the special features of 95324.doc 1353142.

Can the selective capability be used to indicate this capability to the receiver? Which device needs to transmit instructions? Simple Π&gt; ν4 assists PDSN operation (see example in Section 1) MS Action HV4 Same as above MS Simple IPv6 If it is not supported, it can avoid sending unwanted messages. PDSN Max PPP Inactivity Timer If the MS is always on but does not support the 3GPP2 vendor to specify the Max PPP inactivity timer value packet, the PDSN can avoid transmitting unwanted vendor-specific packets to the MS. If the PDSN before version C supports the Max PPP inactivity timer, the mobile device knows to use this feature. MS/PDSN 丨 ROHC [RFC3095] If the transmitter does not support but the receiver supports it, the receiver may not indicate this capability in the initial IPCP configuration request sent to the sender. This avoids the extra "two-way" in IPCP negotiation. MS/PDSN LLA-ROHC U/0 mode [RFC3242] Same as above MS/PDSN IPHC [RFC2507] MS/PDSN LLA-ROHC U/O/R mode [RFC034081 Same as MS/PDSN ECRTP [RFC3545] Same as MS/PDSN multiple services Example If the PDSN does not support multiple service instances, the MS can avoid transmitting unsolicited signaling for process mapping/processing and OTA signaling for initiating secondary service instances. MS/PDSN DNS Server Address Auto Configuration If the PDSN does not support DNS server address autoconfiguration, the MS can avoid additional round trips for IPCP negotiation by not including the DNS server address option. This is a mandatory PDSN feature in version B and later. PDSN Dynamic HA If the PDSN does not support DHA, the MS can avoid the failure action ip registration by not indicating the 拦.〇·〇.〇 or 255.255.255.255 in the HAB of the RRQ. This is a mandatory PDSN feature in version B and later. The PDSN always turns on the selective PDSN feature in this version B, but in the PDSN 95324.doc 19 1353142 indicator pair] the second access method needs to be used to always turn on the experience ° eg if the version B PI) SN does not support the start ~ open And the MS needs to always open the experience, the MS can use the action ip as the access method, and then continue the session by periodically updating the mobile IP registration lifetime. The HA is abolished to support the dynamic authorization extension (DAE) support. True zero RRQ to log out when the power is off. After receiving the RRP, the PDSN knows if it supports the abolition so that the PDSN can indicate this to the MS.

PDSN If the DAE is used for resource management within the PDSN and HA, the MS can avoid transmitting RRQs with zero lifetime to log out during power down.

PDSN Table 1 The list of performance capabilities included in the Support Capability List is 歹彳&amp; The capability list can be further divided into two categories. The first category is for features that are indicated as early as possible during the establishment of the packet data session. All features in the μ and upper tables, except the last two, belong to the first category and should be indicated in the ρρρ Link Control Protocol (LPP) phase. The second category is for features that can be indicated at a later time. The last two features in the above table fall into the second category because the PDSN may not know whether the action is abolished or the Dynamic Authorization Extension (DAE) is available to the MS during the LCP process. Figure 6 is a diagram illustrating additional details of an exemplary support feature list block as shown in Figure 5. As shown in Fig. 6, the 'support feature list column 516 includes a group out queue 602, a length bar 604, and a flag bar 606. The group ID 602 identifies which of the two categories the in-table feature belongs to, that is, the features that should be indicated as early as possible during the establishment of the packet data session or those features that may be indicated at a later time. For example, the group ID column 602 can be one bit level, that is, two values "95324.doc. -20· 1353142 feature list. In this way, the confirmation version/feature packet is correctly received. Example 2: MS and PDSN The split support capability is listed in another example to support the separation capability list of MS and PDSN. In this example, two support capability lists, MS--, PDSN-- are defined. Also in this example, assume only the version. The MS and PDSN of D have the ability to indicate the version/capability. In other words, the MS and PDSN before version D do not have this capability. The MS capability list is encoded into the bit mask defined in Table 4 below. The most significant bit in the C0 series table Each bit in the list indicates whether the MS capability specified in X.SOOH-D is supported. Bit MS Capability Description C0 Simple IPv4 If MS supports Simple IPv4, MS is set to 1. C1 Mobile IPv4 If MS supports Mobile IPv4, MS is set to 1. C2 Simple IPv6 If MS supports Simple IPv6, MS is set to 1. C3 Mobile IPv6 If MS supports Mobile IPv6, MS is set to 1. C4 Max PPP Inactivity Timer if MS supports 3GPP2 vendor specification Max PPP inactivity meter For the packet, the MS is set to 1. C5 to C23 Reserved Table 4 - MS Capability List The PDSN Capabilities List is encoded into the bit mask defined in Table 5 below. The most significant bit in the C0 Series table. Indicates whether the PDSN capability specified in X.S0011-D is supported. 95324.doc 23- 1353142 Bit PDSN Capability Description C0 Auxiliary SI for SO 60 If PDSN supports ancillary service instance for SO 60' then PDSN is set to 1 C1 Auxiliary SI for SO 61 If the PDSN supports an auxiliary service instance for SO 61, the PDSN is set to 1. C2 Auxiliary SI for SO 66 If the PDSN supports an auxiliary service instance for SO 66, the PDSN is set. 1. C3 HA resource management If the PDSN finds that the HA data management is abolished via the action IP, the PDSN is set to 1. C4 to C23 Reserved Table 5 - PDSN Capability List During the LCP negotiation process, the MS shall transmit the version/capability indication packet. If the version/capability indication packet from the PDSN is not received, the MS shall retransmit the version/capability indication packet to a configurable number of times. If the MS receives the configuration-reject, the MS shall stop retransmitting the version/capability indication packet. Configuration-Reject Absolute reception means that the PDSN is version C or earlier. If the MS receives the version/capability indication packet from the PDSN, the MS shall respond with a version/capability reply packet, and the MS shall not transmit more version/capability indication packets in the PPP session. If the PDSN receives the version/capability indication packet from the MS, the PDSN responds with a version/capability indication packet. If the version/capability reply packet from the MS is not received, the PDSN shall retransmit the version/capability indication packet for a configurable number of times. After receiving the version/capability reply packet from the MS, if the pdSN receives the version/capability indication packet, the PDSN should ignore it. 95324.doc • 24· 1353142 The right PDSN did not receive a version/capability indication packet from the MS, which should not transmit a version/capability indication packet. If the PDSN does not receive the version/capability indication packet from the MS, it is likely that it does not support the earlier version Ms of the version/capability indication. Therefore, it is not economical for the PDSN to transmit a version/capability indication packet to the MS. If the PDSN has previously received the version/capability indication packet from the MS, the PDSN may transmit the version/capability indication packet to the MS at any time after the ppp session is established. It shows the PDSN the network capabilities that are not available for pDSN during the PPP session establishment process. For example, the PDSN may not know if it is supported initially! ^ Into resource management, except in the process of IP registration.

Exemplary MS FIG. 7 is a block diagram of a wireless communication device or MS constructed in accordance with an exemplary embodiment of the present invention. The communication device 7〇2 includes a network interface 〇6, a digital signal process dr (dSP) 〇8, a host processing state 〇, a memory device 712, a program product 714, and a user interface. 716. The I-way 706 receives the signal from the infrastructure and transmits it to the host, the processor 71. The host processor 71G receives the signal and responds with an action according to the signal content. For example, the host processor 71G may decide to receive the received data, or it may send the received data packet to determine the contents of the packet in the DSP 7G8. The host processor can also receive data packets from the stupidity and send the packets to the network interface for transmission to the infrastructure. Alternatively, host processor 71G may intercept the DSP output and modify the data packet, and then send the modified data packet to network interface 706' for transmission to the infrastructure. In a specific embodiment, the 'network interface' can be a transceiver and antenna that communicates with the infrastructure through the wireless channel as 95324.doc -25-1353142. In another embodiment, the network interface 706 can be a network interface card that is used as an interface to the infrastructure through the inland. Both host processor 710 and DSP 708 are coupled to memory device 712. Memory device 7i2 can be used to store data during WCD operations and to store code that is executed by host processor 71 or DSP 708. For example, the host processing state, the DSP, or both can operate under the control of programming instructions temporarily stored in the memory device 712. The host processor and Dsp can also include its own program memory H. When the programming designation (4) is executed, the host processor 710 or the DSP 708 or both perform their functions using the identified features in the version/capability data packet. The programming steps therefore implement the functionality of the individual host processors or CPUs and DSPs so that the host processor and the Kiosk can perform their respective functions according to the required support features. The programming steps can be received from the program product 714. The program product 714 can store the programming (4) and transfer it into the memory 712 for execution by the host processor, cpu, or both. The red product 714 can be a semiconductor memory chip, such as a ram memory, a flash memory, a cis memory, an EpR 〇M memory, a (four) job memory, a scratchpad, and other storage devices, such as a hard disk, removable. A disk, ROM, or any other form of storage medium known in the art that can store computer readable instructions. In addition, the program product m can be a source file, which includes receiving and acknowledging from the network _ &amp; mailing and storing in the memory and then executing the program steps in this manner as required by the operation of the present invention. The processing steps can be performed on the private f° 〇 714. In Fig. 7, an exemplary mass media is shown to be processed in the machine a, so that the host processor can read the information from the storage medium and write the media to the media. Alternatively, the storage medium can be integrated with the host processor. The user plane 716 is connected to the host processor and (10). For example, the user interface can include a keyboard or special function keys or buttons that are coupled to the host processor 71G and can be used by the user to request a particular operation by the activation device. The user interface 716 can also include a speaker that is coupled to the cafe 71 and used to output audio material to the user. /3⁄4 This technical person should understand that various technologies and technologies can be used to represent poor news and signals. For example, the data, instructions, signals, signals, bits, symbols, and wafers that may be mentioned in the above description may be from voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof. Those skilled in the art will further appreciate that the various illustrative logical regions &amp; modulating, circuit, and algorithm steps described in connection with the specific embodiments described herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above in terms of functionality. The functional implementation of this functionality into hardware or software depends on the particular application and design constraints imposed on the overall system. A person skilled in the art can implement the described functionality for each particular application in a variety of ways, but such implementation decisions should not be interpreted as causing a departure from the scope of the invention. The various illustrative logic illustrated in the specific embodiments disclosed herein. Blocks, modules, and circuits can be implemented as general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other customizable logic devices. Discrete gate or transistor logic, discrete hardware components or any of the 95324.doc -27-1353142 designs designed to perform the functions described herein are implemented or executed. A general purpose processor may be a microprocessor, but in another example, the processor may be any conventional processor, controller, microcontroller or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, or a plurality of microprocessors in conjunction with a DSP core or any other such configuration. The methods or techniques described in connection with the specific embodiments disclosed herein may be directly implemented as a hardware, a software module executed by a processor, or a combination of both. The software module can reside in RAM memory, flash memory, r〇m memory, EPROM memory, EEPRQM memory, scratchpad, hard drive, removable disk, CD-ROM, DVD storage or this Any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and write the information to the storage medium. In another example, the storage medium can be integrated with the processor. The processor and the storage medium can reside in an ASIC*. In 31 (: may reside in a user terminal, in the alternative, the processor and the storage medium may be placed in a user terminal in the form of discrete components. The previous description of the disclosed specific embodiments is provided to enable any The present invention is made by those skilled in the art, and it is to be understood by those skilled in the art that the invention may be practiced. Therefore, the present invention is not intended to be limited to the specific embodiments shown herein, but is in accord with the broad scope of the principles and novel features disclosed herein. Communication System; 95324.doc -28- 1353142 Figure 2 illustrates components of an exemplary wireless network that can communicate access to a packet data network via the system shown in Figure 301; Figure 3 illustrates the coding capability A block diagram of an exemplary format of the message; FIG. 4 is a call flow diagram illustrating an example of an MS and network using OTA to communicate a version/capability indication; 5 is a diagram illustrating an exemplary version/capability packet format; FIG. 6 is a diagram illustrating additional details of an exemplary support feature list block as shown in FIG. 5; FIG. 7 is an exemplary embodiment in accordance with the present invention. Block diagram of a constructed wireless communication device or MS. [Main component symbol description] 100 Communication system 101 Infrastructure 102 Base station 104 Wireless communication device 105 Wireless communication device 106 Base station controller 108 Mobile switching center 120 Switched network 122 Inland communication Device 124 Inland communication device 132 signal 134 signal 95324.doc -29· 1353142 136 138 202 206 208 210 302 304 402 404 406 408 410 412 414 416 418 420 500 502 504 506 508 510 signal signal packet data network packet data service node (PDSN) Base Station Controller/Packet Control Function (BSC/PCF) Mobile Station (MS) IS-835 Protocol Version Message Mobile Station (MS) Initiate Message Base Station Controller (BSC) A 9 - Set-A 8 Message Packet Control Function (PCF) Packet Data Service Node (PDSN)

All registration request message A11 registration reply message A9-connection-A8 message message packet code identification identification item length limit "magic number" column organization unique identification item column (OUI) 95324.doc -30- 1353142 512 514 516 602 604 606 702 706 708 710 712 714 716 Category bar Version column Support feature list column Group ID column length Flag marker communication device Network interface Digital signal processor (DSP) Host processor memory device program product user interface 95324.doc -31 -

Claims (1)

1353142 f drunk 叩 叩 本 093123534 Patent Application Order Application Patent Fan Park Replacement (June 100) X. Application Patent Scope · A kind of package information service for a mobile station, the method includes Establishing a physical layer connection to one of the wireless network infrastructures; receiving a first message comprising a first and a second block, the first column indicating the support in the wireless network infrastructure a standard version of the wireless packet data, the second column is connected through the air entity layer to indicate that one or more additional capability features supported in the network infrastructure are used corresponding to the wireless network infrastructure One of the standard versions of the non-packaged data standard supported by the network layer is to pass the package to the poor material, according to the standard version of the data support and the additional capability features supported by the road infrastructure. The mobile station generates the packet data; and transmits a second message including a third column and a fourth block, the second column indicating that the mobile station supports the wireless packet f The standard version, the fourth column indicating support within the mobile station _ or more additional capability features. 2. As requested! The method, wherein the wireless packet poor standard version supported in the mobile station is one of IS_835 versions. 3. The method of claim 1, wherein the standard version of the wireless packet data supported in the wireless network infrastructure is a version of IS-835. 4. The method of claim 1 wherein the air communication connection is a radio channel. 5. If the request item ^, &lt; 万法', the radio channel is a CDma channel. 6. As requested in Item 1 $, the network infrastructure further includes a packet data service node. 95324-1000615.doc 1353142 7. The method of claim 6, wherein the standard version of the wireless packet data supported by the network infrastructure is the version supported by the packet data service node. 8. The method of claiming, wherein the mobile station comprises a wireless telephone. 9. The method of claim 1, wherein the mobile station comprises a personal computer that communicates wirelessly. The method of claim 1, wherein the mobile station includes a number of assistants. </RTI> The method of claim 1, wherein the first message is received during initiation of a beacon session using the wireless network infrastructure. The method of claim 1 wherein the first message is received after initiation of a data session using the wireless network infrastructure. The method of claim 1, further comprising the one or more additional capability features supported by the wireless network infrastructure based on the wireless packet data standard version supported by the wireless network infrastructure= The mobile station = the supported standard version of the wireless packet data and the additional capability features supported by the mobile station to adjust the transmission protocol. 14. The method of item 1, wherein the one or more additional capability features are characterized by a plurality of features of the standard version of the home. ~, 15 - a mobile station, comprising: - a receiver configured to receive a first message through an airframe entity infrastructure, comprising a first and a line: a shed, the first The standard version of the wireless network infrastructure flawless packet data and one of the second aids should not be wireless network based 95324] 〇〇〇 615. doc -2 - One or more additional capability features supported in the infrastructure And processing the mobile station based on the standard version of the wireless packet data supported in the wireless network infrastructure and the one or more additional capability features supported within the wireless network infrastructure, configured to adjust the mobile station Operation 'and configured to transmit - a second message comprising - a third column and a fourth block, the second column indicating a standard version of the wireless packet data supported in the mobile station, the fourth column indicating the mobile station One or more additional capability features supported within the mobile station, such as the mobile station of request item 15, wherein the standard version of the wireless packet data supported by the mobile station is one of IS-835 versions. The mobile station of claim 15 wherein the wireless packet data standard version supported in the wireless network infrastructure is one of IS-835 versions. 18. The mobile station of claim 15, wherein the one or more additional capability characteristics correspond to a plurality of features of the wireless packet data standard version. 19. A wireless network infrastructure, comprising: a receiver configured to connect to a wireless network infrastructure via an airborne physical layer to receive a first message comprising -..." coin and a second a first column indicating a standard version of the wireless packet data supported by the mobile station and the second column indicating that the mobile station supports a plurality of additional capability features; or a processor according to the action The standard version of the wireless packet supported by the station and the additional capability features supported by the mobile station are configured to adjust the operation of the wireless network infrastructure and to transmit a second message, which includes a third column And a fourth block, the third shackle _ a j day should not be wireless 95324> 1000615.doc 20. One of the wireless packet data standard versions supported in the network infrastructure, the fourth block indicates the wireless network One or more additional capability features supported in the infrastructure. For example, the wireless network infrastructure of claim 19, wherein the standard version of the wireless packet data supported by the mobile station is IS-835 A version. 21. 22. 23. 24. 25. The wireless network infrastructure of claim 19, wherein the standard version of the wireless packet data supported in the wireless network infrastructure is one of IS_835 versions, such as a request item A wireless network infrastructure, further comprising a base station, such as the wireless network infrastructure of claim 19, further comprising a packet data service node, such as the wireless network infrastructure of claim 19, wherein the one or The plurality of additional capability features correspond to a plurality of features of the wireless packet data standard version. A computer readable medium implementing a method of communicating packet data, comprising: a recordable medium; and a plurality of recorded on the medium The instructions, when read by a computer, cause the computer to perform the following operations, comprising: establishing an airborne physical layer connection using a wireless network infrastructure; receiving a first message comprising a first barrier and a first Second, the first paste indicates a standard version of the wireless packet data supported by the wireless network infrastructure, and the second barrier passes the empty The physical layer connection indicates one or more additional capability features supported within the section wireless network infrastructure; 95324-1000615.doc 1353142 uses the standard version of the wireless packet data supported in the wireless network infrastructure - The network layer transmits the packet data, generates the packet data in the mobile station according to the standard version of the wireless packet data supported by the wireless network infrastructure and the additional capability features; and transmits a second message, including A third column and a fourth block indicating a standard version of the wireless packet data supported by the mobile station, the fourth column indicating one or more additional capability features supported in the mobile station. 26. The computer readable medium of claim 25, wherein the standard version of the wireless packet data supported by the mobile station is one of IS_835 versions. 27. The computer readable medium of claim 25, wherein the wireless packet data standard version supported by the wireless network infrastructure is one of IS_835 versions. 28. The computer readable medium of claim 25, wherein the operations further comprise a standard version of the wireless packet data supported by the wireless network infrastructure, the wireless network infrastructure supporting the One or more additional capability features, a standard version of the wireless packet data supported by the mobile station, and the one or more additional capability features supported within the mobile station to adjust a delivery protocol. 29. The computer readable medium of claim 25, wherein the one or more additional capability traits correspond to a plurality of features of the wireless packet data standard version. 95324-1000615.doc