WO2002082764A2 - Interface between layers in a network interface device - Google Patents

Interface between layers in a network interface device Download PDF

Info

Publication number
WO2002082764A2
WO2002082764A2 PCT/US2002/010495 US0210495W WO02082764A2 WO 2002082764 A2 WO2002082764 A2 WO 2002082764A2 US 0210495 W US0210495 W US 0210495W WO 02082764 A2 WO02082764 A2 WO 02082764A2
Authority
WO
WIPO (PCT)
Prior art keywords
packet
layer
layer manager
pdl
protocol stack
Prior art date
Application number
PCT/US2002/010495
Other languages
French (fr)
Other versions
WO2002082764A3 (en
Inventor
Douglas La Vell Hale
Michael D. Wright
Merrill Kay Smith
Kyle Bryan Seegmiller
Jonathan Brett Wood
David O. Cox
Original Assignee
Rappore Technologies, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Rappore Technologies, Inc. filed Critical Rappore Technologies, Inc.
Priority to AU2002307094A priority Critical patent/AU2002307094A1/en
Priority to EP02763920A priority patent/EP1374535A2/en
Priority to JP2002580594A priority patent/JP2004531128A/en
Publication of WO2002082764A2 publication Critical patent/WO2002082764A2/en
Publication of WO2002082764A3 publication Critical patent/WO2002082764A3/en

Links

Classifications

    • 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/40—Network security protocols
    • 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

Definitions

  • the present invention relates to protocol stacks, and more particularly to packet flow
  • the stack 100 includes a Host Controller Interface (HCI) layer 106, a Logical Link Control and Adaptation Protocol (L2CAP) layer 108, a Telephony Control Protocol Specification (TCS) layer 110, a Service Discovery Protocol (SDP) layer
  • HCI Host Controller Interface
  • L2CAP Logical Link Control and Adaptation Protocol
  • TCS Telephony Control Protocol Specification
  • SDP Service Discovery Protocol
  • the HCI layer 106 provides a command interface which accepts communications
  • the L2CAP layer 108 supports higher level protocol
  • the TCS layer 110 provides call control and signaling of voice channels.
  • RFCOMM protocol layer 114 provides emulation of serial ports over the L2CAP layer 108.
  • the SDP layer 112 provides a means for applications to discover which services are
  • a Bluetooth device may act as an SDP client
  • Each service registers with the
  • the SDP server and information concerning each service is cataloged in service records.
  • a client may send a request to the SDP server to ask what services a remote device provides.
  • the SDP server responds with service records of the services provided by the remote device.
  • Part of each service record is a protocol descriptor list (PDL).
  • the PDL comprises -a list of layers of the protocol stack 100 through which to route a packet for the particular service.
  • each stack layer 106-114 requires intimate knowledge of the stack layer "above” and "below” it in the protocol stack 100.
  • each stack layer 106-114 must have a complete set of information on how to route the packet for this service.
  • each stack layer 106-114 requires point to point information from a client application, through each layer of the stack 100, to a remote device. How a connection to the layer above or below is created and how the packet routed to it varies from layer to layer. This leads to considerable complexity in the protocol stack 100.
  • the present invention provides a method and system for controlling packet flow through a protocol stack.
  • the method includes: receiving a packet by a layer manager, wherein the layer manager may interface with each layer of the protocol stack; determining a service associated with the packet by the layer manager; accessing a list of layers of the
  • the layer manager comprises a plurality of protocol
  • descriptor lists for supported services and uses these lists to route a packet to the appropriate
  • stack layers need not have knowledge of the other layers or
  • Figure 1 illustrates a standard Bluetooth protocol stack.
  • Figure 2 illustrates a preferred embodiment of a protocol stack which controls packet
  • Figure 3 is a flowchart illustrating a preferred embodiment of a method for
  • Figure 2 illustrates a preferred embodiment of a protocol stack which controls packet flow through the protocol stack in accordance with the present invention.
  • the protocol stack 200 in addition to the stack layers 106-114 described in conjunction with Fig. 1, comprises a
  • Layer Manager 202 which interfaces with each stack layer 106-114.
  • the Layer Manager 202 handles the packet flow to the stack layers 106-114.
  • the Layer Manager 202 allows each
  • stack layer 106-114 to process the packet without the need to have knowledge of which stack
  • Each stack layer receives its
  • the Layer Manager 202 then routes the packet to the
  • the Layer Manager 202 comprises a plurality of protocol descriptor lists (PDL) 216.
  • the SDP server notifies the Layer Manager 202 and provides a copy of the PDL for
  • the Layer Manager 202 contains a set of predefined PDL's for services
  • the list is the HCI layer
  • the order is the HCI layer 106, the L2CAP layer 108, and the RFCOMM
  • the Layer Manager 202 knows to which layers of the stack 200 the packet should be routed.
  • Figure 3 is a flowchart illustrating a preferred embodiment of a method for
  • the Layer Manager 202 receives a packet, via step 302. Next, the Layer Manager 202
  • this determination is based on the protocol/service multiplexer (PSM) field.
  • PSM protocol/service multiplexer
  • the PSM field references the PDL to be used for the packet.
  • the Layer Manager 202 accesses the PDL 216 for the service, via step 306.
  • the PDL comprises a list of layers of the protocol stack 200 for the service. Then, the Layer Manager 202 routes
  • the packet to a layer of the protocol stack 200 according to the list, via step 308.
  • the packet is received by the Layer Manager 202, via step 302.
  • the Layer Manager 202 determines that the RFCOMM
  • the Layer Manager 202 then accesses a
  • the RFCOMM service's PDL includes the
  • the Layer Manager 202 then routes the packet to the HCI layer 106, via step 308.
  • the HCI layer 106 processes the packet and returns it to the Layer Manager 202.
  • the Layer Manager 202 receives the packet from the HCI layer 106, via step 302. Again, through the packet's PSM field, it determines that the RFCOMM service is
  • the Layer Manager 202 knows that the packet was received from the HCI
  • the L2CAP layer 108 process the packet and returns it to the Layer Manager 202.
  • the Layer Manager 202 receives the packet from the L2CAP layer 108, via step 302.
  • the Layer Manager 202 knows
  • each stack layer 106-114 communicates with the Layer Manager 202
  • the stack layers 106-114 thus need not have knowledge of the other layers or of the proper routing of the packet. This makes the implementation of the
  • the system comprises a layer manager which interfaces with each stack layer.
  • the layer manager comprises a plurality of protocol descriptor lists for supported
  • the stack layers need not have knowledge of the other layers or of the proper routing of the

Abstract

The present invention provides a method and system for controlling packet flow through a protocol stack. The method includes: receiving a packet by a layer manager, wherein the layer manager may interface with each layer of the protocol stack; determining a service associated with the packet by the layer manager; accessing a list of layers of the protocol stack for the service by the layer manager; and routing the packet to a layer of the protocol stack according to the list. The layer manager comprises a plurality of protocol descriptor lists for supported services and uses these lists to route a packet to the appropriate stack layer. In this manner, the stack layers need not have knowledge of the other layers or of the proper routing of the packet. This makes the implementation of the layers in the protocol stack easier.

Description

CONTROLLING PACKET FLOW THROUGH A STACK USING SERVICE RECORDS
FIELD OF THE INVENTION
The present invention relates to protocol stacks, and more particularly to packet flow
control through the protocol stack.
BACKGROUND OF THE INVENTION
The Bluetooth™ networking protocol is well known in the art. Figure 1 illustrates a
standard Bluetooth protocol stack. The stack 100 includes a Host Controller Interface (HCI) layer 106, a Logical Link Control and Adaptation Protocol (L2CAP) layer 108, a Telephony Control Protocol Specification (TCS) layer 110, a Service Discovery Protocol (SDP) layer
112, and a RFCOMM protocol layer 114.
The HCI layer 106 provides a command interface which accepts communications
over the physical bus (not shown). The L2CAP layer 108 supports higher level protocol
multiplexing, packet segmentation and reassembly, and the conveying of quality of service
information.
The TCS layer 110 provides call control and signaling of voice channels. The
RFCOMM protocol layer 114 provides emulation of serial ports over the L2CAP layer 108.
The SDP layer 112 provides a means for applications to discover which services are
provided by or available through a device. A Bluetooth device may act as an SDP client
querying services, an SDP server providing services, or both. Each service registers with the
SDP server, and information concerning each service is cataloged in service records. Through the SDP layer 112, a client may send a request to the SDP server to ask what services a remote device provides. The SDP server responds with service records of the services provided by the remote device. Part of each service record is a protocol descriptor list (PDL). The PDL comprises -a list of layers of the protocol stack 100 through which to route a packet for the particular service.
However, to properly route packets through the stack 100, each stack layer 106-114 requires intimate knowledge of the stack layer "above" and "below" it in the protocol stack 100. Thus, when a packet is for a particular service provided either by a server or a client, each stack layer 106-114 must have a complete set of information on how to route the packet for this service. In effect, each stack layer 106-114 requires point to point information from a client application, through each layer of the stack 100, to a remote device. How a connection to the layer above or below is created and how the packet routed to it varies from layer to layer. This leads to considerable complexity in the protocol stack 100.
Accordingly, there exists a need for an improved method and system for controlling packet flow through a protocol stack. The present invention addresses such a need.
SUMMARY OF THE INVENTION
The present invention provides a method and system for controlling packet flow through a protocol stack. The method includes: receiving a packet by a layer manager, wherein the layer manager may interface with each layer of the protocol stack; determining a service associated with the packet by the layer manager; accessing a list of layers of the
protocol stack for the service by the layer manager; and routing the packet to a layer of the protocol stack according to the list. The layer manager comprises a plurality of protocol
descriptor lists for supported services and uses these lists to route a packet to the appropriate
stack layer. In this manner, the stack layers need not have knowledge of the other layers or
of the proper routing of the packet. This makes the implementation of the layers in the
protocol stack easier.
BRIEF DESCRIPTION OF THE FIGURES
Figure 1 illustrates a standard Bluetooth protocol stack.
Figure 2 illustrates a preferred embodiment of a protocol stack which controls packet
flow through the protocol stack in accordance with the present invention.
Figure 3 is a flowchart illustrating a preferred embodiment of a method for
controlling packet flow through the protocol stack in accordance with the present invention.
DETAILED DESCRIPTION The present invention provides an improved method and system for controlling
packet flow through a protocol stack. The following description is presented to enable one
of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment
will be readily apparent to those skilled in the art and the generic principles herein may be
applied to other embodiments. Thus, the present invention is not intended to be limited to
the embodiment shown but is to be accorded the widest scope consistent with the principles
and features described herein. To more particularly describe the features of the present invention, please refer to
Figures 2 and 3 in conjunction with the discussion below.
Figure 2 illustrates a preferred embodiment of a protocol stack which controls packet flow through the protocol stack in accordance with the present invention. The protocol stack 200, in addition to the stack layers 106-114 described in conjunction with Fig. 1, comprises a
Layer Manager 202 which interfaces with each stack layer 106-114. The Layer Manager 202 handles the packet flow to the stack layers 106-114. The Layer Manager 202 allows each
stack layer 106-114 to process the packet without the need to have knowledge of which stack
layers reside directly "above" and "below" them. Each stack layer concerns itself only with
whether the packet is to travel "up" or "down" the stack 200. Each stack layer receives its
packet from the Layer Manager 202, and when it is done processing the packet, it gives the packet back to the Layer Manager 202. The Layer Manager 202 then routes the packet to the
next stack layer.
The Layer Manager 202 comprises a plurality of protocol descriptor lists (PDL) 216.
In the preferred embodiment, when a service is registered with the SDP server, as described
above, the SDP server notifies the Layer Manager 202 and provides a copy of the PDL for
that service. Also, the Layer Manager 202 contains a set of predefined PDL's for services
provided by the clients. For example, for the RFCOMM service, the list is the HCI layer
106, the L2CAP layer 108, and the RFCOMM layer 114. If the packet is traveling up the
stack 200, then the order is the HCI layer 106, the L2CAP layer 108, and the RFCOMM
layer 114. If the packet is traveling down the stack 200, then the order is the RFCOMM
layer 114, the L2CAP layer 10.8, and then the HCI layer 106. By using the PDL for a particular service, the Layer Manager 202 knows to which layers of the stack 200 the packet should be routed.
Although the present invention is described with the Layer Manager receiving the PDL's in. the above manner, other methods of obtaining the PDL can be used without departing from the spirit and scope of the present invention.
Figure 3 is a flowchart illustrating a preferred embodiment of a method for
controlling packet flow through the protocol stack in accordance with the present invention.
'First, the Layer Manager 202 receives a packet, via step 302. Next, the Layer Manager 202
determines a service associated with the packet,, via step 304. In the preferred embodiment, this determination is based on the protocol/service multiplexer (PSM) field. The PSM is 16-
bit field occurring after the header in the packet which indicates the upper-level protocol the
packet originated from. The PSM field references the PDL to be used for the packet. The
Layer Manager 202 accesses the PDL 216 for the service, via step 306. The PDL comprises a list of layers of the protocol stack 200 for the service. Then, the Layer Manager 202 routes
the packet to a layer of the protocol stack 200 according to the list, via step 308.
For example, assume a packet is to be sent up through the stack 200 for the
RFCOMM service. The packet is received by the Layer Manager 202, via step 302.
Through the packet's PSM field, the Layer Manager 202 determines that the RFCOMM
service is associated with the packet, via step 304. The Layer Manager 202 then accesses a
PDL for the RFCOMM service, via step 306. The RFCOMM service's PDL includes the
HCI layer 106, the L2CAP layer 108, and the RFCOMM layer 114. The Layer Manager 202 then routes the packet to the HCI layer 106, via step 308. The HCI layer 106 processes the packet and returns it to the Layer Manager 202.
The Layer Manager 202 receives the packet from the HCI layer 106, via step 302. Again, through the packet's PSM field, it determines that the RFCOMM service is
associated with the packet, via step 304, and accesses the PDL for the RFCOMM service, via step 306. The Layer Manager 202 knows that the packet was received from the HCI
layer 106, and thus routes it to the next layer on the PDL, the L2CAP layer 108, via step 308.
The L2CAP layer 108 process the packet and returns it to the Layer Manager 202.
The Layer Manager 202 receives the packet from the L2CAP layer 108, via step 302.
It determines that the RFCOMM service is associated with the packet, via step 304, and •'
accesses the PDL for the RFCOMM service, via step 306. The Layer Manager 202 knows
that the packet was received from the L2CAP layer 108, and thus routes it to the next layer
on the PDL, the RFCOMM layer 112, via step 308.
In this manner, each stack layer 106-114 communicates with the Layer Manager 202
and not with each other. The stack layers 106-114 thus need not have knowledge of the other layers or of the proper routing of the packet. This makes the implementation of the
layers 106- 114 in the protocol stack 200 easier.
Although the present invention is described in the context of the Bluetooth protocol
stack, it may be applied to the packet routing through other protocol stacks without departing
from the spirit and scope of the present invention.
An improved method and system for controlling packet flow through a protocol stack
has been disclosed. The system comprises a layer manager which interfaces with each stack layer. The layer manager comprises a plurality of protocol descriptor lists for supported
services and uses these lists to route a packet to the appropriate stack layer. In this manner, the stack layers need not have knowledge of the other layers or of the proper routing of the
packet. This makes the implementation of the layers in the protocol stack easier. Although the present invention has been described in accordance with the
embodiments shown, one of ordinary skill in the art will readily recognize that there could
be variations to the embodiments and those variations would be within the spirit and scope
of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.

Claims

What is claimed is: 1. A method for controlling packet flow through a protocol stack, comprising the steps of:
(a) receiving a packet by a layer manager, wherein the layer manager may
interface with each layer of the protocol stack; (b) determining a service associated with the packet by the layer manager;
(c) accessing a list of layers of the protocol stack for the service by the layer
manager; and
(d) routing the packet to a layer of the protocol stack according to the list.
2. The method of claim 1 , wherein the determining step (b) comprises: (bl) examining a protocol/service multiplexer (PSM) field in the packet by the
layer manager; and
(b2) determining a protocol descriptor list (PDL) referenced by the PSM field by
the layer manager.
3. The method of claim 1 , wherein the accessing step (c) comprises:
(c) accessing a PDL for the service by the layer manager.
4. A method for controlling packet flow through a protocol stack, comprising
the steps of: (a) receiving a packet by a layer manager, wherein the layer manager may . interface with each layer of the protocol stack; (b) examining a PSM field in the packet by the layer manager; (c) • determining a PDL referenced by the PSM field by the layer manager, wherein the PDL comprises a list of layers of the protocol stack for the service; (d) accessing the PDL by the layer manager; and (e) routing the packet to a layer of the protocol stack according to the PDL.
5. A system, comprising: a plurality of stack layers; and a layer manager, wherein the layer manager may interface with each of the plurality of stack layers, wherein the layer manager comprises a list of stack layers for a service, wherein the layer manager may route a packet to one of the plurality of stack layers according to the list.
6. The system of claim 5, wherein the routing of the packet by the layer manager comprises the steps of: (a) receiving the packet; (b) determining the service associated with the packet;
(c) accessing the list of layers of the protocol stack for the service; and (d) routing the packet to one of the plurality of layers according to the list.
7. The system of claim 6, wherein the determining step (b) comprises: (bl) examining a PSM field in the packet; and
(b2) determining a PDL referenced by the PSM field.
8. The system of claim 6, wherein the accessing step (c) comprises: (cl) accessing a PDL for the service.
9. A system, comprising:
a plurality of stack layers; and
a layer manager, wherein the layer manager may interface with each of the plurality
of stack layers, wherein the layer manager comprises a PDL for a service, wherein the PDL comprises a list of stack layers for a service, wherein the layer manager routes a packet according to the PDL.
10. The medium of claim 9, wherein the routing of the packet by the layer
manager comprises the steps of:
(a) receiving the packet by the layer manager; (b) examining a PSM field in the packet;
(c) determining the PDL referenced by the PSM field;
(d) accessing the PDL; and
(e) routing the packet to one of the plurality of stack layers according to the PDL.
11. A computer readable medium with program instructions for controlling packet flow through a protocol stack, comprising the instructions for: (a) receiving a packet by a layer manager, wherein the layer manager may interface with each layer of the protocol stack;
(b) determining a service associated with the packet by the layer manager;
(c) accessing a list of layers of the protocol stack for the service by the layer manager; and
(d) routing the packet to a layer of the protocol stack according to the list.
12. The medium of claim 11 , wherein the determining instruction (b) comprises instructions for:
(b 1 ) examining a PSM field in the packet by the layer manager; and
(b2) determining a PDL referenced by the PSM field by the layer manager.
13. The medium of claim 11 , wherein the accessing instruction (c) comprises
instructions for:
(c) accessing a PDL for the service by the layer manager.
14. A computer readable medium with program instructions for controlling
packet flow through a protocol stack, comprising the instructions for:
(a) receiving a packet by a layer manager, wherein the layer manager may
interface with each layer of the protocol stack;
-u- (b) examining a value for a PSM field in the packet by the layer manager; (c) determining a PDL referenced by the PSM field by the layer manager, wherein the PDL comprises a list of layers of the protocol stack for the service;
(d) accessing the PDL by the layer manager; and
(e) routing the packet to a layer of the protocol stack according to the PDL.
PCT/US2002/010495 2001-04-03 2002-04-03 Interface between layers in a network interface device WO2002082764A2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU2002307094A AU2002307094A1 (en) 2001-04-03 2002-04-03 Interface between layers in a network interface device
EP02763920A EP1374535A2 (en) 2001-04-03 2002-04-03 Interface between layers in a network interface device
JP2002580594A JP2004531128A (en) 2001-04-03 2002-04-03 Controlling packet flow through the stack using service records

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/825,671 2001-04-03
US09/825,671 US6721274B2 (en) 2001-04-03 2001-04-03 Controlling packet flow through a stack using service records

Publications (2)

Publication Number Publication Date
WO2002082764A2 true WO2002082764A2 (en) 2002-10-17
WO2002082764A3 WO2002082764A3 (en) 2003-03-13

Family

ID=25244644

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2002/010495 WO2002082764A2 (en) 2001-04-03 2002-04-03 Interface between layers in a network interface device

Country Status (5)

Country Link
US (1) US6721274B2 (en)
EP (1) EP1374535A2 (en)
JP (1) JP2004531128A (en)
AU (1) AU2002307094A1 (en)
WO (1) WO2002082764A2 (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6952766B2 (en) * 2001-03-15 2005-10-04 International Business Machines Corporation Automated node restart in clustered computer system
US6792467B2 (en) * 2001-04-03 2004-09-14 Brycen Co., Ltd. Layer manager
US6918051B2 (en) * 2001-04-06 2005-07-12 International Business Machines Corporation Node shutdown in clustered computer system
US6973058B2 (en) * 2001-07-31 2005-12-06 Broadcom Corporation System and method for accessing a multi-line gateway using cordless telephony terminals
US6925582B2 (en) * 2001-08-01 2005-08-02 International Business Machines Corporation Forwarding of diagnostic messages in a group
US7440415B2 (en) * 2003-05-30 2008-10-21 Ixia Virtual network addresses
US7496688B2 (en) * 2004-01-30 2009-02-24 Ixia Label switched data unit content evaluation
US8121148B2 (en) * 2005-03-24 2012-02-21 Ixia Protocol stack using shared memory
US7414975B2 (en) * 2005-03-24 2008-08-19 Ixia Protocol stack
US8180856B2 (en) * 2006-09-14 2012-05-15 Ixia Testing a network
WO2009103340A1 (en) * 2008-02-21 2009-08-27 Telefonaktiebolaget L M Ericsson (Publ) Data retention and lawful intercept for ip services

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001017155A2 (en) * 1999-09-02 2001-03-08 Informix Software, Inc. Network packet aggregation

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5754788A (en) * 1995-12-28 1998-05-19 Attachmate Corporation Method and system for reconfiguring a communications stack
US5920703A (en) * 1997-02-19 1999-07-06 International Business Machines Corp. Systems and methods for managing the processing of relatively large data objects in a communications stack
EP1107522B1 (en) * 1999-12-06 2010-06-16 Telefonaktiebolaget LM Ericsson (publ) Intelligent piconet forming
JP4479040B2 (en) * 2000-03-07 2010-06-09 ソニー株式会社 Communication apparatus and communication method
US6452910B1 (en) * 2000-07-20 2002-09-17 Cadence Design Systems, Inc. Bridging apparatus for interconnecting a wireless PAN and a wireless LAN
US6954438B2 (en) * 2001-02-21 2005-10-11 3Com Corporation Wireless callback access control for a LAN network access point

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001017155A2 (en) * 1999-09-02 2001-03-08 Informix Software, Inc. Network packet aggregation

Also Published As

Publication number Publication date
AU2002307094A1 (en) 2002-10-21
US6721274B2 (en) 2004-04-13
WO2002082764A3 (en) 2003-03-13
EP1374535A2 (en) 2004-01-02
US20020141336A1 (en) 2002-10-03
JP2004531128A (en) 2004-10-07

Similar Documents

Publication Publication Date Title
JP4773946B2 (en) MONITOR CONTROL SYSTEM, MONITOR DEVICE, MONITOR CONTROL METHOD, AND MONITOR CONTROL PROGRAM
JP5653912B2 (en) Method and apparatus for multicast group management
JP2005529545A (en) Application of session service based on packet flow
JP5853378B2 (en) Communication switching system, communication switching method, and program
WO2012058988A1 (en) Method for message forwarding and device for deep packet inspection
US6721274B2 (en) Controlling packet flow through a stack using service records
AU2003205136B2 (en) Method and apparatus for dynamically assigning a network endpoint to a network region
WO2011072583A1 (en) User access method, system and access server, access device
US8149842B2 (en) Automated discovery of network devices supporting particular transport layer protocols
US20120300776A1 (en) Method for creating virtual link, communication network element, and ethernet network system
WO2009025252A1 (en) METHOD FOR PROCESSING OF EMERGENCY SERVICE OF IP-BASED IN WiMAX
US7237025B1 (en) System, device, and method for communicating user identification information over a communications network
US6792467B2 (en) Layer manager
TW591913B (en) Public access separation in a virtual networking environment
JP3823055B2 (en) Effective multilink flow handling
WO2011026355A1 (en) Method for a node accessing a home agent, home agent cluster system and service router
JPH11112503A (en) Network system and network equipment
KR101410510B1 (en) Method and apparatus for data transferring using Stream Control Transfer Protocol
US20020144150A1 (en) Providing access control via the layer manager
WO2022044226A1 (en) Communication system, communication method, communication device, and program
JP5088492B2 (en) Relay device
WO2010006520A1 (en) Method and device for two-layer intercommunication of data stream
US8001248B1 (en) System and method for providing quality of service to DSL internet connections
JP2002290451A (en) Communication bandwidth control method and device therefor
JP2002118588A (en) Communication service condition control method based on realm name or domain name

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

WWE Wipo information: entry into national phase

Ref document number: 2002763920

Country of ref document: EP

Ref document number: 2002580594

Country of ref document: JP

WWP Wipo information: published in national office

Ref document number: 2002763920

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWW Wipo information: withdrawn in national office

Ref document number: 2002763920

Country of ref document: EP