WO2012006927A1 - 一种建立承载的方法、***和设备 - Google Patents
一种建立承载的方法、***和设备 Download PDFInfo
- Publication number
- WO2012006927A1 WO2012006927A1 PCT/CN2011/076427 CN2011076427W WO2012006927A1 WO 2012006927 A1 WO2012006927 A1 WO 2012006927A1 CN 2011076427 W CN2011076427 W CN 2011076427W WO 2012006927 A1 WO2012006927 A1 WO 2012006927A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- address
- port number
- udp port
- bts
- bearer
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/164—Adaptation or special uses of UDP protocol
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- 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
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
Definitions
- the present invention relates to the field of wireless communication technologies, and in particular, to a method, system and device for establishing a bearer. Background technique
- GSM Global System for Mobile Communications
- other mobile communication systems form a dual-mode, multi-channel
- the demand for modular base station systems has increased.
- more and more platformed mobile communication system devices have been developed and commercialized.
- the mobile communication system equipment is platformized while following the development of the Internet, the newly developed mobile communication system equipment mostly uses the all-IP (Internet Protocol) architecture.
- the BSC Base Station Controller
- the all-IP architecture platformized BSC can further be a user plane data stream carried by RTP (Real-time Transport Protocol) between the Abis port (BTS (Base Transceiver Station) and the BSC).
- RTP Real-time Transport Protocol
- BTS Base Transceiver Station
- Providing direct-through forwarding between the interface and the A port reduces the BSC's processing of the user plane to reduce the hardware and software costs of the BSC.
- the GSM base station system needs to change the processing mode of the traditional user plane data according to the carrier frequency packing, that is, the CS (Circuit Switched Domain) is required.
- the user plane data is based on the terminal packing mechanism, but the current CS user plane data has not been connected to the terminal, so it is impossible to directly connect the A port and the Abis port.
- the current CS user plane data has not been packaged according to the terminal, and it is impossible to directly connect the A port and the Abis port. Summary of the invention
- the embodiments of the present invention provide a method, a system, and a device for establishing a bearer, which are used to implement CS user plane data to be packaged by a terminal, so that the A port and the Abis port are directly connected.
- a method for establishing a bearer provided by an embodiment of the present invention includes:
- the base transceiver station BTS After receiving the first user data packet protocol UDP port number and the first network interconnection protocol IP address from the base station controller BSC, the base transceiver station BTS allocates a second UDP port number and a second IP address for the bearer to be established.
- the first UDP port number and the first IP address are allocated by the BSC to the user plane bearer corresponding to the terminal after determining that the channel needs to be activated for the terminal;
- the BTS establishes a user plane based on the first UDP port number, the first IP address, the second UDP port number, and the second IP address.
- the BSC allocates a first UDP port number and a first IP address to the user plane bearer corresponding to the terminal when it is determined that the channel needs to be activated for the terminal;
- the BSC sends a first UDP port number and a first IP address to the BTS, instructing the BTS to establish a user plane bearer for the terminal according to the first UDP port number and the first IP address.
- a BSC configured to allocate a first UDP port number and a first IP address to the user plane bearer corresponding to the terminal, and send the first UDP port number and the first IP address, when determining that the channel needs to be activated for the terminal;
- the BTS is configured to allocate, after receiving the first UDP port number and the first IP address from the BSC, a second UDP port number and a second IP address for the bearer to be established, according to the first UDP port number and the first IP address.
- the second UDP port number and the second IP address establish a user plane bearer.
- a base transceiver station BTS provided by the embodiment of the present invention includes: a baseband processing control module BUC, a digital baseband processing module DBB, and a communication control module CCM;
- the BUC is configured to: after receiving the first UDP port number and the first IP address from the BSC, assign a second UDP port number and a second IP address to the bearer to be established, and set the first UDP port number and the first IP address.
- the second UDP port number and the second IP address are respectively sent to the DBB and the CCM, where the first UDP port number and the first IP address are the user planes of the terminal corresponding to the terminal after determining that the channel needs to be activated for the terminal. distributed;
- a DBB configured to perform channel activation processing according to the channel information and the first UDP port number, the first IP address, the second UDP port number, and the second IP address;
- the CCM is configured to establish a user plane bearer according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address.
- An allocating module configured to allocate a first UDP port number and a first IP address to a user plane bearer corresponding to the terminal when determining that the channel needs to be activated for the terminal;
- the sending module is configured to send the first UDP port number and the first IP address to the BTS, and instruct the BTS to establish a user plane bearer for the terminal according to the first UDP port number and the first IP address.
- the user plane bearer is established, and the CS user plane data is packaged by the user at the base station, so that the GSM user plane data is directly connected to the A port and the Abis port;
- the processing of the user plane data on the BSC is reduced, the BSC cost is reduced, and the stability of the system is improved; and the GSM user plane data is directly connected to the A port and the Abis port, so that the GSM base station system is in the third and fourth generations.
- mobile communication forms a dual-mode, multi-mode communication base station system, it can share the software and hardware of the base station controller platform, and meet the dual-mode and multi-mode requirements of mobile operators at the lowest cost.
- FIG. 1 is a schematic structural diagram of a system for establishing a bearer according to an embodiment of the present invention
- FIG. 2 is a schematic structural diagram of a BSC according to an embodiment of the present invention.
- FIG. 3 is a schematic structural diagram of a BTS according to an embodiment of the present invention.
- FIG. 4 is a schematic flowchart of a method for establishing a bearer according to an embodiment of the present invention
- FIG. 5 is a schematic flowchart of a second method for establishing a bearer according to an embodiment of the present invention.
- FIG. 6 is a schematic flow chart of a method for dynamically establishing and deleting a bearer by a GSM base station according to an embodiment of the present invention. detailed description
- the BTS establishes a user plane bearer according to the first UDP (User Datagram Protocol) port number, the first IP address, the second UDP port number, and the second IP address, where the first UDP port number And the first IP address is allocated by the BSC to the channel corresponding to the terminal after determining that the channel needs to be activated for the terminal, and the second UDP port number and the second IP address are allocated by the BTS.
- the user plane bearer is established, and the CS user plane data is packaged by the user at the base station, so that the GSM user plane data is directly connected to the A port and the Abis port.
- the system for establishing a bearer in the embodiment of the present invention includes: a BSC 10 and a BTS 20.
- the BSC 10 is configured to allocate a first UDP port number and a first IP address to the channel corresponding to the terminal, and send the first UDP port number and the first IP address, when determining that the channel needs to be activated for the terminal.
- the BTS 20 is configured to allocate, after receiving the first UDP port number and the first IP address from the BSC 10, a second UDP port number and a second IP address for the bearer to be established, according to the first UDP port number, the first The IP address, the second UDP port number, and the second IP address establish a user plane bearer.
- the BSC 10 randomly allocates the first UDP port number and the first IP address for the user plane bearer corresponding to the terminal, and then can pass the channel activation request. (CHAN ACTIV)
- the message is sent to BTS 20.
- the system is testable.
- the first UDP port number captures the fixed allocation principle.
- the second port number draws a fixed allocation principle.
- the BTS 20 After receiving the first UDP port number and the first IP address from the BSC 10, the BTS 20 performs channel activation processing, and allocates a second UDP port number and a second IP address to the bearer to be established, according to the first UDP.
- the port number, the first IP address, the second UDP port number, and the second IP address establish a user plane bearer, and then send a channel activation response (CHAN ACTIV ACK) message to the BSC 10.
- CHAN ACTIV ACK channel activation response
- the BTS 20 of the embodiment of the present invention may further include: a BUC (Baseband Unit Controller) 200, a DBB (Digital Baseband, Digital Baseband Processing Module) 210, and a CCM (Communication Control Module). ) 220.
- BUC Baseband Unit Controller
- DBB Digital Baseband, Digital Baseband Processing Module
- CCM Common Communication Control Module
- the BUC 200 After receiving the first UDP port number and the first IP address from the BSC 10, the BUC 200 allocates a second UDP port number and a second IP address for the bearer to be established, and the first UDP port number, the first IP address, The second UDP port number and the second IP address are sent to the DBB 210 and the CCM 220, respectively.
- the DBB 210 performs channel activation processing based on the channel information and the first UDP port number, the first IP address, the second UDP port number, and the second IP address, and then transmits a channel activation response message to the BUC 200 indicating the channel activation processing result.
- the CCM 220 establishes a user plane bearer according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address, and then sends a bearer setup request response message to the BUC 200 to indicate a bearer setup request processing result. If the bearer is successfully established, the response message carries the Link ID. Otherwise, there is no Link ID in the response message. It should be noted that, in the case of a PS (Packet Switched Domain) service, the bearer that is required to be established by the bearer setup request may already exist, and the response message carries the Link ID of the existing bearer. That is to say, after determining that the user plane is successfully established, the CCM 220 sends the Link ID corresponding to the user plane bearer to the BUC 200 in the BTS 20.
- PS Packet Switched Domain
- the BUC 200 sends a channel activation response message to the BSC 10.
- the BUC 200 in order to shorten the total time of the channel activation process, the BUC 200 immediately sends a channel activation response message to the BSC 10 after receiving the channel activation response message from the DBB 210, without waiting for the CCM 220.
- the bearer setup request response message If the channel activation of the DBB 210 fails, the BUC 200 sends a channel activation failure message to the BSC 10; if the channel activation of the DBB 210 is successful in the extreme case, the BUC 200 receives the bearer setup request response message from the CCM 220 indicating that the bearer setup failed. Then, the BUC 200 initiates connection failure signaling to the BSC 10 to perform failure processing.
- the BUC 200 in the PS service must send the channel activation to the BSC 10 after obtaining the channel activation response message from the DBB 210 and the bearer setup request response message from the CCM 220. Otherwise, the BUC 200 sends a channel activation failure (CHAN ACTIV NACK) message to the BSC 10.
- CHAN ACTIV NACK channel activation failure
- the terminal that uses the bearer can perform services normally. To complete the service, you need to apply for deleting the bearer. Specifically, when the bearer needs to be deleted, the BSC 10 sends a radio channel release (RF CHAN REL ) message containing the channel information of the channel to be released to the BTS 20.
- RF CHAN REL radio channel release
- the BUC 200 in the BTS 20 determines the channel information (the channel information includes the channel type and the slot number) according to the received radio channel release message, and transmits the channel information to the DBB 210 (through the channel release (CHP CHAN REL) Send a message);
- the DBB 210 performs radio channel release processing according to the received channel information, and sends the first UDP port number, the first IP address, the second UDP port number, and the second IP address carried by the user plane corresponding to the released channel to the BUC 200. (can be sent by channel release response (CHP CHAN REL ACK) message);
- the BUC 200 receives the first UDP port number from the DBB 210, the first IP address, The second UDP port number and the second IP address, determine the corresponding Link ID, and send the Link ID to the CCM 220 (can be sent by a 7-load release indication (LINK REL IND) message);
- the CCM 220 After receiving the Link ID, the CCM 220 deletes the bearer corresponding to the Link ID.
- the BUC 200 can also notify the BSC 10 that the deletion is successful, for example, by using a radio channel release response (RF CHAN RELACK) message notification.
- RF CHAN RELACK radio channel release response
- the PS payload is deleted.
- the BSC of the embodiment of the present invention includes: an allocation module 100 and a sending module 110. among them,
- the allocating module 100 is configured to allocate a first UDP port number and a first IP address to the user plane bearer corresponding to the terminal when determining that the channel needs to be activated for the terminal.
- the sending module 110 is configured to send, by the BTS, the first UDP port number and the first IP address allocated by the allocating module 100, and instruct the BTS to establish a user plane bearer for the terminal according to the first UDP port number and the first IP address.
- the allocation module 100 allocates the first UDP port number and the first IP address and the sending module 110 sends the first UDP port number and the first IP address, refer to the related content allocated and sent by the BSC in FIG. Narration.
- the sending module 110 sends a radio channel release message when the bearer needs to be deleted.
- the BTS of the embodiment of the present invention includes: BUC 200, DBB 210, and CCM 220. among them,
- the BUC 200 is configured to: after receiving the first UDP port number and the first IP address from the BSC, assign a second UDP port number and a second IP address to the bearer to be established, and set the first UDP port number and the first IP address.
- the address, the second UDP port number, and the second IP address are respectively sent to the DBB 210 and the CCM 220, where the first UDP port number and the first IP address are user plane bearers corresponding to the terminal after the BSC determines that the channel needs to be activated for the terminal.
- the DBB 210 is configured to perform channel activation processing according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address.
- the CCM 220 is configured to establish a user plane bearer according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address.
- the CCM 220 After determining that the user plane is successfully established, the CCM 220 sends the Link ID corresponding to the user plane bearer to the BUC 200 in the BTS.
- the BUC 200 After receiving the radio channel release message from the BSC, the BUC 200 sends the channel information in the radio channel release message to the DBB 210, and according to the received first UDP port number, the first IP address, and the second UDP port. The number and the second IP address, determine the corresponding Link ID, and send the Link ID to the CCM 220 in the BTS.
- the DBB 210 performs radio channel release processing according to the channel information, and sends the first UDP port number, the first IP address, the second UDP port number, and the second IP address corresponding to the released channel to the BUC 200;
- the CCM 220 deletes the bearer corresponding to the Link ID.
- the BUC 200 deletes the PS bearer when there is no other PS service on the bearer of the determined PS.
- the method for establishing a bearer includes the following steps: Step 401: After receiving the first UDP port number and the first IP address from the BSC, the BTS allocates the bearer for the bearer to be established.
- the second UDP port number and the second IP address, wherein the first UDP port number and the first IP address are allocated by the BSC to the user plane corresponding to the terminal after determining that the channel needs to be activated for the terminal.
- Step 402 The BTS establishes a user plane bearer according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address.
- step 401 the method further includes:
- Step 400 When determining that the channel needs to be activated for the terminal, the BSC is the user corresponding to the terminal. The first UDP port number and the first IP address are assigned, and the first UDP port number and the first IP address are sent to the BTS.
- the BSC randomly allocates a first UDP port number and a first IP address to the user plane bearer corresponding to the terminal, and then sends the first UDP port number and the first IP address to the BTS through the channel activation request message.
- the first UDP port number captures a fixed allocation principle.
- the second UDP port number draws a fixed allocation principle.
- the following BTS support 5 baseband processing boards, each baseband processing board can support 12 carriers as an example to illustrate the allocation of CS and PS UDP port numbers (ie, the second UDP port number):
- PS service data is packed by carrier frequency, RTP and RTCP ( Real-time Transport Control
- the UDP port number is assigned by carrier.
- the port number of the PS service ranges from 21384 to 21503, that is, 0x5388 to 0x53FF.
- bitl5 of the port number is fixed to "0", and bitl4 is fixed to "1".
- bitl4 is fixed to "1”.
- the BTS supports five baseband processing boards, other fixed allocation principles can also be used.
- the BTS supports the allocation of other numbers of baseband processing boards in the same manner as described above, and will not be described here.
- the BTS of the embodiment of the present invention includes: BUC, DBB, and CCM.
- the BUC completes the baseband control functions, including: GSM carrier frequency related configuration management, alarm management, GSM service signaling processing, bearer establishment and deletion.
- the DBB performs digital baseband processing functions, including GSM service control plane signaling processing and user plane data modulation and demodulation.
- the CCM is responsible for the communication link control of the BTS, including the bearer relationship management and maintenance of the establishment, deletion, and keep-alive of the bearer. Further, the CCM is responsible for forwarding the data between the BSC and the DBB according to the bearer relationship.
- the forwarding process includes: the CCM establishes a bearer formation bearer relationship table according to the bearer information, and the bearer relationship table includes the IP address and UDP port number information of the BSC and the BTS, and related information of the DBB associated with the bearer; the data processing chip of the CCM is based on the bearer relationship.
- the table performs bearer matching on the uplink and downlink data between the BSC and the DBB, and replaces the header of the data packet.
- the uplink and downlink data between the BSC and the DBB are sent on the correctly matched channel after the data packet header is replaced, and the data forwarding function is completed.
- step 401 after receiving the first UDP port number and the first IP address from the BSC, the BUC allocates a second UDP port number and a second IP address for the bearer to be established.
- the BUC sends the first UDP port number, the first IP address, the second UDP port number, and the second IP address to the DBB and the CCM, respectively.
- the DBB in the BTS according to the channel information in the channel activation request and the first UDP port number, Performing channel activation processing after the first IP address, the second UDP port number, and the second IP address, and then sending a channel activation response message to the BUC in the BTS to indicate a channel activation processing result;
- the CCM in the BTS establishes a user plane bearer according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address, and then sends a bearer setup request acknowledgement message indication bearer setup request processing result to the BUC. If the bearer is successfully established, the response message carries the Link ID, otherwise there is no Link ID in the response message.
- the CCM after determining that the user plane bearer is successfully established, the CCM sends the Link ID corresponding to the user plane to the BUC in the BTS.
- the BUC may also send a channel activation response message to the BSC. It should be noted that, in the CS service, in order to shorten the total time of the channel activation process, the BUC immediately sends a channel activation response message to the BSC after receiving the channel activation response message from the DBB, without waiting for a bearer setup request from the CCM. Reply message. If the channel activation of the DBB fails, the BUC sends a channel activation failure message to the BSC; if the channel activation of the DBB is successful in an extreme case, and the BUC receives the bearer setup request response message from the CCM indicating that the bearer setup fails, the BUC returns to the BSC. The connection failure signaling is initiated for failure processing.
- the BUC in the PS service must send the channel activation to the BSC after obtaining the channel activation response message from the DBB and the bearer setup request response message from the CCM, otherwise the BUC gives The BSC sends a channel activation failure message.
- the terminal that uses the bearer can perform services normally. To complete the service, you need to apply for deleting the bearer.
- the method further includes:
- Step 403 When the BSC needs to delete the bearer, the BSC may send the channel identifier to the BTS by using a radio channel release message.
- Step 404 After receiving the channel identifier from the BSC, the BTS deletes the established user plane bearer. Specifically, in step 404, the BUC determines channel information (channel information includes channel type and slot number) according to the received channel identifier, and sends the channel information to the DBB;
- channel information channel information includes channel type and slot number
- the DBB performs radio channel release processing according to the received channel information, and sends the first UDP port number, the first IP address, the second UDP port number, and the second IP address corresponding to the released channel to the BUC;
- the BUC determines the corresponding Link ID according to the received first UDP port number, the first IP address, the second UDP port number, and the second IP address from the DBB, and sends the Link ID to the CCM;
- the CCM After receiving the Link ID, the CCM deletes the bearer corresponding to the Link ID.
- the BUC may also notify the BSC that the deletion is successful, for example, by releasing the response message notification through the wireless channel.
- the BUC can also determine whether there is a PS service on the bearer of the PS, if the PS is determined. If there is no other PS service on the bearer, the bearer of the PS is deleted; otherwise, it is reserved.
- the method for establishing a bearer includes the following steps: Step 501: When determining that the channel needs to be activated for the terminal, the BSC allocates a first UDP port number and a first IP address to the channel corresponding to the terminal. .
- Step 502 The BSC sends a first UDP port number and a first IP address to the BTS, instructing the BTS to establish a user plane bearer for the terminal according to the first UDP port number and the first IP address.
- steps 501 and 502 For details of the steps 501 and 502, refer to the content of step 400 in FIG. 4, and details are not described herein again.
- the method for dynamically establishing and deleting a bearer by a GSM base station includes the following steps:
- Step 601 When determining that the channel needs to be activated for the terminal, the BSC allocates a first UDP port number and a first IP address to the channel corresponding to the terminal, and sends the first UDP port number and the first to the BTS.
- CHAN ACTIV Channel Activation Request
- Step 602 After receiving the first UDP port number and the first IP address from the BSC, the BUC of the BTS allocates a second UDP port number and a second IP address to the bearer to be established, and sends the first UDP port number to the DBB.
- CHP CHAN ACTIV channel activation
- Step 603 After receiving the CHP CHAN ACTIV message, the DBB performs channel activation processing. After the processing is completed, the CHC sends a CHP CHAN ACTIV RESP (Channel Activation Response) message to indicate the channel activation processing result.
- CHP CHAN ACTIV RESP Channel Activation Response
- Step 604 After receiving the LINK EST REQ message, the CCM establishes a user plane bearer according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address, and sends an i LINK EST REQ ACK to the BUC.
- the setup request response) message indicates the bearer setup request processing result.
- step 603 and step 604 there is no necessary timing relationship between step 603 and step 604, and it is necessary to determine the received message according to the DBB and the CCM and the processing speed. For example, if the DBB and the CCM receive the message at the same time, step 603 and step 604 can be performed simultaneously.
- Step 605 The BUC sends a CHAN ACTIV ACK message to the BSC.
- the BUC can receive the CHP CHAN ACTIV RESP message.
- the CHAN ACTIV ACK message is sent immediately. If the DBB channel activation fails, the BUC sends a channel activation failure (CHAN ACTIV NACK) message to the BSC, so that the entire channel activation process saves the time for the BUC to interact with the CCM.
- CHAN ACTIV NACK channel activation failure
- the BUC is 3 ⁇ 4 If the bearer establishment fails in the LINK EST REQ ACK message received after the message, the BUC then initiates a connection failure (ABIS CONNECT FAIL IND) signaling to the BSC for failure processing.
- the bearer needs to be deleted when the terminal ends the service and no longer uses the bearer.
- Step 606 The BSC sends an RF CHAN REL (Radio Channel Release) message to the BUC.
- RF CHAN REL Radio Channel Release
- Step 608 The DBB determines and releases the corresponding radio channel according to the channel information, and after the completion of the radio channel release process, sends a CHP CHAN REL ACK message to the BUC, where the CHP CHAN REL ACK message carries the corresponding channel corresponding to the released channel.
- Step 609 The BUC determines a corresponding Link ID according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address, and sends a (bearer release indication) message including a Link ID of the LINK REL IND to the CCM. .
- Step 610 The CCM deletes the bearer corresponding to the Link ID carried in the LINK REL IND message.
- Step 611 The BUC sends an RF CHAN REL ACK message to the BSC.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be embodied in the form of one or more computer program products embodied on a computer-usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.
- a computer-usable storage medium including but not limited to disk storage, CD-ROM, optical storage, etc.
- the present invention is directed to a method, apparatus (system), and computer program in accordance with an embodiment of the present invention.
- the flow chart and/or block diagram of the product is described. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
- These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
- the BTS of the embodiment of the present invention allocates a second UDP port number and a second IP address for the bearer to be established, where The first UDP port number and the first IP address are allocated by the BSC to the channel corresponding to the terminal after determining that the channel needs to be activated for the terminal; the BTS is configured according to the first UDP port number, the first IP address, the second UDP port number, and the second IP address.
- the address establishes a user plane bearer.
- the embodiment of the present invention establishes a user plane bearer when the channel needs to be activated for the terminal, and the CS user plane data is packaged by the user at the base station, so that the GSM user plane data is directly connected to the A port and the Abis port;
- the processing of the user plane data on the BSC is reduced, the BSC cost is reduced, and the stability of the system is improved; and the GSM user plane data is directly connected to the A port and the Abis port, so that the GSM base station system is in the third and fourth generations.
- mobile communication forms a dual-mode, multi-mode communication base station system, it can share the software and hardware of the base station controller platform, and meet the dual-mode and multi-mode requirements of mobile operators at the lowest cost.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
摘要本发明公开了一种建立承载的方法、***和设备,其中方法包括:BTS在收到来自BSC的第一UDP端口号和第一IP地址后,为需要建立的承载分配第二UDP端口号和第二IP地址,其中第一UDP端口号和第一IP地址是BSC在确定需要为终端激活信道后为所述终端对应的用户面承载分配的;所述BTS根据第一UDP端口号、第一IP地址、第二UDP端口号和第二IP地址建立用户面承载。由于本发明实施例在需要为终端激活信道时,才建立用户面承载,在基站实现CS用户面数据按用户打包,实现GSM用户面数据在A口和Abis口直接对接。
Description
一种建立承载的方法、 ***和设备 技术领域
本发明涉及无线通讯技术领域, 特别涉及一种建立承载的方法、 *** 和设备。 背景技术
随着移动通讯行业的高速发展, 特别是多种制式第三、 四代移动通讯 的迅速应用, 使得 GSM ( Global System for Mobile Communications, 全球 移动通信***) 与其他制式移动通讯共同组成双模、 多模基站***的需求 增加。 这种大背景下, 平台化的移动通讯***设备越来越多的被开发及商 用。 而移动通讯***设备平台化的同时跟随互联网络的发展, 新开发的移 动通讯***设备大多釆用全 IP ( Internet Protocol, 网络互连协议) 架构。
在 GSM基站***全 IP接口的接入方案中, BSC( Base Station Controller, 基站控制器 ) 可以分开处理控制面数据及用户面数据, 使得 BSC处理不同 类型数据的软、硬件架构更为清晰, 这种全 IP架构平台化的 BSC进一步可 以为承载于 RTP ( Real-time Transport Protocol , 实时传输协议)的用户面数 据流在 Abis口 (BTS ( Base Transceiver Station, 基站收发信台 )和 BSC之 间的接口 )与 A口之间提供直通转发, 使得减少 BSC对用户面的处理以期 降低 BSC的软、 硬件成本。
为了使用户面数据在 A口和 Abis口直接对接, 根据 GSM业务特点, 需要 GSM基站***改变传统的用户面数据按载频打包的处理模式,也就是 说, 要求 CS ( Circuit SwitchedDomain, 电路交换域)用户面数据按终端打 包机制,但是目前 CS用户面数据还没有按终端打包机制, 所以暂无法实现 在 A口和 Abis口直接对接。
综上所述, 目前 CS用户面数据还没有按终端打包的机制, 无法实现在 A口和 Abis口直接对接。 发明内容
有鉴于此, 本发明实施例提供一种建立承载的方法、 ***和设备, 用 以实现 CS用户面数据按终端打包, 从而在 A口和 Abis口直接对接。
为解决上述技术问题, 本发明实施例提供的一种建立承载的方法, 包 括:
基站收发信台 BTS在收到来自基站控制器 BSC的第一用户数据包协议 UDP端口号和第一网络互连协议 IP地址后, 为需要建立的承载分配第二 UDP端口号和第二 IP地址, 其中第一 UDP端口号和第一 IP地址是 BSC 在确定需要为终端激活信道后为所述终端对应的用户面承载分配的;
所述 BTS根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第 二 IP地址建立用户面 载。
本发明实施例提供的一种建立承载的方法, 包括:
BSC 在确定需要为终端激活信道时, 为所述终端对应的用户面承载分 配第一 UDP端口号和第一 IP地址;
所述 BSC向 BTS发送第一 UDP端口号和第一 IP地址,指示所述 BTS 根据所述第一 UDP端口号和第一 IP地址为所述终端建立用户面承载。
本发明实施例提供的一种建立承载的***, 包括:
BSC,用于在确定需要为终端激活信道时,为所述终端对应的用户面承 载分配第一 UDP端口号和第一 IP地址, 并发送第一 UDP端口号和第一 IP 地址;
BTS, 用于在收到来自 BSC的第一 UDP端口号和第一 IP地址后, 为 需要建立的承载分配第二 UDP端口号和第二 IP地址, 根据第一 UDP端口 号、 第一 IP地址、 第二 UDP端口号和第二 IP地址建立用户面承载。
本发明实施例提供的一种基站收发信台 BTS , 包括: 基带处理控制模 块 BUC、 数字基带处理模块 DBB和通信控制模块 CCM;
BUC, 用于在收到来自 BSC的第一 UDP端口号和第一 IP地址后, 为 需要建立的承载分配第二 UDP端口号和第二 IP地址,将第一 UDP端口号、 第一 IP地址、第二 UDP端口号和第二 IP地址,分别发送给 DBB和 CCM, 其中第一 UDP端口号和第一 IP地址是 BSC在确定需要为终端激活信道后 为所述终端对应的用户面 7 载分配的;
DBB, 用于根据信道信息以及第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址进行信道激活处理;
CCM, 用于根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和 第二 IP地址建立用户面承载。
本发明实施例提供的一种基站控制器 BSC, 包括:
分配模块, 用于在确定需要为终端激活信道时, 为所述终端对应的用 户面承载分配第一 UDP端口号和第一 IP地址;
发送模块, 用于向 BTS发送第一 UDP端口号和第一 IP地址, 指示所 述 BTS根据所述第一 UDP端口号和第一 IP地址为所述终端建立用户面承 载。
由于本发明实施例在需要为终端激活信道时, 才建立用户面承载, 在 基站实现 CS用户面数据按用户打包,实现 GSM用户面数据在 A口和 Abis 口直接对接;
进一步还减少 BSC上用户面数据的处理工作, 降低了 BSC成本,提高 ***的稳定性; 而且 GSM用户面数据在 A口和 Abis口直接对接的实现, 使得 GSM基站***在与第三、 四代移动通讯组成双模、 多模通讯基站*** 时能够共享基站控制器平台化的软、 硬件, 最低成本地满足移动运营商的 双模、 多模需求。
附图说明
图 1为本发明实施例建立承载的***结构示意图;
图 2为本发明实施例 BSC的结构示意图;
图 3为本发明实施例 BTS的结构示意图;
图 4为本发明实施例第一种建立承载的方法流程示意图;
图 5为本发明实施例第二种建立承载的方法流程示意图;
图 6为本发明实施例 GSM基站动态建立和删除承载的方法流程示意 图。 具体实施方式
本发明实施例中, BTS根据第一 UDP ( User Datagram Protocol, 用户 数据包协议)端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址建立 用户面承载, 其中第一 UDP端口号和第一 IP地址是 BSC在确定需要为终 端激活信道后为终端对应的信道分配的 ,第二 UDP端口号和第二 IP地址是 BTS 分配的。 由于本发明实施例在需要为终端激活信道时, 才建立用户面 承载, 在基站实现 CS用户面数据按用户打包, 实现 GSM用户面数据在 A 口和 Abis口直接对接。
下面结合说明书附图对本发明实施例作进一步详细描述。
如图 1所示, 本发明实施例建立承载的***包括: BSC 10和 BTS 20。
BSC 10, 用于在确定需要为终端激活信道时, 为终端对应的信道分配 第一 UDP端口号和第一 IP地址 , 并发送第一 UDP端口号和第一 IP地址。
BTS 20,用于在收到来自 BSC 10的第一 UDP端口号和第一 IP地址后, 为需要建立的承载分配第二 UDP端口号和第二 IP地址, 根据第一 UDP端 口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址建立用户面承载。
具体的, BSC 10在确定需要为终端激活信道后, 为终端对应的用户面 承载随机分配第一 UDP端口号和第一 IP地址,然后可以通过信道激活请求
( CHAN ACTIV ) 消息发送给 BTS 20。
为了***故障排查方便, 增强***可测试性, 可选地, 第一 UDP端口 号釆取固定分配原则。 优选地, 第二端口号釆取固定分配原则。
其中, BTS 20在收到来自 BSC 10的第一 UDP端口号和第一 IP地址后, 进行信道激活处理, 并为需要建立的承载分配第二 UDP端口号和第二 IP 地址, 根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地 址建立用户面承载, 然后发送信道激活应答( CHAN ACTIV ACK ) 消息给 BSC 10。
具体的,本发明实施例的 BTS 20中还可以进一步包括: BUC( Baseband Unit Controller, 基带处理控制模块) 200、 DBB ( Digital Baseband, 数字基 带处理模块) 210和 CCM ( Communication Control Module, 通信控制模块) 220。
BUC 200在收到来自 BSC 10的第一 UDP端口号和第一 IP地址后, 为 需要建立的承载分配第二 UDP端口号和第二 IP地址,将第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址, 分别发送给 DBB 210和 CCM 220。
DBB 210根据信道信息以及第一 UDP端口号、第一 IP地址、第二 UDP 端口号和第二 IP地址后进行信道激活处理,然后给 BUC 200发送信道激活 响应消息指示信道激活处理结果。
CCM 220根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第 二 IP地址建立用户面承载,然后给 BUC 200发送承载建立请求应答消息指 示承载建立请求处理结果。如果承载建立成功则应答消息中携带 Link ID(链 路标识), 否则应答消息中无 Link ID。 需要说明的是, 在 PS ( Packet SwitchedDomain, 分组交换域) 业务时, 所述承载建立请求所要求建立的 承载可能已经存在, 则应答消息中携带该所述已存在承载的 Link ID。
也就是说, CCM 220在确定成功建立用户面 载后, 向 BTS 20中的 BUC 200发送用户面承载对应的 Link ID。
BUC 200给 BSC 10发送信道激活应答消息。
需要说明的是, 在 CS 业务中, 为了缩短信道激活流程的总时间, 在 BUC 200收到来自 DBB 210的信道激活响应消息后就立刻给 BSC 10发送 信道激活应答消息, 不需要等来自 CCM 220的承载建立请求应答消息。 如 果 DBB 210的信道激活失败, 则 BUC 200给 BSC 10发送信道激活失败消 息; 如果在极端情况下 DBB 210的信道激活成功, 而 BUC 200收到来自 CCM 220的承载建立请求应答消息指示承载建立失败, 则 BUC 200再向 BSC 10发起连接失败信令进行失败处理。
由于 PS业务建立后没有这种连接失败信令, 所以 PS业务中 BUC 200 必须在获得来自 DBB 210的信道激活响应消息和来自 CCM 220的承载建立 请求应答消息后,才给 BSC 10发送信道激活成功,否则 BUC 200给 BSC 10 发送信道激活失败( CHAN ACTIV NACK ) 消息。
在承载建立完成后, 使用该承载的终端可以正常进行业务, 完成业务, 则需要申请删除该承载。 具体的, BSC 10在需要删除承载时, 发送包含将 要释放信道的信道信息的无线信道释放 ( RF CHAN REL ) 消息给 BTS 20。
相应的, BTS 20中的 BUC 200根据收到的无线信道释放消息, 确定信 道信息(信道信息包括信道类型和时隙号), 并将信道信息发送给 DBB 210 (通过信道释放 ( CHP CHAN REL ) 消息发送);
DBB 210根据收到的信道信息进行无线信道释放处理, 并将释放的信 道对应的用户面承载的第一 UDP端口号、 第一 IP地址、 第二 UDP端口号 和第二 IP地址发送给 BUC 200 (可以通过信道释放应答 ( CHP CHAN REL ACK ) 消息发送);
BUC 200根据收到的来自 DBB 210的第一 UDP端口号、第一 IP地址、
第二 UDP端口号和第二 IP地址, 确定对应的 Link ID , 并将 Link ID发送 给 CCM 220 (可以通过 7 载释放指示 (LINK REL IND ) 消息发送);
CCM 220在收到 Link ID后, 删除 Link ID对应的承载。
可选的, BUC 200在承载删除后, 还可以通知 BSC 10删除成功, 比如 通过无线信道释放应答(RF CHAN RELACK ) 消息通知。
其中, 在 PS业务时, BUC 200在确定 PS的承载上没有 PS业务时, 删 除 PS的 载。
如图 2所示,本发明实施例的 BSC包括:分配模块 100和发送模块 110。 其中,
分配模块 100, 用于在确定需要为终端激活信道时, 为终端对应的用户 面承载分配第一 UDP端口号和第一 IP地址。
发送模块 110, 用于向 BTS发送分配模块 100分配的第一 UDP端口号 和第一 IP地址,指示 BTS根据第一 UDP端口号和第一 IP地址为终端建立 用户面承载。
分配模块 100分配第一 UDP端口号和第一 IP地址以及发送模块 110 发送第一 UDP端口号和第一 IP地址的具体实现方式可以参见图 1中 BSC 分配和发送的相关内容, 在此不再赘述。
进一步的, 发送模块 110在需要删除承载时, 发送无线信道释放消息。 如图 3所示, 本发明实施例的 BTS包括: BUC 200、 DBB 210和 CCM 220。 其中,
BUC 200, 用于在收到来自 BSC的第一 UDP端口号和第一 IP地址后, 为需要建立的承载分配第二 UDP端口号和第二 IP地址, 将第一 UDP端口 号、 第一 IP地址、 第二 UDP端口号和第二 IP地址, 分别发送给 DBB 210 和 CCM 220, 其中第一 UDP端口号和第一 IP地址是 BSC在确定需要为终 端激活信道后为终端对应的用户面承载分配的。
DBB 210, 用于根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口 号和第二 IP地址后进行信道激活处理。
CCM 220, 用于根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口 号和第二 IP地址建立用户面承载。
其中, CCM 220在确定成功建立用户面 载后, 向 BTS中的 BUC 200 发送用户面承载对应的 Link ID。
其中, BUC 200在收到来自 BSC的无线信道释放消息后, 将无线信道 释放消息中的信道信息发送给 DBB 210,以及根据收到的第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址, 确定对应的 Link ID , 并将 Link ID发送给 BTS中的 CCM 220。
DBB 210根据信道信息进行无线信道释放处理, 并将释放的信道对应 的第一 UDP端口号、第一 IP地址、 第二 UDP端口号和第二 IP地址发送给 BUC 200;
CCM 220删除 Link ID对应的承载。
其中, BUC 200在确定 PS的承载上没有其他 PS业务时,删除 PS的承 载。
如图 4所示, 本发明实施例第一种建立承载的方法包括下列步骤: 步骤 401、 BTS在收到来自 BSC的第一 UDP端口号和第一 IP地址后, 为需要建立的承载分配第二 UDP端口号和第二 IP地址, 其中第一 UDP端 口号和第一 IP地址是 BSC在确定需要为终端激活信道后为终端对应的用户 面 载分配的。
步骤 402、 BTS根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口 号和第二 IP地址建立用户面承载。
其中, 步骤 401之前还可以进一步包括:
步骤 400、 BSC在确定需要为终端激活信道时,为终端对应的用户面承
载分配第一 UDP端口号和第一 IP地址,向 BTS发送第一 UDP端口号和第 一 IP地址。
具体的, 步骤 400中 BSC在确定需要为终端进行信道激活时, 并为终 端对应的用户面承载随机分配第一 UDP端口号和第一 IP地址,然后可以通 过信道激活请求消息发送给 BTS。
为了***故障排查方便, 增强***可测试性。 可选地, 第一 UDP端口 号釆取固定分配原则。 优选地, 第二 UDP端口号釆取固定分配原则。 下面 以 BTS支持 5块基带处理板, 每块基带处理板可支持 12载波为例说明 CS 和 PS的 UDP端口号 (即第二 UDP端口号) 的分配情况:
PS业务数据按载频打包, RTP及 RTCP ( Real-time Transport Control
Protocol, 实时传输控制协议) 的 UDP端口号按载波分配。 PS业务的端口 号的范围为 21384 ~ 21503 , 即 0x5388 ~ 0x53FF。 端口号计算规则:
PS RTP端口号:
21384 + (基带处理板的板号 <0 ~ 4> x 12 +载波号 <0 ~ 11>) 2
PS RTCP端口号:
21384 + (基带处理板的板号 <0 ~ 4> x 12 +载波号 <0 ~ 11>) 2 + 1 CS业务下, RTP及 RTCP的 UDP端口号按用户分配, CS业务端口号 范围为 21504 ~ 29695 , 即 0x5400 ~ 0x73FF。
Bit6〜 9 TRXNo 基带处理板上的载波号, 0 ~ 11
O BoardNo 基带处理板的板号, 0 ~ 4
Bitl3 CM Resv 保留位
需要说明的是, 上面只是举例说明, BTS支持 5块基带处理板时, 也 可以釆用其他固定分配原则。 BTS 支持其他数量的基带处理板的分配方式 与上述方式类似, 在此不再赘述。
针对本发明方法的另一实施例中, 本发明实施例的 BTS包括: BUC、 DBB和 CCM。
BUC完成基带控制功能, 包括: GSM载频相关配置管理, 告警管理, GSM业务信令处理, 承载的建立、 删除等功能。
DBB完成数字基带处理功能, 包括 GSM业务控制面信令处理和用户 面数据的调制解调等处理。
CCM负责 BTS的通信链路控制, 包括承载的建立、 删除、保活等承载 关系管理维护工作。 进一步地 CCM 负责用户面承载数据根据承载关系在 BSC与 DBB之间的转发。 转发过程包括: CCM根据承载信息建立承载形 成承载关系表,承载关系表包括 BSC及 BTS的 IP地址及 UDP端口号信息 以及该条承载所关联的 DBB的相关信息; CCM的数据处理芯片根据承载 关系表对 BSC与 DBB之间的上下行数据进行承载匹配, 数据包的包头替 换; BSC与 DBB之间的上下行数据在完成数据包头替换后在匹配正确的通 道上进行发送, 完成数据转发功能。
具体的, 步骤 401中, BUC在收到来自 BSC的第一 UDP端口号和第 一 IP地址后, 为需要建立的承载分配第二 UDP端口号和第二 IP地址。
步骤 402中, BUC将第一 UDP端口号、 第一 IP地址、 第二 UDP端口 号和第二 IP地址, 分别发送给 DBB和 CCM;
BTS中的 DBB根据信道激活请求中信道信息以及第一 UDP端口号、
第一 IP地址、 第二 UDP端口号和第二 IP地址后进行信道激活处理 , 然后 给 BTS中的 BUC发送信道激活响应消息指示信道激活处理结果;
BTS中的 CCM根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口 号和第二 IP地址建立用户面承载, 然后给 BUC发送承载建立请求应答消 息指示承载建立请求处理结果。 如果承载建立成功则应答消息中携带 Link ID , 否则应答消息中无 Link ID。
也就是说, CCM在确定成功建立用户面承载后, 向 BTS中的 BUC发 送用户面 载对应的 Link ID。
进一步的, 步骤 402中, BUC还可以给 BSC发送信道激活应答消息。 需要说明的是, 在 CS 业务中, 为了缩短信道激活流程的总时间, 在 BUC收到来自 DBB的信道激活响应消息后就立刻给 BSC发送信道激活应 答消息, 不需要等来自 CCM的承载建立请求应答消息。 如果 DBB的信道 激活失败,则 BUC给 BSC发送信道激活失败消息;如果在极端情况下 DBB 的信道激活成功, 而 BUC收到来自 CCM的承载建立请求应答消息指示承 载建立失败, 则 BUC再向 BSC发起连接失败信令进行失败处理。
由于 PS业务建立后没有这种连接失败信令,所以 PS业务中 BUC必须 在获得来自 DBB的信道激活响应消息和来自 CCM的承载建立请求应答消 息后, 才给 BSC发送信道激活成功, 否则 BUC给 BSC发送信道激活失败 消息。
在承载建立完成后, 使用该承载的终端可以正常进行业务, 完成业务, 则需要申请删除该承载。 具体的, 步骤 402之后还可以进一步包括:
步骤 403、 BSC在需要删除承载时,可以通过无线信道释放消息将信道 标识发送给 BTS。
步骤 404、 BTS在收到来自 BSC的信道标识后, 删除已建立的用户面 承载。
具体的, 步骤 404中, BUC根据收到的信道标识, 确定信道信息(信 道信息包括信道类型和时隙号), 并将信道信息发送给 DBB;
DBB根据收到的信道信息进行无线信道释放处理, 并将释放的信道对 应的第一 UDP端口号、 第一 IP地址、第二 UDP端口号和第二 IP地址发送 给 BUC;
BUC根据收到的来自 DBB的第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址,确定对应的 Link ID ,并将 Link ID发送给 CCM;
CCM在收到 Link ID后, 删除 Link ID对应的承载。
可选的, BUC在承载删除后, 还可以通知 BSC删除成功, 比如通过无 线信道释放应答消息通知。
其中, DBB将第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第 二 IP地址发送给 BTS中的 BUC之后, BUC还可以判断 PS的承载上有没 有 PS业务,如果确定 PS的承载上没有其他 PS业务时,则删除 PS的承载; 否则保留。
如图 5所示, 本发明实施例第二种建立承载的方法包括下列步骤: 步骤 501、 BSC在确定需要为终端激活信道时,为终端对应的信道分配 第一 UDP端口号和第一 IP地址。
步骤 502、 BSC向 BTS发送第一 UDP端口号和第一 IP地址,指示 BTS 根据第一 UDP端口号和第一 IP地址为终端建立用户面承载。
其中, 步骤 501和步骤 502的具体内容可以参见图 4中关于步骤 400 的内容, 在此不再赘述。
如图 6所示,本发明实施例 GSM基站动态建立和删除承载的方法包括 下列步骤:
步骤 601、 BSC在确定需要为终端激活信道时,为终端对应的信道分配 第一 UDP端口号和第一 IP地址,向 BTS发送包含第一 UDP端口号和第一
IP地址的 CHAN ACTIV (信道激活请求 ) 消息。
步骤 602、 BTS的 BUC在收到来自 BSC的第一 UDP端口号和第一 IP 地址后, 为需要建立的承载分配第二 UDP端口号和第二 IP地址, 向 DBB 发送包含第一 UDP端口号、第一 IP地址、第二 UDP端口号和第二 IP地址 的 CHP CHAN ACTIV (信道激活 ) 消息, 以及向 CCM发送包含第一 UDP 端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址的 LINK EST REQ (承载建立请求) 消息。
步骤 603、 DBB在收到 CHP CHAN ACTIV消息后进行信道激活处理 , 处理完成后, 给 BUC发送 CHP CHAN ACTIV RESP (信道激活响应)消息 指示信道激活处理结果。
步骤 604、 CCM在收到 LINK EST REQ消息后 ,根据第一 UDP端口号、 第一 IP地址、第二 UDP端口号和第二 IP地址建立用户面承载,给 BUC发 i LINK EST REQ ACK (承载建立请求应答) 消息指示承载建立请求处理 结果。
需要说明的是, 步骤 603和步骤 604没有必然的时序关系, 具体需要 根据 DBB和 CCM收到消息以及进行处理速度决定。 比如 DBB和 CCM同 时收到消息, 则可以同时执行步骤 603和步骤 604。
步骤 605、 BUC给 BSC发送 CHAN ACTIV ACK (信道激活应答 ) 消 息。
在 CS业务中, 考虑到 CCM上承载建立绝大多情况都会成功, 只有极 少极端的情况下才会承载建立失败, 为了缩短信道激活流程的总时间, 可 以在 BUC收到 CHP CHAN ACTIV RESP消息后就立刻发送 CHAN ACTIV ACK消息, 如果 DBB信道激活失败, 则 BUC给 BSC发送信道激活失败 ( CHAN ACTIV NACK ) 消息, 这样整个信道激活流程中节省了 BUC与 CCM交互的时间。如果极端情况下 BUC在¾
消息后收到的 LINK EST REQ ACK消息中指示承载建立失败 , 则 BUC再 向 BSC发起连接失败( ABIS CONNECT FAIL IND )信令进行失败处理。
如果承载建立完成, 还需要在终端结束业务不再使用承载时, 删除该 承载。
步骤 606、 BSC给 BUC发送 RF CHAN REL (无线信道释放 ) 消息。 步骤 607、 BUC根据 RF CHAN REL消息中包含的信道标识, 确定信 道信息, 向 DBB发送包含信道信息的 CHP CHAN REL (信道释放 ) 消息。
步骤 608、 DBB根据信道信息确定并释放对应的无线信道, 在完成无 线信道释放处理后, 给 BUC发送 CHP CHAN REL ACK (信道释放应答 ) 消息, 其中 CHP CHAN REL ACK消息中携带所释放信道对应的第一 UDP 端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址。
步骤 609、 BUC根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口 号和第二 IP地址,确定对应的 Link ID, 向 CCM发送包含 Link ID的 LINK REL IND的 (承载释放指示) 消息。
步骤 610、 CCM删除 LINK REL IND消息中携带的 Link ID所对应的 承载。
步骤 611、 BUC给 BSC发送 RF CHAN REL ACK (无线信道释放应答 ) 消息。
本领域内的技术人员应明白, 本发明的实施例可提供为方法、 ***、 或计算机程序产品。 因此, 本发明可釆用完全硬件实施例、 完全软件实施 例、 或结合软件和硬件方面的实施例的形式。 而且, 本发明可釆用在一个 或多个其中包含有计算机可用程序代码的计算机可用存储介质 (包括但不 限于磁盘存储器、 CD-ROM、 光学存储器等)上实施的计算机程序产品的 形式。
本发明是参照根据本发明实施例的方法、 设备(***)、 和计算机程序
产品的流程图和 /或方框图来描述的。 应理解可由计算机程序指令实现流 程图和 /或方框图中的每一流程和 /或方框、 以及流程图和 /或方框图中 的流程和 /或方框的结合。 可提供这些计算机程序指令到通用计算机、 专 用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个 机器, 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产 生用于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方 框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理 设备以特定方式工作的计算机可读存储器中, 使得存储在该计算机可读存 储器中的指令产生包括指令装置的制造品, 该指令装置实现在流程图一个 流程或多个流程和 /或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备 上, 使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机 实现的处理, 从而在计算机或其他可编程设备上执行的指令提供用于实现 在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的 功能的步骤。
尽管已描述了本发明的优选实施例, 但本领域内的技术人员一旦得知 了基本创造性概念, 则可对这些实施例作出另外的变更和修改。 所以, 所 附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和 修改。
从上述实施例中可以看出:本发明实施例 BTS在收到来自 BSC的第一 UDP端口号和第一 IP地址后, 为需要建立的承载分配第二 UDP端口号和 第二 IP地址,其中第一 UDP端口号和第一 IP地址是 BSC在确定需要为终 端激活信道后为终端对应的信道分配的; BTS根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址建立用户面承载。
由于本发明实施例在需要为终端激活信道时, 才建立用户面承载, 在 基站实现 CS用户面数据按用户打包,实现 GSM用户面数据在 A口和 Abis 口直接对接;
进一步还减少 BSC上用户面数据的处理工作, 降低了 BSC成本,提高 ***的稳定性; 而且 GSM用户面数据在 A口和 Abis口直接对接的实现, 使得 GSM基站***在与第三、 四代移动通讯组成双模、 多模通讯基站*** 时能够共享基站控制器平台化的软、 硬件, 最低成本地满足移动运营商的 双模、 多模需求。 本发明的精神和范围。 这样, 倘若本发明的这些修改和变型属于本发明权 利要求及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在 内。
Claims
1、 一种建立承载的方法, 其特征在于, 包括:
基站收发信台 BTS在收到来自基站控制器 BSC的第一用户数据包协议 UDP端口号和第一网络互连协议 IP地址后, 为需要建立的承载分配第二 UDP端口号和第二 IP地址, 其中第一 UDP端口号和第一 IP地址是 BSC 在确定需要为终端激活信道后为所述终端对应的用户面承载分配的;
所述 BTS根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第 二 IP地址建立用户面 载。
2、如权利要求 1所述的方法, 其特征在于, 所述 BTS建立用户面承载 包括:
所述 BTS中的基带处理控制模块 BUC将第一 UDP端口号、第一 IP地 址、 第二 UDP端口号和第二 IP地址, 分别发送给所述 BTS中的数字基带 处理模块 DBB和所述 BTS中的通信控制模块 CCM;
所述 BTS中的 DBB根据收到的第一 UDP端口号、 第一 IP地址、第二 UDP端口号和第二 IP地址进行信道激活处理;
所述 BTS中的 CCM根据第一 UDP端口号、 第一 IP地址、 第二 UDP 端口号和第二 IP地址建立用户面承载。
3、 如权利要求 2所述的方法, 其特征在于, 所述 BTS中的 CCM建立 用户面承载之后还包括:
所述 BTS中的 CCM在确定成功建立用户面承载后, 向所述 BTS中的 BUC发送用户面承载对应的链路标识 Link ID。
4、 如权利要求 2所述的方法, 其特征在于, 所述 BTS中的 DBB根据 进行信道激活处理之后还包括:
所述 BTS中的 DBB向所述 BTS中的 BUC发送信道激活响应消息; 所述 BTS中的 BUC在收到所述信道激活响应消息后, 向所述 BSC发 送信道激活应答消息。
5、如权利要求 2至 4任一所述的方法, 其特征在于, 所述 BTS建立用 户面承载之后还包括:
所述 BTS中的 BUC根据收到的无线信道释放消息,确定需要释放的信 道对应的信道信息, 并将信道信息发送给所述 BTS中的 DBB;
所述 BTS中的 DBB根据所述信道信息进行无线信道释放处理,并将释 放的信道对应的第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址发送给所述 BTS中的 BUC;
所述 BTS中的 BUC根据第一 UDP端口号、 第一 IP地址、 第二 UDP 端口号和第二 IP地址,确定对应的链路标识 ,并将链路标识发送给所述 BTS 中的 CCM;
所述 BTS中的 CCM删除链路标识对应的承载。
6、 一种建立承载的方法, 其特征在于, 包括:
BSC 在确定需要为终端激活信道时, 为所述终端对应的用户面承载分 配第一 UDP端口号和第一 IP地址;
所述 BSC向基站收发信台 BTS发送第一 UDP端口号和第一 IP地址, 指示所述 BTS根据所述第一 UDP端口号和第一 IP地址为所述终端建立用 户面 载。
7、 一种建立承载的***, 其特征在于, 包括:
BSC,用于在确定需要为终端激活信道时,为所述终端对应的用户面承 载分配第一 UDP端口号和第一 IP地址, 并发送第一 UDP端口号和第一 IP 地址;
BTS, 用于在收到来自 BSC的第一 UDP端口号和第一 IP地址后, 为 需要建立的承载分配第二 UDP端口号和第二 IP地址, 根据第一 UDP端口 号、 第一 IP地址、 第二 UDP端口号和第二 IP地址建立用户面承载。
8、 如权利要求 7所述的***, 其特征在于, 所述 BTS 包括: BUC、 DBB和 CCM;
BUC, 用于在收到来自 BSC的第一 UDP端口号和第一 IP地址后, 为 需要建立的承载分配第二 UDP端口号和第二 IP地址,将第一 UDP端口号、 第一 IP地址、第二 UDP端口号和第二 IP地址,分别发送给 DBB和 CCM;
DBB, 用于根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和 第二 IP地址后进行信道激活处理;
CCM, 用于根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和 第二 IP地址建立用户面承载。
9、 如权利要求 8所述的***, 其特征在于, 所述 CCM还用于: 在确定成功建立用户面承载后,向所述 BTS中的 BUC发送用户面承载 对应的链路标识。
10、 如权利要求 8所述的***, 其特征在于,
所述 DBB还用于: 在进行信道激活处理之后, 向所述 BUC发送信道 激活响应消息;
所述 BUC还用于: 在收到所述信道激活响应消息后, 向所述 BSC发 送信道激活应答消息。
11、 如权利要求 8至 10任一所述的***, 其特征在于,
所述 BSC还用于: 在需要删除承载时, 发送无线信道释放消息; 所述 BUC还用于: 根据收到的无线信道释放消息, 确定需要释放的信 道对应的信道信息, 并将信道信息发送给 DBB, 以及根据收到的第一 UDP 端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址, 确定对应的链路 标识, 并将链路标识发送给 CCM;
所述 DBB还用于: 根据所述信道信息进行无线信道释放处理, 并将释 放的信道对应的第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址发送给 BUC;
所述 CCM还用于: 删除链路标识对应的承载。
12、一种基站收发信台 BTS, 其特征在于, 包括: BUC、 DBB和 CCM; BUC, 用于在收到来自 BSC的第一 UDP端口号和第一 IP地址后, 为 需要建立的承载分配第二 UDP端口号和第二 IP地址,将第一 UDP端口号、 第一 IP地址、第二 UDP端口号和第二 IP地址,分别发送给 DBB和 CCM, 其中第一 UDP端口号和第一 IP地址是 BSC在确定需要为终端激活信道后 为所述终端对应的用户面 7 载分配的;
DBB, 用于根据信道信息以及第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址进行信道激活处理;
CCM, 用于根据第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和 第二 IP地址建立用户面承载。
13、 如权利要求 12所述的 BTS , 其特征在于, 所述 CCM还用于: 在确定成功建立用户面承载后,向所述 BTS中的 BUC发送用户面承载 对应的链路标识。
14、 如权利要求 12所述的 BTS , 其特征在于,
所述 DBB还用于: 在进行信道激活处理之后, 向所述 BUC发送信道 激活响应消息;
所述 BUC还用于: 在收到所述信道激活响应消息后, 向所述 BSC发 送信道激活应答消息。
15、 如权利要求 12至 14任一所述的 BTS, 其特征在于,
所述 BUC还用于: 在收到来自 BSC的无线信道释放消息后, 确定需 要释放的信道对应的信道信息, 并将信道信息发送给 DBB, 以及根据收到 的第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址, 确定 对应的链路标识, 并将链路标识发送给所述 BTS中的 CCM; 所述 DBB还用于: 根据所述信道信息进行无线信道释放处理, 并将释 放的信道对应的第一 UDP端口号、 第一 IP地址、 第二 UDP端口号和第二 IP地址发送给 BUC;
所述 CCM还用于: 删除链路标识对应的承载。
16、 一种基站控制器 BSC, 其特征在于, 包括:
分配模块, 用于在确定需要为终端激活信道时, 为所述终端对应的用 户面承载分配第一 UDP端口号和第一 IP地址;
发送模块, 用于向 BTS发送第一 UDP端口号和第一 IP地址, 指示所 述 BTS根据所述第一 UDP端口号和第一 IP地址为所述终端建立用户面承 载。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP11806269.4A EP2592794A1 (en) | 2010-07-12 | 2011-06-27 | Method, system and equipment for establishing bearer |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010225798.1A CN102333385B (zh) | 2010-07-12 | 2010-07-12 | 一种建立承载的方法、***和设备 |
CN201010225798.1 | 2010-07-12 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012006927A1 true WO2012006927A1 (zh) | 2012-01-19 |
Family
ID=45468924
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/076427 WO2012006927A1 (zh) | 2010-07-12 | 2011-06-27 | 一种建立承载的方法、***和设备 |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2592794A1 (zh) |
CN (1) | CN102333385B (zh) |
WO (1) | WO2012006927A1 (zh) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20040056990A (ko) * | 2002-12-24 | 2004-07-01 | 한국전자통신연구원 | 차세대 네트워크에서의 이동통신 서비스 제어 시스템 및방법, 그 프로그램이 저장된 기록매체 |
CN101237396A (zh) * | 2007-01-30 | 2008-08-06 | 中兴通讯股份有限公司 | 一种移动通信***中ip承载建立的实现方法 |
CN101527967A (zh) * | 2008-03-06 | 2009-09-09 | 华为技术有限公司 | 扁平umts中实现cs域业务的方法、***和设备 |
CN101577947A (zh) * | 2008-05-09 | 2009-11-11 | 中兴通讯股份有限公司 | 呼叫建立方法及切换方法 |
CN101645824A (zh) * | 2008-08-08 | 2010-02-10 | 华为技术有限公司 | 数据传输方法、用户终端和网络设备 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1150523A3 (en) * | 2000-04-25 | 2002-06-12 | Lucent Technologies Inc. | Supporting IP on Abis interface |
CN1545288B (zh) * | 2003-11-22 | 2011-06-22 | 中兴通讯股份有限公司 | 一种基站内外部链路标识的映射和处理方法 |
CN101674664A (zh) * | 2008-09-12 | 2010-03-17 | 华为技术有限公司 | 用户面数据传输的方法和网络*** |
CN101594692B (zh) * | 2009-06-30 | 2011-05-11 | 中兴通讯股份有限公司 | 一种ip abis中的快速呼叫建立的方法及*** |
-
2010
- 2010-07-12 CN CN201010225798.1A patent/CN102333385B/zh not_active Expired - Fee Related
-
2011
- 2011-06-27 EP EP11806269.4A patent/EP2592794A1/en not_active Withdrawn
- 2011-06-27 WO PCT/CN2011/076427 patent/WO2012006927A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20040056990A (ko) * | 2002-12-24 | 2004-07-01 | 한국전자통신연구원 | 차세대 네트워크에서의 이동통신 서비스 제어 시스템 및방법, 그 프로그램이 저장된 기록매체 |
CN101237396A (zh) * | 2007-01-30 | 2008-08-06 | 中兴通讯股份有限公司 | 一种移动通信***中ip承载建立的实现方法 |
CN101527967A (zh) * | 2008-03-06 | 2009-09-09 | 华为技术有限公司 | 扁平umts中实现cs域业务的方法、***和设备 |
CN101577947A (zh) * | 2008-05-09 | 2009-11-11 | 中兴通讯股份有限公司 | 呼叫建立方法及切换方法 |
CN101645824A (zh) * | 2008-08-08 | 2010-02-10 | 华为技术有限公司 | 数据传输方法、用户终端和网络设备 |
Also Published As
Publication number | Publication date |
---|---|
CN102333385A (zh) | 2012-01-25 |
CN102333385B (zh) | 2014-12-10 |
EP2592794A1 (en) | 2013-05-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
RU2762681C2 (ru) | Способ передачи данных, устройство сети доступа, терминал и система связи | |
CN112868254A (zh) | 集成接入回程(iab)拓扑适配-控制平面(cp)处置 | |
CN110798408B (zh) | 一种报文传输方法及装置 | |
US20070064608A1 (en) | Apparatus, method and computer program product to configure a radio link protocol for internet protocol flow | |
CN103368688B (zh) | 数据处理装置 | |
RU2413373C2 (ru) | Объединение сигналов связи для эффективности | |
JP2021534661A (ja) | 通信方法および通信装置 | |
CN110868733B (zh) | 一种数据传输方法和装置 | |
US20070076667A1 (en) | Apparatus, method and computer program product to provide Flow_ID management in MAC sub-layer for packet-optimized radio link layer | |
JP2019050587A (ja) | 複数の同時無線アクセス技術によるデータ伝送のためのモバイル端末および方法 | |
KR102083273B1 (ko) | 클라우드 무선 액세스 네트워크의 동적 구성을 위한 방법 및 장치 | |
WO2011106984A1 (zh) | 移动终端并行传输数据的方法和移动终端 | |
KR101509064B1 (ko) | 멀티-모드 디바이스에서의 sms 메시지 식별자들의 관리를 위한 방법들, 장치들 및 컴퓨터 프로그램 물건들 | |
WO2012155434A1 (zh) | 一种数据传输的方法、装置及eNB | |
WO2020085969A1 (en) | Methods for handling link failures in integrated access backhaul (iab) networks | |
EP3915213A1 (en) | Network nodes and methods supporting multiple connectivity | |
KR20220021332A (ko) | 모바일 네트워크에서 에지 컴퓨팅 서비스 지속성을 지원하기 위한 방법 및 장치 | |
WO2019085635A1 (zh) | 确定以太网mac地址的方法及装置 | |
WO2015113233A1 (zh) | 能力信息上报的方法和装置 | |
JP2009177410A (ja) | 移動通信システム、基地局制御装置、基地局及び、通信接続方法 | |
WO2015103780A1 (zh) | 一种承载电路语音业务的方法及装置 | |
WO2020199892A1 (zh) | 无线通信***中的切换方法、装置及*** | |
CN104284383A (zh) | 一种保持业务连续性的方法和装置 | |
WO2017156704A1 (zh) | 数据通道建立及数据包传输方法、终端、服务器及*** | |
WO2012006927A1 (zh) | 一种建立承载的方法、***和设备 |
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: 11806269 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2011806269 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011806269 Country of ref document: EP |