WO2009095070A1 - Interface between rnc and node b (a-interface) using ip or tdm - Google Patents

Interface between rnc and node b (a-interface) using ip or tdm Download PDF

Info

Publication number
WO2009095070A1
WO2009095070A1 PCT/EP2008/050968 EP2008050968W WO2009095070A1 WO 2009095070 A1 WO2009095070 A1 WO 2009095070A1 EP 2008050968 W EP2008050968 W EP 2008050968W WO 2009095070 A1 WO2009095070 A1 WO 2009095070A1
Authority
WO
WIPO (PCT)
Prior art keywords
protocol type
user plane
base station
plane protocol
station subsystem
Prior art date
Application number
PCT/EP2008/050968
Other languages
French (fr)
Inventor
Jukka Rantanen
Kati Vainola
Original Assignee
Nokia Siemens Networks Oy
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 Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2008/050968 priority Critical patent/WO2009095070A1/en
Publication of WO2009095070A1 publication Critical patent/WO2009095070A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the present invention relates to mobile communication network systems and their transmission technology migration.
  • the invention relates to migration to IP (Internet Protocol) technology, for example the migration to A-interface over IP.
  • IP Internet Protocol
  • BSS Base Station Subsystem
  • Gb-interface and A-interface over IP.
  • Gb- interface over IP has been standardised in 3GPP Release 4, and for A-interface over IP, control plane signalling over IP
  • A-interface over IP can also simplify implementation of Multipoint A feature in a pooled network.
  • UTRAN Universal Mobile Telecommunications System
  • GERAN GSM (Global System for Mobile communication) Edge (Enhanced Data rates for Global Evolution) Radio Access Network
  • the invention aims at providing a smooth migration between transmission technologies in a mobile communication system.
  • GSM Global System for Mobile communication
  • AoTDM A-interface over TDM
  • Enhanced GSM architecture with flexible IP transmission enables to continue GSM networks and services in an optimised way.
  • more capacity can be achieved by optimal routing, congestions can be reduced which results in better customer satisfaction, enhanced features such as TrFO (Transcoder Free Operation) can be used which results in better quality and customer satisfaction, network maintenance is facilitated and less network elements may be needed.
  • TrFO Transcoder Free Operation
  • the migration solution presented in the embodiment utilizes existing BSS and MSS/MGW (Media Gateway) functionality as much as possible.
  • MSS/MGW Media Gateway
  • a device can act as a client entity or as a server entity in terms of the present invention, or may even have both functionalities integrated therein;
  • - method steps and/or devices likely to be implemented as hardware components at one of the server / client entities are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS, CMOS, BiCMOS, ECL, TTL, etc, using for example ASIC components or DSP components, as an example;
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention
  • - devices can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved.
  • Fig. 1 shows a schematic diagram illustrating an AoIP migration example in a mobile communication system according to an embodiment of the invention.
  • Fig. 2 shows a signalling diagram illustrating signalling between a BSS and an MSS according to an embodiment of the invention .
  • Fig. 3 shows a schematic block diagram illustrating a structure of a BSS device and an MSS device according to an embodiment of the invention.
  • Fig. 1 shows a schematic diagram illustrating an AoIP migration example in a mobile communication system according to an embodiment of the invention.
  • the mobile communication system comprises a BSS (Base Station Subsystem) 10 and an MSS
  • the BSS 10 comprises a BSC (Base Station Controller) 11 and a plurality of BTSs (Base Transceiver Stations) 12a, 12b, 12c.
  • the MSS 20 comprises an MSC server 21 and a multimedia gateway 22. Control plane signalling between the MSS 20 (MSC server 21) and the BSS 10 (BSC 11) is performed via a BSSAP (Base Station System Application Part) over SIGTRAN (Signalling Transport) interface 1, and user plane transmission between the MSS 20
  • BSSAP Base Station System Application Part
  • SIGTRAN Simalling Transport
  • multimedia gateway 22 and the BSS 10 (BSC 11) is performed over an IP based A-interface 2 and may be performed also over a TDM based A-interface 3.
  • Communication between the MSC server 21 and the multimedia gateway 22 is performed over an H.248 interface 4.
  • the BSS 10 comprises separate internal hardware for AoIP and AoTDM interfaces 2, 3. Transcoding functionality when AoTDM is in use is located in the BSS 10, and A-interface circuits and circuit pools (not shown) for AoTDM are supported at the BSS 10 and MSS 20.
  • the MSS 20 is provided with information which A-interface types the BSS 10 supports.
  • the MSS 20 can be configured with this information via interface 1 in a BSSAP parameter indicating "AoIP only" or "AoIP/AoTDM" .
  • the MSS 20 may be preconfigured with the information on whether the BSS 10 supports IP based A- interface 2 only or both IP based A-interface 2 and TDM based A-interface 3. This information may be stored in a memory (not shown) in the MSS 20.
  • the BSS support for AoIP and/or AoTDM is also signalled via BSSAP.
  • Fig. 2 shows a signalling diagram illustrating signalling between the BSS 10 and the MSS 20 according to an embodiment of the invention.
  • the MSS 20 is provided with BSS capabilities information on whether the BSS 10 supports AoIP interface only or both AoIP interface and AoTDM interface. As described above, this information may be sent from the BSS 10 to the MSS 20 via BSSAP over SIGTRAN interface 1 using a BSSAP parameter. Alternatively, the information may be preconfigured in the MSS 20 as described above.
  • the MSS 20 determines capabilities of the BSS 10 based on the BSS capabilities information.
  • AoIP is preferred for the connection at A-interface.
  • the MSS 20 transmits a message to the BSS 10 which requests a user plane connection according to AoIP. This message may be sent in assignment request and handover messages via BSSAP over SIGTRAN interface 1.
  • the BSS 10 that supports both AoTDM and AoIP processes the message and may decide that AoIP should not be used, e.g. in case the BSS 10 cannot provide AoIP resources for the connection.
  • the BSS 10 transmits a message to the MSS 20, which indicates to the MSS 20 that AoIP should not be used, in order to use AoTDM for the user plane connection. This may be done via known BSSAP signalling in which the BSS 10 indicates in an assignment failure or handover failure message that switching of circuit pool is required.
  • step 206 the MSS 20 processes the failure message received from the BSS 10.
  • the MSS 20 transmits a assignment/handover request message with AoTDM resource in step 207.
  • the BSS 10 performs user plane connection via AoTDM.
  • the BSS 10 if, on reception by the BSS 10 of an assignment/handover request message requesting a connection according to a determined user plane protocol type, the BSS 10 wishes to change the user plane protocol type, it sends an assignment/handover failure with a cause "switch circuit pool” and a "circuit pool list” information element.
  • the "circuit pool list” information element when present in the assignment failure, is used when the BSS 10 wishes to indicate to the MSC 20 its preferred circuit pools.
  • the circuit pools in the "circuit pool list” information element may be given in order of preference.
  • the MSS 20 is provided with the configurable information about BSS capabilities, i.e. if the BSS 10 supports AoIP or both AoIP and AoTDM.
  • the BSS 10 can trigger switching of circuit pool also in case when an assignment request is received with AoIP related information (e.g. IP port and UDP (User Datagram Protocol) address) but the BSS 10 cannot provide AoIP resources, e.g. during temporary exceed of IP resources .
  • AoIP related information e.g. IP port and UDP (User Datagram Protocol) address
  • vendor specific and operator configurable algorithms may be implemented to provide optimal AoIP versus AoTDM resource reservation rate per each BSS in the MSS. For example, depending on the IP resource versus TDM resource configuration at the BSS, the operator may choose to reserve for 2/3 rd of the connections AoIP resource and for l/3 rd AoTDM resource.
  • Fig. 3 shows a schematic block diagram illustrating a structure of a BSS device 100 and an MSS device 200 according to an embodiment of the invention.
  • the BSS 10 shown in Fig. 1 comprises the BSS device 100
  • the MSS 20 shown in Fig. 1 comprises the MSS device 200.
  • the BSS device 100 comprises a receiver 131, a processor 132 and a transmitter 133 which are connected via an internal bus 134.
  • the MSS device 200 comprises a receiver 231, a processor 232 and a transmitter 233 which are connected via an internal bus 234.
  • the BSS device 100 and the MSS device 200 communicate with each other via an interface 301, e.g. the BSSAP over SIGTRAN interface 1 (Fig. 1) .
  • the processor 132 and the processor 232 each may comprise an internal memory (not shown) into which an application program can be loaded and which may function as a working area when the program is executed.
  • the processor 232 of the MSS device 200 determines a user plane protocol type based on information on capabilities of the BSS device 100, and causes the transmitter 233 to transmit a message to the BSS device 100 which requests a connection according to the determined user plane protocol type, e.g. AoIP.
  • the processor 232 may initially determine a first user plane protocol type (e.g. an Internet protocol type) as the determined user plane protocol type in case the information on the capabilities of the base station subsystem comprises information that the base station subsystem supports the first user plane protocol type and a second user plane protocol type (e.g. a time division multiplexing protocol type).
  • a first user plane protocol type e.g. an Internet protocol type
  • a second user plane protocol type e.g. a time division multiplexing protocol type
  • the receiver 231 may receive the information on the capabilities of the BSS device 100, which may have been prepared by the processor 132 of the BSS device 100, from the transmitter 133 of the BSS device 100.
  • the MSS device 200 or the MSS 20 may comprise a memory (not shown) storing configurable information about BSS capabilities, and the processor 232 may retrieve the information on the capabilities of the BSS device 100 from the memory.
  • the receiver 131 of the BSS device 100 receives the message which requests the connection according to the determined (first) user plane protocol type.
  • the processor 132 of the BSS device 100 processes the message, and decides whether to switch to another (second) user plane protocol type, e.g. AoTDM, for the connection, and causes the transmitter 133 to transmit a response message to the MSS device 200, which indicates switching to the second user plane protocol type, in case the processor 132 decides to switch to the second user plane protocol type.
  • second user plane protocol type
  • the receiver 231 of the MSS device 200 may receive the response message from the BSS device 100 which indicates switching to the second user plane protocol type, and the processor 232 may cause the transmitter 233 to send a message to the BSS device 100, which requests the connection according to the second user plane protocol type.
  • a first user plane protocol type is determined by a mobile switching centre server system based on information on capabilities of a base station subsystem.
  • a request message is transmitted to the base station subsystem, which requests a connection according to the determined first user plane protocol type.
  • the request message is processed by the base station subsystem and it is decided whether to switch to a second user plane protocol type for the connection.
  • a response message is transmitted to the mobile switching centre server system, which indicates switching to the second user plane protocol type.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A first user plane protocol type is determined by a mobile switching centre server system based on information on capabilities of a base station subsystem. A request message is transmitted to the base station subsystem, which requests a connection according to the determined first user plane protocol type. The request messageis processed by the base station subsystem and it is decided whether to switch to a second user plane protocol type for the connection. In case it is decided to switch to the second user plane protocol type, a response message is transmitted to the mobile switching centre server system, which indicates switching to the second user plane protocol type.

Description

TITLE OF THE INVENTION
INTERFACE BETWEEN RNC AND NODE B (A-INTERFACE) USING IP OR TDM
FIELD AND BACKGROUND OF THE INVENTION
The present invention relates to mobile communication network systems and their transmission technology migration. In particular, the invention relates to migration to IP (Internet Protocol) technology, for example the migration to A-interface over IP.
In mobile communication networks, many domains and interfaces between these domains have been adapted to IP technology.
BSS (Base Station Subsystem) over IP is a technique trend in wireless network evolution, which can construct high bandwidth, high efficiency and low cost basic networks. BSS over IP involves Gb-interface and A-interface over IP. Gb- interface over IP has been standardised in 3GPP Release 4, and for A-interface over IP, control plane signalling over IP
(SIGTRAN) has been introduced in 3GPP Release 7. However, the user plane of the A-interface is still solely based on TDM
(Time Division Multiplexing) transmission technology.
In order to take full advantage of IP based technologies, protocols of A-interface user plane should be adapted for IP based transport. One of the main advantages of having IP based A-interface also for the user plane is a much more flexible network design between the BSS and the CS (Circuit Switched) core network. The A-interface over IP (AoIP) can also simplify implementation of Multipoint A feature in a pooled network. Furthermore, UTRAN (UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network) and more advanced RAN (Radio Access Network) can use a common IP backhaul with GERAN (GSM (Global System for Mobile communication) Edge (Enhanced Data rates for Global Evolution) Radio Access Network) .
For AoIP, different solution alternatives have been proposed, e.g. in 3GPP AoIP TR.
SUMMARY OF THE INVENTION
The invention aims at providing a smooth migration between transmission technologies in a mobile communication system.
This is achieved by the apparatuses and methods as defined in the appended claims. The invention may also be implemented as a computer program product.
According to an embodiment of the invention, smooth migration to A-interface over IP is provided.
There is a large amount of existing GSM (Global System for Mobile communication) networks with TDM based A-interface. According to an embodiment of the invention, migration scenarios are allowed where a BSS supports simultaneously both AoIP and AoTDM (A-interface over TDM) .
Enhanced GSM architecture with flexible IP transmission enables to continue GSM networks and services in an optimised way. In particular, more capacity (simultaneous calls) can be achieved by optimal routing, congestions can be reduced which results in better customer satisfaction, enhanced features such as TrFO (Transcoder Free Operation) can be used which results in better quality and customer satisfaction, network maintenance is facilitated and less network elements may be needed.
According to an embodiment of the invention, a generic principle for smooth migration from AoTDM to AoIP is described. The migration solution presented in the embodiment utilizes existing BSS and MSS/MGW (Media Gateway) functionality as much as possible.
For the purpose of the present invention to be described herein below, it should be noted that
- a device can act as a client entity or as a server entity in terms of the present invention, or may even have both functionalities integrated therein;
- method steps likely to be implemented as software code portions and being run using a processor at one of the server / client entities are software code independent and can be specified using any known or future developed programming language;
- method steps and/or devices likely to be implemented as hardware components at one of the server / client entities are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS, CMOS, BiCMOS, ECL, TTL, etc, using for example ASIC components or DSP components, as an example;
- generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention;
- devices can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 shows a schematic diagram illustrating an AoIP migration example in a mobile communication system according to an embodiment of the invention.
Fig. 2 shows a signalling diagram illustrating signalling between a BSS and an MSS according to an embodiment of the invention . Fig. 3 shows a schematic block diagram illustrating a structure of a BSS device and an MSS device according to an embodiment of the invention.
DESCRIPTION OF THE INVENTION
In the following the invention will be described by way of embodiments thereof with reference to the accompanying drawings .
Fig. 1 shows a schematic diagram illustrating an AoIP migration example in a mobile communication system according to an embodiment of the invention. The mobile communication system comprises a BSS (Base Station Subsystem) 10 and an MSS
(MSC (Mobile Switching Centre) Server System) 20. The BSS 10 comprises a BSC (Base Station Controller) 11 and a plurality of BTSs (Base Transceiver Stations) 12a, 12b, 12c. The MSS 20 comprises an MSC server 21 and a multimedia gateway 22. Control plane signalling between the MSS 20 (MSC server 21) and the BSS 10 (BSC 11) is performed via a BSSAP (Base Station System Application Part) over SIGTRAN (Signalling Transport) interface 1, and user plane transmission between the MSS 20
(multimedia gateway 22) and the BSS 10 (BSC 11) is performed over an IP based A-interface 2 and may be performed also over a TDM based A-interface 3. Communication between the MSC server 21 and the multimedia gateway 22 is performed over an H.248 interface 4.
The BSS 10 comprises separate internal hardware for AoIP and AoTDM interfaces 2, 3. Transcoding functionality when AoTDM is in use is located in the BSS 10, and A-interface circuits and circuit pools (not shown) for AoTDM are supported at the BSS 10 and MSS 20.
The MSS 20 is provided with information which A-interface types the BSS 10 supports. For example, the MSS 20 can be configured with this information via interface 1 in a BSSAP parameter indicating "AoIP only" or "AoIP/AoTDM" . Alternatively, the MSS 20 may be preconfigured with the information on whether the BSS 10 supports IP based A- interface 2 only or both IP based A-interface 2 and TDM based A-interface 3. This information may be stored in a memory (not shown) in the MSS 20. In addition, it is possible that the BSS support for AoIP and/or AoTDM is also signalled via BSSAP.
Fig. 2 shows a signalling diagram illustrating signalling between the BSS 10 and the MSS 20 according to an embodiment of the invention.
In a step 201 the MSS 20 is provided with BSS capabilities information on whether the BSS 10 supports AoIP interface only or both AoIP interface and AoTDM interface. As described above, this information may be sent from the BSS 10 to the MSS 20 via BSSAP over SIGTRAN interface 1 using a BSSAP parameter. Alternatively, the information may be preconfigured in the MSS 20 as described above.
In case a user plane transmission has to be performed between the MSS 20 and the BSS 10, in a step 202, the MSS 20 determines capabilities of the BSS 10 based on the BSS capabilities information. When the MSS 20 determines that the BSS 10 supports both AoTDM and AoIP, according to an embodiment of the invention AoIP is preferred for the connection at A-interface. In step 203 the MSS 20 transmits a message to the BSS 10 which requests a user plane connection according to AoIP. This message may be sent in assignment request and handover messages via BSSAP over SIGTRAN interface 1.
In a step 204 the BSS 10 that supports both AoTDM and AoIP processes the message and may decide that AoIP should not be used, e.g. in case the BSS 10 cannot provide AoIP resources for the connection. In step 205 the BSS 10 transmits a message to the MSS 20, which indicates to the MSS 20 that AoIP should not be used, in order to use AoTDM for the user plane connection. This may be done via known BSSAP signalling in which the BSS 10 indicates in an assignment failure or handover failure message that switching of circuit pool is required.
In step 206 the MSS 20 processes the failure message received from the BSS 10. In response to the request to switch circuit pool indicated in the failure message, the MSS 20 transmits a assignment/handover request message with AoTDM resource in step 207. In step 208 the BSS 10 performs user plane connection via AoTDM.
According to the embodiment, if, on reception by the BSS 10 of an assignment/handover request message requesting a connection according to a determined user plane protocol type, the BSS 10 wishes to change the user plane protocol type, it sends an assignment/handover failure with a cause "switch circuit pool" and a "circuit pool list" information element.
The "circuit pool list" information element, when present in the assignment failure, is used when the BSS 10 wishes to indicate to the MSC 20 its preferred circuit pools. The circuit pools in the "circuit pool list" information element may be given in order of preference.
According to the embodiment, the MSS 20 is provided with the configurable information about BSS capabilities, i.e. if the BSS 10 supports AoIP or both AoIP and AoTDM.
According to the embodiment, the BSS 10 can trigger switching of circuit pool also in case when an assignment request is received with AoIP related information (e.g. IP port and UDP (User Datagram Protocol) address) but the BSS 10 cannot provide AoIP resources, e.g. during temporary exceed of IP resources . Depending on an IP utilization rate at the A-interface, vendor specific and operator configurable algorithms may be implemented to provide optimal AoIP versus AoTDM resource reservation rate per each BSS in the MSS. For example, depending on the IP resource versus TDM resource configuration at the BSS, the operator may choose to reserve for 2/3rd of the connections AoIP resource and for l/3rd AoTDM resource.
Fig. 3 shows a schematic block diagram illustrating a structure of a BSS device 100 and an MSS device 200 according to an embodiment of the invention.
The BSS 10 shown in Fig. 1 comprises the BSS device 100, and the MSS 20 shown in Fig. 1 comprises the MSS device 200.
The BSS device 100 comprises a receiver 131, a processor 132 and a transmitter 133 which are connected via an internal bus 134. The MSS device 200 comprises a receiver 231, a processor 232 and a transmitter 233 which are connected via an internal bus 234. The BSS device 100 and the MSS device 200 communicate with each other via an interface 301, e.g. the BSSAP over SIGTRAN interface 1 (Fig. 1) . The processor 132 and the processor 232 each may comprise an internal memory (not shown) into which an application program can be loaded and which may function as a working area when the program is executed.
The processor 232 of the MSS device 200 determines a user plane protocol type based on information on capabilities of the BSS device 100, and causes the transmitter 233 to transmit a message to the BSS device 100 which requests a connection according to the determined user plane protocol type, e.g. AoIP. The processor 232 may initially determine a first user plane protocol type (e.g. an Internet protocol type) as the determined user plane protocol type in case the information on the capabilities of the base station subsystem comprises information that the base station subsystem supports the first user plane protocol type and a second user plane protocol type (e.g. a time division multiplexing protocol type).
The receiver 231 may receive the information on the capabilities of the BSS device 100, which may have been prepared by the processor 132 of the BSS device 100, from the transmitter 133 of the BSS device 100. Alternatively or in addition, the MSS device 200 or the MSS 20 may comprise a memory (not shown) storing configurable information about BSS capabilities, and the processor 232 may retrieve the information on the capabilities of the BSS device 100 from the memory.
The receiver 131 of the BSS device 100 receives the message which requests the connection according to the determined (first) user plane protocol type. The processor 132 of the BSS device 100 processes the message, and decides whether to switch to another (second) user plane protocol type, e.g. AoTDM, for the connection, and causes the transmitter 133 to transmit a response message to the MSS device 200, which indicates switching to the second user plane protocol type, in case the processor 132 decides to switch to the second user plane protocol type.
The receiver 231 of the MSS device 200 may receive the response message from the BSS device 100 which indicates switching to the second user plane protocol type, and the processor 232 may cause the transmitter 233 to send a message to the BSS device 100, which requests the connection according to the second user plane protocol type.
According to an embodiment of the invention, a first user plane protocol type is determined by a mobile switching centre server system based on information on capabilities of a base station subsystem. A request message is transmitted to the base station subsystem, which requests a connection according to the determined first user plane protocol type. The request message is processed by the base station subsystem and it is decided whether to switch to a second user plane protocol type for the connection. In case it is decided to switch to the second user plane protocol type, a response message is transmitted to the mobile switching centre server system, which indicates switching to the second user plane protocol type.
It is to be understood that the above description is illustrative of the invention and is not to be construed as limiting the invention. Various modifications and applications may occur to those skilled in the art without departing from the true spirit and scope of the invention as defined by the appended claims.

Claims

Cl aims :
1. An apparatus, comprising: a processor configured to determine a user plane protocol type based on information on capabilities of a base station subsystem; and a transmitter, wherein the processor is configured to cause the transmitter to transmit a message to the base station subsystem, which requests a connection according to the determined user plane protocol type.
2. The apparatus of claim 1, wherein the processor is configured to initially determine a first user plane protocol type as the determined user plane protocol type in case the information on the capabilities of the base station subsystem comprises information that the base station subsystem supports the first user plane protocol type and a second user plane protocol type.
3. The apparatus of claim 2, wherein the first user plane protocol type comprises an Internet protocol type and the second user plane protocol type comprises a time division multiplexing protocol type.
4. The apparatus of claim 2, comprising: a receiver configured to receive a response message which indicates switching to the second user plane protocol type, and the processor is configured to cause the transmitter to send a message to the base station subsystem, which requests the connection according to the second user plane protocol type.
5. The apparatus of claim 1, comprising: a receiver configured to receive the information on the capabilities of the base station subsystem.
6. The apparatus of claim 1, comprising: a memory storing configurable information about base station system capabilities, wherein the processor is configured to retrieve the information on the capabilities of the base station subsystem from the memory.
7. The apparatus of claim 1, wherein the user plane protocol type is to be used on an interface between a mobile switching centre server system and the base station subsystem and comprises at least one of an Internet protocol type and a time division multiplexing protocol type.
8. The apparatus of claim 1, wherein the transmitter is configured to transmit the message via a control plane signalling over Internet protocol.
9. The apparatus of claim 1, wherein the message comprises at least one of an assignment request message and a handover request message.
10. The apparatus of claim 5, wherein the receiver is configured to receive the information via a control plane signalling over Internet protocol.
11. The apparatus of claim 1, wherein the information on the capabilities of the base station subsystem comprises information on whether the user plane protocol type supported by the base station subsystem comprises the Internet protocol type or both the Internet protocol type and a time division multiplexing protocol type.
12. The apparatus of claim 1, wherein the processor is configured to determine the user plane protocol type based on the information on the capabilities of the base station subsystem and a user plane protocol type reservation rate of the base station subsystem.
13. An apparatus, comprising: a processor configured to process a request message which requests a connection according to a first user plane protocol type, and decide whether to switch to a second user plane protocol type for the connection; and a transmitter, wherein the processor is configured to cause the transmitter to transmit a response message to a mobile switching centre server system, which indicates switching to the second user plane protocol type, in case the processor decides to switch to the second user plane protocol type.
14. The apparatus of claim 13, wherein the first user plane protocol type is an Internet protocol type and the second user plane protocol type is a time division multiplexing protocol type.
15. The apparatus of claim 13, wherein the response message comprises at least one of an assignment failure message and a handover failure message.
16. The apparatus of claim 13, wherein the processor is configured to include in the response message information on circuit pools.
17. The apparatus of claim 13, wherein the transmitter is configured to transmit the response message via a control plane signalling over Internet protocol.
18. The apparatus of claim 13, comprising: a receiver configured to receive the request message via a control plane signalling over Internet protocol.
19. The apparatus of claim 13, wherein the processor is configured to prepare information on capabilities of a base station subsystem and cause the transmitter to transmit the information to the mobile switching centre server system.
20. The apparatus of claim 19, wherein the information on the capabilities of the base station subsystem comprises information on whether the first user plane protocol type is supported by the base station subsystem or the first and second user plane protocol types are supported by the base station subsystem.
21. An apparatus, comprising: processing means for determining a user plane protocol type based on information on capabilities of a base station subsystem; and transmitting means, the processing means causing the transmitting means to transmit a message to the base station subsystem, which requests a connection according to the determined user plane protocol type.
22. An apparatus, comprising: processing means for processing a request message which requests a connection according to a first user plane protocol type, and deciding whether to switch to a second user plane protocol type for the connection; and transmitting means, the processing means causing the transmitting means to transmit a response message to a mobile switching centre server system, which indicates switching to the second user plane protocol type, in case the processing means decides to switch to the second user plane protocol type.
23. A method, comprising: determining a user plane protocol type based on information on capabilities of a base station subsystem; and transmitting a message to the base station subsystem, which requests a connection according to the determined user plane protocol type.
24. The method of claim 23, wherein the determining comprises initially determining a first user plane protocol type as the determined user plane protocol type in case the information on the capabilities of the base station subsystem comprises information that the base station subsystem supports the first user plane protocol type and a second user plane protocol type.
25. The method of claim 24, wherein the first user plane protocol type comprises an Internet protocol type and the second user plane protocol type comprises a time division multiplexing protocol type.
26. The method of claim 24, comprising: receiving a response message which indicates switching to the second user plane protocol type; and transmitting a message to the base station subsystem, which requests the connection according to the second user plane protocol type.
27. The method of claim 23, comprising: receiving the information on the capabilities of the base station subsystem.
28. The method of claim 23, comprising: retrieving the information on the capabilities of the base station subsystem from a memory storing configurable information about base station system capabilities.
29. The method of claim 23, wherein the user plane protocol type is to be used on an interface between a mobile switching centre server system and the base station subsystem and comprises at least one of an Internet protocol type and a time division multiplexing protocol type.
30. The method of claim 23, comprising: transmitting the message via a control plane signalling over Internet protocol.
31. The method of claim 23, wherein the message comprises at least one of an assignment request message and a handover request message.
32. The method of claim 27, comprising: receiving the information via a control plane signalling over Internet protocol.
33. The method of claim 23, wherein the information on the capabilities of the base station subsystem comprises information on whether the user plane protocol type supported by the base station subsystem comprises the Internet protocol type or both the Internet protocol type and a time division multiplexing protocol type.
34. The method of claim 23, the determining comprising determining the user plane protocol type based on the information on the capabilities of the base station subsystem and a user plane protocol type reservation rate of the base station subsystem.
35. A method, comprising: processing a request message which requests a connection according to a first user plane protocol type; deciding whether to switch to a second user plane protocol type for the connection; and transmitting a response message to a mobile switching centre server system, which indicates switching to the second user plane protocol type, in case it is decided to switch to the second user plane protocol type.
36. The method of claim 35, wherein the first user plane protocol type is an Internet protocol type and the second user plane protocol type is a time division multiplexing protocol type.
37. The method of claim 35, wherein the response message comprises at least one of an assignment failure message and a handover failure message.
38. The method of claim 35, comprising: including in the response message information on circuit pools .
39. The method of claim 35, comprising: transmitting the response message via a control plane signalling over Internet protocol.
40. The method of claim 35, comprising: receiving the request message via a control plane signalling over Internet protocol.
41. The method of claim 35, comprising: preparing information on capabilities of a base station subsystem and transmitting the information to the mobile switching centre server system.
42. The method of claim 41, wherein the information on the capabilities of the base station subsystem comprises information on whether the first user plane protocol type is supported by the base station subsystem or the first and second user plane protocol types are supported by the base station subsystem.
43. A computer program product including a program for a processor, comprising software code portions for performing the method of any one of claims 23 to 42 when the program is run on the processor.
44. The computer program product according to claim 43, wherein the computer program product comprises a computer- readable medium on which the software code portions are stored.
45. The computer program product according to claim 43, wherein the program is directly loadable into an internal memory of the processor.
PCT/EP2008/050968 2008-01-28 2008-01-28 Interface between rnc and node b (a-interface) using ip or tdm WO2009095070A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2008/050968 WO2009095070A1 (en) 2008-01-28 2008-01-28 Interface between rnc and node b (a-interface) using ip or tdm

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2008/050968 WO2009095070A1 (en) 2008-01-28 2008-01-28 Interface between rnc and node b (a-interface) using ip or tdm

Publications (1)

Publication Number Publication Date
WO2009095070A1 true WO2009095070A1 (en) 2009-08-06

Family

ID=40044058

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2008/050968 WO2009095070A1 (en) 2008-01-28 2008-01-28 Interface between rnc and node b (a-interface) using ip or tdm

Country Status (1)

Country Link
WO (1) WO2009095070A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011088892A1 (en) * 2010-01-20 2011-07-28 Nokia Siemens Networks Oy A method for selecting an a-interface resource in a mobile communication system
CN105792266A (en) * 2014-12-25 2016-07-20 北京神州泰岳软件股份有限公司 Base station automatic cutting-connecting method and device
CN113228715A (en) * 2018-12-28 2021-08-06 中兴通讯股份有限公司 Configuring user plane functionality for a wireless system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1868395A1 (en) * 2006-05-26 2007-12-19 NEC Corporation Network selection

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1868395A1 (en) * 2006-05-26 2007-12-19 NEC Corporation Network selection

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project;Technical Specification Group GERAN;A-interface over IP Study (AINTIP);(Release 8)", 3GPP DRAFT; 43903-002, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. tsg_geran\TSG_GERAN\GERAN_36_Vancouver\Docs, no. Vancouver; 20071112, 14 November 2007 (2007-11-14), XP050018929 *
ERICSSON: "AoIP Inter and Intra BSC Handover", 3GPP TSG GERAN2 MEETING #35BIS, G2-070307, SOPHIA ANTIPOLIS, FRANCE, no. 35BIS, 8 October 2007 (2007-10-08), pages 1 - 5, XP002479267 *
TELEFON AN LM ERICSSON: "AOIP call control signalling, 3GPP TSG GERAN2, Meeting #35bis, G2-070333", 10 October 2007 (2007-10-10) - 10 October 2007 (2007-10-10), Sophia Antipolis, France, pages 1 - 11, XP002507021, Retrieved from the Internet <URL:www.3gpp.org> [retrieved on 20081204] *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011088892A1 (en) * 2010-01-20 2011-07-28 Nokia Siemens Networks Oy A method for selecting an a-interface resource in a mobile communication system
CN102792768A (en) * 2010-01-20 2012-11-21 诺基亚西门子通信公司 A method for selecting an A-interface resource in a mobile communication system
US8873492B2 (en) 2010-01-20 2014-10-28 Nokia Siemens Networks Oy Method for selecting an A-interface resource in a mobile communication system
CN102792768B (en) * 2010-01-20 2016-07-06 诺基亚通信公司 For the method selecting the A interface resource in mobile communication system
CN105792266A (en) * 2014-12-25 2016-07-20 北京神州泰岳软件股份有限公司 Base station automatic cutting-connecting method and device
CN113228715A (en) * 2018-12-28 2021-08-06 中兴通讯股份有限公司 Configuring user plane functionality for a wireless system
CN113228715B (en) * 2018-12-28 2023-08-22 中兴通讯股份有限公司 Wireless communication method, apparatus and computer readable medium
US11882476B2 (en) 2018-12-28 2024-01-23 Zte Corporation Configuration of user plane functions for wireless systems

Similar Documents

Publication Publication Date Title
EP3886502B1 (en) Apparatus, method and computer readable medium related to information about scp(s) and sepp(s) stored in nrf
US11706702B2 (en) Network entity, user equipment and method for the control and use of network slices
US20200245383A1 (en) Data Transmission Channel Processing Method, Apparatus, and System
US11683723B2 (en) Methods and system for offloading data traffic
CN110662308B (en) Communication method and device
WO2019033796A1 (en) Session processing method and related device
EP2115951A2 (en) Quality of service application programming interface over socket
US8995467B2 (en) System and method for providing information indicating the priority level of a non access stratum signaling message and for using the priority level information to select a response
CN111919502A (en) Apparatus and method for processing network
CN105873241B (en) Method and device for establishing call connection
US20210274529A1 (en) Communication system
CN110719611B (en) Message sending method and device
WO2009095070A1 (en) Interface between rnc and node b (a-interface) using ip or tdm
US7340255B2 (en) Management of cell-specific address information
US9020507B2 (en) Radio access technology multiplexing
WO2020094210A1 (en) Coordinated resource reservation for ultra-reliable low latency communication
US8531965B2 (en) Message processing method and system
CN116097751A (en) Re-anchoring with SMF reselection
WO2014134823A1 (en) Wireless transmission method for service data, apparatus and device thereof
EP2526735B1 (en) A method for selecting an a-interface resource in a mobile communication system
US9743325B2 (en) Communication apparatus, storage apparatus, and control method
WO2020034343A1 (en) Ultra reliable communication using a single packet data unit session
CN117641467A (en) Communication method and device
CN115699875A (en) 5G multicast broadcast service handover

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08708286

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08708286

Country of ref document: EP

Kind code of ref document: A1