WO2005107184A1

WO2005107184A1 - Communication system, ip line multiplexing device management entity, and ip line multiplexing device function entity

Info

Publication number: WO2005107184A1
Application number: PCT/JP2004/006132
Authority: WO
Inventors: Kentaro Tanaka
Original assignee: Mitsubishi Denki Kabushiki Kaisha
Priority date: 2004-04-28
Filing date: 2004-04-28
Publication date: 2005-11-10
Also published as: JP4425912B2; JPWO2005107184A1

Abstract

An ME (4) creates a multiplex link management table defining channel information according to IP telephones (7a-1, 7a-2, 7b-1, 7b-2, 7c-1, 7c-2) notified from multiplex link information based on FE (1a to 1c) and the SIP server (3) and the IP address and port number of the VoIP gateways (8a, 8b, 8c), and transmits it to the FE (1a to 1c). According to the multiplex link management table received from the ME (4), the FE (1a to 1c) create a short packet from the local IP packet transmitted from the IP telephones (7a-1, 7a-2, 7b-1, 7b-2, 7c-1, 7c-2) or the VoIP gateways (8a, 8b, 8c), multiplex the short packet generated, isolate a bearer IP packet received from the IP service network (5) according to the multiplex link management table, and create a local IP packet to the IP telephones (7a-1, 7a-2, 7b-1, 7b-2, 7c-1, 7c-2) or the VoIP gateways (8a, 8b, 8c).

Description

Communication system, IP line multiplexing device management entity, and IP line multiplexing device functional entity

Technical field '

The present invention describes a short bucket inside an IP (Internet Protocol) bucket.

The present invention relates to a communication system including a communication device having a duplication / separation function.

Voice over IP (Vo IP: Voice Over IP)

The present invention relates to a communication system to which a communication system in which a plurality of short buckets are multiplexed into one IP bucket is applied.

Background art

The spread of the Internet since the 1990s has been remarkable. The basis of the Internet is a BestEffort type in which the entire network treats all buckets fairly, that is, a communication service that does not guarantee the quality of service. However, with the spread of the Internet, business using the Internet has been developed, and high-quality services and real-time applications such as voice and video have been demanded.

One of the systems that requires real-time applications such as voice and video using the Internet is VoIP. VoIP is a technology for transmitting and receiving voice data using a TCP / IP network such as a mobile phone and an intranet.Non-Patent Document 1 states that voice and video communications are required for IP-based networks including the Internet. Protocol is disclosed.

In addition, various technologies related to a communication device of a communication system that handles audio and images have been conventionally considered. For example, Non-Patent Literature 2 discloses that RTP / UDP (User Datagram Protocol) / A technique related to an IP line multiplexer (IPCME) that multiplexes a plurality of short buckets on the red of the P payload and transmits the short bucket is disclosed.

Further, Patent Document 1 discloses a technique related to a communication device that shortens the bucket length and retransmits the transmitted packet when the communication device on the receiving side cannot correctly receive the transmitted packet.

Patent Document 2 discloses a technology related to a communication device that transfers image data and audio data by performing multiplex Z separation, compression / decompression, and data transfer in response to dynamic changes in transmission format information. ing. ·

Patent Document 1

JP 2001-086190

Patent Document 2

JP 11-225168 A

Non-patent document 1.

I TU-T H. 323

Non-patent document 2

I TU-T G. 769

However, since the communication devices described in Patent Documents 1 and 2 are communication devices arranged at the end of a network, when used in a network accommodating a large number of voice channels, such as an international line, the communication device of the communication protocol Due to the complexity and poor response, there was a problem that the performance required for IP communication equipment could not be satisfied.

Also, when high-efficiency multiplexing transmission is controlled and operated by the signaling method described in Non-Patent Document 1, as in the IP CME described in Non-Patent Document 2, complicated procedures are required, and the response becomes poor. Therefore, there was a problem that it was not realistic.

The present invention has been made in view of the above, and has been made in consideration of the above-mentioned problems. It is a first object of the present invention to obtain a communication system for performing mutual communication according to the above, an IP line multiplexing device management entity, and an IP line multiplexing device function entity. A second object is to provide a communication system in which an IP terminal end user can use a voice line seamlessly without recognizing and recognizing multiplexed Z separation of packets, an IP line multiplexer management entity, and an IP line multiplexer. The goal is to obtain a circuit multiplexer function entity. .

A third object is a communication system capable of operating a voice line efficiently and at low cost by multiplexing packets, an IP line multiplexer management entity, and an IP line multiplexer. To get the function entity. Disclosure of the invention

In the present invention, when IP terminal devices connected to a network via a router perform mutual communication under the control of a SIP server, a local IP bucket from the IP terminal device to an opposite IP terminal device is provided. A multiplexed IP packet multiplexer generates a bearer IP packet, and separates a bearer IP packet from the opposite IP terminal device to generate a local IP bucket. In a communication system including an IP line multiplexing device management entity that controls the IP line multiplexing device function entity, the IP line multiplexing device management entity includes multiplexed link information based on the IP line multiplexing device function entity. Based on the IP address and port number of the IP terminal device notified from the SIP server, Generating a multiplex link management table that defines channel information associated with the packet number, and transmitting the generated multiplex link management table to the IP line multiplexer functional entity; Generating a short packet from the local IP packet based on the multiplex link management table, multiplexing the generated short packet to generate the bearer IP bucket, and transmitting the generated packet to the network. Transmitting, and based on the multi-link management table, (1) Separate P packets to generate a local IP bucket addressed to the IP terminal device.

According to the present invention, a multiplex link formed by registering an IP address from an IΡ circuit multiplexing device function entity to an IΡ circuit multiplexing device management entity, an I NV ITE in a call origination call in a SIP signaling, and 20 A multilink management table is generated based on the IP address and port number obtained by OOK, and the IP line multiplexer function entity is bucketed based on the management table generated by the IP line multiplexer management entity. Multiplexing / demultiplexing to generate local IP packets and bearer IP buckets. Brief Description of Drawings

FIG. 1 is a conceptual diagram showing an example of a configuration of a communication system according to the present invention. FIG. 2 is a configuration of a multiplex link and a configuration of a multiplex link management table of the communication system shown in FIG. FIG. 3 is a block diagram showing the configuration of the IP line multiplexing equipment functional entity shown in FIG. 1, and FIG. 4 shows the configuration of a low power IP packet. FIG. 5 is a diagram showing a configuration of a short packet, and FIG. 6 is a diagram showing a configuration of a bearer IP bucket. BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of a communication system, an IP line multiplexing device management entity, and an IP line multiplexing device function entity according to the present invention will be described in detail with reference to the drawings. The present invention is not limited by the embodiment. Embodiment.

An embodiment of the present invention will be described with reference to FIGS. FIG. 1 is a conceptual diagram showing an example of a configuration of a communication system according to an embodiment of the present invention. The communication system according to the embodiment of the present invention includes a router 2 a having a filter transfer function,

2b, 2c and a SIP server that performs call control and session management in VoIP No. 3 and an IP line multiplexer management entity (hereinafter, referred to as ME) 4 are connected to an IP service network 5, which is a network. The router 2a has an IP line multiplexer equipment function entity (hereinafter referred to as FE) 1a, an IP telephone 7a-1, 7a-2, and a VolP gateway (first 8a is connected), and analog telephones 6a-1 and 6a-2 are connected to the Vo IP gateway 8a. Router 2a, IP phone 7a-1, 7a_2, Vo IP gateway 8a, analog phone 6a-1, 6, 6a-2, and FE la belong to the same domain or network.

The FE 1 b, the IP g 7 b—l, 7 b—2, and the Vo IP gateway 8 b are connected to the nolator 2 b, and the analog telephone 6 b—11, 6 b— 2 is connected. Router 2 b, IP phone 7 b—1, 7 b—2, Vo IP gateway 8 b, analog phone 6 b-1, 6 b—2, and FE 1 b belong to the same domain or network .

The router 2 c is connected to the FE 1 c, IP S7 c_l, 7 c-2, and the Vo IP gateway 8 c, and the Vo IP gateway 8 c is connected to the analog telephone 6 c-1, 6 c — 2 is connected. Router 2c, IΡβΙ§7c-1, 7c-2, Vo IP gateway 8c, analog phone 6c-1, 6c-2, and FE lc belong to the same domain or network .

In FIG. 1, FE la to lc have an external interface such as Ethernet (registered trademark) and are connected to routers 2 a to 2 c, but routers 2 a to 2 c In addition, the function of FEl a to lc may be provided. In the following, to indicate the location of the IP address and port, the terminal device (VoI gateway 8a-8c, IP phone 7a-1, 7a-2, 7b-1, 7, 7b) -The end user side of 2, 7c-1 and 7c-2) is the local side, and the IP service network 5 side is the bearer side.

ME 4 manages and controls FE1a ~ lc encoding / decoding and multiple Z separation In addition, a multiplex link is configured by the IP address of each device notified from FE 1 a to FE 1 c, and the multiplexed voice channels of FE la to FE lc and the dependency of the FE link are managed. Generate a multiple link management table. Note that the ME 4 may be physically distributed and may be included in the SIP server 3.

FIG. 2 is a diagram showing a configuration of a multiplexed link of FEla to FElc and a configuration of a multiplexed link management table 10a of FEla. In FIG. 2, the multiple link 9 ab power which is a logical link between FE 1 a and FE 1 b is a multiple link 9 ac power which is a logical link between FE la and FE lc FE lb and FE 1 b A multilink 9 bc, which is a logical link, is completed between them.

The FE 1 a multilink management table 10 a contains the IP address of the FE 1 b, which is the destination of the FE 1 a multilink 9 ab, and the information of the channel included in the multilink 9 ab, that is, the The IP address and port number of the Vo IP gateway 8a and the IP phones 7a-1 and 7a-2 are registered.

The ME 4 uses the IP address of the destination FE of the managed multiple link (in this case, multiple link 9 ab, 9 ac, 9 be) and the information of the channel included in the multiple link, that is, the information included in the domain. A multi-link management table that registers the IP address and port number of the Vo IP gateway or IP phone that has been registered is generated for each FE1a-lc, and the generated multilink management table is stored in FE1a-FElc. Send.

FE1a to FE1c have the same function, and encode and Z-decode the short packet and multiplex Z-demultiplex according to the recommendation of ITU-T G.769. The function of the FE will be described with reference to a block diagram showing the configuration of the FE 1a shown in FIG. The FE 1a includes an interface 20, a local IP packet receiving unit 11, an SP generating unit 13, a multiplexing unit 14, a bearer IP packet generating unit 15, a bearer IP packet receiving unit 16, a separating unit 17, An SP disassembly unit 18, a local IP packet generation unit 19, and a multiple link management table storage unit 10 are provided. The interface 20 is a physical interface, for example, a port, but may have any physical form or number. If the router 2a has the FE 1a, the interface 20 does not exist. The multiple link management table storage unit 10 stores the multiple link management table 10a transmitted from the ME 4.

The local IP packet receiving unit 11 receives a local IP packet input from an IP terminal device. As shown in FIG. 4, the local IP packet includes a low-level IP header 21, a UDP header 22, an RTP header 23, and an RTP payout port 24. The RTP payload 24 contains, for example, voice data that has been subjected to PCM (Puice Code Modulation) coding. Based on the local IP header 21 and the multi-link management tape storage 10 a stored in the multi-link management table storage unit 10, the local IP packet receiving unit 11 determines the channel of the low power IP packet based on the multi-link management tape storage 10 a stored in the multi-link management table storage unit 10. Identify. More specifically, the channel is identified by searching the multi-link management table 10a using the source IP address as a search key. 'Then, the channel short bucket generator (hereinafter referred to as a channel SIP generator) 13-1 to 13 -k of the SP generator 13 corresponding to the channel is output.

The SP generator 13 generates k (k is a natural number) channels SP generators 13— :! that generate short packets of one channel. ~ 13-k. Channel SP generators 13-1 to: L 3-k correspond to one of a plurality of channels multiplexed by FE la, apply a specific media coding for each channel, and generate a short packet for each channel. Generate. Specifically, a specific media encoding is performed on the RTP payload 24 of the local IP packet shown in Fig. 4 to generate the SP payload 27 shown in Fig. 5, which includes channel information and the like. A short packet to which the SP header 26 is added is generated. The channel generators 13-1 to 13-k output the generated short packets to the multiplexer 14.

The multiplexing unit 14 multiplexes a plurality of short packets generated by the SP generation unit 13. The bearer IP bucket generation unit 15 multiplexes the packets multiplexed by the multiplexing unit 14. A bearer IP packet with the destination address set to the destination FE (here, FE1b or FElc) based on the multiple link management table 10a stored in the multiple link management table storage unit 10 in the short bucket. Generate As shown in Fig. 6, the bearer IP bucket is composed of a bearer IP header 29, a UDP header 22, a RTP header 23, and a plurality of short packets (SP header 26 and SP payload). RTP payload consisting of 28. The multiplexing unit 14 outputs the bearer IP bucket generated via the interface 20 to the router 2a.

The bearer IP bucket receiving unit 16 receives the bearer IP bucket (see FIG. 6), extracts a message from the received bearer IP bucket, and outputs the message to the separating unit 17.

The separating unit 17 extracts a short packet from the message input from the bearer IP packet receiving unit 16. Then, the channel of the extracted short packet is identified based on the SP header 26 inside the short packet, and the short bucket (see FIG. 4) is assigned to each channel.

The SP decomposition section 18 is composed of k channel short packet decomposition sections (hereinafter, channel

SP-decomposition section) 18-1 to 18-k are provided. The channel SP decomposing units 18 11 to 18 k perform a specific media decoding on the short bucket input from the demultiplexing unit 17 in response to channels / records, and perform media decoding. The resulting short packet (see Fig. 5) is output to the local IP packet generator 19.

The local IP packet generator 19 is stored in the SP header 26 of the short bucket and the multilink management table storage 10 that are input to the channel SP decomposer 18-1 to 18-k. Based on the multiplex link management table 10a, the IP address and the destination port number of the mouth are discriminated. Specifically, the multiplex link using the channel information included in the SP header 26 as a search key By searching the management table 10a, the local IP address and the port number corresponding to the channel are identified, and the local IP packet and the local IP packet are used by using the identified local IP address and the port number (see FIG. 4). ) Is generated and transmitted to the low power side via interface 20 To do.

The channel SP generation units 13-1 to 13-k and the channel SP decomposition units 18_1 to 18-} do not always need to perform the coded Z decoding. In addition, any method may be used for the encoding / decoding Z decoding when performing the encoding / decoding.

Next, the operation of the communication system according to the present invention will be described. The FE la to FE lc register their own IP address in the ME 4 by a general method such as transmitting a command to the ME 4 every one second, and the multiplex links 9 ab, 9 ac, Make up 9 bc. The procedure for FE la to FE lc to register the IP address in ME 4 and the procedure for keep-alive are not particularly defined in the present invention.

When configuring the multiple links 9 ab, 9 ac, and 9 bc, the ME 4 generates a multiple link management table corresponding to FE 1 a to FElc. The ME 4 transmits IP addresses of FEla to FElc to FEla to FE1c. In FIG. 2, the IP address of FE 1 b is transmitted to FE 1 a as information of multiplex link 9 ab, the IP address of FE 1 a is transmitted to FE 1 b, and FE 1 a is transmitted as information of multiplex link 9 ac The IP address of FE 1c is transmitted to FE 1c, the IP address of FE 1a is transmitted to FE 1c, the IP address of FE 1c is transmitted to FE 1b as information of multiplex link 9bc, and FE 1c To the FE 1b IP address.

The SIP server 3 sends the information of I NV I TE and 200 OK in the SIP to the ME 4. Incidentally, the information of I NV I TE and 200〇K may be transmitted from the routers 2a to 2c.

ME 4 obtains the I I address and port number of the IΡ flow used as a voice line from the received I NVETE and 200〇K information. Here, it is assumed that communication is started between the IP telephone 7a-1 and the IP telephone 7b-1. ME 4 obtains the IP address and port number of IP telephone 7a_l and IP telephone 7b-1.

ME 4 routes the acquired IP address and port number of IP phone 7a_1. Server 2b, and sends the IP address and port number of IP phone 7b-1 to router 2b. As a result, the local-side IP packet transmitted from IP phone 7a-1 is forwarded to FE 1a, and the local-side IP packet transmitted from IP phone 7b-1 is forwarded to FE 1b. . If multiple voice lines are not accommodated by one IP address, there is no need to send port numbers to routers 2a and 2b.

ME 4 generates a multiplex link management table for FE 1 a and FE 1 b based on the IP address and port number of IP phone 7 a-1 and IP phone 7 b _ 1, and generates the generated multiplex. Send the link management table to FE 1a and FE 1b.

The FE 1 a and the FE 1 b store the multiple link management table received from the ME 4 in the multiple link management table storage unit 10. The ME 4 sends the information of the multiplex link, IP address, port number, and channel number individually to FE 1a and FE 1b, and FE 1a and FE 1b generate a multi-link management table. Then, the generated multiple link management table may be stored in the multiple link management table storage unit 10. The channel number is a common number for FE 1 a and FE 1 b for the same voice call, that is, call ID of SIP server 3, and is embedded as channel information in SP header 26. According to the multiplex link management table, FE 1a and FE 1b determine the short bucket multiplexed in the IP bucket when FE 1a and 1b receive the bearer from the IP service network 5 on the bearer side. You can specify the final destination.

As described above, in the call control in the SIP signaling by the SIP server 3, the communication between the IP telephone 7a-1 and the IP telephone 7b-1 is started by exchanging 200 OK with the NV ITE.

The IP telephone 7a-1 transmits a local IP packet addressed to the IP telephone 7b_1 to the router 2a. The router 2a has been notified of the IP address and port number of the IP phone 7a-1 from the ME 4. The router 2a identifies the local IP packet received from the IP phone 7a-1 by the finolater function, and transmits it to the FE 1a. When receiving the local IP bucket from the IP telephone 7a-1, the local IP bucket receiving unit 11 of the FE 1a stores the local IP bucket 21 and the multilink management table storage unit 10 in the local IP header 21. Based on the multiplexed link management table 10a, the channel of the local IP bucket is identified and output to the channel generators 13-1 to 13-k of the SP generator 13 corresponding to the channel.

The channel generator 13-1 to 13-k of the FE 1a generates a short bucket by applying a specific media code to the RTP payload 24 of the input local IP packet. The short bucket is output to the multiplexing unit 14.

The multiplexing section 14 of the FE 1a multiplexes the plurality of short packets generated by the SP generating section 13 to form a bearer IP bucket! ^ The generating unit 15 adds the destination address to the short-circuited packet multiplexed by the multiplexing unit 14 based on the multiplex link management table 10 a stored in the multiplex link management table storage unit 10 to the destination FE 1 b. Generate an IP bucket. The bearer IP bucket generating unit 15 transmits the bearer IP bucket to the IP service network 5 via the interface 20 and the router 2a.

Upon receiving the bearer IP packet from the IP service network 5, the router 2b transmits the received bearer IP bucket to the FE 1b. The bearer IP packet receiving unit 16 of F E 1 b extracts the message from the received bearer IP bucket packet and outputs the message to the separating unit 17.

The demultiplexer 17 of F E 1b extracts a short packet from the message input from the bearer IP bucket receiver 16. Then, the channel of the extracted short packet is identified based on the SP header 26 inside the short packet, and the short packet is distributed to each channel.

The channel of the SP decomposer 18 of FE 1 b The SP decomposer 18-1 to 18-k converts the short packet input from the demultiplexer 17 to a specific channel to perform specific media decoding. Then, the short bucket subjected to the media decryption is output to the local IP packet generator 19. The local IP packet generator 19 of the FE 1 b is stored in the SP header 26 of the short packet input from the channel SP decomposer 18-1 to 18-k and the multilink management table storage 10. The local IP address and the destination port number are identified based on the existing multilink management table 10a, and a local IP packet is generated using the identified local IP address and port number. Here, a local IP bucket of the IP address and port number of the IP phone 7b-1 is generated. The local IP bucket generation unit 19 transmits the generated local IP bucket to the router 2b via the interface 20. Nolator 2b sends a local IP bucket to IP phone 7a-1.

In this way, the voice data is transferred to the IP telephone 7a_1 and the IP telephone 7b_1. The transfer of voice data from IP phone 7b-1 to IP phone 7a-1 is the reverse of the operation from IP phone 7a_1 to IP phone 7b-1. Omitted.

As described above, in the present embodiment, a multiplex link configured by registering an IP address from a general IP line multiplexing device functional entity to an IP line multiplexing device management entity, and a call in a SIP signal rig. A multiplex link management table is generated based on the IP address and port number obtained by the I NV ITE and 200 OK at the time of calling, and a local IP packet and a bearer IP bucket are generated based on the generated link management table. Therefore, it is possible to apply the existing signaling method, SIP, to perform mutual communication using multiplexed IP packets.

In addition, since the IP line multiplexer functional entity in the communication system multiplexes / demultiplexes the packets based on the link management table, the terminal equipment end user can use the IP line multiplexer in the communication system. The voice line can be used seamlessly without any control.

Also, since the IP line multiplexer function entity multiplexes the packets, the voice line is used efficiently by highly efficient coded multiplex transmission, and the The system can be operated at low cost. Industrial applicability

As described above, the communication system according to the present invention is useful for a communication system that handles voice data in VoIP, and is particularly suitable for a communication system that accommodates a large number of voice channels such as an international line.

Claims

The scope of the claims

1. When IP terminal devices connected to a network via a router communicate with each other under the control of a SIP server, multiplex local IP packets from the IP terminal device to the opposite IP terminal device. An IP line multiplexer functional entity that generates a bearer IP bucket and separates bearer IP packets from the opposite IP terminal device to generate a local IP packet; and an IP line multiplexer functional entity. In a communication system having an IP line multiplexer management entity to control,

The IP line multiplexer management entity is:

Based on the multi-link information by the IP line multiplexer function entity and the IP address and port number of the IP terminal device notified from the SIP server, channel information corresponding to the IP address and port number is defined. A multi-link management table to be generated, and transmits the generated multi-link management table to the IP line multiplexer functional entity;

The IP line multiplexer function entity is:

A short bucket is generated from the local IP packet packet based on the multi-link management table, the generated short bucket is multiplexed to generate the bearer IP bucket, and the generated bucket is transmitted to the network. Separating the bearer IP bucket based on the multi-link management table to generate a local IP bucket addressed to the IP terminal device;

A communication system comprising:

2. When the IP terminal devices connected to the network via the router communicate with each other under the control of the SIP server, the IP terminal devices face each other.

The local IP bucket to the IP terminal device is multiplexed to generate a bearer IP bucket, and the bearer IP bucket from the opposite IP terminal device is separated. In the IP line management device management entity that controls the IP line multiplexing device function entity that generates the local IP bucket,

Based on the multi-link information by the IP line multiplexer function entity and the IP address and port number of the IP terminal device notified from the SIP server, a plurality of channels defining channel information corresponding to the IP address and port number are defined. Generating a duplicate link management table, and transmitting the generated multiple link management table to the IP line multiplexer function entity;

An IP line multiplexer management entity.

3. When the IP terminal devices connected to the network via the router communicate with each other under the control of the SIP server, the IP terminal devices are controlled by the IP line multiplexer management entity, and the IP terminal devices face each other. IP line multiplexing to generate a bearer IP packet by multiplexing the local IP bucket to the IP terminal device to be generated, and to generate a local IP bucket by separating the bearer IP bucket from the opposite IP terminal device Device function entity

A short packet is generated from the local IP packet based on a multiplex link management table in which channel information associated with the IP address and port number of the IP terminal device received from the IP line multiplexer management entity is defined. Multiplexing the generated short bucket to generate the bearer IP bucket, transmitting the generated packet to the network, and separating the bearer IP bucket based on the multiplex link management table. Generating a local IP bucket addressed to the IP terminal device,

An IP line multiplexing device functional entity, characterized by: