JP2014017618A - Communication device, method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a communication device that allows an operator to enjoy high-speed transfer by off-load setting without off-load setting by the operator.SOLUTION: The invention relates to a communication device which includes a first processor unit for performing call control and transfer of a media packet and a second processor unit for performing high-speed transfer of a media packet in a session registered with an off-load registration management unit. The first processor unit is characterized by including: a storage unit for managing session information extracted from a call control packet; a control unit for determining whether off-load setting should be registered or not by acquiring a parameter related to an established session from the storage unit when the session is established and the transmission and reception of media packets is started; and a setting processing unit for registering off-load setting with the off-load registration management unit on the basis of the information given by the control unit.

Description

  The present invention relates to a communication apparatus, method, and program, and can be applied to, for example, a VoIP home gateway in which one of a plurality of processors executes a VoIP (Voice over IP) media transfer process.

  A communication device has already been proposed in which one of a plurality of processors executes a VoIP media transfer process (see Patent Document 1).

  For example, a communication apparatus 10 shown in FIG. 10 includes an application processor (hereinafter referred to as AP) 11 that performs complicated communication packet processing and control, and a fast path processor (hereinafter referred to as FP) for transferring communication packets at high speed. And provides a call function to a subordinate SIP (Session Initiation Protocol) terminal 13.

  FIG. 11 shows a sequence in the case where the subordinate SIP terminal 13 makes an external line call. In FIG. 11, the network is expressed as WAN, and the side where a plurality of subordinate SIP terminals 13 exist is expressed as LAN. The terms “WAN” and “LAN” are used as appropriate in the description of the embodiments described later.

  SDP (Session Description Protocol) information is exchanged between the SIP terminal 13 and the communication device 10 and between the communication device 10 and the network, and RTP (Real-time Transport Protocol) packets entering from the network are exchanged. On the other hand, the destination IP address and port number, source IP address and port number, DSCP (Differentiated Service Code Point) value, RTP header information (SSRC identifier (synchronized source identifier), sequence number, timestamp), etc. 10 is rewritten in accordance with the route between the SIP terminal 13 and transmitted to the SIP terminal 13. Similarly, the destination IP address and port number of the RTP packet that enters from the SIP terminal 13 are transmitted. Source IP address and port number, DSCP value, and transmits rewritten in accordance with the path of the communication device 10 and a network such as RTP header information.

  FIG. 10 described above also shows the flow of RTP packets from the network to the SIP terminal 13. A transfer processing unit 14 is provided as a functional unit carried by the AP 11, and a high-speed transfer processing unit 15 is provided as a functional unit carried by the FP 12. The high-speed transfer processing unit 15 includes a header information comparison processing unit 15B, and the header information comparison processing unit 15B confirms whether or not an FP path is registered in the FP registration management table 16 for the input RTP packet. If it is registered, the RTP header conversion processing unit 15A in the high-speed transfer processing unit 15 is caused to function to perform the above-described RTP packet conversion and subsequent transfer (see double-line arrows). If not, the RTP header conversion processing unit 14A in the transfer processing unit 14 is operated to perform the above-described RTP packet conversion and subsequent transfer (see the dotted arrow).

  Since various applications operate on the AP 11, there is only a relatively low transfer capacity, and there is a possibility that processing delays of other applications may be caused by the transfer process. On the other hand, when the RTP packet is transferred through a path (double line arrow) where the AP 11 does not intervene, high-speed transfer by the FP 12 can be realized with a minimum load of the AP 11.

  Conventionally, an operator (human) explicitly manually sets which RTP packet is offloaded from the AP 11 to the FP 12 (to be excluded from the transfer processing target of the AP 11). That is, the FP control unit 17 is provided as a function unit that the AP 11 bears. The FP control unit 17 includes a maintenance terminal directly connected to the communication device 10 and a remote maintenance connected to the communication device 10 via a network. The terminal or a display / operation unit (not shown) (for example, a touch panel) (not shown) included in the communication device 10 is controlled to capture an operation signal from the operator, and registration to the FP registration management table 16 is executed based on the operation signal. The registration deletion is similarly performed manually by the operator.

JP 2006-180162 A

  As described above, in the conventional communication device, the high-speed transfer target must be manually set by the operator, and when the high-speed transfer becomes unnecessary, the operator must delete the setting each time. In other words, there is a problem that it takes time for actual operation.

  There are also communication services that are difficult to set off-load. For example, a service in which the SIP terminal 13-1 puts the call on hold and forwards the call to another SIP terminal 13-2 from a state in which the SIP terminal 13-1 and the network side terminal are talking via the communication device 10 Is a communication service that is difficult to set off-load. The RTP header information (SSRC identifier, sequence number, time stamp) sent from the SIP terminal 13-1 and the RTP header information sent from the SIP terminal 13-2 are different in SSRC identifier, and the sequence number and time stamp are also serial numbers. However, it is necessary to rewrite the RTP header information so that the RTP header information of the RTP packet output from the communication apparatus 10 to the network side has the same SSRC identifier, sequence number, and time stamp before and after transfer. However, it has been difficult to set such rewrite processing to the FP 12 as an offload.

  Therefore, there is a demand for a communication apparatus, method, and program that can enjoy high-speed transfer by offload setting without an operator performing offload setting.

  The first aspect of the present invention is a first processor unit that performs call control and transfer of media packets, and a second processor unit that transfers high-speed media packets of an offload-set session registered in the offload registration management unit The first processor unit includes: (1) a call information storage unit that manages session information extracted from a call control packet; and (2) a session is established and media packets are transmitted and received. A media control unit for determining whether or not to register an offload setting for the established session by acquiring a parameter related to the established session from the call information storage unit when starting, and (3) the media When it is determined to set offload for a session established by the control unit, the information given from the media control unit Hazuki, and having an off-load setting processing unit to be performed on the offload registration management unit, the registration of the off-road setting for the established session.

  The second aspect of the present invention is a first processor unit that performs call control and transfer of media packets, and a second processor unit that transfers high-speed media packets of an offload-set session registered in the offload registration management unit (1) the call information storage unit of the first processor unit manages session information extracted from the call control packet, and (2) the media control unit of the first processor unit. Determines whether or not to register parameters for the established session from the call information storage unit and register offload settings for the established session when the session is established and media packet transmission / reception is started. (3) The offload setting processing unit of the first processor unit sets offload for the established session. When the media control unit determines that the offload setting is registered for the established session to the offload registration management unit based on the information given from the media control unit. Method.

  The third aspect of the present invention is a first processor unit that performs call control and transfer of media packets, and a second processor unit that transfers media packets of an offload-set session registered in the offload registration management unit at high speed. A communication program executed by the first processor unit in a communication device including: (1) a call information storage unit that manages session information extracted from a call control packet; (2) Whether to register parameters related to the established session from the call information storage unit and register offload settings for the established session when the session is established and media packet transmission / reception is started (3) a session established by the media control unit is determined to be offloaded. The offload registration management unit functions as an offload setting processing unit for registering an offload setting for the established session based on information given from the media control unit. .

  According to the present invention, it is possible for an operator to enjoy high-speed transfer by offload setting without performing offload setting or the like.

It is a block diagram which shows the functional structure of the communication apparatus of embodiment. It is explanatory drawing which shows the structure of the 1st FP registration management table of FIG. It is explanatory drawing which shows the structure of the call information storage table of FIG. It is explanatory drawing which shows the structure of the 2nd FP registration management table of FIG. It is a sequence diagram which shows the automatic addition operation | movement of an offload setting when the outside line telephone call is started with the wired SIP terminal in the communication apparatus of embodiment. It is a block diagram which shows the audio | voice processing route of the reverse direction of the audio | voice processing route shown in FIG. It is a sequence diagram which shows the automatic addition operation | movement of an offload setting when an outside line call is started with the radio | wireless SIP terminal in the communication apparatus of embodiment. It is a sequence diagram which shows the automatic deletion operation | movement of the offload setting in the communication apparatus of embodiment. It is a sequence diagram which shows the change of the offload setting at the time of extension transfer in the communication apparatus of an embodiment. It is a block diagram which shows the functional structure of the conventional communication apparatus. FIG. 11 is a sequence diagram when a SIP terminal under the communication apparatus of FIG. 10 performs an outside line call.

(A) Main Embodiment Hereinafter, an embodiment of a communication apparatus, method and program according to the present invention will be described with reference to the drawings. The communication device of this embodiment is, for example, a VoIP home gateway.

(A-1) Configuration of Embodiment FIG. 1 is a block diagram illustrating a functional configuration of a communication apparatus according to an embodiment. The communication apparatus 20 according to the embodiment includes an application processor and a fast path processor, and a function unit that is exhibited when the application processor executes its own program, and a program that is used by the fast path processor. FIG. 1 shows a functional part that is exhibited by executing the above.

  In FIG. 1, AP 30 represents a functional unit group that is exhibited when an application processor executes its own program, and FP 50 is a function that is exhibited when a fast path processor executes its own program. Represents a group. In the description of the prior art, AP and FP are roughly referred to, but strictly speaking, it is the same as in the case of this embodiment.

  The communication device 20 realizes a call between the subordinate wired SIP terminal 21 or the wireless SIP terminal 22 and the network (WAN) side.

  The AP 30 includes a transfer processing unit 31, an RTP registration management table 32, a VoIP control unit 33, an interface information management unit 34, an offload setting processing unit 35, and a wireless processing unit 36. The VoIP control unit 33 includes a session management unit 40, a media control unit 41, a first FP registration management table 42, and a call information storage table 43.

  On the application processor, a general-purpose OS (Operating System) having a network stack such as Linux (registered trademark) operates, and on that, a DHCP (Dynamic Host Configuration Protocol) server / client, a PPPoE (Point-to-to) -Point Protocol over Ethernet) It is assumed that an application such as a client / server or a VoIP application operates. A functional representation of such an AP 30 is shown in FIG.

  The FP 50 includes a high-speed transfer processing unit 51, a LAN side wired processing unit 52, a WAN side wired processing unit 53, and a second FP registration management table 54. The high-speed transfer processing unit 51 includes a header information comparison processing unit 60 and an RTP header conversion processing unit 61.

  The FP 50 realizes high-speed transfer of RTP packets received from the WAN side wired processing unit 53 (wired WAN interface) and the LAN side wired processing unit 52 (wired LAN interface).

  The transfer processing unit 31 corresponds to a transfer processing unit in the network stack of the Linux kernel, for example. The transfer processing unit 31 searches the list of the RTP registration management table 32 provided in the transfer processing unit 31, determines the output destination interface by comparing with the frame header information, and rewrites the RTP header. To perform the transfer.

  The RTP registration management table 32 is a table in which a list of resource RTP sockets is described, and registers and manages resource information.

  The VoIP control unit 33 performs call control to establish or disconnect a session related to the SIP terminals 21 and 22 under the communication device 20.

  The session management unit 40 performs management and call control of the state of the session (extension call, external call) and the states of the SIP terminals 21 and 22 under the communication device 20. The communication device 20 is not a dedicated IP-PBX, but a call between subordinate SIP terminals is called an extension call, and between the subordinate SIP terminal and a terminal of an external network (hereinafter referred to as an opposite terminal). Is called an outside line call.

  The session management unit 40 acquires SDP information of the SIP packet and stores it in the call information storage table 43. For example, the IP address and port number of the opposite terminal are acquired and stored, the IP address and port number of the subordinate SIP terminal are acquired and stored, and direction information (sendrecv ( The communication device transmits / receives packets) / sendly (the communication device only transmits packets) / recvonly (the communication device only receives packets) / inactive (the communication device also receives packets) Also do not execute))) to get and save. Further, the session management unit 40 searches for a port that is not in use, sets an RTP reception port on the external terminal side or SIP terminal side of the communication device 20, notifies it with SIP / SDP information, and stores it in the call information storage table 43. save. Further, the session management unit 40 notifies the media control unit 41 of an RTP transmission start request when processing of the SIP session for starting a call is completed. Furthermore, when the session management unit 40 receives the SIP packet for ending the call, the session management unit 40 notifies the media control unit 41 of an RTP transmission stop request, and performs an SIP session termination process. In addition, when the session management unit 40 receives the SIP packet for updating the session information, the session management unit 40 notifies the media control unit 41 of an RTP information update request. When the exchange of the SIP session for extension transfer is completed, the session management unit 40 notifies the media control unit 41 of a terminal change request.

  The media control unit 41 according to this embodiment receives a request from the session management unit 40, acquires information necessary for offload setting, and requests the offload setting processing unit 35 for offload setting.

  The first FP registration management table 42 holds FP session IDs and FP resource IDs in entries held by a second FP registration management table 54 described later. The first FP registration management table 42 is mainly used for assigning a free ID (numbering) of the first FP registration management table 42 and deleting an offload setting from the FP 50 when an entry is added. The

  The first FP registration management table 42 includes a session table 42A shown in FIG. 2A and a resource table 42B shown in FIG. The session table 42A describes a combination of sockets (FP resource IDs) at both ends that are connected to an FP path by offload setting in association with the FP session ID. The resource table 42B describes the resource usage status in association with the FP resource ID. From the FP resource IDs in the resource table 42B, socket IDs at both ends for FP path connection are allocated by offload setting, and the usage status of the allocated resources (LAN side wired processing unit, WAN side wired processing unit) is “Used”. "Medium" is described.

  The entry addition, deletion, and update triggers for entries in the first FP registration management table 42 are as follows, and are synchronized with the addition, deletion, and update of entries in the second FP registration management table 54. The entry addition trigger is when the offload setting is added to the FP 50, the entry deletion trigger is when the offload setting is deleted from the FP 50, and the entry update trigger is when the FP 50 off-load setting is changed. .

  The call information storage table 43 is a table for the VoIP control unit 33 to store and refer to information set in the FP 50 using the session ID. The call information storage table 43 includes a session table 43A shown in FIG. 3A and a resource table 43B shown in FIG.

  In the session table 43A, a combination of sockets (resource IDs) at both ends of the RTP is registered in association with the session ID.

  In the resource table 43B, resource IDs of sockets at both ends of the RTP (an RTP socket on the WAN side during an external line call and an RTP socket on the LAN side during an external line call) are registered. The entry for each resource ID includes: [1] clock rate, [2] packetization period, [3] destination IP address and port number, [4] destination IP address & port number, [5] SSRC identifier , [6] FP resource ID (stores the ID of the FP socket for the wired interface), [7] ACP resource ID (stores the ID of the FP socket for the kernel), and the like.

  For example, the registration state of the session table 43A and the resource table 43B during an outside line call is as follows.

  [1] RTP resource ID1 (WAN side resource ID) and [2] RTP resource ID2 (LAN side resource ID) are registered in the session table 43A.

  Regarding the RTP resource ID1 (WAN side resource ID) of the resource table 43B, the following registration is made.

[1] The clock rate value set in SDP a = rtmap is registered. In the following example, “8000” is registered.

a = rtpmap: <payload type><encodingname> / <clock rate>
Example: a = rtpmap: 0 PCMU / 8000
[2] A value set in a = ptime of SDP is registered as a packetization period. In the following example, “20” is registered. If ptime is not set, 0 is set (registered).

a = ptime: <ptime>
Example: a = ptime: 20
[3] The IP address and port number of the opposite terminal are registered. [4] The WAN-side IP address and port number in the communication device are registered. [5] The SSRC identifier is registered. [6] The FP resource ID is stored. [7] Not set.

  Regarding the RTP resource ID 2 (LAN side resource ID) of the resource table 43B, the following registration is made.

[1] The clock rate value set in SDP a = rtmap is registered. [2] A value set in a = ptime of SDP is registered. [3] The IP address and port number of the SIP terminal are registered. [4] The IP address and port number on the LAN side in the communication device are registered. [5] The SSRC identifier is registered. [6] Not set in the case of a wireless SIP terminal. In the case of a wired SIP terminal, the FP resource ID is stored. [7] In the case of a wired SIP terminal, it is not set. In the case of a wireless SIP terminal, the AP resource ID is stored.

  When an IP address is given from the media control unit 41, the interface information management unit 34 sends the MAC address and interface information (wired (WAN), wired (LAN), and wireless (LAN)) corresponding to the IP address to the media control unit. This is a reply to 41.

  The wireless processing unit 36, the LAN-side wired processing unit 52, and the WAN-side wired processing unit 53 may be arranged in either the AP 30 or the FP 50. However, as shown in FIG. 1, when the wireless processing unit 36 is mounted on the AP 30, and the LAN side wired processing unit 52 and the WAN side wired processing unit 53 are mounted on the FP 50, the socket with the wireless SIP terminal 22 is for the AP 30. The socket for the wired SIP terminal 21 and the network side is created for the FP 50. Therefore, the interface information management unit 34 is used to distinguish between the wired SIP terminal 21 and the wireless SIP terminal 22. When both the LAN side wired processing unit 52 and the wireless processing unit 36 are in the FP 50, or when both the LAN side wired processing unit 52 and the wireless processing unit 36 are in the AP 30, the interface information management unit 34 There is no need for determination.

  In response to a request from the media control unit 41, the offload setting processing unit 35 performs offload setting for the FP 50.

  The wireless processing unit 36 corresponds to, for example, a wireless LAN driver, and transmits and receives a frame for the wireless SIP terminal 22.

  In the high-speed transfer processing unit 51, the built-in RTP header conversion processing unit 61 performs conversion of the RTP header and high-speed frame transfer based on the result of the built-in header information comparison processing unit 60.

  The LAN-side wired processing unit 52 corresponds to, for example, a wired LAN (network interface card; NIC) driver and transmits / receives a frame to / from the wired SIP terminal 21.

  The WAN-side wired processing unit 53 corresponds to, for example, a wired WAN (NIC) driver, and transmits / receives a frame to / from the network side.

  The header information comparison processing unit 60 determines the transfer destination of the frame from the destination IP address and port of the input frame (IP packet) and the source IP address and port. The header information comparison processing unit 60 determines the transfer destination by searching the second FP registration management table 54. When the entry corresponding to the frame is not hit in the second FP registration management table 54, the header information comparison processing unit 60 transfers the input frame to the transfer processing unit 31 of the AP 30, and the comparison by the AP 30 is performed. To perform a slow transfer process. When an entry corresponding to the input frame is hit, the header information comparison processing unit 60 gives the input frame to the RTP header conversion processing unit 61 together with the entry contents, and transfers them at high speed.

  The RTP header conversion processing unit 61 performs header conversion of RTP packets (see FIG. 11) and transfers frames at high speed.

  The second FP registration management table 54 is a table included in the FP 50, and holds information on frames to be subjected to high-speed transfer processing and RTP header conversion processing. The second FP registration management table 54 includes a session table 54A shown in FIG. 4A and a resource table 54B shown in FIG. 4B.

  The elements of the entry in the session table 54A are as follows. [1] Session ID, [2] Socket ID (WAN side), [3] Socket ID (LAN side (wired) / AP (wireless)), [4] Socket attribute (sendrecv / recvonly / sendonly / inactive), [ 5) Sequence number base, [6] SSRC identifier, [7] Time stamp base, [8] Frequency (time stamp increment). The sequence number of the RTP packet is stored in the above-mentioned [5] sequence number base. The set value is stored at the start of RTP packet transmission, and the sequence number updated every time one packet is transmitted is stored. [7] The time stamp base stores the time stamp value of the RTP packet. The set value is stored at the start of RTP packet transmission, and the updated time stamp value is stored every time one packet is transmitted. [8] In the frequency (time stamp increment), an increment of the time stamp value is set. For example, when the first packet is timestamp = 10000 and the second packet is timestamp = 10160, the increment of the time stamp value is 160.

  The elements of the entry in the resource table 54B are as follows. [1] Socket ID, [2] Type FP / AP, [3] Destination IP address, [4] Receiving IP address, [5] Destination port number, [6] Receiving port number. [2] In the type FP / AP, AP 30 is set when the wireless SIP terminal 22 is used, and FP 50 is set when the wired SIP terminal 21 and the network side (WAN).

  For example, the registration state of the session table 54A and the resource table 54B when an external line call is made at the wired SIP terminal 21 is as follows.

  In the session table 54A, the same session ID as the first FP registration management table 42 is stored in [1] Session ID. [2] The FP resource ID on the WAN side is stored in the socket ID (WAN), and the FP resource ID on the LAN side is stored in [3] socket ID (LAN / AP). [4] The socket attribute stores sendrecv when a call is in progress, and inactive during transfer processing. [5] The sequence number base stores the sequence number of the RTP packet. An arbitrarily set value is passed as the initial setting value based on the sequence number. After the packet transmission, the sequence number updated every packet transmission is stored. [6] A randomly generated value is set in the SSRC identifier. [7] The time stamp base stores the time stamp value of the RTP packet. Pass an arbitrarily set value as the initial setting value of timestamp base. After packet transmission, the time stamp value updated every packet transmission is stored. [8] The increment of the time stamp value is set for the frequency. Set based on clock rate and packetization period values. When the packetization period is 0, the clock rate is set. If the packetization period is other than 0, (clock rate × packetization period) / 1000 is set.

  The following registration is made for FP resource ID1 (WAN side resource) in the resource table 54B.

  The resource ID on the WAN side is stored in the [1] socket ID of the FP resource ID1 (WAN side) of the resource table 54B, the FP is stored in the [2] type FP / AP, and [3] in the destination IP address The IP address of the opposite terminal is stored, the IP address on the WAN side of the communication device 20 is stored in [4] received IP address, the port number of the opposite terminal is stored in [5] destination port number, and [6] In the reception port number, the port number on the WAN side of the communication device 20 is stored.

  On the other hand, the resource ID on the LAN side is stored in the [1] socket ID of the FP resource ID2 (LAN side) of the FP resource ID2 in the resource table 54B, the AP is stored in the [2] type FP / AP, and [3 The IP address of the wired SIP terminal 21 is stored in the destination IP address, the IP address on the LAN side of the communication device 20 is stored in the received IP address, and the wired SIP terminal is stored in the destination port number. 21 is stored, and the port number on the LAN side of the communication device 20 is stored in [6] reception port number.

(A-2) Operation of Embodiment Next, a characteristic operation in the communication device 20 of the embodiment will be described with reference to a sequence diagram in addition to FIG.

(A-2-1) Automatic addition operation of offload setting (part 1)
In the communication device 20 according to the embodiment, when starting an external line call, the session management unit 40 of the VoIP control unit 33 notifies the media control unit 41 of the VoIP control unit 33 of the RTP transmission start request, and the media control unit 41 is turned off. An offload setting can be automatically added by making a load setting addition request to the offload setting processing unit 35.

  FIG. 5 is a sequence diagram showing an offload setting addition operation when an outside line call is started at the wired SIP terminal 21. When an offload setting is made for an external line call of the wired SIP terminal 21 by the series of processes of FIG. 5, a call signal flows from the network to the wired SIP terminal 21 through the double line audio processing route of FIG. The call signal flows from the wired SIP terminal 21 to the network through the double-line audio processing route of FIG. In other words, an offload setting is added so as to realize the double-line audio processing route of FIGS. 1 and 6.

  Here, when an outside line call is started, the following operation is executed prior to the offload setting addition operation. That is, the session management unit 40 stores the information (transmission destination IP address and port number and direction information) acquired from the SDP of the SIP packet in the call information storage table 43 (step S100), and then notifies the session ID. The RTP packet transmission start request is given to the media control unit 41 (step S101), and the media control unit 41 sends the direction information and the transmission destination in each communication direction from the call information storage table 43 based on the notified session ID. IP address and port number, and the destination IP address and port number of each communication direction are acquired (step S102). For the communication direction from the wired SIP terminal 21 to the opposite terminal, the IP address and port number of the opposite terminal are acquired as the destination IP address and port number, and the communication apparatus is used as the destination IP address and port number. 20 to obtain the IP address and port number of the wired SIP terminal 21 as the destination IP address and port number for the communication direction from the opposite terminal to the wired SIP terminal 21. Then, the IP address and port number on the LAN side in the communication device 20 are acquired as the IP address and port number of the receiving destination.

  After the process of step S102 described above, an offload setting addition operation is performed.

  The media control unit 41 acquires interface information from the interface information management unit 34 based on the IP address information obtained from the call information storage table 43 (step S103). In the case of the example of FIG. 5, the interface information management unit 34 determines a WAN (network side; wired), LAN (SIP terminal side; wired) interface based on the transmission destination IP address, and represents a value representing the interface. Send back.

  The media control unit 41 acquires two free FP resource IDs from the first FP registration management table 42 and assigns them to be used for the current offload setting, and sends the FP resource ID and the FP resource ID to the offload setting processing unit 35. Then, the socket information (partner IP address and port number, the IP address and port number of the communication device 20 and the socket type (FP)) in the FP 50 including various acquired information is passed and additional registration (creation) of the FP socket is performed. A request is made (step S104). At this time, two FP sockets on the network side (WAN) and SIP terminal side (LAN) are registered and created. Since the WAN side wired processing unit 53 and the LAN side wired processing unit 52 are in the FP 50, the socket type is created by FP. Further, the media control unit 41 registers the acquired FP resource ID in the call information storage table 43 (step S105).

  Note that if the FP resource ID in the free state cannot be acquired from the first FP registration management table 42, the media control unit 41 determines that the offload setting cannot be performed, and stops the subsequent setting operation.

  In response to the request for additional registration (creation) of the FP socket, the offload setting processing unit 35 registers (adds an entry) FP socket information in the resource table of the second FP registration management table 54 (step S106).

  The media control unit 41 obtains a free FP session ID from the first FP registration management table 42, registers the combination of WAN / LAN FP sockets in the first FP registration management table 42, and also registers the FP session ID. The FP resource ID (WAN) and the FP resource ID (LAN) are transferred to the offload setting processing unit 35 to request registration of the FP path (step S107).

  In addition, the media control unit 41 passes the FP session ID, socket attribute, and RTP information (SSRC, time stamp base, time stamp increment) to the offload setting processing unit 35 for the FP path, and rewrites the RTP header in the FP 50. Registration of information to be executed is requested (step S108).

  The offload setting processing unit 35 registers (adds entries) the information in the session table of the second FP registration management table 54 in response to the request for registering the FP path and the request for registering the rewrite information of the RTP header (step S109). ).

(A-2-2) Automatic addition operation of off-road setting (part 2)
In the above, the offload setting addition operation when the wired SIP terminal 21 starts an outside line call has been described. Hereinafter, an offload setting addition operation when an external line call is started at the wireless SIP terminal 22 will be described.

  FIG. 7 is a sequence diagram showing an offload setting addition operation when an external line call is started at the wireless SIP terminal 22.

  When an external line call is started, an operation executed prior to the offload setting addition operation is performed when an external line call is started at the above-described wired SIP terminal 21 even when the external call is started at the wireless SIP terminal 22 (step S100). To S102) (steps S200 to S202).

  The media control unit 41 acquires interface information from the interface information management unit 34 based on the IP address information obtained from the call information storage table 43 (step S203). In the case of the example in FIG. 7, the interface information management unit 34 determines a WAN (network side; wired) or LAN (SIP terminal side; wired) interface based on the transmission destination IP address, and sets a value representing the interface. Send back.

  Therefore, the media control unit 41 differs from the case of FIG. 5 in information when requesting the offload setting processing unit 35 to perform additional registration (creation) of the FP socket (step S204). In the case of FIG. 7, since the acquired interface information is LAN (wireless), the media control unit 41 creates the FP socket on the WAN side with the socket type “FP” as in FIG. Unlike the case of FIG. 5, the socket is created with the socket type “AP”.

  The subsequent processing in FIG. 7 (steps S205 to S209) is the same as in the case of FIG. 5 described above (steps S105 to S109).

  When the offload setting is performed by the operation illustrated in FIG. 7, the RTP packet directed from the opposite terminal to the wireless SIP terminal 22 is determined to be transferred to the high-speed transfer target and the AP 30 by the header information comparison processing unit 60 of the high-speed transfer processing unit 51. Then, after the RTP header conversion processing unit 61 performs RTP header conversion and the like, it is given to the wireless processing unit 36 via the transfer processing unit 31 in the AP 30. Also, the RTP packet from the wireless SIP terminal 22 to the opposite terminal goes to the high-speed transfer processing unit 51 via the transfer processing unit 31 in the AP 30 and is subject to high-speed transfer by the header information comparison processing unit 60 of the high-speed transfer processing unit 51. After the RTP header conversion processing unit 61 performs RTP header conversion and the like, it is given to the WAN side wired processing unit 53.

  In this embodiment, since the wireless processing unit 36 is on the AP 30, the wireless processing unit 36 must pass through the transfer processing unit 31 of the AP 30. For this reason, the FP socket on the LAN side needs to have the socket type “AP”, but the wireless processing unit 36 may be on the FP 50. In this case, the socket type of the FP socket on the LAN side is Becomes “FP”.

(A-2-3) Automatic deletion operation of off-road setting In the communication apparatus 20 of the embodiment, the off-road setting can be automatically deleted at the end of the external line call. That is, in the communication device 20 according to the embodiment, at the end of the external line call, the session management unit 40 notifies the media control unit 41 of a stop request for RTP transmission, and the media control unit 41 sets an offload setting deletion request as an offload setting. By performing the processing to the processing unit 35, it is possible to automatically delete the offload setting.

  FIG. 8 is a sequence diagram showing an automatic deletion operation for offload settings. The automatic deletion operation for offload settings will be described in detail with reference to FIG. 8 as well.

  When the call for a certain session (RTP session) ends, the session management unit 40 identifies the session ID and gives a request to stop the RTP transmission to the media control unit 41 (step S300).

  At this time, the media control unit 41 acquires from the call information storage table 43 the FP resource ID related to the session ID of the call termination (step S301). In this process, the fact that the FP resource ID cannot be acquired indicates that the session for which the call has ended is not set to offload.

  After acquiring the FP resource ID, the media control unit 41 next acquires an FP session ID corresponding to the FP resource ID from the first FP registration management table 42 (step S302). Then, the media control unit 41 sends an FP path disconnection request for the acquired FP session ID to the offload setting processing unit 35 (step S303), and from the session table of the first FP registration management table 42, the FP FP resource ID1 and FP resource ID2 associated with the session ID are initialized (cleared) (step S304).

  The offload setting processing unit 35 that has received the FP path disconnection request deletes the entry related to the FP session ID from the session table of the second FP registration management table 54 (step S305).

  In addition, the media control unit 41 passes the WAN-side FP resource ID and the LAN-side FP resource ID to the offload setting processing unit 35 to make a request to delete the FP socket, and in the first FP registration management table 42 Information matching the FP resource ID is deleted from the resource table (step S306).

  Upon receiving the FP socket deletion request, the offload setting processing unit 35 deletes the entry related to the FP socket requested to be deleted from the WAN side and LAN side resource tables of the second FP registration management table 54 (step S307). ).

(A-2-4) Automatic operation of offload setting associated with extension transfer The communication apparatus 20 according to the embodiment starts from a state in which the subordinate SIP terminal 21 or 22 is in an external line call, and other subordinate SIP terminals Even when the extension transfer is performed, the offload setting can be automatically operated so that the high-speed transfer can be realized in the communication between the other SIP terminal and the opposite terminal after the extension transfer.

  That is, the session management unit 40 notifies the media control unit 41 of a terminal change request, and the media control unit 41 requests the offload setting processing unit 35 to stop / restart RTP and update information of offload settings. It is possible to automatically delete the offload setting related to the SIP terminal before the extension transfer and register the offload setting related to another SIP terminal after the extension transfer.

  FIG. 9 is a sequence diagram showing an automatic operation of offload setting at the time of extension transfer. With reference to FIG. 9 as well, automatic offload setting at the time of extension transfer (voice processing route change) is performed. The operation will be described in detail.

  When the session management unit 40 recognizes that the LAN-side SIP terminal related to the session has been changed by extension transfer, the session control unit 40 mediates the change request of the terminal with the session ID and information related to the SIP terminal after extension transfer. The data is sent to the unit 41 (step S400).

  At this time, the media control unit 41 uses the session ID as a key to retrieve the FP resource ID, the destination IP address and port number on the LAN side, and the destination IP address and port number on the LAN side from the call information storage table 43. Obtain (step S401).

  Then, the media control unit 41 acquires the FP session ID from the first FP registration management table 42 based on the FP resource ID acquired from the call information storage table 43 (step S402), and sends it to the offload setting processing unit 35. On the other hand, the stop of RTP transmission / reception in the route stretched to the SIP terminal before the extension transfer is instructed (step S403). The media control unit 41 specifies the FP session by the FP session ID, and then instructs the offload setting processing unit 35 to stop the RTP transmission / reception by changing the RTP socket attribute to inactive (packet transmission / reception stop). At this time, the offload setting processing unit 35 changes the socket attribute of the corresponding entry in the second FP registration management table 54 to inactive and shifts to the RTP transmission / reception stop state (step S404).

  Note that if the FP session ID cannot be obtained from the first FP registration management table 42 in the process of step S402, the media control unit 41 determines that the offload setting has not been set before the extension transfer, and the extension after the extension transfer. Assume that RTP packets are transferred without setting offload.

  Next, the media control unit 41 acquires the FP resource ID from the first FP registration management table 42 in order to create a new FP socket of the transfer destination SIP terminal (step S405), and the offload setting processing unit. 35 is requested to newly register the FP socket of the transfer destination SIP terminal (step S406). At this time, the offload setting processing unit 35 adds the requested FP socket entry to the resource table on the LAN side of the second FP registration management table 54 (step S407).

  Thereafter, the media control unit 41 obtains the LAN side FP resource ID in the corresponding FP session (specified by the FP session ID) in the session table of the first FP registration management table 42 in the above-described step S405. In addition to the change (step S408), a path connection update request is sent to the offload setting processing unit 35 (step S409). At this time, the offload setting processing unit 35 combines the WAN side FP resource ID and the LAN side FP resource ID in the corresponding FP session (specified by the FP session ID) in the session table of the second FP registration management table 54. Among them, the LAN side FP resource ID is changed from the transfer source FP resource ID to the transfer destination FP resource ID, and the path is reconnected (step S410).

  Thereafter, the media control unit 41 specifies the FP session with the FP session ID, and then instructs the offload setting processing unit 35 to resume RTP transmission / reception by changing the RTP socket attribute to sendrecv (packet transmission / reception allowed). (Step S411). At this time, the offload setting processing unit 35 changes the socket attribute of the corresponding entry in the session table of the second FP registration management table 54 to sendrecv and shifts to the RTP transmission / reception state (step S412).

  Finally, the media control unit 41 sends an FP resource deletion request including the FP resource ID on the LAN side before transfer to the offload setting processing unit 35 and transfers in the resource table of the first FP registration management table 42. The previous FP resource ID entry on the LAN side is made free (step S413). The offload setting processing unit 35 to which the FP resource deletion request is given deletes the entry of the FP resource requested to be deleted from the LAN-side resource table of the second FP registration management table 54 (step S414).

  By the above-described processing of steps S408 to S410, the FP session ID before transfer is used as it is instead of newly acquiring the FP session ID, and only the FP resource ID on the LAN side is updated, so that the sequence number and SSRC identifier are updated. The RTP can be transmitted after the transfer with the time stamp value inheriting the value before the transfer.

(A-3) Effect of Embodiment According to the above embodiment, the following effect can be obtained.

  According to the above-described embodiment, offload setting, which conventionally requires manual operation by an operator, can be automatically executed when RTP transmission is started. In addition, the SIP terminal on the LAN side is not limited to a wired SIP terminal, and the offload setting can be automatically performed even in the case of a wireless SIP terminal.

  Since the offload setting can be automatically executed, it can be expected that the number of sessions that can be transferred at high speed will be larger than before, which leads to the reduction of the processing load on the AP 30 and the service of the communication apparatus.

  Further, according to the above-described embodiment, the release of the offload setting, which conventionally required manual operation by the operator, can be automatically executed when RTP transmission is stopped. Since the automatic offload setting is canceled, unnecessary entries can be prevented from remaining in the FP registration management table. This means that the inconvenience of rejecting a new offload setting because the table is full can be prevented. Also, by canceling the offload setting after receiving the call disconnection packet, it is possible to prevent the RTP packet transmitted by the other party before the call disconnection is completed from being transferred to the terminal that transmitted the call disconnection packet.

  Furthermore, according to the above embodiment, offload setting after extension transfer, which was impossible in the past, is also automatically executed. That is, high-speed transfer can be performed regardless of before or after extension transfer.

(B) Other Embodiments In the above embodiment, the LAN side wired processing unit 52 is arranged on the FP 50. However, a part or all of the LAN side wired processing units 52 are arranged on the AP 30. Also good.

  In the above embodiment, the WAN-side wired processing unit 53 is arranged on the FP 50. However, some or all of the WAN-side wired processing units 53 may be arranged on the AP 30.

  In the above embodiment, the wireless processing unit 36 is arranged on the AP 30, but a part or all of the wireless processing units 36 may be arranged on the FP 50.

  In the above embodiment, the WAN side includes only the wired processing unit 53, but a part or all of the interface processing units on the WAN side may be wireless processing units.

  In the description of each of the embodiments described above, a plurality of LAN-side wired processing units 52 are described. However, a single LAN-side wired processing unit having a plurality of wired LAN ports may be used. Similarly, instead of the plurality of wireless processing units 36, a single wireless processing unit having a plurality of SSIDs (Service Set IDentifiers) may be applied.

  In each of the above-described embodiments, the high-speed transfer (offload setting) is possible in the communication between the WAN-side terminal and the subordinate SIP terminal. However, the high-speed transfer (offload) is possible in the communication between the subordinate SIP terminals. Setting) is possible.

  In each of the above embodiments, any session is automatically set to be offloaded at the start of a call as long as the FP registration management table is free. However, a condition is also provided for a session to be automatically set to offload. You may do it. For example, the offload setting may be automatically performed on condition that the parameter indicating the priority in the RTP header information is equal to or higher than a predetermined priority.

  In each of the above embodiments, the call control protocol is SIP. However, other call control protocols may be used.

  In each of the above embodiments, the present invention is applied to VoIP communication, but the media is not limited to voice.

  DESCRIPTION OF SYMBOLS 20 ... Communication apparatus, 21 ... Wired SIP terminal, 22 ... Wireless SIP terminal, 30 ... AP (functional part group which an application processor performs), 31 ... Transfer processing part, 32 ... RTP registration management table, 33 ... VoIP control part 34 ... Interface information management unit, 35 ... Offload setting processing unit, 36 ... Wireless processing unit, 40 ... Session management unit, 41 ... Media control unit, 42 ... First FP registration management table, 43 ... Call information storage table , 50... FP (functional unit group executed by fast path processor), 51... High-speed transfer processing unit, 52... LAN side wired processing unit, 53... WAN side wired processing unit, 54. 60... Header information comparison processing unit, 61... RTP header conversion processing unit.

Claims (5)

In a communication apparatus comprising: a first processor unit that performs call control and media packet transfer; and a second processor unit that performs high-speed transfer of a media packet of an offload-set session registered in the offload registration management unit.
The first processor unit includes:
A call information storage unit managing session information extracted from the call control packet;
When a session is established and media packet transmission / reception is started, parameters related to the established session are acquired from the call information storage unit, and it is determined whether or not to register offload settings for the established session. A media control unit;
When the media control unit determines to set offload for the established session, the offload setting management unit is registered with the offload setting for the established session based on the information given from the media control unit. An offload setting processing unit for performing communication. When the media control unit terminates transmission / reception of the media packet of the established session, it determines the necessity of deregistration of the offload setting based on whether or not the offload setting has been registered for the session,
When the offload setting registration unit is instructed by the media control unit, the offload setting processing unit releases the offload setting registration of the instructed session to the offload registration management unit. The communication apparatus according to claim 1. When the subordinate communication terminal, which is one element of the established session, is switched to the other subordinate communication terminal while maintaining communication, the media control unit has registered offload settings for that session. Based on whether or not it is necessary to change the registration information of the offload settings,
When the offload setting processing unit is instructed by the media control unit to change the offload setting registration content, the offload setting processing unit converts the offload setting registration content related to the subordinate communication terminal before switching to the subordinate after switching The communication apparatus according to claim 1, wherein the communication apparatus is changed so as to target other communication terminals and so that the information of the media packet is consistent before and after switching. Communication in a communication apparatus having a first processor unit that performs call control and media packet transfer, and a second processor unit that transfers media packets of an offload-set session registered in the offload registration management unit at high speed In the method
The call information storage unit of the first processor unit manages session information extracted from the call control packet,
When the media control unit of the first processor unit establishes a session and starts transmission / reception of media packets, the media control unit acquires parameters related to the established session from the call information storage unit and offloads the established session. Determine whether to register the settings,
The offload setting processing unit of the first processor unit, when the media control unit determines that the offload setting is performed for the established session, determines the offload registration management unit based on the information given from the media control unit. On the other hand, a communication method characterized by registering offload settings for an established session. A communication apparatus comprising: a first processor unit that performs call control and media packet transfer; and a second processor unit that performs high-speed transfer of a media packet of an offload-set session registered in the offload registration management unit. A communication program executed by the first processor unit,
The first processor unit is
A call information storage unit managing session information extracted from the call control packet;
When a session is established and media packet transmission / reception is started, parameters related to the established session are acquired from the call information storage unit, and it is determined whether or not to register offload settings for the established session. A media control unit;
When the media control unit determines to set offload for the established session, the offload setting management unit is registered with the offload setting for the established session based on the information given from the media control unit. A communication program that functions as an offload setting processing unit.

Images