CN1738303A - Method for carrying out different service treatment according to different bearing network type - Google Patents

Method for carrying out different service treatment according to different bearing network type Download PDF

Info

Publication number
CN1738303A
CN1738303A CNA2004100584555A CN200410058455A CN1738303A CN 1738303 A CN1738303 A CN 1738303A CN A2004100584555 A CNA2004100584555 A CN A2004100584555A CN 200410058455 A CN200410058455 A CN 200410058455A CN 1738303 A CN1738303 A CN 1738303A
Authority
CN
China
Prior art keywords
network
functional entity
network type
bearer network
control layer
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.)
Granted
Application number
CNA2004100584555A
Other languages
Chinese (zh)
Other versions
CN100466645C (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.)
Huawei 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 CNB2004100584555A priority Critical patent/CN100466645C/en
Priority to PCT/CN2005/001273 priority patent/WO2006017985A1/en
Publication of CN1738303A publication Critical patent/CN1738303A/en
Application granted granted Critical
Publication of CN100466645C publication Critical patent/CN100466645C/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

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
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/02—Transmitters
    • H04B1/04—Circuits
    • H04B1/0483—Transmitters with multiple parallel paths
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/38—Transceivers, i.e. devices in which transmitter and receiver form a structural unit and in which at least one part is used for functions of transmitting and receiving
    • H04B1/40—Circuits
    • 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/2803—Home automation networks
    • 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/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/2809—Exchanging configuration information on appliance services in a home automation network indicating that an appliance service is present in a home automation network
    • 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
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/344—Out-of-band transfers
    • 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/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—Arrangements for allocating sub-channels of the transmission path 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—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • 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
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4541—Directories for service discovery
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/103—Media gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • 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/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • 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
    • 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/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • 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
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • 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
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/141—Systems for two-way working between two video terminals, e.g. videophone
    • H04N7/148—Interfacing a video terminal to a particular transmission medium, e.g. ISDN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • 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. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—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. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—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. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—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. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—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. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H04L2012/6445—Admission control
    • H04L2012/6462—Movable boundaries in packets or frames
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • 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
    • 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/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42085—Called party identification service
    • H04M3/42102—Making use of the called party identifier
    • 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. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—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, variance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—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, Eb/lo
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—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
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • 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
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

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)
  • Computing Systems (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Automation & Control Theory (AREA)
  • Bioethics (AREA)
  • Marketing (AREA)
  • Tourism & Hospitality (AREA)
  • Medical Informatics (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Human Resources & Organizations (AREA)
  • Primary Health Care (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Technology Law (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method for operating different service according to the different type of served network, comprising: A, the function entity of service control layer attains the type information of served network of present user apparatus; B, said function entity ensures the type of served network according to aforementioned type information and operates different service process. The method can make the relative function entity of IMS network service control layer ensure the type of present served network, for operating different service process according to the different type of served network.

Description

A kind of method of implementing the different business processing according to the different loading network type
Technical field
The present invention relates in professional Control Network, implement the technology that different business is handled, particularly a kind of method of in professional Control Network, implementing the different business processing according to the different loading network type.
Background technology
Along with the development of broadband network, the business that mobile communication system is carried out will not only be confined to traditional voice communication, will carry out gradually in conjunction with the multimedia service of multiple medium types such as audio frequency, video, picture and text.Multimedia service comprise present that business (presence), short message, webpage (WEB) are browsed, the combination of locating information, propelling movement business (PUSH), file-sharing etc. and above-mentioned data service, can satisfy user's multiple demand.
Under the promotion of the multiple application of multimedia, the standardized partnership projects of 3G (Third Generation) Moblie (3GPP) normal structure has been released IP-based IP multimedia subsystem, IMS (IMS) framework, purpose is to use a kind of standardized open architecture to realize diversified multimedia application in wireless communication system, offers more selection of user and abundanter impression.
(R5, Release5) stage have been introduced IMS domain, are called for short IMS, are superimposed upon on the packet switching network at 3GPP version 5.IMS is made up of CSCF (CSCF), MGCF (MGCF), media resource function (MRF) and home signature user server functional entitys such as (HSS), and wherein CSCF can be divided into serving CSCF (S-CSCF), proxy CSCF (P-CSCF) and three logic entities of inquiry CSCF (I-CSCF) again.S-CSCF is the service switching center of IMS, carries out session control, and peace preservation association's speech phase is in charge of user profile, produces charge information etc.; P-CSCF is the access point of terminal user access to IMS, finishes user's registration, is responsible for QoS control and safety management etc.; I-CSCF is responsible for the intercommunication between the IMS territory, and network topology and configuration are externally hidden in the distribution of management S-CSCF, produce metering data etc.The MGCF control gateway realizes the intercommunication of IMS network and other network, and MRF provides media resource, as the folding and unfolding sound, and encoding and decoding and multimedia conferencing bridge.HSS is a customer data base, storage IMS user's subscription data and configuration information etc.Use the Session Initiation Protocol agreement as session control protocol among the IMS.
Arrived the 3GPP R6 stage, on the basis of having finished the IMS basic frame structure, beginning is further improved the IMS network as a carrying separates with control, control separates with application hierarchical network.Because IMS has accomplished the independence of professional control and bearer network access way, therefore, network in R6 a lot of other types of stage also begins to consider to use IMS as professional Control Network, such as the packet network of 3GPP2, network that use WLAN inserts and the NGN that uses fixedly connected access etc.Therefore, the IMS network of 3GPP definition also can be applied on other packet switching networks, and the intercommunication with multiple bearer types network is provided, and realizes and the user uses the independence of terminal type.
Below simply introduce the bearer network type that the IMS network can superpose.The type of bearer network has packet field network, wireless lan (wlan) and the next generation network (NGN) of Wideband Code Division Multiple Access (WCDMA) (WCDMA) grouping of network territory network, CDMA2000.
WCDMA grouping of network territory comprises two kinds on GPRS (GPRS) network and global system for mobile communications (UMTS) network, the main distinction is the wireless access technology difference that Access Network adopts: continued to use the base station system of digital mobile communication system (GSM) among the GPRS, upgraded among the UMTS and use UTRAN or from enhancing data rate (GERAN) technology of GSM evolution.The core net of the two partly is the same, all comprises Gateway GPRS Support Node (GGSN, GatewayGPRS Supporting Node) and Serving GPRS Support Node (SGSN, Serving GPRSSupporting Node).
GGSN plays the critical point between WCDMA network and public data network, it can be connected with multiple different data network, as the Internet, public land mobile system (PLMN) and local area network (LAN) (LAN, Local Area Network) etc.SGSN writes down the current location information of travelling carriage, and finishes the transmission and the reception of mobile packet data between travelling carriage and various data network, for all travelling carriages in the service area provide two-way grouping route.Interface between SGSN and the GGSN is realized the tunnel transmission function based on GRPS tunnel protocol (GTP GPRS Tunnel Protocol).
CDMA2000 network correlation technique and evolution are that the 3GPP2 tissue proposes.In 3GPP2, also defined the service control layer face of similar IMS, (MMD, MultimediaDomain), its essence is moved IMS fully on the cdma2000 network exactly and is used to be called multimedia domain, MMD.
The maximum characteristics of CDMA2000 data service are to make full use of the IP technology.In the grouped data field, 3GPP2 regulation: the reference model of packet network, it is by packet data serving node (PDSN, PacketData Serving Node)/external agent (FA, Foreign Agent), limited several functional entitys such as remote customer dialing authentication system (RADIUS) and home agent (HA, Home Agent) constitute; Quote the specific (special) requirements that IETF has issued the IP standard; In order to solve the specific (special) requirements that wireless system charges, defined the form of ticket.
Except foregoing, all concrete agreements are all directly quoted the IP standard, thereby packet network is structured on the IP technical foundation.Wherein FA and HA are the functional entitys that mobile IP (MIP, Mobile IP) requires realization; The radius server mode is finished authentication, charging, authorization service; GGSN among the similar UMTS in the status of PDSN is the gateway between wireless access network and all kinds of packet switched public data network, is the access device of mobile terminal accessing the Internet in the CDMA2000 network.
Wlan network belongs to a kind of short-distance wireless communication technology, and it is to be the computer local network that transmission medium constitutes with the wireless channel, and (RF, Radio Frequency) transmits data, speech and vision signal aloft by wireless radio-frequency.Wlan network can remedy the deficiency that relies on copper cable or optical cable to constitute cable LAN in some special applied environments, realize the extension of network, make personal computer have mobility, can solve the connectivity problem that is difficult for realizing network channel by wired mode rapidly, easily.
Wlan network in order to be linked into the IP the Internet and to use various multimedia services, has increased packet data gateway (PDG, Packet DataGateway) node as a kind of wireless technology that is used in the limited range.As the gateway device that is linked into IMS, the function class of this node is like GGSN, can equally with UMTS user use mobile network service when the user inserts through WLAN like this, a plurality of intercommunication aspects are arranged, comprise unified authentication, charge, utilize PS that mobile network provides and IMS business, business was not interrupted etc. when different access way was switched.
NGN is a relatively generalized concept as next generation network, has several characteristics: adopt unified agreement, based on packet switching; Professional control with calling separated, and calls out control and separates with carrying; Realize intercommunication by gateway device and existing network.The call control layer face of IMS as its definition NGN adopted in the TISPAN of ETSI (ETSI) normal structure decision in the recent period, thereby also becomes a kind of bearer network of IMS.Though present research does not also provide concrete solution, but it is clear and definite: as to set up a gateway device and be linked in the IMS network, thereby can use the miscellaneous service control ability that existing IMS can provide and be linked on the Packet Service of various external networks.
Because the function that the service control layer face of IMS network will be realized is a lot, control two embodiment as an illustration for billing function and local policy at this.
Charging (the FBC of internet protocol-based (IP) stream, Flow Based Charging) function, for a Packet Service, the user is using the data volume that this business consumed to be called business data flow (Service Data Flow), and business data flow is the set that a plurality of IP streams are formed.And in a packet data protocol content (PDP context), can carry a plurality of different Packet Services, so the FBC granularity can be less than the charging granularity based on PDP context, thus the more charging means of horn of plenty can be provided.
Aspects such as system configuration, functional requirement and message flow to FBC in the TS23.125 of 3GPP are described.The FBC system configuration of wherein supporting online charging as shown in Figure 1; The FBC system configuration of support offline charging as shown in Figure 2.Each functional entity effect shown in Fig. 1 and Fig. 2 is respectively:
Transmission surface function entity (TPF, Traffic Plane Function), TPF is the functional entity of loaded packet data stream, it can distinguish the grouping bag that belongs in the different business data flow, is used for offline charging information gathering and carries out online credit control.When the packet data streams of carrying changes, the for example foundation of loaded packet data stream, revise or delete procedure, TPF passes through the Gx interface to the charging regulation function entity (CRF that charges based on Business Stream, Service Data Flow Based Charging Rule Function) sends request charging regulation message, can carry in the message: the terminal related information that user and user use, as Mobile Subscriber International ISDN number (MSISDN) and international mobile contracted user's sign (IMSI), bearer properties such as Quality of Service information, and the relevant information of network, as Mobile Network Code (MNC) and Mobile Country Code MCC (MCC).The charging regulation that TPF returns according to CRF, TPF carry out packet filtering on the corresponding service data flow and metering data is collected.
TPF can be by one or more CRF services, are chosen as the CRF of its service according to user's identification information, and TPF can support predefined charging regulation and predefined filter.
CRF, CRF are the functional entitys of preserving charging regulation, support dynamic charging regulation, promptly generate some charging regulation data and static charging regulation in real time according to professional criterion, use the user promptly that charging regulation is unalterable in the data service process.Static charging regulation can be activated by dynamic charging regulation.The TPF information of CRF by receiving, Application Function (AF, ApplicationFunction) information and Online Charging System (OCS, Online Charging System) information is as input, be used to choose suitable charging regulation, the charging regulation of choosing sent to TPF in the TPF request or when specific events trigger is arranged.
A CRF can corresponding a plurality of TPF.
AF, AF represents all and uses relevant functional entity, AF provides corresponding information to make CRF can select or dispose corresponding charging regulation to CRF, and the information that AF provides comprises: the identification information of business data flow can be set to wildcard, the information that charging regulation is selected, application/service identification, application/service billing rule triggered time, stream type, can be chosen as video or audio frequency, flow rate.
An AF can be corresponding to a plurality of CRF.AF can select CRF to carry out alternately according to user's identification information.
OCS, OCS is made up of service control point (SCP, Service Control Point) and two functional entitys of credit control (CC, Credit Control) as Online Charging System, and the user credit when wherein CC is to online charging manages.When the user used business, CCF authorized the credit in this user credit pond, and issued the operable credit of user to TPF.By the Ry interface, OCS can provide the input information of charging regulation selection to CRF.
Entity (CCF/CGF is collected in charging gateway entity/charging, Charging GatewayFunction/Charging Collection Function), these two functional entitys are used for off-line accounting system, can continue to use the realization in the existing GPRS network charging.
If bearer network is a GPRS network, then TPF is positioned at the GGSN place, and AF is a Service Gateway among the PDN, or service server.AF is exactly P-CSCF when IP Multimedia System (IMS) is carried on the GPRS network, and CRF is newly-increased logic entity; When IP Multimedia System (IMS) was carried in the packet network of 3GPP2, TPF was located on the PDSN; When IP Multimedia System (IMS) was carried in the network configuration of WLAN, TPF was exactly a logic function of packet data gateway (PDG).
At present, according among the standard 23.125v610 to the definition of charging regulation, charging regulation comprise in have: the charging way of a particular traffic data stream: online charging still be offline charging, be to identify by flow, duration or flow and duration write down, charge key, one or more business datum flow filter, priority and charging regulation when offline charging.Wherein, the business datum flow filter is to be used for distinguishing the packet data package that belongs to particular traffic data stream, and basic formation is the IP five-tuple, comprises source IP address, purpose IP address, source port number, destination slogan, host-host protocol number or application protocol number; The charging key is used for determining rate; Priority is to be used for determining to use which charging regulation to use when the charging regulation appearance is overlapping; The charging regulation sign is used for identifying charging regulation.
When implementing business, TPF is according to selected charging regulation, packet data package to this business data flow is filtered, may be to be unit with the duration, also may be to be unit with the flow, perhaps adding duration with flow is unit, generates bearing charging information, gives the final CDR that the charging related functional entities produces the user.
When the local policy controlled function that realizes based on business, 3GPP has defined mutual between the local bearer service of UE, GPRS bearer service and the external bearer service, and these are combined to packet domain end-to-end service Quality of Service is provided.IP bearer management function (IP BS Manager) all may exist in UE and GGSN, generally uses differential service (DiffServ) or integrated service/resource reservation (IntServ/RSVP) and external IP network to carry out intercommunication.
Simultaneously, 3GPP has described the essential mechanism of IP layer that end-to-end QoS is provided for packet domain, realizes by the local policy controlling mechanism based on business.Fig. 3 is the local policy controlling mechanism framework schematic diagram based on business: strategy decisive function (PDF, Policy Decision Function) and UE by Session Initiation Protocol mutual, PDF is applied layer as Session Description Protocol (SDP from application server, SessionDescription Protocol) parameter in, this application layer parameter information is mapped among IP qos parameter such as the RSVP, and specific policing rule is observed in this mapping.The decision-making of PDF will be sent to the IP bearer management function among the GGSN, further be mapped on the UMTS bearer management function by translation/mapping function, and GGSN finishes corresponding IP Policy Enforcement Point (PEP, IP Policy Enforcement Point) function.Go interface between PDF and the GGSN adopts public open protocol service (COPS, Common OpenPolicy Service) agreement, transmits qos-related information and strategy.
Only, the IMS business controls among the 3GPP R5, so PDF is the logic entity among the IMS entity P-CSCF for providing the QoS based on business.R6 stage PDF is an independent functional entity, can control for all packet switch domain services provide based on the qos policy of business.When the bearer network of other types will be realized policy control based on business, PEP just realized on the gateway device of correspondence.When using IMS, AF is exactly the logic entity among the P-CSCF.
When the carrying of setting up transmit traffic data when UE request connected, PEP sends request to PDF, and (REQ, Request) message were wherein carried the dialog information of client, are used for identifying the sign of authorization token and this one or more stream of session of corresponding PDF.If passed through mandate, then PDF return decision (DEC, Decision) message is given PEP, wherein carry the dialog information of client, control aspect charging identifier, up-downgoing indication, the QOS information of authorizing, the state information whether filter information and corresponding passage are opened.GGSN can be according to the implementation status of DEC then, and (RPT, Report) message is given PDF, the result of report executing etc. to return report.
By between existing IMS network and the bearer network, be to see at the realization mechanism aspect charging and the policy control between existing business key-course and the bearer network: in order to realize the independence of professional control and carrying, all do not transmit the relevant information of any bearer network on gateway function entity and the service control layer between the functional entity of correspondence, this is benefit on the one hand, also caused the disappearance of some information on the other hand, such as, about the information of bearer network type.
When the IMS network occurs at first, just give the network use of one type of UMTS, therefore, do not need the functional entity of GGSN in IMS to report any bearer network type information, because have only one type of UMTS, but when IMS expands to when can be applied on polytype bearer network, in certain professional process of enforcement, operator need know which network is this business specifically be carried on.This is because different bearer networks still can be distinguished to some extent in the requirement of aspects such as charging, service quality, safety, even as broad as long in theory, operator also may need the operation strategy according to oneself, formulates the corresponding service pattern.Such as, at 3G (Third Generation) Moblie (3G) the network development initial stage, use 3G network in order to encourage the user, cultivate user's custom etc., operator just wishes to use the user of UMTS network to charge low than the user who uses wlan network.
In addition, analyze the realization of existing UMTS packet switching network: because the Access Network in the UMTS network has used multiple access technology, comprise WCDMA and from the enhancing data rate (EDGE) of GSM evolution, also have later synchronous code division multiple access of time-division (TD-SCDMA) technology etc., so, core net is in order to carry out different processing at aspects such as charging, service quality at different Access Networks, core net can obtain the relevant information (RAT type, Radio Access Technologies type) of radio access technology types that Access Network transmits at present.Carry out reasoning thus, when the IMS extension of network is on can being applied in polytype bearer network, the information of relevant bearer network type also needs to allow the related functional entities in the IMS Network key-course know, thereby can implement different Business Processing at different bearer networks.
Therefore, how to allow the related functional entities in the IMS Network key-course determine the network type of current bearer network, thereby implement different Business Processing, become problem demanding prompt solution according to the different loading network type.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of and implements the method that different business is handled according to the different loading network type in professional Control Network, this method can allow the related functional entities in the IMS Network key-course determine the network type of current bearer network, thereby implements different Business Processing according to the different loading network type.
According to above-mentioned purpose, technical scheme of the present invention is achieved in that
A kind of method of handling according to different loading network type enforcement different business, this method comprises:
Functional entity in A, the service control layer obtains the bearer network type information that current user equipment is used;
This functional entity in B, the service control layer is determined the bearer network type according to this bearer network type information, implements different Business Processing.
When existing professional control interface and this interface to be used for the controlling and processing services of load bearing process between the functional entity corresponding in functional entity in the bearing bed and the service control layer, the functional entity that the described bearer network type information of steps A is a bearing bed sends to functional entity corresponding in the service control layer.
The described bearer network type information of steps A sets in advance in the functional entity of bearing bed.
The described bearer network type information of steps A is a functional entity of being determined and sent to bearing bed by subscriber equipment.
When the professional control interface that does not have professional control interface or existence between the functional entity corresponding in functional entity in the bearing bed and the service control layer was not used in the controlling and processing services of load bearing process, the described bearer network type information of steps A was that subscriber equipment sends to functional entity corresponding in the service control layer.
Affiliated load bearing process is loading establishing process, bearing modification process and deleting load-bearing process.
This functional entity in the service control layer is provided with different Business Processing strategies at the different loading network type;
After the described definite bearer network type of step B, this method further comprises: this functional entity in the service control layer is implemented different Business Processing according to the bearer network type selecting corresponding service processing policy of determining according to the Business Processing strategy of selecting.
Described controlling and processing services comprises: based on the charging of business data flow or based on the local policy control of business or at ongoing authentication of calling and licensing process.
From such scheme as can be seen, because method provided by the invention can be offered the bearer types at service control layer current business place by UE or bearing bed, so method provided by the invention can be used for realizing business and separate with control, in the next generation network framework that control separates with carrying, service control layer can be according to the difference of the employed bearer network of business, implement different Business Processing, comprise charging, service quality assurance, policy control, safety, Lawful Interception etc.By the present invention, can between the service control layer of complete independent evolution and bearing bed, transmit Useful Information each other, make concrete professional enforcement not only can accomplish the bearer network independence, also can in professional Control Network, realize the otherness service according to the characteristics of bearer network.The former independence is for independent evolution separately, and independent development considers that the latter's otherness is at bearer network realization technology the influence of business to be considered, also can embody the operation strategy of operator simultaneously.Therefore, this method can allow the related functional entities in the IMS Network key-course determine the network type of current bearer network, thereby implements different Business Processing according to the different loading network type.
Description of drawings
Fig. 1 is for supporting the FBC system construction drawing of online charging.
Fig. 2 is for supporting the FBC system construction drawing of offline charging.
Fig. 3 is the local policy controlling mechanism framework schematic diagram based on business.
Fig. 4 determines an embodiment flow chart of the network type of current bearer network for the related functional entities in the IMS Network key-course of the present invention.
Fig. 5 determines another embodiment flow chart of the network type of current bearer network for the related functional entities in the IMS Network key-course of the present invention.
Fig. 6 carries out the flow chart that different business is handled for the present invention's service control layer in carrying out based on the charging process of business data flow utilizes the bearer network type information.
The flow chart of the licensing process again that Fig. 7 triggers when revising for bearing bed of the present invention.
Fig. 8 carries out the flow chart that different business is handled for the present invention's service control layer in carrying out based on the local policy control procedure of business utilizes the different loading type information.
Fig. 9 carries out the schematic diagram that different business is handled for the present invention's service control layer in call control procedure utilizes the different loading type information.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, by the following examples and with reference to accompanying drawing, the present invention is further elaborated.
Therefore the present invention considers that bearer network can produce certain influence in some aspects to service implementation, needs related functional entities in the IMS Network key-course to know the professional employed bearer network type of present enforcement.
The present invention when there are professional control interface in bearing bed and service control layer, can by the user utilize bearer network for the first time and the related functional entities in the service control layer set up and be notified to related functional entities when getting in touch.Fig. 4 is the embodiment flow chart that the related functional entities in the IMS Network key-course of the present invention is determined the network type of current bearer network, and its concrete steps are:
Step 400, UE function corresponding entity in bearing bed is initiated carrying and is set up request, for using certain professional application bearing resource;
This functional entity in step 401, the bearing bed receives after this request, need to find and service control layer is set up and got in touch, so according to the configuration information of this locality or determine the type of own place bearer network from the information that other functional entitys obtain;
This functional entity in step 402, the bearing bed sends carries out the functional entity of certain professional request message of controlling to the service control layer correspondence, has the bearer network type information in this request message;
The functional entity of step 403, service control layer correspondence judges whether self is provided with different controlling and processing services according to different bearer network types, if not, and execution in step 404; Otherwise, execution in step 405;
The functional entity of step 404, service control layer correspondence does not need to carry out different controlling and processing services according to the bearer network type, directly this business control request is handled accordingly, carry out after the professional control, echo reply message is given this functional entity of bearing bed, execution in step 406;
The functional entity of step 405, service control layer correspondence is determined the bearer network type according to the bearer network type information that has in this request message, according to definite network type this business control request is handled accordingly, carry out after the professional control, echo reply message is given this functional entity of bearing bed;
The response message that this functional entity of step 406, bearing bed returns according to service control layer in conjunction with local strategy and information, is returned carrying and is set up the response message of request to UE.
This functional entity of bearing bed can have multiple implementation method in the step 401 when determining the type of own place bearer network, simply describes the some of them method at this:
Method one: when setting up network, in advance the bearer network type at this functional entity place is arranged on this functional entity, when this functional entity needs and key-course surface function entity interaction message the time, directly this information inserted in the message of correspondence;
Method two: UE is when selecting bearer network to be linked into service control layer, selected bearer network type information is placed on carrying sets up to give together in the request message with service control layer this functional entity in the mutual bearing bed is arranged, this functional entity directly utilizes this information;
Method three: this functional entity of bearing bed does not need the explicit functional entity that the bearer network type is given service control layer that carries, and the functional entity of two aspects has some parameters just can indicate what the type of bearer network is in mutual information.
In the network configuration that has, do not have direct professional control interface between bearing bed and the service control layer, perhaps the professional control interface of Cun Zaiing is not used in the Business Processing in the loading establishing process.UE can set up after loading end connects by the bearing bed agreement so, utilize this connection directly and service control layer mutual, the direct transparent transmission service key-course of bearing bed message, in this message, subscriber equipment directly is notified to professional Control Network with the type information of bearer network, as shown in Figure 5, Fig. 5 is another embodiment flow chart that the related functional entities in the IMS Network key-course of the present invention is determined the network type of current bearer network, and its concrete steps are:
Step 500, UE initiate carrying to the corresponding function entity of bearing bed and set up request, for using certain professional application bearing resource;
This functional entity of step 501, bearing bed receives after this request that according to the CAMEL-Subscription-Information of user at bearing bed, decision is accepted this carrying and set up request, returns to carry to set up and accepts message;
Step 502, UE determine bearer network type relevant information according to the business of oneself asking;
Step 503, UE send the functional entity of the request message of service control layer to service control layer, have the bearer network type information in this request message;
The functional entity of step 504, service control layer correspondence judges whether self is provided with different controlling and processing services according to different bearer network types, if not, and execution in step 505; Otherwise, execution in step 506;
The functional entity of step 505, service control layer correspondence does not need to carry out different controlling and processing services according to the bearer network type, directly this business control request is handled accordingly, carries out after the professional control, and echo reply message is given UE;
The functional entity of step 506, service control layer correspondence is determined the bearer network type according to the bearer network type relevant information that has in this request message, according to definite network type this business control request is handled accordingly, carry out after the professional control, echo reply message is given UE.
Service control layer obtains after the bearer network type information, can in business control implementation from now on, directly use this information, for example initiatively send professional control messages to bearing bed, the bearer network that the Business Processing of wherein carrying is used at current user equipment from service control layer.
Except above processing procedure, in the implementation of follow-up business,, also need to use similar method that new bearer network type information is notified to service control layer if switching between the bearer network has taken place.
Because the Business Processing kind that service control layer is carried out is very many, all run relevant aspect with communication network to relate to charging, safety, policy control, service quality assurance etc.So at this, the processing procedure of controlling with regard to charging, policy control and calling is that example describes.
Fig. 6 carries out the flow chart that different business is handled for the present invention's service control layer in carrying out based on the charging process of business data flow utilizes the bearer network type information, the present invention is with the routine explanation of being embodied as of online charging, suppose to use wlan network as bearer network, TPF is the logic function of PDG, at the CRF place, it is different inserting the charging regulation that access is used with GPRS network at wlan network, and its concrete steps are:
Step 600, UE send carrying to TPF and set up request message (Establish Bearer Serv Req); For WLAN, be exactly that PDG receives the tunnel and sets up request message;
Step 601, TPF ask charging regulation (Request Charging Rules) to CRF, carry the input information that decision CRF selects charging regulation in the message;
For WLAN, comprising: user and the UE information of using UE, as mobile contracted user's ISDN number (MSISDN), International Mobile Station Equipment Identification and software version number (IMEISVI, nternational Mobile station Equipment Identity and Software Version Number) etc.; Load characteristic is as the QoS after consulting, the Access Point Name of WLAN (wireless local area network) (W-APN, WLAN-Access Point Name) etc.; The network information is as Mobile Country Code MCC (MCC, MobileCountry Code) and Mobile Network Code (MNC, Mobile Network Code); Also have bearer network type, i.e. wlan network;
Step 602, CRF select corresponding charging regulation (IdentifyCharging Rules To Install) according to the information that obtains, except carrying and user-dependent information that TPF brings up, this moment, CRF place may also can obtain controlling relevant information from the application of AF and service related information and from the credit of OCS;
This user's charging regulation information is searched at step 603, CRF place according to user ID, find identical business, at WLAN carrying and other carryings, carry as GPRS, the charging regulation of using is different, CRF selects according to the bearer network type so, the charging regulation (Provision Charging Rules) that is applied to wlan network is handed down to TPF, as replying of charging regulation request message;
Step 604, TPF carry out application (Perform Charging Rules Actions) according to the operation indication to charging regulation that CRF provides to corresponding charging regulation;
Under step 605, the online charging situation, TPF asks credit information (Credit Request) to OCS, carries the required input information of OCS decision credit in the message;
Step 606, OC S provide credit information (Credit Response) to TPF;
Step 607, TPF are returned carrying to UE and are set up and accept message (Establish Bearer ServAccept), and UE just can be at the carrying transmitting data of having set up.
After the execution of step 607, UE just can carry out service request and transfer of data in the carrying of having set up, set up professional the company such as an application server in request and the network, required data in transport service request process, implementation and the abort process, reception is from information of application server or the like, and the transmission of these data all will take bearing resource.For the bearer network of having realized based on service data flow charge, at the TPF place, according to the difference of the Business Stream under each packet data package, TPF will use different charging regulations, and relevant bearing charging information is reported the charging related functional entities.
Because the bearer network that should business uses can cause using different charging regulations when changing.In order to monitor the variation of bearer network type, can dispose some trigger points among the TPF, when changing, the bearer network type triggers this trigger point, when offline charging, report CRF or when online charging, report OCS, thereby CRF or OCS can select different charging regulations according to the situation of change of bearer network.The flow chart of the licensing process again that Fig. 7 triggers when revising for bearing bed of the present invention, its concrete steps are:
Step 700, TPF receive the request message (Modify Bearer Serv Req) of revising carrying;
Step 701, TPF judge this time whether the modification of carrying mates the re-authorization trigger point, if, execution in step 703; Otherwise, execution in step 702;
Here bearing modification is to change into from the GPRS carrying using the WLAN carrying, therefore mates to be provided with the re-authorization trigger point that changes the WLAN carrying from the GPRS carrying among the TPF;
Step 702, proceed subsequent session and handle;
Step 703, TPF return under this charging regulation unspent information and give OCS, ask simultaneously this charging regulation is authorized (Credit Control Request) again;
Step 704, OCS carry out reauthorization process, under the situation of account's abundance, return new credit and give TPF (Credit Control Answer);
Step 705, TPF promptly change the charging regulation that carries based on WLAN into from the charging regulation based on the GPRS carrying, and send this bearing modification request (Modify Bearer Serv Accept) of accepting to UE according to the credit change charging regulation that returns.
Fig. 8 carries out the flow chart that different business is handled for the present invention's service control layer in carrying out based on the local policy control procedure of business utilizes the different loading type information, suppose that UE can insert IMS from WCDMA network or cdma2000 network, but when being to use different loading network to insert, identical business, signatory differences such as qos parameter, PDF is in implementation strategy control so, what the bearer network type that need know the current business carrying is, thereby selects different policy distributions to carry out to PEP.Its concrete steps are:
Step 800, UE send carrying and set up request to the functional entity that has PEP in the bearer network, wherein have qos parameter, be used for the binding information of PDF addressing and identification data stream;
The functional entity at step 801, PEP place sends COPS request (COPS REQ) message and gives PDF, so that obtain relevant policy information, wherein has binding information and the information that can distinguish the bearer network type;
Authorization token in step 802, the binding information makes PDF can find corresponding licensing status information, and PDF sends authorization requests to AF by Gq interface then;
Step 803, AF send to PDF with the business information of being asked, and promptly confirm by the Gq interface return authorization;
Step 804, PDF be according to the information from AF, and whether the carrier policy rule that defines among the conversation description of checking AF place and the PDF is consistent, if unanimity is authorized required QoS resource, and application IP layer strategy; When PDF checks, find that the policing rule at the different bearer types network is different in the carrier policy rule, then the conversation description of further selecting corresponding strategy rule and AF to send here according to the bearer network type information compares, authorize corresponding QoS resource, use corresponding IP layer strategy; If inconsistent, process ends then;
Step 805, PDF return the functional entity that COPS decision (COPS DEC) message is given the PEP place;
The functional entity at step 806, PEP place returns COPS report (COPS RPT) message and gives PDF, and this process can trigger PDF and send a report message to AF;
The functional entity at step 807, PEP place according to obtain based on the policy information of IP stream with this policy mappings to the bearing bed of bearer network, and then whether decision accept carrying this time and set up request, acceptance is returned carrying and is set up and accept message and give UE; Otherwise, process ends.
Fig. 9 carries out the schematic diagram that different business is handled for the present invention's service control layer in call control procedure utilizes the different loading type information, as shown in the figure:
UEA and UEB carry out a1 and b1 start process separately, according to the bearer network type difference at place separately, carry out different Business Processing then.
What UEA used is GPRS network, therefore initiate the a2GPRS attaching process, utilize the PDP Context that a3 sets up to initiate the a4IMS register requirement, can carry the information of bearer network type of the current use of subscriber equipment or the extension of message part relevant in the registration message with different loading network to application server AS and IMS core net.The IMS core net judges that according to information relevant with the employed bearer network of subscriber equipment in the registration message bearer network that UEA uses is a GPRS network, because the fail safe of GPRS network is better, therefore decision is only carried out authentication to this UEA when UEA registers for the first time, re-registration process is all directly returned affirmation later on, does not re-authenticate.
What UEB used is wlan network, therefore initiate b23GPP WLAN attaching process, utilize the WLAN tunnel that b3 sets up to initiate the b4IMS register requirement, can carry the information of bearer network type of the current use of subscriber equipment or the extension of message part relevant in the registration message with different loading network to application server AS and IMS core net.The IMS core net is a wlan network according to information judgement UEB use relevant with the employed bearer network of subscriber equipment in the registration message; and the safeguard protection of wlan network is poor; therefore decision will be carried out authentication process when UEB registers for the first time; all to re-authenticate process when re-registering afterwards, do not emitted by puppet to guarantee UEB.
The invention provides a kind of feasible professional Control Network can be according to the different method of carrying out different disposal of the employed bearer network type of business, according to whether there being direct professional control interface between bearing bed and the service control layer, use diverse ways that the type information of the bearer network of subscriber equipment use is notified to service control layer, thereby make service control layer to use different charging policy according to the characteristics of bearer network, different service quality, different level of security or the like, allow operator when realizing concrete the application, can implement different business control according to carrying, thereby can offer the discrepant service of user, help segmenting customers, cultivate user's custom, reach the purpose of increasing the benefit.
Give this method of service control layer more common by bearing bed or user equipment to report bearer network type information, no matter what the application layer on the service control layer was carried out is any concrete application, can implement different controlling and processing services according to the difference of bearer network type, but not all controlling and processing services all needs to distinguish the bearer network type.Therefore whether the present invention can also be needed by the own decision of concrete business of application layer to implement different controlling and processing services according to the difference of bearer network type, if desired, the network type that can carry so according to this business, the corresponding service control and treatment is used from the functional entity that service control layer is handed down to the bearing bed correspondence, also can be reached professional Control Network and carry out the purpose that different business is handled according to the bearer network type.The shortcoming of this method is: because do not know the particular type of bottom carrying, may need to issue multiple bearer network corresponding service control and treatment information, cause information redundancy, the controlling and processing services information that perhaps issues is not suitable for the bearer network of current use.
The above only is preferred embodiment of the present invention, not in order to restriction the present invention, all any modifications of being made within the spirit and principles in the present invention, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.

Claims (8)

1, a kind of method of handling according to different loading network type enforcement different business is characterized in that this method comprises:
Functional entity in A, the service control layer obtains the bearer network type information that current user equipment is used;
This functional entity in B, the service control layer is determined the bearer network type according to this bearer network type information, implements different Business Processing.
2, the method for claim 1, it is characterized in that, when existing professional control interface and this interface to be used for the controlling and processing services of load bearing process between the functional entity corresponding in functional entity in the bearing bed and the service control layer, the functional entity that the described bearer network type information of steps A is a bearing bed sends to functional entity corresponding in the service control layer.
3, method as claimed in claim 2 is characterized in that, the described bearer network type information of steps A sets in advance in the functional entity of bearing bed.
4, method as claimed in claim 2 is characterized in that, the described bearer network type information of steps A is a functional entity of being determined and sent to bearing bed by subscriber equipment.
5, the method for claim 1, it is characterized in that, when the professional control interface that does not have professional control interface or existence between the functional entity corresponding in functional entity in the bearing bed and the service control layer was not used in the controlling and processing services of load bearing process, the described bearer network type information of steps A was that subscriber equipment sends to functional entity corresponding in the service control layer.
As claim 2 or 5 described methods, it is characterized in that 6, affiliated load bearing process is loading establishing process, bearing modification process and deleting load-bearing process.
7, the method for claim 1 is characterized in that, this functional entity in the service control layer is provided with different Business Processing strategies at the different loading network type;
After the described definite bearer network type of step B, this method further comprises: this functional entity in the service control layer is implemented different Business Processing according to the bearer network type selecting corresponding service processing policy of determining according to the Business Processing strategy of selecting.
8, as claim 1 or 7 described methods, it is characterized in that described controlling and processing services comprises: based on the charging of business data flow or based on the local policy control of business or at ongoing authentication of calling and licensing process.
CNB2004100584555A 2004-08-16 2004-08-16 Method for carrying out different service treatment according to different bearing network type Expired - Lifetime CN100466645C (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CNB2004100584555A CN100466645C (en) 2004-08-16 2004-08-16 Method for carrying out different service treatment according to different bearing network type
PCT/CN2005/001273 WO2006017985A1 (en) 2004-08-16 2005-08-16 A method of implementing the service treatment by the functional entity in the service control layer

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2004100584555A CN100466645C (en) 2004-08-16 2004-08-16 Method for carrying out different service treatment according to different bearing network type

Publications (2)

Publication Number Publication Date
CN1738303A true CN1738303A (en) 2006-02-22
CN100466645C CN100466645C (en) 2009-03-04

Family

ID=35907228

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2004100584555A Expired - Lifetime CN100466645C (en) 2004-08-16 2004-08-16 Method for carrying out different service treatment according to different bearing network type

Country Status (2)

Country Link
CN (1) CN100466645C (en)
WO (1) WO2006017985A1 (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007104215A1 (en) * 2006-03-15 2007-09-20 Huawei Technologies Co., Ltd. Method, apparatus and system for controlling the qos request by the network
WO2008055448A1 (en) * 2006-11-10 2008-05-15 Huawei Technologies Co., Ltd. A method, an apparatus and a system for acquiring access information of a user terminal
CN101459881B (en) * 2007-12-12 2010-09-08 中国移动通信集团公司 Message bearing method and client, message server
CN101527968B (en) * 2009-04-09 2011-01-05 北京航空航天大学 Interaction method between space network and ground network, and communication protocol gateway
CN101222521B (en) * 2008-01-21 2011-03-16 中兴通讯股份有限公司 File transfer method based on conversation launching protocol
CN101127629B (en) * 2006-08-18 2012-08-22 华为技术有限公司 Policy and billing execution device, online billing system and method for communication system
CN102932671A (en) * 2012-11-26 2013-02-13 北京奇虎科技有限公司 Method and server for supplying picture to computing terminal
CN101873716B (en) * 2009-04-27 2013-02-13 电信科学技术研究院 Carrying establishing method and system of home network or local network
CN103460631A (en) * 2011-04-08 2013-12-18 阿尔卡特朗讯 A method and tool for automatically generating a limited set of spectrum and service profiles
CN104038974A (en) * 2014-06-11 2014-09-10 中国联合网络通信集团有限公司 Method and device for processing voice service
CN104158801A (en) * 2014-07-25 2014-11-19 华为技术有限公司 Call handling method and device
CN109587349A (en) * 2018-11-14 2019-04-05 平安科技（深圳）有限公司 Multimedia is attended a banquet line testing process and device, electronic equipment, storage medium
CN112333221A (en) * 2019-08-05 2021-02-05 迈普通信技术股份有限公司 Network architecture, method and communication equipment for centralized processing of network services

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH02230888A (en) * 1989-03-03 1990-09-13 Nec Corp Hierarchical separation type call controller
CN1175601C (en) * 2001-09-17 2004-11-10 华为技术有限公司 Method for identifying service quality of user's interface transmission network layer in wireless switch-in network
KR100537499B1 (en) * 2002-07-26 2005-12-19 삼성전자주식회사 Method of generating transmission control parameter and selective retranmission method according to the packet characteristics.

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007104215A1 (en) * 2006-03-15 2007-09-20 Huawei Technologies Co., Ltd. Method, apparatus and system for controlling the qos request by the network
CN101127629B (en) * 2006-08-18 2012-08-22 华为技术有限公司 Policy and billing execution device, online billing system and method for communication system
WO2008055448A1 (en) * 2006-11-10 2008-05-15 Huawei Technologies Co., Ltd. A method, an apparatus and a system for acquiring access information of a user terminal
CN101459881B (en) * 2007-12-12 2010-09-08 中国移动通信集团公司 Message bearing method and client, message server
CN101222521B (en) * 2008-01-21 2011-03-16 中兴通讯股份有限公司 File transfer method based on conversation launching protocol
CN101527968B (en) * 2009-04-09 2011-01-05 北京航空航天大学 Interaction method between space network and ground network, and communication protocol gateway
CN101873716B (en) * 2009-04-27 2013-02-13 电信科学技术研究院 Carrying establishing method and system of home network or local network
CN103460631A (en) * 2011-04-08 2013-12-18 阿尔卡特朗讯 A method and tool for automatically generating a limited set of spectrum and service profiles
CN102932671A (en) * 2012-11-26 2013-02-13 北京奇虎科技有限公司 Method and server for supplying picture to computing terminal
CN104038974A (en) * 2014-06-11 2014-09-10 中国联合网络通信集团有限公司 Method and device for processing voice service
CN104038974B (en) * 2014-06-11 2017-03-29 中国联合网络通信集团有限公司 A kind of processing method and processing device of speech business
CN104158801A (en) * 2014-07-25 2014-11-19 华为技术有限公司 Call handling method and device
CN104158801B (en) * 2014-07-25 2017-08-25 华为技术有限公司 A kind of call processing method and device
CN109587349A (en) * 2018-11-14 2019-04-05 平安科技（深圳）有限公司 Multimedia is attended a banquet line testing process and device, electronic equipment, storage medium
CN109587349B (en) * 2018-11-14 2022-02-01 平安科技（深圳）有限公司 Multimedia agent line testing method and device, electronic equipment and storage medium
CN112333221A (en) * 2019-08-05 2021-02-05 迈普通信技术股份有限公司 Network architecture, method and communication equipment for centralized processing of network services
CN112333221B (en) * 2019-08-05 2023-09-12 迈普通信技术股份有限公司 Network system, method and communication equipment for centralized processing of network service

Also Published As

Publication number Publication date
WO2006017985A1 (en) 2006-02-23
CN100466645C (en) 2009-03-04

Similar Documents

Publication Publication Date Title
EP1576839B1 (en) Enhanced qos control
CN101385307B (en) Optimization of pdp context usage
EP1382214B1 (en) Binding information for ip media flows
US7826353B2 (en) Method, system and network element for authorizing a data transmission
EP1685682B1 (en) Controlling network resources after determination of a flow termination
CA2515412C (en) Mobile network having ip multimedia subsystem (ims) entities and solutions for providing simplification of operations and compatibility between different ims entities
US8532125B2 (en) Method, system and apparatus for session association
Agrawal et al. IP multimedia subsystems in 3GPP and 3GPP2: overview and scalability issues
CN100550804C (en) A kind of network attached method and network attachment system
EP1332627B1 (en) Method and apparatus for coordinated charging of services in a multimedia session
CN1444824A (en) Common charging identifier for communication networks
US20020068545A1 (en) Method and apparatus for coordinating charging for services provided in a multimedia session
US20030120135A1 (en) Method for remote medical consultation and care
US20020120749A1 (en) Media binding to coordinate quality of service requirements for media flows in a multimedia session with IP bearer resources
CN101222343B (en) Policy and charging control system and control method for media gateway
WO2006017985A1 (en) A method of implementing the service treatment by the functional entity in the service control layer
CN1968139A (en) Subscriber contract information processing method and apparatus in strategy and charging control
CN1806428A (en) Distribution of a charging identifier in particular in UMTS networks.
US20060221828A1 (en) Establishment of QoS by applications in cellular networks using service based policy control mechanisms
Psimogiannos et al. An IMS-based network architecture for WiMAX-UMTS and WiMAX-WLAN interworking
CN101047874A (en) Decision method for service information in mobile communication network
CN100466804C (en) Method for confirming data transmission service quality in communication network
CN1870635B (en) Service quality authorization method
CN101860836A (en) Processing method, system and equipment for policy and charging control
WO2009036694A1 (en) Method, device and system for establishing multiple pdn connections

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
EE01 Entry into force of recordation of patent licensing contract

Application publication date: 20060222

Assignee: APPLE Inc.

Assignor: HUAWEI TECHNOLOGIES Co.,Ltd.

Contract record no.: 2015990000755

Denomination of invention: Method for carrying out different service treatment according to different bearing network type

Granted publication date: 20090304

License type: Common License

Record date: 20150827

LICC Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model
CX01 Expiry of patent term

Granted publication date: 20090304

CX01 Expiry of patent term