[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN100466630C - Iub interface data transmission method and system in mobile communication network - Google Patents

Iub interface data transmission method and system in mobile communication network Download PDF

Info

Publication number
CN100466630C
CN100466630C CNB2006101594500A CN200610159450A CN100466630C CN 100466630 C CN100466630 C CN 100466630C CN B2006101594500 A CNB2006101594500 A CN B2006101594500A CN 200610159450 A CN200610159450 A CN 200610159450A CN 100466630 C CN100466630 C CN 100466630C
Authority
CN
China
Prior art keywords
node
frame
data frame
layer
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CNB2006101594500A
Other languages
Chinese (zh)
Other versions
CN1960340A (en
Inventor
蓝海青
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
XFusion Digital Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CNB2006101594500A priority Critical patent/CN100466630C/en
Publication of CN1960340A publication Critical patent/CN1960340A/en
Application granted granted Critical
Publication of CN100466630C publication Critical patent/CN100466630C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J13/00—Code division multiplex systems
    • H04J13/10—Code generation
    • H04J13/12—Generation of orthogonal codes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2002—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant
    • G06F11/2005—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant using redundant communication controllers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2002—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant
    • G06F11/2007—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant using redundant communication media
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G06Q20/123—Shopping for digital content
    • G06Q20/1235—Shopping for digital content with control of digital rights management [DRM]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/385—Payment protocols; Details thereof using an alias or single-use codes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G06Q30/0277—Online advertisement
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0609—Buyer or seller confidence or verification
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services
    • G06Q50/188—Electronic negotiation
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/16—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for devices exhibiting advertisements, announcements, pictures or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0602—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using antenna switching
    • H04B7/0604—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using antenna switching with predefined switching scheme
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0837—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station using pre-detection combining
    • H04B7/084—Equal gain combining, only phase adjustments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
    • H04B7/15535—Control of relay amplifier gain
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0041—Arrangements at the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045—Arrangements at the receiver end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0064—Concatenated codes
    • H04L1/0066—Parallel concatenated codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0067—Rate matching
    • H04L1/0068—Rate matching by puncturing
    • H04L1/0069—Puncturing patterns
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0071—Use of interleaving
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/02—Arrangements for detecting or preventing errors in the information received by diversity reception
    • H04L1/06—Arrangements for detecting or preventing errors in the information received by diversity reception using space diversity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1835—Buffer management
    • H04L1/1841—Resequencing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/12—Arrangements for remote connection or disconnection of substations or of equipment thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/287—Remote access server, e.g. BRAS
    • H04L12/2874—Processing of data for distribution to the subscribers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40052—High-speed IEEE 1394 serial bus
    • H04L12/40078—Bus configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40169—Flexible bus arrangements
    • H04L12/40176—Flexible bus arrangements involving redundancy
    • H04L12/40195—Flexible bus arrangements involving redundancy by using a plurality of nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/44—Star or tree networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/22—Traffic shaping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/43—Assembling or disassembling of packets, e.g. segmentation and reassembly [SAR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/621—Individual queue per connection or flow, e.g. per VC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0042—Intra-user or intra-terminal allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H04L5/0082—Timing of allocation at predetermined intervals
    • H04L5/0083—Timing of allocation at predetermined intervals symbol-by-symbol
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/065—Network architectures or network communication protocols for network security for supporting key management in a packet data network for group communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1441—Countermeasures against malicious traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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]
    • 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/168—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/253—Telephone sets using digital voice transmission
    • H04M1/2535—Telephone sets using digital voice transmission adapted for voice communication over an Internet Protocol [IP] network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/0024—Services and arrangements where telephone services are combined with data services
    • H04M7/0057—Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H04M7/0066—Details of access arrangements to the networks
    • H04M7/0069—Details of access arrangements to the networks comprising a residential gateway, e.g. those which provide an adapter for POTS or ISDN terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61—Network physical structure; Signal processing
    • H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
    • H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
    • H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
    • H04N21/64738—Monitoring network characteristics, e.g. bandwidth, congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
    • H04N21/64784—Data processing by the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/143—Downlink power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/245—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account received signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/38—TPC being performed in particular situations
    • H04W52/46—TPC being performed in particular situations in multi-hop networks, e.g. wireless relay networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/38—TPC being performed in particular situations
    • H04W52/48—TPC being performed in particular situations during retransmission after error or non-acknowledgment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/02—Hybrid access
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/1608—Error detection by comparing the output signals of redundant hardware
    • G06F11/1625—Error detection by comparing the output signals of redundant hardware in communications, e.g. transmission, interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2101—Auditing as a secondary aspect
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2149—Restricted operating environment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0891—Space-time diversity
    • H04B7/0894—Space-time diversity using different delays between antennas
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15507—Relay station based processing for cell extension or control of coverage area
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1835—Buffer management
    • H04L1/1845—Combining techniques, e.g. code combining
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0096—Channel splitting in point-to-point links
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40208—Bus networks characterized by the use of a particular bus standard
    • H04L2012/40241—Flexray
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40267—Bus for use in transportation systems
    • H04L2012/40273—Bus for use in transportation systems the transportation system being a vehicle
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/12—Details relating to cryptographic hardware or logic circuitry
    • H04L2209/127—Trusted platform modules [TPM]
    • 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/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/22—TPC being performed according to specific parameters taking into account previous information or commands
    • H04W52/225—Calculation of statistics, e.g. average or variance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/241—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account channel quality metrics, e.g. SIR, SNR, CIR or Eb/lo
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/242—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account path loss
    • 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
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Computer Hardware Design (AREA)
  • General Business, Economics & Management (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Bioethics (AREA)
  • Multimedia (AREA)
  • Tourism & Hospitality (AREA)
  • Databases & Information Systems (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Game Theory and Decision Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Technology Law (AREA)
  • Medical Informatics (AREA)
  • Human Resources & Organizations (AREA)
  • Primary Health Care (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention is used for improving the transmission efficiency of Iub interface and uses SDTP protocol to make data transmission of Iub interface. For each FP layer connection, the bottom layer needs to provide two links; when the length of FP frame is less than M bytes, one of said links maps the IP address and UDP port number to the SDTP node number and MUX-AL port number; when the length of FP frame is more than M bytes, another link directly uses IP address and UDP to package and adopt D-AL to bear.

Description

Iub interface data transmission method and system in mobile communication network
Technical Field
The invention relates to the field of mobile communication, in particular to an Iub interface data transmission technology in a mobile communication network.
Background
Wideband Code Division Multiple Access (WCDMA for short) is one of the three main standards of the 3rd Generation (3G for short), it inherits the characteristics of high standardization degree and good openness of the existing Global system for mobile communications (GSM for short), has good compatibility and interoperability with GSM network, and is one of the development trends of future mobile communications.
In a WCDMA system, a Radio Access Network (RAN) includes a Radio Network Controller (RNC) and a Node B (Node B) serving as a base station. Each Node B is used for receiving User Equipment (UE) signals in the administered range, and summarizing the signals to the RNC through a transmission channel after processing; the RNC is used for processing the information transmitted by the Node B in a centralized way and sending the processed information to the UE through the Node B.
In order to save the cost of the RNC when building a network, one RNC is usually required to provide a large area coverage, which connects and controls a plurality of Node bs, and the Node bs connected to it may be far away from the RNC, which may be up to hundreds of kilometers, and the Node bs are also far away from each other. Node B and RNC are connected through Iub interface.
The Iub interface Protocol includes Asynchronous Transfer Mode (ATM) and Internet Protocol (IP). Because the ATM network and the IP network of Wideband Code Division Multiple Access (WCDMA for short) are developed, and the transmission of the Iub interface mainly uses the ATM network or the IP network, the ATM and the IP network can fully use the existing ATM network or the IP network with low cost and high bandwidth and statistical multiplexing, so as to reduce the system transmission cost.
The most dominant transport employed by the current Iub interface is still the end-to-end primary cluster (E1/T1) transport mode. Wherein, E1 is the bandwidth rate standard of the digital hierarchy first group (or called group) of the pulse code modulation multiplexing system in europe, which comprises 32 channels of 64 kilobits per second (kbit/s), and the bandwidth rate of the first group is 2.048 megabits per second (Mbit/s). T1 is a north american, japanese pulse Code Modulation ("PCM") multiplex system digital hierarchy first group (or "basis group") bandwidth rate standard that includes 24 telephone channels with a bandwidth rate of 1.544Mbit/s, where each channel is 64 kbit/s.
Currently, when an Iub interface adopts an IP mode for Transmission, a Stream Control Transmission Protocol (SCTP) is used to carry control plane data, and the specific Protocol is as follows: NodeB Application Part (NodeB Application Part, abbreviated "NBAP")/STCP/Internet Protocol (Internet Protocol, abbreviated "IP")/multi-Protocol/High-level data Link Control (High-level data Link Control, abbreviated "HDLC")/E1; the method adopts a User datagram protocol (User datagram protocol, abbreviated as 'UDP') to bear wireless User plane data, and the specific protocol is as follows: frame protocol (FrameProtocol, abbreviated as "FP")/UDP/IP/multiprotocol/HDLC/E1; a Transmission Control Protocol (TCP) is used to carry operation and maintenance data, and the specific Protocol is as follows: operation maintenance/TCP/IP/multi-protocol/HDLC/E1.
In practical applications, there are the following problems: when the Iub interface adopts E1/T1 transmission end to end, the transmission efficiency is very low.
The main reason for this is that when ATM and IP technologies are initially developed, the bandwidth of the bearer network is considered to be large enough, and the development focuses mainly on the forwarding rate rather than on the transmission efficiency, so the transmission efficiency of both ATM and IP is low. However, when E1/T1 is used to transmit large bandwidth service data end to end between Node B and RNC, the bandwidth of E1/T1 is not large, and the transmission cost per bit is relatively high, so it is not economical to transmit large bandwidth data service between Node B and RNC. For operators, this transmission method is not favorable for reducing the number of E1/T1 used for transmission in WCDMA network, and cannot reduce the construction cost and maintenance cost, and cannot guarantee profitability of operators.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and a system for transmitting data of an Iub interface in a mobile communication network, so that the transmission efficiency of the Iub interface is improved.
In order to achieve the above object, the present invention provides a method for transmitting data of an Iub interface in a mobile communication network, comprising the following steps:
setting a node number corresponding to an IP address of the node and a user datagram protocol port number or the node number and a multiplexing micro-frame port number at a lower layer of an IP layer in advance;
and the source node encapsulates and sends the data frame on the lower layer of the IP layer by using the node number or the node number and the multiplexing micro-frame port number of the target node, and the target node finds the corresponding IP address and the corresponding user datagram protocol port number according to the node number or the node number and the multiplexing micro-frame port number of the received data frame to complete the reception of the data frame.
If the source node sends a data frame adapted by a direct adaptation layer, the node number of a target node is used for packaging and sending the data frame at the lower layer of the IP layer, and the target node finds a corresponding IP address and a corresponding user datagram protocol port number according to the node number of the received data frame to complete the receiving of the data frame;
if the source node sends the data frame adapted by the multiplexing adaptation layer, the node number and the multiplexing micro-frame port number of the target node are used for packaging and sending the data frame at the lower layer of the IP layer, and the target node finds out the corresponding IP address and the corresponding user datagram protocol port number according to the node number and the multiplexing micro-frame port number of the received data frame to complete the receiving of the data frame.
In addition, in the method, if the frame protocol data frame sent to the user equipment is smaller than the specified length, the frame protocol data frame is adapted by the multiplexing adaptation layer;
and if the frame protocol data frame sent to the user equipment is greater than or equal to the specified length, the frame protocol data frame is adapted by the direct adaptation layer.
Further in the method, the data frame comprises a frame for transmitting operation maintenance data and/or a frame for transmitting base station node application part data;
the frame for transmitting operation maintenance data and the frame for transmitting base station node application part data are adapted by the direct adaptation layer.
In addition, in the method, the lower layer of the IP layer is a simple data transfer protocol layer.
In addition, the method also comprises the following steps:
when the target node receives the data frame, whether the node number of the data frame is the node number of the node is judged, if yes, the corresponding IP address and the user datagram protocol port number are found according to the node number or the node number of the received data frame and the multiplexing micro-frame port number.
In addition, in the method, the source node is a radio network controller, and the target node is a base station node; or,
the source node is a base station node, and the target node is a wireless network controller.
Further in the method, the radio network controller is provided with a different node number for each of the base station nodes.
The invention also provides an Iub interface data transmission system in the mobile communication network, which comprises a source node and a target node, wherein the source node comprises: an encapsulation module, configured to encapsulate a data frame at a lower layer of an IP layer according to a node number, or a node number and a multiplexing micro-frame port number, which are preset at the lower layer of the IP layer and correspond to an IP address of a target node and a user datagram protocol port number; the sending module is used for sending the data frame encapsulated by the encapsulating module to a target node;
the target node comprises a searching and receiving module which is used for finding out the corresponding IP address and the corresponding user datagram protocol port number according to the node number or the node number of the received data frame and the multiplexing micro-frame port number, and completing the receiving of the data frame.
The encapsulation module of the source node encapsulates the data frame adapted by the direct adaptation layer at the lower layer of the IP layer by using the node number of the target node, and the search receiving module of the target node finds the corresponding IP address and the user datagram protocol port number according to the node number of the received data frame to complete the receiving of the data frame;
and the searching and receiving module of the target node finds the corresponding IP address and the corresponding user datagram protocol port number according to the node number and the multiplexing micro-frame port number of the received data frame, and finishes the receiving of the data frame.
In addition, in the system, the source node further includes a determining module, configured to determine whether a frame protocol data frame sent to the user equipment is smaller than a specified length before the data frame is encapsulated by the encapsulating module, and if so, indicate that the frame protocol data frame is adapted by the multiplexing adaptation layer, otherwise, indicate that the frame protocol data frame is adapted by the direct adaptation layer.
Through comparison, the technical scheme of the invention is mainly different from the prior art in that a node number corresponding to the IP address and the UDP port number of the node or the node number and the multiplexing micro-frame port number are arranged on the lower layer of the IP layer in advance. If the source node sends the data frame adapted by the direct adaptation layer, the node number of the target node is used for packaging and sending the data frame on the lower layer of the IP layer, and the target node finds the corresponding IP address and the user datagram protocol port number according to the node number of the received data frame to complete the receiving of the data frame; if the source node sends the data frame adapted by the multiplexing adaptation layer, the node number of the target node and the multiplexing micro-frame port number are used for packaging and sending the data frame at the lower layer of the IP layer, and the target node finds the corresponding IP address and the corresponding user datagram protocol port number according to the node number of the received data frame and the multiplexing micro-frame port number, so that the data frame is received. The problem that upper layer Data of the Iub interface is loaded in a Simple Data Transport Protocol (SDTP for short) is solved, so that the information Data can be loaded and sent in an SDTP mode, and the transmission efficiency of the Iub interface is improved. The profitability of the operator can be increased, since an increase in the transmission efficiency will directly reduce the investment costs and the operating costs.
Because the frame for transmitting the operation maintenance data is the control information and belongs to the same connection information with the frame for transmitting the application part data of the base station node, if the sent data frame is the frame for transmitting the operation maintenance data or the frame for transmitting the application part data of the base station node, the data frame is adapted by the direct adaptation layer, and the transmission efficiency of the Iub interface is further improved.
Because the frame protocol data frame may belong to a plurality of different connections, the adaptation is determined by the direct adaptation layer or the multiplexing adaptation layer according to the size of the frame protocol data frame, thereby further fully utilizing the SDTP protocol with high transmission efficiency and greatly reducing the transmission cost.
Drawings
Fig. 1 is a flow chart of transmission of operation maintenance data in an Iub interface data transmission method in a mobile communication network according to a first embodiment of the present invention;
fig. 2 is a flow chart of receiving operation maintenance data in an Iub interface data transmission method in a mobile communication network according to a first embodiment of the present invention;
fig. 3 is a flowchart for transmitting NBAP data in an Iub interface data transmission method in a mobile communication network according to a second embodiment of the present invention;
fig. 4 is a flow chart of NBAP data reception in an Iub interface data transmission method in a mobile communication network according to a second embodiment of the present invention;
fig. 5 is a flowchart for transmitting FP frame data in an Iub interface data transmission method in a mobile communication network according to a third embodiment of the present invention;
fig. 6 is a flowchart of receiving FP frame data in an Iub interface data transmission method in a mobile communication network according to a third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings.
The core of the present invention is that if a source node transmits a data frame adapted by a direct adaptation layer (D-AL), an IP address and a UDP port number of a target node are mapped to a node number of the target node, the data frame is encapsulated and transmitted at a lower layer of an IP layer using the node number, and the target node finds a corresponding IP address and UDP port number according to a node number of the received data frame, thereby completing reception of the data frame. If the source node sends the data frame adapted by a multiplexing adaptation layer (MUX-AL), mapping the IP address and the UDP port number of the target node into the node number and the multiplexing micro-frame port number of the target node, packaging and sending the data frame on the lower layer of the IP layer by using the node number and the multiplexing micro-frame port number, finding the corresponding IP address and the corresponding user datagram protocol port number by the target node according to the node number and the multiplexing micro-frame port number of the received data frame, and finishing the receiving of the data frame.
Specifically, as the WCDMA Iub interface adopts the SDTP transport bearer mode as shown in table 1, NBAP is directly carried by the direct adaptation layer, and as the Operation and Maintenance (OM) data is generally carried by TCP/IP protocol, OM/TCP/IP/D-AL is carried. For FP frame, there are two carrying modes, the first one is that FP uses multiplex adaptive layer directly, the other one is that FP/UDP/IP/D-AL carries mode, and carries on IP packet slicing function. And determining the specific bearer mode adopted by the FP according to the length of the FP, for example, when the length of the FP is less than or equal to a predetermined length M, adopting a first bearer mode, and when the length of the FP is greater than M, adopting a second bearer mode, wherein the length unit of M is bytes.
Figure C200610159450D00121
TABLE 1
Since one unidirectional connection negotiated through the NBAP layer supporting IP as an FP frame contains a source IP address, a source UDP port number, a destination IP address, and a destination UDP port number. That is, when the unidirectional connection is an uplink connection, the source IP address and the source UDP port number are the IP address of NodeB and the UDP port number of NodeB, and the destination IP address and the destination UDP port number are the IP address of RNC and the UDP port number of RNC; when the unidirectional connection is downlink connection, the source IP address and the source UDP port number are the IP address of the RNC and the UDP port number of the RNC, and the target IP address and the target UDP port number are the IP address of the NodeB and the UDP port number of the NodeB.
In the scheme of the invention, the mapping of the target IP address and the target UDP port number to the node number of the target node or the node number of the target node and the multiplexing micro-frame port number is determined according to whether the sent data frame is a data frame adaptive to a direct adaptation layer or a data frame adaptive to a multiplexing adaptation layer. If the mapping is the node number of the target node, the source node encapsulates and sends the data frame by using the node number of the target node on the lower layer of the IP layer, and the target node finds the corresponding IP address and UDP port number according to the node number of the received data frame, thereby completing the receiving of the data frame. If the mapping is the node number of the target node and the multiplexing micro-frame port number, the source node encapsulates and sends the data frame on the lower layer of the IP layer by using the node number of the target node and the multiplexing micro-frame port number, and the target node finds the corresponding IP address and the corresponding UDP port number according to the node number of the received data frame and the multiplexing micro-frame port number, thereby completing the receiving of the data frame.
It should be noted that, for the RNC, the same physical port may carry several nodebs, and a MUX-AL port number supported by one node number may not be sufficient, so that the RNC is required to support multiple node numbers on the same physical port.
The core of the present invention is described above, and a first embodiment of the present invention will be explained in detail below based on the principle. In the embodiment, the operation maintenance data of the WCDMA Iub interface is transmitted in an SDTP mode, namely, an operation maintenance transmission channel is firstly established by the WCDMA Iub interface through an SDTP protocol, then an NBAP transmission channel is established through the operation maintenance and the SDTP protocol, and finally an FP frame transmission channel is established through the NBAP, the operation maintenance and the SDTP protocol.
The transmission flow of the operation maintenance data is shown in fig. 1. It should be noted that, before entering step 101, the APP (application) layer needs to configure a source node number and a destination node number for operation and maintenance data transmission. The source node number corresponds to an IP address and a UDP port number of the source node, and the destination node number corresponds to an IP address and a UDP port number of the destination node.
Because the same physical port of the RNC may have several nodebs, and the MUX-AL port number supported by one node number may be insufficient, a source node number of the RNC is configured for each NodeB, and RNC source node numbers corresponding to different nodebs are different.
In step 101, the APP layer implements the OM/TCP/IP protocol stack for the operation maintenance data to be transmitted, and sends the IP packet to the D-AL layer and the destination node number to the SDTP layer.
And then, entering the step 102, carrying out D-AL frame encapsulation by the D-AL layer, and sending the encapsulated data frame to the SDTP layer. Because the frame for transmitting the operation maintenance data is the control information and belongs to the same connection information, the data frame is adapted by the direct adaptation layer, and the transmission efficiency of the Iub interface can be further improved.
Then, step 103 is entered, where the SDTP layer performs SDTP frame encapsulation, identifies the protocol type of the APP as IP, and sets a destination node number, that is, encapsulates the data frame in the SDTP layer by using the node number of the destination node.
Then, step 104 is performed, and the data frame encapsulated by the SDTP layer is processed and transmitted by the layers below a High-Level DataLink Control (HDLC) layer of the source node.
The flow of receiving operation maintenance data is shown in fig. 2. Likewise, before entering step 201, the APP layer needs to configure a source node number and a destination node number for operation and maintenance data transmission. The source node number corresponds to an IP address and a UDP port number of the source node, and the destination node number corresponds to an IP address and a UDP port number of the destination node. Because the same physical port of the RNC may have several nodebs, and the MUX-AL port number supported by one node number may be insufficient, a source node number of the RNC is configured for each NodeB, and RNC source node numbers corresponding to different nodebs are different.
In step 201, the HDLC-like layers of the node receive data from the line and transmit the data up to the SDTP layer.
Next, step 202 is entered to determine whether the destination node number of the received SDTP frame is the node number of the node. If the node number is the node number of the node, the node is a target node, and step 203 is entered, otherwise, the node is not the target node, and step 207 is entered.
In step 203, the SDTP layer performs frame stripping and extracts the protocol identifier and the destination node number.
Then, step 204 is entered, whether the protocol type is IP is judged according to the extracted protocol identifier, if yes, step 205 is entered, otherwise, step 207 is entered.
In step 205, the D-AL layer performs frame stripping and transmits the IP packet to the APP layer.
Then, step 206 is entered, the APP layer receives the IP packet data from the D-AL layer and the destination node number of the SDTP layer, and the APP layer resolves the OM data through the OM/TCP/IP protocol stack, thereby completing the receiving process.
If it is determined in step 202 that the destination node number of the received SDTP frame is not the node number of the node itself, or it is determined in step 204 that the protocol type is not IP according to the retrieved protocol identifier, step 207 is entered, and other processing is performed on the received data, thereby completing the receiving process.
Therefore, the IP address and the UDP port number of the target node are mapped to the node number of the target node on the SDTP layer, so that the problem that upper layer data of the Iub interface is borne in the SDTP is solved, information data can be borne and sent in the SDTP mode, and the transmission efficiency of the Iub interface is improved. The profitability of the operator can be increased, since an increase in the transmission efficiency will directly reduce the investment costs and the operating costs.
A second embodiment of the present invention relates to an Iub interface data transmission method in a mobile communication network, and in the present embodiment, NBAP data of a WCDMA Iub interface is transmitted in an SDTP manner. This embodiment is substantially the same as the first embodiment, and differs therefrom only in that operation and maintenance data is carried over the Iub interface in the first embodiment, while NBAP data is carried over the Iub interface in the present embodiment.
The flow of NBAP data transmission is shown in fig. 3. It should be noted that, before entering step 301, the APP layer needs to configure a source node number and a destination node number for NBAP data transmission. The source node number corresponds to an IP address and a UDP port number of the source node, and the destination node number corresponds to an IP address and a UDP port number of the destination node.
In step 301, the APP layer implements an OM/TCP/IP protocol stack for NBAP data to be transmitted, and sends an IP packet to the D-AL layer and a destination node number to the SDTP layer.
Steps 302 to 304 are completely the same as steps 102 to 104, and are not described herein again.
The flow of NBAP data reception is shown in fig. 4. Likewise, before entering step 401, the APP layer needs to configure the source node number and destination node number for NBAP data transmission. The source node number corresponds to an IP address and a UDP port number of the source node, and the destination node number corresponds to an IP address and a UDP port number of the destination node.
Steps 401 to 403 are completely the same as steps 201 to 203, and are not described herein again.
In step 404, determining whether the protocol type is NBAP according to the retrieved protocol identifier, if so, entering step 405, otherwise, entering step 407.
Then, step 405 is entered, the D-AL layer performs frame dropping and transmits NBAP data to the APP layer.
Then, step 406 is entered, and the APP layer receives the NBAP data from the D-AL layer and the destination node number of the SDTP layer, completing the receiving process.
If it is determined in step 402 that the destination node number of the received SDTP frame is not the node number of the node itself, or it is determined in step 404 that the protocol type is not NBAP according to the retrieved protocol identifier, step 407 is entered, and other processing is performed on the received data, thereby completing the receiving process.
It is not easy to find that, the embodiment can also solve the problem that the upper layer data of the Iub interface is carried in the SDTP, so that the information data can be carried and sent in the SDTP manner, thereby improving the transmission efficiency of the Iub interface. The profitability of the operator can be increased, since an increase in the transmission efficiency will directly reduce the investment costs and the operating costs. In addition, because the frame for transmitting the NBAP data is control information and belongs to the same connection information, the data frame is adapted by the direct adaptation layer, so that the transmission efficiency of the Iub interface can be further improved.
A third embodiment of the present invention relates to a method for transmitting data of an Iub interface in a mobile communication network, and in the present embodiment, FP frame data of a WCDMA Iub interface is transmitted in an SDTP manner.
In this embodiment, before transmitting FP frame data, a connection between the source node and the target node, that is, a connection between the NodeB and the RNC, needs to be established first.
Specifically, first, through OM negotiation, the APP layer needs to configure a source node number and a destination node number for FP frame data transmission. The source node number corresponds to an IP address and a UDP port number of the source node, and the destination node number corresponds to an IP address and a UDP port number of the destination node. Because the same physical port of the RNC may have several nodebs, and the MUX-AL port number supported by one node number may be insufficient, a source node number of the RNC is configured for each NodeB, and RNC source node numbers corresponding to different nodebs are different.
Secondly, the source node and the target node finish Iub IP transmission negotiation of NBAP in the APP layer, and negotiate IP address and UDP port number of IP transmission.
Finally, the APP layers of the source node and the target node complete the mapping of the IP address, the UDP port number, the node number and the multiplexing micro-frame port number, and the mapping relation is as follows:
downlink connection: (IPRNC, UDPRNC, IPNodeB, UDPNodeB) - > (NodeB, PortNodeB)
Uplink connection: (IPNodeB, UDPNodeB, IPRNC, UDPRNC) - > (NodeRNC, PortRNC)
That is, for downlink connection, mapping an IP address of an RNC, a UDP port number of the RNC, an IP address of a NodeB, and a UDP port number of the NodeB to a node number of the NodeB and a multiplexing micro-frame port number of the NodeB; for uplink connection, the IP address of the NodeB, the UDP port number of the NodeB, the IP address of the RNC and the UDP port number of the RNC are mapped into the node number of the RNC and the multiplexing micro-frame port number of the RNC. It should be noted that both the RNC and the NodeB need to maintain the uplink and downlink connection relationship at the same time.
After the connection between the NodeB and the RNC is completed, the FP frame data may be transmitted, and the transmission flow of the FP frame data is shown in fig. 5.
In step 501, the APP layer receives upper FP frame data, and sends a destination port number, i.e., a multiplexing micro-frame port number, to the MUX-AL layer, and sends a destination node number to the SDTP layer, so that when the FP frame needs to be adapted by the MUX-AL layer, the MUX-AL layer can perform MUX-AL frame encapsulation on a payload by using the destination port number.
Then, the process proceeds to step 502, and determines whether the FP frame length is smaller than the predetermined length M, if not, it indicates that the data frame cannot be multiplexed, and proceeds to step 503, otherwise, it indicates that the data frame can be multiplexed, and proceeds to step 505.
In step 503, the APP layer implements the FP/UDP/IP protocol stack on the FP data frame to be transmitted, and sends the FP/UDP/IP protocol stack to the D-AL layer after completing the IP packet fragmentation.
In step 504, the D-AL layer performs D-AL frame encapsulation and sends the encapsulated data frame to the SDTP layer.
If the length of the FP frame is determined to be smaller than the predetermined length M in step 502, that is, the data frame can be multiplexed, step 505 is performed, the FP frame is issued by the APP layer to the MUX-AL layer, the MUX-AL layer performs MUX-AL frame encapsulation on the payload by using the multiplexing micro-frame port number to distinguish data sent to different users of the same node, and the data frame encapsulated by the MUX-AL layer is sent to the SDTP layer.
Because the FP data frame may belong to a plurality of different connections, the direct adaptation layer or the multiplexing adaptation layer is used for adaptation according to the size of the FP data frame, thereby further fully utilizing the SDTP protocol with high transmission efficiency and greatly reducing the transmission cost.
Then, step 506 is entered, the SDTP layer performs SDTP frame encapsulation on the data frame encapsulated by the adaptation layer by using the destination node number, and identifies the protocol type of the APP as WCDMA FP.
Then, step 507 is performed, and the data frames encapsulated by the SDTP layer are processed and transmitted by the layers below the HDLC-like layer of the source node.
In this embodiment, the source node may multiplex the FP frame and then transmit the FP frame, so that it is necessary to distinguish a node to which the data frame belongs by a node number of a target, and further distinguish different users of the node to which the data frame belongs by multiplexing a micro-frame port number.
Before receiving FP frame data, the connection between the NodeB and the RNC is also required, and the connection establishment method is the same as the above method, and is not described herein again.
The flow of receiving FP frame data is as shown in fig. 6, in step 601, the layers below the HDLC-like layer receive data from the line and transmit the data up to the SDTP layer, which is exactly the same as step 201.
Then, step 602 is entered to determine whether the destination node number of the received SDTP frame is the node number of the node. If the node number is the node number of the node, the node is a target node, the step 603 is entered, otherwise, the node is not the target node, the step 605 is entered, and other processing is performed on the received data, and the receiving process is completed.
In step 603, the SDTP layer performs SDTP frame unpacking, and takes out the protocol type, multiplexing identifier, and node number of the APP.
Then, step 604 is entered to determine whether the APP protocol type is WCDMA FP, if not, step 605 is entered to perform other processing on the received data to complete the receiving process, and if the APP protocol type is WCDMA FP, step 606 is entered.
In step 606, it is determined whether the data frame is a multiplexed data frame according to the value of the multiplexing flag. If the data frame is determined to be a multiplexed data frame, step 609 is entered, otherwise step 607 is entered.
In step 607, the D-AL layer defragments and feeds the data into the APP layer.
Then, step 608 is entered, the IP packet fragment reassembly function is completed in the APP layer, the FP frame, the IP address and the UDP port number are taken out from the UDP/IP protocol stack, and the receiving process is completed.
If the data frame is determined to be a multiplexed data frame in step 606, step 609 is entered, and MUX-AL deframing is performed in the MUX-AL layer, and the MUX-AL layer provides the payload of the MUX-AL to the APP layer.
Then, step 610 is entered, the APP acquires the IP address and UDP port number corresponding to the data frame according to the correspondence between the node number and multiplexing micro-frame port number of the node and the IP address and UDP port number, and acquires the payload of the MUX-AL as a process of receiving FP frame data.
A fourth embodiment of the present invention relates to an Iub interface data transmission system in a mobile communication network, comprising a source node and a target node.
The source node comprises: the judging module is used for judging whether the sent data frame is smaller than the specified length; an encapsulation module, configured to encapsulate a data frame at a lower layer of an IP layer of a target node according to a node number, or a node number and a multiplexing micro-frame port number, which are preset at the lower layer of the IP layer of the target node and correspond to an IP address and a UDP port number of the target node; and the sending module is used for sending the data frame encapsulated by the encapsulating module to the target node.
The target node comprises a searching and receiving module which is used for finding out a corresponding IP address and a corresponding UDP port number according to the node number or the node number of the received data frame and the multiplexing micro-frame port number so as to complete the receiving of the data frame.
Specifically, the determining module of the source node determines whether the data frame is smaller than a specified length before the encapsulating module encapsulates the data frame, and if so, indicates that the data frame is adapted by the multiplexing adaptation layer, otherwise, indicates that the frame protocol data frame is adapted by the direct adaptation layer.
For the data frame adapted by the direct adaptation layer, the encapsulation module encapsulates the data frame at the lower layer of the IP layer by using the node number of the target node, and the search receiving module of the target node finds the corresponding IP address and UDP port number according to the node number of the received data frame to complete the receiving of the data frame; for the data frame adapted by the multiplexing adaptation layer, the encapsulation module encapsulates the data frame at the lower layer of the IP layer by using the node number of the target node and the multiplexing micro-frame port number, and the search receiving module of the target node finds the corresponding IP address and UDP port number according to the node number of the received data frame and the multiplexing micro-frame port number, thereby completing the receiving of the data frame. Therefore, the problem that upper layer data of the Iub interface is loaded in the SDTP is solved, and the information data can be loaded and sent in the SDTP mode, thereby improving the transmission efficiency of the Iub interface. The profitability of the operator can be increased, since an increase in the transmission efficiency will directly reduce the investment costs and the operating costs.
While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

Claims (11)

1. A method for Iub interface data transmission in mobile communication network is characterized in that the method comprises the following steps:
setting a node number corresponding to an IP address of the node and a user datagram protocol port number or the node number and a multiplexing micro-frame port number at a lower layer of an IP layer in advance;
and the source node encapsulates and sends the data frame on the lower layer of the IP layer by using the node number or the node number and the multiplexing micro-frame port number of the target node, and the target node finds the corresponding IP address and the corresponding user datagram protocol port number according to the node number or the node number and the multiplexing micro-frame port number of the received data frame to complete the reception of the data frame.
2. The method of claim 1, wherein if the source node sends a data frame adapted by a direct adaptation layer, the node number of a target node is used to encapsulate and send the data frame on a lower layer of the IP layer, and the target node finds a corresponding IP address and a user datagram protocol port number according to the node number of the received data frame to complete reception of the data frame;
if the source node sends the data frame adapted by the multiplexing adaptation layer, the node number and the multiplexing micro-frame port number of the target node are used for packaging and sending the data frame at the lower layer of the IP layer, and the target node finds out the corresponding IP address and the corresponding user datagram protocol port number according to the node number and the multiplexing micro-frame port number of the received data frame to complete the receiving of the data frame.
3. The method of claim 2, wherein if the frame protocol data frame sent to the user equipment is smaller than a specified length, the frame protocol data frame is adapted by the multiplexing adaptation layer;
and if the frame protocol data frame sent to the user equipment is greater than or equal to the specified length, the frame protocol data frame is adapted by the direct adaptation layer.
4. The method of claim 2, wherein the data frame comprises a frame for transmitting operation maintenance data and/or a frame for transmitting base station node application part data;
the frame for transmitting operation maintenance data and the frame for transmitting base station node application part data are adapted by the direct adaptation layer.
5. The method of claim 1, wherein the lower layer of the IP layer is a simple data transfer protocol layer.
6. The method for transmitting Iub interface data in a mobile communication network according to any one of claims 1 to 5, further comprising the steps of:
when the target node receives the data frame, whether the node number of the data frame is the node number of the node is judged, if yes, the corresponding IP address and the user datagram protocol port number are found according to the node number or the node number of the received data frame and the multiplexing micro-frame port number.
7. The method for data transmission over the Iub interface in a mobile communication network according to any one of claims 1 to 5, wherein the source node is a radio network controller, and the target node is a base station node; or,
the source node is a base station node, and the target node is a wireless network controller.
8. The method of claim 7, wherein the rnc is provided with a different node number corresponding to each of the base station nodes.
9. An Iub interface data transmission system in a mobile communication network comprises a source node and a target node, and is characterized in that the source node comprises an encapsulation module, a data frame encapsulation module and a data frame transmission module, wherein the encapsulation module is used for encapsulating the data frame at the lower layer of an IP layer according to a node number, or the node number and a multiplexing micro-frame port number, which are preset at the lower layer of the IP layer and correspond to an IP address of the target node and a user datagram protocol port number; the sending module is used for sending the data frame encapsulated by the encapsulating module to a target node;
the target node comprises a searching and receiving module which is used for finding out the corresponding IP address and the corresponding user datagram protocol port number according to the node number or the node number of the received data frame and the multiplexing micro-frame port number, and completing the receiving of the data frame.
10. The Iub interface data transmission system in a mobile communication network according to claim 9, wherein the encapsulation module of the source node encapsulates the data frame adapted by the direct adaptation layer at the lower layer of the IP layer using the node number of the target node, and the search receiving module of the target node finds the corresponding IP address and the user datagram protocol port number according to the node number of the received data frame to complete the reception of the data frame;
and the searching and receiving module of the target node finds the corresponding IP address and the corresponding user datagram protocol port number according to the node number and the multiplexing micro-frame port number of the received data frame, and finishes the receiving of the data frame.
11. The Iub interface data transmission system in a mobile communication network according to claim 9 or 10, wherein the source node further includes a determining module, configured to determine whether a frame protocol data frame sent to the user equipment is smaller than a specified length before the encapsulating module encapsulates the data frame, if so, indicate that the frame protocol data frame is adapted by the multiplexing adaptation layer, otherwise, indicate that the frame protocol data frame is adapted by the direct adaptation layer.
CNB2006101594500A 2006-09-21 2006-09-21 Iub interface data transmission method and system in mobile communication network Active CN100466630C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2006101594500A CN100466630C (en) 2006-09-21 2006-09-21 Iub interface data transmission method and system in mobile communication network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2006101594500A CN100466630C (en) 2006-09-21 2006-09-21 Iub interface data transmission method and system in mobile communication network

Publications (2)

Publication Number Publication Date
CN1960340A CN1960340A (en) 2007-05-09
CN100466630C true CN100466630C (en) 2009-03-04

Family

ID=38071835

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2006101594500A Active CN100466630C (en) 2006-09-21 2006-09-21 Iub interface data transmission method and system in mobile communication network

Country Status (1)

Country Link
CN (1) CN100466630C (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100574283C (en) 2007-06-12 2009-12-23 华为技术有限公司 Uplink and downlink transmission method and aggregation node
CN101183924B (en) * 2007-12-19 2010-09-29 华为技术有限公司 User datagram protocol multiplexing and multiplexing negotiation method and apparatus
CN107911415A (en) * 2017-10-20 2018-04-13 深圳市网心科技有限公司 Multiplex system and its method, the storage medium and terminal of TCP flow
CN113760799B (en) * 2020-06-03 2024-04-09 中车株洲电力机车研究所有限公司 Scalable communication method, device, computer equipment and storage medium of UPP interface

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001060023A1 (en) * 2000-02-08 2001-08-16 Telefonaktiebolaget Lm Ericsson (Publ) Using internet protocol (ip) in radio access network
WO2002049381A1 (en) * 2000-12-11 2002-06-20 Nokia Corporation Configuring a data transmission interface in a communication network
CN1406006A (en) * 2001-09-17 2003-03-26 华为技术有限公司 Method for identifying service quality of user's interface transmission network layer in wireless switch-in network
CN1780427A (en) * 2004-11-17 2006-05-31 华为技术有限公司 Interface parameter configuration of mobile telecommunication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001060023A1 (en) * 2000-02-08 2001-08-16 Telefonaktiebolaget Lm Ericsson (Publ) Using internet protocol (ip) in radio access network
WO2002049381A1 (en) * 2000-12-11 2002-06-20 Nokia Corporation Configuring a data transmission interface in a communication network
CN1406006A (en) * 2001-09-17 2003-03-26 华为技术有限公司 Method for identifying service quality of user's interface transmission network layer in wireless switch-in network
CN1780427A (en) * 2004-11-17 2006-05-31 华为技术有限公司 Interface parameter configuration of mobile telecommunication system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
WCDMA系统Iub接口功能及协议栈. 陈兵.广西通信技术，第3期. 2005
WCDMA系统Iub接口功能及协议栈. 陈兵.广西通信技术，第3期. 2005 *

Also Published As

Publication number Publication date
CN1960340A (en) 2007-05-09

Similar Documents

Publication Publication Date Title
US7944943B2 (en) Method and apparatus for MAC layer inverse multiplexing in a third generation radio access network
US6671287B1 (en) Data transmission method in GPRS
CA2847074C (en) Method and apparatus for data transportation and synchronization between mac and physical layers in a wireless communication system
CN101388825B (en) Method and apparatus for transmitting data package of GPRS tunnel protocol
CN110365609B (en) Data packet segmentation method and device
US9078290B2 (en) Uplink transmission method, downlink transmission method, and convergence device
US9001654B2 (en) Enhanced multiplexing for single RLC entity
JP2005533418A (en) Apparatus, system and method for transmitting data having different QoS attributes
CN101369977A (en) Method, apparatus and system for transmitting data
JP2003512774A (en) Driving method of mobile radio network
WO2016050042A1 (en) Synchronous data processing method and device
WO2009026845A1 (en) Method for data transmitting and receiving, wireless access point apparatus, gateway and communication system
EP1472835B1 (en) Processing different size packet headers for a packet based conversational service in a mobile communications system
JP3872077B2 (en) Data transmission method using multi-frame
CN100514975C (en) Iub interface data transmission method in broadband CDMA network
CN100466630C (en) Iub interface data transmission method and system in mobile communication network
KR102067246B1 (en) Base station and method thereof for data packet transmission
JP2000349806A (en) Network having several network clusters for radio transmission of packet
KR20080015693A (en) Method and apparatus for buffer status report of ue in mobile communication system
TWI816496B (en) Methods and user equipment for wireless communication
JP4550897B2 (en) Information transmission in communication systems
EP2053798B1 (en) Method and device for data transmitting and receiving between radio network controller and station node
WO2006032203A1 (en) A radio access network and the communication method
JP2005123787A (en) Wireless access network system and data transfer method
KR20050089700A (en) Method and device for modification of mac header format in broadband wireless access specification

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20211223

Address after: 450046 Floor 9, building 1, Zhengshang Boya Plaza, Longzihu wisdom Island, Zhengdong New Area, Zhengzhou City, Henan Province

Patentee after: xFusion Digital Technologies Co., Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd.

TR01 Transfer of patent right