Method for controlling handover in a mobile telecommunications network
Abstract
This record has no abstract on file.
Term
Term ended
Expired 1 February 2021, 5.6 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
19 claims: 10 independent, 9 dependent
- 1Mobile communication networkOf mobile stations withinCommunication sessionOfHow to control handoverIn, SaidMobile communicationThe network ispluralIncluding wireless access domainEach wireless access domain has a different wireless access technology, the method described above. Indicates a handover requestHandoverReceive the trigger,Using a handover algorithmnetworkHandoverpolicydataTest at least one available handover that meets the above requirements forIt tests whether the network handover policy is met andIf the network handover policy is met,The request and the networkHandoverpolicydataAccording to, Of a communication session between one radio access domain in the plurality of radio access domains and another radio access domain different from it.HandoverStartRu、Method. 移動体通信ネットワーク内で移動局の通信セッションのハンドオーバを制御する方法において、前記移動体通信ネットワークは、複数の無線アクセスドメインを含み、各無線アクセスドメインは異なる無線アクセス技術を有しており、前記方法は、 ハンドオーバの要求を示すハンドオーバトリガを受信し、ハンドオーバアルゴリズムを使用してネットワークハンドオーバポリシデータに対する前記要求を満たす少なくとも1つの利用可能なハンドオーバをテストし、それによって、ネットワークハンドオーバポリシが満たされているかどうかをテストし、前記ネットワークハンドオーバポリシが満たされている場合には、前記要求及び前記ネットワークハンドオーバポリシデータに従って、前記複数の無線アクセスドメインの中の1つの無線アクセスドメインと、それと異なる他の1つの無線アクセスドメインとの間の通信セッションのハンドオーバを開始する、方法。
- 4Assign priority to the request and networkHandoverAssign priorities to policies and follow the relationships between the priorities, Of a communication session between one radio access domain in the plurality of radio access domains and another radio access domain different from it.HandoverstartTo do、ClaimAny one of 1 to 3The method described. 前記要求に優先度を割り当て、ネットワークハンドオーバポリシに優先度を割り当て、前記優先度間の関連に従って、前記複数の無線アクセスドメインの中の1つの無線アクセスドメインと、それと異なる他の1つの無線アクセスドメインとの間の通信セッションのハンドオーバを開始する、請求項1乃至3のいずれか1項記載の方法。
- 6Assign priority to the communication session and networkHandoverAssign priorities to policies and the relationships between the prioritiesAnd the above requestAccording to, Of a communication session between one radio access domain in the plurality of radio access domains and another radio access domain different from it.HandoverstartTo do、ClaimAny one of 1 to 3Item description method. 前記通信セッションに優先度を割り当て、ネットワークハンドオーバポリシに優先度を割り当て、前記優先度間の関連と前記要求に従って、前記複数の無線アクセスドメインの中の1つの無線アクセスドメインと、それと異なる他の1つの無線アクセスドメインとの間の通信セッションのハンドオーバを開始する、請求項1乃至3のいずれか1項記載の方法。
- 11The request isnetworkClaims 1 to the designated request7The method described in any one of the above. 前記要求は、ネットワーク指定の要求である請求項1乃至7のいずれか1項記載の方法。
- 13Even if there is one or more handovers that meet the above requirements, the networkHandoverIf there is no handover that satisfies the policy, perform the handover.DoNo claims 1 to12The method described in any one of the above. 前記要求を満たす1以上のハンドオーバが存在しても、ネットワークハンドオーバポリシを満足するハンドオーバが存在しない場合には、ハンドオーバを行わない請求項1乃至12のいずれか1項記載の方法。
- 14networkHandoverIn addition to the policy and the above requirements, service qualityRequestAccording to, Of a communication session between one radio access domain in the plurality of radio access domains and another radio access domain different from it.HandoverStart,Claims 1 to13The method described in any one of the above. ネットワークハンドオーバポリシと前記要求に加えて、サービス品質に係る要求に従って、前記複数の無線アクセスドメインの中の1つの無線アクセスドメインと、それと異なる他の1つの無線アクセスドメインとの間の通信セッションのハンドオーバを開始する、請求項1乃至13のいずれか1項記載の方法。
- 15networkHandoverIn addition to the policies and requirements mentioned above, according to quasi-static user-specified preferences, Of a communication session between one radio access domain in the plurality of radio access domains and another radio access domain different from it.HandoverStart,Claims 1 to14The method described in any one of the above. ネットワークハンドオーバポリシと前記要求に加えて、準静的なユーザ指定の好みに従って、前記複数の無線アクセスドメインの中の1つの無線アクセスドメインと、それと異なる他の1つの無線アクセスドメインとの間の通信セッションのハンドオーバを開始する、請求項1乃至14のいずれか1項記載の方法。
- 16Handover algorithm resultsNetwork in time to changeHandoverpolicydatachangeHowever, the network handover policy data is changed under the control of the network operator.Claims 1 to15The method described in any one of the above. ハンドオーバアルゴリズムの結果を変更するために、時間でネットワークハンドオーバポリシデータを変更し、ネットワークハンドオーバポリシデータはネットワークオペレータの制御の下で変更される、請求項1乃至15のいずれか1項記載の方法。
- 19Mobile communication networkOf mobile stations withinCommunication sessionOfControl handoverIn the handover manager, SaidMobile communicationThe network ispluralIncluding wireless access domainEach wireless access domain has a different wireless access technology, and the handover manager is Indicates a handover requestHandoverMeans that are configured to receive triggers,Using a handover algorithmnetworkHandoverpolicydataTest at least one available handover that meets the above requirements forAnd thereby test if the network handover policy is metAnd the means that are configured toIf the network handover policy is met,The request and the networkHandoverpolicydataAccording to, Of a communication session between one radio access domain in the plurality of radio access domains and another radio access domain different from it.HandoverstartIs configured toHandWith stepsHandover manager。 移動体通信ネットワーク内で移動局の通信セッションのハンドオーバを制御するハンドオーバマネージャにおいて、 前記移動体通信ネットワークは、複数の無線アクセスドメインを含み、各無線アクセスドメインは異なる無線アクセス技術を有しており、前記ハンドオーバマネージャは、 ハンドオーバの要求を示すハンドオーバトリガを受信するように構成されている手段と、ハンドオーバアルゴリズムを使用してネットワークハンドオーバポリシデータに対する前記要求を満たす少なくとも1つの利用可能なハンドオーバをテストし、それによって、ネットワークハンドオーバポリシが満たされているかどうかをテストするように構成されている手段と、前記ネットワークハンドオーバポリシが満たされている場合には、前記要求及び前記ネットワークハンドオーバポリシデータに従って、前記複数の無線アクセスドメインの中の1つの無線アクセスドメインと、それと異なる他の1つの無線アクセスドメインとの間の通信セッションのハンドオーバを開始するように構成されている手段とを備えている、ハンドオーバマネージャ。
Independent claims10
1 paragraph, as filed
[0001] The present invention relates to mobile communication, and particularly relates to a method of controlling the handover of a mobile station of a mobile communication network. [0002] Handover algorithms are well known in current cellular radio technologies. Cellular mobile stations that receive the services of the cell uplink or downlink channels of the cellular network may experience signal-to-noise ratio (S / N) deterioration of the uplink and / or downlink channels. Performing a handover algorithm in a network that results in handover between cell channels or between different cells ensures that the call does not drop and improves the overall quality of service between the calls. [0003] A number of different wireless access technologies have been proposed for future adoption, providing the appropriate level of service for the type of access where the user requires some specific time. This user's requirements may vary between communication sessions, communication sessions, or single communication sessions. Handovers between different wireless access technologies can be valuable in order to allow users different types of access during a single communication session. For example, when a user requests a video conferencing link, third generation wireless access technology is used. On the contrary, if voice calls are required, second generation wireless access technology may be sufficient. In the future heterologous genotype mobile environment, both user migration and migration should be supported. Therefore, the user should be able to initiate a communication session using different wireless access technologies and be able to deliver services over roaming between wireless access technologies (floating). Furthermore, handover between wireless access technologies should be supported while the user is actively engaged in a communication session (movement). Examples of such handovers are between 2nd generation public GSM networks, 3rd generation public wideband code division multiple access (W-CDMA) networks, and wireless local area networks (WLANs). [0004] According to the present invention, it is a method of controlling the handover of a mobile station that manages a communication session of a mobile communication network, and the network includes a large number of wireless access domains and receives a trigger indicating a request for handover. A method is provided that includes testing at least one available handover that meets the requirements for a network policy and controlling the handover in accordance with the requirements and the network policy. [0005] Further aspects of the invention are presented in the additional claims. [0006] The features and advantages of the present invention will be apparent by the following description of preferred embodiments of the present invention, which are given according to the examples with reference to the drawings. [0007] FIG. 1 illustrates a mobile communication network according to an embodiment of the present invention. This mobile communication network has a number of radio access domains 2, 4, 6 each implementing a different radio access technology. In this example, the first radio access domain 2 is a second generation GSM radio access domain that includes the GSM base transceiver station 3 and operates at frequencies of approximately 900 MHz and / or 1800 MHz. The second radio access domain 4 is a third generation W-CDMA radio access domain that includes the W-CDMA radio access node 5 and operates at a frequency of approximately 2 GHz. The third wireless access domain 6 is a wireless LAN access domain having a wireless LAN access node 7 and can operate at some frequency between 2 and 60 MHz. According to the present invention, the mobile station 8 may communicate via the respective access nodes 3, 5, 7 and via the respective radio access domains 2, 4, 6. For example, a mobile station is a laptop computer with three different wireless access technologies for plug-in cards, or a mobile handset functionally equipped with the appropriate three bands, where the mobile station is GSM, W-CDMA and WLAN. It is used to access the domain and allows it to be attached to a domain suitable for the terminal's request at a specific time. The mobile station also has an interworking function, which allows a substantially uniform handover between different domains during a communication session. While different radio access domains implement different radio access technologies, a single physical access node serves one or more of those radio access technologies, so changing the radio access domain of a mobile station is wireless. It is not always necessary to change the access node. [0008] The radio access domains 2, 4, and 6 each implement a well-known intranet handover mechanism, whereby services provided separately by each radio access domain are provided by mobile stations within the scope of the radio access domain. Maintained throughout the move. [0009] This mobile communication network also has a handover manager 10, which is layered on the individual radio access domains 2, 4, 6 of the network architecture. The handover manager 10 manages the internal domain handover between the radio access domains 2, 4, and 6 according to the handover trigger received during the handling of the communication session managed by the mobile station 8. This handover manager consists of a single service node or a plurality of nodes, and can handle the internal domain handover of all mobile stations connected to the mobile communication network. Alternatively, this handover manager is implemented for the formation of an object-oriented processing system assigned to each handover manager, and the handover manager object form controls the handover function of each mobile station connected to the mobile communication network. To do. These objects include a user agent for initialization, maintain and terminate virtual connections over the core network, and, moreover, "pre-authenticate" the system to see if the user is physically connected. It includes a terminal agent for maintaining a mobile station, a security agent for proving that user authentication has occurred, and a handover agent for controlling the execution of handover. [0010] The handover manager 10 receives the network policy data from the handover policy server 12. In the case of the handover manager 10 implemented in the form of a single node or a plurality of nodes, the data is in the form of a signaling message and is transmitted between the handover policy server 12 and the handover manager 10. In the case of the handover manager 10 implemented in the assigned processing environment, the network policy data is in the form of a handover policy object transmitted between the handover policy server 12 and the handover manager 10. [0011] The management terminal 14 is used to allow the handover policy to be improved by the network administrator, whereby the control of the handover by the handover manager is directly affected according to the operator's request of the mobile communication system. Receive. This allows the operator to modify the result of the handover algorithm without modifying the general mechanism of the handover algorithm, thereby providing convenience and flexibility to the network operator. This operator changes the priorities to conclude possible factors and handovers when planning the handover. [0012] Network policies include: [0013] A) Try to minimize call costs by passing between different wireless access domains and maintain communication in the least possible cost domains when deemed appropriate. [0014] B) Minimize the use of 3rd generation radio access network resources. This policy is especially effective when such resources are scarce. Handovers are performed from the 3rd generation domain whenever in use. [0015] C) When it is deemed appropriate, it exceeds the user's expectation by handing it over to a high quality unused resource. [0016] D) Maximize network efficiency by passing the call to the earning radio access domain for manipulating the cost ratio whenever it deems appropriate. [0017] E) Make a call by giving priority to a particular type of user or by passing it to such a user, or by making a priority call to a high quality resource and then giving it to another user, or Call away from such a resource. [0018] These are examples of many different types of network policies implemented. And it can be highly appreciated that some policies are mutually exclusive (eg, B and C above). However, different internal network handover policies are executed at different times by executing such a policy in the policy server and by providing an interface for the handover algorithm to the policies stored in the policy server. To. [0019] Handover triggers are distinguished in this as a user request and a system request. User requests result from modification of user requests across communication sessions. For example, user applications may have different requirements for security. Handover to a selective radio access domain is required if the current radio access domain does not meet the security requirements for the requested user application. Instead, the user's quality of service (Qos) requirements can change in response to new applications used throughout the communication session. In addition, the capabilities of mobile stations can change depending on the need or priority of handover. For example, the mobile station moves to the target area of the wireless access domain without retaining the necessary software components. Alternatively, the mobile station may have the most recently downloaded software component suitable for the selected wireless access domain. Therefore, the user's request is notified to the handover manager 10 from the user's mobile station or from the user agent (for example, a software object of the processing system) that manipulates the user's interests. If the user is easily served by the GSM network, the transmission of the signal is made as described in our UK patent GB2332340. The user's request is also due to the matching priorities already stored in the system for the user and the new resources available. This is, for example, cost, service level, and privacy priority. User priorities in such a state are stored in the user agent. [0020] System requests arise from wireless access domain standards or network standards. It maintains and improves signal-to-noise ratio or reduces interface overdensity (ie, response to current density), availability (ie, aggressiveness to avoid potential density), priority given to very services. Like Qos standards, forced maintenance behavior, or specific user priorities (eg, access domains that consist primarily of picocells prefer slow-moving users). The system request is notified to the handover manager 10 directly from the currently supplied wireless access domain or network element in the network. [0021] [0021] The data stored on the policy server 12 is defined by different levels of priority and is assigned to all system requests, user requests, network policies, and call types. This allows for some conflicts between different user requirements, wireless access domains, and the network policy itself. And these are determined according to the network policy. These levels of priority are also varied by means of management terminal 14. [0022] The main function of the Handover Manager 10 to receive a handover request or trigger is, firstly, to acquire and compare, and if necessary, information is requested from various sources, including network policy data from the network policy server 12. Related to the handover that was done. From a user-first standpoint, the user agent maintains the capabilities of the mobile station from the terminal agent and the security data from the security agent. Second, the handover manager 10 identifies the best out of all potential handovers, taking into account information that obtains the user's priority and network policy. Third, the handover manager informs the implementation of the most available handover, if any. This handover is controlled by the handover agent. [0023] FIG. 2 illustrates a handover algorithm executed by the handover manager 10 based on the reception of the user request handover trigger in step 100. First, in step 102, the handover manager 10 identifies all handovers that satisfy the user request according to the latest minimum request of the user. If there is no handover that satisfies the user's request, the user request is rejected in step 104. On the other hand, if a single handover can satisfy the user request, the handover manager 10 checks that the network policy is satisfied by the handover. This check includes checking for predetermined features of the handover identified from within the handover policy server 12 related to the network policy, and in step 106 such features go beyond the framework of the network policy. Make sure you haven't. When the network policy is satisfied by the handover that satisfies the user's request, the handover manager 10 executes the handover in step 108. If it is found that the network policy is not satisfied by the handover that meets the user's request, the relevant priority and network policy of the user request, or the element of the unsatisfied network policy, is checked in step 108. If the level of priority given to the user request is higher than the network policy, the handover is performed in any case at step 112. On the other hand, if the network policy is prioritized, the user request is rejected in step 114. [0024] In step 102, it is found that a large number of handovers satisfy the user request and the user's current minimum requirements. A large number of handovers that satisfy the network policy are checked in step 116. If step 102 identifies that no handover satisfies the network policy, then step 118 checks whether the priority given to the user request is superior to the priority given to the network policy. To. If the user request takes precedence, the handover so identified in step 102 and having the best network policy is selected in step 120, and the handover is performed in step 122 according to the best handover selected. On the other hand, in step 118, if the network policy takes precedence over the user request, the user request is rejected in step 124. In step 116, if one of the plurality of handovers identified in step 102 is identified as satisfying the network policy, the handover is performed in step 126. If in step 116 the large number of handovers identified in step 102 are identified as satisfying the network policy, the best handover is identified in step 128. Finding the best handover in this manner allows the user's desired requirements as well as the user's current minimum requirements to be taken into account. For example, a video call can be initiated at 28.8 Kbps, although a bandwidth of 56 Kbps is preferred. If a channel handover that provides 56 Kbps bandwidth is available in step 128, the low bandwidth video call will satisfy both the user request and the network policy, but the low bandwidth video call will be the preferred choice. Will be done. Following the selection of the best handover in step 128, the selected handover is performed in step 130. [0025] As mentioned in FIGS. 3a and 3b, the handover trigger is received by the handover manager 10 for call maintenance reasons. It is referred to as quality of service (Qos) and is expected to degrade signal strength and / or signal quality, or worsen in the current wireless access domain. In this case, the handover manager 10 receives in step 200 a system request that includes a handover trigger for possible handovers for different radio access domains. The handover manager 10 first identifies in step 202 all handovers that satisfy the user's current minimum requirements and system requests. If no handover meets the system requests and those requirements, nevertheless, in step 204, the quality of service is better than the expected or current low quality service received without the handover in step 206. Check whether it is possible to improve and handover. When a handover that provides such a Qos is not available, the system request for the handover is rejected in step 208. However, if one or more good Qos handovers are found in step 206, such a best handover is identified in step 210 and the best handover is tested against the network policy in step 212. If the network policy is satisfied, step 214 performs this selected handover. If the network policy is not satisfied, step 216 tests whether the call is treated with a higher priority than the network policy motive. And if so, the best handover is performed in step 218 in any case. Other than good Qos predicted or available without handover in step 220 when the priority level assigned to the call is not higher than the motivation of the network policy It is tested whether or not the handover is possible. If not possible, the system request will be rejected in step 222. If step 220 identifies that one or more other handovers are possible, the process returns to step 210. [0026] If a single handover is identified in step 204 as satisfying the system request and the current minimal user requirement, the handover manager 10 checks in step 224 to see if the network policy is satisfied. If the network policy is satisfied, this handover is performed in step 226. If the network policy is not satisfied in step 224, then in step 228 it is tested whether the call is prioritized over the network policy, or at least such a feature of the unsatisfied network policy. And if so, the handover selected in step 204 is performed in step 230, even if the network policy is not satisfied. If the network policy is prioritized in step 228, the process proceeds to step 206. [0027] In step 204, if one or more handovers are identified as satisfying the system request and the current minimum user requirements, then a number of handovers that also satisfy the network policy are identified in step 232. If there is no handover identified in step 204 as also satisfying the network policy, then in step 234 the priority level assigned to the call is the priority level of the network policy, or at least the characteristics of the handover that does not satisfy the network policy in step 234. Tested to be larger than. If network policy is prioritized, the system request will be rejected in step 236. When the call is prioritized, the large number of handovers identified in step 204 as having the best network policy compliance are identified in step 238. Then, the selected handover is executed in step 240. [0028] If in step 232 a single handover is identified as satisfying the network policy, then this selected handover is performed in step 242. If the large number of handovers identified in step 232 satisfy the network policy, the best handover identifies in step 244, taking into account the requirements desired by the user in addition to the minimum requirements. Then, in step 246, an appropriate handover is executed. [0029] As mentioned in FIGS. 4a-4c, the handover trigger may be received by the handover manager for reasons other than user requests or call maintenance reasons. For example, this reason is a network maintenance reason (eg domain loading takes more specific time). In this case, the handover manager 10 not only satisfies the system request, the user's current minimum request, and the network policy, but also holds the Qos if possible. [0030] In step 300, a system request generated in a wireless access domain that is currently useful for network reasons is received, and all handovers that satisfy this system request and the user's current minimum requirements are identified in step 302. In the absence of a handover that satisfies such a standard, step 304 determines whether the system request has a higher priority than the call itself. If so, in step 308, a handover that satisfies the system request but does not satisfy the current minimum user requirements, but for reasons of low Qos, nevertheless in step 308. It is checked whether it is available. If so, the available handover is performed in step 310. If not, the call will be forced down in step 312. [0031] If a single handover is identified in step 302, then step 314 is tested to see if the handover results in worse Qos than what is available without the handover. If so, step 316 tests whether the system request is at a higher priority level than the call itself. If so, the handover is performed in step 318, even if the resulting Qos is reduced. If the call takes precedence in step 316, the system request is rejected in step 320. When the handover identified in step 302 is at a similar, high, Qos level, step 322 checks whether the network policy is satisfied by the handover. If so, the selected handover is performed in step 324. If the network policy is not satisfied by the selected handover, step 326 checks to see if the system request is at a higher priority level than the network policy. If so, the handover is performed in step 328. If not, the system request is rejected in step 332. [0032] If, in step 302, a large number of handovers are identified as satisfying the system request and the user's current minimum requirements, all of the identified handovers are held or improved in step 334 by Qos Analyzed to identify whether. If none of the identified handovers can retain or improve the QoS, then in step 336 it is checked whether the system request has a higher priority than the call priority. Otherwise, the system request is rejected in step S338. However, if the system request is prioritized, that of the large number of handovers identified in step 302 with the best predicted Qos will be identified in step 340. This identified handover is tested in step 342 to see if the network policy is satisfied by the handover, and if so, the handover is performed in step 344. If the network policy is not satisfied by the best identified Qos handover, the handover manager 10 tests in step 346 whether the system request has a higher priority than the network policy. If so, the handover is performed in step 348, even if the network policy is not satisfied. However, if network policy is prioritized, step 350 checks for the availability of further handovers. If no further handover is available, the call is forcibly dropped in step 352. If further handover is available, then the best predicted Qos is identified in step 354 and processing returns to step 342. [0033] If step 334 identifies a single handover that holds at least Qos as well as satisfying the system request and the current minimum user requirements, then the handover is in step 334, the network policy. Is tested to check if is satisfied. If so, the selected handover is performed in step 358. Otherwise, step 360 checks to see if the network policy has a higher level of priority than the system request. If so, the process moves to step 340. If the system request takes precedence, the identified handover is performed in step 362. [0034] If, in step 334, a large number of handovers are identified as holding at least Qos, as well as satisfying the system request and the current minimum user requirement, then the network policy is also satisfied. All such handovers are identified in step 364. If none of them satisfy the network policy, then step 366 tests whether the system request has a higher priority level than the network policy. If so, that of the large number of handovers identified in step 334 with the lowest network policy compliance is identified in step 370 and the selected handover is performed in step 372. If network policy takes precedence in step 366, the system request is rejected in step 368. [0035] If a single handover is identified in step 364, that handover is performed in step 374. [0036] If one or more handovers are identified in step 364, a single handover is all standards already taken into account, along with some requirements of the user to identify the best handover. Is selected on the basis of. The network policy is also taken into account in step 376, and once the best handover according to the selected standard is identified in step 376, this selected handover is performed in step 378. [0037] The handover manager 10 controls the execution of the handover suitable for the related heterogeneous type of radio access technology. This execution is performed, for example, by a handover agent. In a basic handover between two access nodes, the handover manager 10 sets up two separate connections to the mobile station, bridging the connections to prevent data loss during the handover. Handover also implies rerouting connections over a fixed network, transmitting control functions tied from one network to another, and initializing new security transactions. [0038] It will be appreciated that various improvements can be adopted as related to the embodiments described above without departing from the object of the present invention. They are defined in the added claims. Although the above overview relates to handover algorithms used for handovers between different wireless access technologies, similar algorithms may be used for other handovers. Generally, the above-mentioned algorithms are used for handover between access nodes / cell channels, wireless access techniques similar to mobile communication networks, term handovers, and some combinations thereof or theirs. It is understood to include a handover between some of the above. For example, when access nodes serving different cells have different capabilities (whether in place of or in general for a particular mobile station required or needed for a particular communication session), of the access node / cell. The handover between them is initiated as a result of a user or system request. Similarly, when different channels of access nodes have different properties, handover between channels is initiated. In frequency division systems, handover between different frequency channels is initiated, for example, to reduce interference. Similarly, in a time division system, a handover between different time slots is initiated, and in a code division system, a handover between different codes is initiated. In addition, if different mobile communication networks have different capabilities (generally, on behalf of a particular access node in the network, or specific required or required for a particular communication session). (Mobile station), handover between the network is started. For example, a handover from one network to another, where roaming aggregates are present, is initiated by a user or system request, resulting in the satisfaction of the Qos request. As a further example, a service provider or virtual service [0039] Although considered separately, the benefits of using a handover algorithm to obtain user preferences or requirements and network policies, and the need for improvement when network policies and / or user preferences or requirements change, are Applies to this case. [Simple explanation of drawings] FIG. 1 is a schematic diagram of a mobile communication network designed according to an embodiment of the present invention. FIG. 2 is a flow chart showing a handover algorithm implemented by the handover manager of the embodiment shown in FIG. 1. FIG. 3a is a flow chart showing a handover algorithm implemented by the handover manager of the embodiment shown in FIG. 1. FIG. 3b is a flow chart showing a handover algorithm implemented by the handover manager of the embodiment shown in FIG. 1. FIG. 4a is a flow chart showing a handover algorithm implemented by the handover manager of the embodiment shown in FIG. 1. FIG. 4b is a flow chart showing a handover algorithm implemented by the handover manager of the embodiment shown in FIG. 1. FIG. 4c is a flow chart showing a handover algorithm implemented by the handover manager of the embodiment shown in FIG. 1. [Explanation of symbols] 2,4,6 wireless access domain 3 GMS Base Transceiver Station 5 W-CDMA wireless access node 7 Wireless LAN access node 8 mobile stations 10 Handover manager 12 Handover policy server 14 Management Terminal
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| WO0005913A1 | Cites | World Intellectual Property Organization (WIPO) | Search report |
| WO9859513A1 | Cites | World Intellectual Property Organization (WIPO) | Examiner |
| WO0005913A1 | Cites | World Intellectual Property Organization (WIPO) | – |
| WO9859513A1 | Cites | World Intellectual Property Organization (WIPO) | – |
38 members in 18 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 0002495 | United Kingdom | A | |
| 0002495 | United Kingdom | A | |
| 00024950 | United Kingdom | – | |
| 0100424 | United Kingdom | W | |
| 0100424 | United Kingdom | W | |
| 2000200002495 | – | – | – |
| 2001000424 | – | – | – |
| GB20000002495 | – | – | – |
| WO2001GB00424 | – | – | – |
Members38
| Document | Office | Kind | |
|---|---|---|---|
| GB0102567D0 | United Kingdom | D0 | |
| CA2399064A1 | Canada | A1 | |
| WO0158177A2 | World Intellectual Property Organization (WIPO) | A2 | |
| AU3039601A | Australia | A | |
| GB2359220A | United Kingdom | A | |
| WO0158177A3 | World Intellectual Property Organization (WIPO) | A3 | |
| GB2364620A | United Kingdom | A | |
| WO0158177B1 | World Intellectual Property Organization (WIPO) | B1 | |
| NO20023664D0 | Norway | D0 | |
| NO20023664L | Norway | L | |
| KR20020077899A | Republic of Korea | A | |
| EP1256254A2 | European Patent Office (EPO) | A2 | |
| HK1045428A | Hong Kong, China | A | |
| CN1398495A | China | A | |
| EA200200827A1 | Eurasian Patent Organization (EAPO) | A1 | |
| US2003125028A1 | United States of America | A1 | |
| JP2003522490A | Japan | A | |
| ZA200206093B | South Africa | B | |
| BR0108069A | Brazil | A | |
| GB2364620B | United Kingdom | B | |
| PL363449A1 | Poland | A1 | |
| AU778444B2 | Australia | B2 | |
| CN1188010C | China | C | |
| HK1045428B | Hong Kong, China | B | |
| CA2399064C | Canada | C | |
| US7149524B2 | United States of America | B2 | |
| US2007117564A1 | United States of America | A1 | |
| US7403778B2 | United States of America | B2 | |
| NO328375B1 | Norway | B1 | |
| EP2164287A1 | European Patent Office (EPO) | A1 | |
| EP1256254B1 | European Patent Office (EPO) | B1 | |
| AT469517T | Austria | T | |
| ATE469517T1 | Austria | T1 | |
| DE60142222D1 | Germany | D1 | |
| ES2345183T3 | Spain | T3 | |
| JP4842485B2This record | Japan | B2 | |
| EP2164287B1 | European Patent Office (EPO) | B1 | |
| ES2553110T3 | Spain | T3 |
28 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of completion of termEXPY | EXPY | |
| Cancellation because of completion of termEXPY | EXPY | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelR150 | R150 | |
| Certificate of patent or registration of utility modelR150 | R150 | |
| First payment of annual fees (during grant procedure)A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedA521 | A521 | |
| Written permission of extension of timeA602 | A602 | |
| Written request for extension of timeA601 | A601 | |
| Notification of reasons for refusalA131 | A131 | |
| Request for written amendment filedA521 | A521 | |
| Request for written amendment filedA521 | A521 | |
| Notification of change in applicantA711 | A711 | |
| Report on retrievalA977 | A977 | |
| Request for written amendment filedA521 | A521 | |
| Written request for application examinationA621 | A621 |
Numbers
- Publication
- 4842485
- Publication, DOCDB
- 4842485
- Publication, EPODOC
- JP4842485B
- Application
- 557302
- Application, DOCDB
- 2001557302
- Application, EPODOC
- JP20010557302
Titles2
- Japanese
- 移動体通信ネットワークのハンドオーバを制御する方法
- English
- How to control the handover of a mobile communication network
Classification
- CPC, 1
- H04W36/24
- IPC, 4
- H04W36 16
- H04L12 56
- H04W36 12
- H04W36 14