WO1997038513A1 - Controleur de communications et procede de controle des communications - Google Patents
Controleur de communications et procede de controle des communications Download PDFInfo
- Publication number
- WO1997038513A1 WO1997038513A1 PCT/JP1997/001178 JP9701178W WO9738513A1 WO 1997038513 A1 WO1997038513 A1 WO 1997038513A1 JP 9701178 W JP9701178 W JP 9701178W WO 9738513 A1 WO9738513 A1 WO 9738513A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- terminal
- asel
- transmission standard
- value
- Prior art date
Links
Classifications
-
- 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/40058—Isochronous transmission
-
- 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
- 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]
-
- 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/40097—Interconnection with other 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/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/4608—LAN interconnection over ATM networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
- H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
- H04Q11/0478—Provisions for broadband connections
-
- 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
-
- 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
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5614—User Network Interface
-
- 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
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5629—Admission control
- H04L2012/563—Signalling, e.g. protocols, reference model
-
- 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
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5638—Services, e.g. multimedia, GOS, QOS
Definitions
- TECHNICAL FIELD The present invention relates to a communication control device and method, and for example, relates to a communication control device and method suitable for use in a video-on-demand system or the like that provides multimedia data.
- Background Art Figure 1 shows an ATM (Asynchronous Transfer Mode) network on the knockbone side and an IEEE (Institute of Electrical and Electronic Engineers, Inc.) 13 9 4 serial bus (IEEE 1) on the front end side.
- ATM Asynchronous Transfer Mode
- IEEE Institute of Electrical and Electronic Engineers, Inc. 13 9 4 serial bus
- VOD Video On Demand
- the ATM terminal 1 is a server that stores video data and the like, is connected to the ATM network 2 through a UNI (User-Network Interface), and transmits the video data to the terminals 13 1 to 4 1 to 4 ( Below, 1 3 9 4 terminal 4 1 1 to
- the ATM / 1 394 repeater 3 is connected to the ATM network 2 via the UNI, receives video data transmitted from the ATM terminal 1 via the ATM network 2, and receives the IEEE 1394 serial data.
- 1 3 9 4 Terminal 4 is provided via the bus.
- 1 394 Terminal 4 receives the video data provided via the IEEE 1394 serial bus from ATM / 1 394 repeater 3 and displays it on a display device such as a CRT or LCD. It has been done.
- IP over ATM (hereinafter abbreviated as IP / ATM) is used as a standard protocol.
- IP / ATM IP over ATM
- the protocol blocks of the U (User) brain and the C (Control) brain of the end to end are laid out as shown in FIGS. 2 and 3, respectively. That is, as shown in FIG. 2, the U-plane protocol block of the ATM network 2 includes a PHY (physical) layer and an ATM layer. Therefore, the U-plane protocol block of the ATM terminal 1 has a PHY layer and an ATM layer corresponding to the ATM network 2, an IP / ATM layer for exchanging IP packets, and Has an IP layer.
- the unit of data (user information from 1 byte to 64 kilobytes) of the higher-level application (IP / ATM layer) and the cell are unified. It has an AAL (ATM Adaptation Layer) 5, which performs coordination with the 48-byte user information handled.
- AAL ATM Adaptation Layer
- the U-brain protocol of ATM / 1 394 repeater 3 has the same configuration as ATM terminal 1 on ATM network 2 side. That is, it is composed of a PHY layer, an ATM layer, an AAL5 layer, an IP / ATM layer, and an IP layer.
- the 1394 terminal 4 side It has the same configuration as the tack, and consists of a 1394PHY layer, a 1394UNK layer, and an IP layer. There is no one corresponding to the IP / ATM layer on the ATM network 2 side (there is described as null in Fig. 2) (However, it is possible to arrange a protocol such as IP / 1394).
- the C-plane of the ATM terminal 1 pro Tokorusu tack, PHY Layer, ATM layer, AAL5 layer, SSCF (Service Specific Coordination Function) (ITU (International Telecommunication Union) -TQ. 2 130) + SSC0P (Service Specific Connection Oriented Protocol) (ITU-TQ. 21 10) layer , And Q.2931 (ITU-TQ.2931) layers.
- the configuration of the C-plane protocol of the ATM network 2 is the same as that of the ATM terminal 1.
- the C-brain protocol stack of the ATM / 1394 repeater 3 has the same configuration as the case where the ATM network 2 side is the ATM terminal 1 and the ATM network 2.
- the 1394 terminal 4 has the same configuration as the protocol stack of the 1394 terminal 4, and includes a 1394 PHY layer, a 1394 LINK layer, and an original signaling protocol (Original Signaling Protocol 1) layer.
- the C-brain protocol stack of the 1394 terminal 4 includes a 1394 PHY layer, a 1394 LIM layer, and an Original Signaling Protocol layer.
- VPC Virtual Pass Connection
- VCC Virtual Channel Connection
- Handing may be performed using an IP header.
- the ATM / 1 394 repeater 3 needs a routing function using IP.
- the present invention has been made in view of such a situation, and reduces the burden on a central unit when exchanging data of different transmission standards between terminals via a repeater. It is intended to reduce the number of system development steps.
- a communication control device includes a first conversion unit that converts a data of a second transmission standard received via a repeater into a data of a first transmission standard. Means for converting predetermined data of the first transmission standard into data of the second transmission standard.
- the communication control method comprises: converting data of a first transmission standard received via a repeater into data of a second transmission standard; and To data of a first transmission standard.
- a communication control device includes: first conversion means for converting data of a first transmission standard transmitted from a first terminal into data of a second transmission standard; and a second terminal. Second conversion means for converting the data of the second transmission standard transmitted from the first terminal into the data of the first transmission standard, and the same signaling protocol as that of the first terminal. And a processing means for processing the data of the first transmission standard transmitted from the first terminal and the data of the first transmission standard converted by the second conversion means.
- the communication control method includes: a first conversion step of converting data of a first transmission standard transmitted from a first terminal into data of a second transmission standard; and transmitting the data from the second terminal.
- the repeater includes a first conversion unit that converts the data of the first transmission standard transmitted from the first terminal into data of the second transmission standard. And the second message transmitted from the second terminal.
- a second conversion means for converting the data of the transmission standard into the data of the first transmission standard, wherein the second terminal transmits the data of the second transmission standard transmitted from the repeater to the first transmission standard.
- the repeater converts the data of the first transmission standard transmitted from the first terminal into data of the second transmission standard, and transmits the data to the second terminal. Transmitting the data of the second transmission standard transmitted from the second terminal to data of the first transmission standard and transmitting the data to the first terminal.
- the second terminal comprises: a step of converting data of the second transmission standard transmitted via the repeater into data of the first transmission standard; and a step of converting a predetermined data of the first transmission standard. And a step of converting the data into data of the second transmission standard and transmitting the data to the repeater.
- the communication control device sets a communication path for transferring data of a transmission standard exchanged between a terminal and another terminal between a repeater or a terminal using a predetermined control command in advance. It has setting means.
- the communication control method is a step of setting a communication path for transferring data of a transmission standard exchanged between a terminal and another terminal between a repeater or a terminal using a predetermined control command in advance. Is provided.
- the first conversion means converts data of the first transmission standard received via the repeater into data of the second transmission standard
- the second conversion means The predetermined data of the second transmission standard Evening is converted to data of the first transmission standard.
- the data of the first transmission standard received via the repeater is converted to the data of the second transmission standard, and the predetermined data of the second transmission standard is converted. Is converted to the data of the first transmission standard.
- the first transmission standard data transmitted from the first terminal with the same signaling protocol as the first terminal has. And c) the data of the first transmission standard converted by the second conversion means is processed.c.
- the first conversion means is connected to the first terminal by the repeater.
- the transmitted data of the first transmission standard is converted into data of the second transmission standard
- the second converting means converts the data of the second transmission standard transmitted from the second terminal. Convert to the data of the first transmission standard.
- the third conversion means converts the data of the second transmission standard transmitted from the repeater into data of the first transmission standard
- the fourth conversion means And converting predetermined data of the first transmission standard into data of the second transmission standard.
- the repeater converts the data of the first transmission standard transmitted from the first terminal into the data of the second transmission standard, and The data is transmitted to the second terminal, and the data of the second transmission standard transmitted from the second terminal is converted into data of the first transmission standard and transmitted to the second terminal.
- the second terminal converts the data of the second transmission standard transmitted via the repeater into the data of the first transmission standard, and converts the data of the first transmission standard into a predetermined data. Evening is converted to data of the second transmission standard and transmitted to the repeater. 7/01178
- a communication path for transferring data of a transmission standard exchanged between a terminal and another terminal between the repeater and the terminal is provided in advance by a predetermined control command. Is set using.
- the communication control device includes a second transmission standard (for example, the IEEE 1394 standard) received through a repeater (for example, the ATM / 1 394 repeater 3 in FIG. 4).
- the first conversion means for example, ASEL32 in FIG. 54 for converting the data into the data of the first transmission standard (for example, the ATM standard)
- Second conversion means for example, ASEL32 in FIG. 54 for converting the data into data of the second transmission standard.
- the communication control device includes processing means (for example, layer 36 in FIG. 55) for processing data of the first transmission standard using the same signaling protocol as the signaling protocol of the terminal. Prepare.
- the communication control device transmits data of a first transmission standard (for example, ATM standard) transmitted from a first terminal (for example, ATM terminal 1 in FIG. 4) to a second transmission standard.
- a first transmission standard for example, ATM standard
- a second transmission standard for example, ASEL 33 in FIG. 55
- a second conversion means for example, ASEL 33 in FIG. 55
- Terminal has The same signaling protocol as the
- Processing means for processing the data of the first transmission standard transmitted from the first terminal and the data of the first transmission standard converted by the second conversion means (for example, layer 35 in FIG. 55) Prepare.
- the communication control device is applicable to a case where a plurality of second terminals (for example, 1394 terminals 22-1 and 23-1 in FIG. 4) are connected on transmission paths of different second transmission standards. Further, there is further provided a relay means (for example, ASEL31 in FIG. 54) for relaying the data of the second transmission standard in the U-brain exchanged between the plurality of second terminals.
- a relay means for example, ASEL31 in FIG. 54
- a plurality of second terminals (for example, 1394 terminals 22-1 and 22-2 in FIG. 4) are connected on a transmission path of the same second transmission standard.
- a relay means for example, ASEL31 in FIG. 54 for substantially slew-through and relaying the data of the second transmission standard in the U-brain exchanged between a plurality of second terminals is further provided.
- the repeater transmits the first terminal (for example, the ATM terminal 1 in FIG. 4) transmitted from the first terminal.
- a first conversion means for example, ASEL31 in FIG. 54 for converting data of a transmission standard (for example, ATM standard) into data of a second transmission standard (for example, IEEE1394 standard);
- Second conversion means for example, FIG. 4 for converting the data of the second transmission standard transmitted from the second terminal (for example, the terminal 394 of FIG. 4) into the data of the first transmission standard.
- the second terminal converts the data of the second transmission standard transmitted from the repeater into the data of the first transmission standard (ASEL 31).
- ASEL32 in Figure 54 And a fourth conversion means for converting a predetermined data of the first transmission standard into a data of the second transmission standard.
- the communication control device includes a terminal between a repeater (for example, the ATM / 13944 repeater 3 in FIG. 4) and a terminal (for example, the 1394 terminal 4-1 in FIG. 4). (For example, 1394 terminal 4-1 in Fig. 4) and a communication path for transferring data of a transmission standard exchanged between other terminals (for example, 1394 terminal 4-1 in Fig. 4) There is provided setting means for setting in advance using a predetermined control command.
- FIG. 1 is a diagram showing a configuration example of a conventional V0D system.
- Figure 2 is a diagram showing a possible U-plane protocol sequence when using IP / ATM.
- FIG. 3 is a diagram showing a possible protocol lock of the C plane when the IP / ATM is used.
- FIG. 4 is a diagram showing a configuration example of a V0D system to which the communication control device of the present invention is applied.
- FIG. 5 is a diagram illustrating the relationship between ASEL-UNI.
- FIG. 6 is a diagram showing a layer relation diagram of the ASEL.
- FIG. 7 is a diagram showing an insertion field of the ASEL-PDU.
- FIG. 8 is a diagram showing a format and coding example common to all AAL types of ASEL-PDU.
- FIG. 9 is a diagram showing a format and a coding example of ASEL-PDU (AAL 5 Type).
- FIG. 10 is a diagram showing a format and a coding example of ASEL-PDU (AAL O Type).
- FIG. 11 is a diagram for explaining the relationship between ASEL-CMI and ASEL-UNI.
- FIG. 12 is a diagram for explaining the state transition of the ASEL-CME in the user side.
- FIG. 13 is a diagram illustrating the state transition of ASEL-CME on the Network side.
- FIG. 14 is a diagram showing a format of a field common to ASEL-CMP messages.
- FIG. 15 is a diagram showing the format of the WakeUp message.
- FIG. 16 is a diagram showing the format of the ActReq message.
- FIG. 17 is a diagram showing the format of the ActAck message.
- FIG. 18 is a diagram showing the format of the IsoReq message.
- FIG. 19 is a diagram showing the format of the IsoRply message.
- FIG. 20 is a diagram showing a format of the DestIDReq message.
- FIG. 21 is a diagram showing a format of the Dest lDRply message.
- FIG. 22 is a diagram illustrating SDL.
- FIG. 23 is a flowchart illustrating a process of state transition from the reset state in FIG.
- FIG. 24 is a flowchart illustrating the process of transition from the ActPending state in FIG. 12.
- FIG. 25 is a flowchart illustrating the process of transition from the Act state in FIG. 12.
- FIG. 26 is a flow chart illustrating a process of a state transition from the Act state in FIG. 12.
- FIG. 27 is a flowchart illustrating a state transition process from an arbitrary state in FIG.
- FIG. 28 is a flowchart illustrating a process of state transition from an arbitrary state in FIG.
- FIG. 29 is a flowchart illustrating a process of state transition from an arbitrary state in FIG. 13.
- FIG. 30 is a flowchart for explaining a process of a state transition from the reset state in FIG.
- FIG. 31 is a flowchart illustrating a process of transitioning from the ActPending state in FIG. 13.
- FIG. 32 is a flowchart for explaining the processing of the state transition from the state of Act in FIG. 13.
- FIG. 33 is a flow chart for explaining a process of a state transition from the Act state in FIG. 13.
- FIG. 34 is a flowchart for explaining processing of state transition from an arbitrary state in FIG.
- FIG. 35 is a flowchart illustrating a process of state transition from an arbitrary state in FIG. 13.
- FIG. 36 is a flowchart for explaining data transfer processing from the state of Act.
- FIG. 37 is a flowchart for explaining the processing when transferring data.
- Fig. 38 is a flow chart explaining the process when transferring data. It is.
- FIG. 39 is a flowchart for explaining the processing when transferring data.
- FIG. 40 is a flowchart illustrating the more detailed process of step S287 in FIG.
- FIG. 41 is a flowchart for explaining the more detailed processing of step S288 in FIG.
- FIG. 42 is a flowchart for explaining the more detailed process of step S294 of FIG.
- FIG. 43 is a flowchart for explaining the more detailed process of step S300 in FIG.
- FIG. 44 is a flowchart illustrating a process when data is received.
- FIG. 45 is a flowchart for explaining a process when receiving a night.
- FIG. 46 is a flowchart illustrating a process when data is received.
- FIG. 47 is a flowchart for explaining the more detailed processing of step S452 in FIG.
- FIG. 48 is a flowchart for explaining the more detailed processing of step S489 of FIG.
- FIG. 49 is a flowchart for explaining the more detailed process of step S479 of FIG.
- FIG. 50 is a flowchart for explaining the more detailed processing of step S459 in FIG.
- FIG. 51 is a flowchart illustrating the more detailed process of step S470 in FIG.
- FIG. 52 is a flowchart for explaining the more detailed processing of step S483 of FIG.
- FIG. 53 is a flowchart for explaining the more detailed process of step S 4 62 of FIG. 45.
- Figure 54 is a diagram showing the U-plane protocol stack when using IP / ATM when ASEL is adopted.
- FIG. 55 is a diagram showing a block diagram of the C-plane port when using IP / ATM when ASEL is adopted.
- BEST MODE FOR CARRYING OUT THE INVENTION FIG. 4 shows a configuration example of a V0D system to which the present invention is applied.
- an ATM (Asynchronous Transfer Mode) network is installed on the Nokbone side, and an IEEE 1394 serial path (IEEE 1394 Standards Draft 8.0 v2) is installed on the Frontend side. You are using ATM (Asynchronous Transfer Mode) network.
- IEEE 1394 serial path IEEE 1394 Standards Draft 8.0 v2
- the ATM terminal 1 is a server that stores video data, is connected to the ATM network 2 via a UNI (User-Network Interface), and provides video data and the like.
- the ATM / 1 394 repeater 3 is connected to the ATM network 2 via the UNI, receives video data from the ATM terminal 1 via the ATM network 2, and connects to the IEEE 1394 serial bus.
- 1 3 9 4 terminal 4 1 1 to 4-7 (hereinafter, 1 3 9 4 terminal 4 1 to 4-7 When it is not necessary to distinguish individually, 1 3 9 4 terminal 4 is appropriately described. To provide).
- 1 3 9 4 Terminal 4 is ATM / 1 3 9 4 Video data provided from the repeater 3 via the IEEE1394 serial bus is received and displayed on a display device such as a CRT or LCD.
- the ATM / 1 3 9 4 repeater 2 1 is connected to the ATM network 2 via the UNI, receives video data from the ATM terminal 1 via the ATM network 2, and receives the IEEE 1 3 9 4 1 3 9 4 terminals 2 2-1 to 2 2-4 (hereinafter, 1 3 9 4 terminals 2 2-1 to 2 2-4 via serial bus) 3 9 4 terminal 22).
- the 1394 terminal 22 receives the video data provided via the IEEE1394 serial path from the ATM / 1394 repeater 21 and displays it on a display device such as a CRT or LCD. Has been made.
- the ATM / 1 394 repeater 21 also has an IEEE 1394 serial path (serial bus different from the IEEE 1394 serial bus to which the 1394 terminal 22 is connected). Via 1 3 9 4 terminal 2 3— 1 through
- connection method of the IEEE 1394 serial path either “daisy chain” or “node branching” can be used.
- daisy chain method up to 16 13 4 terminals (nodes (1
- the limitation of the number of connected terminals in the daisy chain method is due to the transmission delay between the terminals at both ends.
- no Of the 16 bits for the code ID 10 bits specify the bus ID number, and 6 bits specify the physical ID number.
- physical ID numbers 0 to 62 can be assigned to 1394 terminals, and the maximum number of connections is 63. Since the last physical ID number, 63, is used for broadcast, it cannot be assigned to a physical ID number for each terminal.
- All nodes receive a packet sent to their own node ID number and a packet sent to physical ID number 63, which is the same or broadcast as the node ID number.
- the 1394 terminal can connect and disconnect the IEEE 1394 standard cable while the power is on, that is, while the device is operating, and nodes are added or deleted. At this time, or when the power is turned on, the 1394 network is automatically reconfigured, and the node ID number is reset for each node.
- the link layer (IEEE 1394 standard) A method to implement a layer that simulates AAL (ATM Adaptation Layer) / ATM layer (ITU-TI.363 / ITU-TI.366.1) on 1 394 LINK) .
- AAL ATM Adaptation Layer
- ATM layer ITU-TI.363 / ITU-TI.366.1
- ASEL ATM over IEEE1394 Serial bus Emulsion Layer
- the ASEL hides the IEEE 1394 serial bus from software at the layer above the ASEL of the device and emulates the AAL / ATM layer. For this reason, devices equipped with ASEL can multiplex and demultiplex VPC (Virtual Pass Connection) / VCC (Virtual Channel Connection) via their own IEEE 1394 serial bus interface. Corresponding network access protocol software and various application software can be used as they are.
- Figure 5 shows that the ASEL entities at the ATM / 1394 repeater 3 and the 1394 terminals 4-1 through 4-3 are interconnected one-to-one via each ASEL-UNI.
- FIG. As shown in the figure, multiple ASEL-UNIs can physically exist on one 1394 serial bus cable.
- the ASEL entity is divided into the operations of Network side (AT / 1 394 repeater 3 side) and User side (1 394 terminal 4-1 to 4-13 side) at ASE UNI.
- Each ASEL-UN on the Network side is assigned to each ASEL-UNI and the 1394 Node Unique ID, which is held individually by the 1394 terminals 4-1 to 4-13 on the User side. It is identified by associating the ASEL-UNI ID.
- FIG. 6 is a layer relation diagram showing the position of the ASEL.
- ASEL provides primitives similar to those provided by various AALs as primitives with the upper layer. That is, AAL UNITDATA. Req (request) from the upper layer And supply AALJJNITMTA.ind (indication). It also receives AAL_U_ABORT.req and supplies AAL_U_ABORT.ind.
- AAL-P-ABORT, ind is supplied to the upper layer.
- the software of the upper layer of the ASE L for example, the IP layer and IP / ATM layer of FIG. 54 described later, and the Q.2931 layer of FIG. 55, SSCF + SSCOP
- the lower layer for example, FIG. 54 and the 1394 LINK layer and the 1394 PHY layer in Fig. 55
- FIG. 54 and the 1394 LINK layer and the 1394 PHY layer in Fig. 55 can behave in the same way as when AAL is used.
- AALJJNITDATA.req and AAL_UNITDATA.ind are primitives for performing overnight transfer with the upper layer.
- VPI Virtual Pass Identifier
- VCI Virtual Channel Identifier
- AAL5 parameters This parameter group is included when the AAL type of ASEL-VCC is AAL5.
- Interface Data When AAL 5 is operating in message mode, this parameter is equivalent to a complete AA Service Data Unit (SDU). When operating in streaming mode, this parameter is equivalent to some AA or SDU.
- SDU Service Data Unit
- This parameter is not used in message mode. In streaming mode, this parameter indicates that the incoming and outgoing interface data contains the last part of the entire AA or SDU. Or not.
- Loss Priority This parameter indicates the loss priority of the AA / SDU. This parameter is mapped to an ASEL-PDU (Protocol Data Unit) header described later.
- ASEL-PDU Protocol Data Unit
- This sniffer indicates if the AAL-SDU has gone through a congestion state. This parameter is mapped to the ASEL-PDU header described later.
- AAL User-User Information (AAL User-User Information): This parameter is transferred transparently by ASEL between peer ASEL upper layer entities. This parameter is mapped to the ASEL-PDU header described later.
- Error Status This parameter indicates that the interface data may contain transmission errors. This parameter is used only when the error data distribution function is used. This parameter is not included in the AALJIN ITDATA.req primitive.
- AAL 0 parameters This parameter is included when the AAL type of ASEL-VCC is AAL 0.
- Interface Data This parameter always corresponds to a complete AAL-SDI.
- Loss Priority This parameter indicates the loss priority of AA / SDU. This parameter is mapped to the ASEL-PDU header described later.
- Congestion Indication This parameter indicates whether the AAL-SDU has gone through a congestion state. This param overnight Is mapped to the ASEL-PDU header described later.
- Error Status This parameter indicates that an error has occurred and may have transmission errors. This parameter is used only when the error data distribution function is used. This parameter is not included in the AAL_UNITDATA.req primitive.
- AAL_U_AB0RT.req, AAL_U_AB0RT.ind and AAL_P_AB0RT.ind primitives are primitives for performing an abort service with an upper layer. These primitives are used only when the corresponding ASEL-VCC is in AAL3 / 4 or AAL5 streaming mode.
- the AALJLABORT.req primitive is used by the upper layers of ASEL to invoke an application service.
- the AAL_U_AB0RT.ind primitive indicates that the AAL-SDU partially distributed should be discarded by the upper layer of ASEL according to the instruction from the upper layer of the peer (the other ASEL).
- the AAL_P_AB0RT.ind primitive is used to indicate that the upper layer of ASEL should discard the partially delivered AA SDU due to an error occurring in the lower layer of ASEL or ASE L. Used by ASEL entities.
- AAL_U_AB0RT.req, AAL_U_AB0RT.ind and AAL_P_AB0RT.ind primitives contain the following information.
- ASEL uses the primitive provided by the IEEE 1394 link layer as it is as a primitive with the lower layer. That is, Supply LK_IS0_C0NT.req to the lower layer and receive LK_CYCLE. Ind. It also supplies LK_IS0.req to the lower layer and receives LK_IS0.ind. It also supplies LK_DATA.req to the lower layer, receives LK-DATA.conf and LK_DATA. Ind, and supplies LK_DATA. Resp to the lower layer. As a result, the link layer does not need to be aware of the upper layer.
- the LK_IS0-CONT.req primitive is used when the ASEL entity requests a list of received isochronous channel numbers that are allowed to accept.
- the LK_IS0_C0NT.req primitive contains the following information.
- the LK_CYCLE.ind primitive is used by the 1394 Link layer to notify the ASEL entity that a Cycle sync event has occurred.
- the LK—CYCLE, ind primitive contains the following information:
- LK_IS0.req and LK ISO.ind primitives are ASEL and 139 4 Link Used to transfer CBR (Constant Bit Rate) data to and from the layer.
- the ASEL entity uses the LK-ISO.req primitive to request the transmission of one Isochronous packet from the 1394Link layer.
- the 1394Link layer uses the LK-ISO.ind primitive to notify the ASEL entity that one Isochronous packet has been received.
- the LK_DATA.req primitive is used to transmit UBR (Unassigned Bit Rate) or ABR (Available Bit Rate) data.
- the ASEL entity uses this primitive to request the 1394 Link layer to send one Asynchronous packet.
- the LK—DATA.req primitive contains the following information.
- Destination offset This parameter is fixed to a value indicating that ASEL-PDU is stored in the Data field of this Asynchronous packet.
- the LK_DATA.conf primitive is used by the 1394Link layer to allow the upper layer to confirm the transmission of one Asynchronous packet.
- the LK_DATA.ind primitive is used to receive UBR or ABR data.
- the 1394 Link layer uses this primitive to notify the ASEL entity that one Asynchronous bucket has been received.
- the LK_DATA.ind primitive contains the following information.
- Destination offset This writer is fixed to a value to indicate that ASEL-PDU is stored in the Data field of this Asynchronous knock.
- Resp primitive is used by the ASEL entity to respond to a single received Asynchronous packet. That is, by sending one acknowledge packet, the sub-action is completed.
- Resp primitive contains the following information:
- This parameter contains one of the Ack_code values defined in the IEEE1394 standard.
- Bus Occupancy Control This parameter controls whether the 1394 Link Layer will relinquish control of the 1394 Serial Bus after transmitting the acknow 1 edge packet.
- ASEL exchanges various management information with its own (local) ASEL layer management entity, such as configuration, faults, performance, and alarms on the other ASEL entity and its own ASEL entity.
- ASEL management primitives including.
- the MASEL_Act.req primitive is used by the ASEL layer management on the User side to request that the ASEL entity transition to the activated state (Actstatus).
- the MASEL_Act. Ind primitive is used by the ASEL entity to notify the ASEL layer management that the ASEL entity has transitioned to the active state (Actstatus).
- MASEL_Act.req and MASEL_Act.ind primitives contain the following information.
- MASEL_Reset.req from ASEL layer management is received as a primitive related to ASEL reset.
- the MASELJeset.req primitive is used by the ASEL layer management to request that the ASEL entity transition to the reset status (Resetstatus).
- MASEL_Reset.req primitive contains the following information.
- MASEL_ConSet.req and MASEL-ConRec.req from ASEL layer management as primitives related to ASEL connection control, and provides MASEL ConSet.conf.
- ASEL layer money Receives MASEL_ConRel.req from the comment and provides MASEL_ConRel.conf.
- MASEL The ConSet.req primitive is used by ASEL layer management to request that a new ASEL-VCC be set.
- Routing Area This parameter indicates the ASEL-VCC routing area to be set. There are five types of parameter values: External / Internal and same 1 394 Bus / Internal and other 1 394 Bus / Terminate / Unknown.
- Topology This parameter indicates the form of ASEL-VCC. There are two types of parameter values: Point-Point / Point-Multipoint.
- AAL5 Specific information This parameter is used only when the AAL type parameter is AAL5.
- QoS class This parameter determines the quality of service of the ASE VCC. There are four types of parameter values: UBR / CBR / VBR (Variable Bit & ate) / ABR.
- ABR traffic information This parameter is used only when the QoS class parameter is ABR.
- MASEL The Con & ec.req primitive is used to request that the ASEL-VCC at the ASEL-UNI that has returned to Act status after returning to Reset status due to a bus reset at 1394 be reset. Used by ASEL layer management of User side.
- the MASEL_ConSet.conf primitive is used by the ASEL entity to verify the result of an action on the MASEL_ConSet.req or MASEL_ConHereq primitive by the ASEL layer management.
- the ASEL entity also uses the MASEL-ConSet.conf primitive to notify that ASEL-VCC has been restored.
- the MASEL_ConRel.req primitive is used by ASEL layer management to release ASEL-VCC.
- the MASEL_ConRel.conf primitive is used by the ASEL entity to confirm the result of an action on the MASEL_ConRel.req primitive to the ASEL layer management.
- the MASEL_Conec.req, MASEL_ConSet.conf, MASEL_ConRel.req and MASEL_ConRel.conf primitives contain the following information.
- VPI / VC1 value • An ID (ASEL Connection ID) for uniquely identifying each ASEL connection on all ASEL-UNIs existing in the ASEL entity
- MASEL_BusHa.ind and MASEL-ExpireEr.ind are supplied to the ASEL layer management as primitives related to ASEL local faults. Since these primitives indicate that a critical ASEL entity has experienced a major failure, the ASEL layer management entity and application software will immediately respond to the failed ASEL- All resources associated with the UNI should be released.
- the MASEL_BusHalt.ind primitive indicates that the 1394 serial bus has been stopped on the User side, and the 1394 serial bus has been stopped on the Network side, or Indicates that the terminal has been lost.
- the MASEL—ExpireEr. Ind primitive indicates that the local ASEL entity has experienced a critical error upon expiration of the event.
- the MSEL_BusHalt.ind and MASEL—ExpireEr.ind primitives include the following information.
- MASEL_FatalEr Ind is supplied to the ASEL layer management as a primitive related to the remote control of ASEL. This primitive means that some serious error has occurred in the remote ASEL entity, so that the ASEL layer management entity and the application software can immediately respond to the failed ASEL entity. -All resources related to VCC should be released
- the MASEL_FatalEr.ind primitive contains the following information.
- Error Code This parameter code is used to code the error that occurred in the remote A SEL entity.
- MASEL_IsoEr.ind, MASEL_DestEr.ind, and MASEL_StsEr.ind are supplied to ASEL layer management as primitives related to ASEL local errors.
- the DestEr.ind primitive indicates that an error related to the ASEL-VCC setting has occurred in the local ASEL entity, so the ASEL layer management entity and application software Should immediately release all resources associated with the failed ASEL-VCC.
- MASEL The StsEr. Ind primitive indicates that an error related to a state transition has occurred at the ASEL entity.
- the MASEL_StsEr. Ind primitive contains the following information.
- ASEL_UNI ID identifying ASEL-UNI
- MASEL_DATA.req is received from ASEL layer management as a primitive for data transfer including ASEL layer management information, and DATA.ind is supplied to MASE. These primitives are used to transfer arbitrary management information between peer peer ASEL layer management entities.
- the MASE DATA. ⁇ ⁇ eq and MASEL ⁇ _DATA.ind primitives contain the following information.
- Management ID This parameter is used to identify the type of management information included as an interface.
- Interface Data This parameter always corresponds to a complete AAL-SDU.
- Loss Priority This parameter indicates the loss priority of the AA / SDU. This parameter is mapped to an ASEL-PDU described later.
- Congestion Indication This parameter indicates whether the AAL-SDU has gone through a congestion state. This parameter is mapped to the ASE PDU header described later.
- Error Status This parameter indicates that the interface status may contain transmission errors. This parameter is used only when the error data distribution function is used. This parameter is not included in the MASEL_DATA.req primitive.
- VPC / VCC demultiplexing in each ASEL-UNI is possible. That is, the ASEL entity enables setting of a plurality of VPCs / VCCs on the isochronous channel. Note that VPC / VCC VPI (Virtual Path Identification) / VCI (Virtual Channel Identification) values set on different Isochronous channels may overlap.
- VPC / VCC VPI Virtual Path Identification
- VCI Virtual Channel Identification
- the ASEL entity has a Dest (Destination) -ID, which is the destination node ID number when transmitting, and a Src (Source) -ID, which is its own node ID number when receiving, which has multiple VPI / VCI values for each ID. Settings and identification.
- VPC / VCC VPI / VCI values for different Dest-IDs or Src-IDs may overlap.
- Various parameters related to VPC / VCC are set using the MASEL_ConSet.req primitive from ASEL layer management.
- ASEL guarantees Quality of Service (QoS). That is, ASEL uses ATM's CBR (Constant Transmission Rate: Constant Bit Rate) service using Isochronous packet of IEEE1394 standard, ATM's UBR (Unassigned Bit Rate) service, and ABU (Available Bit Rate) Service is performed using Asynchronous packets of the IEEE1394 standard, and QoS is guaranteed for ASEL users.
- Figure 7 shows the overnight format of buckets exchanged in the IEEE1394 standard. This packet is composed of a header part and a data field, and the header part contains information such as a destination address, own node address, and transfer data size in the case of an asynchronous packet.
- sochronous packet information such as a channel ID is entered, and data to be actually transmitted is stored in a data field in units of quadlets.
- the size of the data field is variable, and the data field has an appropriate number of bytes and zero pad bytes as needed at the end of the data transfer so that the size of the packet is in units of 4 bytes. Is inserted 0
- the maximum length of the bucket is 102 bytes for an IEEE 1394 standard isochronous packet, and IEEE 1394 standard. In the Asynchronous bucket of this, it is 512 pite. Also, in the ASEL entity, the transmission segment size parameter of the MASEL-ConSet.req primitive is set for each ASEL-VCC before performing the data transfer. Therefore, a packet exceeding either value is divided into multiple packets and software and transmitted.
- a packet transmitted from a predetermined node is transferred to all nodes in the IEEE 1394 serial bus. It reads the header part of this packet and reads it if it is a packet destined for its own node.
- a channel ID is used without using a node address. For example, when transferring data from multiple nodes at the same time, set the channel ID to distinguish the contents of the transferred data and receive the data. The node sets the channel ID corresponding to the predetermined transfer data and receives only the desired data. Therefore, two or more nodes can receive data with the same channel ID.
- ASEL-PDU Protocol 'Data Unit: Protocol Data Unit
- ASEL-PDU is a write request for Asynchronous packet formats with data block payload specified in IEEE1394 standard. Inserted in the data field of data block packets or Isochronous data-block packed format. As described later with reference to FIGS. 8 to 10, the ASEL-PDU is composed of a header part and a payload part.
- Destination offset field A unique offset value that indicates that the ASEL-PDU is stored in the destination field of this Asynchronous packet.
- the ASEL-PDU includes a header section and a payload section.
- VPI / VCI information for identifying VPC / VCC
- AAL-SDU Service Data Unit
- the ASEL-PDU payload contains the following information.
- ASEL implements the various functions described above by using an ASEL-PDU as shown in FIG. 8 between peer ASEL entities.
- Figure 8 shows the format of the ASEL-PDU common to all AAL types.
- VPI / VCI value is a VPI / VCI value field. One byte is allocated to VPI value and two bytes are allocated to VCI value. This is for emulating VPI and VCI in ATM.
- Ml is a 1-bit Management information Indicator field that indicates whether the contents of the AA / SDU are ASEL layer management information. A value of 0 is set when the information is not ASEL layer management information, and a value of 1 is set when the information is ASEL layer management information.
- the MNG-ID is a 3-bit ASEL Layer Management Identifier Value is set when the value is Peer ASEL Entity Management, and the value is set when the value is Segment F5 flow 0AM. End-End F5 flow When 0AM, the value 0 1 0 is set. Further, when the resource management is performed, the value 011 is set. Other values are reserved. Here, “reserved” means an undefined state.
- QoS Class is a 4-bit QoS Class field that is set to a value of 0000 when URB service is used and is set to a value of 00001 when using CBR service. . Also, when using the VBR (Variable Bit Rate) service, the value 010 is set. In addition, the value 0 0 1 1 is set when using the ABR (Available Bit Rate) service. Other values are reserved.
- MR is a 1-bit More Indication field that indicates whether the exchanged PDU includes the end of the AA or SDU.
- the value 0 is set when the end of the AA-SDU is included, and the value 1 is set when the end of the AAL-SDU is not included.
- SN is a 7-bit Sequence Number field, which is managed for each VPI / VCI value.
- AAL-SDU transmits an ASEL-PDU other than ASEL layer management information
- the modulo 128 Is incremented by 1. This field is not added when ASEL layer management information is included. Therefore, if the value of the SN field is discontinuous, the receiving side can detect that ASEL-PDU has been lost or erroneously inserted due to a transmission error or the like in the middle.
- the AAL-Type field is composed of 4 bits and indicates the type of AAL.
- AAL 0 equivalent to null AAL or raw cell
- the value 0 00 00 is set.
- the AAL type is AAL1
- the value 00001 is set.
- the AAL type is AAL2
- the value 0 0 1 0 is set.
- the AAL type is AAL 3 or 4
- the value 0 1 1 is set.
- the AAL type is AAL5, the value 0101 is set. The value 0 100 and other values are reserved.
- the AAL Specific Information field is composed of 20 bits, and stores information specific to each AAL type.
- the Payload (AAL-SDU) field is variable in length and stores the SDU to be exchanged with the upper layer or layer management.
- the PAD field is the zero pad bytes in the asynchronous field of the Asynchronous / Isochronous packet of the IEEE1394 standard, and is inserted so that the Payload field is an integral multiple of 4 bytes. You.
- Fig. 9 shows the format and coding example of ASE (PDU) (AAL 5 Type).
- ASEL-PDU of AAL5 Type the value 0 is set in the Ml field shown in FIG. 8, and the value 0101 is set in the AAL Type field.
- information specific to the AAL 5 Type is stored in the AAL Specific Information field. That is, LP is a 1-bit Loss Priority field, and the value 0 is set when the loss priority is low and the value 1 is set when the loss priority is high.
- the LP field is used when priority is given to discarding unimportant cells in the event of congestion in the system.For example, those with a value of 0 are hard to discard. Processed so that a value of 1 is set to be easily discarded.
- CI is a 1-bit Congestion Indicator field that is set to a value of 0 when there is no congestion history and to a value of 1 when there is congestion history. Is done. The next two bits are reserved.
- EI is a 1-bit Error Indicator field. The value is set to 0 when there is no error, and to 1 when there is an error.
- the ER-ID is a 7-bit Error Identifier field. If not used, the value 0000-0000 is set. The value 0 00000 1 to 0 1 1 1 1 1 is reserved. In the case of a CPCS (Common Part Convergence Sublayer) CRC error, the value 1 0 0000 1 is set, and in the case of a CPCS-SDU Length error, the value 1 0000 10 is set. Other values are reserved.
- CPCS Common Part Convergence Sublayer
- the next CPCS-UU is an 8-bit CPCS-User to User information fie Id.
- Figure 10 shows an example of the format and coding of an ASE (PDU) (AAL0 Type).
- AAL0 Type In the format of the ASEL-PDU of AAL0 Type, a value of 0 is set in the MR field and a value of 0000 is set in the AAL Type field shown in FIG. Then, information specific to the AAL0 Type is stored in the AAL Specific Information field. That is, LP is a 1-bit Loss Priority field, in which the value 0 is set when the loss priority is low, and the value 1 is set when the loss priority is high.
- CI is a 1-bit Congestion Indicator field. The value 0 is set when there is no congestion history, and the value 1 is set when there is congestion history. The next two bits are reserved.
- EI is a 1-bit Error Indicator field. The value is set to 0 when there is no error, and to 1 when there is an error.
- ER-ID is a 7-bit Error Identifier field, and the value 0000000 is set when it is not used.
- OAM Operaation And Maintenance
- ASE or CMI Connection Management Interface
- ASEL-CMI exchanges ASE CMEs (Connection Management Entities) mounted on ATM / 1 394 repeater 3 which is a network side and 1 394 terminals 4-1 to 4-3 which are User side This is the interface for connection.
- ASEL-CMI The functions of ASEL-CMI are shown below.
- ASEL-PDUs called "ASEL Connection Management Protocol (ASEL-CMP)" are transferred via ASEL-CMI.
- ASEL-CMP ASEL Connection Management Protocol
- ASEL-CMP controls ASEL-VCC by transferring messages between peer ASEL-CMEs using ASEL-PDUs using AAL0-type Asynchronous packets.
- VPI / VCI value All "0"
- MNG-ID 0 0 0 (peer ASEL entity management)
- QoS class 0 0 0 0 0
- AAL-Type AAL0
- Tables 1 and 2 list the messages used in ASEL-CMP.
- the messages in Table 1 cause ASEL-CME to make a state transition when transmitted and received. These are possible messages, and the messages in Table 2 are those that do not cause a state transition.
- the Wakellp message (the format of which will be described later with reference to Fig. 15) is used when the ASEL-CME on each User side notifies the Network side that its startup has been completed. .
- This message always uses the broadcast address as the Destination ID of the 1394 Asynchronous packet.
- the ASEL-CME on the Network side activates the ASEL-CME for each User side after receiving the WakeUp message.
- Used when requesting registration of the Self ID of the Network side for example, an ID automatically added by the IEEE1394 standard at power-on, etc.
- Node Unique ID for example, an ID automatically added by the IEEE1394 standard at power-on, etc.
- the ActAck message (the format of which will be described later with reference to Fig. 17) is used when the ASEL-CME of the user side notifies the Network side of the result of the operation for ActReq reception.
- the IsoReq message (the format of which will be described later with reference to FIG. 18) is used by the ASEL-CME on the user side to request the value of the isochronous channel for resolving the assigned VPI / VCI from the network side. Used when doing
- the IsoRply message (the format of which is described below with reference to FIG. 19) is used when the ASEL-CME of the network side responds to Iso & eq to assign the isochronous channel to the user side. You.
- the DestlDReq message (the format of which will be described later with reference to FIG. 20) is a method in which the ASEL-CME on the user side uses the Asynchronous target CD Destinat ion IDiO i to resolve the assigned VPI / VC I. Used when requesting a Network side.
- the DestlDRply message (the format of which will be described later with reference to FIG. 21) is used when the ASEL-CME of the network side responds to the DestlMeq to inform the user side of the self ID of the destination node to the user side. used.
- Figures 12 and 13 show the state transitions in the ASEL-CME on the User side and Network side, respectively.
- Reset Status indicates the initialization state or the state of whether or not the reset topology is determined immediately after the reset of the 1394 serial path.
- ActPending Status indicates the user side. (Fig. 12) shows the state of receiving ActReq message from Network side, and Network side (Fig. 13) shows the state of waiting for ActAck message from User side. Act Status is Network side.
- both USER SIDE and USER SIDE indicate that they recognize each other that ASEL-CME is activated.
- Timerjleset is for indicating a bus reset permission period of the 1394 serial bus. Normally, even when a 1394 bus reset occurs, it recovers from the reset state within several 10 Ozs.
- ASEL-VCC must not be released by such a transition to the reset state. That is, until Timer_Reset expires, N
- the ASEL-CME on the etwork side and each User side must maintain all ASEL-VCC settings. However, Asynchronous buckets in ASE L-VCC of Point-Point topology type will be discarded until each ASEL-CME returns to Act Status. This is because those Asynchronous nozzles (DestinationIDs at this time are indeterminate at this time).
- Timer-ActPending indicates a timing for resending a WakeUp message on the User side or an ActReq message on the Network side.
- Figure 14 shows the format of the fields common to all ASEL-CMP messages.
- the Message ID field is composed of 8 bits and indicates the type of the ASEL-CMP message.
- the value 0 0 0 0 0 0 0 0 is unused.
- the value 0 0 0 0 0 0 1 is set for the WakeUp message
- the value 0 0 0 0 0 0 10 is set for the ActBeq message
- 0 1 1 is set, if the value is an IsoHeq message, the value 0 0 0 00 100 is set, if the message is an IsoRply message, the value 0 0 0 0 101 is set, and the DestlDReq message is set.
- the value 0 0 0 0 0 1 1 10 is set, and in the case of the DestlDRply message, the value 0 0 0 0 0 1 1 is set.
- Other values are reserved.
- the Reference ID field consists of 16 bits, and indicates an identification number that is referred to by each other so that there is no inconsistency in state transition between Network side and User side.
- the Error Code field is composed of 8 bits, and indicates the error or the cause of the storage error that occurred in ASEL-CME.
- the Error Code field is defined for each message. Details of the coding rules will be described later. If there are no errors or warnings, the value 0 0 0 0 0 0 0 0 is set. If a warning event occurs, the value is set to the upper two bits. If a message with a warning is received, continue processing as much as possible. If a serious error event occurs, the upper two bits are set to the value 11. When a message with this error is received, an error is immediately notified to the ASEL layer management. Other values are reserved.
- FIG. 15 shows the format of the WakeUp message.
- the coding of the Error Code field is set to the value 0 0 0 0 0 0 0 0 0 0 if there is no error, and the value 1 0 0 0 0 0 if the message retransmission warning 0 0 1 is set.
- Other values are reserved
- the Unique_ID (NU_ID) field of the User Side Node is composed of 64 bits, and the ASEL-CME of the User Side uses the globally unique Node Unique held by the User Side Node 1394 terminal.
- the value of ique ID is set. Upper 24 bits indicate Vendor_ID, Lower 40 bits Indicates Chip-ID.
- the User side Self ID field is composed of 16 bits, and the value of Self ID which is the node address of User side is set by ASEL-CME of User side.
- the upper 10 bits indicate BUSJD, and the lower 6 bits indicate PHY_ID.
- Figure 16 shows the format of the ActReq message.
- the coding of the Error Code field is set to the value 0 0 0 0 0 0 0 0 0 when there is no error, and the value 1 0 0 0 0 0 0 is set in the case of a message retransmission warning. 1 is set. Furthermore, in the case of a topology change warning, the value 1 00 0 0 0 10 is set. Other values are reserved.
- the Network side Node_Unique_ID (NU_ID) field is composed of 64 bits and is globally unique by the ASEL-CME on the User side, which is owned by the Network side device for each 1394 serial path.
- One of the Node Unique ID values is set.
- the upper 24 bits indicate Vendor_ID, and the lower 40 bits indicate Chip-ID.
- the Network side Self ID field is composed of 16 bits, and the value of Self ID, which is the node address of the Network side, is set by the ASEL-CME of the Network side.
- the upper 10 bits indicate BUS_ID, and the lower 6 bits indicate PHYJD.
- FIG. 17 shows the format of the ActAck message.
- the coding of the Error Code field is set to the value 0 0 0 0 0 0 0 0 0 0 if there is no error, and the value 1 1 0 0 0 0 0 0 if the error is a serious error of startup failure. 1 is set. Other values are reserved. 1 7
- Figure 18 shows the format of the IsoReq message.
- the coding of the Error Code field is set to the value 000 000 000 if there is no error, and to the value 1 0000 001 if there is a message retransmission warning. You.
- the Assigned VPI / VCI field consists of 24 bits, and the VPI value (8 bits) and the VCI value (16 bits) assigned by the MASEL-ConSet.req primitive from its own ASEL layer management. Bit) is set.
- FIG 19 shows the format of the IsoRply message.
- the coding of the Error Code field is set to the value 00000000 if there is no error, and to the value 1100000 if there is a critical error for which there is no available isometric channel. 10 is set.
- the Assigned VPI / VCI field consists of 24 bits, in which the VPI value (8 bits) included in the IsoReq message from the user side and the VCI value (16 bits) are set.
- the Assign Isochronous Channel field is composed of 8 bits, and the upper 2 bits are set to the Tag field of the 1394 Isochronous packet header.
- Lower six bi Uz DOO is 0 Isochronous channel that Network side assigned is Se Uz Bok
- the Tag field As an example of how to use the Tag field, it is used as a bitmap for filtering when receiving Isochronous packets. For example, of the 2 bits, the upper bit is the Listen Bit of the Network Side and the lower bit is the Listen Bit of the User Side, and the packet is received only when the corresponding bit is "1". To This usage is different for each node However, when the filtering function of the Isochronous channel is not sufficient (for example, when the number of channels that can be set is small), it is effective when it is desired to prevent the reception of unnecessary packets as easily as possible. For example, by setting the Tag field of the Dummy bucket to be transmitted when there is no packet to be transmitted to (0, 0), the value of the isochronous channel can be ignored without being identified.
- (0, 1) is assigned to ASEL-VCC that only the User Side should receive
- (1, 0) is assigned to ASEL-VCC that only the Network Side should receive
- (1, 1) is User Both Side and Network Side are assigned to ASEL-VCC to be received.
- the tag field or expand the number of channels of the isochronous channel. In other words, expand the 6-bit isochronous channel to 8 bits and use the tag field for the upper 2 bits.
- the value 00 of the Tag field is not used, so the value from 00000000 to 00 1 1 1 1 1 1 cannot be used for this field as a whole.
- the value from 0 000000 to the value 1 1 1 1 1 1 1 1 is set as the isochronous channel 1.
- the ASEL-VCC Opr_Speed field consists of 8 bits, and indicates the speed at which data can be transferred in this ASE-VCC. For S100 (100 Mb ps), the value 00000000 is set; for S200 (200 Mbps), the value 00000001 is set. Furthermore, in the case of S400 (400Mbps), the value 00000010 is set. Other values are reserved.
- Figure 20 shows the format of the DestlDReq message.
- the coding of the Error Code field is If there is no password, the value 000000 00 is set, and in the case of a message resend warning, the value 100000001 is set.
- the Assigned VPI / VCI field consists of 24 bits, and the VPI value (8 bits) and VCHil (16 bits) assigned by the MASEL_ConSet.req primitive from its own ASEL layer management. Set.
- Figure 21 shows the format of the DesUDRply message.
- the coding of the Error Code field is set to the value 000000 0 0 if there is no error, and to the value 1 1 0000 1 1 if there is a serious error where the Destination ID cannot be found. Is done.
- the Assigned VPI / VCI field consists of 24 bits, and sets the VPI value (8 bits) and the VCI value (16 bits) included in the DestlDReq message from the User side.
- the Destination Self ID field is composed of 16 bits, and the value of Self ID, which is the destination node address corresponding to this ASEL-VCC, is set.
- the upper 10 bits indicate BUS_ID and the lower 6 bits indicate PHY_ID.
- the ASE VCC 0pr_Speed field is composed of 8 bits and indicates the speed at which data can be transferred in this ASE-VCC.
- S 100 100 Mb ps
- the value 0000000 0 is set.
- S 200 200 Mbps
- the value 00 00 00 01 is set.
- S400 400Mbps
- the value 00 00 00 10 is set.
- Other values are reserved.
- SDL Stateand The explanation will be made using the flowchart described in (Description Language).
- the list of SDL keys is shown in Figure 22.
- Each symbol shown in the flowcharts of FIGS. 23 to 53 has a meaning as shown in FIG.
- the processes related to ASEL-CME commands on the User side shown in Fig. 12 are shown in Figs. 23 to 28, and the processes related to ASEL-CME commands on the Network side shown in Fig. 13 are shown in Figs. See Figure 35.
- a data transfer process on the transmission side is shown in FIGS. 36 to 43, and a data transfer process on the reception side is shown in FIGS. 44 to 53.
- • aselLayerOprMode indicates whether the ASEL entity is operating in User side mode or Network side mode. It can be set to three values: Unknown (0), Use r side (l), and Network side (2). Can be taken.
- • aselLayerTimerJleset indicates the time from Timer_Reset activation to expiration, and is represented by an integer value from 1 to 64. The unit is seconds. The default value is 32.
- • aselLayerTimer_ActPendiiig indicates the time from the start of the Timer-ActPending to the expiration, and is represented by an integer from 1 to 64. The unit is seconds. The default value is 1.
- • aselLayerMaxTimerExpire indicates the maximum number of expirations allowed for a Timer—ActPending event, and can range from 1 to 255. The default value is 4.
- • aselLayerl394Dest0ff set indicates a special Destination Offset address used to identify that the content (payload) of the received Asynchronous write request packet is an ASEL-PDU, and 48 bits (0 to O xffffffffffffffff) can be an integer.
- • aselLayerl394Bus Index indicates the value (1394 Bus Index value) for uniquely identifying the 1394 serial path existing on ASEL-UNI.
- aselLayerStatus indicates the current operation status of ASEL-UNI, and can take three types of values, Reset (O), ActPending (1), Act (2), like Status of ASEL-CME.
- the initial value is Reset (O).
- • aselLayerNetSideNodeUniqld indicates a globally unique value (Network side Node_ Unique. ID value) for identifying the 1394 node on the Network side of ASEL-UNI, and 64 bits (0 to 0 xf ff ffffffffff ) Can take an integer value.
- • aselLayerUserSideNodeUniqld indicates a globally unique value (User side Node_ Unique_ID value) for identifying the 1394 node on the User side of ASEL-UNI, and 64 bits (0 to 0 xf fffffff) fff fffff).
- • aselLayerNetSideNodeSelf ld indicates the physical address value (Network side Self ID) on the 1394 serial path for identifying the 1394 node on the Network side of ASEL- UNI, and 16 bits ( It can take an integer value from 0 to O x ffff). The initial value and the value after clearing are O xffff You.
- • aselLayerUserSideNodeSelfld indicates the physical address value (User side SelfID) on the 1394 serial bus for identifying the 1394 node on the ASEL-UNI User side, and 16 bits (0 to Oxffff) Can take an integer value.
- the initial value and the value after clearing are Oxffff.
- • aselVccVpi indicates the VSEL value of ASEL-VCC, and can take a value from 0 to 255.
- • aselVccVci indicates the VSEL value of ASEL-VCC and can take a value from 0 to 65535.
- • aselVccConnld indicates the value (ASEL Connection ID value) for identifying ASEL-VCC to the public through all ASEL-UNIs.
- aselVccTopology indicates the type of ASEL-VCC topology that has been set, and can take two values: Point-Point (1) and Point-MultiPoint (2).
- • aselVccStatus indicates the status of ASEL-VCC, and can take two values: Down (0) and Up (1).
- the upper layer of ASEL can perform data transfer only when this state is Up (l).
- aselVccAalType indicates AAL Eve used by ASEL-VCC, and can take five values: AAL0 (0), AAL1 (1), AAL3 / 4 (3), and AAL5 (5).
- aselVccQosType indicates the QoSClass for bidirectional transmission and reception of ASEL-VCC, and can take four values: UBR (0), CBR (l), VBR (2), and ABR (3).
- aselVccOprSpeed indicates the speed at which ASEL-VCC data can be transferred, and can take three values: S100 (0), S200 (l), and S400 (2).
- • aselVccTransmitSegLen is used to split a long AAL-SDU into several equal length data units, excluding the final data unit. These data units are transmitted as ASEL-SDU.
- the value of this parameter is equal to the length of the ASEL-PDU to be transmitted, and is indicated by an integer value in units of bits.
- • aselVccReceiveSeqUse sets whether or not the ASEL entity uses the Sequence Number of the received ASEL header for each ASEL-VCC, and can take two values: No use (0) and Use (l) .
- aselVccIsoChannel indicates the tag value and isochronous channel value used by the ASE VCC, and is expressed as an integer from 0 to 255.
- aselVccIsoDelayVariationTolerance indicates the permissible delay fluctuation value for ASEL-PDU in ASEL-VCC on Isochronous link, and is expressed in the number of ASEL-PDUs per unit time.
- aselVccIsoTransmitBand indicates the transmission band of ASEL-PDU in ASE or VCC on Isochronous link, and the unit is 64Kbps (1 Byte / Cycle).
- aselVccIsoReceivedBand indicates the reception band of ASEL-PDU in ASE or VCC on Isochronous link, and the unit is 64Kbps (1 Byte / Cycle).
- aselAal5ConnErSduDeliver is only relevant for ASEL-VCC using AAL5. If a CRC error is found in the received AAL5-SDU, the ASEL 5's emulation function in the ASEL entity can select whether to deliver the SDU to the upper layer.
- aselAal5ConnTransmitMaxSduSize indicates the maximum AAL5-SDU size (unit is octets) supported in the transmission direction of ASEL-VCC, and can take a value from 0 to 65535. The default value is 9 1 8 8.
- • aselAal5ConnReceiveMaxSduSize indicates the maximum AAL5-SDU size (unit is octet) supported in the ASEL-VCC reception direction, and can take a value from 0 to 65535. The default value is 9 1 8 8.
- AselAalOCormErSduDeliver is only relevant for ASEL-VCC using AAL0. If a CRC error is detected in the received AAL0-SDU, the emulation function of AAL0 in the ASE entity can select whether or not to deliver the SDU to the upper layer. The following parameters are set independently for each ASEL-VCC whose QoS Class is ABR.
- • aselVccAbrMinReceiveRate indicates the minimum reception rate of ASEL-PDU in ABR ASEL-VCC, and the unit is 64 Kbps.
- aselVccAbr lnitialTransmitRate indicates the initial transmission rate of ASEL-PDU in ABR ASEL-VCC, expressed in 64 Kbps. This parameter derives the sum of the ASEL-PDU lengths per first unit time at which the occurrence of the event starts. The value of this parameter must not be greater than aselVccAsyncPeakTransmitRate and is usually smaller.
- • aselVccAbrinitialReceive & ate indicates the initial reception rate of ASEL-PDU in ABR ASEL-VCC, and the unit is 64 Kbps.
- aselVccAbrAllowedTransmitRate indicates the transmittable rate of ASEL-PDU in ABR ASEL-VCC, expressed in 64 Kbps. This parameter may limit the total ASEL-PDU length per unit time. As soon as this is done, the aselVccAsyncPeakTransmitRate must not be too small and is usually small.
- • aselVccAbrTransmitTrm indicates the upper limit of the transmission RM cell interval included in the ASEL-P DU at the active source in milliseconds, and trm0point7 8125 (1), trmlpoint5625 (2) s trm3pointl25 (3), trm6point25 (4), trml2point5 (5), trm25 (6), trm50 (7), tnnl00 (8).
- the default value is trml00 (8).
- • aselVccAbrTransmitCdf is a cutoff reduction factor that controls the rate to be reduced in association with the loss or delay of backward RM cells included in the ASE-PDU.
- This parameter is composed of 8 types of cdfO (l), cdf0ne0ver64 (2), cdfOneOver32 (3), cdf0ne0verl6 (4), cdf0ne0ver8 (5), cdf0ne0ver4 (6), cdf0ne0ver2 (7), cdf0ne (8) Can take a value. The larger the value, the sooner the rate decreases. The default value is cdf0ne0verl6 (4).
- These parameters are: rifOne 0ver32768 (l), rif0ne0verl6384 (2), rif0ne0ver8192 (3), rifOneO ver4096 (4), rif0ne0ver2048 (5), rif0ne0verl024 (6), rifOneOver 512 (7), rif0ne0ver0256 (8) (9), rif0ne0ver64 (10), rif0ne0ver32 (ll), rif0ne0verl6 (12), rif0ne0ver8 (13), rifOneO ver4 (14), rif0ne0ver2 (15), rif0ne (16). The higher the value, the faster the rate will increase. The default value is rif
- These parameters are: rdf0neOver3276 8 (1), rdf0ne0verl6384 (2), rdf0ne0ver8192 (3), rdf0ne0ver4096 (4), rdf0ne0ver2048 (5), rdf0ne0verl024 (6) rdf0ne0ver512 (7), rdf0ne0ver256 (8), rdf0ne0verl28 (9), rdf0ne0ver64 (10), rdfOne 0ver32 (ll), rdf0ne0verl6 (12), rdf0ne0ver8 (13), rdf0ne0ver4 (1 4), rdf0ne0ver2 (15),
- • aselVccAbrTransmitAdtf is the ACR decrease time factor, and indicates the allowable time between transmissions of the RM cell included in the ASEL-PDU before the ACR is reduced to the ICR, from 1 to 1023 (unit is 1 0 Values up to milliseconds). The higher the value, the longer the current rate will be maintained. The default value is 50 (50 Oms).
- steps S1 to S10 in FIG. 23 is processing in the case of transition from the reset state to the state of ActPending, and the processing of steps S13 to S19 returns to the state of reset again. This is the process in the case of transition.
- the route corresponding to the processing of steps S11 and S12 is not shown in FIG.
- step S1 upon receiving the primitive of MASEL—Act—Req from the ASEL layer management, in step S2, the ASE L-CME determines whether the ASEL-UNI ID already exists. . If the ID does not yet exist, the process proceeds to step S3, and the ASEL-CME sets the ASEL-UNI ID to asel LayerUni Id.
- step S4 aselLayer1394BusIndex is set. Further, in step S5, aselLayerllserSideNodeUniqld and aselLayerUserSideNodeSelfld are set. If it is determined in step S2 that the ASEL-UNI ID already exists, Steps S3 to S5 are skipped.
- step S7 a message of Wakellp is output to ASEL-CME of Network side.
- step S8 ActPending is set in aselLayerStatus.
- Timer_Reset is stopped in step S9, and Timer-ActPending is started in step S10.
- the state transits to the ActPending state.
- step S13 when a local event indicating that the Timerjleset has expired is received, the process proceeds to step S14, and a process of transmitting a stop event of a recovery stop from reset is performed.
- step S15 the ASEL-VCC on the corresponding ASEL-UNI is searched.
- step S16 it is determined whether or not the search has been completed. If the search has not been completed, the process proceeds to step S17, and a process of releasing all resources related to the searched ASEL-VCC is executed. Thereafter, the process returns to step S15, and the subsequent processes are repeatedly executed.
- step S16 When it is determined in step S16 that the search has been completed, the process proceeds to step S18, and aselLayerUni Id, aselLayer 13394 Buslndex, aselLayerNetSideNodeUniqld, and ase ayerUserSideNodeUniqld are cleared, respectively. Thereafter, the flow advances to step S19 to output a MASEL_BusHalt. Ind primitive to ASEL layer management, and returns to the reset state again. After receiving the MASEL_BusHalt. Ind primitive, the application software immediately releases all VCC-related resources on the ASEL-UNI.
- step S1.1 if a recoverable local event from Reset is received, the process proceeds to step S12, where ASE is UN I It is determined whether or not the ID already exists. If the ID does not exist, the state returns to the Reset state again. If the ID exists, the process proceeds to step S6, and the subsequent processing is executed and the ActPending is executed. Transition to the state.
- steps S31 to S38 represents the processing when transitioning from the ActPending state to the Act state, and the processing of steps S39 to S46 is performed again from the ActPending state. This shows the process when returning to the ActPending state.
- step S32 When the ActReq PDU is received from the ASEL-CME on the Network side in step S31, it is checked in step S32 whether the Refrence ID is True. If this ID is True, the process proceeds to step S33, where aselLayerNetSideNodeUniqldii aselLayerNetSideNodeSelfld is set. In Step S34, the PDU of ActAck is transmitted to the ASEL-CME of the Network side, and in Step S35, MASEL_Act. Ind is transmitted to the ASEL layer management.
- step S36 Timer_ActPending is stopped.
- K is set to 0, and in step S38, ActLayerStatus is set to Act. Then, the state transits to the state of Act.
- step S32 If it is determined in step S32 that the Refrence ID is False, the state returns to ActPending.
- step S39 if an oral event indicating that Timer_ActPending has expired is received, the process proceeds to step S40, and is incremented. This K represents the number of times Timer__ActPending has expired.
- K is aselLayerMax It is determined whether it is greater than TimerExpire. If it is determined that K is larger, the process proceeds to step S45, MASEL_expireEr.Ind is output to the ASEL layer management, and in step S46, is set to 0, and ActPending is set. Return to the state.
- step S41 When it is determined in step S41 that K is equal to aseLayerMaxTimerExpire or K is smaller, the process proceeds to step S42, and Timer_ActPending is restarted.
- Step S43 Error Code is set to Ox81, and in Step S44, a WakeUp message is transmitted as a PDU to ASEL-CME of Network side (retransmitted), and the state of ActPending Return to
- step S62 aselVccConnld, aselVccVpi, aselVccVci, aselVccAalType, aselVccQosType, aselVccTransmitSegLen, aseVcc, aselVcc , aselAalConn objects are set.
- step S63 it is determined whether or not aselVccQosType is subjected to CBI.
- step S64 If it is set to CBR, the flow advances to step S64 to set aselVccIsODe1ayVariationTo1eranc e, aselVcc IsoTransmitBand ⁇ aselVcc IsoReceiveBand. Then, in step S65, Iso & eq is transmitted to the ASEL-CME on the Network side as a PDU, and the state returns to the Act state.
- step S63 If it is determined in step S63 that CBR is not set in aselVccQosType, the process proceeds to step S66 and aselVccAsyncPeak TransmitRate and aselVccAsyncPeakReceiveRate are set.
- step S67 it is determined whether or not ABR is set in aselVccQosType, and if it is determined that ABR is not set, the process proceeds to step S69, and the PDU of DesUDReq is transmitted to ASEL-CME on the network side. And return to the Act state.
- step S 6 7 if the ABR is determined to be set to AselVccQosType, the process proceeds to step S 68, aselVccAbrVpi, aselV ccAbrVci, aselVccAbrMinTransmitRate, aselVccAbrMinReceiveRat e, aselVccAbrlnitialTransmitRate, aselVccAbrlnitialReceiveRa te, aselVccAbrAllowedTransmitRate, aselVccAbrAllowedReceiveR ate, aselVccAbrTransmitCdf, aselVccAbrTransmitRif, aselVccAbrTransmitRdf and aselVccAbrTransmitAtdf are set respectively. Thereafter, the process proceeds to step S69, where the PDU of DestlDReq is output to ASEL-CME on the network side
- step S70 When MASE L_ConRe Req is received from the ASEL layer management in step S70, the process proceeds to step S69, where DestlDReq is transmitted to ASEL-CME on the network side, and the state returns to Act.
- step S71 when the PDU of IsoRply is received from the ASEL-CME on the network side, the process proceeds to step S72, and it is determined whether a serious error has occurred. If it is determined that a serious error has occurred, the process proceeds to step S76, and ASE FatalEr.Ind (ErrorCode is set to C2h) is output to the ASEL layer management. Return to the state of Act.
- step S72 If it is determined in step S72 that no serious error has occurred, the process proceeds to step S73, where aselVccIsoChannel, aselVcc OprSpeed is set. In step S74, Up is set in aselVccStatus. Then, in step S75, MASE ConSet. Conf is output to the ASEL layer management, and the state returns to Act.
- step S77 when Dest lDRply is received from ASEL-CME on the Network side, the process proceeds to step S78, and it is determined whether or not a serious error has occurred. When it is determined that a serious error has occurred, the process proceeds to step S82, and MASEL_FatalEr. Ind (ErrorCode is set to C3h) is output to the ASEL layer management, and the state of Act Return to
- step S78 If it is determined in step S78 that no serious error has occurred, the process proceeds to step S79, where aselVccAsyncDest ID and aselVccOprSpeed are set, and in step S80, aselVcc Status is updated to Up. Is set. Further, in step S81, MASEL_ConSet. Conf is output to the ASEL layer management, and the state changes to Act.
- step S92 when ActReq is received from ASEL-CME on the network side in step S91, it is determined in step S92 whether or not the Reference ID is True. If it is determined that this ID is True, the process proceeds to step S93, where 0 is set in Error Code, and in step S94, ActAck is transmitted to ASEL-CME of the Network side. Then, in step S95, MASEL_StsEr. Ind is output to the ASEL layer management, and the state returns to Act. If it is determined in step S92 that the Reference ID is False, the processing in steps S93 to S95 is skipped, and the state immediately returns to the Act state. In addition, any state except Reset shown in Fig. 12 (ActPending or ActPending 27), the process shown in the flowchart of FIG. 27 is performed, and a transition to the Reset state occurs.
- step S101 when MASEL_Heset. Req is received from the ASEL layer management in step S101, the ASEL-VCC in the Asynchronous Link on the corresponding ASEL-UNI is searched in step S102. In step S103, it is determined whether or not the search has been completed. If not, the process proceeds to step S108, and "down" is set in aselVccStatus. Then, in step S109, aselVcc AsyncDest ld is cleared, the process returns to step S102, and the subsequent processing is repeatedly executed.
- step S103 If it is determined in step S103 that the search has been completed, the flow advances to step S104 to clear aselLayerUserSideSelfIdaselLayerNe tSideSelfld.
- step S105 Reset is set in aselLayerStatus, and in step S106, Timer_Reset is shut down. Further, in step S107, a mouth event during recovery starting from Reset is transmitted, and the state transits to the Reset state.
- step S122 when MASE ConRel. Req is received from the ASEL layer management in step S122, the process proceeds to step S122, and all the parameters in the corresponding ASEL-VCC are cleared. Then, in step S123, MASE L_Conile l. Conf is output to the ASEL layer management, and the private state is restored.
- FIG. 29 is a process performed in any of the three states shown in FIG.
- step S132 when the Wakelip is received from the ASEL-CME of the User side in step S131, in step S132, aselLayerNetSideNodeSelfID and aselLayerUserSideNodeSelfID are cleared.
- step S133 it is determined whether or not the NU-ID of the terminal on the User side that has transmitted the WakeUp message is the NU_ID of a new User side different from the previous one.
- step S 1 If it is determined that this is the new User side NIJ_ID, step S 1
- step S1305 the 1394 Bus Index in LK_DATA. Ind is set in the aselLayer 1394 Bus Index.
- step S136 aselLayerNetSideNodeUniqld and aselLayerUserSideNodeUniqld are set. Step S 1
- step 3 if it is determined that the NU-ID of the user side terminal that has transmitted the WakeUp message is not the NU_ID of the new user side, the processing in steps S 1 34 to S 1 36 is performed. Skipped.
- step S137 the process proceeds to step S137, where aselLayerUserSideNodeSelfld and aselLayerNetSideNodeSelfld are set.
- step S138 the Reference ID is stored.
- step S139 ActPending is set in aselLayerStatus.
- ActReq is transmitted to ASEL-CME on the User side, and in step S141, Timer_Reset is stopped. Further, in Step S142, after Timer_ActPending is activated, the state transits to the ActPending state.
- the Reset state the Act state
- the process of transition from the ActPending state to the ActPending state is performed.
- FIG. 30 shows a process for returning from the reset state of FIG. 13 to that state again.
- this process first, when a local event of Timer_Reset expiration is received in step S151, an ASEL-VCC on the corresponding ASEL-UNI is searched in step S152. Then, in step S153, it is determined whether or not the search has been completed. If not, the process proceeds to step S154 to execute processing for releasing all resources related to the searched ASEL-VCC. You. Then, the process returns to step S152, and the subsequent processing is repeatedly executed.
- step S155 proceed, aselLayerUni Id, aselLayer 13394 Bus Index, aselLayerNetSideNodellniqld, aselLayerUserSideNodeUniq Id is cleared. Ind is output to the ASEL layer management and returns to the reset state in SI 56.
- MASEL_BusHalt.Ind is output to the ASEL layer management in step S156, the steps in FIG. As in S19, after receiving this primitive, the application software releases resources for all VCCs on the ASEL-UNI.
- Step 3 Steps S161 to S167 from the state of ActPending to the state of ActPending, and the processing of returning to the state from the ActPending state (Step Flop S 1 6 1, S 1 6 2, S 1 6 3, S 1 6 8 to about the S 1 7 6) will be described.
- ActAck is received from ASEL-CME of User side in step S161
- reference ID is checked in step S162. If it is determined that the Reference ID is True, the flow advances to step S163 to determine whether a serious error has occurred. If no serious error has occurred, the process proceeds to step S164 and Act is set in aselLayerStatus. Then, in step S165, MASEL_Act. Ind is output to the ASEL layer management.
- step S166 Timer-ActPending is stopped, K is set to 0 in step S166, and the state transits to Act.
- Step S162 when it is determined that the Reference ID is Fault, the state immediately transits to the ActPending state. If it is determined in step S163 that a serious error has occurred, the process proceeds to step S168, where MASE FatalEr. Ind (Error Code is set to C1h) is transmitted to the ASEL layer. After being output to the management, it transits to the ActPending state.
- MASE FatalEr. Ind Error Code is set to C1h
- step S169 if an event indicating that Timer_ActPending has expired is received, the process proceeds to step S170, in which a variable equal to the number of timer_ActPending expirations is incremented by 1, and then to step S171. Therefore, it is determined whether K is greater than aselLayerMaxTimerExpire. If K is determined to be larger, the process proceeds to step S175, MASEL_ExpireEr.Ind is output to the ASEL layer management, and then in step S176, K is set to 0, and ActPending Return to the state.
- step S 172 The processing for restarting Timer_ActPending is performed. Then, in step S173, 0x81 is set to the Error Code, and in step S174, ActReq is transmitted (retransmitted) to ASEL-CME on the User side. Then, the state returns to ActPending.
- step S193 it is determined whether or not CBR is set in aselVccQosType. If it is determined that the setting has been made, step S194 proceeds, and aselVccIsoDelayVariationTolerance, ase IVccIsoTransmitBand, and aselVcc IsoReceiveBand are set. Then, it returns to the state of Act.
- step S193 If it is determined in step S193 that CBR is not set in aselVccQosType, the process advances to step S195 to set aselVccAsyncPeakTransmitRate, aselVccAsyncPeakReceiveRate.
- step S196 the flow advances to step S196 to determine whether or not aselVccQosType is ABR. , aselVccAbrAllowedTransmitRate, aselVccAbrAllowedRec eiveRate is set. If it is determined in step S196 that aselVccQosType is not ABR, the processing of step S197 is skipped. And it returns to the state of Act.
- step S198 when IsoReq is received from ASEL-CME on the User side in step S198, the process proceeds to step S199 to check for an available Isochronous channel. Then, in step S200, it is determined whether an available Isochronous channel exists. If it is determined that the channel exists, the process proceeds to step S201, the channel is set in aselVccIsoChannel, and in step S202, Up is set in aselVccStatus. Then, in step S203, IsoRply is transmitted to ASEL-CME on the user side, and in step S204, MASEL-ConSet.Conf is output to the ASEL layer management. Then, it returns to the state of Act.
- step S200 If it is determined in step S200 that there is no available isochronous channel, the process proceeds to step S205, and 0xC2 is set in Error Code.
- step S206 IsoRply indicating that the Iso channel does not exist is transmitted to the ASEL-CME on the user side, and in step S207, MASEL-IsoEr.Ind is output to the ASEL layer management. You. Then, the state returns to Act.
- step S208 If DestlDReq is received from the ASEL-CME on the User side in step S208, the process proceeds to step S209, and a search process for Destination SelfID is performed.
- step S210 it is determined whether or not Destination SelflD has been searched. If found, the process proceeds to step S211 and the result is set in aselVccAsyncDestID.
- step S212 Up is set in aselVccStatus, and step S2 At 123, DestlDRply is sent to ASEL-CME on User side. Further, in step S214, MASEL_ConSet.Conf is output to the ASEL layer management, and the state returns to Act.
- step S210 If it is determined in step S210 that the Destination Self ID has not been found, the process proceeds to step S215, and 0XC3 is set in Error Code.
- step S216 DestlDRply indicating that the Destination ID could not be found is transmitted to ASEL-CME on the User side.
- step S217 MASE DestlDEr. Ind is output to the ASE layer management, and then the state returns to Act.
- Step S231 of FIG. 33 when ActAck is received from ASEL-CME on the User side, it is determined in Step S232 whether Reference ID is True. If this ID is True, the flow advances to step S233 to determine whether a serious error has occurred. When it is determined that a serious error has occurred, the process proceeds to step S235, and MASEL_FatalEr. Ind (Error Code is set to C1h) is output to the ASEL layer management, and the Return to the state.
- step S233 If it is determined in step S233 that no serious error has occurred, the process proceeds to step S234, in which MASE StsEr. Ind is output to A SEL layer management, and then the state of Act is set. Return.
- step S232 If it is determined in step S232 that the Reference ID is False, the processing in steps S233 to S235 is skipped, and the state returns to Act.
- step S241 the processing of transition to Reset is performed by the processing in FIG. 34.
- MASEL—Reset.Req is received from the ASEL layer management in step S241
- the ASEL-VCC in the Asynchronous Link on the corresponding ASEL-UN is detected in step S224.
- a search process is performed.
- step S243 it is determined whether or not the search has been completed. If the search has not been completed, the process proceeds to step S244 and aselVccStatus is set to down. Then, after aselVccAsyncDestID is cleared in step S245, the process returns to step S242, and the subsequent processing is repeatedly executed.
- step S243 If it is determined in step S243 that the search has been completed, the flow advances to step S246 to clear aselLayerUserSideSelfId, aselLayerNetSideSelfld.
- step S247 Reset is set to aselLayerStatus, and in step S248, after Timer_Reset is started, the state transits to the Reset state.
- step S261 when MASEL_ConRel. & Eq is received from the ASEL layer management in step S261, all parameters in the corresponding ASEL-VCC are cleared in step S262. . Then, in step S263, MASEL-ConRel.Conf is output to the ASEL layer management, and then returns to the original state.
- Figures 36 and 37 show ASEL from AAL UNITDAT from Upper Layer in Figure 6.
- A. represents the processing when LKJS O.req or LK_DATA.req is output to the 1394 Link layer when receiving the input of Req.
- step S281 AAL_UNITDATA.Req is received from the Upper Layer in the Act state.
- This AALJJN I TDATA. Req includes ASEL-UNI ID, VPI / VCI Value, AAL-ID, More, AAL-LP, AAL-CI, AAL-UU, and AA ES.
- step S282 a check is made as to whether or not aselVccVpi and aselVccVci corresponding to the ASEL-UNI ID and VPI / VCI Value exist. If it is determined that these are true, the process proceeds to step S283, and it is determined whether or not aselVccStatus is Up. If Up is set in aselVcc Status, the process proceeds to step S284, where the value of aselVccVpi is set in the VPI Value of the ASEL header and the value of aselVccVci is set in the VCI Value. If the result of the check is False in step S 282, or if it is determined in step S 283 that Up is not set in aselVccStatus, the state returns to Act.
- step S285 aselVccQosType is set in the QoS class, and in step S286, it is determined whether the QoS class is CBR. If it is determined that the QoS class is CBR, the process proceeds to step S287, and a process for creating parameters for the primitive of LK_IS0.req is executed. Details of this processing will be described later with reference to the flowchart of FIG.
- step S286 If it is determined in step S286 that the QoS class is not CBR, the flow advances to step S288 to execute a process for creating a parameter of the primitive of LK_DATA.req. The details of this process are shown in the flow chart in Figure 41. —It will be described later with reference to the chart.
- TR_SN is a variable that is incremented in step S307, as described later.
- step S290 Ml is set to 0, and in step S291, MNG-ID is set to 0.
- step S292 it is determined whether aselVccAalType is AAL5 or AAL0. If aselVccAalType is determined to be AAL5, the process advances to step S293 to set AAL_Type to AAL5. Next, in step S294, the parameter creation process of AAL5Specificfile is executed. Details of this processing will be described later with reference to the flowchart in FIG.
- step S295 a pointer to the buffer storing the AAL-ID is set in ptrSDU, and in step S296, the length of the AA-ID is set in Count.
- step S297 it is determined whether the value of Count is greater than a value obtained by subtracting 8 from aselVccTransmitSegLen.
- step S297A More is "Not Used” (that is, not used) or "End of SDU” (that is, the last part of AAL-SDU). It is determined whether or not. If it is determined that More is “Not Used” or “End of SDU”, the process proceeds to step S298, MR is set to 0, and in step S310, the value obtained by adding 8 to Count is Set to Data Length.
- step S302 it is determined whether or not the QoS class is CBR. Is determined. Here, if the determination is Yes, the process proceeds to step S303, where LK_IS0.req is output to the 1394Link layer, and then returns to the Act state. If it is determined in step S302 that the QoS class is not CBR, in step S304, LK—DATA. Req is output to the 1394 Link layer, and then the state returns to Act.
- step S292 If it is determined in step S292 that aselVccAalType is AAL0, the flow advances to step S299 to set AAL0 in AAL_Type.
- step S300 the parameter creation process of the AALO Specific field is executed. The details of this process will be described later with reference to the flowchart in FIG. Thereafter, the process proceeds to step S301, and the subsequent processes are executed.
- step S297 if it is determined in step S297 that the value of Count is larger than the value obtained by subtracting 8 from aselVccTransmitSegLen, the process proceeds to step S305 and MR is set to 1. Then, the value of TR_SN is incremented in step S307 (here, the value of aselVccTransmitSegLen is set. In step S307, the QoS class is set to CBR in step S308). If YES is determined here, the process proceeds to step S309, and LK_IS0.req is output to the 1394 Link layer. If the determination is made, in step S310, LK_DATA.req is output to the 1394 Link layer.
- step S311 to add a value obtained by subtracting 8 from aselVccTransmitSegLen to the current value of ptrSDU '.
- step S312 the value of Count is decremented by the value obtained by subtracting 8 from aselVccTransmitSegLen. Then, return to step S297, Subsequent processes are repeatedly executed.
- step S297A If it is determined in step S297A that More is not "Not Used” or "End of PDU", the process proceeds to step S305, and the subsequent processing is performed.
- FIG. 38 shows the process of FIG. 6 in which ASEL outputs LK-DATA.req to the 1394Link layer when MASEL_DATA.Req is received from ASEL layer management.
- MASEL_DATA.Req is received from ASEL layer management.
- the MASEL_DATA. Req includes ASEL-UNI ID, VPI / VCI Value, MNG-ID, AAL-ID (SDU), AA-LP, AAL-CI, and AAL-ES.
- step S322 it is determined whether the corresponding aselVccVpi and aselVccVci exist. If aselVccVpi and aselVccVci exist, the process advances to step S323 to determine whether Up is set in aselVccStatus. When the determination of Yes is made in step S323, the process proceeds to step S324, where the value of aselVccVpi is set to the VPI Value of the ASEL header, and the value of asel VccVci is set to the value of VCI Value. . In step S325, the value of aselVccQosType is set in the QoS Class. In step S326, the process of creating the parameters of the primitive of LK_DATA.req (see FIG. 41 for details of this process) Will be described later).
- step S327 TR_SN is set to SN, and in step S328, 1 is set to Ml. Further, in step S329, the value of the MNG-ID in MASEL_DATA.req is set to the MNG-ID. In step S330, AAL0 is set to AAL Type. It is.
- step S331 a process of creating parameters of the AAL O Specific field (the details of this process will be described later with reference to FIG. 43) is executed.
- step S332 a value obtained by adding 8 to the length of AAL-SDU is set to Data Length.
- step S333 LK—DATA.req is output to the 1394 Link layer, and then the state returns to Act.
- step S322 when it is determined that aselVccVpi and aselVccVci are False, no particular processing is performed, and the state returns to the Act state. The same applies when it is determined in step S323 that Up is not set in aselVccStatus.
- Fig. 39 shows ASEL-CMP transfer processing performed in an arbitrary status.
- 0 is set in the QoS class in step S 352.
- the value of aselLayer 1 394 Bus lndex is set in 1 394 Bus Index, and in step S 354, 0 is also set in the VPI Value and VCI Value of the ASEL header. , Are set respectively.
- step S355 it is determined whether aselLayerOprMode is User side or Network side.
- the process proceeds to step S356, and aselLayerNetSideNodeSelf Id is set as the Destination Self ID.
- Step S 3 5 5 If it is determined that aselLayerOprMode is Network side, go to step S 3 5 7 ion 561 0 is set to & 5611 ⁇ 61] 36 10
- step S358 Transaction Code is set to 1, and Retry Code is set to 1 in step S359.
- step S360 the value of AselVccOprSpeed is set in Speed, and in step S366, TR_SN is set in SN.
- step S362 Ml is further set to 1, and in step S363, MNG-ID is set to 0.
- step S364 AAL0 is set to AAL_Type.
- step S365 MR is set to 0, in step S366, LP is set to 0, in step S366, CI is set to 0, in step S368, EI is set to 0, and in step S366, EI is set to 0.
- E & -ID is set to 0, respectively.
- step S370 a value obtained by adding 8 to the length of ASE CMP is set to Data Length.
- step S371, LKJ) ATA.req is output to the 1394Link layer and returns to the original state.
- FIG. 40 shows details of the parameter creation process of the LK_IS0.req primitive in step S287 of FIG. 36.
- the value of aselLayer 1394 Buslndex is set to 1394 Bus Index.
- the value of the lower 6 bits of aselVccIsoChannel is set to Isochro nous Channel number.
- the value of the upper two bits of ase IVccIsoChannel is set in the Tag value.
- the value of aselVccOprSpeed is set to Spped.
- FIG. 41 shows steps S 288 in FIG. 36 and step S 3 88 in FIG. It shows the details of the parameter creation process of the LK_DATA.req primitive in 26.
- step S401 the value of aselLayer 1394 Buslndex is set to 1 394 Bus Index.
- step S402 the value of aselVccAsyncDestld is set in Destination SelflD.
- step S403 the value of aselLayerl 394 DestOf fset is set in Destination of fset.
- a value of 1 is set to the Transaction Code and Retry Code, respectively.
- step S406 the value of aselVccOprSpeed is set in Speed.
- FIG. 42 illustrates details of the parameter creation process of the AAL5 Specific field in step S294 of FIG.
- step S411 the value of AAL-LP is set to LP. This parameter is mapped from the AA LJJNITDATA.req primitive.
- step S412 AAL-CI is set to CI. Again, this parameter is mapped from the AALJJNITDATA.req primitive.
- step S414 it is determined whether ES is No Error.
- the process proceeds to step S 415, where 0 is set to EI, and 0 is set to ER-ID in step S 416.
- step S417 it is determined whether or not the ES is a CPCS CRC error. If the result is Yes, the process proceeds to step S 419, and ER-ID is set to 0 ⁇ 81. Is performed.
- step S420 it is determined whether the ES is a CPCS-SDU Length error. If the determination is Yes, the process proceeds to step S421, and 0x82 is set to the ER-ID. If No is determined in step S420, the process proceeds to step S422, and 0 is set in the ER-ID.
- FIG. 43 shows details of the AALO Specific field parameter creation processing in step S300 in FIG. 36 and step S331 in FIG. 38.
- step S431 MR is set to 0, and in step S432, AAL-LP is set to LP.
- step S433 AAL-CI is set in the CI.
- step S434 it is determined whether ES is No Error. Here, if the determination is Yes, the process proceeds to step S435, where EI is set to 0, and in step S436, ER-ID is set to 0.
- step S434 When the determination of No is made in step S434, the process proceeds to step S437, and 1 is set to EI. Then, in step S438, 0X01 is set in the ER-ID.
- the flow charts in Fig. 44 to Fig. 46 receive the input of LK-DATA.Ind or LK_IS0.Ind from the 1394 Link layer in Fig. 6 and output AA LJJNITDATA.ind in the upper layer, or the ASEL layer. This shows the process of outputting MASE DATA.Ind to the management.
- step S4 51 _08.111 (1 is received from 13941 ⁇ layer. This includes 1394 Bus Index, Source self ID, Destination Self ID, Destination Of fset, Transaction code, Retry code, Data Length, Data (ASEL-PDU), Speed, Packet status are included.
- step S452 a check process of the 1394 Asynchronous header format is performed. Details of this processing will be described later with reference to the flowchart in FIG. Next, the process proceeds to step S4453, and it is determined whether or not Result is 0K. If Result is not 0K, the process proceeds to step S465. If the result is 0K, the process proceeds to step S445 to search for an ASEL-UNI ID using the 1394 Bus Index and Source SelflD.
- step S455 it is determined whether the ASEL-UN ID has been searched. If found, the flow advances to step S456 to check the VP I / VC I Value of the ASEL header. If this value is correct and VPI / VCI is not 0/0, go to step S457, and if this value is correct and VPI / VCI is 0/0, go to step S47. Go to 5. If this value is not correct, go to step S465.
- that the VP I / VCI is 0/0 indicates that the VP I Value is 0 and the VCI Value is also 0.
- step S455 If it is determined in step S455 that the ASEL-UNI ID has not been searched, the flow advances to step S467 to determine whether both VPI / VCI are 0. In step S467, if the determination is Yes, the process proceeds to step S475, and if the determination is No, the process proceeds to step S465.
- step S457 it is determined whether Ml is 0 or not.
- the process proceeds to step S458, and the determination of AAL Type is made.
- the process proceeds to Step S459, and when the AAL Type is Type 5, the process proceeds to Step S479. If AAL Type is another Type, step S 4 6 5 Proceed to.
- step S459 AALO (User data overnight) assembly processing is performed.
- the process proceeds to step S460, and it is determined whether or not Result is 0K. If it is determined to be 0K, the process proceeds to step S461, and a process of adding ASEL_SDU (that is, AAL-SDU) to the reception buffer is executed.
- step S 4 62 the process proceeds to step S 4 62, and a process of creating an AAL0 parameter is executed. Details of this processing will be described later with reference to the flowchart in FIG. Next, the process proceeds to step S463, where AAL-UNIDATA.Ind is output to the upper layer of FIG. This AALJJNIMTA.Ind includes ASEL-UNI ID, VPI / VCI value, AAL-ID (SDU), AAL-LP, AAL-CI, and AA ES. Then, it returns to its original state.
- step S460 If Result is determined to be NG in step S460, the process advances to step S464 to set No error in Rcv_ER_Status. This parameter indicates the error status of the received AA or SDU, and has an independent value for each ASEL-VCC. Then, the process proceeds to step S465. If it is determined in step S457 that the value of Ml is not 0, the process proceeds to step S468, where it is determined whether the MNG ID is 0. Here, if the determination is Yes, the process proceeds to step S475. On the other hand, if No is determined, the process proceeds to step S469. In step S469, it is determined whether or not AAL Type is 0. Here, when the determination of No is performed, the process proceeds to step S465. Here, if the determination is Yes, the process proceeds to step S470, and the assembling process of AALO (LM data) is executed. Details of this processing will be described later with reference to the flowchart in FIG.
- step S471 it is determined whether Result is 0K. If it is NG, the process proceeds to step S464, and if it is 0K, the process proceeds to step S472.
- step S472 a process of adding ASEL-SDU (that is, AA or SDU) to the reception buffer is executed. Further, in step S4753, a process of creating an AAL0 parameter is executed. Details of this processing will be described later with reference to the flowchart of FIG.
- MASE MTA.Ind is output to the ASEL layer management of FIG.
- This MASEL_DATA.Ind includes SEL-UNI ID, VPI / VCI value, AAL-ID (SDU), AAL-LP, AAL-CI, and AAL-ES. After that, it returns to the original state.
- step S475 AALO (LM data) assembling processing is executed. Details of this processing will be described later with reference to the flowchart of FIG. Next, the process proceeds to step S476, where it is determined whether or not Result is 0K. If it is NG, the process proceeds to step S465.
- step S476 it is determined whether or not Result is 0K. If it is NG, the process proceeds to step S465.
- step S477 execute processing for adding ASEL-SDU (that is, ASEL_CMP) to the reception buffer.
- ASEL_CMP ASEL-SDU
- step S479 AAL5 assembling processing is executed. The details of this processing will be described later with reference to the flowchart of FIG. Next, the process proceeds to step S480, and it is determined whether or not Result is 0K. If it is 0K, proceed to step S 4 81 and receive A process is performed to add ASEL-SDU to the buffer (ie, AAI ⁇ SDU during assembly). Next, in step S 482, it is determined whether MR is 0 or 1. If MR is 0, the flow advances to step S 483 to execute processing for creating an AAL5 parameter. The details of this processing will be described later with reference to the flowchart in FIG. Next, in step S484, AA UNIDATA.Ind is output to the Upper Layer in FIG.
- This AAL_UNIDATA includes ASEL-U NI ID, VPI / VCI value, AAL-ID (SDU), AAL-LP, AAL-CI, AAL-UU, and AAL-ES. After that, it returns to the original state.
- step S482 If it is determined in step S482 that the value of MR is 1, the processing in steps S483 and S484 is skipped.
- step S480 determines whether the value of MR is 0 or 1. If it is determined in step S485 that MR is 1, the process proceeds to step S468. If it is determined that MR is 0, the process proceeds to step S4866, and 0 is set to Rev—ER_Flag. This parameter indicates that the received AAL-SDU contains some error, and has an independent value for each ASEL-VCC.
- step S487A a value obtained by incrementing the SN value by 1 is set in Next_Rcv_SN.
- This parameter indicates the next expected SN value on the receiving side, is incremented by modulo 128, and has an independent value for each ASEL-VCC.
- step S465 proceed to step S465 to execute processing for discarding the ASEL-PDU. Is done.
- step S466 OK is set in Result, and then the state returns to the original state.
- LK_IS0.Ind includes 1394 Bus Index, Isochronus Channel number, Tag value, Data Length, Data (ASEL-PDU), Speed, Packet status, and the like.
- step S 489 a check process is performed for the 139 Isochronous header format. The details of this process will be described later with reference to the flowchart of FIG. Next, proceeding to step S490, it is determined whether or not Result is 0K. If it is NG, the process proceeds to step S465, and the subsequent processing is executed.
- step S491 a search process of ASEL-UNI ID using 1394 Bus Index, Isochronous Channel number, and Tag value is executed.
- step S492 it is determined whether an ASE or UNI ID has been retrieved. If found, the flow advances to step S493 to check the VPI / VCI value of the ASEL header. If this value is correct, the flow advances to step S457 to execute the subsequent processing.
- Step S492 If it is determined in Step S492 that the ASE or UNI ID has not been searched, or if it is determined in Step S493 that the value of the VPI / VCI value is incorrect, the process proceeds to Step S465. Subsequent processing is executed.
- FIG. 47 The more detailed processing of the subroutine shown in the processing of FIG.
- FIG. 47 shows details of the check process of the 1394 Asynchronous header format in step S452 of FIG. 44.
- step S501 it is determined whether a 1394 header CRC error has occurred. If no error has occurred, the flow advances to step S502, and it is determined whether the value of Destination Offset is equal to the value of aselLayer 1 394 Dest0ffset. If the two values are equal, the process advances to step S503 to determine whether the Transaction Code is 1. If this value is 1, the process proceeds to step S504, and it is determined whether the Retry Code is 1. If this value is 1, the process further proceeds to step S505, and it is determined whether or not the packet statistics is F0RMAT_ERR0il. Here, when the determination of No is performed, the process proceeds to step S506.
- step S501 It is determined in step S501 that an error has occurred, or it is determined in step S502 that the Destination Offset is not equal to aselLayer 1 394 Dest0ffset, or step S In 503, it is determined that the value of the transaction code is not 1, in step S504, it is determined that the retry code is not 1, or in step S505, the packet status is When it is determined that the value is F0RMAT_EIiR0R, the process proceeds to step S515, and NG is set in Result.
- step S506 it is determined whether or not the Packet status is BROADCAST. Here, if the determination of Yes is made, the process proceeds to step S516, and 0K is set to Result.
- step S506 Proceeding to 507, it is determined whether the Packet status is DATA_CRC_ERROR.
- the process proceeds to step S508, and 0K is set to Resist.
- step S509 Acknowledge is set to 1 (the state is set to ack_complete).
- step S510 RELEASE is set in Bus Occupancy Control.
- step S511 the value of aselVccOprSpeed is set in Speed.
- step S512 LK—DATA. Resp is output to the 1394 Link layer in FIG. The LK_DATA. Resp includes 1394 Bus Index, Acknowledge, Bus Occupancy Control, and Speed.
- step S507 if it is determined in step S507 that the Packet status is DATA-CRC-ERROR, the process proceeds to step S513, and a process of discarding the Acknowledgment packet is executed. Further, in step S514, 0XD is set to the acknowledge edge (ack_data-error is set). Next, the process proceeds to step S515, and NG is set in Result.
- FIG. 48 shows details of the check processing of the 1394 Isochronous header format in step S489 of FIG. 44.
- step S 521 it is determined whether an error has occurred in the 1394 header CRC. If no error has occurred, the process advances to step S522 to determine whether or not DATA_CRC_ERR0R is set in Packet status.
- step S523 it is determined whether or not F0RMAT_ERR0R is set in Packet status.
- 0K is set to Result.
- step S522 determines whether an error has occurred in the header CRC. If it is determined in step S522 that DATA_CRC_ERROR is set in the Packet status. Otherwise, or if it is determined in step S523 that F0RMAT_ERROR is set for the Packet status, the process proceeds to step S525, and NG is set for Result.
- FIG. 49 shows the details of the AAL 5 assembling process in step S479 of FIG.
- step S5401 it is determined whether Rcv_ER_Flag is 0 or 1. If it is determined that Rev—ER_Flag is 1, the process proceeds to step S5552, and NG is set in Result.
- step S5401 If it is determined in step S5401 that Rcv_ER-Flag is 0, the process proceeds to step S542 and it is determined whether EI is 1. If EI is not 1, the flow advances to step S4443 to determine whether aselVccReceiveSeqUse is Use. If aselVcc ReceiveSeqUse is determined to be Use, step S 5
- step S544 the process proceeds to step S545, where Next_Rcv—SN is incremented, and
- step S444 If it is determined in step S444 that aselVccReceiveSeqUse is not Use, the processing in step S544 and step S545 is skipped, and the flow advances to step S546.
- step S546 a value obtained by subtracting 8 from Data Length is added to Sum_AA or SDU_Len. This parameter indicates the length of the assembled AA or SDU being received, and is independent for each ASEL-VCC. Have.
- step S 547 it is determined whether or not aselAai 5 Coim & eceiveMaxSduSize is smaller than Sum—AAL_SDU_Len.
- N 0 0K is set to Result in step S548.
- step S545 the process proceeds to step S549, and 1 is set to Rcv_ER_Flag.
- step S550 a process of discarding the AA or SDU being assembled is performed.
- step S551 NG is set in Result.
- step S545 If it is determined in step S545 that SN is not equal to Next-Rcv_SN, the process proceeds to step S555, and & AL_Sii Length is set to AAL-S DU Length Error.
- step S556 it is determined whether or not aselAal5ConnErSduDel iver is All low. If it is All low, the process proceeds to step S557 to execute processing for storing the NextJLcv_SN and the SN value in the received ASE L-PDU in the SN error list.
- step S557 Next—RCV_SN is set to the value obtained by adding 1 to SN. Thereafter, the process proceeds to step S546, and the subsequent processes are executed.
- step S556 When it is determined in step S556 that aselAal5ConnErSduDeliver is not All low, the process proceeds to step S555, and 1 is set to ilcv_EiLFlag.
- step S560 a process of discarding the AAL-SDU being assembled is executed. Then, in step S5661, NG is set to Result.
- step S554 If it is determined in step S554 that EI is 1, the process proceeds to step S553, and the ER-ID is a CPCS-SDU Length error. , Or a CPCS CRC error. In the former case, the process proceeds to step S555, and the subsequent processes are executed. In the latter case, the process proceeds to step S555 and AAL-SDURC Error is set in Rcv_ER_Status. Then, the process proceeds to step S556, and the subsequent processing is executed.
- FIG. 50 shows details of the assembling process of AAL 0 (User data overnight) in step S 459 of FIG. 45.
- step S581 it is determined whether EI is 1. If EI is not 1, the flow advances to step S582 to determine whether or not aselVccReceiveSeqUse is Use. If aseVccReceiveSeqllse is Use, the process advances to step S583 to determine whether SN is equal to Next_Rcv_SN. Here, if the determination of Yes is made, the process proceeds to step S584, and the value of Next_Rcv_SN is incremented.
- step S582 If it is determined in step S582 that aselVccfleceiveSeqUse is not Use, the processing of steps S583 and S584 is skipped, and the flow proceeds to step S585.
- step S585 a value obtained by subtracting 8 from Data Length is set in SDU_Len of Sum_AA.
- step S586 it is determined whether Sum_AAL-SDU_Len is greater than 48.
- the process proceeds to step S587, and 0K is set to Result.
- step S588 the process proceeds to step S588 to discard the AAL-SDU being assembled.
- step S589 the process proceeds to step S589, and NG is set in Result.
- step S583 the value of SN is not equal to the value of Next Rev SN. If it is determined that it is, the process proceeds to step S595, and Nextjlcv—SN is set to a value obtained by incrementing the value of SN by 1. Next, the process proceeds to step S585, and the subsequent processing is executed.
- step S581 If it is determined in step S581 that EI is 1, the process proceeds to step S590, and it is determined whether the ER-ID is a CPCS-SDU Length Error or a CPCS CRC error. Is done. In the former case, the process proceeds to step S591, and AAL-SDU Length Error is set in Hcv_EILStatus. Next, the process proceeds to step S593, and it is determined whether or not aselAal OConnEr SduDeliver is Allow. If it is “Allow”, the process proceeds to step S 594, and the process of saving the Next_Rcv_SN and the SN value in the header to the received ASEL-PDU in the SN error list is executed.
- step S595 the process proceeds to step S595, and the subsequent processing is executed.
- step S592 the process proceeds to step S592, and AAL-SDU CRC Error is set in Rcv_ER_Status. Thereafter, the process proceeds to step S593.
- step S 593 If it is determined in step S 593 that aselAal 0 ConnErSduDeiiver is not “Allow”, the process proceeds to step S 596, and a process of discarding the AA or SDU being assembled is executed. Further, in step S597, NG is set to Result.
- FIG. 51 shows details of the AALO (LM data) assembling process in step S470 and step S475 in FIG.
- step S611 it is determined whether or not EI is 1. If EI is not 1, the process proceeds to step S612, and it is determined whether or not aselVccReceiveSeqUse is Use. If aselVccReceiveSeqlise is Use, proceed to step S 6 13, where SN subtracts 1 from Next—Rcv_SN It is determined whether or not it is equal to the calculated value. If both are determined to be equal, the process proceeds to step S614, and a value obtained by subtracting 8 from Data Length is set to Sum-AA or SDU_Len.
- step S615 it is determined whether SunU ⁇ -SDLLEN is greater than 48.
- the process proceeds to step S616, and 0K is set to Result.
- the process proceeds to step S616, and the process of discarding the AA or SDU being assembled is executed.
- the process proceeds to step S618, and NG is set to the Result.
- step S612 If it is determined in step S612 that aselVccReceiveSeqUse is not Use, the process proceeds to step S616, and the subsequent processing is executed.
- step S613 If it is determined in step S613 that SN is not equal to the value obtained by subtracting 1 from Next_Rcv_SN, the process proceeds to step S623A, where Next_Rcv_SN is set to a value obtained by incrementing the value of SN by 1. You. Thereafter, the process proceeds to step S614, and the subsequent processes are executed.
- step S611 If it is determined in step S611 that EI is 1, the process proceeds to step S619, and it is determined whether the ER-ID is a CPCS-SDU Length error or a CPCS CRC error. . If the former is determined, the process proceeds to step S620, and AA or SDU Length Error is set in Rev. ER_Status. Next, the process proceeds to step S622, and it is determined whether or not aselAalOConnErSduDeliver is All low. If it is determined to be All low, the process proceeds to step S6203, and a process of storing the Next—RCV_SN and the SN value in the received ASEL-PDU in the SN error list is executed. .
- step S623A Is executed.
- step S621 AAL-SDU CRC Error is set in Rcv_ER_Status. Thereafter, the process proceeds to step S622.
- step S622 If it is determined in step S622 that aselAal0ConnErSduDeliver is not "Allow”, the process proceeds to step S624, and processing for discarding the AA or SDU being assembled is executed. Then, in step S625, NG is set to Result.
- FIG. 52 shows the details of the processing for creating the AAL5 parameter overnight in step S483 of FIG.
- step S641 LP is set in AAL-LP. This parameter is mapped to the AAL5 specific field of the ASEL-PDU header.
- step S642 the CI is set to the AA CI. This parameter is also mapped to the AAL5 specific field of the PDU header of the ASE.
- step S643 Rcv_ER_Status is set in AAL-ES. Further, in step S644, CPA-UU is set to AA or UU.
- FIG. 53 shows the details of the process of creating the AAL0 parameter overnight in steps S4 62 and S473 of FIG.
- step S651 LP is set in AAL-LP. This parameter is mapped to the AALO specific field of the ASEL-PDU header.
- step S652 CI is set in AAL-CI. This parameter is also mapped in the AAL0 specific field of the ASEL-PDU header.
- step S6553 Rcv_ER_Status is set in the AA / ES.
- ATM terminals 1 and 1 When communication with terminals 4, 22, and 23 is performed using IP / ATM as the standard protocol as in the conventional case, the end-to-end U (User) plane and C (Control) plane protocol are used.
- the protocol stack is laid out as shown in FIGS. 54 and 55, respectively.
- the U-plane protocol of ATM terminal 1 is composed of a PHY (physical) layer, an ATM layer, an AAL5 layer, an IP / ATM layer, and an IP layer.
- the U-Brain protocol consists of a PHY layer and an ATM layer.
- the U-plane protocol stack of the ATM / 1 394 repeaters 3 and 21 consists of the PHY layer, ATM layer and AAL 5 layer on the ATM network side, and the 1 394 PHY layer and 1 394LINK on the 1394 terminal side. Layer and ASEL layer 31.
- the U-brain protocol stack of the 1394 terminals 4, 22, and 23 is composed of the 1394PHY layer, the 1394LINK layer, the 5layer 32, the IP / ATM layer, and the IP layer.
- AAL / ATM is emulated by ASEL 31 between ATM / 1 394 repeaters 3 and 1 394 terminal 4 and between ATMZ 139 4 repeaters 21 and 1 394 terminals 22 and 23. Since the concept of VPC / VCC exists, handling of U-plane packets can be performed not by IP but by VPI / VCI values. This VPI / VCI is usually included in the disk library table of the AA / PDU, and is not included in the bucket like the interface data. As a result, when the ASEL31 performs routing, it is not necessary to copy the contents of the packet (interface data). Therefore, the load is reduced at the ATM / 1 394 repeaters 3 and 21 and the throughput of the ATM / 1 394 repeaters 3 and 2 1 is reduced. Can be improved.
- the protocol stack of the C plane of ATM terminal 1 is composed of PHY layer, ATM layer, AAL5 layer, SSCF (ITU-T Q.2130) + SSC0P (ITU-TQ . 2 110) layer and the Q.2931 (ITU-TQ. 2931) layer.
- the protocol of the C plane of ATM network 2 has the same configuration as that of ATM terminal 1.
- the protocol stack of the C plane of the ATM / 1 394 repeaters 3 and 21 has the same configuration as the case where the ATM network side is the ATM terminal 1 and the ATM network 2.
- the 1394 terminal has the same configuration as the protocol stack of the 1394 terminals 4, 22, and 23, and the 1394 PHY layer, the 1394 LINK layer, and the ASEL layer 33 ( (Corresponding to ASEL layer 31 in Fig. 54).
- 139 4 Terminal 4, 2, 2 and 23 C-plane protocol stacks are 1394 PHY layer, 1394 LIM layer, ASE L layer 34 (corresponding to ASEL layer 32 in Fig. 54), SSCF It consists of + SSC0P layer and Q.2931 layer.
- ASEL provides multi-point, multi-point
- the services provided by various connection-based applications using connections are based on the characteristics of the IEEE1394 serial bus: low cost, ease of cape ringing, and shared 'media (media sharing network: 1). It can be provided as it is on an infrastructure that has the element of enabling effective use of media resources by means of a cable (transmission medium that connects various terminals to communicate).
- the ASEL-CME of the ATM / 1 3 9 4 repeater 2 1 Upon receiving the WakeUp (Fig. 15), the ASEL-CME of the ATM / 1 3 9 4 repeater 2 1 assigns a new ASEL-UNI ID, and the 1 3 9 4 Bus Index, Node Unique ID and Se Register in association with lf ID. And ActReq (Fig. 16) is sent to the ASEL-CME of each 1394 terminal, requesting activation of ASEL-CME of each User side, and registering Node Unique ID and Self ID of Network side. Request.
- the ASEL-CME of each 1394 terminal performs registration in response to this request, transits to Active status, and sends ActAck (Fig. 17) to the ASEL-CME of the ATM / 1 394 repeater 21. Send, and both sides become Active status.
- ASEL-CME issues MASEL_Act.Ind primitive to ASEL layer management.
- the ASEL layer management recognizes the activated ASE UNI ID and the 1394 Bus Index in which the ASEL-UNI exists. Therefore, since the above-described processing is performed with all connected 1394 terminals, the ATM / 1 394 repeater 21 can determine which 13 9 4 It can recognize whether it is connected to the serial bus.
- the final exchange of data between 1 3 9 4 terminal 2 2-1 and ATM terminal 1 is data on the U plane as shown in Figure 54.
- the protocol stack of the C-brain shown in Fig. 55 is used.
- VPI / VC I In order to exchange protocols on the C plane, VPI / VC I usually uses two types of VCC using 0/5 and 0/16 for each ASEL-UNI and each AT. Established in advance for each M-UNI.
- ASEL 33 and 34 of ATM / 1 394 repeater 21 and 1394 terminal 22-1 convert data of IEEE 1394 standard into data of ATM (AAL) standard. It has a function to convert data, and a function to convert data from the ATM (AAL) standard to data from the IEEE 1394 standard.
- the signaling protocols 35 and 36 in the ATM / 1 394 repeaters 21 and 1394 terminals 22-1 can use the same protocol as the ATM terminal 1 and ATM network 2.
- These signaling protocols determine the various parameters (VPI / VCI Value, AAL Type, QoS class, Transmit / Receive Bandwidth etc,) of the VCC used in the U-brain in Fig. 54. o
- the ATM / 1394 repeater 21 and 13394 terminal 22-1 have access to the signaling protocol 35, 36 from the application program.
- ConSet.req primitive is issued to MASE for each ASEL-CME due to ASEL layer management.
- the ATM / 1 394 repeater 21 has already recognized that the ATM terminal 1 which is the termination point of the VCC on one side does not exist in the ASE or UNIs that it owns by the signaling protocol. 0
- IsoReq (Fig. 18), which requests the allocation of an isochronous channel that resolves the allocated VPI / VCI, Transmit to ATM / 1 394 repeater 21 where L-CME is installed.
- the DestlDReq ( Figure 20) that requests the value of the destination ID of the Asynchronous bucket that resolves the assigned VP I / VCI is sent to the ATM / 13 that the ASE CME of the Network side implements. 9 4 Transmit to repeater 21.
- ASEL-CME of ATM / 1 3 9 4 repeater 2 1 is 1 3 9 4 terminal
- VCC is established between ATM terminal 1 and 1394 terminal 22-1.
- the ASELs 31 and 32 of the ATM / 1 394 repeaters 21 and 1 394 terminals 2 2-1 transmit data of the IEEE 1394 standard to ATM (AA or other standard). Since it has a function to convert data to data in the ATM (AAL) standard and data to data in the IEEE 1394 standard, it has As the upper layer of ASEL 32 in 2-1, the same protocol (for example, IP / ATM) as the upper layer of AAL5 in ATM terminal 1 can be used.
- the signaling protocol 3 5 for ATM / 1 3 9 4 repeaters 2 1, 1 3 9 4 terminals 2 2-1 and 1 3 9 4 terminals 2 3-1 , 36, MASEL_ConSet.req primitive is issued to each ASEL-CME via ASEL layer management.
- the ATM / 1394 repeater 21 has its own terminals 1339 4 terminal 2 2-1 and 1 394 terminal 2 3-1, which are the termination points of both VCCs. It is present in the containing ASEL-UN Is, but has already recognized that it is a separate 1394 serial bus.
- the ASEL-CME of each user Sends IsoReq (Fig. 18) requesting the assignment of an isochronous channel to resolve the assigned VPI / VCI to the ATM / 1 394 repeater 21 equipped with ASEL-CME on the network side.
- ASEL-CME of ATMZ1394 repeater 21 returns IsoReply (Fig. 19), and specifies the isochronous channel there.
- the isochronous channel numbers can be specified independently.
- the ASEL-CME on each user side sends Dest IDReq (Fig. 20) to the ATM / 1 394 repeater 21 equipped with ASEL-CME on the network side.
- ASEL-CME of ATM / 1 394 repeater 21 returns DestlDRply (FIG. 21).
- the communication path in the IEEE 1394 standard is secured by notifying the self ID of the ATM node 1394 repeater 21 itself, which is the destination node, in the respective 1394 serial path.
- the VCC is opened between the 139 4 terminal 22-1 and the 1 394 terminal 23-1 via the ATM / 1 394 repeater 21.
- the ASEL31 of the ATM / 1 394 repeater 21 converts the data of the IEEE 1394 standard into data of the ATM (AAL) standard.
- the data exchanged between the 1394 terminal 22-1 and the 1394 terminal 23-1 is relayed by using the function to convert the IEEE 1394 standard data into the IEEE 1394 standard data.
- the signaling protocols 35 and 36 of the ATM / 1 394 repeater 2 1, 1 394 terminal 2 2-1 and 1 394 terminal 2 2-2 use a common protocol. These signaling protocols determine the various parameters (VPI / VCI Value, AAL Type, QoS class, Transmit / Receive Bandwidth etc.) of the VCC used in the U-plane of Fig. 54. .
- the signaling ports 3 5 and 3 6 must be connected to the 1 3 9 4 terminal 2 2-1 and 1 3 9 4 terminal 2 2-2 via the ATM / 13 9 4 repeater 21. It is exchanged between.
- the signaling protocol 3 5 for ATM / 1 394 repeaters 21, 1 394 terminals 2 2-1 and 1 394 terminals 2 2-2 is used.
- 36 application programs issue ASEL-ConSet.req primitives to each ASEL-CME via ASEL layer management.
- the ATM / 1394 repeater 21 has its own terminal 1394 terminal 22-1 and 1394 terminal 22-2, which are the termination points of both VCCs. It already exists in the ASEL-UNIs that it is housed in and has already recognized that it is the same 1394 serial path. Therefore, since there is no need to relay the data on this VCC, the terminals 1 3 9 4 2 2 1 and 1 2
- Terminal 2 Open VCC that can directly exchange data with 2 2-2.
- the ASEL-CME on each user side sends IsoReq (Fig. 18) to the ATM / 1 394 repeater 21 equipped with the ASEL-CME on the network side, and
- the ASE or CME of the ATM / 1 394 repeater 21 returns Iso & eply (Fig. 19), and specifies the isochronous channel there.
- the same Isochronous channel number is specified for each.
- by specifying the Tag Value corresponding to the upper 2 bits of the assigned Isochronous channel to (0, 1), it can be used to indicate that the channel is received only by ASEL32 on the User side. In this way, 1 3 9 4 terminal 2
- An isochronous channel used between 2 _ 1 and 13394 terminal 22-2 is allocated, and a communication path in the IEEE1394 standard that can directly exchange data is secured.
- the ASEL-CME on each user side uses Dest IDReq (Fig. 20) to transfer the ATM /
- the direct data Communication channels in the IEEE 1394 standard that can be exchanged are secured.
- VCC is established between 3 9 4 terminal 2 2—1 and 1 3 9 4 terminal 2 2—2. It is. At this VCC, the ASEL 31 of the ATM / 1 394 repeater 21 is used for data exchanged between the 1394 terminal 2 2-1 and the 1394 terminal 2 3 -1. Does not know.
- connection control primitives (MASEL_ConSet.req, MASEL-ConRec.req, MASEL-ConSet.conf, MASEL.ConRel.req, MASEL-Co) are included in the ASEL layer management primitives. conf), these primitives have been published via ASEL layer management.
- ASEL layer management primitives. conf these primitives have been published via ASEL layer management.
- an implementation that is issued directly from the application program of the signaling protocol 35, 36 or issued directly from the signaling protocol 35, 36 itself is used.
- one ATM terminal is connected to the ATM network.
- a plurality of ATM terminals are connected to the ATM network, and each of the 1394 terminals is desirably connected to the ATM network. It is also possible to receive the provision of data.
- Industrial Applicability According to the communication control device and the communication control method according to the present invention, the data of the second transmission standard received via the repeater is converted into the data of the first transmission standard. However, since the predetermined data of the first transmission standard is converted to the data of the second transmission standard, the existing signaling protocol used in the first transmission standard can be applied. In addition, it is possible to reduce the number of system development steps and improve the reliability.
- the data of the first transmission standard transmitted from the first terminal and the second transmission data transmitted from the second terminal is processed using the same signaling protocol as the signaling protocol used in the first terminal. , Reliability can be improved
- the repeater converts the data of the first transmission standard transmitted from the first terminal into the data of the second transmission standard. And converts the data of the second transmission standard transmitted from the second terminal to the data of the first transmission standard, and the second terminal transmits the data via the repeater.
- the data of the second transmission standard is converted to data of the first transmission standard, and a predetermined data of the first transmission standard is converted to data of the second transmission standard. Routing can be performed only with connection information in the first transmission standard, so that the load on the repeater can be reduced.
- the conventional signaling protocol used in the first transmission standard can be applied between the repeater and the second terminal, thereby reducing system development man-hours and improving reliability. Is possible.
- a communication path for transferring data of a transmission standard exchanged between a terminal and another terminal between the repeater and the terminal is determined in advance by a predetermined control command. Since the setting is made using a network, the burden on the repeater can be reduced. In addition, data can be transferred substantially without going through a repeater.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Communication Control (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP97914616A EP0841791A4 (en) | 1996-04-04 | 1997-04-04 | TRANSMISSION CONTROL AND METHOD FOR CONTROLLING THE TRANSMISSION |
US08/973,175 US6115392A (en) | 1996-04-04 | 1997-04-04 | Communication control equipment and communication control method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP8/82545 | 1996-04-04 | ||
JP8082545A JPH09275402A (ja) | 1996-04-04 | 1996-04-04 | 通信制御システムおよび通信制御装置並びにデータ送受信装置および通信制御方法 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/572,250 Continuation US6456631B1 (en) | 1996-04-04 | 2000-05-17 | Communication control equipment and communication control method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1997038513A1 true WO1997038513A1 (fr) | 1997-10-16 |
Family
ID=13777481
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP1997/001178 WO1997038513A1 (fr) | 1996-04-04 | 1997-04-04 | Controleur de communications et procede de controle des communications |
Country Status (5)
Country | Link |
---|---|
US (2) | US6115392A (ja) |
EP (1) | EP0841791A4 (ja) |
JP (1) | JPH09275402A (ja) |
KR (1) | KR19990022287A (ja) |
WO (1) | WO1997038513A1 (ja) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0938218A2 (en) * | 1998-02-24 | 1999-08-25 | Canon Kabushiki Kaisha | Data communication system, data communication method, data communication apparatus and digital interface |
EP0939529A2 (en) * | 1998-02-24 | 1999-09-01 | Canon Kabushiki Kaisha | Data communication system, data communication method, data communication apparatus and digital interface |
US6378000B1 (en) | 1999-04-29 | 2002-04-23 | Mitsubish Electric Research Laboratories, Inc | Address mapping in home entertainment network |
US6496862B1 (en) | 1998-08-25 | 2002-12-17 | Mitsubishi Electric Research Laboratories, Inc. | Remote monitoring and control of devices connected to an IEEE 1394 bus via a gateway device |
US6505255B1 (en) | 1999-04-29 | 2003-01-07 | Mitsubishi Electric Information Technology Center America, Inc. (Ita) | Method for formatting and routing data between an external network and an internal network |
US6523064B1 (en) | 1999-04-29 | 2003-02-18 | Mitsubishi Electric Research Laboratories, Inc | Network gateway for collecting geographic data information |
US6633547B1 (en) | 1999-04-29 | 2003-10-14 | Mitsubishi Electric Research Laboratories, Inc. | Command and control transfer |
US6667987B1 (en) | 1998-10-15 | 2003-12-23 | Samsung Electronics Co., Ltd. | Method of extending channels for IEEE-1394 serial bus |
US6678769B1 (en) | 1998-02-24 | 2004-01-13 | Canon Kabushiki Kaisha | Control apparatus and method for managing a logical connection between source and destination nodes |
WO2004107666A1 (en) * | 2003-06-02 | 2004-12-09 | Utstarcom Korea Limited | Aal0 cell format of an atm protocol for communicating voice traffic in a cdma system |
US7002964B1 (en) | 1998-02-24 | 2006-02-21 | Canon Kabushiki Kaisha | Communication system, method for a communication system and controller for a communication system |
CN100380890C (zh) * | 1998-08-29 | 2008-04-09 | 三星电子株式会社 | 将上协议层匹配到高速串行总线的数据传送方法 |
Families Citing this family (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH09275402A (ja) * | 1996-04-04 | 1997-10-21 | Sony Corp | 通信制御システムおよび通信制御装置並びにデータ送受信装置および通信制御方法 |
US6751221B1 (en) * | 1996-10-04 | 2004-06-15 | Kabushiki Kaisha Toshiba | Data transmitting node and network inter-connection node suitable for home network environment |
JP3365262B2 (ja) * | 1997-07-14 | 2003-01-08 | 松下電器産業株式会社 | 通信プロトコル処理装置 |
JP4168302B2 (ja) * | 1998-05-12 | 2008-10-22 | ソニー株式会社 | 情報受信装置および方法、並びに記録媒体 |
EP1006696A1 (en) * | 1998-05-29 | 2000-06-07 | Sony Corporation | Method and apparatus for relaying data, communication system, and recording medium |
KR100298979B1 (ko) * | 1998-06-12 | 2001-09-06 | 윤종용 | 아이 트리플 이 1394 시리얼 버스 토폴로지 최적화방법 |
JP2004500731A (ja) | 1998-06-18 | 2004-01-08 | ソニー エレクトロニクス インク | 複数のディスプレイ装置に亘ってビデオ及び/又はグラフィック画像を分割し、スケーリングし、表示する方法及び装置 |
US6593937B2 (en) * | 1998-06-18 | 2003-07-15 | Sony Corporation | Method of and apparatus for handling high bandwidth on-screen-display graphics data over a distributed IEEE 1394 network utilizing an isochronous data transmission format |
US6301662B1 (en) * | 1998-08-21 | 2001-10-09 | Nortel Networks Corporation | Authentication of routing data using variable output length one-way functions |
WO2000011840A2 (en) * | 1998-08-25 | 2000-03-02 | Mitsubishi Electric Corporation | Home gateway |
JP3583657B2 (ja) * | 1998-09-30 | 2004-11-04 | 株式会社東芝 | 中継装置及び通信装置 |
KR100359092B1 (ko) * | 1998-11-18 | 2003-02-19 | 삼성전자 주식회사 | 가변 등시성 데이터 전송방법 및 그 장치 |
KR100335432B1 (ko) | 1998-11-18 | 2002-06-20 | 윤종용 | Ieee 1394 등시성 데이타의 외부 동기 네트워크로의 전송시에 채널 재배열 방법 및 그 장치 |
KR100297818B1 (ko) * | 1998-12-28 | 2001-08-07 | 윤종용 | 외부통신망을이용한아이트리플이1394네트웍간의통신시스템및방법 |
FI107425B (fi) * | 1999-03-16 | 2001-07-31 | Nokia Mobile Phones Ltd | Menetelmä ja järjestelmä multimediaan liittyvän informaation välittämiseksi pakettikytkentäisessä solukkoradioverkossa |
AU4482000A (en) | 1999-04-23 | 2000-11-10 | Sony Electronics Inc. | Method of and apparatus for implementing and sending an asynchronous control mechanism packet |
JP3365340B2 (ja) | 1999-04-28 | 2003-01-08 | 日本電気株式会社 | データ転送システム及びその転送方法 |
GB9921049D0 (en) * | 1999-09-07 | 1999-11-10 | Koninkl Philips Electronics Nv | Clustered networked devices |
JP2001077831A (ja) | 1999-09-08 | 2001-03-23 | Sony Corp | 通信制御装置および方法、通信システム、並びにプログラム格納媒体 |
JP3655510B2 (ja) * | 1999-10-29 | 2005-06-02 | 株式会社東芝 | ネットワーク接続装置、通信装置及びネットワーク接続方法 |
EP1133108A1 (en) | 2000-03-07 | 2001-09-12 | Sony International (Europe) GmbH | Interface link layer device for long delay connections |
US7111163B1 (en) | 2000-07-10 | 2006-09-19 | Alterwan, Inc. | Wide area network using internet with quality of service |
CN1201545C (zh) * | 2000-09-28 | 2005-05-11 | 皇家菲利浦电子有限公司 | 无线网络接口 |
FR2816159B1 (fr) * | 2000-10-30 | 2002-12-06 | Mitsubishi Electric Inf Tech | Methode d'etablissement de lien radio entre un controleur d'acces et une station de base |
EP1346534B1 (en) * | 2000-12-28 | 2012-11-14 | Abb Ab | Method, system architecture and computer software for communication between devices |
FR2832827B1 (fr) * | 2001-11-23 | 2004-10-22 | Canon Kk | Procedes et dispositifs de gestion des transmissions de donnees isochrones sur des supports non dedies |
AU2003235660A1 (en) * | 2002-01-10 | 2003-07-30 | Thomson Licensing S.A. | Telephony device with irda repeater |
US7173937B1 (en) * | 2002-03-27 | 2007-02-06 | Nortel Networks Limited | Intelligent address registration for optical user-network interface |
DE10245528A1 (de) * | 2002-09-30 | 2004-04-15 | OCé PRINTING SYSTEMS GMBH | Zugriff auf Datenobjekte mit Hilfe von den Datenobjekten zugeordneten Netzwerkadressen |
EP1599010A4 (en) * | 2003-02-26 | 2008-11-26 | Nec Corp | PROTOCOL IMPLEMENTATION DEVICE AND METHOD |
US7656880B1 (en) * | 2004-06-09 | 2010-02-02 | Verizon Laboratories Inc. | Prioritized segmentation and reassembly methods and systems |
DE102004062034A1 (de) * | 2004-12-23 | 2006-07-13 | Robert Bosch Gmbh | Repeaterknoten für ein Netzwerk |
WO2007010606A1 (ja) * | 2005-07-21 | 2007-01-25 | Mars Technology Institute Co., Ltd. | 3ステートアドレスを利用するネットワークシステム |
US20070035668A1 (en) * | 2005-08-11 | 2007-02-15 | Sony Corporation | Method of routing an audio/video signal from a television's internal tuner to a remote device |
KR20080069841A (ko) * | 2007-01-24 | 2008-07-29 | 삼성전자주식회사 | 홈 네트워크 통신 시스템 |
JP2009010721A (ja) * | 2007-06-28 | 2009-01-15 | Kyocera Corp | 通信方法および通信システム |
CN101753393B (zh) * | 2008-12-19 | 2011-12-07 | 中国科学院沈阳自动化研究所 | 基于iec61158标准现场总线的通信芯片架构 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06311185A (ja) * | 1993-04-20 | 1994-11-04 | Toshiba Corp | Atm通信システム |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH03123244A (ja) * | 1989-10-06 | 1991-05-27 | Matsushita Electric Ind Co Ltd | 通信装置 |
JPH0732397B2 (ja) * | 1989-10-17 | 1995-04-10 | 松下電器産業株式会社 | データ伝送機能付き電子機器 |
EP0596651A1 (en) * | 1992-11-02 | 1994-05-11 | National Semiconductor Corporation | Network for data communication with isochronous capability |
JP3090827B2 (ja) * | 1993-10-30 | 2000-09-25 | ソニー株式会社 | 送信信号の形成方法、双方向バスシステムの受信方法及び通信システム |
US5640386A (en) * | 1995-06-06 | 1997-06-17 | Globalstar L.P. | Two-system protocol conversion transceiver repeater |
US5742602A (en) * | 1995-07-12 | 1998-04-21 | Compaq Computer Corporation | Adaptive repeater system |
US5745837A (en) * | 1995-08-25 | 1998-04-28 | Terayon Corporation | Apparatus and method for digital data transmission over a CATV system using an ATM transport protocol and SCDMA |
JP3407838B2 (ja) * | 1995-09-05 | 2003-05-19 | ソニー株式会社 | ビデオオンデマンドシステム |
US5784370A (en) * | 1995-12-29 | 1998-07-21 | Cypress Semiconductor Corp. | Method and apparatus for regenerating a control signal at an asynchronous transfer mode (ATM) layer or a physical (PHY) layer |
JPH09275402A (ja) * | 1996-04-04 | 1997-10-21 | Sony Corp | 通信制御システムおよび通信制御装置並びにデータ送受信装置および通信制御方法 |
US5847771A (en) * | 1996-08-14 | 1998-12-08 | Bell Atlantic Network Services, Inc. | Digital entertainment terminal providing multiple digital pictures |
US6014381A (en) * | 1996-09-13 | 2000-01-11 | Sony Corporation | System and method for distributing information throughout an aircraft |
-
1996
- 1996-04-04 JP JP8082545A patent/JPH09275402A/ja active Pending
-
1997
- 1997-04-04 KR KR1019970708766A patent/KR19990022287A/ko not_active Application Discontinuation
- 1997-04-04 EP EP97914616A patent/EP0841791A4/en not_active Withdrawn
- 1997-04-04 US US08/973,175 patent/US6115392A/en not_active Expired - Fee Related
- 1997-04-04 WO PCT/JP1997/001178 patent/WO1997038513A1/ja not_active Application Discontinuation
-
2000
- 2000-05-17 US US09/572,250 patent/US6456631B1/en not_active Expired - Fee Related
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06311185A (ja) * | 1993-04-20 | 1994-11-04 | Toshiba Corp | Atm通信システム |
Non-Patent Citations (3)
Title |
---|
"Wide-Band ISDN and ATM Technology (in Japanese)", Edited by IEICE, Supervised by AOKI et al., 20 February 1995, IEICE, Tokyo, p. 47-63. * |
NIKKEI ELECTRONICS, No. 654, 29 January 1996, Tokyo, p. 113-120. * |
See also references of EP0841791A4 * |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6804250B2 (en) | 1998-02-24 | 2004-10-12 | Canon Kabushiki Kaisha | Data communication system and node, and method of using the system and the node |
EP0939529A2 (en) * | 1998-02-24 | 1999-09-01 | Canon Kabushiki Kaisha | Data communication system, data communication method, data communication apparatus and digital interface |
EP0939529A3 (en) * | 1998-02-24 | 2001-08-01 | Canon Kabushiki Kaisha | Data communication system, data communication method, data communication apparatus and digital interface |
EP0938218A3 (en) * | 1998-02-24 | 2001-08-01 | Canon Kabushiki Kaisha | Data communication system, data communication method, data communication apparatus and digital interface |
EP0938218A2 (en) * | 1998-02-24 | 1999-08-25 | Canon Kabushiki Kaisha | Data communication system, data communication method, data communication apparatus and digital interface |
CN1301471C (zh) * | 1998-02-24 | 2007-02-21 | 佳能株式会社 | 数据通信系统及其方法 |
US7002964B1 (en) | 1998-02-24 | 2006-02-21 | Canon Kabushiki Kaisha | Communication system, method for a communication system and controller for a communication system |
US6678769B1 (en) | 1998-02-24 | 2004-01-13 | Canon Kabushiki Kaisha | Control apparatus and method for managing a logical connection between source and destination nodes |
US6690648B2 (en) | 1998-02-24 | 2004-02-10 | Canon Kabushiki Kaisha | Data communication apparatus, method, and system utilizing reception capability information of a destination node |
US6496862B1 (en) | 1998-08-25 | 2002-12-17 | Mitsubishi Electric Research Laboratories, Inc. | Remote monitoring and control of devices connected to an IEEE 1394 bus via a gateway device |
CN100380890C (zh) * | 1998-08-29 | 2008-04-09 | 三星电子株式会社 | 将上协议层匹配到高速串行总线的数据传送方法 |
US6667987B1 (en) | 1998-10-15 | 2003-12-23 | Samsung Electronics Co., Ltd. | Method of extending channels for IEEE-1394 serial bus |
US6378000B1 (en) | 1999-04-29 | 2002-04-23 | Mitsubish Electric Research Laboratories, Inc | Address mapping in home entertainment network |
US6633547B1 (en) | 1999-04-29 | 2003-10-14 | Mitsubishi Electric Research Laboratories, Inc. | Command and control transfer |
US6523064B1 (en) | 1999-04-29 | 2003-02-18 | Mitsubishi Electric Research Laboratories, Inc | Network gateway for collecting geographic data information |
US6505255B1 (en) | 1999-04-29 | 2003-01-07 | Mitsubishi Electric Information Technology Center America, Inc. (Ita) | Method for formatting and routing data between an external network and an internal network |
WO2004107666A1 (en) * | 2003-06-02 | 2004-12-09 | Utstarcom Korea Limited | Aal0 cell format of an atm protocol for communicating voice traffic in a cdma system |
US7809014B2 (en) | 2003-06-02 | 2010-10-05 | Woo Young Yang | AAL0 cell format of an ATM protocol for communicating voice traffic in a CDMA system |
Also Published As
Publication number | Publication date |
---|---|
JPH09275402A (ja) | 1997-10-21 |
US6115392A (en) | 2000-09-05 |
EP0841791A1 (en) | 1998-05-13 |
EP0841791A4 (en) | 2000-08-16 |
US6456631B1 (en) | 2002-09-24 |
KR19990022287A (ko) | 1999-03-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO1997038513A1 (fr) | Controleur de communications et procede de controle des communications | |
US7385967B2 (en) | Network interconnection apparatus, network node apparatus, and packet transfer method for high speed, large capacity inter-network communication | |
US5867481A (en) | Node device and alarm notification control method for ATM network | |
JP2002522958A (ja) | Atm仮想プライベートネットワーク | |
GB2331199A (en) | ATM/LAN interface | |
US6601127B1 (en) | Communication control apparatus and method, communication system, and program storage medium | |
US8077728B2 (en) | Substitution call control system in a communication network | |
US6125123A (en) | Signaling method, switching system, storage medium and network | |
US6418126B1 (en) | Wireless ATM networks | |
JP3426646B2 (ja) | ネットワークシステム、通信方法及び通信装置 | |
KR100460496B1 (ko) | 에이티엠 교환기 가입자 장치에서 비정상적 제어셀 복구장치 및 방법 | |
JPH07264207A (ja) | Atm交換網へのデータ端末接続方法 | |
KR19990087607A (ko) | Atm 네트워크를 통한 atm 셀의 전송 방법 | |
JPH1168782A (ja) | シグナリング処理装置およびその方法 | |
KR100191836B1 (ko) | 비동기전송모드 통신방식에서 브릿지 포맷 데이터전송방법 | |
JP3445532B2 (ja) | Atm通信システム | |
JP3593640B2 (ja) | Atm交換機及びatmセル中継伝送方法 | |
Armitage | gNET: An ATM LAN Signalling Protocol," | |
JP2820067B2 (ja) | Atm装置 | |
JP3546814B2 (ja) | Atm装置およびatm通信網 | |
JPH09181726A (ja) | Atmネットワークで接続を結合する方法及びシステム | |
JP3557199B2 (ja) | Atm通信システム及びatm通信方法 | |
Kasera et al. | AAL2 Signalling: A White Paper | |
JPH05167601A (ja) | 制御信号転送方式 | |
JPH11187044A (ja) | メッセージ組立/分解装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): JP KR US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): DE FR GB |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1997914616 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 08973175 Country of ref document: US Ref document number: 1019970708766 Country of ref document: KR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWP | Wipo information: published in national office |
Ref document number: 1997914616 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1019970708766 Country of ref document: KR |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1997914616 Country of ref document: EP |
|
WWR | Wipo information: refused in national office |
Ref document number: 1019970708766 Country of ref document: KR |