CN1738303A - A method for implementing different service processing according to different bearer network types - Google Patents
A method for implementing different service processing according to different bearer network types Download PDFInfo
- 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
- bearer
- network
- functional entity
- service
- service control
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 84
- 238000012545 processing Methods 0.000 title claims abstract description 48
- 230000008569 process Effects 0.000 claims description 49
- 238000012986 modification Methods 0.000 claims description 5
- 230000004048 modification Effects 0.000 claims description 5
- 230000006870 function Effects 0.000 description 25
- 238000013475 authorization Methods 0.000 description 13
- 238000005516 engineering process Methods 0.000 description 13
- 230000004044 response Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 5
- 239000003795 chemical substances by application Substances 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 238000000926 separation method Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000000275 quality assurance Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
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—Intra-user or intra-terminal allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0078—Timing of allocation
- H04L5/0082—Timing of allocation at predetermined intervals
- H04L5/0083—Timing of allocation at predetermined intervals symbol-by-symbol
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- 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. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/06—TPC algorithms
- H04W52/14—Separate analysis of uplink or downlink
- H04W52/143—Downlink power control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/18—TPC being performed according to specific parameters
- H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/18—TPC being performed according to specific parameters
- H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
- H04W52/245—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account received signal strength
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/38—TPC being performed in particular situations
- H04W52/46—TPC being performed in particular situations in multi-hop networks, e.g. wireless relay networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/38—TPC being performed in particular situations
- H04W52/48—TPC being performed in particular situations during retransmission after error or non-acknowledgment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/02—Hybrid access
-
- 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. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/18—TPC being performed according to specific parameters
- H04W52/22—TPC being performed according to specific parameters taking into account previous information or commands
- H04W52/225—Calculation of statistics, e.g. average or variance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/18—TPC being performed according to specific parameters
- H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
- H04W52/241—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account channel quality metrics, e.g. SIR, SNR, CIR or Eb/lo
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/04—Transmission power control [TPC]
- H04W52/18—TPC being performed according to specific parameters
- H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
- H04W52/242—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account path loss
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- 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)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Finance (AREA)
- Computer Hardware Design (AREA)
- Strategic Management (AREA)
- Computing Systems (AREA)
- Multimedia (AREA)
- General Business, Economics & Management (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Automation & Control Theory (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Medical Informatics (AREA)
- Bioethics (AREA)
- Databases & Information Systems (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Human Resources & Organizations (AREA)
- Primary Health Care (AREA)
- Technology Law (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明公开了一种根据不同承载网络类型实施不同业务处理的方法，该方法包括：A.业务控制层中的功能实体获取当前用户设备使用的承载网络类型信息；B.业务控制层中的该功能实体根据该承载网络类型信息确定承载网络类型，实施不同的业务处理。该方法能够让IMS网络业务控制层中的相关功能实体确定当前承载网络的网络类型，从而根据不同承载网络类型实施不同的业务处理。
The invention discloses a method for implementing different service processing according to different types of bearer networks, the method comprising: A. a functional entity in the service control layer obtains the type information of the bearer network used by the current user equipment; B. the function entity in the service control layer The functional entity determines the bearer network type according to the bearer network type information, and performs different service processing. The method enables relevant functional entities in the service control layer of the IMS network to determine the network type of the current bearer network, so as to implement different service processing according to different bearer network types.
Description
技术领域technical field
本发明涉及了在业务控制网络中实施不同业务处理的技术，特别涉及一种在业务控制网络中根据不同承载网络类型实施不同业务处理的方法。The present invention relates to the technology for implementing different service processing in the service control network, in particular to a method for implementing different service processing in the service control network according to different bearer network types.
背景技术Background technique
随着宽带网络的发展，移动通信系统开展的业务将不仅仅局限于传统的语音通信，结合音频、视频、图片和文本等多种媒体类型的多媒体业务将逐渐开展起来。多媒体业务包括呈现业务(presence)、短消息、网页(WEB)浏览、定位信息、推送业务(PUSH)、文件共享等和上述数据业务的结合，可以满足用户的多种需求。With the development of broadband networks, the services carried out by mobile communication systems will not only be limited to traditional voice communications, but also multimedia services that combine multiple media types such as audio, video, pictures, and text will gradually develop. Multimedia services include presence, short messages, webpage (WEB) browsing, positioning information, push services (PUSH), file sharing, etc. and the combination of the above data services, which can meet various needs of users.
在多媒体多种应用的推动下，第三代移动通信标准化的伙伴项目(3GPP)标准组织推出了基于IP的多媒体子系统(IMS)架构，目的是在无线通信系统中使用一种标准化的开放结构来实现多种多样的多媒体应用，提供给用户更多的选择和更丰富的感受。Driven by the multiple applications of multimedia, the 3rd Generation Mobile Communications Standardization Partnership Project (3GPP) standard organization has launched the IP-based Multimedia Subsystem (IMS) architecture, aiming to use a standardized open structure in wireless communication systems To achieve a variety of multimedia applications, to provide users with more choices and richer experience.
在3GPP版本5(R5，Release5)阶段，引入了IP多媒体子系统域，简称IMS，叠加在分组交换网络之上。IMS由呼叫状态控制功能(CSCF)、媒体网关控制功能(MGCF)、媒体资源功能(MRF)和归属签约用户服务器(HSS)等功能实体组成，其中CSCF又可以分成服务CSCF(S-CSCF)、代理CSCF(P-CSCF)和查询CSCF(I-CSCF)三个逻辑实体。S-CSCF是IMS的业务交换中心，执行会话控制，维持会话状态，负责管理用户信息，产生计费信息等；P-CSCF是终端用户接入IMS的接入点，完成用户注册，负责QoS控制和安全管理等；I-CSCF负责IMS域之间的互通，管理S-CSCF的分配，对外隐藏网络拓扑和配置，产生计费数据等。MGCF控制网关，实现IMS网络和其它网络的互通，MRF提供媒体资源，如收放音，编解码和多媒体会议桥。HSS是用户数据库，存储IMS用户的签约数据和配置信息等。IMS中使用会话发起协议(SIP)协议作为会话控制协议。In the 3GPP version 5 (R5, Release5) stage, the IP Multimedia Subsystem domain, referred to as IMS, is introduced, which is superimposed on the packet switching network. IMS is composed of functional entities such as call state control function (CSCF), media gateway control function (MGCF), media resource function (MRF) and home subscriber server (HSS), among which CSCF can be divided into serving CSCF (S-CSCF), Proxy CSCF (P-CSCF) and Inquiry CSCF (I-CSCF) three logical entities. S-CSCF is the service switching center of IMS, which performs session control, maintains session state, manages user information, generates billing information, etc.; P-CSCF is the access point for terminal users to access IMS, completes user registration, and is responsible for QoS control and security management; I-CSCF is responsible for the intercommunication between IMS domains, manages the allocation of S-CSCF, hides network topology and configuration from the outside, and generates billing data, etc. The MGCF controls the gateway to realize the intercommunication between the IMS network and other networks, and the MRF provides media resources, such as audio playback, codec and multimedia conference bridge. The HSS is a user database, which stores subscription data and configuration information of IMS users. The Session Initiation Protocol (SIP) protocol is used in the IMS as the session control protocol.
到了3GPP R6阶段，在完成了IMS基本框架结构的基础上，开始进一步完善IMS网络作为一个承载与控制分离、控制与应用分离的分层网络。由于IMS做到了业务控制与承载网络接入方式的无关性，因此，在R6阶段很多其他类型的网络也开始考虑使用IMS作为业务控制网络，比如3GPP2的分组网络，使用WLAN接入的网络以及使用固定连接接入的NGN等。因此，3GPP定义的IMS网络也可以应用于其他分组交换网络之上，提供和多种承载类型网络的互通，实现和用户使用终端类型的无关性。At the 3GPP R6 stage, on the basis of completing the basic framework structure of IMS, the IMS network began to be further improved as a layered network with separation of bearer and control, control and application. Because IMS achieves the independence of service control and bearer network access, many other types of networks also began to consider using IMS as a service control network in the R6 stage, such as 3GPP2 packet networks, networks using WLAN access, and networks using Fixed connection access NGN, etc. Therefore, the IMS network defined by 3GPP can also be applied to other packet switching networks to provide intercommunication with multiple types of bearer networks and to achieve independence from the types of terminals used by users.
以下简单介绍一下IMS网络可以叠加的承载网络类型。承载网络的类型有宽带码分多址(WCDMA)网络的分组域网络、CDMA2000的分组域网络、无线局域网(WLAN)和下一代网络(NGN)。The following briefly introduces the bearer network types that can be superimposed on the IMS network. The types of the bearer network include packet domain network of wideband code division multiple access (WCDMA) network, packet domain network of CDMA2000, wireless local area network (WLAN) and next generation network (NGN).
WCDMA网络的分组域包括通用分组无线业务(GPRS)网络和全球移动通信系统(UMTS)网络两种，主要区别在于接入网采用的无线接入技术不同：GPRS中沿用了数字式移动通信系统(GSM)的基站系统，UMTS中升级为使用UTRAN或者从GSM演进的增强数据速率(GERAN)技术。二者的核心网部分是一样的，都包括网关GPRS支持节点(GGSN，GatewayGPRS Supporting Node)和服务GPRS支持节点(SGSN，Serving GPRSSupporting Node)。The packet domain of WCDMA network includes General Packet Radio Service (GPRS) network and Universal Mobile Telecommunications System (UMTS) network. GSM) base station system, UMTS is upgraded to use UTRAN or enhanced data rate (GERAN) technology evolved from GSM. The core network part of the two is the same, including a gateway GPRS support node (GGSN, GatewayGPRS Supporting Node) and a serving GPRS support node (SGSN, Serving GPRS Supporting Node).
GGSN在WCDMA网络和公用数据网之间起关口的作用，它可以和多种不同的数据网络连接，如互联网、公共陆地移动系统(PLMN)和局域网(LAN，Local Area Network)等。SGSN记录移动台的当前位置信息，并在移动台和各种数据网络之间完成移动分组数据的发送和接收，为服务区内所有移动台提供双向的分组路由。SGSN和GGSN之间的接口基于GRPS隧道协议(GTP GPRS Tunnel Protocol)，实现隧道传输功能。GGSN acts as a gateway between the WCDMA network and the public data network, and it can be connected to a variety of different data networks, such as the Internet, public land mobile system (PLMN) and local area network (LAN, Local Area Network). SGSN records the current location information of the mobile station, completes the sending and receiving of mobile packet data between the mobile station and various data networks, and provides two-way packet routing for all mobile stations in the service area. The interface between SGSN and GGSN is based on the GRPS Tunnel Protocol (GTP GPRS Tunnel Protocol) to realize the tunnel transmission function.
CDMA2000网络相关技术和演进是3GPP2组织提出的。在3GPP2中，也定义了类似IMS的业务控制层面，叫做多媒体域(MMD，MultimediaDomain)，其实质就是将IMS完全搬移到cdma2000网络上使用。CDMA2000 network-related technologies and evolution are proposed by 3GPP2. In 3GPP2, a service control layer similar to IMS is also defined, called Multimedia Domain (MMD, MultimediaDomain). Its essence is to completely move IMS to the cdma2000 network for use.
CDMA2000数据业务的最大特点是充分利用IP技术。在分组数据领域，3GPP2规定：分组网络的参考模型，它由分组数据服务节点(PDSN，PacketData Serving Node)/外部代理(FA，Foreign Agent)、远程用户拨号认证系统(RADIUS)和家乡代理(HA，Home Agent)等有限的几个功能实体构成；引用IETF已经发布IP标准的特殊要求；为了解决无线系统计费的特殊要求，定义了话单的格式。The biggest characteristic of CDMA2000 data business is to make full use of IP technology. In the field of packet data, 3GPP2 stipulates: the reference model of packet network, which consists of packet data service node (PDSN, PacketData Serving Node)/foreign agent (FA, Foreign Agent), remote user dial authentication system (RADIUS) and home agent (HA) , Home Agent) and other limited functional entities; refer to the special requirements of IP standards that have been released by IETF; in order to solve the special requirements of wireless system billing, the format of bills is defined.
除了上述内容以外，所有的具体协议都直接引用IP标准，从而将分组网络构建在IP技术基础上。其中FA和HA是移动IP(MIP，Mobile IP)要求实现的功能实体；RADIUS服务器方式完成鉴权、计费、授权服务；PDSN的地位类似UMTS中的GGSN，是无线接入网和各类分组交换公共数据网之间的网关，是CDMA2000网络中移动终端访问互联网的接入设备。In addition to the above-mentioned content, all specific protocols directly refer to the IP standard, so that the packet network is built on the basis of IP technology. Among them, FA and HA are functional entities required by Mobile IP (MIP, Mobile IP); RADIUS server mode completes authentication, billing, and authorization services; The gateway between the switched public data networks is the access device for mobile terminals in the CDMA2000 network to access the Internet.
WLAN网络属于一种短距离无线通信技术，它是以无线信道为传输媒介构成的计算机局域网络，通过无线射频技术(RF，Radio Frequency)在空中传输数据、话音和视频信号。WLAN网络可以在一些特殊的应用环境中弥补依靠铜缆或光缆构成有线局域网的不足，实现网络的延伸，使个人计算机具有可移动性，能迅速、方便地解决通过有线方式不易实现网络信道的连通问题。WLAN network belongs to a short-distance wireless communication technology. It is a computer local area network composed of wireless channels as the transmission medium, and transmits data, voice and video signals in the air through radio frequency technology (RF, Radio Frequency). WLAN network can make up for the deficiency of relying on copper cables or optical cables to form a wired local area network in some special application environments, realize the extension of the network, make the personal computer mobile, and quickly and conveniently solve the problem that it is difficult to realize the connection of network channels through wired methods. question.
WLAN网络作为一种用于有限范围内的无线技术，为了能够接入到IP互联网以及应用各种多媒体业务，增加了分组数据网关(PDG，Packet DataGateway)节点。作为接入到IMS的网关设备，该节点的功能类似GGSN，这样用户经过WLAN接入时可与UMTS用户一样使用移动网业务，有多个互通层面，包括统一鉴权、计费、利用移动网提供的PS和IMS业务、不同接入方式切换时业务不中断等。As a wireless technology used in a limited range, a WLAN network is added a packet data gateway (PDG, Packet Data Gateway) node in order to be able to access the IP Internet and apply various multimedia services. As a gateway device connected to IMS, the function of this node is similar to GGSN, so that users can use mobile network services like UMTS users when accessing through WLAN. The PS and IMS services provided, and the services are not interrupted when switching between different access modes.
NGN作为下一代网络，是一个比较广义的概念，具有几个特点：采用统一的协议，基于分组交换；业务与呼叫控制分离，呼叫控制与承载分离；通过网关设备和现有网络实现互通。近期欧洲电信标准化协会(ETSI)TISPAN标准组织决定采用IMS作为其定义NGN的呼叫控制层面，从而也成为了IMS的一种承载网络。虽然目前的研究还没有给出具体的解决方案，但是已经明确：建立一个网关设备来接入到IMS网络中，从而可以应用现有IMS能够提供的各种业务控制能力和接入到各种外部网络的分组业务上。As a next-generation network, NGN is a relatively broad concept with several characteristics: it adopts a unified protocol and is based on packet switching; it separates business from call control, and separates call control from bearer; it realizes intercommunication with existing networks through gateway equipment. Recently, the TISPAN standard organization of the European Telecommunications Standards Institute (ETSI) decided to adopt IMS as the call control layer for defining NGN, thus becoming a bearer network of IMS. Although the current research has not given a specific solution, it has been clarified: to establish a gateway device to access the IMS network, so that various service control capabilities that the existing IMS can provide and access to various external On the packet business of the network.
因为IMS网络的业务控制层面要实现的功能很多，在此只举计费功能和本地策略控制两个实施例作为说明。Because there are many functions to be realized on the service control plane of the IMS network, only two embodiments of the charging function and local policy control are used as illustrations here.
基于互联网协议(IP)流的计费(FBC，Flow Based Charging)功能，对于一个分组业务来说，用户在使用该项业务所消耗的数据量称为业务数据流(Service Data Flow)，业务数据流是多个IP流组成的集合。而在一个分组数据协议内容(PDP context)中可以承载多个不同的分组业务，因此FBC粒度可以小于基于PDP context的计费粒度，从而能够提供更为丰富的计费手段。The FBC (Flow Based Charging) function based on the Internet protocol (IP) flow. For a packet service, the amount of data consumed by the user when using the service is called Service Data Flow (Service Data Flow). Service data A flow is a collection of multiple IP flows. However, multiple different packet services can be carried in one packet data protocol content (PDP context), so the granularity of FBC can be smaller than the granularity of charging based on PDP context, thereby providing richer charging means.
在3GPP的TS23.125中对FBC的系统结构、功能要求以及消息流程等方面进行了描述。其中支持在线计费的FBC系统结构如图1所示；支持离线计费的FBC系统结构如图2所示。图1和图2中所示的各个功能实体作用分别为：In TS23.125 of 3GPP, the system structure, functional requirements and message flow of FBC are described. The structure of the FBC system supporting online charging is shown in Figure 1; the structure of the FBC system supporting offline charging is shown in Figure 2. The functions of each functional entity shown in Figure 1 and Figure 2 are as follows:
传输面功能实体(TPF，Traffic Plane Function)，TPF是承载分组数据流的功能实体，其可区分属于不同业务数据流中的分组包，用于离线计费信息收集和执行在线信用控制。当承载的分组数据流发生变化时，例如承载分组数据流的建立、修改或删除过程，TPF通过Gx接口向基于业务流计费的计费规则功能实体(CRF，Service Data Flow Based Charging Rule Function)发送请求计费规则消息，消息中可以携带：用户和用户使用的终端相关信息，如移动台国际ISDN号码(MSISDN)和国际移动签约用户标识(IMSI)，承载特性如业务质量(QoS)信息，以及网络相关的信息，如移动网编码(MNC)和移动国家码(MCC)。TPF根据CRF返回的计费规则，TPF在对应的业务数据流上执行分组过滤和计费数据收集。Transport plane functional entity (TPF, Traffic Plane Function), TPF is a functional entity carrying packet data streams, which can distinguish packets belonging to different service data streams, and is used for offline charging information collection and online credit control. When the carried packet data flow changes, such as the process of establishing, modifying or deleting the carried packet data flow, the TPF sends a service data flow based charging rule function entity (CRF, Service Data Flow Based Charging Rule Function) through the Gx interface. Send a request charging rule message, the message can carry: the user and the terminal information used by the user, such as the mobile station international ISDN number (MSISDN) and the international mobile subscriber identity (IMSI), bearing characteristics such as quality of service (QoS) information, As well as network related information such as Mobile Network Code (MNC) and Mobile Country Code (MCC). According to the charging rule returned by the CRF, the TPF performs packet filtering and charging data collection on the corresponding service data flow.
一个TPF可以由一个或多个CRF服务，根据用户的标识信息来选择为其服务的CRF，TPF可以支持预定义的计费规则以及预定义的过滤器。A TPF can be served by one or more CRFs, and the CRF serving it can be selected according to the identification information of the user. The TPF can support predefined charging rules and predefined filters.
CRF，CRF是保存有计费规则的功能实体，支持动态的计费规则，即根据业务准则实时生成一些计费规则数据，和静态的计费规则，即在用户使用数据业务过程中计费规则是一成不变的。静态的计费规则可以被动态的计费规则激活。CRF通过接收到的TPF信息，应用功能实体(AF，ApplicationFunction)信息以及在线计费系统(OCS，Online Charging System)信息作为输入，用于选取适当的计费规则，在TPF请求或者有特定事件触发的时候将选取的计费规则发送给TPF。CRF, CRF is a functional entity that saves charging rules, supports dynamic charging rules, that is, generates some charging rule data in real time according to business criteria, and static charging rules, that is, charging rules in the process of users using data services is immutable. Static charging rules can be activated by dynamic charging rules. CRF uses the received TPF information, application function entity (AF, ApplicationFunction) information and online charging system (OCS, Online Charging System) information as input to select the appropriate charging rule, which is triggered by a TPF request or a specific event The selected charging rules are sent to the TPF at the time.
一个CRF可以对应多个TPF。One CRF can correspond to multiple TPFs.
AF，AF代表所有和应用相关的功能实体，AF向CRF提供相应的信息使得CRF可以选择或配置相应的计费规则，AF提供的信息包括：业务数据流的标识信息，可以设置为通配，计费规则选择的信息，应用/业务标识，应用/业务计费规则触发时间，流类型，可以选择为视频或音频，流速率。AF, AF represents all application-related functional entities. AF provides corresponding information to CRF so that CRF can select or configure corresponding charging rules. The information provided by AF includes: identification information of business data flow, which can be set as wildcard, Charging rule selection information, application/service identification, application/service charging rule trigger time, stream type, which can be selected as video or audio, and stream rate.
一个AF可以对应于多个CRF。AF可以根据用户的标识信息选择CRF进行交互。One AF can correspond to multiple CRFs. The AF may select a CRF for interaction according to the user's identification information.
OCS，OCS作为在线计费系统由业务控制点(SCP，Service Control Point)和信用控制(CC，Credit Control)两个功能实体组成，其中CC对在线计费时的用户信用进行管理。当用户使用业务时，CCF对该用户信用池中的信用进行授权，并向TPF下发用户可以使用的信用。通过Ry接口，OCS可以向CRF提供计费规则选择的输入信息。OCS, as an online charging system, OCS is composed of two functional entities: Service Control Point (SCP, Service Control Point) and Credit Control (CC, Credit Control), where CC manages user credit during online charging. When a user uses a service, the CCF authorizes the credit in the user's credit pool, and issues the credit that the user can use to the TPF. Through the Ry interface, the OCS can provide input information for charging rule selection to the CRF.
计费网关实体/计费收集实体(CCF/CGF，Charging GatewayFunction/Charging Collection Function)，这两个功能实体是用于离线计费系统的，可以沿用现有的GPRS网络计费中的实现。Charging Gateway Entity/Charging Collection Entity (CCF/CGF, Charging Gateway Function/Charging Collection Function), these two functional entities are used in the offline charging system, and can follow the implementation in the existing GPRS network charging.
如果承载网络是GPRS网络，则TPF位于GGSN处，AF为PDN中的一个业务网关，或是业务服务器。当IP多媒体子系统(IMS)承载在GPRS网络之上时AF就是P-CSCF，CRF为新增的逻辑实体；当IP多媒体子系统(IMS)承载在3GPP2的分组网络中时，TPF就位于PDSN上；IP多媒体子系统(IMS)承载在WLAN的网络结构中时，TPF就是分组数据网关(PDG)的一个逻辑功能。If the bearer network is a GPRS network, the TPF is located at the GGSN, and the AF is a service gateway or a service server in the PDN. When the IP Multimedia Subsystem (IMS) is carried on the GPRS network, the AF is the P-CSCF, and the CRF is a newly added logical entity; when the IP Multimedia Subsystem (IMS) is carried on the 3GPP2 packet network, the TPF is located in the PDSN Above; when IP Multimedia Subsystem (IMS) is carried in the network structure of WLAN, TPF is a logical function of Packet Data Gateway (PDG).
目前，根据规范23.125v610中对计费规则的定义，计费规则包含的内容有：一个特定业务数据流的计费方式：在线计费还是离线计费、在离线计费时是按流量、时长还是流量和时长进行记录、计费键、一个或者多个业务数据流过滤器、优先级以及计费规则标识。其中，业务数据流过滤器是用来区分属于一个特定业务数据流的分组数据包的，基本的构成是IP五元组，包括源IP地址，目的IP地址，源端口号，目的端口号，传输协议号或者应用协议号；计费键是用于确定费率的；优先级是在计费规则出现重叠的时候用于确定应用哪一个计费规则用的；计费规则标识是用来标识计费规则的。At present, according to the definition of billing rules in specification 23.125v610, the billing rules include: the billing method of a specific service data flow: online billing or offline billing, whether offline billing is based on traffic, duration It also records traffic and duration, billing key, one or more service data flow filters, priority and billing rule identification. Among them, the service data flow filter is used to distinguish packet data packets belonging to a specific service data flow. The basic composition is an IP quintuple, including source IP address, destination IP address, source port number, destination port number, transmission The protocol number or application protocol number; the charging key is used to determine the charging rate; the priority is used to determine which charging rule to apply when the charging rules overlap; the charging rule ID is used to identify the charging rule fee rules.
在实施业务的时候，TPF根据选定的计费规则，对该业务数据流的分组数据包进行过滤，可能是以时长为单位，也可能是以流量为单位，或者以流量加时长为单位，生成承载计费信息，送给计费相关功能实体产生用户的最终话单。When implementing the service, TPF filters the grouped data packets of the service data flow according to the selected charging rules, which may be based on the duration, or the flow, or the flow plus time. Generate bearer charging information and send it to charging-related functional entities to generate the user's final bill.
在实现基于业务的本地策略控制功能时，3GPP定义了UE本地承载业务、GPRS承载业务和外部承载业务之间的交互，以及这些组合在一起为分组域端到端业务提供业务质量(QoS)。IP承载管理功能(IP BS Manager)在UE和GGSN中都可能存在，一般使用差分服务(DiffServ)或综合服务/资源预留(IntServ/RSVP)与外部IP网络进行互通。When realizing the service-based local policy control function, 3GPP defines the interaction between UE local bearer service, GPRS bearer service and external bearer service, and the combination of these services provides quality of service (QoS) for packet domain end-to-end services. The IP bearer management function (IP BS Manager) may exist in both UE and GGSN, and generally uses differentiated services (DiffServ) or integrated services/resource reservations (IntServ/RSVP) to communicate with external IP networks.
同时，3GPP描述了为分组域提供端到端QoS的IP层必需机制，通过基于业务的本地策略控制机制实现。图3为基于业务的本地策略控制机制构架示意图：策略决策功能(PDF，Policy Decision Function)和UE通过SIP协议交互，PDF从应用服务器得到应用层如会话描述协议(SDP，SessionDescription Protocol)中的参数，将该应用层参数信息映射到IP QoS参数如RSVP中，该映射遵守特定的策略规则。PDF的决策将传送到GGSN中的IP承载管理功能，进一步通过翻译/映射功能映射到UMTS承载管理功能上，GGSN完成相应的IP策略执行点(PEP，IP Policy Enforcement Point)功能。PDF和GGSN之间的Go接口采用公共开放协议服务(COPS，Common OpenPolicy Service)协议，传送QoS相关信息和策略。At the same time, 3GPP has described the IP layer necessary mechanism for providing end-to-end QoS for the packet domain, which is realized through the local policy control mechanism based on the business. Figure 3 is a schematic diagram of a service-based local policy control mechanism: the Policy Decision Function (PDF, Policy Decision Function) interacts with the UE through the SIP protocol, and the PDF obtains the parameters in the application layer such as the Session Description Protocol (SDP, Session Description Protocol) from the application server , mapping the application layer parameter information to IP QoS parameters such as RSVP, and the mapping complies with specific policy rules. The PDF decision will be transmitted to the IP bearer management function in the GGSN, and further mapped to the UMTS bearer management function through the translation/mapping function, and the GGSN will complete the corresponding IP Policy Enforcement Point (PEP, IP Policy Enforcement Point) function. The Go interface between PDF and GGSN adopts the Common Open Policy Service (COPS, Common OpenPolicy Service) protocol to transmit QoS related information and policies.
3GPP R5中只为IMS业务提供基于业务的QoS控制，所以PDF是IMS实体P-CSCF中的逻辑实体。R6阶段PDF是一个单独的功能实体，可以为所有分组域业务提供基于业务的QoS策略控制。当其他类型的承载网络要实现基于业务的策略控制的时候，PEP就在对应的网关设备上实现。当使用IMS的时候，AF就是P-CSCF中的逻辑实体。3GPP R5 only provides service-based QoS control for IMS services, so PDF is a logical entity in the IMS entity P-CSCF. R6 stage PDF is a separate functional entity, which can provide business-based QoS policy control for all packet domain services. When other types of bearer networks need to implement service-based policy control, PEP is implemented on the corresponding gateway device. When using IMS, AF is a logical entity in P-CSCF.
当UE请求建立传送业务数据的承载连接时，PEP向PDF发送请求(REQ，Request)消息，其中携带客户端的对话信息，用于标识对应PDF的授权令牌以及该会话中一个或者多个流的标识。如果通过了授权，则PDF返回决定(DEC，Decision)消息给PEP，其中携带客户端的对话信息，控制层面计费标识，上下行指示，授权的QOS信息，过滤器信息以及对应的通道是否打开的状态信息。然后GGSN会根据DEC的执行情况，返回报告(RPT，Report)消息给PDF，报告执行的结果等。When the UE requests to establish a bearer connection for transmitting service data, the PEP sends a request (REQ, Request) message to the PDF, which carries the session information of the client, which is used to identify the authorization token corresponding to the PDF and the ID of one or more flows in the session logo. If the authorization is passed, the PDF returns a decision (DEC, Decision) message to the PEP, which carries the client's dialogue information, control plane charging identifier, uplink and downlink instructions, authorized QOS information, filter information and whether the corresponding channel is opened status information. Then the GGSN will return a report (RPT, Report) message to the PDF according to the execution of the DEC, and report the execution result, etc.
通过对现有IMS网络和承载网络之间，即现有业务控制层和承载网络之间在计费和策略控制方面的实现机制可以看到：为了实现业务控制和承载的无关性，网关功能实体和业务控制层上对应的功能实体之间都没有传送任何承载网络相关的信息，这一方面是好处，另一方面也造成了一些信息的缺失，比如，关于承载网络类型的信息。Through the implementation mechanism of charging and policy control between the existing IMS network and the bearer network, that is, between the existing service control layer and the bearer network, it can be seen that: in order to realize the independence of service control and bearer, the gateway functional entity No information related to the bearer network is transmitted between the corresponding functional entities on the service control layer. This is an advantage on the one hand, but on the other hand, it also causes the lack of some information, for example, information about the type of bearer network.
IMS网络最初出现的时候，只是给UMTS一种类型的网络使用的，因此，不需要GGSN向IMS中的功能实体上报任何承载网络类型信息，因为只有UMTS一种类型，但是当IMS扩展到可以应用在多种类型的承载网络上的时候，在实施某个业务的过程中，运营商需要知道这个业务具体是承载在哪个网络上的。这是因为不同的承载网络，在计费、服务质量、安全等方面的要求还是会有所区别的，即使理论上没有区别，运营商也可能需要根据自己的运营策略，制定对应的业务模式。比如，在第三代移动通信(3G)网络发展初期，为了鼓励用户使用3G网络，培养用户习惯等，运营商就希望使用UMTS网络的用户要比使用WLAN网络的用户收费要低一些。When the IMS network first appeared, it was only used for one type of UMTS network. Therefore, there is no need for the GGSN to report any bearer network type information to the functional entity in the IMS, because there is only one type of UMTS, but when the IMS is extended to be applicable In the process of implementing a certain service on multiple types of bearer networks, the operator needs to know which network the service is carried on. This is because different bearer networks have different requirements in terms of billing, service quality, and security. Even if there is no difference in theory, operators may need to formulate corresponding business models according to their own operating strategies. For example, in the initial stage of the development of the third-generation mobile communication (3G) network, in order to encourage users to use the 3G network and cultivate user habits, operators hope that users using the UMTS network will charge lower fees than users using the WLAN network.
此外，分析现有UMTS分组交换网络的实现：由于UMTS网络中的接入网使用了多种接入技术，包括WCDMA和从GSM演进的增强数据速率(EDGE)，以后还会有时分同步的码分多址(TD-SCDMA)技术等，所以，核心网为了在计费、服务质量等方面针对不同接入网进行不同的处理，目前核心网可以得到接入网传送的无线接入技术类型相关的信息(RAT type，Radio Access Technologies type)。由此进行推理，当IMS网络扩展到可以应用在多种类型的承载网络上时，有关承载网络类型的信息也需要让IMS网络业务控制层中的相关功能实体知道，从而针对不同的承载网络能够实施不同的业务处理。In addition, the implementation of the existing UMTS packet-switched network is analyzed: since the access network in the UMTS network uses a variety of access technologies, including WCDMA and Enhanced Data Rates Evolved from GSM (EDGE), there will be time-division synchronized codes in the future Multiple Access (TD-SCDMA) technology, etc. Therefore, in order to perform different processing for different access networks in terms of billing and service quality, the core network can currently obtain information related to the type of wireless access technology transmitted by the access network. information (RAT type, Radio Access Technologies type). Based on this reasoning, when the IMS network is extended to be applied to multiple types of bearer networks, the information about the bearer network type also needs to be known to the relevant functional entities in the service control layer of the IMS network, so that different bearer networks can Implement different business processes.
因此，如何让IMS网络业务控制层中的相关功能实体确定当前承载网络的网络类型，从而根据不同承载网络类型实施不同的业务处理，成为了亟待解决的问题。Therefore, how to let relevant functional entities in the IMS network service control layer determine the network type of the current bearer network, so as to implement different service processing according to different bearer network types, has become an urgent problem to be solved.
发明内容Contents of the invention
有鉴于此，本发明的主要目的在于提供一种在业务控制网络中根据不同承载网络类型实施不同业务处理的方法，该方法能够让IMS网络业务控制层中的相关功能实体确定当前承载网络的网络类型，从而根据不同承载网络类型实施不同的业务处理。In view of this, the main purpose of the present invention is to provide a method for implementing different service processing according to different bearer network types in the service control network, which can allow relevant functional entities in the service control layer of the IMS network to determine the current bearer network network Type, so as to implement different service processing according to different bearer network types.
根据上述目的，本发明的技术方案是这样实现的：According to above-mentioned purpose, technical scheme of the present invention is achieved like this:
一种根据不同承载网络类型实施不同业务处理的方法，该方法包括：A method for implementing different service processing according to different bearer network types, the method comprising:
A、业务控制层中的功能实体获取当前用户设备使用的承载网络类型信息；A. The functional entity in the service control layer obtains the type information of the bearer network currently used by the user equipment;
B、业务控制层中的该功能实体根据该承载网络类型信息确定承载网络类型，实施不同的业务处理。B. The functional entity in the service control layer determines the bearer network type according to the bearer network type information, and implements different service processing.
当承载层中的功能实体和业务控制层中对应的功能实体之间存在业务控制接口并且该接口用于承载过程的业务控制处理时，步骤A所述的承载网络类型信息是承载层的功能实体发送给业务控制层中对应的功能实体的。When there is a service control interface between the functional entity in the bearer layer and the corresponding functional entity in the service control layer and this interface is used for service control processing of the bearer process, the bearer network type information described in step A is the functional entity of the bearer layer It is sent to the corresponding functional entity in the service control layer.
步骤A所述的承载网络类型信息预先设置在承载层的功能实体中。The bearer network type information described in step A is preset in the functional entity of the bearer layer.
步骤A所述的承载网络类型信息是由用户设备确定并发送给承载层的功能实体的。The bearer network type information described in step A is determined by the user equipment and sent to the functional entity of the bearer layer.
当承载层中的功能实体和业务控制层中对应的功能实体之间不存在业务控制接口或存在的业务控制接口不用于承载过程的业务控制处理时，步骤A所述的承载网络类型信息是用户设备发送给业务控制层中对应的功能实体的。When there is no service control interface between the functional entity in the bearer layer and the corresponding functional entity in the service control layer or the existing service control interface is not used for the service control process of the bearer process, the bearer network type information described in step A is the user The device sends it to the corresponding functional entity in the service control layer.
所属的承载过程为承载建立过程、承载修改过程和承载删除过程。The associated bearer processes are bearer establishment process, bearer modification process and bearer deletion process.
业务控制层中的该功能实体针对不同承载网络类型设置有不同的业务处理策略；The functional entity in the service control layer has different service processing strategies for different bearer network types;
步骤B所述确定承载网络类型之后，该方法进一步包括：业务控制层中的该功能实体根据确定的承载网络类型选择对应的业务处理策略，按照选择的业务处理策略实施不同的业务处理。After the bearer network type is determined in step B, the method further includes: the functional entity in the service control layer selects a corresponding service processing strategy according to the determined bearer network type, and implements different service processing according to the selected service processing strategy.
所述的业务控制处理包括：基于业务数据流的计费、或者基于业务的本地策略控制、或者在呼叫进行中的鉴权和授权过程。The service control process includes: charging based on service data flow, or local policy control based on service, or authentication and authorization process during a call.
从上述方案可以看出，由于本发明提供的方法可以由UE或者承载层提供给业务控制层当前业务所在的承载类型，所以本发明提供的方法可以用于实现业务与控制分离，控制与承载分离的下一代网络架构中，业务控制层能够根据业务所使用的承载网络的不同，实施不同的业务处理，包括计费、服务质量保证、策略控制、安全、合法监听等。通过本发明，可以在完全独立演进的业务控制层和承载层之间传递彼此有用的信息，使得具体业务的实施不但可以做到承载网络无关性，也可以根据承载网络的特点在业务控制网络中实现差异性服务。前者的无关性是出于各自独立演进，独立发展考虑，后者的差异性是针对承载网络实现技术对业务的影响考虑的，同时也能够体现运营商的运营策略。因此，该方法能够让IMS网络业务控制层中的相关功能实体确定当前承载网络的网络类型，从而根据不同承载网络类型实施不同的业务处理。It can be seen from the above scheme that since the method provided by the present invention can be provided by the UE or the bearer layer to the bearer type of the current service of the service control layer, the method provided by the present invention can be used to realize the separation of service and control, and the separation of control and bearer In the next-generation network architecture, the service control layer can implement different service processing according to the bearer network used by the service, including billing, service quality assurance, policy control, security, legal interception, etc. Through the present invention, mutually useful information can be transferred between the completely independently evolved service control layer and the bearer layer, so that the implementation of specific services can not only be independent of the bearer network, but also can be carried out in the service control network according to the characteristics of the bearer network. Realize differentiated services. The former's irrelevance is due to their independent evolution and development considerations, while the latter's differences are considered for the impact of bearer network implementation technologies on services, and can also reflect operators' operating strategies. Therefore, the method enables relevant functional entities in the service control layer of the IMS network to determine the network type of the current bearer network, so as to implement different service processing according to different bearer network types.
附图说明Description of drawings
图1为支持在线计费的FBC系统结构图。Figure 1 is a structural diagram of an FBC system supporting online charging.
图2为支持离线计费的FBC系统结构图。Fig. 2 is a structural diagram of an FBC system supporting offline charging.
图3为基于业务的本地策略控制机制构架示意图。FIG. 3 is a schematic diagram of a structure of a service-based local policy control mechanism.
图4为本发明的IMS网络业务控制层中的相关功能实体确定当前承载网络的网络类型的一个实施例流程图。Fig. 4 is a flowchart of an embodiment of determining the network type of the current bearer network by relevant functional entities in the IMS network service control layer of the present invention.
图5为本发明的IMS网络业务控制层中的相关功能实体确定当前承载网络的网络类型的另一个实施例流程图。Fig. 5 is a flowchart of another embodiment of determining the network type of the current bearer network by relevant functional entities in the IMS network service control layer of the present invention.
图6为本发明在进行基于业务数据流的计费过程中业务控制层利用承载网类型信息进行不同业务处理的流程图。Fig. 6 is a flow chart of the service control layer using bearer network type information to process different services in the charging process based on the service data flow in the present invention.
图7为本发明承载层修改时触发的重新授权过程的流程图。Fig. 7 is a flow chart of the re-authorization process triggered when the bearer layer is modified in the present invention.
图8为本发明在进行基于业务的本地策略控制过程中业务控制层利用不同承载网类型信息进行不同业务处理的流程图。FIG. 8 is a flow chart of the service control layer using different bearer network type information to process different services during the service-based local policy control process of the present invention.
图9为本发明在呼叫控制过程中业务控制层利用不同承载网类型信息进行不同业务处理的示意图。FIG. 9 is a schematic diagram of the service control layer using different bearer network type information to process different services during the call control process of the present invention.
具体实施方式Detailed ways
为了使本发明的目的、技术方案和优点更加清楚明白，以下举实施例并参照附图，对本发明进行进一步详细说明。In order to make the purpose, technical solution and advantages of the present invention more clear, the present invention will be further described in detail by citing the following embodiments and referring to the accompanying drawings.
本发明考虑到承载网络对业务实施在某些方面会产生一定的影响，因此需要IMS网络业务控制层中的相关功能实体知道目前实施的业务所使用的承载网络类型。The present invention considers that the bearer network will have a certain impact on service implementation in some aspects, so the relevant functional entities in the service control layer of the IMS network need to know the bearer network type used by the currently implemented service.
本发明当承载层和业务控制层存在业务控制接口时，可以通过用户利用承载网络第一次和业务控制层中的相关功能实体建立联系时通知给相关功能实体。图4为本发明的IMS网络业务控制层中的相关功能实体确定当前承载网络的网络类型的一个实施例流程图，其具体步骤为：In the present invention, when there is a service control interface between the bearer layer and the service control layer, the relevant functional entity can be notified when the user uses the bearer network to establish contact with the relevant functional entity in the service control layer for the first time. Fig. 4 is a flow chart of an embodiment of determining the network type of the current bearer network for relevant functional entities in the IMS network service control layer of the present invention, and its specific steps are:
步骤400、UE向承载层中相应的功能实体发起承载建立请求，为使用某个业务申请承载资源；
步骤401、承载层中的该功能实体收到该请求之后，发现需要和业务控制层建立联系，那么根据本地的配置信息或者从其他功能实体得到的信息确定自己所在承载网络的类型；Step 401: After receiving the request, the functional entity in the bearer layer finds that it needs to establish contact with the service control layer, then determines the type of bearer network it is in according to local configuration information or information obtained from other functional entities;
步骤402、承载层中的该功能实体发送执行某个业务控制的请求消息给业务控制层对应的功能实体，该请求消息中带有承载网络类型信息；
步骤403、业务控制层对应的功能实体判断自身是否根据不同的承载网络类型设置了不同的业务控制处理，如果否，执行步骤404；否则，执行步骤405；
步骤404、业务控制层对应的功能实体不需要根据承载网络类型进行不同的业务控制处理，直接对该业务控制请求进行相应的处理，执行业务控制之后，返回应答消息给承载层的该功能实体，执行步骤406；
步骤405、业务控制层对应的功能实体根据该请求消息中带有的承载网络类型信息确定承载网络类型，根据确定网络类型对该业务控制请求进行相应的处理，执行业务控制之后，返回应答消息给承载层的该功能实体；
步骤406、承载层的该功能实体根据业务控制层返回的应答消息，结合本地的策略和信息，返回承载建立请求的应答消息给UE。
步骤401中承载层的该功能实体在确定自己所在承载网络的类型时可以有多种实现方法，在此简单描述其中一些方法：In
方法一：在建立网络时预先将该功能实体所在的承载网络类型设置在该功能实体上，当该功能实体需要和控制层面功能实体交互消息的时候，直接将该信息填入对应的消息中；Method 1: Set the bearer network type of the functional entity on the functional entity in advance when establishing the network, and when the functional entity needs to exchange messages with the control plane functional entity, directly fill in the information into the corresponding message;
方法二：UE在选择承载网络接入到业务控制层时，将选定的承载网络类型信息放在承载建立请求消息中一起送给和业务控制层有交互的承载层中的该功能实体，该功能实体直接利用该信息；Method 2: When the UE selects the bearer network to access the service control layer, it puts the selected bearer network type information in the bearer establishment request message and sends it to the functional entity in the bearer layer that interacts with the service control layer. Functional entities use this information directly;
方法三：承载层的该功能实体不需要显式的携带承载网络类型送给业务控制层的功能实体，两个层面的功能实体在交互的信息中有一些参数就可以指示承载网络的类型是什么。Method 3: The functional entity of the bearer layer does not need to explicitly carry the type of the bearer network to the functional entity of the service control layer. The functional entities of the two layers can indicate the type of the bearer network with some parameters in the exchanged information. .
有的网络配置中，承载层和业务控制层之间不存在直接的业务控制接口，或者存在的业务控制接口不用于承载建立过程中的业务处理。那么UE可以通过承载层协议建立承载面连接之后，利用该连接直接和业务控制层交互，承载层直接透传业务控制层消息，在该消息中，用户设备将承载网络的类型信息直接通知给业务控制网络，如图5所示，图5为本发明的IMS网络业务控制层中的相关功能实体确定当前承载网络的网络类型的另一个实施例流程图，其具体步骤为：In some network configurations, there is no direct service control interface between the bearer layer and the service control layer, or the existing service control interface is not used for service processing during bearer establishment. After the UE establishes the bearer plane connection through the bearer layer protocol, it can use the connection to directly interact with the service control layer, and the bearer layer directly transparently transmits the message of the service control layer. In this message, the user equipment directly notifies the type information of the bearer network to the service Control network, as shown in Figure 5, Figure 5 is another embodiment flow chart of determining the network type of the current bearer network for relevant functional entities in the IMS network service control layer of the present invention, and its specific steps are:
步骤500、UE向承载层的相应功能实体发起承载建立请求，为使用某个业务申请承载资源；
步骤501、承载层的该功能实体收到该请求之后，根据用户在承载层的签约信息，决定接受这个承载建立请求，返回承载建立接受消息；Step 501: After receiving the request, the functional entity of the bearer layer decides to accept the bearer establishment request according to the subscription information of the user at the bearer layer, and returns a bearer establishment acceptance message;
步骤502、UE根据自己请求的业务确定承载网络类型相关信息；
步骤503、UE发送业务控制层的请求消息给业务控制层的功能实体，该请求消息中带有承载网络类型信息；
步骤504、业务控制层对应的功能实体判断自身是否根据不同的承载网络类型设置了不同的业务控制处理，如果否，执行步骤505；否则，执行步骤506；
步骤505、业务控制层对应的功能实体不需要根据承载网络类型进行不同的业务控制处理，直接对该业务控制请求进行相应的处理，执行业务控制之后，返回应答消息给UE；
步骤506、业务控制层对应的功能实体根据该请求消息中带有的承载网络类型相关信息确定承载网络类型，根据确定网络类型对该业务控制请求进行相应的处理，执行业务控制之后，返回应答消息给UE。
业务控制层得到承载网络类型信息之后，可以在今后的业务控制执行过程中直接使用该信息，例如主动从业务控制层向承载层发送业务控制消息，其中携带的业务处理就是针对当前用户设备使用的承载网络的。After the service control layer obtains the bearer network type information, it can directly use the information in the future service control execution process, such as actively sending service control messages from the service control layer to the bearer layer, and the service processing carried in it is for the current user equipment. carrying the network.
除了以上处理过程之外，在后续业务的执行过程中，如果发生了承载网络之间的切换，也需要使用类似的方法将新的承载网络类型信息通知给业务控制层。In addition to the above processing, in the execution of subsequent services, if a switch between bearer networks occurs, a similar method needs to be used to notify the service control layer of the new bearer network type information.
因为业务控制层执行的业务处理种类非常多，涉及计费、安全、策略控制、服务质量保证等所有和通信网络运营有关的方面。所以，在此，就计费、策略控制以及呼叫控制的处理过程为例进行说明。Because there are many types of business processing performed by the business control layer, involving all aspects related to communication network operations such as billing, security, policy control, and service quality assurance. Therefore, here, the processing procedures of charging, policy control and call control are taken as examples for description.
图6为本发明在进行基于业务数据流的计费过程中业务控制层利用承载网类型信息进行不同业务处理的流程图，本发明以在线计费的实现为例说明，假设使用WLAN网络作为承载网络，TPF是PDG的一个逻辑功能，在CRF处，针对WLAN网络接入和GPRS网络接入使用的计费规则是不同的，其具体步骤为：Figure 6 is a flowchart of the service control layer using bearer network type information to process different services in the charging process based on the service data flow in the present invention. The present invention takes the realization of online charging as an example to illustrate, assuming that a WLAN network is used as the bearer Network, TPF is a logical function of PDG. At CRF, the charging rules for WLAN network access and GPRS network access are different. The specific steps are:
步骤600、UE向TPF发送承载建立请求消息(Establish Bearer Serv Req)；对于WLAN，就是PDG接收到隧道建立请求消息；Step 600, the UE sends a bearer establishment request message (Establish Bearer Serv Req) to the TPF; for WLAN, the PDG receives the tunnel establishment request message;
步骤601、TPF向CRF请求计费规则(Request Charging Rules)，消息中携带决定CRF选择计费规则的输入信息；Step 601, the TPF requests charging rules (Request Charging Rules) from the CRF, and the message carries the input information for determining the charging rules selected by the CRF;
对于WLAN，其中包括：使用UE的用户和UE信息，如移动签约用户ISDN号码(MSISDN)，国际移动设备标识及软件版本号(IMEISVI，nternational Mobile station Equipment Identity and Software Version Number)等；承载特征，如协商后的QoS，无线局域网的接入点名(W-APN，WLAN-Access Point Name)等；网络信息，如移动国家码(MCC，MobileCountry Code)和移动网络码(MNC，Mobile Network Code)；还有承载网络类型，即WLAN网络；For WLAN, it includes: user and UE information using UE, such as mobile subscriber ISDN number (MSISDN), international mobile equipment identity and software version number (IMEISVI, international Mobile station Equipment Identity and Software Version Number), etc.; bearer characteristics, Such as negotiated QoS, WLAN access point name (W-APN, WLAN-Access Point Name), etc.; network information, such as mobile country code (MCC, MobileCountry Code) and mobile network code (MNC, Mobile Network Code); There is also a type of bearer network, that is, a WLAN network;
步骤602、CRF根据得到的信息来选择相应的计费规则(IdentifyCharging Rules To Install)，除了TPF带上来的承载以及用户相关的信息之外，此时CRF处可能也会得到来自AF的应用和业务相关信息以及来自OCS的信用控制相关信息；Step 602, the CRF selects the corresponding charging rules (IdentifyCharging Rules To Install) according to the obtained information. In addition to the bearer and user-related information brought by the TPF, the CRF may also obtain applications and services from the AF at this time Relevant information and credit control related information from OCS;
步骤603、CRF处根据用户标识查找该用户的计费规则信息，发现相同的业务，针对WLAN承载和其他承载，如GPRS承载，应用的计费规则是不一样的，那么CRF根据承载网络类型进行选择，将应用于WLAN网络的计费规则(Provision Charging Rules)下发给TPF，作为计费规则请求消息的应答；Step 603, the CRF searches for the charging rule information of the user according to the user ID, and finds that the same service is applied for WLAN bearer and other bearer, such as GPRS bearer, and the applied charging rule is different, so the CRF performs the charging rule according to the bearer network type. Select, send the provision charging rules (Provision Charging Rules) applied to the WLAN network to the TPF as a response to the charging rule request message;
步骤604、TPF根据CRF提供的对计费规则的操作指示，对相应的计费规则执行应用(Perform Charging Rules Actions)；Step 604, the TPF executes the application (Perform Charging Rules Actions) on the corresponding charging rules according to the operation instructions on the charging rules provided by the CRF;
步骤605、在线计费情况下，TPF向OCS请求信用信息(Credit Request)，消息中携带OCS决定信用所需的输入信息；Step 605, in the case of online charging, the TPF requests credit information (Credit Request) from the OCS, and the message carries the input information required by the OCS to determine the credit;
步骤606、OC S向TPF提供信用信息(Credit Response)；Step 606, OCS provides credit information (Credit Response) to TPF;
步骤607、TPF向UE返回承载建立接受消息(Establish Bearer ServAccept)，UE就可以在已经建立的承载上传输数据了。In step 607, the TPF returns a bearer establishment acceptance message (Establish Bearer ServAccept) to the UE, and the UE can transmit data on the established bearer.
执行完步骤607之后，UE就可以在已经建立的承载上执行业务请求和数据传输了，比如请求和网络中的一个应用服务器建立业务连，传送业务请求过程、执行过程以及中止过程中所需的数据，接收来自应用服务器的信息等等，这些数据的传输都要占用承载资源。对于实现了基于业务数据流计费的承载网络来说，在TPF处，根据每个分组数据包所属的业务流的不同，TPF将应用不同的计费规则，将相关的承载计费信息上报给计费相关功能实体。After step 607 is executed, the UE can perform service request and data transmission on the established bearer, such as requesting to establish a service connection with an application server in the network, and transmitting the service request process, execution process and termination process. Data, receiving information from the application server, etc., the transmission of these data will occupy bearer resources. For a bearer network that implements charging based on service data flow, at the TPF, according to the different service flows to which each packet belongs, the TPF will apply different charging rules and report the relevant bearer charging information to Charging-related functional entities.
因为该业务使用的承载网络发生变化时会导致使用不同的计费规则。为了能够监控承载网络类型的变化，TPF中可以配置一些触发点，当承载网络类型发生变化时触发该触发点，在离线计费时上报给CRF或者在在线计费时上报给OCS，从而CRF或者OCS可以根据承载网络的变化情况选择不同的计费规则。图7为本发明承载层修改时触发的重新授权过程的流程图，其具体步骤为：Because when the bearer network used by this service changes, different charging rules will be used. In order to be able to monitor the change of the bearer network type, some trigger points can be configured in the TPF. When the bearer network type changes, the trigger point is triggered and reported to the CRF during offline charging or reported to the OCS during online charging, so that the CRF or The OCS can select different charging rules according to the change of the bearer network. Figure 7 is a flow chart of the re-authorization process triggered when the bearer layer is modified in the present invention, and its specific steps are:
步骤700、TPF收到修改承载的请求消息(Modify Bearer Serv Req)；Step 700, the TPF receives a request message for modifying the bearer (Modify Bearer Serv Req);
步骤701、TPF判断此次承载的修改是否匹配重授权触发点，如果是，执行步骤703；否则，执行步骤702；Step 701, TPF judges whether the modification of the bearer matches the re-authorization trigger point, if yes, execute step 703; otherwise, execute step 702;
这里承载修改是从GPRS承载改为使用WLAN承载，因此匹配TPF中设置有从GPRS承载改为WLAN承载的重授权触发点；Here, the bearer modification is changed from GPRS bearer to WLAN bearer, so the re-authorization trigger point for changing from GPRS bearer to WLAN bearer is set in the matching TPF;
步骤702、继续进行后续会话处理；Step 702, continue to perform subsequent session processing;
步骤703、TPF返回该计费规则下没有用完的信息给OCS，同时请求对该计费规则进行重新授权(Credit Control Request)；Step 703, the TPF returns the unused information under the charging rule to the OCS, and requests the charging rule to be re-authorized (Credit Control Request);
步骤704、OCS执行重授权过程，在帐户充足的情况下，返回新的信用给TPF(Credit Control Answer)；Step 704, OCS executes the re-authorization process, and returns new credit to TPF (Credit Control Answer) if the account is sufficient;
步骤705、TPF根据返回的信用更改计费规则，即从基于GPRS承载的计费规则改为基于WLAN承载的计费规则，并向UE发送接受此次承载修改请求(Modify Bearer Serv Accept)。Step 705, the TPF changes the charging rule according to the returned credit, that is, from the charging rule based on the GPRS bearer to the charging rule based on the WLAN bearer, and sends a modify bearer serv accept request (Modify Bearer Serv Accept) to the UE.
图8为本发明在进行基于业务的本地策略控制过程中业务控制层利用不同承载网类型信息进行不同业务处理的流程图，假设UE可以从WCDMA网络或者cdma2000网络中接入IMS，但是使用不同承载网络接入的时候，相同的业务，签约的QoS参数等不同，那么PDF在执行策略控制的时候，需要知道当前业务承载的承载网络类型是什么，从而选择不同的策略下发给PEP执行。其具体步骤为：Figure 8 is a flow chart of the service control layer using different bearer network type information to process different services in the process of service-based local policy control in the present invention, assuming that the UE can access the IMS from a WCDMA network or a cdma2000 network, but uses different bearers When accessing the network, the same service has different contracted QoS parameters. When implementing policy control, the PDF needs to know the type of the bearer network that the current service bears, so that it can select different policies and send them to the PEP for execution. The specific steps are:
步骤800、UE发送承载建立请求给承载网络中具有PEP的功能实体，其中带有QoS参数、用于PDF寻址和标识数据流的绑定信息；Step 800, UE sends a bearer establishment request to a functional entity with PEP in the bearer network, which contains QoS parameters, binding information for PDF addressing and identification data flow;
步骤801、PEP所在的功能实体发送COPS请求(COPS REQ)消息给PDF，以便获取相关的策略信息，其中带有绑定信息和能够区分承载网络类型的信息；Step 801, the functional entity where the PEP is located sends a COPS request (COPS REQ) message to the PDF in order to obtain relevant policy information, which contains binding information and information capable of distinguishing bearer network types;
步骤802、绑定信息中的授权令牌使得PDF能够找到对应的授权状态信息，然后PDF通过Gq接口发送授权请求给AF；Step 802, the authorization token in the binding information enables the PDF to find the corresponding authorization status information, and then the PDF sends an authorization request to the AF through the Gq interface;
步骤803、AF将所请求的业务信息发送给PDF，即通过Gq接口返回授权确认；Step 803, AF sends the requested business information to PDF, that is, returns an authorization confirmation through the Gq interface;
步骤804、PDF根据来自AF的信息，检查AF处的会话描述和PDF中定义的运营商策略规则是否一致，如果一致，授权所需的QoS资源，应用IP层策略；当PDF检查时，发现运营商策略规则中针对不同承载类型网络的策略规则是不一样的，则进一步根据承载网络类型信息选择对应的策略规则和AF送来的会话描述进行比较，授权对应的QoS资源，应用对应的IP层策略；如果不一致，则结束本流程；Step 804, PDF checks whether the session description at the AF is consistent with the operator policy rules defined in the PDF according to the information from the AF, and if consistent, authorizes the required QoS resources and applies the IP layer policy; when the PDF checks, it finds that the operator In the policy rules of the provider, the policy rules for different types of bearer networks are different, and the corresponding policy rules are further selected according to the bearer network type information and compared with the session description sent by AF, the corresponding QoS resources are authorized, and the corresponding IP layer is applied. Policy; if inconsistent, end this process;
步骤805、PDF返回COPS决定(COPS DEC)消息给PEP所在的功能实体；Step 805, PDF returns the COPS decision (COPS DEC) message to the functional entity where the PEP is located;
步骤806、PEP所在的功能实体返回一个COPS报告(COPS RPT)消息给PDF，该过程可以触发PDF发送一个报告消息给AF；Step 806, the functional entity where the PEP is located returns a COPS report (COPS RPT) message to the PDF, and this process can trigger the PDF to send a report message to the AF;
步骤807、PEP所在的功能实体根据得到的基于IP流的策略信息将该策略映射到承载网络的承载层上，进而决定是否接受此次承载建立请求，接受的话，返回承载建立接受消息给UE；否则，结束本流程。Step 807, the functional entity where the PEP is located maps the policy to the bearer layer of the bearer network according to the obtained policy information based on the IP flow, and then decides whether to accept the bearer establishment request, and if accepted, returns a bearer establishment acceptance message to the UE; Otherwise, end this process.
图9为本发明在呼叫控制过程中业务控制层利用不同承载网类型信息进行不同业务处理的示意图，如图所示：Figure 9 is a schematic diagram of the service control layer using different bearer network type information to perform different service processing in the call control process of the present invention, as shown in the figure:
UEA和UEB各自执行a1和b1开机过程，然后根据各自所在的承载网络类型不同，进行不同的业务处理。The UEA and the UEB respectively perform a1 and b1 start-up processes, and then perform different service processing according to different types of bearer networks where they are located.
UEA使用的是GPRS网络，因此发起a2GPRS附着过程，利用a3建立好的PDP上下文向应用服务器AS以及IMS核心网发起a4IMS注册请求，注册消息中可以携带用户设备当前使用的承载网络类型的信息或者和不同承载网络相关的消息扩展部分。IMS核心网根据注册消息中和用户设备所使用的承载网络相关的信息判定UEA使用的承载网络是GPRS网络，因为GPRS网络的安全性较好，因此决定仅在UEA第一次进行注册的时候对该UEA进行鉴权，以后重新注册过程都直接返回确认，不进行重新鉴权。The UEA uses the GPRS network, so it initiates the a2GPRS attach process, uses the PDP context established in a3 to initiate an a4IMS registration request to the application server AS and the IMS core network, and the registration message can carry the information of the bearer network type currently used by the user equipment or the Message extensions related to different bearer networks. The IMS core network judges that the bearer network used by the UEA is the GPRS network according to the information related to the bearer network used by the user equipment in the registration message. Because the security of the GPRS network is better, it is decided to only register for the first time when the UEA registers. The UEA performs authentication, and the subsequent re-registration process will directly return confirmation without re-authentication.
UEB使用的是WLAN网络，因此发起b23GPP WLAN附着过程，利用b3建立好的WLAN隧道向应用服务器AS以及IMS核心网发起b4IMS注册请求，注册消息中可以携带用户设备当前使用的承载网络类型的信息或者和不同承载网络相关的消息扩展部分。IMS核心网根据注册消息中和用户设备所使用的承载网络相关的信息判定UEB使用的是WLAN网络，而WLAN网络的安全保护比较差，因此决定在UEB第一次进行注册的时候要进行鉴权过程，在以后重新注册的时候都要进行重新鉴权过程，以确保UEB没有被伪冒。The UEB uses a WLAN network, so it initiates the b23GPP WLAN attach process, uses the WLAN tunnel established in b3 to initiate a b4IMS registration request to the application server AS and the IMS core network, and the registration message can carry information about the bearer network type currently used by the user equipment or Message extensions related to different bearer networks. The IMS core network determines that the UEB is using a WLAN network based on the information related to the bearer network used by the user equipment in the registration message, and the security protection of the WLAN network is relatively poor, so it decides to perform authentication when the UEB registers for the first time process, the re-authentication process must be performed when re-registering in the future to ensure that the UEB is not faked.
本发明提供了一种使得业务控制网络能够根据业务所使用的承载网络类型不同而执行不同处理的方法，根据承载层和业务控制层之间是否存在直接的业务控制接口，使用不同的方法将用户设备使用的承载网络的类型信息通知给业务控制层，从而使得业务控制层能够根据承载网络的特点使用不同的计费策略，不同的服务质量，不同的安全级别等等，让运营商在实现具体应用的时候能够根据承载实施不同的业务控制，从而能够提供给用户有差异的服务，有利于细分客户群，培养用户习惯，达到提高效益的目的。The present invention provides a method for enabling the service control network to perform different processing according to the type of bearer network used by the service. According to whether there is a direct service control interface between the bearer layer and the service control layer, use different methods to The type information of the bearer network used by the device is notified to the service control layer, so that the service control layer can use different charging policies, different service qualities, different security levels, etc. according to the characteristics of the bearer network, so that operators can realize specific During application, different service controls can be implemented according to the bearer, so that users can be provided with differentiated services, which is conducive to subdividing customer groups, cultivating user habits, and achieving the purpose of improving efficiency.
由承载层或者用户设备上报承载网络类型信息给业务控制层的这种方法比较通用，不论业务控制层上的应用层执行的是什么具体应用，都可以根据承载网络类型的不同实施不同的业务控制处理，但是并不是所有的业务控制处理都需要区分承载网络类型。因此本发明还可以由应用层的具体业务自己决定是否需要根据承载网络类型的不同实施不同的业务控制处理，如果需要，那么根据该业务能够承载的网络类型，将对应的业务控制处理从业务控制层下发给承载层对应的功能实体使用，也能够达到业务控制网络根据承载网络类型执行不同业务处理的目的。这种方法的缺点是：因为不知道底层承载的具体类型，可能需要下发多种承载网络对应的业务控制处理信息，造成信息冗余，或者下发的业务控制处理信息不适合当前使用的承载网络。The method of reporting the type information of the bearer network to the service control layer by the bearer layer or user equipment is relatively general. No matter what specific application is executed by the application layer on the service control layer, different service control can be implemented according to the different bearer network types processing, but not all service control processing needs to distinguish bearer network types. Therefore, the present invention can also decide by the specific business of the application layer whether to implement different service control processing according to different bearer network types. If necessary, then according to the network type that the service can carry, the corresponding The layer is delivered to the corresponding functional entity of the bearer layer for use, and the purpose of the service control network performing different service processing according to the bearer network type can also be achieved. The disadvantage of this method is: because the specific type of the underlying bearer is not known, it may be necessary to deliver service control and processing information corresponding to multiple bearer networks, resulting in information redundancy, or the delivered service control and processing information is not suitable for the currently used bearer network.
以上所述仅为本发明的较佳实施例而已，并不用以限制本发明，凡在本发明的精神和原则之内所做的任何修改、等同替换和改进等，均应包含在本发明的保护范围之内。The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention. within the scope of protection.
Claims (8)
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100584555A CN100466645C (en) | 2004-08-16 | 2004-08-16 | A method for implementing different service processing according to different bearer network types |
| 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 | A method for implementing different service processing according to different bearer network types |
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 | A method for implementing different service processing according to different bearer network types |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN100466645C (en) |
| WO (1) | WO2006017985A1 (en) |
Cited By (14)
| 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 carrying 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 |
| WO2025020040A1 (en) * | 2023-07-24 | 2025-01-30 | 华为技术有限公司 | Method and apparatus for transmitting data |
Family Cites Families (3)
| 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 Distinguishing QoS of User Plane Transmission Network Layer in Radio Access Network |
| KR100537499B1 (en) * | 2002-07-26 | 2005-12-19 | 삼성전자주식회사 | Method of generating transmission control parameter and selective retranmission method according to the packet characteristics. |
-
2004
- 2004-08-16 CN CNB2004100584555A patent/CN100466645C/en not_active Expired - Lifetime
-
2005
- 2005-08-16 WO PCT/CN2005/001273 patent/WO2006017985A1/en active Application Filing
Cited By (18)
| 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 carrying 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 |
| WO2025020040A1 (en) * | 2023-07-24 | 2025-01-30 | 华为技术有限公司 | Method and apparatus for transmitting data |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2006017985A1 (en) | 2006-02-23 |
| CN100466645C (en) | 2009-03-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101385307B (en) | Optimization of pdp context usage | |
| US7826353B2 (en) | Method, system and network element for authorizing a data transmission | |
| EP1382214B1 (en) | Binding information for ip media flows | |
| CN101395483B (en) | Quality of Service (QoS) reservations triggered by the network | |
| CN100348010C (en) | IP multimedia communication conversation charging method, telecommunication system and network element | |
| CN101406086B (en) | Quality of service configuration for wireless communication | |
| CN101047950B (en) | Method for allocating default load in 3GPP evolution network | |
| CN1444824A (en) | Common charging identifier for communication networks | |
| US20130269002A1 (en) | Access Based Internet Protocol Multimedia Service Authorization | |
| US20040109459A1 (en) | Packet filter provisioning to a packet data access node | |
| CN1473443A (en) | Method and device for coordinating billing for services provided in a multimedia session | |
| CN1443414A (en) | Application of controlling policy | |
| CN1531811A (en) | Billing in Communication Networks | |
| CN101518120B (en) | Streaming quality optimization | |
| CN1691821A (en) | A method and system for implementing roaming charging | |
| CN1738303A (en) | A method for implementing different service processing according to different bearer network types | |
| CN101047874A (en) | Decision method for service information in mobile communication network | |
| CN1838610A (en) | Method for realizing user registration in internet protocol multimedia subsystem | |
| US7376081B2 (en) | Establishment of QoS by applications in cellular networks using service based policy control mechanisms | |
| CN1925450A (en) | Communication method preventing circumbendibus of media-flow | |
| WO2007045137A1 (en) | A method of qos authorization | |
| EP2078262B1 (en) | Systems and methods for signal reduction in wireless communication | |
| CN100466804C (en) | Method for confirming data transmission service quality in communication network | |
| WO2009036694A1 (en) | Method, device and system for establishing multiple pdn connections | |
| CN1753370A (en) | Method of implementing user's equipment reorientation in mobile pocket data business |
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 |