Agw Tracker serial key or number

Agw Tracker serial key or number

Agw Tracker serial key or number

Agw Tracker serial key or number

US20080020745A1 - Method and apparatus for supporting communication service of idle user terminal located in common routing area in a mobile communication system - Google Patents

Method and apparatus for supporting communication service of idle user terminal located in common routing area in a mobile communication system Download PDF

Info

Publication number
US20080020745A1
US20080020745A1US11/784,114US78411407AUS2008020745A1US 20080020745 A1US20080020745 A1US 20080020745A1US 78411407 AUS78411407 AUS 78411407AUS 2008020745 A1US2008020745 A1US 2008020745A1
Authority
US
United States
Prior art keywords
information
routing area
network
terminal
hss
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.)
Abandoned
Application number
US11/784,114
Inventor
Eun-Hui Bae
Sung-Ho Choi
O-Sok Song
No-jun Kwak
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority to KR2006-31145priorityCritical
Priority to KR1020060031145Aprioritypatent/KR20070099849A/en
Application filed by Samsung Electronics Co LtdfiledCriticalSamsung Electronics Co Ltd
Assigned to SAMSUNG ELECTRONICS CO., LTD.reassignmentSAMSUNG ELECTRONICS CO., LTD.ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).Assignors: BAE, EUN-HUI, CHOI, SUNG-HO, KWAK, NO-JUN, SONG, O-SOK
Publication of US20080020745A1publicationCriticalpatent/US20080020745A1/en
Abandonedlegal-statusCriticalCurrent

Links

  • 238000010295mobile communicationMethods0.000titleclaimsabstractdescription15
  • 238000004891communicationMethods0.000titleclaimsabstractdescription8
  • 230000005540biological transmissionEffects0.000claimsabstractdescription5
  • 238000000034methodsMethods0.000description28
  • 238000005516engineering processesMethods0.000description1

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • 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
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements

Abstract

Description

  • This application claims priority under 35 U.S.C. §119(a) to a Korean Patent Application filed in the Korean Intellectual Property Office on Apr. 5, 2006 and assigned Serial No. 2006-31145, the disclosure of which is incorporated herein by reference.
  • 1. Field of the Invention
  • The present invention relates generally to a mobile communication system, and in particular, to an apparatus and method for registering terminal information when a terminal in an idle mode is located in a common routing area. In addition, the present invention relates to a method and apparatus in which a terminal that has ever forwarded a voice call being delivered to a specific terminal located in a routing area, to the specific terminal via an IP Multimedia Subsystem (IMS) network and a Long Term Evolution (LTE) network, or ever received a voice call via the IMS network and the LTE network, can seamlessly receive the voice call over the IMS network and the LTE network even when it moves to a 3rd Generation (3G) network.
  • 2. Description of the Related Art
  • The 3rd Generation Partnership Project (3GPP) is in charge of Universal Mobile Telecommunications System (UMTS) standardization. In 3GPP, Long Term Evolution (LTE) is now under discussion as the next generation mobile communication system of the UMTS system. LTE, aiming for deployment in about 2010, is technology for implementing high-speed packet based communication at approximately 100 Mbps. To this end, several schemes are under discussion, and for example, those schemes include one scheme for reducing the number of nodes located in a communication path by simplifying the network configuration, and another scheme for maximally approximating wireless protocols to wireless channels. As a result, it is expected that the LTE configuration will change from the existing 4-node configuration to a 2-node or 3-node configuration.
  • The LTE network with the simple node configuration, as it interworks with the existing 3G network, can exchange voice and data with an existing user terminal, guaranteeing backward compatibility.
  • illustrates a connection configuration between an LTE network and a 3G network in a mobile communication system.
  • Referring to , the illustrated configuration provides Circuit Switched (CS) voice services and Packet Switched (PS) data services to a terminal 105, or User Equipment (UE), based on a 3G-UMTS network 110, an LTE-Evolved UMTS (LTE-EUMTS) network 155, and an IMS network 135.
  • Specifically, when the terminal 105 exists in a 3G network 110, the terminal 105, for exchanging CS calls with a CS Core Network (CN) 130, sends signaling to a Radio Network Controller (RNC) 115 connected to the terminal 105, among a plurality of RNCs connected to an Gateway Mobile Switching Center (GMSC) 125 in the 3G network 110. The GMSC 125 can acquire information on the terminal 105 through a Home Subscriber Server (HSS) 150.
  • As for a PS call, an IMS network 135 is connected to a Serving GPRS Support Node (SGSN) 120 in the 3G network 110, and the RNC 115 forwards a received PS call delivered from the SGSN 120 to the terminal 105.
  • The LTE network 155 includes an Access Gateway (AGW) 160 and an Evolved Node B (ENB) 165. The AGW 160 corresponds to a Core Network Entity that takes charge of a User Plane Control function (for example, Gateway GPRS Support Node (GGSN)) and a Control Plane Control function (for example, SGSN). The ENB 165, a node corresponding to the existing Node B, is connected to the terminal 105 over a wireless channel. Compared with the existing Node B, the ENB 165 performs a complex function.
  • In LTE, all user traffic including real-time services, such as Voice over Internet Protocol (VoIP) will be serviced over shared channels, and this means that there is a need for an apparatus of collecting status information of terminals 105 and performing scheduling depending thereon. The scheduling is managed by the ENB 165.
  • The IMS network 135 includes Call Session Control Functions (CSCFs) 140 and interworking entities 145.
  • The CSCFs 140 include a Serving-Call Session Control Function (S-CSCF) in charge of SIP-based call setup to a terminal operating based on Session Initiation Protocol (SIP), a Proxy-Call Session Control Function (P-CSCF) in charge of Signaling Control with the 3G-UMTS network 110 and the LTE-EUMTS network 155, and an Interrogating-Call Session Control Function (I-CSCF) in charge of performing search of the S-CSCF and hiding the IMS network 135 from the external network. The interworking entities 145 include a Switching Gateway (SGW) in charge of interworking with CS Signaling and IMS Signaling, and a Media Gateway Control Function (MGCF).
  • When the terminal 105 moves from the 3G network 110 to the LTE network 155 (PS-only network) based on the network shown in , a CS voice call being delivered to the terminal 105 will be converted into a PS data call before delivery. Similarly, when the terminal 105 moves from the LTE network 155 to the 3G network 110, a PS data call being delivered to the terminal 105 via the LTE network 155 will be converted into a CS voice call through a Circuit Switched Core Network (CS CN) 130 of the 3G network, or converted into a PS data call through a Packet Switched Core Network (PS CN) of the 3G network before the delivery to the terminal 105.
  • In this system configuration, when a terminal is in an idle state and is currently located in the physically same area for the 3G network and the LTE network, i.e. when a routing area (RA) in the 3G network and a tracking area in the LTE network are located in the same common routing area (or Common RA), if the terminal frequently performs routing area update (i.e. moves from the LTE network to the 3G network) and/or tracking area update (i.e. moves from the 3G network to the LTE network) within coverage of the common routing area, conversion of a CS voice call being delivered to the terminal into a PS call and/or conversion of a PS call based on the LTE network into a PS call based on the 3G network are continuously performed.
  • In the foregoing conventional mobile communication network system, there is a need for a scheme of realizing the concept of the common routing area for minimizing unnecessary signaling due to movement in the area where frequent inter-system change occurs as the system is generally established in the boundary between the LTE network and the 3G network. In addition, due to the characteristics of the CS voice call supportable in the 3G network, in order to process a CS call in the common routing area proposed for reducing signaling for mobility control due to the movement of the terminal, additional signaling is needed undesirably.
  • An aspect of the present invention is to address at least the problems and/or disadvantages above and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a method and apparatus for registering a mobile terminal in a common routing area to minimize unnecessary signaling due to movement in an area where frequent inter-system change occurs in a mobile communication network system established in the boundary between an LTE network and a 3G network.
  • Another aspect of the present invention is to provide a method and apparatus for delivering a voice call to a terminal when a tracking area for a terminal in an idle mode in an LTE network and a routing area for a terminal in an idle mode in a 3G network are equal to each other.
  • Another aspect of the present invention is to provide a method and apparatus capable of always receiving a PS call via an LTE network, for a CS voice call, to reduce interworking overhead for the CS call and the PS call when system change occurs from a 3G network to the LTE network or from the LTE network to the 3G network as movement occurs in a common routing area after a terminal accesses the LTE network, or even when a CS call can be received through a CS connection of the 3G network.
  • Another aspect of the present invention is to provide a method and apparatus for converting all CS voice calls being delivered to a terminal into PS data calls before delivery by registering, in an HSS, a terminal, if any, located in a common routing area in a mobile communication system.
  • According to one aspect of the present invention, there is provided a method for supporting a communication service of an idle mode terminal located in a common routing area in a mobile communication system that includes a Node B, an Access Gateway (AGW), and a Home Subscriber Server (HSS), and has a Long Term Evolution (LTE) network and a 3rd Generation (3G) network connected to each other to perform transmission/reception. The method includes receiving, by the AGW, tracking area information of the LTE network, including routing area information of the 3G network, from the idle mode terminal via the Node B; sending, by the AGW, common routing area indication information and identification information of the terminal to the HSS if the routing area information is coincident with the tracking area information; and storing, by the HSS, the common routing area indication information and the identification information of the terminal, and sending a response message according to the indication information.
  • According to another aspect of the present invention, there is provided a apparatus for supporting a communication service of an idle mode terminal located in a common routing area in a mobile communication system in which a Long Term Evolution (LTE) network and a 3rd Generation (3G) network are connected to perform transmission/reception. The apparatus includes a Home Subscriber Server (HSS) for performing tracking area update to register routing area information of the LTE network and storing common routing area information; an Access Gateway (AGW) for receiving, from the terminal, tracking area information of the LTE network, including routing area information of the 3G network from the idle mode terminal, comparing the routing area information with the tracking area information, and sending common routing area indication information and identification information of the terminal to the HSS if the routing area information is coincident with the tracking area information; and the HSS for storing the common routing area information and the identification information of the terminal, and sending a response message according to the common routing area indication information.
  • The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings in which:
  • is a diagram illustrating a connection configuration between an LTE network and a 3G network in a mobile communication system;
  • is a diagram illustrating a process of registering common routing area information in an HSS according to a preferred embodiment of the present invention;
  • is a diagram illustrating a call reception procedure of a terminal in a mobile communication system in which an LTE network and a 3G network are connected according to a preferred embodiment of the present invention; and
  • is a diagram illustrating a process of converting a CS call into a PS call and delivering the PS call to an idle terminal via an IMS network according to a preferred embodiment of the present invention.
  • Exemplary embodiments of the present invention will now be described in detail with reference to the annexed drawings. In the following description, a detailed description of known functions and configurations incorporated herein has been omitted for clarity and conciseness.
  • The present invention provides a method and apparatus for delivering a voice call to a terminal when a tracking area (or routing area) for a terminal in an idle mode (or sleep mode) in an LTE network and a routing area for a terminal in an idle mode in a 3G network are equal to each other, i.e. when a terminal in the idle mode is located in a common routing area.
  • In addition, the present invention provides a method and apparatus in which after the time a terminal has attached to (or accessed) an LTE network or after the time the terminal has moved to the LTE network, converted a CS call being delivered thereto into a PS call and then received the PS call, the terminal can always receive the CS voice call via the LTE network to reduce interworking overhead for a CS call and a PS call, even in the situation where the terminal can receive the CS call via a CS connection of a 3G network, while maintaining the CS connection and a PS connection of the 3G network as system change occurs from the 3G network to the LTE network or from the LTE network to the 3G network due to movement of the terminal in a common routing area.
  • Further, the present invention provides a method and apparatus in which when a terminal is located in a common routing area, a network (for example, HSS) maintains information indicating the presence of the terminal in the common routing area, thereby enabling automatic conversion of a CS voice call being delivered to the terminal into a PS data call when the terminal is located in an LTE network. In addition, as for a terminal that has converted a CS voice call into a PS data call and received the PS data call through the LTE network, the terminal can seamlessly convert the CS voice call into the PS data call and receive the PS data call through the LTE network using common routing area information of the terminal, being maintained in the HSS, even when the terminal moves from the LTE network to the 3G network. The scheme of maintaining Common RA information through the HSS provides a scheme for efficiently processing the CS voice call and also allows seamless connection of the CS connection and the PS connection of the 3G network for smooth delivery of voice/packet data to the terminal as the terminal moves from the 3G network to the LTE network, thereby reducing overhead for connection reset and security reset due to the frequently occurring movement between the LTE network and the 3G network.
  • To this end, an embodiment of the present invention provides one scheme of registering, in an HSS, common routing area information of a terminal when the terminal accesses an LTE network, or when the terminal in an idle mode moves from a 3G network to the LTE network, and another scheme of converting a CS voice call into a PS data call through an IMS network and the LTE network using the information stored in the HSS.
  • illustrates a process in which a terminal registers, in an HSS, common routing area information through an access process or a tracking area update process according to a preferred embodiment of the present invention.
  • Referring to , when a terminal 101 (or a Mobile Station (MS)) in an idle mode, located in a 3G network, moves to an LTE network, the terminal 101 sends in step 201 a Tracking Area Update (TAU) Request message to an AGW 105, which is an LTE core network entity, in order to perform a TAU (or Routing Area Update (RAU)) process. The TAU Request message includes information on a routing area in the 3G network.
  • Upon receipt of the TAU Request message, the AGW 105 compares, in step 203, its current tracking area information (TAI) with routing area information (RAI) in the 3G network, sent by the terminal 101. If the tracking area information is coincident with the routing area information, the AGW 105 sends in step 205, to an HSS 107, common routing area indication information for indicating the coincidence between the routing area and the tracking area for the terminal 101. The common routing area indication information can be individually sent to the HSS 107 over a separate message, or the indication information can be added to an existing message (for example, Update Location message) for registering information of the AGW 105 in the HSS 107 and then registered in the HSS 107.
  • Upon receipt of the common routing area indication information indicating that both the 3G network and the LTE network are serviceable in the current location of the terminal 101, the HSS 107 stores in step 207 the common routing area indication information and user Identity (ID) information included together with the indication information. The HSS 107 sends in step 209 a response message (or Ack message) for the common routing area indication information to the AGW 105.
  • The response message for the common routing area indication information is optional, and when the common routing area indication information is piggybacked on the existing message, it follows an operation of a response message (for example, Location Update Accept message) for the existing message. If information (for example, information on an MSC 113 or information on an SGSN) on the 3G network of the terminal 101, which has sent to the HSS 107 the indication information indicating that the terminal 101 is currently located in the common routing area, is stored, the HSS 107 additionally stores the common routing area indication information of the terminal 101 without deleting the existing registration information for the terminal 101. On the contrary, if the common routing area indication information is not sent to the HSS 107, the HSS 107 should delete the previously stored common routing area indication information for the corresponding terminal. A security-related operation and a context transfer operation of step 211 occurring in a TAU process, and a Tracking Area Update Accept process of step 213 follow the existing scheme or a scheme defined in LTE, and a description thereof will be omitted herein because they are not related to the present invention.
  • Although the scheme of registering common routing area information in the HSS 107 in the tracking area update process has been described herein, the terminal can register the common routing area information in the HSS 107 in the same manner using the foregoing operations, through a process of first accessing the LTE network.
  • In the conventional method, if TAU is completed after movement from the 3G network to the LTE network, the HSS deletes information on a CS network of the 3G network, i.e. information on both a connection and a PS network. Therefore, if the terminal moves back to the 3G network later, the conventional method must re-perform the process of registering in the HSS the information necessary for security setting and connection setting. Thus, in , if the terminal is located in a specific area called a Common RA, the information indicating that the terminal is located in the Common RA is registered in the HSS to make the best use of the characteristics of this area, thereby reducing additional processing.
  • illustrates a call reception procedure of a terminal in a mobile communication system in which an LTE network and a 3G network are connected according to a preferred embodiment of the present invention.
  • Referring to , an HSS 350 stores in step 301 common routing area information through the tracking area update process described in , and sends in step 303 common routing area indication information to an MSC 325. The common routing area indication information sent from the HSS 107 to the (G)MSC 113 (325) is information indicating that a CS voice call being delivered to the terminal should be sent via the LTE network. This information can be an indication interpretable in the MSC 113 (see ), or can be an address for call delivery to the LTE network.
  • Thereafter, if the MSC 325 receives in step 305 a CS voice call signal from a CS 330, it sends information ordering conversion from a CS call to a PS call to interworking entities 345 of an IMS network 335 based on the received common routing area indication information, and the interworking entities 345 send an INVITE message to a CSCF 340 after the call conversion. The CSCF 340 sends the INVITE message to an AGW 360 along with the packet data being exchanged with an LTE network 355.
  • A paging procedure is performed between the AGW 360 and a terminal 370 to exchange packet data including the INVITE message. As a result, the CS voice call signal received at the MSC 325 is converted into a PS call and then delivered to the terminal 370 without system modification while the terminal 370 moves in the common routing area.
  • illustrates a process of converting a CS voice call being delivered to a terminal into a PS data call through an IMS network and an LTE network before delivery, using common routing area information registered in an HSS through a tracking area update process according to a preferred embodiment of the present invention.
  • If a terminal 101 in an idle state, located in a 3G network, moves to an LTE network, the terminal 101 performs in step 401 a tracking area update process to the LTE network. A scheme of registering, in an HSS, location information of the terminal, i.e. common routing area information, through the tracking area update has been described with reference to . The process in step 401 sends context information such as QoS and security information of the terminal from the 3G network to the LTE network, sets up a radio connection between the terminal 101 and an ENB 103, and sets up a bearer between the ENB 103 and an AGW 105. After completion of step 401, the terminal 101 performs in step 403 authentication on an IMS network and an IMS registration process for registering, in an HSS 107, terminal ID information (for example, Public User Identity and Private User Identity) to be used in the IMS network, and an S-CSCF 109 for the terminal 101.
  • The IMS registration process of step 403 is equal to the operation specified in 3GPP TS23.228 (IP Multimedia Subsystem; Stage 2) and TS24.229 (IP multimedia call Control protocol based on SIP and Session Description Protocol (SDP); Stage 3), so an additional description thereof will be omitted.
  • If an Initial Address Message (IAM) message, a request message for setting up a CS call to the terminal 101 that has moved to the LTE network, is sent in step 405, the CS CN entity (or (G)MSC) 113 in the 3G network, receiving the IAM message, sends a Query message for routing information to the HSS 107 in step 407 to detect the current location information of the terminal 101. Because the information indicating that the terminal 101 is located in the common routing area and the CS voice call for the corresponding terminal 101 should be converted into the PS data call, has already been registered in the HSS 107 through the tracking area update process of step 401, the CS-to-PS conversion information is sent to the (G)MSC 113 in the 3G network using a Response message in step 411. From the Response message, the (G)MSC 113 acquires information indicating that it should send to the terminal 101 a CS call setup request message (shown in step 405) to the terminal 101 via the IMS network and the LTE network, i.e. the AGW 105.
  • To this end, the 3G (G)MSC 113 sends an IAM message, which is a CS call setup request message, to interworking entities 111 (for example, MGCF (Media Gateway Control Function) and SGW (Service Gateway) in the IMS network in step 413. A scheme of sending the IAM message from the 3G (G)MSC 113 to the interworking entities 111 follows the method defined in 3GPP TS29.163 (Interworking between the IMS and CS networks), and a detailed description thereof will be omitted herein because it is not related to the present invention. Upon receiving the IAM message or the CS call setup request message, the interworking entities 111 in the IMS network perform in step 415 an operation of converting a CS message into an IMS Session Initiation Protocol (SIP) message.
  • An INVITE message, which is an SIP-based call (or session) setup request message generated by the interworking entities 111, is sent to the S-CSCF/P-CSCF 109 in step 417, and the INVITE message is sent to the AGW 105, which is a CN entity of the LTE network, in the IP packet format in step 419. Upon receipt of packet data including the SIP INVITE message, the AGW 105, recognizing that the terminal 101 is in the idle state, performs in step 421 a paging procedure for detecting an accurate location of the terminal 101 through a process of broadcasting a Paging Request message to the corresponding tracking area and receiving a Paging Response message to detect the accurate location in the LTE network, and reestablishing a bearer.
  • After detecting the location of the terminal 101 and establishing a bearer for packet data delivery through the paging procedure of step 421, the AGW 105 sends packet data including an INVITE message to the terminal 101 in step 423. Upon receipt of the packet data, the terminal 101 sends a 200 OK response message for the call setup to the AGW 105 along with packet data and the AGW 105 forwards the 200 OK message to the P-CSCF/S-CSCF 109, in step 425. Upon receipt of the 200 OK message, the P-CSCF/S-CSCF 109, which is an IMS entity, forwards the 200 OK message to the interworking entities 111 in step 427 to covert the 200 OK message into an ISDN User Part (ISUP) message. Through the interworking entities 111, the 200 OK message is converted into an Answer Message (ANM), or an ISUP message, and then sent to the called party via a CS network in step 429.
  • As can be understood from the foregoing description, when a terminal is located in a common routing area, the present invention registers the corresponding information in an HSS to convert all CS voice calls being delivered to the terminal into PS data calls before delivery, thereby reducing overhead of the procedure for converting the CS voice calls into the PS data calls, which may incidentally occur due to the frequent movement of the terminal in the common routing area. In addition, when a terminal is located in a common routing area, the present invention registers the corresponding information in an HSS to maintain the CS connection information and PS connection information of the 3G network for the corresponding terminal without deleting the information, thereby reducing overhead of the procedure for CS connection and PS connection reestablishment of the 3G network, and security reestablishment for the HSS, which may incidentally occur due to the frequent movement of the terminal in the common routing area.
  • While the invention has been shown and described with reference to a certain preferred embodiment thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims (8)

1. A method for supporting a communication service of an idle mode terminal located in a common routing area in a mobile communication system that includes a Node B, an Access Gateway (AGW), and a Home Subscriber Server (HSS), and has a Long Term Evolution (LTE) network and a 3rd Generation (3G) network connected to each other to perform transmission/reception, the method comprising:
receiving, by the AGW, tracking area information of the LTE network, including routing area information of the 3G network, from the idle mode terminal via the Node B;
sending, by the AGW, common routing area indication information and identification information of the terminal to the HSS if the routing area information is coincident with the tracking area information; and
storing, by the HSS, the common routing area indication information and the identification information of the terminal, and sending a response message according to the indication information.
2. The method of , further comprising:
sending, by the HSS, indication information indicating that a Circuit Switched (CS) voice call to the terminal should be delivered via the LTE network, in response to a location confirm request of the terminal for delivering a CS voice call from the 3G network; and
converting a CS voice call of the 3G network into a Packet Switched (PS) call of the LTE network based on the indication information before call delivery.
3. The method of , wherein the common routing area indication information is information indicating that a CS voice call of the 3G network is always converted into a PS call of the LTE network for call service.
4. The method of , further comprising:
after receiving the indication information, maintaining CS connection information and PS connection information of the 3G network without deleting the information.
5. An apparatus for supporting a communication service of an idle mode terminal located in a common routing area in a mobile communication system in which a Long Term Evolution (LTE) network and a 3rd Generation (3G) network are connected to perform transmission/reception, the apparatus comprising:
a Home Subscriber Server (HSS) for performing tracking area update to register routing area information of the LTE network and storing common routing area information;
an Access Gateway (AGW) for receiving, from the terminal, tracking area information of the LTE network, including routing area information of the 3G network from the idle mode terminal, comparing the routing area information with the tracking area information, and sending common routing area indication information and identification information of the terminal to the HSS if the routing area information is coincident with the tracking area information; and
the HSS for storing the common routing area information and the identification information of the terminal, and sending a response message according to the common routing area indication information.
6. The apparatus of , further comprising a Mobile Switching Center (MSC) for sending Packet Switched (PS) indication information to an interworking entity so as to convert a voice call of the 3G network into a PS call of the LTE network based on indication information, received from the HSS, indicating that a Circuit Switched (CS) voice call to the terminal is delivered via the LTE network.
7. The apparatus of , wherein the common routing area indication information is information indicating that a CS voice call of the 3G network is always converted into a PS call of the LTE network for call service.
8. The apparatus of , wherein after receiving the indication information, the HSS maintains CS connection information and PS connection information of the 3G network without deleting the information.
US11/784,1142006-04-052007-04-05Method and apparatus for supporting communication service of idle user terminal located in common routing area in a mobile communication system AbandonedUS20080020745A1 (en)

Priority Applications (2)

Application NumberPriority DateFiling DateTitle
KR2006-311452006-04-05
KR1020060031145AKR20070099849A (en) 2006-04-052006-04-05Method and apparatus for transmitting circuit switched call to an idle user equipment in a common routing area of a mobile communication system

Publications (1)

ID=38563872

Family Applications (1)

Application NumberTitlePriority DateFiling Date
US11/784,114AbandonedUS20080020745A1 (en) 2006-04-052007-04-05Method and apparatus for supporting communication service of idle user terminal located in common routing area in a mobile communication system

Country Status (3)

Cited By (61)

Publication numberPriority datePublication dateAssigneeTitle
US20080268878A1 (en) *2007-04-262008-10-30Interdigital Technology CorporationMethod and apparatus of measurement mechanism and efficient paging and broadcasting scheme implementation in mbms dedicated cell of lte systems
US20090119404A1 (en) *2007-11-022009-05-07Nortel Networks LimitedMethod for Improving Subscriber Data Integrity in an IMS Network
WO2009135365A1 (en) *2008-05-042009-11-12中兴通讯股份有限公司Method and device for deployment of tracking areas
WO2010071545A1 (en) *2008-12-172010-06-24Telefonaktiebolaget L M Ericsson (Publ)Methods and arrangements in a wireless communication network for handling at least one primary tracking area
US20110002267A1 (en) *2009-06-032011-01-06Johanna Lisa DwyerVoice service in evolved packet system
US20110158165A1 (en) *2009-07-022011-06-30Johanna Lisa DwyerMethods and apparatus for mobile voice service management
US20110176436A1 (en) *2009-07-232011-07-21Arvind SwaminathanMethod and apparatus that facilitates redirecting wireless terminals between wireless networks
US20110182249A1 (en) *2010-01-282011-07-28Verizon Patent And Licensing, Inc.Data offloading at wireless node
US20110256873A1 (en) *2008-12-232011-10-20Telefonaktiebolaget Lm Ericsson (Publ)Maintaining current cell location information in a cellular access network
US20110268035A1 (en) *2009-01-092011-11-03Kazunori OzawaGateway apparatus, gateway method, and program
US20110320569A1 (en) *2009-04-172011-12-29Lae Young KimMethod for performing inter-user equipment transfer in wireless communication system based on internet protocol multimedia subsystem
US20120011257A1 (en) *2009-04-172012-01-12Lae Young KimMethod for performing transfer of collaborative session control in wireless communication system based on internet protocol multimedia subsystem
US20120057569A1 (en) *2009-05-222012-03-08Zte CorporationMethod for realizing single radio voice call continuity and single radio voice call continuity system
US20130188606A1 (en) *2010-09-282013-07-25Zte CorporationMethod and system for switching circuit switch domain service to packet switch domain
CN103546885A (en) *2012-07-092014-01-29中兴通讯股份有限公司Digital trunked communication system based location updating method and system
US8755329B2 (en) 2010-06-112014-06-17Blackberry LimitedMethods and apparatus for voice domain operation
US20140295800A1 (en) *2007-08-312014-10-02Huawei Technologies Co., Ltd.Method, System and Device for Negotiating Security Capability when Terminal Moves
US9118655B1 (en) 2014-01-242015-08-25Sprint Communications Company L.P.Trusted display and transmission of digital ticket documentation
US9161325B1 (en) 2013-11-202015-10-13Sprint Communications Company L.P.Subscriber identity module virtualization
US9161227B1 (en) *2013-02-072015-10-13Sprint Communications Company L.P.Trusted signaling in long term evolution (LTE) 4G wireless communication
US9171243B1 (en) 2013-04-042015-10-27Sprint Communications Company L.P.System for managing a digest of biographical information stored in a radio frequency identity chip coupled to a mobile communication device
US9185626B1 (en) 2013-10-292015-11-10Sprint Communications Company L.P.Secure peer-to-peer call forking facilitated by trusted 3rd party voice server provisioning
US9183606B1 (en) 2013-07-102015-11-10Sprint Communications Company L.P.Trusted processing location within a graphics processing unit
US9183412B2 (en) 2012-08-102015-11-10Sprint Communications Company L.P.Systems and methods for provisioning and using multiple trusted security zones on an electronic device
US9191522B1 (en) 2013-11-082015-11-17Sprint Communications Company L.P.Billing varied service based on tier
CN105072706A (en) *2015-07-022015-11-18中国联合网络通信集团有限公司Business processing method and system based on double-card terminal
US20150340139A1 (en) *2012-10-022015-11-26Siemens AktiengesellschaftSuperconductive coil device and production method therefor
US9210576B1 (en) 2012-07-022015-12-08
Источник: [https://torrent-igruha.org/3551-portal.html]
, Agw Tracker serial key or number

Welcome!
I hope you're here because you're interested in tracking something at a rally in the US. I set this website up to be as friendly and as EASY as possible for YOU to get into Amateur Radio Automatic Position Reporting System Tracking! Wow - that was a complicated mouthful.. Please keep reading and I'll walk you through it.

TrackerBox is a case containing several pieces of integrated hardware for sending APRS (Automatic Position Reporting System) packet data over 144.390Mhz. It was designed for use in rally cars, sweep vehicles, and general stage rally use and abuse. The TrackerBox system itself is NOT COMMERCIAL and you MUST have an amateur radio licence to purchase and use it.

Step One: Discover what APRS is.
I'm excited to tell you about it, because I think it's a cool piece of technology that lets everyone in on the action. I'm sure it may seem complicated at first, but it's easy to setup and use - even in a rallycar! Plus it's cheap! (One time cost of 2-3 rally tires) Please continue reading the Frequently Asked Questions section if you don't know what APRS is.

Step Two: Get you amateur (ham) radio licence.
(or convince your co-driver to - or better yet BOTH of you get it)
No morse code needed. Start taking the practice test and study on-line. Click here for the eHam practice tests. Click on "Technician - (July 1, 2006 question pool)" and take this until you can get at least a 90% three times in a row. Any questions on the questions, just copy it into Google and you'll find it! Maybe you're more of a book person? Check out this book and more at ARRL.com.

Get your FCC FRN Number here. Then find a local test center by clicking - find me a local test center. Take the test - good luck - congratulations you're a ham! Look online for your callsign.

Step Three: Put together the hardware.
eBay is a SELLERS market. If you want good cheap gear I suggest you hit a swap meet or buy new. You might be able to pickup a used HT for $50 for your tracker box. I have included the best radio IMO to stuff in a box and possibly use for emergencies. It will save you $60, but it may take a month to find one...

Keep in mind - if you have a radio other then a Yaesu, you will need to find your own power, tracker, and antenna adapters. Check out the parts list for links to where you can find these items. Let me know if you want to use another radio and I will subtract these items from your TrackerBox. The Yaesu radio takes 12v power, has a SMA antenna connector and a 4 contact 1/8" stereo cable for its connection to the tracker.




The TrackerBox in action.


10 TrackerBoxes ready to go!


Here's what it's all about:
I'm basically doing this so that a lot more people have the ability to take advantage of APRS. I have been asked by several people to provide a turn-key kit for rally. This will get more rally people into amateur radio and more amateur radio people into stage rally. I only want to make enough to cover the cost of my time and shipping. I provided all the links to various items - there are no doubt other ways to build one of these - but I feel this would be your best bet. If you have the ability, I encourage you to go out on your own or modify what I have here. Seeing 10+ cars at a rally with APRS beacons on a big screen in service is my goal. Following the action of a US national level rally from the internet would be cool too.

Programming? YES! Programming.
The OpenTracker+ included with the TrackerBox can easily be programmed with a windows machine that has a serial port, null modem cable, and the OpenTracker+ software.

Don't have an old laptop? I recommend the IBM 600 series.
Don't have a serial port? Get a USB Serial adapter.
You will need a null modem cable. Click here to find one.
You will need the OpenTracker+ Windows software - download here.
Download a copy of the OpenTracker+ Manual.

Here is what the settings page looks like:


Check to see if your packets are getting on the internet.
aprs.he.fi
findu.com

Stop and take a breath :)

Everything past this step MAY be done by your local rally. They may have a station setup for your crew to check in on your APRS beacon. If they don't have this yet - ASK! Talk to the communications captain or the rally organizers. Tell them you are running APRS in your car and that you are a ham. Tell them that you would love for your crew to be able to watch the rally in real time. Send them to this website to see what it's all about! Maybe get together with other crews who have this setup. This way you're not all bringing laptops and scanners. :)

Laptop and Scanner for the crew.
Get a used laptop with a sound card. You will need AGW Packet Engine - KC2RLM has a great site on how to install and set it up. You just want a stereo cable to receive only. You will need AGW Tracker - Go to the AGW Tracker download page. You will need a used radio scanner (police scanner) that can receive 144.390Mhz - Click here to find a used one. Should be around $30. You don't need any memories or trunking, just handheld and takes batteries.

Power on your scanner, plug in to your line-in, fire up the packet engine and start receiving packets. Now you'll just need a map that can be downloaded locally...

Get a local map.
Right now I can't find any good resources on how to make local maps. Here is one site with info.
I personally have created a number of local maps that can be loaded into AGWTracker. I hope to collect a local downloadable map for every rally in the US. If you can't find one, or can't find someone to make you one - I'll try to do it for the rally. Email me -

The .jpg is the image and the .inf are the LAT/LON coordinates.
You will need both. Save them in:

C:\Program Files\AGWSoft\AGWTracker

maps/DS2008.jpg
maps/DS2008.inf
maps/2007_PrescottRally_hires.jpg
maps/2007_PrescottRally_hires.inf
maps/2007_LaughlinRally_hires.jpg
maps/2007_LaughlinRally_hires.inf
maps/jean_NV_seed9.jpg
maps/jean_NV_seed9.inf



In closing - There is a lot more to be updated and discovered. As of 2-28-2008 this is what I've got. - Kris

5/1/2008 - TrackerBox Walkthrough.wmv

Источник: [https://torrent-igruha.org/3551-portal.html]
Agw Tracker serial key or number
BPQ Home   BPQ32 Home

Recent Changes to BPQ32 Node

24 April 2020 Version 6.0.20.1

Trap and reject YAPP file transfer request
Fix possible overrun of TCP to Node Buffer
Fix possible crash if APRS WX file doesn't have a terminating newline
Change communication with BPQAPRS.exe to restore old message popup behaviour
Preparation for 64 bit version
Improve flow control on SCS Dragon
Fragment messages from network links to L2 links with smaller paclen
Change WL2K report rate to once every two hours
Add PASS, CTEXT and CMSG commands and Stream Switch support to TNC2 Emulator
Add SessionTimeLimit command to HF drivers (ARDOP, SCSPactor, WINMOR, VARA)
Add links to Ports Web Management Page to open individual Driver windows
Add STOPPORT/STARTPORT support to ARDOP, KAM and SCSPactor drivers
Add CLOSE and OPEN RADIO command so Rigcontrol port can be freed for other use
Don't try to send WL2K Traffic report if Internet is down
Move WL2K Traffic reporting to a separate thread so it doesn't block if it can't connect to server
ADD AGWAPPL config command to set application number. AGWMASK is still supported
Register Node Alias with UZ7HO Driver
Register calls when UZ7HO TNC Restarts and at intervals afterwards
Fix crash when no IOADDR or COMPORT in async port definition
Fix Crash with Paclink-Unix when parsing ; VE7SPR-10 DE N7NIX QTC 1
Only apply BBSFLAG=NOBBS to APPPLICATION 1
Add RIGREONFIG command
fix APRS RECONFIG on LinBPQ
Fix Web Terminal scroll to end problem on some browsers
Add PTT_SETS_INPUT option for IC7600
Add TELRECONFIG command to reread users or whole config
Enforce PACLEN on UZ7HO ports
Fix PACLEN on Command Output
Retry axip resolver if it fails at startup
Fix AGWAPI connect via digis
Fix Select() for Linux in MultiPSK, UZ7HO and V4 drivers
Limit APRS OBJECT length to 80 chars
UZ7HO disconnect incoming call if no free streams
Improve response to REJ (no F) followed by RR (F)
Try to prevent more than MAXFRAME frames outstanding when transmitting
Allow more than one instance of APRS on Linux
Stop APRS digi by originating station
Send driver window trace to main monitor system
Improve handling of IPOLL messages
Fix setting end of address bit on dest call on connects to listening sessions
Set default BBS and CHAT application number and number of streams on LinBPQ
Support #include in bpq32.cfg processing

24 September 2019 Version 6.0.19.1

Fix UZ7HO interlock
Add commands to set Centre Frequency and Modem with UZ7HO Soundmodem (on Windows only)
Add option to save and restore MH lists and SAVEMH command
Add Frequency (if known) to UZ7HO MH lists
Add Gateway option to Telnet for PAT
Try to fix SCS Tracker recovery
Ensure RTS/DTR is down on CAT port if using that line for PTT
Experimental APRS Messaging in Kernel
Add Rigcontrol on remote PC's using WinmorControl
ADD VARAFM and VARAFM96 WL2KREPORT modes
Fix WL2K sysop update for new Winlink API
Fix APRS when using PORTNUM higher than the number of ports
Add Serial Port Type
Add option to linbpq to log APRS-IS messages.
Send WL2K Session Reports
Drop Tunneled Packets from 44.192 - 44.255
Log incoming Telnet Connects
Add IPV4: and IPV6: overrides on AXIP Resolver.
Add SessionTimeLimit to HF sessions (ARDOP, SCSPactor, WINMOR, VARA)
Add RADIO FREQ command to display current frequency

7 January 2019 Version 6.0.18.1

Fix validation of NODES broadcasts
Fix HIDENODES
Check for failure to reread config on axip reconfigure
Fix crash if STOPPORT or STARTPORT used on KISS over TCP port
Send Beacons from BCALL or PORTCALL if configured
Fix possible corruption of last entry in MH display
Ensure RTS/DTR is down when opening PTT Port
Remove RECONFIG command
Preparations for 64 bit version

7 November 2018 Version 6.0.17.1

Change WINMOR Restart after connection to Restart after Failure and add same option to ARDOP and VARA
Add Abort Connection to WINMOR and VARA Interfaces
Reinstate accidentally removed CMS Access logging
Fix MH CLEAR
Fix corruption of NODE table if NODES received from station with null alias
Fix loss of buffer if session closed with something in PARTCMDBUFFER
Fix spurious GUARD ZONE CORRUPT message in IP Code.
Remove "reread bpq32.cfg and reconfigure" menu options
Add support for PTT using CM108 based soundcard interfaces
Datestamp Telnet log files and delete old Telnet and CMSAcces logs

19 March 2018 Version 6.0.16.1

Fix Setting data mode and filter for IC7300 radios
Add VARA to WL2KREPORT
Add trace to SCS Tracker status window and tidy up other status windows
Fix possible hang in IPGATEWAY
Add BeacontoIS parameter to APRSDIGI. Allows you to stop sending beacons to APRS-IS.
Fix sending CTEXT on WINMOR sessions

26 February 2018 Version 6.0.15.1

Partial support for ax.25 V2.2
Add MHU and MHL commands and MH filter option
Fix scan interlock with ARDOP
Add Input source select for IC7300
Remove % transparency from web terminal signon message
Fix L4 Connects In count on stats
Fix crash caused by corrupt CMSInfo.txt
Add Input peaks display to ARDOP status window
Add options to show time in local and distances in KM on APRS Web pages
Add VARA support
Fix WINMOR Busy left set when port Suspended
Add ARDOP-Packet Support
Add Antenna Switching for TS 480
Fix possible crash in Web Terminal
Support different Code Pages on Console sessions
Use new Winlink API interface (api.winlink.org)
Support USB/ACC switching on TS590SG
Fix scanning when ARDOP or WINMOR is used without an Interlocked Pactor port.
Set NODECALL to first Application Callsign if NODE=0 and BBSCALL not set.
Add RIGCONTROL TUNE and POWER commands for some ICOM and Kenwwod rigs
Fix timing out ARDOP PENDING Lock
Support mixed case WINLINK Passwords
Add TUNE and POWER Rigcontol Commands for some radios
ADD LOCALTIME and DISPKM options to APRS Digi/Igate

12 July 2017 Version 6.0.14.1

Fix Socket leak in ARDOP and FLDIGI drivers.
Add option to change CMS Server hostname
ARDOP Changes for 0.8.0+
Discard Terminal Keepalive message (two nulls) in ARDOP command hander
Allow parameters to be passed to ARDOP TNC when starting it
Fix Web update of Beacon params
Retry connects to KISS ports after failure
Add support for ARDOP Serial Interface Native mode.
Fix gating APRS-IS Messages to RF
Fix Beacons when PORTNUM used
Make sure old monitor flag is cleared for TermTCP sessions
Add CI-V antenna control for IC746
Don't allow ARDOP beacons when connected
Add support for ARDOP Serial over I2C
Fix possble crash when using manual RADIO messages
Save out of sequence L2 frames for possible euse after retry
Add KISS command to send KISS control frame to TNC
Stop removing unused digis from packets sent to APRS-IS
Processing of ARDOP PING and PINGACK responses
Handle changed encoding of WL2K update responses.
Allow anonymous logon to telnet
Don't use APPL= for RP Calls in Dragon Single mode.
Add basic messaging page to APRS Web Server
Add debug log option to SCSTracker and TrkMulti Driver
Support REBOOT command on LinBPQ
Allow LISTEN command on all ports that support ax.25 monitoring

27 September 2016 Version 6.0.13.1

Allow /ex to exit UNPROTO mode
Support ARDOP ARQBW commands
Support IC735
Fix sending ARDOP beacons after a busy holdoff
Enable BPQDED driver to beacon via non-ax.25 ports
Fix channel number in UZ7HO monitoring
Add SATGate mode to APRSIS Code
Fix crash caused by overlong user name in telnet logon
Add option to log L4 connects
Add AUTOADDQuiet mode to AXIP
Add EXCLUDE processing
Support WinmorControl in UZ7HO driver and fix starting TNC on Linux
Convert calls in MAP entries to upper case
Support Linux COM Port names for APRS GPS
Fix using NETROM serial protocol on ASYNC Port
Fix setting MYLEVEL by scanner after manual level change
Add DEBUGLOG config param to SCS Pactor Driver to log serial port traffic
Use #myl to set SCS Pactor MYLEVEL, and add checklevel command
Add Multicast RX interface to FLDIGI Driver
Fix processing application aliases to a connect command
Fix Buffer loss if radio connected to PTC rig port but BPQ not configured to use it
Save backups of bpq32.cfg when editing with Web interface and report old and new length
Add DD command to SCS Pactor, and use it for forced disconnect
Add ARDOP mode select to scan config
ARDOP changes for ARDOP V 0.5+
Flip SSID bits on UZ7HO downlink connects
Force L2 connect to call in NODES table if call preceeded with ! (eg C 2 !g8bpq)

2nd November 2015 Version 6.0.12.1

Fix logging of IP addresses for connects to FBBPORT
Allow lower case user and passwords in Telnet "Attach and Connect"
Fix possible hang in KISS over TCP Slave mode
Fix duplicating LinBPQ process if running ARDOP fails
Allow lower case command aliases and increase alias length to 48
Fix saving long IP frames pending ARP resolution
Fix dropping last entry from a RIP44 message.
Fix displaying Digis in MH list
Add port name to Monitor config screen port list
Add KISSOPTIONS TRACKER to allow SCS Tracket to be used in KISS Mode
Fix APRS command call filter and add port filter
Support port names in BPQTermTCP Monitor config
Add FINDBUFFS command to dump lost buffers to Debugview/Syslog
Buffer Web Mgmt Edit Config output
Add WebMail Support
Fix not closing APRS Send WX file.
Add RUN option to APRS Config to start APRS Client
LinBPQ runs FindLostBuffers and exits if QCOUNT < 5
Close ARDOP and restart connection if nothing received for 90 secs
Add option to bridge all packets between ports (not just APRS UI frames)

10th September 2015 Version 6.0.11.1

Fixes for IPGateway configuration and Virtual Circuit Mode
Separate Portmapper from IPGateway
Add PING Command
Add ARDOP Driver
Add basic APPLCALL support for PTC-PRO/Dragon 7800 Packet (using MYALIAS)
Add "VeryOldMode" for KAM Version 5.02
Add KISS over TCP Slave Mode.
Support Pactor and Robust Packet on same port on P4Dragon
Add "Remote Station Quality" to Web ROUTES display
Add AMPRNet (Net44) Tunneling and RIP44 process
Add NAT for local hosts to IPGateway
Fix setting filter from RADIO command for IC7410
Add Memory Channel Scanning for ICOM Radios
Try to reopen Rig Control port if it fails (could be unplugged USB)
Fix restoring position of Monitor Window
Stop Codec on Winmor and ARDOP when an interlocked port is attached (instead of listen false)
Support APRS beacons in RP mode on Dragon
Change Virtual MAC address on IPGateway to include last octet of IP Address
Fix "NOS Fragmentation" in IP over ax.25 Virtual Circuit Mode
Fix sending I frames before L2 session is up
Fix Flow control on Telnet outbound sessions.
Fix reporting of unterminatred comments in config
Add option for RigControl to not change mode on FT100/FT990/FT1000
Add "Attach and Connect" for Telnet ports

14th February 2015 Version 6.0.10.1

Fix crash if corrupt HTML request received.
Allow SSID's of 'R' and 'T' on non-ax.25 ports for WL2K Radio Only network.
Make HTTP server HTTP Version 1.1 complient - use persistent conections and close after 2.5 mins
Add INP3ONLY flag.
Fix program error if UNPROTO command entered without a destination path
Show client IP address on HTTP sessions in Telnet Server
Reduce frequency and number of attempts to connect to routes when Keepalives or INP3 is set
Add FT990 RigControl support, fix FT1000MP support.
Support ARMV5 processors
Changes to support LinBPQ APRS Client
Add IC7410 to supported Soundcard rigs
Add CAT PTT to NMEA type (for ICOM Marine Radios
Fix KISS ACKMODE
Add KISS over TCP
Support ACKMode on VKISS
Improved reporting of configuration file format errors
Experimental driver to support ARQ sessions using UI frames

26th October 2014 Version 6.0.9.1

Fix setting NOKEEPALIVE flag on route created from imcoming L3 message
Ignore NODES from locked route with quality 0
Fix seting source port in AXIP
Fix Dual Stack (IPV4/V6) on Linux.
Fix RELAYSOCK if IPv6 is enabled.
Add support for FT1000
Fix hang when APRS Messaging packet received on RF
Attempt to normalize Node qualies when stations use widely differing Route qualities
Add NODES VIA command to display nodes reachable via a specified neighbour
Fix applying "DisconnectOnClose" setting on HOST API connects (Telnet Server) Fix buffering large messages in Telnet Host API
Fix occasional crash in terminal part line processing
Add "NoFallback" command to Telnet server to disable "fallback to Relay"
Improved support for APPLCALL scanning with Pactor
MAXBUFFS config statement is no longer needed.
Fix USEAPPLCALLS with SCS Tracker when connect to APPLCALL fails
Implement LISTEN and CQ commands
FLDIGI driver can now start FLDIGI on a remote system
Add IGNOREUNLOCKEDROUTES parameter

17th August 2014 Version 6.0.8.1

Use Registry Key HKEY_CURRENT_USER on all OS versions
Fix crash when APRS symbol is a space.
Fixes for FT847 CAT
Fix display of 3rd byte of FRMR
Add "DEFAULT ROBUST" and "FORCE ROBUST" commands to SCSPactor Driver
Fix possible memory corruption in WINMOR driver
Fix FT2000 Modes
Use new WL2K reporting system (Web API Based)
APRS Server now cycles through hosts if DNS returns more than one
BPQ32 can now start and stop FLDIGI
Fix loss of AXIP Resolver when running more than one AXIP port
mplement LISTEN and CQ commands

13th April 2014 Version 6.0.7.1

FLDigi now checks for busy before allowing an outgoing connect

1st April 2014 Version 6.0.6.1

Added FLDigi Interface See here for details.
Fix "All CMS Servers are inaccessible" message so Mail Forwarding ELSE works.
Validate INP3 messages to try to prevent crash
Fix possible crash if an overlarge KISS frame is received
Fix error in AXR command
Add LF to Telnet Outward Connect signin if NEEDLF added to connect line
Add CBELL to TNC2 emulator
Add sent objects and third party messages to APRS Dup Check List
Incorporate UIUtil in BPQ32.dll
Fix TNC State Display for Tracker
Cache CMS Addresses on LinBPQ
Fix count error on DED Driver when handling 256 byte packets
Add basic SNMP interface for MRTG
Fix memory loss from getaddrinfo
Process "BUSY" response from Tracker
Handle serial port writes that don't accept all the data (could cause truncated packets)

4th January 2014 Version 6.0.5.1


Add "Clear" option to MH command
Add "Connect to RMS Relay" Option
Revert to one stop bit on serial ports, explictly set two on FT2000 rig control
Fix routing of first call in Robust Packet
Add Options to switch input source on rigs with build in soundcards (so far only IC7100/7200 and Kenwood 590)
Add RTS>CAT PTT option for Sound Card rigs
Add Clear Nodes Option (NODE DEL ALL)
SCS Pactor can set differeant APPLCALLS when scanning.
Fix possible Scan hangup after a manual requency change with SCS Pactor
Accept Scan entry of W0 to disable WINMOR and P0 to disable Pactor on that frequency
Fix corruption of NETROMCALL by SIMPLE config command
Enforce Pactor Levels
Add Telnet outward connect
Add Experimantal RMS Relay/Trimode Emulation (Not complete yet)
Fix V4 Driver
Add PTT Mux (so more than one sound card mode can use the same radio)
Add Locked ARP Entries (via bpq32.cfg)
Fix IDLETIME node command
Fix STAY param on connect
Add STAY option to Attach and Application Commands
Fix crash on copying a large AXIP MH Window
Fix possible crash when bpq32.exe dies
Fix DIGIPORT for UI frames

6th October 2013 Version 6.0.4.1

Add frequency dependent autoconnect appls for Pactor
Fix DED Monitoring of I and UI with no data
Include AGWPE Emulator (from AGWtoBPQ)
Accept DEL (Hex 7F) as backspace in Telnet
Fix re-running resolver on re-read AXIP config
Speed up processing, mainly for Telnet Sessions
Fix APRS init on restart of bpq32.exe
Change serial port setup to 2 stop bits
Fix scrolling of WINMOR trace window
Fix Crash when ueing DED TNC Emulator
Fix Disconnect when using BPQDED2 Driver with Telnet Sessions
Allow HOST applications even when CMS option is disabled
Fix APRS DIGIMAP command with no targets (didn't suppress default settings)

17th July 2013 Version 6.0.3.1

Add facility to start amd kill a WINMOR TNC on a remote host
Fix Program Error when APRS Item or Object name is same as call of reporting station
Don't digi a frame that we have already digi'ed
Add ChangeSessionIdleTime API
Add WK2KSYSOP Command
Add IDLETIME Command
Fix Errors in RELAYAPPL processing
Add STOPPORT and STARTPORT commands to close/reopen KISS ports so TNC can be reconfigured without closing node
Fix possible crash caused by invalid RIGCONFIG line

The documentation of Node User and SYSOP commands has been updated

6th June 2013 Version 6.0.2.1

Fix operation on Win98
Fix callsign error with AGWtoBPQ
Fix PTT problem with WINMOR
Fix Reread telnet config
Add Secure CMS signon
Fix error in cashing addresses of CMS servers
Fix Port Number when using Send Raw.
Fix PE in KISS driver if invalid subchannel received
Fix Origin address of beacons
Speed up Telnet port monitoring.
Add TNC Emulators. See here for details
Add CountFramesQueuedOnStream API
Add XDIGI feature. See here for details
Add Winmor Robust Mode switching for compatibility with new Winmor TNC
Add APRS packet decode and Web Interface
APRS Digi/Igate can now gate packets from APRS-IS to RF - please use with caution!
Stop corruption caused by overlong KISS frames

22th March 2013 Version 6.0.1.1

Now available for Linux systems (LinBPQ) as well as Windows. See here for more information.

New KISSOPTIONS:
  PITNC
  NOPARAMS  - Don't send Parameters (TXDELAY, SLOTTIME, etc) to TNC;

Optional L2 Alias can be specified on APPLICATION config statement

Add "KISS over UDP" driver.

Add option to bridge APRS frames from one port to another. Mainly to allow uising 3rd party APRS clients with BPQ32 APRS Digi/IGate

Web Interface includes Drivr and Stream Status Windows.

TCP/IP API added - mainly for LinBPQ, but also available on Windows version See here for details.

25th September 2012 Version 5.2.9.1

Fix possible crash when using KISS ports with COMn > 16

8nd August 2012 Version 5.2.8.1

Fix handling TelnetServer packets over 500 bytes in normal mode
Fix Igate handling packets from UIView
Prototype Baycom driver (not yet fully functional)
Set WK2K group ref to MARS (3) if using a MARS service code
Various bug fixes to reduce random crashes/hangs
Add TNCX KISSOPTION for TNC-X BPQKISS software (includes the ACKMODE bytes in the checksum)

2nd June 2012 Version 5.2.7.1

Fix opening more thn one console window on Win98
Change method of configuring multiple timelots on WL2K reporting (use : to separate)
Add option to update the WK2K Sysop Database
Add Web server
Add UIONLY port option

2nd April 2012 Version 5.2.6.1

Convert to MDI (Multiple Docment Interface) presentation of BPQ32.dll windows. See here for details
Add option to send APRS Objects and Items
Send APRS Status packets
Send QUIT not EXIT in SCS PTC Initialisation sequence
Implement new WL2K reporting format and include traffic reporting info in CMS signon
New formet for WL2KREPORT Configuration Statement. See here for details
Prevent loops when APPL alias refers to itself
Add RigControl for Flex and ICOM IC-M710 Marine radios

17th February 2012 Version 5.2.5.1

Don't look for Password file. Password is now specified in BPQ32.cfg
Add extra MultiPSK commands for control of ALE Beacons and Mode changes
Fix MultiPSK Transparency. MultiPSK can now be used for binary transfers
Make LOCATOR command compulsory
Add MobileBeaconInterval APRS param
Send Course and Speed when APRS is using GPS
Fix Robust Packet reporting in PTC driver when some channels are Pactor only
Fix corruption of some MIC-E packets by APRS code

29th January 2012 Version 5.2.4.1

Remove CR from Telnet User and Password Prompts
Add Rigcontrol to UZ7HO driver
Fix corruption of Free Buffer Count by Rigcontol
Fix WINMOR and V4 PTT
Add MultiPSK Driver (for ALE400 and 141A modes)
Remove need for MAP DUMMY in AXIP config (for Chat Map)
Fix check on length of Port Config ID String with trailing spaces
Fix interlock when Port Number is not equal to the port position in config filet
Add optional NETROMCALL for L3 Activity
Fix Telnet you dont have a TCPPORT and use FBBPORT
Add Reread APRS Config command to BPQ32 Console
Fix switching to Pactor after scanning in normal packet mode (SCSPTC Driver)
Add Support for BPQAPRS - an APRS Mapping and Messaging Application
Add IPV6 support to APRS IGate

4th January 2012 Version 5.2.3.1

If you use RigControl, please read this, before installing this version, as the configuration format has changed.

If you are currently running a version below 5.2.1.3, please read warming at the start of the 5.2.1.3 Changelog.

Rewrite RigControl and add "Reread RigControl Config"
Connects from the console to an APPLCALL or APPLALIAS now invoke any Command Alias that has been defined.
Fix reporting of Tracker freqs to WL2K.
Fix Tracker monitoring setup (sending M UISC)
Fix possible call/application routing error on RP
Changes for P4Dragon
Supports User Mode VCOM Driver for VKISS Ports
Include APRS Digi/IGate
Tracker monitoring now includes DIGIS
Include driver for UZ7HO soundcard modem.
Support sending UI frames using SCSTRACKER, SCTRKMULTI and UZ7HO drivers
Accept DRIVER as an alternative to DLLNAME, and COMPORT as an alternative to IOADDR in bpq32.cfg. COMPORT is decimal
No longer supports separate config files, or BPQTELNETSERVER.exe
Improved flow control for Telnet CMS Sessions
Fix handling Config file without a newline after last line
Add non - Promiscuous mode option for BPQETHER
Change Console Window to a Dialog Box.
Fix possible corruption and loss of buffers in Tracker drivers
Add "Beacon After Session" option to Tracker and UZ7HO Drivers
Add option to add comments to the NodeMap

17th October 2011 Version 5.2.1.3

WARNING!!!! If you use VISTA or WIN7, the first time you run this version, your registry configuration for all BPQ32 programs will be moved from HKEY_LOCAL_MACHINE to HKEY_CURRENT_USER.
This is necessary as I've found that Vista/WIN7 stores HKEY_LOCAL_MACHINE in an obscure place unless you are running as administrator. This messes up the Registry Save/Restore process.

Add caching of CMS Server IP addresses. This enables CMS Telnet to function during a DNS outage.
Initialise TNC State on Pactor Dialogs. The TNC State wasn't always shown correctly.
Add Shortened (6 digit) AUTH mode. Supports BPQAuth, a new method for BBS SYSOP Authentication over radio links.
Update MH with all frames (not just I/UI). MH didn't used to update on connect requrests, etc.
Add IPV6 Support for TelnetServer and AXIP.
Fix TNC OK Test for Tracker. You could sometimes attach a Tracker port, even if the link to TNC was down.
Fix crash in CMS mode if terminal disconnects while tcp connect in progress.
Add WL2K reporting for Robust Packet.
Add option to suppress WL2K reporting for specific frequencies.
Fix Timeband processing for Rig Control. Having more that two timebands didn't always work properly.
New Driver for SCS Tracker allowing multiple connects, so Tracker can be used for user access. See SCSTrackerMulti.
Experimental Driver for V4 TNC. V4 is a narrowband soundcard mode from the author of WINMOR.
Combine busy detector on Interlocked Ports (SCS PTC, WINMOR or KAM)
Improved program error logging
WL2K reporting format changed. This should allow BPQ32 stations to appear on the Winlink HF Status page

11th April 2011 Version 5.0.0.1

Add "Close all programs" command
Add BPQ Program Directory registry key, so software and config can be placed in different directories
Time out IP Gateway ARP entries, and only reload ax.25 ARP entries from BPQARP.DAT
Add support for SCS Tracker HF Modes
Fix WL2K Reporting for Packet Sessions
Report software version to WL2K when using Telnet CMS Mode

14th February 2011 Version 4.10.16.15

Add support for BPQTermTCP, a new program for remote accesss to a BPQ32 Node over the Internet
Allow TelnetServer to listen on more that one port in FBB Mode.
Allow Telnet FBB mode sessions to send CRLF as well as CR on user and pass msgs, simplifiying use with WinPack
Add session length to CMS Telnet logging.
Show uptime in Days/Hours/Minutes instead of minutes

20th January 2011 Version 4.10.16.13

Fix loss of buffers in TelnetServer causing Node to hang.
Add logging of CMS Telnet sessions.
Add non - Promiscuous mode option for BPQETHER, for use with cards that don't support Promiscuous mode
Add option for Hardware PTT to use a different com port from the scan port
Add CAT PTT for Yaesu 897
Fix RMS Packet ports reporting busy after restart or reconfiguration of RMS Packet
Fix CMS Telnet with MAXSESSIONS > 10

5th January 2011 Version 4.10.16.11

Fix MH Update for SCS Outgoing Calls
Allow BPQ32 to access the WL2K CMS Servers via TelnetServer (Instead of via RMS Packet)
Fix occasional Program Error when a Pactor or Winmor session disconnects with data outstanding.

20th December 2010 Version 4.10.16.10

Fix freq display for FT100 (was KHz, not MHz)
Allow Map reporting position to be set using Lat/Lon as well as Locator. See here for details.
Fix Telnet Log Name
Fix starting with Minimized windows when Minimizetotray isn't set
Support SCS Robust Packet Mode on some SCS PTC Controllers. See here for details. Robust Packet support is still experimental.
Add support for FT2000 to Rigcontrol
Only Send CTEXT to connects to Node (not to connects to an Application Call)

16th November 2010 Version 4.10.16.8

Include support for HAL Clover/Pactor Modems
Changes to Pactor Drivers disconnect code
AXIP now sends with source port = dest port, unless overridden by SOURCEPORT param. See here for details.
Config now checks for duplicate port definitions
Add Node Map reporting
Fix WINMOR deferred disconnect.
Write Telnet log to BPQ Directory
Add Port to AXIP resolver display
Add support for FT100 to Rigcontrol
Add "Save Registry Config" command to "Actions" menu
The AEA PK232 Pactor driver is no longer considered experimental.

14th October 2010 Version 4.10.16.5

Fix problem with loading on Win98/ME systems.
Fix problem wirh re-reading AXIP Resolver config.
Support more than one AXIP Port
Move TelnetServer into bpq32.dll. See here for details.
Report AXIP accept() fails to syslog, not a popup.
AEA Pactor driver is included in bpq32.dll, but this driver is still considered experimental.

7th October 2010 Version 4.10.16.3

Rigcontrol has been rewritten, with new options, such as setting Winmor/Pactor session bandwidth, ICOM Repeater Shift and Data Mode and Antenna Switching. Configuration is now in the driver config, and there is no separate RigControl window - the info appears in the Pactor/Winmor windows. See the RigControl documentation for details

Most drivers previously provided as .dll files are now built in to bpq32.dll. However, you still configure them the same - TYPE=EXTERNAL DLLNAME=xxxxx.dll.

Extend INFOMSG to 2000 bytes
Improve Scan freq change lock (check both SCS and WINMOR Ports)
Add option to reread IP Gateway config.
Fix extra entries being left in window list after reinitialisation.
If you are using WINMOR, you can now get bpq32 to start the TNC, and close it when BPQ32 exits. See the WINMOR documentation for details.

The WINMOR and Pactor drivers now include most configuration commands, Only site-specific customisation is needed in the config files. See the documentation for each driver for details.

You can now included all driver configuration information in bpq32.cfg. Just before the ENDPORT add CONFIG, then the config statements from your driver.cfg file, eg:

PORT
ID=AXIP Link
TYPE=EXTERNAL
DLLNAME=BPQAXIP.DLL
QUALITY=200
MAXFRAME=4
FRACK=5000
RESPTIME=1000
RETRIES=10
PACLEN=236
MINQUAL=150
UNPROTO=FBB ; DEFAULT UNPROTO ADDR
BCALL=GM8BPQ ; Call for Beacons

CONFIG

BROADCAST NODES
MHEARD ON

UDP 10093 ;Listens for UDP packets on this port number

AUTOADDMAP
MAP GM8BPQ 192.168.0.101 UDP 10093 B
MAP DUMMY bpqchatmon.ham-radio-op.net UDP 10090 B

ENDPORT

You can still have separate config files, but I recommend converting to the new format.
The configuration for the WINMOR and Pactor drivers is a bit different when the config in bpq32.cfg - see the documentation for each driver for details.

16th August 2010 Version 4.10.15.4

New Configuration file documentation here.
Read bpq32.cfg (or bpqcfg.txt) instead of bpqcfg.bin
Support 32 bit MMASK (Allowing 32 Ports)
Support 32 bit APPLMASK (Allowing 32 Applications)
Allow longer Application command aliases (up to 32 bytes)
Fix logic error in RIGControl Port Initialisation (wasn't always raising RTS and DTR)
Clear RIGControl RTS and DTR on close
Fix Kenwood Rig Control when more than one message received at once.
Save minimzed state of Rigcontrol Window
Fix reporting of set errors in scan to a random session
Now returns "Sorry, Application XXX is not running - Please try later" instead of "Sorry, All XXX Ports are in use - Please try later" if Application isn't running.

2nd June 2010 Version 4.10.14.3

Add option to prevent node trying to keep link to a neighbours open.

6th April 2010 Version 4.10.14.2

No longer flips SSID bits on Downlink Connect if uplink is Pactor/WINMOR
Fix resetting IDLE Timer on Pactor/WINMOR sessions. This was preventing transfers lasting more than 15 minutes
Add KISS OPTION "D700" which removes risk of accidentally taking D700/D710 radios out of KISS Mode

20th March 2010 Version 4.10.14.1

Rig Control is now build in to bpq32.dll. Rigcontrol.dll is no longer used.
Adds control of Kenwood Rigs
Adds option to combine Attach and Call commands for Pactor and WINMOR

Источник: [https://torrent-igruha.org/3551-portal.html]
.

What’s New in the Agw Tracker serial key or number?

Screen Shot

System Requirements for Agw Tracker serial key or number

Add a Comment

Your email address will not be published. Required fields are marked *