CN1364389A - Multiple tree hierarchical communication system and method - Google Patents

Multiple tree hierarchical communication system and method Download PDF

Info

Publication number
CN1364389A
CN1364389A CN01800447A CN01800447A CN1364389A CN 1364389 A CN1364389 A CN 1364389A CN 01800447 A CN01800447 A CN 01800447A CN 01800447 A CN01800447 A CN 01800447A CN 1364389 A CN1364389 A CN 1364389A
Authority
CN
China
Prior art keywords
node
registration
message
local
address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN01800447A
Other languages
Chinese (zh)
Inventor
王众和
阿尔蒙 唐大链
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.)
Motorola Solutions Inc
Original Assignee
Motorola Inc
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
Application filed by Motorola Inc filed Critical Motorola Inc
Publication of CN1364389A publication Critical patent/CN1364389A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing 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/08Mobility data transfer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • H04W12/062Pre-authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing 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/08Mobility data transfer
    • H04W8/085Mobility data transfer involving hierarchical organized mobility servers, e.g. hierarchical mobile IP [HMIP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04Network layer protocols, e.g. mobile IP [Internet Protocol]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

A method and system for improving the registration process in a communication system, preferably an all IP communication system, wherein a set of Location Registration (LR) nodes are designed to handle mobile registration locally. When the mobile node registers with the home network from a foreign network, a Location Registration chain is established through these nodes. The information needed for the mobile node to access the network is distributed to these nodes from the home network. When the mobile node roams into a different visiting network or returns to its home network, the nearby location registration nodes then process the mobile registration and update the location chain accordingly.

Description

Multiple tree hierarchical communication system and method
Technical field
The present invention relates generally to a kind of communication system, particularly relate to a kind of improving one's methods and system of registration process in the all-IP communication system of improving.
Technical background
Universal personal communication system is a kind of system that anyone can be communicated with the world any other people Anywhere.One of problem of a kind of like this system may be to locate millions of mobile subscribers with effective means.Location mobile subscriber's prior art is to use central database to carry out paging and registration in system.Consider a large number of users in the global system, if do not know user's position, then first The Application of Technology is unpractical.The register technique that recording user moves in central database also is unpractical.
Global roaming is the design object of the next generation or the third generation (3G) cellular network.In order effectively to support the real-time application of mobile subscriber in these networks, signaling and Payload traffic delay must minimize.It has been recognized that one of root that causes long delay is the triangle Route Selection.Just, for example, in registration process, when mobile node starts a calling or when mobile node roams into the different access network, must always ask that registration send to local network from the external agent of visited network.In addition, in call setup was handled, the triangle Route Selection was considered to cause the root of long delay.
In the mobile IP network of stipulating in RFC2002, local agent plays the effect of concentrated position registration and termination point of a tunnel, is that all groupings of a mobile node appointment must be routed to its local agent like this, encapsulates and be sent to corresponding external agent then.This situation is commonly referred to as triangle Route Selection or long line loop (tromboning), and this situation can not make Internet resources effectively be used, and is one of major obstacle of IP network support application in real time.
Regional tunnel management is introduced IP network with layering external agent structure, to eliminate the triangle Route Selection of registration signaling.Yet, when regional tunnel management is used for the 3G cellular network, can have some problems.These problems comprise: the inhomogeneity system configuration in this locality and the external domain; Call out the triangle Route Selection in connecting; Can not support individual's (comparing) mobility with device; Undefined mobile management separate registration process; And a large amount of participations that in registration process, need mobile node.
General mobile IP (UMIP) technology of suggestion is used for the next generation (3G) cellular network.Its objective is to a plurality of heterogeneous radio access networks real-time and that non real-time is used provide and have the comprehensive mobility service that the whole world covers.The technology of being advised joins some features in the mobile IP standard of stipulating among the RFC2002, and moves the back compatible of IP standard with this, and this is a kind of special circumstances of NMIP.Regional tunnel management also is a kind of special circumstances of UMIP.
So, needing a kind of like this method and system, they can reduce call setup and required time of Payload Route Selection.The objective of the invention is by the access domain of mobile radio station and the distributed hierarchy in the local domain, eliminate the triangle Route Selection in signaling and the Payload business,
Brief description of drawings
Subsidiary claim has illustrated of the present inventionly believe it is the feature of novel features.Yet, the present invention itself and best use pattern, other purpose and advantage, by with reference to following in conjunction with the accompanying drawings to the detailed description of illustrative embodiment, will be understood best, wherein:
Fig. 1 shows the 3G wireless network architecture of the simplification of the inventive method and system;
Fig. 2 shows a communication system of the inventive method and system, has shown the hierarchical system structure of four layers with location register;
Fig. 3 shows the location register table of storage mobile node locating information;
Fig. 4 shows an example of locate chain in the hierarchy of the inventive method and system;
Fig. 5 shows the functional flow diagram that the location register of having described layer>1 receives a registration processing of request;
Fig. 6 and Fig. 7 show and describe the functional flow diagram that a location register generates the processing of a registration answer;
Fig. 8 shows the functional flow diagram that the location register of describing layer>1 receives the processing of a registration answer;
Fig. 9 shows and describes the functional flow diagram that a mobile node generates a registration processing of request;
Figure 10 shows and describes the functional flow diagram that a mobile node receives the processing of a registration answer;
Figure 11 shows and describes the functional flow diagram that mobile node generates the processing of a life-span update request;
Figure 12 shows and describes the functional flow diagram that mobile node receives the processing of a life-span renewal answer;
Figure 13 shows and describes the functional flow diagram that location register (1) receives a registration processing of request;
Figure 14 shows the functional flow diagram that the location register of describing layer=1 receives the processing of a registration answer;
Figure 15 shows the location register of describing layer=1 and receives a functional flow diagram that compiles the processing of renewal;
Figure 16 shows the location register of describing layer=1 and receives a functional flow diagram of separating the processing of registration;
Figure 17 shows the functional flow diagram that the location register of describing layer=1 receives the processing of a life-span update request;
Figure 18 shows the functional flow diagram that the location register of describing layer=1 receives the processing of a life-span renewal answer;
Figure 19 shows the location register of describing layer>1 and receives a functional flow diagram of separating the processing of registration message;
Figure 20 shows the location register of describing layer>1 and receives a functional flow diagram that compiles the processing of renewal; With
Figure 21 shows the functional flow diagram that the location register of describing layer>1 receives the processing of a life-span update request;
Detailed description of the present invention
For convenience's sake, will use initialism with full text with reference to the accompanying drawings.Be the tabulation of employed initialism below.
Bluetooth Bluetooth is a kind of code name of technical specification, is used for little formation factor, low cost, short-distance wireless electrical links between mobile PC, mobile phone and other portable unit.The industrial group that the bluetooth specific service groups is made up of the leader in telecommunications and the computer industry, this industrial group will promote the development of this technology and with its substitution market.
B Bit Take, busy
BRAN Wideband radio access network
BTS The base station transceiver station
CN Core IP network
Current I D The ID (NAI) of the LR that mobile node has successfully been registered
DECT The digital europe cordless telephone
DNS Name server
F Bit The external agent
FA The external agent
FD External domain.Be that mobile node is subscribed the overlay area outside the local domain of network service.
H Bit Local agent
HA Local agent
Local ident Subscribe the ID (NAL) of mobile node of the local LR appointment of network service by MN
Local network MN subscribes the overlay area of the local LR of network service
HD Local domain.The whole zone that top layer LR is covered, described LR comprises the local subtree of mobile node reservation network service.
IR The intelligence Route Selection
IrDA Infrared Data Association
Locate chain The sequence of the positioning pointer on the LR that forms the Route Selection path between the current LR of MN and its local LR
Positioning pointer It is the IP address that a mobile subscriber transmits the LR of departures grouping
??LR Location registers or location register, the network entity in the IP network of a processing mobile management
??MIN The mobile node identification number
??MN Mobile node
??NAI Network access identifier
??NE The network entity that comprises LR, RNN
New ID That mobile subscriber finds recently and send the ID (NAI) of the LR of general register request message to it
??PDSN Packet data serving node
??RAN Radio access network
??RNN The radio network node that voice/data is used
??RNS The radio net subsystem
??RT The tunnel, zone
??UMIP General mobile IP
??VHF Empty home environment
??AA: The mobile IP agent advertisement information
??Authen: Checking
??Cch(i): When the current and local address (NAL) of MN when layer i is identical with its upper strata, be genuine
??Ccn *(i): When layer i processing node is during in current branch, be genuine
??Chn *(i): When layer i processing node is during in local branch, be genuine
??Cnc(i): When new and current address (NAI) of MN when layer i is identical with its upper strata, be genuine
??Cnh(i): When the new and local address (NAI) of MN when layer i is identical with its upper strata, be genuine
??Cnn *(i): When layer i processing node is during in new branch, be genuine
??CRN: The current root node, the root node of the tree of registration MN
????DR: Separate registration
????FL: The transmission link address that carries in the message
????FRN: Outside root node is not the root node of the tree of MN this locality
????FWD: Transmit the state of indication MN project
????HB: Local branch is connected to the local LR of MN the branch of HRN always
????HRN: The local root node, the root node of the tree of MN booking service
????I: The LR node of UMIP layering top
????i: The layer of indication LR node, [1, I]
????LRh(i): Layer i location register in the local branch
????LRn(i): Layer i location register in the new branch
????LT: Life-span
????LTR: The life-span update request
????n * The node of processing messages
????NACK: Negative response
????NRN: New root node
????PTR: Be indicated to the pointer of next LR in the chain of MN
????Rch: Index identifies the layer that current branch separates with new branch, [0, I]
????Rnc: Index, the layer that the new branch of mark separates with current branch, [0, I]
????Rnh: Index identifies the layer that new branch separates with local branch, [0, I]
????RN: Root node
????RR: The registration request
????RR?FL: The FL that carries in the register request message
????TA: The destination address of the message that sends
Fig. 1 shows the 3G wireless network architecture of simplification.The network segment that two separation are arranged in this structure as shown in the figure.First section is the radio access network (RAN) that comprises radio network node (RNN), is associated with the area of coverage such as region, paging zone or route district.Second section of system is core network (CN), provides a comprehensive mobility solution (for one of other function) to potential foreign peoples RAN.
Fig. 2 shows the have location register UMIP system configuration of four layers of (LR).RNN is that minimum layer LR be (that is, L1LR) in this structure.In a preferred embodiment, the LR in unique N AI or this hierarchy of IP address designation.Different wireless systems that they can be arranged with the network entity RNN equivalence.For example, radio net subsystem (RNS) is an equivalent entity in the GPRS network.RNN uses responsible to speech and/or data.Each RNN is identified by single location ID, and is shared by a plurality of base station transceivers station (BTS) under its control.Supposing that RNN has with the link layer of mobile node (MN) is connected (for example, Common Control Channel or equivalent).
All radio are inserted RAN and little mobile management (if any) item is responsible for.Core net (CN) can be supported multiple radio access technologies, such as WCDMA, CDMA2000, GSM, IS-95, DECT, BRAN (wideband radio access network), BLUETOOTH, IrDA and other WeiLai Technology.For example, perhaps CDMA user is ready by dialling the direct and GSM phone user conversation of called party's id number simply.The solution of being advised can and be carried out suitably continuing to the called party by distributed LR database-located called party.As the byproduct of UMIP, Network-Network interface (NNI) is descended to shift onto the CN that make mobile management and is re-used and the maximized RAN-CN of system synthesis.Be used for being noted as " M interface " at Fig. 2 such as the RAN-CN interface of the management function of mobile management.No matter what technology RAN has been implemented, in most preferred embodiment, the RAN-CN interface must be based on IP.
Mobile management is implemented in LR (location register).Be used for the registration request of local agent except serving as the external agent and answering, LR also keeps and upgrades portability database.LR presses sandwich construction (in Fig. 2, maximum layer i equals 4) and arranges.Layer index is assigned in proper order with the increase from top to bottom of structure.The number of plies in the different subtrees (territory) needn't be identical.Each LR can have zero or a plurality of sub-LR in next lower level.Each LR can have zero (being called root LR) or the female LR in centre.Suppose that all root LR can intercom mutually, to form the locate chain of crossing over a plurality of territories.Each LR is associated with a logic overlay area.Total overlay area of lower level LR must be the suitable subclass of the overlay area of its female LR.In other words, the logical boundary of higher level LR needn't pass any border of its subsystem LR.
The behavior of each LR can be different, and the residing layer of LR is depended in its behavior.Have only those LR that have the wave point of MN just their existence need be announced to MN.Need to prove that the LR on given layer can have sub-LR and interface to RAN of facing.Root LR in hierarchy can dock the root node in another separation structure.
Except their IP address, all functional entitys (that is, LR, RNN and MN) are by their global unique identification symbol sign.In a preferred embodiment, NAI (network access identifier) is used as the global unique identification symbol.Yet those skilled in the art will be appreciated that the global unique identification symbol that also can use other, and this measure does not deviate from the spirit and scope of the present invention.
In a preferred embodiment, in order to have an efficient system solution, following rule is followed in the appointment of NAI: the mobile subscriber is identified by his or her NAI.A chance of supporting personal mobility among the UMIP so just is provided.The NAI of bottom LR, rather than IP address are used as current, the new or local position identifier of mobile node.The NAL of LR should specify in such a way: by comparing mobile subscriber's current, new or local identifier, the LR on any layer can make the Route Selection decision.
The complete description of NAI appointment has exceeded scope of the present invention.Yet a method of enforcement is to be that higher layer entities specifies short NAI, and to make specified NAI be suffix to the NAI of the fructification appointment of its lower level.For example, layer 1 LR can have the NAI such as " 123.Arlington Heights.Chicago.IL US@abc ".Layer 2 LR can have the NAI such as " Arlington Heights.Chicago.IL US@abc ".Layer 3 LR can have the NAI such as " Chicago.IL US@abc ".Layer 4 LR can have the NAI such as " IL US@abc ".At last, a mobile subscriber who registers with layer 1 LR can have the NAI such as " 4567.123.Arlington Heights.Chicago.IL US (@abc ".Need to prove, can be a kind of like this flexi mode definition NAI of an effective NAI with an all figure numbering (such as a telephone number).In addition, all existing IP, IMSI and MIN addressing schemes can be treated to effective NAI.In addition, consider that for scalability the NAI that comprises LR and mobile subscriber's all-network entity can be appointment again.The solution of being advised can also work in the mobile subscriber of the NAI with permanent appointment.Yet, recommend to use the NAI of appointment again.Efficient when specifying NAI is the problem of executive mode.UMIP supports preassignment and specifies NAI again.
Referring to Fig. 3, in each LR, a store M N locating information and the LR table that is used for Route Selection are arranged.In a preferred embodiment, under following condition, have a project of setting up and keeping in mobile subscriber's LR table: described condition is outside the local network of mobile subscriber in its registration and LR is on locate chain.Locate chain originates in the bottom LR of the mobile subscriber in its local domain, and ends at the bottom LR of its visited network.In a preferred embodiment, when not finding project in the LR table, suppose that mobile node is in its local network.
As shown in Figure 3, in a preferred embodiment, have five entities at least in the LR table.They are key word index, pointer, pointer state, life-span and playback protection, its each as described below.First hurdle of LR table is a key word index, and it is mobile subscriber's local NAI.It is used by LR, and mobile message is handled registration and positioned update is connected with calling to seek.In the solution of suggestion, a mechanism must be arranged, so as from a mobile subscriber's sign (NAI) but be mapped to the IP address of a Route Selection.This mapping function is carried out on LR.Second hurdle is mobile subscriber's a positioning pointer.Mobile subscriber's positioning pointer is that this LR will transmit the IP address of a LR of mobile subscriber's departures grouping to it.Third column is the state of mobile subscriber's positioning pointer.Preferably have three class states at least.They are state co-pending, effective status and delivery status.Receive a positive reply (affirmation) before after LR receives a general registration request that is started by the mobile subscriber and at LR, mobile subscriber's project is noted as " co-pending ".After one related with the mobile subscriber sure general registration answer had been received, LR was labeled as " effectively " with a project.Certifiedly have the separating after the registration message of transfer address receiving one between the expiration of life-span of association, LR is labeled as " transmission " with a project.
The 4th hurdle of LR table is the life-span.All three class pointer state in this LR table must be associated with the life-span (a few time in second).It should be quite little being assigned to a life-span with project of " transmission " state, to prevent accumulating bulk items in the LR table.UMIP must carry out the life-span and upgrade, and expands the life-span of the sink information of MN with request.Life-span upgrades and can be sent by any LR on the locate chain of MN or be sent by its local LR and MN.In order before the life-span expiration, to support the life-span to upgrade, must on the path of the local network that leads to the mobile subscriber, guide the life-span update request that generates by MN.LR should not make any decision according to expiration information.The style of resetting and protecting during the 5th hurdle is to use.If a general registration request that is received contains a playback protection expansion that requires the unsupported playback protection of LR style; then LR must reject this general registration request, and sends a general registration answer with the code field that is set to UNSUPPORTED_REPLAY_PROTECTION.
Since MN can be on its local network with the general registration of conventional registration executed in parallel, so MN must be kept for playback protection mechanism and the sequence of LR, and the separating mechanism and the sequence that are used for HA.When using current playback to protect, use the identification field in general registration request/message playback.The sender of message is required that high-order 32 bits of identification field are set to the present value of using by LR in sending to the next general registration request/answer message of this LR node.Low order 32 bits in the identification field are required to be set to be used for the present value of this message.
Thereby in each message, LR notification target LR next time is with the present value of using.If in network, do not lose message, then LR and target LR can keep about now of just using synchronously.Yet, if receiving, target LR thinks a wrong current message, can use general registration request and LR synchronous again.
For example, as shown in Figure 4, if the current location of MN is LR2122, may exist one from LR 1121 (local network) to LR112, arrive LR11, LR1, LR2, LR21, LR212 then, arrive the locate chain that LR2122 sets up at last.
Layer i LR must be kept for following at least three class mobile subscribers' locating information.(1) visitor: be a mobile subscriber, he registers (that is, booking service) outside the area of coverage of LR, and roams into the area of coverage of described LR.(2) local ramber is a mobile subscriber, and he registers in the area of coverage of LR, but is currently located at a different layers i-1 area of coverage, rather than is positioned at the area of coverage of being registered.(3) local traveller: be a mobile subscriber, it is registered in the area of coverage, and roams into outside the area of coverage of described layer i LR.For example, as shown in Figure 4, suppose that a mobile subscriber subscribes its service to LR1121.If he registers to LR1122, he is a LR2122 so, LR212, the visitor of LR21 and LR2.If he registers to LR1111, he is the local ramber of a LR11 so.If he is to any LR registration with the root except LR1, he is a LR1121 so, LR112, the local traveller of LR11 and LR1.As long as the mobile subscriber rests in the local area of coverage of its layer i-1, the layer i LR that is used for this mobile subscriber does not just need locating information.Consider mobile subscriber's localized mobility behavior, thereby greatly reduced memory span, search delay, and the complexity of LR and cost.
In order to support foreign peoples RAN technology in institute's suggested solution, agent advertisement must be implemented on a plurality of layers of hierarchy.For example, a honeycomb Route Selection zone can be associated with layer 1 network entity, and a satellite cell can be associated with layer 2 LR, etc.Layer i (for example, i=1) must announce its existence to using J (for example, honeycomb) mobile subscriber by agent advertisement message, and the minimum area of coverage of wherein using J is associated with the layer i area of coverage by network entity.Preferably, " RT " mark is arranged in agent advertisement message, to distinguish whether support area tunnel management of local system.If use the IP agreement, then this mark is inserted in the reserved field through air interface.
Another mark is to indicate " IR " that whether supports intelligent Route Selection.If by this system implementation,, in agent advertisement message, must regularly comprise whole world inquiry for security consideration.Layer i LR IP address (Care-of Address) and its NAI advertisement in agent advertisement message.If use IP through air interface, then LR NAI extension name must appear in the agent advertisement message after the pre-determined advertisement extension name.
In agent advertisement message, have a plurality of Care-of Address and NAI.First Care-of Address and NAI are used for layer address of i LR and a NAI.Bottom LR must send agent advertisement continuously, makes and will know that to any mobile node of this bottom LR registration they do not shift out this regional scope and network entity is not failed.By " B " bit in its agent advertisement is set, network entity can be indicated its " too busy " so that do not allowed new mobile node to register to it.If " F " bit is not set in agent advertisement message, " B " bit then should be set, but in " F " bit and " H " bit at least one must be set in any agent advertisement message that sends.
The advertising network entity must comprise its NAI in agent advertisement message, to support UMIP.If like this, then network entity NAI extension name must appear in the pre-determined advertisement extension name agent advertisement message afterwards.By the territory part of the NAI of network entity and the territory part of its NAI are compared, mobile node can be determined that it is in its local domain or is in the accessed territory and determines whether and change the territory after its last registration.
As long as on the layer i on the bottom of related application and upper strata LR, receive effective general registration message, just can be added to the additional extension name on this message.They are, but do not comprise the new address (NAI) that increases on the bottoms of using.Consider that for intelligent Route Selection the LR extension name of layering (layer i (on the bottom of application) LR NAI and its IP address) also can be added in this message.
The layer i LR NAL (serving as current I D) of the original stored of the MN when powering up must be its MN NAI.MN can register a Care-of Address or any other local index that is adopted by the RAN relevant with LR.Be noted that perhaps the layer i LR that finds recently is its local LR (HA).
A plurality of addresses can be assigned to a mobile subscriber, its each address is used for a different application.Extension name is defined in and is mounted with effect in the general register request message of combination and uses the address.By receiving the multiaddress extension name from general registration request, LR is with the part storage of this information as the mobile subscriber profile related with mobile node.This message should access from the LR table of LR.
RAN can implement any MN moving body detection by the employing of RAN system.A preferred MN moving body detection is described as follows.In UMIP, MN does not need the knowledge of core network architecture, does not therefore need this category information regularly to send on the qualification frequency range of wireless channel.From the viewpoint of registration, it is whole that MN paid close attention to is the NAI that monitor with the Common Control Channel of the bottom LR of an association.Move to detect use the NAI of LR, if use IP, then on public/Dedicated Control Channel or acting on behalf of the NAI that sends this LR in the broadcast through air interface.MN should lock onto the LR that is identified, and (details of LR identification process has exceeded scope of the present invention), and according to the tracking of all advertisements maintenances that received to LR NAI extension name.If the NAI that is received will change, then mobile node must think (supposition) it moved.For example, suppose that the MN of the application J that is used for a mobile subscriber receives the agent advertisement of the layer i (lowermost layer of application J) from LR, and find that it is positioned at the new layer i LR area of coverage (paging zone, Route Selection district and zone etc.).If it supports general registration the agent advertisement indication, then MN must start registration process by a general registration request being sent to the layer i LR that finds recently.In order to support user rs authentication, must comprise that the answer to whole world inquiry is used as the part of general register request message with whole world inquiry.
In case receive the general registration request that is verified, LR must register the IP address of the network entity that sends general registration request.Relevant information also must be stored and index with mobile subscriber's NAL.This comprises mobile subscriber's NAI, state and life-span.State is marked " co-pending ".If LR does not have authorization information, then in order to verify, it is forwarded to next LR on the path of the local network of MN with general registration request, and may finally arrive local LR.If general registration request comprises all security information, then LR will verify this request.After good authentication, this state will be marked " effectively ".Can also generate the registration answer message, and send this message along locate chain towards mobile node.The registration answer message can also comprise out of Memory, such as user profiles (to support VHE) and security information (to support mobile subscriber's checking), and charging information.
In case receive the registration answer message, LR need check this message, and checks whether there has been a project " co-pending ".If this registration request of this answer indication is accepted, the state of mobile subscriber's project will be marked " effectively ".Then, LR can be sent to next LR along the path towards MN with answer message.
Registering more on the new route, each LR, rather than bottom LR can be added to layering LR extension name on the registration message.This information can be used for downstream LR (consistent with position renewal chain) and upgrade their LR table.It can also be used to making the Route Selection optimization.Can in the general registration request of core net, present one or more layering LR extension name.When LR is added to a registration request when going up with these extension name, the IP address of the LR by will receiving general registration request receives the registration record co-pending that LR foundation is used for the mobile subscriber as mobile subscriber's positioning pointer.In addition, a new extension name is established, and must add this extension name in the ending of all extension name that comprised by upstream LR, with the part as registration message.If do not implement multi-segment LR extension name, then receiving LR will replace this layering LR extension name with an extension name of its information of loading.
With only on its more new route that makes progress (from layer i to i+1) increase layering LR extension name.If multi-segment LR extension name is implemented, then should after the extension name of lower level, add the extension name of higher level.Layering LR extension name can be defined as: by E.Gustafsson, A.Jonsson and C.Perkins are described in detail in mobile IP regional tunnel management, following modification in addition.Generally speaking, the LR network must be able to set up be used for any they the locate chain of the mobile subscriber outside the network of registering (HA).Locate chain must originate in the local LR of bottom and end at mobile subscriber's current location.But all pointers of locate chain are IP addresses of Route Selection.Each link of locate chain can point to its next higher level, the next lower level LR (or another network entity) of same domain (subtree), if perhaps LR is root LR itself, then points to a not root LR of same area.Consider that for efficient pointer can also refer to any other LR (or network entity).No matter when send general register request message, a timer all is set.Have only when timer expires, just send a retry or registration failure (after time failure retry of N>=0) message to appropriate users.
Have full distributed positioned update processing in the such system that handles global mobile management and use in real time expects very much.As long as a location register receives general registration request, whether it will be that the last transition of route is apart from making a decision at it.If not last transition distance, it will determine the next one of the general registration message distance that jumps.In a preferred embodiment, will make all mobile management message Route Selection decisions according to the sign (NAI) of mobile subscriber, previous LR and current LR.
Here will directly not relate to the mobile node of separating in the registration process.Separate registration process and should be a part that the mobile subscriber starts and that handle by the positioned update that the group effort of LR network is finished.
One separate registration message will notify all be positioned in the past on the locate chain that is associated with mobile subscriber's MN current location and no longer be positioned at present with the related locate chain of the reposition of this mobile node on LR, and should be correspondingly new database more.
What check was received separates after the registration message, and the state of usefulness " transmissions " that any LR can upgrade it is indicated the related data project of mobile subscriber's reposition (IP address).The pointer that passes on can help, and for example, the grouping on the horizon of roaming mobile subscribers is sent to its reposition.Transmitting pointer is effective before its life-span expires.Arrive after date when the life-span, will from the database of LR, eliminate relevant item.In this, all information of mobile subscriber also will be eliminated from the database of LR such as user's secret data, user profiles etc.
For example.Suppose the mobile subscriber is assigned to LR1121 as its register way address (NAL), as shown in Figure 4.If mobile node is retained in the coverage of LR1121, then will there be locating information in the LR layering, because if there is not available locating information on any LR, then acquiescence supposition mobile subscriber is in this locality.Then, suppose that the mobile subscriber attempts to register in the area of coverage of LR2122.Foundation is started from the locate chain that local LR ends at LR2122.Several potential modes of setting up locate chain are arranged.A kind of possible mode is as described below.Pointer comprises the IP address of next upper strata LR among each LR (except the top layer) in mobile subscriber's local domain.For example, pointer is present among the LR1121 that points to LR112 etc.A pointer that points to the root node of access domain (LR2) is arranged on the top layer LR of mobile subscriber's local domain.In each LR of mobile subscriber's external domain, there is a position indicator pointer that points to location mobile subscriber's next lower level LR.For example, the pointer on LR2 indication RL21 is the next one of the located in connection chain distance that jumps.LR21 has the pointer that points to LR212.LR212 has the pointer that points to LR2122, and the latter has the link layer connection (for example, on Common Control Channel) to MN.
Another method is to walk around some layer of LR.For example, the pointer of the relevant LR in the MN local domain can be external domain root node LR2 with minimizing jump apart from the counting.
As a MN successfully after the registration when moving to a different locating area, for example, when it to the LR2122 registration and when moving to the area of coverage of LR2121, registration message does not always turn back to LR1121.In fact, may be at a distance of half earth.The associated pointers among LR212, the LR2122 is just upgraded in required variation, and sets up a new pointer in LR2121.All these renewals are carried out partly.
Because locating information is local available in the LR of mobile subscriber's this locality and external domain, and on statistics, most of business (Incoming and striking out) produce in these territories, has therefore significantly reduced the shake of time delay and correlation time.For example, at local LR1121 and being currently registered under the situation of LR2122, one produces in the area of coverage of calling at LR2121 of MN, and this can be by visiting LR2121 partly, and LR212 and LR2122 find callee's position.
Might communication system have by a plurality of entities.Therefore, two kinds that have adjacent LR.The LR of the first kind is those LR that share same operation power.In the case, they can share identical secret data.The second class LR is those LR under the different operating power.A kind of security key management mode of supporting to set up the secure federation body among these LR must be arranged here.
Suppose that the secure federation body is established, and can between territory (set), suitably work from different network operators' LR.Also suppose and between LR, set up the secure federation body.Suppose that also from the LR of same area not must be compatible, just they must support encapsulation, compression mechanism of a common type etc. at least.Need to prove, be that the secure federation body is set up on the basis based on the network operator to the network operator rather than to call out calling.
When MN carries out general registration, must comprise MN-HA checking extension name, as the part of general registration request.Receive a general registration request, if the local copy of MN associated safety data is arranged.Then LR will confirm the validity of MN.If the mobile subscriber is verified that partly it will upgrade its location database, and confirm that to its upstream (to upgrade chain corresponding with the position) network entity the position upgrades.Otherwise if the local copy of MN associated safety data is arranged but authentication failed, then it will reject this request (ignore this request or send a NACK).If there is not the available secure data in this part, then LR is forwarded to the next one distance that jumps with registration message along the path to the mobile subscriber's who requires to verify local network.During this period, the position indicator pointer of Geng Xining will be noted as " co-pending " stage with finite lifetime that is in recently, until (corresponding with the positioned update chain) LR receives a positive reply from the downstream.If the relevant life-span expires or, receive negative reply for mobile subscriber's information co-pending, then refuse this request and give up related data.If before the relevant life-span expires, receive positive reply, then relevant location information is upgraded to " effectively " state from " co-pending ", and an acknowledge message is sent to its upstream (corresponding with position renewal chain) network entity.
Checking among the LR is carried out by the checking extension name.It shares identical form, and the default algorithm support is still distinguished according to its type such as the demand that is defined three the checking extension name of mobile substantially IP.This checking symbol numerical value calculates from byte stream, these bytes comprise shared secret, UDP Payload (promptly, general registration request or answer message), all type and length in their integral body in preceding extension name and this extension name, but do not comprise checking symbol field itself, do not comprise the UDP title yet.This extension name is required to use in any general registration request and answer message.
Handle the LR that upgrades the position and only under two conditions, successfully generate general registration answer.First condition is to be the terminal point of forward facing position renewal processing as LR.Such example be when it be bottom LR in mobile subscriber's the local domain.Another example be when it be know the mobile subscriber secure data LR and need in system, further not propagate positioned update message the time.
Generating the second condition that general registration answers is, when a LR receives the general registration answer that is used for mobile subscriber co-pending from its downstream LR.General registration is answered will be forwarded to upstream (corresponding with the positioned update chain) network entity.Generate a general registration answer message, a downstream (corresponding with mobile subscriber's positioned update chain) LR must can be from layering LR extension name or the LR IP address, upstream that obtain in the new address extension name the general register request message that receives again to the next one with this direct messages, wherein general register request message is recorded in the LR table, with as pointer co-pending.The LR that starts general registration answer distributes suitable secure data (for example, vector is answered in registration keys or inquiry) to relevant LR.For example, LR can use the mobile subscriber's key that is added on the general registration answer message to answer extension name, perhaps can use other aaa functionality.Can also comprise the user profiles extension name, with a part as general registration answer message.The distribution of secure data and subscriber profile information makes it available to the visited network part, and then reduces by the time delay and shake correlation time of verifying and serving that the triangle Route Selection (long line loop) in activity's reason causes,
If present mobile-outside LR checking extension name in general register request message, then the LR in the external domain will carry out checking.Equally, if in general register request message, present outside-local verification extension name, then between the LR of accessed and local domain, carry out checking.
If all are working properly, the all-network entity that sends a general register request message must receive one and also only receive a general registration answer.When LR generated or receives a general registration and answers, this forwards where its execute store locating function determined.When the general registration that receives success as (corresponding with the located in connection chain) LR from its downstream was answered, the bottom LR in the visited network must send general registration answer to relevant MN.
It should be noted that general registration request/answer message may be because of encrypting and security consideration need be encoded again on some branch road of positioned update chain.For example, answer extension name if present mobile subscriber's key, the LR that then receives general registration answer deciphers this secure data.Before being forwarded to next LR, can (when needing), for example new mobile subscriber's key is answered extension name and be added on the general registration answer message.New mobile subscriber's key is answered extension name and is comprised secure data, and this secure data is to jump apart from shared between a LR private cryptography with the LR in the layering and the next one.
This general registration is answered to transmit to handle and is repeated in each LR that participates in of layering, arrives the residing bottom LR of mobile subscriber until this message.When bottom LR received general registration and answers, its execute store locating function also was transmitted to mobile node to this answer.
The purpose of existing IP encryption technology is to carry secure data.The purpose of existing IP verification technique (AAA and security extension name) is to support the LR checking to handle.The security extension name is the part of general registration request and general registration answer message.For example, when LR received general registration request from another LR, it need use and send the checking extension name in the mobility safety association check message that LR shares.The checking extension name need be used for general registration message.If checking is achieved success, then upgrade location database.Otherwise, should promote the checking exception.
Each location of mobile users renewal that is triggered by general registration request is associated with a maximum life.When sending general register request message, relevant LR should be set to remain registration lifetime in this life-span.The position that is used for identical mobile subscriber of each back is upgraded and will be refreshed this life-span.Effectively separate registration process owing to there is one,, should be set to sizable value by life parameter for the consideration of network bandwidth efficient.
Usually use to generate (layer 1), use amount to (layer 2) and draw a bill (layer 3) between cut apart accounting feature.In UMIP, will use to generate and amount to merge.The function that merges is distributed on a layer i, and (i=is used for 1 of RAN, corresponding to the L1 among Fig. 1; Perhaps 2 among the i=CN is corresponding to the L2 among Fig. 1) LR in.The network operator can determine that this combination accounting feature is in RAN or in CN.
Except elemental user and information on services, each LR on the locate chain of layer i also will comprise the accounting of user information that is maintained at usually in the system that draws a bill that keeps accounts (layer 3).For example, LR will comprise following information: when day access that is allowed to, the different brackets of the service that will provide, and credit/prepay status.
Because bearer path is by LR, therefore, the LR record that generated with user-dependent business.Except the accounting of user information that keeps in LR, user service information will allow LR to set up CDR (call details record), and these records are sent to the record keeping that the generates user's invoice system that draws a bill.The record keeping system of drawing a bill contains the required information of generation invoice, for example title, address, credit card number, record keeping address and telephone number.
When the user is in a visited network, user's CDR will collect in the accessed record keeping system of drawing a bill, and this locality that sends it to user system that draws a bill that keeps accounts.
This distributed record keeping scheme does not need to collect to mediate device from the centralized record keeping of the use information of all-network unit, determines to use because will go up at source LR (for example, LR1121 among Fig. 1 or LR112).In addition, network operator does not need to use independent ' prepaid server ', because can obtain the advance payment state information on the LR of source yet.When the transmission user uses data in network, will consume a spot of communication resource, consequently customer service will obtain more bandwidth.
Accounting of user information among the accessed LR is distributed to LR with the registration answer message.On the contrary, if upgrade accounting of user data (for example, the change of rank of the service that provides), then it is sent to the current LR that the user is registered at the LR of local network.
The user can visit the charging information of being stored among he the current local LR that is registered.Available information comprises the rank and the prepay status of the service of allowing.Deserving accessing allows the user to check his record keeping state in real time.
The flow chart of Fig. 5 has shown when receiving a registration request in the response of the LR of communication system middle level i>1 of operation according to one embodiment of present invention.Receiving registration request back (step 20), carrying out the LR checking and determine (step 22).Under the situation that LR is not verified, the message of authentication failed sent to send location register (step 24), this processing stops then.Under the situation that LR is verified, on step 26, determine layer i processing node whether in local branch, wherein i=2.If, then generating one and answer (step 28), flow process advances to Fig. 6 then.Otherwise flow process advances to step 30, determines at this whether a project exists.If, generating an answer in step 28, flow process advances to Fig. 6 then.If not, whether flow process advances to step 32, be outside root node at this node of determining this message of processing.If determine on step 34 that then whether mobile node is from another external domain.If, then sending and separate registration in step 36, the transmission link address that carries in this message is set to equal LRn (2), and the destination address of message to be sent is set to equal the current root node.
After this, in step 38, for the request of will registering sends to the local root node with transmission link address identical with the node of processing messages address, destination address is set to equal the local root node.After this, in step 40, establishment has the project of state co-pending.If on step 34, mobile node is not from another external domain, then on step 38, for the registration request is sent to the local root node with transmission link address identical with the node of processing messages address, destination address is set to equal the local root node.If on step 32, the node of processing messages is not outside root node, and then flow process advances to step 42, at this node of determining processing messages whether in local branch.If then in order to send the registration request, destination address is set to equal the address (step 46) of LR (i-1), and establishment has the project of state co-pending on step 40.If the node in step 42 processing messages is not in local branch, in order to send the registration request to female LR, destination address is set to equal the address (step 44) of LR (i+1), and establishment has a project of state co-pending on step 40 so.
After this, in step 48, determine whether to receive to have the registration request that transmits link address.If the pointer that then is indicated to the next location register on the chain of mobile node is set to equal to transmit link address (step 54), send and have the registration request (step 56) that transmits link address, stop then handling.If on step 48, the registration request of receiving does not transmit link address, the pointer that then is indicated to the next location register in the chain of mobile node is set to equal to send the IP address (step 50) of location register, send the registration request that does not transmit link address in step 52, stop then handling.
The flow chart of Fig. 6 and Fig. 7 has shown when generating a registration answer, the response of LR in Cao Zuo the communication system according to one embodiment of present invention.After making a generation to answer decision (step 28), determine whether mobile node is verified (step 72).If not, the answer that will have authentication failed sends to and sends location register (step 74), and stops to handle.If verified mobile node, extract user profiles (step 76) so in step 72.After this, determine that mobile node is whether on local network (step 78).If, then in step 80, create a project, indicate the pointer of the next location register in this chain to be set to identical or with to send the location register address identical, this depends on the state of pointer with the transmission link address that in register request message, carries.Then, destination address message is set to equal to send location register.After this, flow process advances to piece A, the step 81 of Fig. 7.If mobile node, determines then that whether mobile node is at present in local (step 82) not in local (step 78).If then determine whether to send and separate registration (step 84).If, then sending the registration of separating with transmission link address of equaling LRn (2) in step 86, destination address is set to equal the address of LR (i+1), and the life-span is set.After this,, eliminate this project, and stop to handle in step 90 for RR is provided with the life-span and send answer (step 88) to postbacking.
Do not separate registration if on step 84, do not need to send,, to send the registration of separating with destination address identical with the address of layer 1 location register in the local branch then in step 92.After this, the life-span is set and send one to answer (step 88), eliminate this project, stop then handling in step 90 to postbacking.
If mobile node is not in this locality on step 82, the node of determining processing messages in step 94 territory whether externally then.If then determine whether to send and separate registration in step 96.If, then step 98 send have be set to indicate chain in the identical destination address of the current pointer of next location register separate registration, will transmit the link address setting for equaling LRn (2) and the life-span being set.After this in step 100, be set to equal to send the address of location register and be set to equal pointer, come more new projects by destination address by pointer.After this, flow process enters piece B, the step 101 of Fig. 7.Do not send on step 96 if separate registration, then flow process advances to above-mentioned step 100.If the node of processing messages is externally territory (step 94) not, then determine that in step 102 whether the node of processing messages is in local branch.If not, flow process enters above-mentioned step 96.If then determine in step 104 whether mobile node roams into root node.If in step 104, mobile node does not roam into root node, then determines whether to send in step 106 and separates registration.Separate registration if be ready for sending, then flow process enters above-mentioned step 98.If not, then flow process advances to above-mentioned step 100.If roam into root node, then determine that in step 108 whether externally mobile node at present in the territory at step 104 mobile node.If then flow process advances to piece C, the step 109 of Fig. 7.If in step 108, mobile node roams into external domain, then send and separate registration in step 110, and if i=I, destination address is set to equal current pointer, otherwise destination address is set to equal the address of female LR i+1.In addition, will transmit the link address setting for equaling LRn (2) and the life-span being set.After this, in step 112, if i greater than 2, compiles renewal to postbacking to send, this compiles destination address, the life-span of upgrading transmission link address with the node that is set to equal processing messages, being set to equal the address of LR in the local branch (i-1).After this, flow process advances to above-mentioned step 100.
If determining on the step 108 is sure, then determine in step 120 whether mobile node comes from the external domain roaming.If, then in step 122, sending and separate registration message, this knot registration message has the destination address that is set to equal current pointer, transmission link address, the life-span that is set to equal layer 2 location register (that is LRn (2)) in the new branch.If on step 120, mobile node is territory externally not, then determines whether to send in step 124 and separates registration and compile renewal.If, then sending and separate registration message in step 126, this separates registration message and has the destination address that is set to equal current pointer, be set to equal transmission link address, the life-span of layer 2 location register (that is LRn (2)) of new branch.If determining of step 124 is not will send to separate registration and compile renewal, then project is updated to state co-pending, and pointer is set to the transmission link address that equals to carry in the register request message in step 130.
Transmission is separated after the registration, flow process advances to step 128, compile renewal at this to postbacking to send, this compiles to upgrade and has the transmission link address that is set to the transmission link address that equals to carry in the register request message, destination address, the life-span that is set to equal LRn (i-1) address in the local branch.After this, in step 130, project is updated to state co-pending, and is set to the transmission link that equals to carry in the register request message by pointer, it is co-pending that pointer is set to.In step 132, determine whether to send answer along local branch.If then be set to equal the address of female LR (i+1) in step 134 destination address.If not, then in step 136, destination address is set to equal to indicate the pointer of next location register in the chain.After this, flow process advances to piece B (step 101), arrives step 140 then, at this is set the life-span, sends answer and state and is set to effectively.After this, processing stops.If flow process advances to piece A (step 81), then send one and compile updating message in step 138, this compiles updating message and has the destination address that is set to equal layer 1 location register (that is LRh (1)) in the local branch, be set to equal the transmission link address of the node of processing messages.After this, flow process advances to step 140, at this is set the life-span, and the state that sends answer and project is set to equal effective.
The flow process of Fig. 8 has shown the response as the LR of layer i>1 of receiving a communication system of operating according to one embodiment of present invention when registering answer.Layer i location register (i is greater than 1) receive a registration answer after (in step 150), then make the LR checking and determine (step 152).If do not verify, then send the message of authentication failed to the location register that sends answer.Handle then and stop.
If empirical tests on step 152 then determines to handle the node of this message whether in local branch in step 156.If not, then in step 158, destination address is set to equal this pointer.If in step 156, the node of processing messages then determines whether to send along local branch in step 162 not in local branch.If not, flow process advances to above-mentioned step 158, is set to equal this pointer in this destination address.If determining on the step 162 is to prepare to send along local branch, then in step 164, destination address is set to equal the address of female LR (i+1).After destination address is set up, make sure determining in step 160.If the answer on the step 160 is sure, then is set to effectively and upgrades the life-span at step 166 state.After this, send an answer in step 168, processing stops then.If the answer on the step 160 negates, the project in step 170 deletion LR table then, and determine whether to send negative answer in step 172.If not, this processing stops.If be ready for sending negative reply, then send this answer in step 168, this processing stops then.
The flow process of Fig. 9 has shown when generating a registration request, the response of a mobile node in Cao Zuo the communication system according to one embodiment of present invention.Mobile node receives (step 180) after a paging or the mobile Ipi agent advertisement message, and new network access identifier is set to equal the network access identifier (step 182) that received.After this, in step 184, determine whether new network access identifier equals current network and insert identifier.If then processing stops.If not, then sending the registration request to location register (1) in step 186, processing stops then.
The flow chart of Figure 10 has shown when receiving a registration answer, the response of a mobile node in Cao Zuo the communication system according to one embodiment of present invention.After mobile node is received an answer (step 190), carry out a checking in step 192 and determine.If it is fixed that checking determines whether, then this processing stops.If checking determines it is sure, then make certainly and determining in step 194.If it is sure answering, then in step 196, upgrade this address, and current network inserts identifier and be set to equal new network access identifier, and indicate this registration to finish.After this, processing stops.If in step 194, answer is negated, then at determining that step 198 resends.If determining of resending negated that then processing stops.If resending on the step 198 determines it is sure, then resend register request message, and stop this processing in step 200.
The flow process of Figure 11 has shown when generating a life-span during update request, the response of a mobile node in Cao Zuo the communication system according to one embodiment of present invention, after generating a life-span update request (step 210), determine in step 212 whether the life-span expires.If not, then this processing stops.If in step 212, the life-span will expire, and then send the life-span update request in step 214 to the location register (1) of locking mobile node, after this finish this processing.
The flow chart of Figure 12 has shown when receiving life-span and has upgraded when answering the response of a mobile node in Cao Zuo the communication system according to one embodiment of present invention.After mobile node is received a life-span renewal answer (step 220), verify definite in step 222.If it is fixed that checking determines whether, then stop this processing.If the checking on the step 222 determines it is sure, then on step 224, upgrade the life-span, stop this processing then.
The flow chart of Figure 13 has shown when receiving a registration request to have the response of a LR of layer=1 according to one embodiment of present invention in Cao Zuo the communication system.After location register (1) receives a registration request (step 230), create a project co-pending in step 232, pointer is set to equal the address of female LR (i+1).After this, in step 234, the request of will registering is forwarded to location register (2), stops this processing then.
The flow chart of Figure 14 has shown receives when a registration is answered to have the response of a LR of layer=1 according to one embodiment of present invention in Cao Zuo the communication system.After location register (1) receives a registration answer (step 240), verify definite in step 242.If it is fixed that checking determines whether, then stop to handle.If checking determines it is sure, then on step 244, carry out determining certainly.If it is sure answering, then on step 246, be set to effectively come more new projects by state, after this this answer is forwarded to mobile node in step 248.Stop then handling.If the answer on the step 244 is negated then to handle the affirmation negating in step 250, and carry out determining of a transmission answer in step 252.Negate then to stop to handle if send determining of answering.If what the transmission on the step 252 was answered determines it is sure, then on step 248, this answer is forwarded to mobile node, and stops to handle.
The flow chart of Figure 15 has shown when one of reception compiles renewal to have the response of a LR of layer=1 according to one embodiment of present invention in Cao Zuo the communication system.Receive one at location register (1) and compile renewal back (step 260), on step 262, verify definite.If it is fixed that checking determines whether, then stop to handle.If the checking on the step 262 determines it is sure, then on step 264 mobile node away from situation under upgrade this project, stop then handling.
The flow chart of Figure 16 shown when receiving that is separated when registration, has in Cao Zuo the communication system according to one embodiment of present invention layer=response of a LR of 1.When location register (1) receive separate registration after (step 270), carry out a checking in step 272 and determine.If it is fixed that this checking determines whether, stop to handle.If checking determines it is sure on the step 272, then in step 274, mobile node away from situation under upgrade this project, and stop to handle.
The flow chart of Figure 17 has shown when receiving that a life-span during update request, has the response of the LR of layer=1 according to one embodiment of present invention in Cao Zuo the communication system.After location register (1) is received a life-span update request (step 280), verify definite in step 282.If it is fixed that this checking determines whether, then stop to handle.If the checking on the step 282 determines it is sure, then will ask to be forwarded to female LR (i+1) life-span, after this stop to handle.
The flow chart of Figure 18 has shown when receiving that a life-span is upgraded answer to have the response of a LR of layer=1 according to one embodiment of present invention in Cao Zuo the communication system.After location register (1) is received a life-span renewal answer (step 290), verify definite in step 292.If it is fixed that checking determines whether, then stop to handle.If the checking on the step 292 determines it is sure, then upgrade this project in step 294, the life-span is set to equal life-span of being received, and will answer in the life-span on step 296 and be forwarded to mobile node, after this stops to handle.
The flow chart of Figure 19 has shown when receiving one when separating registration message, the response of a LR of layer i>1 in Cao Zuo the communication system according to one embodiment of present invention.When layer i location register (i is greater than 1) receive one separate registration message (step 300) after, carry out a checking in step 302 and determine.If it is fixed that checking determines whether,, separate the message of an authentication failed of location register transmission of registration to transmission then in step 304.After this, stop to handle.If the checking on the step 302 determines it is sure, then determine to handle the node of this message whether on layer 2 in step 306.If not, then on step 308, sending and separate registration, its destination address that has is set to equal the address of the indicated LR of existing pointer (i-1).If in step 306, the node of processing messages is on the layer 2, whether node that then determine to handle this message on step 310 is in local branch, if on step 310, the node of handling this message is not in local branch, and then the destination address of the message that will send in step 314 is set to equal current pointer.If in step 310, the node of handling this message is in local branch, then determines whether to send along local branch in step 312.If then in step 316, the destination address of the message that will send is set to equal the address of female LR (i+1).If what the edge branch on the step 312 sent determines to negate then to be set to equal current pointer in step 314 destination address.Be provided with after the destination address, flow process advances to step 318, has in this transmission and inherits the registration of separating that transmits link address and the life-span of explaining registration by oneself or default lifetime.After this, in step 320, whether the node of determining processing messages is in local branch.If not, then be set to equal transmit at step 324 state, the state of indication mobile node project, the pointer of next location register is set to the transmission link address that equals to carry in the message in the indication chain, and upgrades the life-span.After this, stop to handle.If in step 320, the node of processing messages is then eliminated this project on step 322 in local branch, after this stop to handle.
The flow chart of Figure 20 has shown when receiving and has compiled when upgrading the response of a LR of layer i>1 in Cao Zuo the communication system according to one embodiment of present invention.After location register (i) (i is greater than 1) receives to compile renewal (step 330), verify definite in step 332.If it is fixed that checking determines whether, then in step 334, the location register that compiles renewal to transmission sends the message with authentication failed, after this stops to handle.If checking determines it is sure on the step 332, then determine whether to send and compile renewal in step 336.If, then in step 338, sending and compile renewal usefulness, this destination address of compiling renewal is set to equal the address of the indicated LR of existing pointer (i-1), and inherits entrained transmission link address in life-span and the message according to compiling updating message.After this, in step 340, pointer is set to equal to transmit link address, and upgrades the life-span.If the transmission on the step 336 compile renewal determine negate, then flow process advances to above-mentioned step 340, at this, pointer is set to equal to transmit link address, and upgrades the life-span.
The flow chart of Figure 21 has shown when receiving a life-span during update request, the response of a LR of layer i>1 in Cao Zuo the communication system according to one embodiment of present invention.In step 350, when location register (i) (i is greater than 1) receives that a life-span is during update request, carry out a checking in step 352 and determine, fixed if checking determines whether, then the location register of asking to the transmission life-span in step 356 sends an authentication failed message and stops to handle.If the checking on the step 352 determines it is sure, then carry out a mobile node checking and determine in step 354.If mobile node is not verified, then send authentication failed message to the location register that sends the life-span request.If at this mobile node of step 354 checking, then determine layer i processing node whether in local branch, wherein i=2 in step 358.If then determine whether to upgrade the life-span in step 360.If the life-span prepares to upgrade, then a new life-span is set and determines whether to send a life-span answer in step 364 in step 362.If not, stop to handle.If, then sending the life-span and answer in step 366, this life-span answers and has the destination address that is set to equal by the address of the LR (i-1) of existing pointer indication.After this, stop to handle.If determining of the renewal life-span on the step 360 negated then to stop to handle.If determining on the step 358 negate, externally whether the node of then determining to handle this message on step 368 on the root node.If then the destination address in step 370 message to be sent is set to equal the local root node, and on step 372, send the life-span update request.If in step 368, the node of processing messages is externally on the root node, then determines that in step 374 node of processing messages is whether in local branch.If not, for the life-span update request is sent to female LR, the destination address of message to be sent is set to equal the address of female LR (i+1).If in step 374, the node of processing messages is in local branch, and then in step 378, the destination address of message to be sent is set to equal the address of the LR (i-1) in the local branch.After this, send the life-span update request in step 372.Send after the LTR, flow process advances to the step 360 in above-mentioned renewal life-span.
The above-mentioned explanation of the preferred embodiments of the present invention is used for exemplary and illustration purpose.This explanation is not detailed, perhaps limits the invention on the disclosed precision architecture.Clearly, according to above-mentioned instruction, various modifications or variation all are possible.Select and explanation embodiment is for the best illustration of principle of the present invention and practical application is provided, and make the common skilled person of this area can utilize different embodiment and obtain various modification of the present invention, the specific use of being thought deeply to be suitable for.All such modifications and variation all fall into scope of the present invention.Scope of the present invention by by equitably, law ground and the described claim when reasonably the protection range of vest right makes an explanation determine.

Claims (1)

  1. One kind in communication system the location portable transceiver method, communication system has:
    Various ports is used for transmitting the communication information through communication system between a plurality of transceivers, and portable transceiver is a member of a plurality of transceivers, and each of a plurality of transceivers is connected with a port of various ports;
    Multiple node is used for transmission information between various ports, and one of each of various ports and multiple node is connected, and each of multiple node has a memory, and this memory can be stored the data of the indication port that portable transceiver connected; With
    A plurality of node trees comprise various ports and multiple node, and each of a plurality of node trees has:
    A plurality of described various ports; With
    The described multiple node that a plurality of hierarchical systems of pressing node constitute; Wherein
    Root node is constructed to the high node in the hierarchical system of node;
    Wherein a plurality of node trees comprise:
    A local tree that is associated with portable transceiver; Described portable transceiver has an address of the local port of the local tree of indication, and a plurality of node trees also comprise:
    One second tree has second port, said method comprising the steps of:
    (a) second port is connected with portable transceiver; With
    (b) response Connection Step (a) is added to one first data items on the root node of local tree, and this first data items is associated with portable transceiver, and indicates the root node of second tree.
CN01800447A 2000-03-10 2001-02-27 Multiple tree hierarchical communication system and method Pending CN1364389A (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US52356200A 2000-03-10 2000-03-10
US09/523,562 2000-03-10

Publications (1)

Publication Number Publication Date
CN1364389A true CN1364389A (en) 2002-08-14

Family

ID=24085507

Family Applications (1)

Application Number Title Priority Date Filing Date
CN01800447A Pending CN1364389A (en) 2000-03-10 2001-02-27 Multiple tree hierarchical communication system and method

Country Status (6)

Country Link
EP (1) EP1179268A4 (en)
JP (1) JP2003527008A (en)
KR (1) KR20020000887A (en)
CN (1) CN1364389A (en)
AU (1) AU2001243301A1 (en)
WO (1) WO2001069948A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114187341A (en) * 2021-11-16 2022-03-15 泰瑞数创科技(北京)有限公司 Artificial neural network road texture mapping method and system based on mobile following recognition

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1477884A (en) * 2002-08-20 2004-02-25 �廪��ѧ Hiearchical moving data packet communication network and its communication method
JP4378182B2 (en) * 2003-12-22 2009-12-02 株式会社ケンウッド Mobile communication system, mobile communication control method, and program
US20070239906A1 (en) * 2006-03-13 2007-10-11 Vakil Kersi H Input/output agent having multiple secondary ports
CN102223734A (en) * 2011-06-14 2011-10-19 广州从兴电子开发有限公司 Wireless communication network and communication method of same
FR3002101B1 (en) * 2013-02-12 2016-07-01 Streamwide LOCATION OF MOBILE TERMINALS
CN110351827A (en) * 2019-07-30 2019-10-18 深圳小鲨智能科技有限公司 A kind of wireless self-networking method and system based on Sub-GHz

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5539922A (en) * 1992-01-03 1996-07-23 Motorola, Inc. Multiple tree hierarchical portable communication system and method
US5956637A (en) * 1996-02-20 1999-09-21 Telefonaktiebolaget L M Ericsson (Publ) Subscriber database management in a mobile telecommunications system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114187341A (en) * 2021-11-16 2022-03-15 泰瑞数创科技(北京)有限公司 Artificial neural network road texture mapping method and system based on mobile following recognition

Also Published As

Publication number Publication date
JP2003527008A (en) 2003-09-09
KR20020000887A (en) 2002-01-05
EP1179268A4 (en) 2002-09-18
AU2001243301A1 (en) 2001-09-24
WO2001069948A1 (en) 2001-09-20
EP1179268A1 (en) 2002-02-13

Similar Documents

Publication Publication Date Title
CN1202689C (en) Arrangement for secure communication and key distribution in telecommunication system
CN1231079C (en) Selection of mobility agent in access network
CN1867200A (en) Controlling access to communication services
CN1264091C (en) Distributed cache synchronization protocol
CN101036353A (en) Method, apparatus and system for routing AAA-messages from a home service network over a number of intermediary networks to a roaming network
CN102318381A (en) Method for secure network based route optimization in mobile networks
CN1969529A (en) Autonomous and heterogeneous network discovery and reuse
CN1902978A (en) Context transfer in a communication network comprising plural heterogeneous access networks
CN1711794A (en) Providing of route information in communication system
CN1209943C (en) Handover in wireless mobile-IP network
CN1173954A (en) Packet radio system and methods for a protocol-independent routing of a data packet in packet radio networks
CN1759628A (en) Methods and apparatus for providing manual selection of a communication network for a mobile station
CN1361969A (en) Routing in a packet switching network with mobile terminals
CN1902979A (en) Network selection methods and apparatus with home network prioritization in country border regions
CN1623300A (en) System and method for supporting mobility of mobile node using regional anchor point in future internet
CN101052200A (en) Route renewing method in mobile communication system
CN1270555C (en) Architecture and packet routing in a multi-bearer-type network
CN1192576C (en) Multicast business realizing method in mobile network
CN1795656A (en) Secure traffic redirection in a mobile communication system
CN1364389A (en) Multiple tree hierarchical communication system and method
CN1691607A (en) Associating subscriber information between protocols
CN101047971A (en) Method for trigging intelligent service at attatching area when intelligent user roaming
CN1643853A (en) Method and system for providing network services
CN1845638A (en) Wireless data communication monitoring system and method
CN1483296A (en) Method and means for providing enhanced subscriber identity confidentiality during roming in a cellular radio communication system

Legal Events

Date Code Title Description
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C06 Publication
PB01 Publication
C02 Deemed withdrawal of patent application after publication (patent law 2001)
WD01 Invention patent application deemed withdrawn after publication