Patent US5663086A successfully refreshed from Google Patents.
Patent EP1037498A2 successfully refreshed from Google Patents.
EP1037498A2
Expired / Lapsed
EP
⏱️ 0.0 years remaining
Distributed control of service category request mapping
Assignee: Fujitsu Network Communications Inc
•
Filing: 2000-03-15
•
Granted: —
•
Expires: 2020-03-15
Abstract
Abstract Each switch along a call setup path in a network decides whether the call request should be upgraded from a non-flow-controlled service type to a flow-controlled service type. Each switch bases the decision on whether a boolean variable for the calling subscriber that appears in a management information base (MIB) is set to a value indicating that the subscriber is entitled to the upgrade. In addition, the upgrade is performed only if an interface on the route to the called party on which the call setup request is to be forwarded supports flow-controlled connections. When the call is to be upgraded, the switch replaces the service type indicator in the setup message with a value indicating a flow-controlled service type, and forwards the setup message toward the called subscriber. If the MIB variable is set to a value indicating that the upgrade is not to be performed, it is still possible for a subscriber to request flow-controlled service directly, by indicating this service type in the original call setup message. Each switch also makes a call downgrade decision. When a call setup message is received requesting flow-controlled service but destined for an interface that does not support flow-controlled operation, the switch replaces the service type indicator in the outgoing setup message with a value indicating a non-flow-controlled service type.
Inventors
- 👤 Thomas A. Manning
- 👤 David N. Peck
- 👤 Robert Constantin
- 👤 David E. Hammond
- 👤 Andrew Michal
- 👤 Stephen R. Veit
Bibliographic Details
Application Number
—
Jurisdiction
EP
Data Source
google_patents
Last Synchronized
2026-10-30 21:11
CPC Classifications
H; H04; H04L; H04L12/00; H04L12/54; H04L12/56; H04L12/5601; H04L12/5602; H04L49/00; H04L49/20; H04L49/205; H04Q; H04Q11/00; H04Q11/04; H04Q11/0428; H04Q11/0478; H04L2012/5629; H04L2012/5631; H04L2012/5632; H04L2012/5634; H04L2012/5635; H04L2012/5636
Claims Analysis
Total Claims: 24
Claim 1
Independent Claim
190 words
A method of conditionally mapping a network service from one type to
another type, comprising the steps of: if upon receiving an incoming call management message from a calling
subscriber requesting a connection to a called party, the following conditions
are satisfied : (i) a network service type signaled in the call management
message is a non-flow-controlled network service type, (ii) mapping of the
network service for the calling subscriber is enabled, and (iii) a flow-controlled
network service type is supported on an interface on a route to the called party,
then forwarding a first type of outgoing call management message on the
interface on the route to the called party, the first type of outgoing call
management message signaling the flow-controlled network service type; and if upon receiving the incoming call management message from the
calling subscriber, mapping of the network service for the calling subscriber is
not enabled, then forwarding a second type of outgoing call management
message on the interface on the route to the called party, the second type of
outgoing call management message signaling the same service type signaled
in the incoming call management message.
Claim 2
Dependent Claim
87 words
A method according to claim 1, further comprising the step of: if upon receiving the incoming call management message from the
calling subscriber, the incoming call management messages signals the flow-controlled
network service type and the flow-controlled network service type is
not available on the interface on the route to the called party, then forwarding a
third type of outgoing call management message on the interface on the route
to the called party, the third type of outgoing call management message
signaling a non-flow-controlled network service type.
Claim 3
Dependent Claim
44 words
A method according to claim 2, wherein the interface on the route to the
called party is capable of providing flow-controlled service when enabled, and
wherein the flow-controlled network service type on the interface on the route to
the called party has been disabled.
Claim 4
Dependent Claim
23 words
A method according to claim 2, wherein the interface on the route to the
called party is not capable of providing flow-controlled service.
Claim 5
Independent Claim
22 words
A method according to any of claims 1 to 4, wherein the flow-controlled
service type is flow-controlled available bit rate (ABR) service.
Claim 6
Independent Claim
21 words
A method according to any of claims 1 to 5, wherein the non-flow-controlled
service type is unspecified bit rate (UBR) service.
Claim 7
Independent Claim
27 words
A method according to any of claims 1 to 6, wherein the interface on
the route to the called party is a Public Network-to-Network Interface (PNNI)
interface.
Claim 8
Independent Claim
31 words
A method according to any of claims 1 to 7, wherein the service type for
each call management message is signaled by a corresponding value in a field
of the message.
Claim 9
Independent Claim
34 words
A method according to any of claims 1 to 8, wherein mapping of the
network service for the calling subscriber is indicated to be enabled by setting a
corresponding flag in a user database.
Claim 10
Dependent Claim
16 words
A method according to claim 9, wherein the user database is a network
management information base.
Claim 11
Independent Claim
25 words
A method according to any of claims 1 to 10, wherein the incoming call
management message from the calling subscriber is a call set-up message.
Claim 12
Independent Claim
25 words
A method according to any of claims 1 to 10, wherein the incoming call
management message from the calling subscriber is an add party message.
Claim 13
Dependent Claim
239 words
A network switch, comprising : a first port processor operative to receive an incoming call management
message from a calling subscriber, the incoming call management message
requesting a connection to a called party; a central processor coupled to the first port processor and the second
port processor, the central processor being operative to : receive the incoming call management message from the first port
processor; if upon receiving the incoming call management message, the following
conditions are satisfied : (i) a network service type signaled in the call
management message is a non-flow-controlled network service type, (ii)
mapping of the network service for the calling subscriber is enabled, and (iii) a
flow-controlled network service type is supported on the interface on the route
toward the called party, then to forward a first type of outgoing call management
message to the second port processor for forwarding on the interface on the
route to the called party, the first type of outgoing call management message
signaling the flow-controlled network service type ; and if upon receiving the incoming call management message, mapping of
the network service for the calling subscriber is not enabled, then to forward a
second type of outgoing call management message to the second port
processor for forwarding on the interface on the route to the called party, the
second type of outgoing call management message signaling the same service
type signaled in the incoming call management message.
Claim 14
Dependent Claim
86 words
A network switch according to claim 13, wherein the central processor
is further operative, if the incoming call management message signals the flow-controlled
network service type and the flow-controlled network service type is
not available on the interface on the route to the called party, to forward a third
type of outgoing call management message to the second port processor for
forwarding on the interface on the route to the called party, the third type of
outgoing call management message signaling a non-flow-controlled network
service type.
Claim 15
Dependent Claim
48 words
A network switch according to claim 14, wherein the interface on the
route to the called party is capable of providing flow-controlled service when
enabled, and wherein the availability of the flow-controlled network service type
on the interface on the route to the called party has been disabled.
Claim 16
Dependent Claim
24 words
A network switch according to claim 14, wherein the interface on the
route to the called party is not capable of providing flow-controlled service.
Claim 17
Dependent Claim
23 words
A network switch according to any of claims 13 to 16, wherein the flow-controlled
service type is flow-controlled available bit rate (ABR) service.
Claim 18
Dependent Claim
22 words
A network switch according to any of claims 13 to 17, wherein the non-flow-controlled
service type is unspecified bit rate (UBR) service.
Claim 19
Dependent Claim
27 words
A network switch according to any of claims 13 to 18, wherein the
interface on the route to the called party is a Public Network-to-Network
Interface (PNNI).
Claim 20
Dependent Claim
32 words
A network switch according to any of claims 13 to 19, wherein the
service type for each call management message is signaled by a corresponding
value in a field of the message.
Claim 21
Dependent Claim
35 words
A network switch according to any of claims 13 to 20, wherein mapping
of the network service for the calling subscriber is indicated to be enabled by
setting a corresponding flag in a user database.
Claim 22
Dependent Claim
17 words
A network switch according to claim 21, wherein the user database is a
network management information base.
Claim 23
Dependent Claim
26 words
A network switch according to any of claims 13 to 22, wherein the
incoming call management message from the calling subscriber is a call set-up
message.
Claim 24
Dependent Claim
26 words
A network switch according to any of claims 13 to 22, wherein the
incoming call management message from the calling subscriber is an add party
message.
References Cited (Backward Citations)
No citation records indexed.
USPTO Annuity & Maintenance Windows
Maintenance schedule is calculated for granted US utility patents.