EP1978768A1 - Système de communication mobile, dispositif de commande de réseau sans fil et méthode de répartition de charge - Google Patents
Système de communication mobile, dispositif de commande de réseau sans fil et méthode de répartition de charge Download PDFInfo
- Publication number
- EP1978768A1 EP1978768A1 EP06834549A EP06834549A EP1978768A1 EP 1978768 A1 EP1978768 A1 EP 1978768A1 EP 06834549 A EP06834549 A EP 06834549A EP 06834549 A EP06834549 A EP 06834549A EP 1978768 A1 EP1978768 A1 EP 1978768A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- wireless
- areas
- wireless area
- service
- loads
- 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.)
- Withdrawn
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/20—Selecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/52—Allocation or scheduling criteria for wireless resources based on load
Definitions
- the present invention relates to a mobile communication system, and more particularly to a mobile communication system for distributing loads on wireless areas to provide services.
- Fig. 1 is a flowchart of a load distribution control process in a mobile communication system.
- the mobile communication system determines whether there is a request for establishing a call or not (step 9901). If there is not a request for establishing a call, then the mobile communication system does not establish a call and puts the process to an end (step 9902).
- the mobile communication system determines whether a plurality of frequencies are permitted or not (step 9903). If a plurality of frequencies are not permitted, then the mobile communication system establishes a call without distributing loads, and finishes the process (step 9904).
- the mobile communication system compares the loads on wireless areas having the frequencies (step 9905). It is assumed that wireless area A and wireless area B are permitted. Wireless area A has load LA and wireless area B has load LB.
- the mobile communication system determines whether a smaller one of LA, LB is equal to LA or not (step 9906). If a smaller one of LA, LB is equal to LA, then the mobile communication system selects wireless area A, and assigns wireless resources thereof to the mobile equipment (step 9907). If a smaller one of LA, LB is not equal to LA, then the mobile communication system selects wireless area B, and assigns wireless resources thereof to the mobile equipment (step 9908).
- the remaining resources of a wireless area having a larger load could possibly be greater than the remaining resources of a wireless area having a smaller load. If a wireless area to be assigned to the mobile equipment is selected based on loads only, then small remaining resources of a wireless area may preferentially be assigned to the mobile equipment. As a result, since the remaining resources of the wireless area are small, the mobile communication system may be unable to accept requests for providing various services from the mobile equipment after it has established an RRC connection.
- a mobile communication system for distributing loads on wireless areas to provide a service to a mobile equipment comprises a wireless base station apparatus and a wireless network controller.
- the wireless base station apparatus provides a plurality of wireless areas on which loads can be distributed.
- the wireless network controller manages loads on the wireless areas provided by the wireless base station apparatus.
- the wireless network controller determines remaining resources of the wireless areas from the loads on the wireless areas, and selects a wireless area to be assigned to the mobile equipment based on the result produced by comparing the remaining resources of the wireless areas.
- a mobile communication system illustrated below employs a CMDA (Code Division Multiple Access) process as a wireless access process, and provides a plurality of services.
- the types of the services include a conversational service, a streaming service, an interactive service, a background service, and a signalling service.
- the conversational service is typified by voice communications and video distributions.
- the streaming service is used for streaming music and images.
- the interactive service is typified by Web browsing.
- the background service is used to distribute mails.
- the signalling service is used for short messages and positional registration.
- a mobile equipment (UE) requests the mobile communication system for a service to be started as an establishment cause.
- Fig. 2 is a block diagram showing the configuration of a mobile communication system according to a first exemplary embodiment.
- the mobile communication system includes a switching system (CN: Core Network) 11, a wireless network controller (RNC: Radio Network Controller) 12, and a wireless base station apparatus (NodeB) 13.
- CN Core Network
- RNC Radio Network Controller
- NodeB wireless base station apparatus
- CN 11, RNC 12, and NodeB 13 are shown one for each, they are usually provided as plural for each.
- CNs 11 are connected to each other for switching operation.
- Each RNC 12 is connected to either one of CNs 11 and accommodates a plurality of NodeBs 13.
- RNC 12 processes calls made through NodeBs 13 accommodated thereby and control wireless resources of each of NodeBs 13.
- Each NodeB 13 is connected to either one of RNCs 12 and is connected to mobile equipments (UE) through wireless links. Under the control of RNC 12, NodeB 13 provides wireless resources to each UE. NodeB 13 provides a plurality of wireless areas having different frequencies. RNC 12 indicates, to NodeB 13, which wireless area is to assign resources to UE. NodeB13 provides the resources of the wireless area indicated by RNC 12 to UE. Though an example in which loads are distributed on wireless areas having different frequencies will be illustrated below, the present invention is not limited to such an example. The present invention is applicable to wireless areas over which loads can be distributed, and is not limited to the frequencies.
- NodeB 13 provides wireless area 41 having frequency F1 and wireless area 42 having frequency F2.
- UE 21 and UE 22 are shown as being connected to wireless area 41, and UE23, UE 24 are shown as being connected to wireless area 42, with UE 25 newly requesting a new connection.
- Fig. 3 is a block diagram of the configuration of the RNC. As shown in Fig. 3 , RNC 12 includes load distributor 31 and load manager 32.
- Load manager 32 manages the load statuses of wireless areas 41, 42 that are covered by NodeB 13.
- the load statuses include loads imposed on respective wireless areas 41, 42.
- load manager 32 indicates the present load statuses of the respective wireless areas to load distributor 31.
- load distributor 31 Based on the load statuses managed by load manager 32, load distributor 31 distributes the loads on wireless areas 41, 42.
- load distributor 31 selects a wireless area to be assigned to UE 25 which has requested a connection for a new service
- load distributor 31 uses the remaining resources of the wireless areas for judgement.
- load distributor 31 judges based on thresholds of the remaining resources which differ from service to service. The thresholds are held by load distributor 31.
- load distributor 31 selects a wireless area to be assigned to new UE 25
- load distributor 31 also uses the information of the service requested by UE 25 for judgement. Specifically, the above thresholds are determined for the respective types of services, and load distributor 31 judges using the threshold for the requested service.
- Fig. 4 is a diagram showing the general concept of a load distribution performed by the mobile communication system according to the first exemplary embodiment.
- UE 25 which is to receive a new service sends service start request S1 to RNC 12 of the mobile communication system.
- RNC 12 Upon receipt of service start request S1, RNC 12 selects a wireless area suitable for establishing a connection to UE 25 from wireless areas 41, 42 that are managed by itself. At this time, load distributor 31 of RNC 12 is triggered by service start request S1 to confirm the load statuses managed by load manager 32.
- load distributor 31 For confirming the load statuses, load distributor 31 requests load manager 32 for information about the present load statuses, as shown in Fig. 3 . In response to the request from load distributor 31, load manager 32 indicates the loads on wireless areas 41, 42 to load distributor 31. Based on the loads indicated by load manager 32, load distributor 31 selects an optimum wireless area.
- RNC 11 indicates information S1 about the wireless area selected by load distribution device 111 to UE 25, indicating that the service can be started in the wireless area.
- UE 25 then establishes a call between itself and RNC 12.
- Fig. 5 is a sequence diagram showing an operation of an UE at the time of starting a service in the mobile communication system according to the first exemplary embodiment.
- UE 25 which is to receive a new service sends an RRC: RRC CONNECTION REQUEST message to RNC 12.
- This message contains information about the contents of the requested service as an establishment cause parameter.
- RNC 12 performs a load distribution process using the establishment cause parameter indicated from UE 25 and the load statuses managed by load manager 32.
- RNC 12 After having selected a wireless area according to the load distribution process, RNC 12 performs a process of establishing an RL (Radio Link) and a process of establishing an ALCP between itself and NodeB 21 in order to establish a call in the wireless area.
- RL Radio Link
- RNC 12 sends an RRC: RRCC CONNECTION SETUP message to UE 25, indicating the wireless area to UE 25.
- UE 25 When UE 25 has received the RRC: RRCC CONNECTION SETUP message, it sends back an RRC: RRCC CONNECTION COMPLETE message to RNC 12, indicating that the establishment of a call in the wireless area is completed.
- Fig. 6 is a flowchart showing an operation sequence of the RNC according to the first exemplary embodiment for a load distribution control process.
- RNC 12 determines whether there is a call establishing request from UE 25 or not (step 101). If there is no call establishing request, then RNC 12 does not establish a call and puts the process to an end (step 102).
- RNC 12 determines whether wireless areas with a plurality of frequencies are permitted or not (step 103). If NodeB 13 managed by RNC 12 provides wireless areas with a plurality of frequencies, then a plurality of wireless areas are permitted.
- RNC 12 does not distribute loads and puts the process to an end (step 104).
- RNC 12 acquires requested service contents (traffic conditions) from the establishment clause parameter contained in the RRC: RRC CONNECTION REQUEST message from UE 25 (step 105), and performs a load distribution control process with respect to the service contents.
- RNC 12 determines whether the service contents (traffic conditions) represent a conversational service or not (step 106). If the service contents (traffic conditions) represent a conversational service, then RNC 12 performs a process for the conversational service (step 107). Details of the process for the conversational service will be described later.
- RNC 12 determines whether the service contents (traffic conditions) represent a streaming service or not (step 108). If the service contents (traffic conditions) represent a streaming service, then RNC 12 performs a process for the streaming service (step 109). Details of the process for the streaming service will be described later.
- RNC 12 determines whether the service contents (traffic conditions) represent an interactive service or not (step 110). If the service contents (traffic conditions) represent an interactive service, then RNC 12 performs a process for the interactive service (step 111). Details of the process for the interactive service will be described later.
- RNC 12 determines whether the service contents (traffic conditions) represent a background service or not (step 112). If the service contents (traffic conditions) represent a background service, then RNC 12 performs a process for the background service (step 113). Details of the process for the background service will be described later.
- RNC 12 performs a process for a signalling service (step 114). Details of the process for the signalling service will be described later.
- Fig. 7 is a flowchart showing a processing sequence for the conversational service according to the first exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the conversational service in wireless areas 41, 42 and the present loads imposed on wireless areas 41, 42 (step 201), and calculates the remaining resources (step 202).
- RNC 12 determines whether a greatest one of R41, R42 is equal to R41 or not (step 203).
- RNC 12 selects wireless area 41 (step 204).
- RNC 12 selects wireless area 42 (step 205).
- Fig. 8 is a flowchart showing a processing sequence for the streaming service according to the first exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the streaming service in wireless areas 41, 42 and the present loads imposed on wireless areas 41, 42 (step 301), and calculates the remaining resources (step 302).
- RNC 12 determines whether a greatest one of R41, R42 is equal to R41 or not (step 303).
- RNC 12 selects wireless area 41 (step 304).
- RNC 12 selects wireless area 42 (step 305).
- Fig. 9 is a flowchart showing a processing sequence for the interactive service according to the first exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the interactive service in wireless areas 41, 42 and the present loads imposed on wireless areas 41, 42 (step 401), and calculates the remaining resources (step 402).
- RNC 12 determines whether a greatest one of R41, R42 is equal to R41 or not (step 403).
- RNC 12 selects wireless area 41 (step 404).
- RNC 12 selects wireless area 42 (step 405).
- Fig. 10 is a flowchart showing a processing sequence for the background service according to the first exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the background service in wireless areas 41, 42 and the present loads imposed on wireless areas 41, 42 (step 501), and calculates the remaining resources (step 502).
- RNC 12 determines whether a greatest one of R41, R42 is equal to R41 or not (step 503).
- RNC 12 selects wireless area 41 (step 504).
- RNC 12 selects wireless area 42 (step 505).
- Fig. 11 is a flowchart showing a processing sequence for the signalling service according to the first exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the signalling service in wireless areas 41, 42 and the present loads imposed on wireless areas 41, 42 (step 601), and calculates the remaining resources (step 602).
- RNC 12 determines whether a greatest one of R41, R42 is equal to R41 or not (step 603).
- RNC 12 selects wireless area 41 (step 604).
- RNC 12 selects wireless area 42 (step 605).
- RNC 12 when RNC 12 accommodating NodeB 13 that provides a plurality of wireless areas assigns wireless resources upon a request from new UE 25, RNC 12 selects a wireless area based on the remaining resources of the wireless areas. Therefore, when the total capacities of the respective wireless areas are different from each other, RNC 12 can select a wireless area according to the appropriate load distribution process.
- RNC 12 accommodating NodeB 13 that provides a plurality of wireless areas assigns wireless resources to new UE 25
- RNC 12 selects a wireless area based on the type of a service requested by UE 25. Therefore, when the properties of respective services are different from each other, RNC 12 can select a wireless area according to the appropriate load distribution process.
- the first exemplary embodiment has illustrated the example in which a UE requests the mobile communication system for a service.
- a second exemplary embodiment an example in which a CN requests the mobile communication system for a service will be illustrated.
- a Configuration of a mobile communication system according to the second exemplary embodiment is the same as the configuration of the system according to the first embodiment shown in Fig. 2 .
- a Configuration of RNC 12 according to the second exemplary embodiment is the same as the configuration of RNC 12 according to the first embodiment shown in Fig. 3 .
- Fig. 12 is a diagram showing the general concept of a load distribution performed by the mobile communication system according to the second exemplary embodiment.
- CN 11 sends service start request S3 to RNC 12 of the mobile communication system.
- RNC 12 selects a wireless area suitable for a load distribution base on the load statuses in the respective wireless areas. Then, a call establishment process (S4) is performed between RNC 12 and UE 25.
- Fig. 13 is a sequence diagram showing an operation of an UE at the time of starting a service in the mobile communication system according to the second exemplary embodiment.
- CN 11 which is to request a service sends an RANAP: RAB ASSIGNMENT REQUEST message to RNC 12.
- This message contains service information (RAB parameter).
- RNC 12 performs a load distribution control process to select an appropriate wireless area based on the RAB parameter indicated by CN 51 and the load statuses managed by load manager 32.
- a sequence for adding RL (NBAP: RL Addition sequence) is performed between RNC 12 and UE 25.
- RRC PHYSICAL CHANNEL RECONFIGURATION sequence
- RNC 12 performs an NBAP: RL Reconfiguration sequence and an ALCAP sequence between itself and NodeB 13.
- RNC 12 also performs an RRC: RADIO BEARER SETUP sequence between itself and UE 25.
- RNC 12 sends an RANAP: RAB ASSIGNMENT RESPONSE message to CN 11, indicating that the establishment of the service is completed.
- RNC 12 Operation of RNC 12 for the load distribution control process according to the second exemplary embodiment is the same as the operation according to the first exemplary embodiment shown in Fig. 6 . However, whereas RNC 12 is triggered by a call establishment request from UE 25 to start operating for the load distribution in Fig. 6 , RNC 12 starts operating for the load distribution based on a request from CN 11 according to the second exemplary embodiment.
- the load distribution control process performed with respect to service contents by RNC 12 according to the second exemplary embodiment is basically the same as the load distribution control process according to the first exemplary embodiment. However, there are some differences because of the three wireless areas. Traffic information is indicated from UE 25 or CN 11 according to a sequence.
- Fig. 14 is a flowchart showing a processing sequence for a conversational service according to the second exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the conversational service in wireless areas 41, 42, 43 and the present loads imposed on wireless areas 41, 42, 43 (step 701), and calculates the remaining resources (step 702).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R41 or not (step 703).
- RNC 12 selects wireless area 41 (step 704).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R42 or not (step 705).
- RNC 12 selects wireless area 42 (step 706).
- RNC 12 selects wireless area 43 (step 707).
- Fig. 15 is a flowchart showing a processing sequence for a streaming service according to the second exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the streaming service in wireless areas 41, 42, 43 and the present loads imposed on wireless areas 41, 42, 43 (step 801), and calculates the remaining resources (step 802).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R41 or not (step 803).
- RNC 12 selects wireless area 41 (step 804).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R42 or not (step 805).
- RNC 12 selects wireless area 42 (step 806).
- RNC 12 selects wireless area 43 (step 807).
- Fig. 16 is a flowchart showing a processing sequence for an interactive service according to the second exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the interactive service in wireless areas 41, 42, 43 and the present loads imposed on wireless areas 41, 42, 43 (step 901), and calculates the remaining resources (step 902).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R41 or not (step 903).
- RNC 12 selects wireless area 41 (step 904).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R42 or not (step 905).
- RNC 12 selects wireless area 42 (step 906).
- RNC 12 selects wireless area 43 (step 907).
- Fig. 17 is a flowchart showing a processing sequence for a background service according to the second exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the background service in wireless areas 41, 42, 43 and the present loads imposed on wireless areas 41, 42, 43 (step 1001), and calculates the remaining resources (step 1002).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R41 or not (step 1003).
- RNC 12 selects wireless area 41 (step 1004).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R42 or not (step 1005).
- RNC 12 selects wireless area 42 (step 1006).
- RNC 12 selects wireless area 43 (step 1007).
- Fig. 18 is a flowchart showing a processing sequence for a signalling service according to the second exemplary embodiment.
- RNC 12 checks the remaining resources of the wireless areas based on the thresholds for loads that permit the signalling service in wireless areas 41, 42, 43 and the present loads imposed on wireless areas 41, 42, 43 (step 1101), and calculates the remaining resources (step 1102).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R41 or not (step 1103).
- RNC 12 selects wireless area 41 (step 1104).
- RNC 12 determines whether a greatest one of R41, R42, R43 is equal to R42 or not (step 1105).
- RNC 12 selects wireless area 42 (step 1106).
- RNC 12 selects wireless area 43 (step 1107).
- RNC 12 accommodating NodeB 13 that provides a plurality of wireless areas assigns wireless resources to UE 25 upon a request from CN 11, RNC 12 selects a wireless area based on the remaining resources of the wireless areas. Therefore, when the total capacities of the respective wireless areas are different from each other, RNC 12 can select a wireless area according to the appropriate load distribution process.
- RNC 12 accommodating NodeB 13 that provides a plurality of wireless areas assigns wireless resources to new UE 25
- RNC 12 selects a wireless area based on the type of a service requested by UE 25. Therefore, when the properties of respective services are different from each other, RNC 12 can select a wireless area according to the appropriate load distribution process.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2006012391 | 2006-01-20 | ||
PCT/JP2006/324794 WO2007083462A1 (fr) | 2006-01-20 | 2006-12-13 | Système de communication mobile, dispositif de commande de réseau sans fil et méthode de répartition de charge |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1978768A1 true EP1978768A1 (fr) | 2008-10-08 |
EP1978768A4 EP1978768A4 (fr) | 2012-10-10 |
Family
ID=38287418
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP06834549A Withdrawn EP1978768A4 (fr) | 2006-01-20 | 2006-12-13 | Système de communication mobile, dispositif de commande de réseau sans fil et méthode de répartition de charge |
Country Status (5)
Country | Link |
---|---|
US (1) | US20100323734A1 (fr) |
EP (1) | EP1978768A4 (fr) |
JP (1) | JP4737459B2 (fr) |
CN (1) | CN101361382B (fr) |
WO (1) | WO2007083462A1 (fr) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102131231A (zh) * | 2011-04-22 | 2011-07-20 | 西安电子科技大学 | 异构网络剩余资源信息的获取方法 |
CN102143510A (zh) * | 2011-03-25 | 2011-08-03 | 西安电子科技大学 | 异构网络间剩余资源的交互方法 |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011035763A (ja) * | 2009-08-04 | 2011-02-17 | Hitachi Ltd | 負荷分散方法および無線基地局制御装置 |
CN102843722B (zh) * | 2011-06-22 | 2018-01-09 | 中兴通讯股份有限公司 | 同覆盖小区负荷信息的同步方法、接入方法及装置 |
US9723536B2 (en) | 2013-01-17 | 2017-08-01 | Avago Technologies General Ip (Singapore) Pte. Ltd. | Wireless communication system utilizing broadcast-based blind offloading |
JP2020053863A (ja) * | 2018-09-27 | 2020-04-02 | Kddi株式会社 | 複数の回線を用いてネットワークと端末装置との間で複製したデータの通信を実行可能なシステムにおけるネットワークノード、制御方法、及びプログラム |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6205335B1 (en) * | 1998-03-20 | 2001-03-20 | Fujitsu Limited | Zone selection method for mobile radio communication system |
US6542742B2 (en) * | 1998-04-01 | 2003-04-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Cell selection in mobile radio systems |
EP1372347A1 (fr) * | 2002-06-11 | 2003-12-17 | NEC Corporation | Système de communication mobile et procédé de répartition de charge de plusieurs fréquences dans ce système |
US20040156334A1 (en) * | 2002-03-29 | 2004-08-12 | Akira Okubo | Radio network system and radio communication control method |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FI109513B (fi) * | 1997-05-13 | 2002-08-15 | Nokia Corp | Solun kuormitukseen perustuva kanavanvaihto matkaviestinjärjestelmässä |
JP3529982B2 (ja) * | 1997-07-16 | 2004-05-24 | 株式会社エヌ・ティ・ティ・ドコモ | 多元トラヒックの呼受付制御方法 |
US6266531B1 (en) * | 1998-07-01 | 2001-07-24 | Ericsson Inc. | System and method for adaptive thresholds for cell load sharing |
US6415153B1 (en) * | 1999-09-29 | 2002-07-02 | Lucent Technologies Inc. | System and method for aggregate overload control |
US6714789B1 (en) * | 2000-09-18 | 2004-03-30 | Sprint Spectrum, L.P. | Method and system for inter-frequency handoff and capacity enhancement in a wireless telecommunications network |
US7224976B2 (en) * | 2000-10-09 | 2007-05-29 | Nokia Corporation | Service priorities in a multi-cell network |
GB2378093B (en) * | 2001-07-27 | 2004-03-24 | Motorola Inc | System,method and transceiver for mobile communications |
US7454213B2 (en) * | 2002-11-08 | 2008-11-18 | Nokia Siemens Networks Oy | Traffic management in radio system |
JP3874720B2 (ja) * | 2002-11-29 | 2007-01-31 | 株式会社東芝 | ソフトハンドオーバ制御方法 |
US20040120286A1 (en) * | 2002-12-23 | 2004-06-24 | Uwe Schwarz | Transmission method, system and radio network controller |
EP1668835A1 (fr) * | 2003-09-30 | 2006-06-14 | Telefonaktiebolaget LM Ericsson (publ) | Procede et dispositif de regulation de congestion dans des reseaux de donnees en rafale sans fil, a grande vitesse |
US7187934B2 (en) * | 2004-12-14 | 2007-03-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for steering idle mobile stations |
US20060142021A1 (en) * | 2004-12-29 | 2006-06-29 | Lucent Technologies, Inc. | Load balancing on shared wireless channels |
-
2006
- 2006-12-13 CN CN2006800515088A patent/CN101361382B/zh not_active Expired - Fee Related
- 2006-12-13 WO PCT/JP2006/324794 patent/WO2007083462A1/fr active Application Filing
- 2006-12-13 US US12/160,414 patent/US20100323734A1/en not_active Abandoned
- 2006-12-13 JP JP2007554827A patent/JP4737459B2/ja not_active Expired - Fee Related
- 2006-12-13 EP EP06834549A patent/EP1978768A4/fr not_active Withdrawn
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6205335B1 (en) * | 1998-03-20 | 2001-03-20 | Fujitsu Limited | Zone selection method for mobile radio communication system |
US6542742B2 (en) * | 1998-04-01 | 2003-04-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Cell selection in mobile radio systems |
US20040156334A1 (en) * | 2002-03-29 | 2004-08-12 | Akira Okubo | Radio network system and radio communication control method |
EP1372347A1 (fr) * | 2002-06-11 | 2003-12-17 | NEC Corporation | Système de communication mobile et procédé de répartition de charge de plusieurs fréquences dans ce système |
Non-Patent Citations (1)
Title |
---|
See also references of WO2007083462A1 * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102143510A (zh) * | 2011-03-25 | 2011-08-03 | 西安电子科技大学 | 异构网络间剩余资源的交互方法 |
CN102143510B (zh) * | 2011-03-25 | 2014-06-18 | 西安电子科技大学 | 异构网络间剩余资源的交互方法 |
CN102131231A (zh) * | 2011-04-22 | 2011-07-20 | 西安电子科技大学 | 异构网络剩余资源信息的获取方法 |
CN102131231B (zh) * | 2011-04-22 | 2013-08-14 | 西安电子科技大学 | 异构网络剩余资源信息的获取方法 |
Also Published As
Publication number | Publication date |
---|---|
EP1978768A4 (fr) | 2012-10-10 |
US20100323734A1 (en) | 2010-12-23 |
CN101361382B (zh) | 2013-10-23 |
CN101361382A (zh) | 2009-02-04 |
JPWO2007083462A1 (ja) | 2009-06-11 |
WO2007083462A1 (fr) | 2007-07-26 |
JP4737459B2 (ja) | 2011-08-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR100801132B1 (ko) | 무선 통신 시스템에서 시 분할 듀플렉스 및 주파수 분할 듀플렉스 사이의 자원 할당을 통합하는 방법 및 시스템 | |
JP4382348B2 (ja) | マルチセルネットワークにおけるサービスプライオリティ | |
US8787159B2 (en) | Mechanism for wireless access networks to throttle traffic during congestion | |
US6125276A (en) | Inter-exchange signaling for in-call service change requests | |
CN1951028B (zh) | 用于无线通信系统中射频频带分配的方法和设备 | |
KR20010062293A (ko) | 개선된 모빌 대 모빌 콜 방법 | |
EP1978768A1 (fr) | Système de communication mobile, dispositif de commande de réseau sans fil et méthode de répartition de charge | |
KR100971067B1 (ko) | 셀룰러 통신 시스템의 무선 베어러 관리 | |
US20080101243A1 (en) | Communication Apparatus, Communication System and Communication Method | |
KR100790074B1 (ko) | 휴대단말기의 호 연결방법 | |
KR20060127150A (ko) | 이동 가입자망, 및 리소스 관리 방법 | |
KR100833639B1 (ko) | 무선 통신 시스템에서 시 분할 듀플렉스 및 주파수 분할듀플렉스 사이의 자원 배당을 통합하는 방법 및 시스템 | |
KR100688437B1 (ko) | 통신 시스템의 용량 관리를 위한 장치 및 방법 | |
JP5953171B2 (ja) | 通信方法および通信システム | |
EP1718099A2 (fr) | Procédé de contrôle de priorité de service dans un réseau de communication radio, système de radio-communication, équipement de contrôle radio, équipement terminal et réseau coeur | |
JP4484367B2 (ja) | 移動システム及び移動システムのベースステーションにおけるチャンネル割り当て方法及び装置 | |
EP1838043A2 (fr) | contrôleur de réseau de radio avec méthode d'allocation de canal | |
JP2003224882A (ja) | Cdma移動通信システムおよびその記録媒体 | |
US20120099528A1 (en) | Radio network control device, packet switching device, circuit switching device, and information reporting method | |
CN101242632B (zh) | 一种分配专有信道的方法和基站设备 | |
JP2009206641A (ja) | 移動通信システム及び無線基地局制御装置 | |
US7107037B1 (en) | Reserving channel elements to maximize utilization of resources and prevent blocking of calls | |
KR100866778B1 (ko) | 호 처리를 위한 중계선의 자원 할당 방법, 시스템 및 장치 | |
CN115915482A (zh) | 会话建立方法及设备 | |
KR20020051698A (ko) | 무선 자원 할당 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20080721 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): DE FI GB SE |
|
RBV | Designated contracting states (corrected) |
Designated state(s): DE FI GB SE |
|
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20120912 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 48/20 20090101AFI20120906BHEP |
|
17Q | First examination report despatched |
Effective date: 20170207 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20170620 |