WO2015052866A1 - 端末装置、端末装置制御方法および端末装置制御プログラム - Google Patents
端末装置、端末装置制御方法および端末装置制御プログラム Download PDFInfo
- Publication number
- WO2015052866A1 WO2015052866A1 PCT/JP2014/004518 JP2014004518W WO2015052866A1 WO 2015052866 A1 WO2015052866 A1 WO 2015052866A1 JP 2014004518 W JP2014004518 W JP 2014004518W WO 2015052866 A1 WO2015052866 A1 WO 2015052866A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- flow
- packet
- instruction information
- policy
- unit
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/10—Flow control between communication endpoints
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/31—Flow control; Congestion control by tagging of packets, e.g. using discard eligibility [DE] bits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/66—Substation equipment, e.g. for use by subscribers with means for preventing unauthorised or fraudulent calling
- H04M1/667—Preventing unauthorised calls from a telephone set
- H04M1/67—Preventing unauthorised calls from a telephone set by electronic means
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
- H04L45/306—Route determination based on the nature of the carried application
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/38—Flow based routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/20—Traffic policing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
Definitions
- the present invention relates to a terminal device capable of communicating with the outside, a terminal device control method for controlling the terminal device, and a terminal device control program for controlling the terminal device.
- Open flow is known as a protocol in which a control device controls a switch that transfers a packet. OpenFlow is defined in Non-Patent Document 1.
- the control device sets a flow entry in the switch. Then, the switch processes the received packet according to the flow entry.
- the flow entry is information that defines how to process a packet (for example, transfer, discard, etc.).
- the flow entry is set for each packet flow.
- the switch receives a packet and there is a flow entry corresponding to the flow of the packet, the switch processes the packet according to the flow entry.
- the switch notifies the control device to that effect. Then, the control device determines a flow entry corresponding to the flow of the packet and sets it in the switch.
- Examples of messages transmitted and received between the control device and the switch in OpenFlow include “Packet_in”, “Flow_mod”, “Packet_out”, and “Flow_removed”.
- Packet_in is a message sent from the switch to the control device. “Packet_in” is used to send a packet for which no corresponding flow entry exists from the switch to the control device.
- Flow_mod is a message sent from the control device to the switch.
- Flow_mod is a message for adding, changing, or deleting a flow entry from the control device to the switch.
- Packet_out is a message sent from the control device to the switch.
- Packet_out is a message instructing packet output from the port.
- Flow_removed is a message sent from the switch to the control device.
- Flow_removed is a message that notifies the control device when a flow entry is not used for a certain period of time and is deleted from the switch due to a timeout.
- the switch transmits statistical information of the flow corresponding to the deleted flow entry to the control device.
- Patent Document 1 describes a system to which OpenFlow is applied. Then, if the control device verifies an unauthorized address that spoofs the source MAC (Media Access Control) address or IP (Internet Protocol) address, and detects a false certificate, it sets a flow entry in the switch that does not permit packet transfer It is described to do.
- MAC Media Access Control
- IP Internet Protocol
- terminal devices that can communicate with the outside.
- These terminal devices communicate according to various installed applications.
- such communication may include communication that is not intended by the user.
- an application disguised as an application that is unlikely to communicate for example, a battery saving application
- the terminal device has no general-purpose means for recognizing what kind of communication is being performed and realizing communication control based on the recognition result. Therefore, as described above, communication unintended by the user or the like may occur.
- an object of the present invention is to provide a terminal device, a terminal device control method, and a terminal device control program that can prevent the occurrence of communication unintended by a user or the like.
- a terminal apparatus includes a communication control unit that controls a packet transfer unit that transmits a packet, and an instruction information providing unit that gives instruction information representing an instruction to the communication control unit to the communication control unit, and the communication control unit includes: If a new flow is detected, a flow detection notification indicating that the new flow has been detected is sent to the instruction information adding unit, and if the instruction information adding unit receives the flow detection notification, the flow communication is permitted. Determining whether or not to permit communication, and providing the communication control means with instruction information for instructing to transmit a packet of a flow as a route through the access network designated by the instruction information providing means. To do.
- the communication control means controls the packet transfer means for transmitting the packet
- the instruction information giving means gives the instruction information indicating the instruction to the communication control means to the communication control means
- the communication When the control unit detects a new flow, it sends a flow detection notification, which is a notification that the new flow has been detected, to the instruction information providing unit.
- the instruction information providing unit receives the flow detection notification, the flow communication is performed.
- the communication control unit is determined to permit the communication, the communication control unit is provided with instruction information for instructing to transmit the packet of the flow through the access network designated by the instruction information providing unit. It is characterized by that.
- the terminal device control program comprises a communication control means for controlling a packet transfer means for transmitting a packet, and an instruction information giving means for giving instruction information representing an instruction for the communication control means to the communication control means.
- a terminal device control program installed in a computer used as a device, and when the communication control means detects a new flow, instructs the computer for a flow detection notification that is a notification that the new flow has been detected.
- the flow detection notification process sent to the information providing means and the instruction information giving means determine whether or not to allow communication of the flow upon receiving the flow detection notification.
- Instruction control information for instructing transmission via the access network designated by the instruction information giving means as a route Characterized in that to execute the instruction information addition processing to give.
- OFC OpenFlow Controller
- OFS OpenFlow Switch
- FIG. 1 is a block diagram showing an example of a terminal device of the present invention.
- the terminal device 1 of this invention is a smart phone and a tablet-type terminal device, for example, it is not limited to these.
- the terminal device 1 of the present invention includes a communication control management unit 2, a control application unit 3, a packet transfer unit 4, a protocol processing unit 5, an application unit 6, and communication interface units 7a to 7n.
- Each application unit 6 is realized by a CPU that operates in accordance with each application software (hereinafter simply referred to as an application) installed in the terminal device 1. Each application unit 6 performs an operation according to the corresponding application.
- the packet transfer unit 4 processes a packet that the application unit 6 intends to transmit to the outside according to the communication control management unit 2 (for example, transfers or discards the packet).
- the communication control management unit 2 controls packet processing in the packet transfer unit 4 based on an instruction from the control application unit 3.
- the communication control management unit 2 corresponds to the OFC in the open flow
- the packet transfer unit 4 corresponds to the OFS in the open flow.
- the communication control management unit 2 may control the packet transfer unit 4 with a protocol other than OpenFlow.
- the communication control management unit 2 is referred to as OFC2.
- the packet transfer unit 4 is referred to as OFS4.
- OFC2 and OFS4 are realized by a CPU that operates according to a program.
- a program for realizing the function as the OFC 2 is called an OFC base.
- the control application unit 3 is realized by a CPU that operates according to control application software.
- the control application software is referred to as a control application.
- the control application unit 3 sends instruction information indicating an instruction for the OFC 2 to the OFC 2. This instruction information is referred to as a policy.
- the communication interface units 7a to 7n are communication interfaces corresponding to various communications such as 3G (3rd Generation), LTE (Long Term Evolution), and Wi-Fi (Wireless Fidelity®, registered trademark). Each of the communication interface units 7a to 7n is specifically identified as an OFS2 port.
- the protocol processing unit 5 is realized by a CPU that operates according to a program.
- the protocol processing unit 5 provides a communication service for the application.
- the protocol processing unit 5 is a part in which protocols such as TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) used in the transmission path are implemented.
- the protocol processing unit 5 monitors whether or not each of the communication interface units 7a to 7n is usable, and notifies the monitoring result to the OFC 2 (specifically, a node state management unit 25 described later, see FIG. 3). . Further, the protocol processing unit 5 notifies the OFC 2 (specifically, a protocol state management unit 26 described later, see FIG. 3) of the own port number and the process ID (Identification) corresponding to the own port number.
- the self port number is a self port number such as TCP or UDP in each communication instructed by the application.
- Each program for realizing the functions of the control application and OFC2, OFS4, and protocol processor 5 can be referred to as a terminal device control program.
- the terminal device control program is stored in a storage device (not shown) of the terminal device 1, and the CPU of the terminal device 1 reads the terminal device control program, and according to the program, OFC2, control application unit 3, OFS4, protocol processing unit 5 Works as.
- FIG. 2 is an explanatory view schematically showing a policy.
- the policy includes a search key used when searching for a policy and an action indicating an operation specified by the policy.
- Information specifying traffic is described as a search key.
- an application ID is described as a search key.
- the application ID is an identifier of an application that transmits / receives the control target traffic within the terminal device. If the application ID is not specified in the policy, it is regarded as a wild card.
- the identification information of the flow of the control target traffic may be described as a search key.
- the flow identification information includes, for example, an address and a port number. If the address or port number used as flow information is not specified, it is regarded as a wild card.
- the search key may include a priority.
- the priority indicates the priority of the policies when there are a plurality of policies corresponding to the common traffic. Therefore, when a plurality of policies are obtained as a result of the OFC 2 searching for a policy corresponding to a certain traffic, the OFC 2 finally uses only the policy with the highest priority among the policies as a search result.
- the search key includes a policy ID which is a policy identifier.
- the mode for specifying the action includes a mode for specifying the route of the traffic according to the traffic.
- an access network Wi-Fi, 3G, etc.
- Wi-Fi Wi-Fi, 3G, etc.
- the packet of the traffic is transmitted from the communication interface unit corresponding to Wi-Fi.
- a flag As an aspect for specifying an action, there is an aspect in which whether or not to execute a predetermined operation is determined by a flag.
- the predefined operation for example, “when OFC 2 detects a new flow that meets the conditions specified by the policy, OFC 2 notifies the control application unit 3 of the transmission source application and destination of the new flow. And the like. Assume that the flag corresponding to this operation is set to ON in the policy.
- the OFC 2 detects a new traffic (more specifically, a new flow corresponding to the specified condition) and searches for this policy as a policy corresponding to the traffic, the OFC 2 executes the above-described operation specified by the flag. To do. If this flag is set to OFF in the policy, the OFC 2 does not execute the above operation even if this policy is retrieved.
- an application corresponding to the application unit 6 that has transmitted a packet to the OFS 4 is referred to as an application that has transmitted the packet.
- the OFC 2 when the OFC 2 detects a packet of traffic specified by the policy, the OFC 2 notifies the control application unit 3 of the application and destination information of the packet according to the policy. For example, the control application unit 3 transmits the information notified from the OFC 2 to the user of the terminal device 1.
- the control application unit 3 sends a policy to the OFC 2 to transmit the packet of the traffic to the access network designated by the user.
- the control application unit 3 sends a policy to the OFC 2 to discard the traffic packet.
- the operation of the control application unit 3 for such an OFC 2 and the operation of the OFC 2 for the control application unit 3 are features of the present invention.
- the Northbound API Application programming I Interface
- the control application unit 3 and the OFC 2 is a feature of the present invention.
- production of the communication which a user does not intend can be prevented by such a characteristic of this invention.
- the control application unit 3 receives a communication permission or non-permission instruction from the user is illustrated here.
- the control application unit 3 performs communication according to the contents defined by MDM (Mobile Device Management), for example. Permission or non-permission may be determined.
- MDM Mobile Device Management
- FIG. 3 is a block diagram showing the details of OFC2.
- the OFC 2 includes an API management unit 21, a policy management unit 22, a statistical information management unit 23, a flow management unit 24, a node state management unit 25, and a protocol state management unit 26.
- the API management unit 21 relays API calls from the control application unit 3 and responses from the OFC 2 side. For example, when the API management unit 21 receives a policy addition, change, or deletion notification from the control application unit 3, the API management unit 21 sends the notification to the policy management unit 22. When the policy management unit 22 transmits information to the control application unit 3, the API management unit 21 relays the information. For example, when the API management unit 21 receives a request for traffic statistical information from the control application unit 3, the API management unit 21 sends the request to the statistical information management unit 23. When the statistical information management unit 23 transmits statistical information to the control application unit 3 in response to the request, the API management unit 21 relays the statistical information.
- the policy management unit 22 holds each policy sent from the control application unit 3.
- the policy management unit 22 searches for a policy corresponding to the packet, Perform the action specified by the retrieved policy. More specifically, when the flow management unit 24 receives a packet sent from the OFS 4 together with “Packet_in“ ”to the OFC 2, the flow management unit 24 sends the packet to the policy management unit 22 to request a policy search. In the following description, this operation may be called a policy inquiry.
- the policy management unit 22 searches for a policy in response to the request, and executes an operation defined by the searched policy.
- the policy management unit 22 returns the action and the policy ID to the flow management unit 24 to return to the flow management unit. 24 is instructed to create a flow entry.
- the statistical information management unit 23 holds statistical information sent from the OFS 4.
- the flow management unit 24 communicates with the OFS 4 and manages information related to the flow entry set in the OFS 4.
- the flow management unit 24 receives a packet (packet for which no matching flow entry exists in OFS 4) together with “Packet_in” from the OFS 4, the flow management unit 24 sends the packet to the policy management unit 22 to request a policy search.
- the flow management unit 24 creates a flow entry based on the action and the flow information of the packet, The flow entry is transmitted to OFS4.
- the flow management unit 24 manages information related to the flow entry.
- FIG. 4 is a schematic diagram illustrating an example of information managed by the flow management unit 24.
- the flow management unit 24 creates and holds information illustrated in FIG. 4 for each flow entry.
- Each piece of information managed by the flow management unit 24 includes a search key for searching for each piece of information.
- the search key describes the flow flow identification information controlled by the flow entry.
- the flow identification information includes, for example, an address and a port number. If the address or port number used as flow information is not specified, it is regarded as a wild card.
- the search key also includes the policy ID used when setting the flow entry.
- each information managed by the flow management unit 24 also describes an action set in the flow entry.
- the flow management unit 24 sends the statistical information received from the OFS 4 together with “Flow_removed” to the statistical information management unit 23.
- the statistical information management unit 23 performs the statistical information. It is possible to recognize which application corresponds to statistical information.
- the node state management unit 25 acquires information indicating whether or not each communication interface unit 7a to 7n (see FIG. 1) is usable from the protocol processing unit 5 and holds it.
- the policy management unit 22 (specifically, an action selection unit 224, which will be described later, see FIG. 5) refers to this information to determine whether or not each communication interface unit 7a to 7n is usable. To do.
- the policy management unit 22 (specifically, the action selection unit 224), when the communication interface unit to which the packet is to be transmitted cannot be used, the action specifying the access network corresponding to the communication interface unit in the retrieved policy. Even if it is described, the action is not sent to the flow management unit 24. As a result, a flow entry for sending a packet from an unusable communication interface unit is not created.
- the protocol state management unit 26 holds information indicating the correspondence between the flow information of a packet and the application ID (application identifier) of the transmission source application of the packet.
- the protocol state management unit 26 acquires its own port number and process ID from the protocol processing unit 5 (see FIG. 1).
- the protocol state management unit 26 creates information in which a UID (User ID) corresponding to the process ID is associated with an application ID corresponding to the UID, and holds the information.
- the flow information (own port number) is associated with the application ID, and the application ID can be searched from the flow information.
- the mode in which the protocol state management unit 26 holds information indicating the correspondence between the flow information and the application ID is not particularly limited, and may not be the above mode.
- FIG. 5 is a block diagram showing details of the policy management unit 22.
- the policy management unit 22 includes a policy table storage unit 221, a policy entry management unit 222, a policy search unit 223, and an action selection unit 224.
- the policy table storage unit 221 is a storage device (for example, a memory) that stores policies.
- the policy entry management unit 222 When the policy entry management unit 222 receives a policy addition, change, or deletion notification from the control application unit 3 via the API management unit 21, the policy entry management unit 222 updates the policy in the policy table storage unit 221 according to the notification. For example, the policy entry management unit 222 newly stores the policy in the policy table storage unit 221, changes the contents of the policy stored in the policy table storage unit 221, or is stored in the policy table storage unit 221. Or delete existing policies.
- the policy search unit 223 When a packet is sent from the flow management unit 24, the policy search unit 223 causes the protocol state management unit 26 to search for an application ID corresponding to the flow information using the flow information (port number in this example) of the packet as a key. .
- the protocol state management unit 26 returns the searched application ID to the policy search unit 223.
- This application ID is the application ID that is the source of the packet.
- the policy search unit 223 searches the policy table storage unit 221 for a policy using the application ID and the flow information of the packet sent from the flow management unit 24 as a key.
- the action selection unit 224 selects an action defined by the policy searched by the policy search unit 223. For example, in the policy searched by the policy search unit 223, when an action to perform flow detection notification is defined, the action selection unit 224 performs flow detection notification to the control application unit 3. Further, for example, when an action for specifying an access network is described in the policy, the action selection unit 224 returns the action and the policy ID to the flow management unit 24, thereby causing the flow management unit 24 to execute the flow. Instructs creation of an entry.
- FIG. 6 is a sequence diagram showing an example of the processing progress of the present invention.
- APP means an application.
- the content of the policy sent from the control application unit 3 to the OFC 2 and the content of the flow detection notification sent from the OFC 2 to the control application unit 3 are shown surrounded by broken lines.
- the control application unit 3 “when the OFC 2 detects a new flow corresponding to the condition specified by the policy, the OFC 2 notifies the control application unit 3 of the transmission source application and the destination of the new flow”.
- the OFC 2 is instructed to add a policy that defines the conditions (step S1).
- the OFC 2 holds this policy.
- the control application unit 3 may set the flag corresponding to the flow detection notification to ON.
- the case where the control application unit 3 specifies the application ID of the transmission source application as the flow detection notification condition in the policy search key sent from the control application unit 3 to the OFC 2 in step S1 will be described as an example. To do.
- a case where an application ID of a game application is designated as the application ID will be described as an example.
- control application unit 3 may create the above policy based on information input from the user, or may create the above policy based on contents defined by the MDM. .
- step S2 the application unit 6 corresponding to the game application specified in the policy transmits a packet addressed to the game site (game Web site) to the OFS 4 (step S2).
- step S3 the OFS 4 does not store a flow entry corresponding to this packet flow. Therefore, the OFS 4 transmits the packet to the OFC 2 by “Packet_in” (step S3).
- OFC2 detects a new flow by receiving “Packet_in”. Then, OFC 2 searches for a policy corresponding to the new flow. Here, the policy acquired in step S1 is obtained as a search result. The OFC 2 executes a flow detection notification according to this policy. That is, the OFC 2 notifies the control application unit 3 of the application (game application) that is the transmission source of the new flow and the destination (game site) of the new flow (step S4).
- the control application unit 3 determines whether or not to allow communication by the new flow according to the flow detection notification received in step S4. Then, the control application unit 3 instructs the OFC 2 to add a policy according to the determination result.
- a method for determining whether or not to allow communication of a new flow is not particularly limited.
- the control application unit 3 displays a new flow transmission source application and a destination Web site on a display unit (not shown) of the terminal device 1, and determines whether or not to permit communication of the new flow from the user. May be specified. That is, the control application unit 3 may determine whether to permit communication according to the user's determination. In this case, for example, the control application unit 3 also designates an access network serving as a communication path by the user. Further, the control application unit 3 may determine whether or not to permit communication in accordance with the contents predetermined by the MDM. In this case, the access network used when communication is permitted may be determined by the MDM.
- control application unit 3 permits communication of a new flow and sets the communication path to Wi-Fi
- the control application unit 3 creates a policy to transmit using Wi-Fi, and adds the policy Is instructed to the OFC 2 (step S5).
- the control application unit 3 makes the priority of the policy created in step S5 higher than the priority of the policy created in step S1.
- the OFC 2 newly holds a policy in accordance with an instruction from the control application unit 3.
- the application unit 6 corresponding to the game application transmits a packet addressed to the game site to the OFS 4 even after step S2 (step S6). Even at the time of step S6, the flow entry corresponding to the flow of this packet is not stored in the OFS4. Therefore, the OFS 4 transmits the packet to the OFC 2 by “Packet_in” (step S7).
- the packet received by the OFC 2 in step S7 has the game application as the transmission source and the game site as the destination.
- the OFC 2 searches for the policy acquired in step S5 as the policy corresponding to the flow information of this packet.
- the policy acquired in step S1 is also searched, but the priority of the policy acquired in step S5 is higher. Therefore, the OFC 2 uses the policy acquired in step S5 as a search result.
- the OFC 2 creates a flow entry based on the retrieved policy. That is, the OFC 2 determines a flow entry that determines that the packet flow received from the OFS 4 together with “Packet_in” in step S7 is transmitted from the Wi-Fi communication interface unit, and sends the flow entry to the OFS 4 (step S8). Then, OFS 4 stores the flow entry.
- the OFC 2 specifically sends “Flow_mod (Wi-Fi)” and “Packet_out” to the OFS 4.
- the OFS 4 transmits the packet addressed to the game site received from the application unit 6 from the Wi-Fi communication interface unit according to the flow entry (step S9). As a result, the packet is transmitted to the game site.
- step S8 Until the OFC 2 sets a flow entry for the OFS 4 in step S8, even if the application unit 6 corresponding to the game application sends a packet addressed to the game site to the OFS 4, the packet is not transmitted to the game site. That is, until a flow entry is set in step S8, communication of a packet addressed to the game site with the game application as a transmission source is not performed.
- OFS 4 transmits the packet addressed to the game site received from application unit 6 corresponding to the game application to the Wi-Fi communication interface unit according to the flow entry. Send from.
- the application unit 6 corresponding to the game application transmits a packet addressed to a site other than the game site (hereinafter referred to as Web site X) to the OFS 4 (step S12).
- the OFS 4 does not store a flow entry corresponding to this packet flow. Therefore, the OFS 4 transmits the packet to the OFC 2 by “Packet_in” (step S13).
- OFC2 detects a new flow by receiving “Packet_in”. Then, OFC 2 searches for a policy corresponding to the new flow.
- the policy acquired in step S1 is obtained as a search result. Note that in the policy acquired in step S5, the destination that is the search key does not match the destination of the new flow, so the policy acquired in step S5 is not searched.
- OFC2 performs flow detection notification according to the policy. That is, the OFC 2 notifies the control application unit 3 of the application (game application) that is the transmission source of the new flow and the destination (Web site X) of the new flow (step S14).
- the control application unit 3 determines whether or not to allow communication by the new flow according to the flow detection notification received in step S14, and sends a policy corresponding to the determination result to the OFC 2.
- a case where the control application unit 3 does not permit communication of a new flow will be described as an example. For example, it is assumed that an application that is a transmission source of a new flow and a Web site that is a destination are displayed on a display unit (not shown) of the terminal device 1. Since the destination is a Web site that is not intended by the user, it is assumed that the new flow communication is not permitted by the user.
- the control application unit 3 For the flow corresponding to the transmission source (game application) and destination (Web site X) notified in step S14, the control application unit 3 creates a policy to drop the packet and adds the policy Is instructed to OFC2 (step S15). However, the control application unit 3 sets the priority of the policy created in step S15 to be higher than the priority of the policy created in step S1. The OFC 2 newly holds a policy in accordance with an instruction from the control application unit 3.
- the application unit 6 corresponding to the game application transmits a packet addressed to the website X to the OFS 4 even after step S12 (step S16). Even at the time of step S16, the flow entry corresponding to the flow of this packet is not stored in the OFS4. Therefore, the OFS 4 transmits the packet to the OFC 2 by “Packet_in” (step S17).
- the packet received by the OFC 2 in step S17 has the game application as the transmission source and the Web site X as the destination.
- the OFC 2 searches for the policy acquired in step S15 as a policy corresponding to the flow information of this packet.
- the policy acquired in step S1 is also searched, but the priority of the policy acquired in step S15 is higher. Therefore, the OFC 2 uses the policy acquired in step S15 as a search result.
- the OFC 2 creates a flow entry based on the retrieved policy. That is, the OFC 2 determines a flow entry that determines discarding the flow of the packet received from the OFS 4 together with “Packet_in” in step S17, and sends the flow entry to the OFS 4 (step S18). Then, OFS 4 stores the flow entry.
- the OFC 2 specifically sends “Flow_mod (Drop)” to the OFS 4.
- the OFS 4 discards the packet addressed to the Web site X received from the application unit 6 according to the flow entry. Thereafter, when the OFS 4 receives a packet addressed to the website X from the application unit 6 corresponding to the game application, the OFS 4 discards the packet according to the flow entry set in step S18.
- FIG. 7 is a sequence diagram showing an example of the processing progress of OFC2.
- the processing progress of the OFC 2 in the operation shown in FIG. 6 will be described with reference to FIGS.
- the API management unit 21 in the OFC 2 receives the instruction and adds the policy to the policy management unit 22. Is instructed (step S21).
- the policy management unit 22 holds the policy added according to the instruction.
- This policy is a policy for instructing the flow detection notification described in step S1 above.
- the application ID of the game application is specified in the search key (see FIG. 2) in the policy.
- the flow management unit 24 receives the “Packet_in”. As a result, the flow management unit 24 also receives a packet for which no corresponding flow entry exists in the OFS 4. This packet is a packet whose source is a game application. In this packet, for example, “54321” is defined as the own port number. The flow management unit 24 sends this packet to the policy management unit 22, and requests a policy search corresponding to the packet (step S22).
- the policy management unit 22 detects reception of “Packet_in” in response to this request (in other words, detects a new flow). Then, the policy management unit 22 instructs the protocol state management unit 26 to search for the application ID corresponding to the packet based on the flow information of the packet acquired in step S22 (step S23). That is, the policy management unit 22 instructs the protocol state management unit 26 to search for the application ID of the application that is the transmission source of the packet. In this example, it is assumed that the policy management unit 22 designates its own port number (in this example, “54321”) in the flow information as a key.
- the protocol state management unit 26 holds the flow information of the packet and the application ID of the transmission source application of the packet.
- the protocol state management unit 26 holds a correspondence relationship between the own port number, process ID, UID, and application ID included in the packet.
- the protocol state management unit 26 Upon receiving a search instruction from the policy management unit 22, the protocol state management unit 26 searches for the application ID corresponding to the own port number “54321” and notifies the policy management unit 22 of the application ID.
- the policy management unit 22 acquires and accumulates the searched application ID (step S24). This application ID is the application ID of the game application.
- the policy management unit 22 searches for a policy using the application ID and the destination of the packet acquired in step S22 as a search key. Then, the policy instructed to be added in step S1 is obtained. Note that in the policy instructed to be added in step S1, only the application ID is specified, and the destination is not specified, so it is a wild card.
- the policy management unit 22 notifies the control application unit 3 of the new flow transmission source application (game application) and the destination of the new flow (game site) in accordance with this policy. This operation corresponds to step S4 (flow detection notification) shown in FIG. In this operation, the policy management unit 22 sends a notification to the API management unit 21 (step S25), and the API management unit 21 sends the notification to the control application unit 3 (step S26).
- the control application unit 3 creates a policy to transmit using Wi-Fi for the flow corresponding to the notified transmission source (game application) and destination (game site). Assume that the OFC 2 is instructed to add a policy. This operation corresponds to step S5 shown in FIG. Then, the API management unit 21 in the OFC 2 receives the instruction and instructs the policy management unit 22 to add the policy (step S27).
- Step S7 when the OFS 4 transmits “Packet_in” in step S7 (see FIG. 6), the flow management unit 24 receives the “Packet_in”. As a result, the flow management unit 24 also receives a packet for which no corresponding flow entry exists in the OFS 4. The flow management unit 24 sends this packet to the policy management unit 22, and requests a policy search corresponding to the packet (step S28). Step S28 is the same operation as step S22.
- the policy management unit 22 instructs the protocol state management unit 26 to search for the application ID corresponding to the packet based on the flow information of the packet acquired in step S28 (step S29). Then, in response to this instruction, the protocol state management unit 26 searches for the application ID and notifies the policy management unit 22 of it. The policy management unit 22 acquires and accumulates the searched application ID (step S30).
- the operations in steps S29 and S30 are the same as the operations in steps S23 and S24.
- the application ID of the game application is obtained.
- the destination of the packet sent to the policy management unit 22 in step S28 is the game site.
- the policy management unit 22 searches for the policy acquired in step S5 using these pieces of information as search keys. Note that the policy acquired in step S1 (policy using only the application ID as a search key) can also be searched. However, as described above, the priority of the policy acquired in step S5 is higher. Accordingly, the policy management unit 22 searches for the policy acquired in step S5. In this policy, an action for specifying Wi-Fi as an access network is described. Therefore, the policy management unit 22 instructs the flow management unit 24 to create a flow entry by sending this action and the policy ID of the searched policy to the flow management unit 24 (step S31).
- the flow management unit 24 creates a flow entry that defines that the packet flow received from the OFS 4 together with “Packet_in” in step S7 is transmitted from the Wi-Fi communication interface unit. Then, the flow management unit 24 instructs the OFS 4 to set the flow entry. This operation corresponds to step S8 shown in FIG. At this time, the flow management unit 24 sends “Flow_mod (Wi-Fi)” and “Packet_out” to the OFS 4.
- FIG. 8 is a sequence diagram showing an example of processing progress of the policy management unit 22. With reference to FIG. 8 and FIG. 5, the processing progress of the policy management unit 22 in the operation shown in FIG. 7 will be described.
- the policy entry management unit 222 in the policy management unit 22 receives the instruction and stores the policy table.
- the policy to be added is stored in the unit 221 (step S41).
- This policy is a policy for instructing the flow detection notification described in step S1 above.
- the search key in the policy specifies the application ID of the game application.
- step S22 the flow management unit 24 sends the packet to the policy management unit 22, and requests a policy search according to the packet. Then, the policy search unit 223 in the policy management unit 22 receives this packet and the policy search request.
- This packet is a packet received by the flow management unit 24 together with “Packet_in”, and the transmission source of this packet is a game application.
- the policy search unit 223 instructs the protocol state management unit 26 to search for the application ID corresponding to the packet (step S23), and is searched by the protocol state management unit 26.
- the obtained application ID is acquired (step S24). This application ID is the application ID of the game application.
- the policy search unit 223 searches the policy stored in the policy table storage unit 221 for a policy using the application ID acquired in step S24 and the destination of the packet acquired in step S22 as a search key. (Step S42). Then, the policy search unit 223 acquires the searched policy from the policy table storage unit 221 (step S43). This policy is the policy stored in the policy table storage unit 221 in step S41.
- the policy search unit 223 instructs the action selection unit 224 to select the action of the policy acquired in step S43 (step S44).
- the action selection unit 224 selects an action in the policy in response to this instruction.
- an action “notify the control application unit 3 of the transmission source application and the destination of the new flow” is defined by the flag. Therefore, the action selection unit 224 selects this action, and notifies the control application unit 3 of the application (game application) that is the transmission source of the new flow and the destination (game site) of the new flow according to the action.
- the action selection unit 224 sends a notification to the API management unit 21 (step S25). And the API management part 21 transmits the notification to the control application part 3 (refer step S26 shown in FIG. 7).
- step S27 when the API management unit 21 instructs the policy management unit 22 to add a policy, the policy entry management unit 222 receives the instruction and stores it in the policy table storage unit 221.
- the policy to be added is stored (step S45).
- This policy is the policy described in step S5. That is, for a flow in which the transmission source is a game application and the destination is a game site, it is a policy that stipulates transmission using Wi-Fi.
- step S28 the flow management unit 24 sends the packet to the policy management unit 22 and requests a policy search corresponding to the packet. Then, the policy search unit 223 in the policy management unit 22 receives this packet and the policy search request.
- the policy search unit 223 instructs the protocol state management unit 26 to search for the application ID corresponding to the packet (step S29), and is searched by the protocol state management unit 26.
- the obtained application ID is acquired (step S30). This application ID is the application ID of the game application.
- the policy search unit 223 searches the policy stored in the policy table storage unit 221 using the application ID acquired in step S30 and the destination of the packet acquired in step S28 as a search key. (Step S46). Then, the policy search unit 223 acquires the searched policy from the policy table storage unit 221 (step S47). This policy is the policy stored in the policy table storage unit 221 in step S45.
- the policy search unit 223 instructs the action selection unit 224 to select the action of the policy acquired in step S47 (step S48).
- the action selection unit 224 selects an action in the policy in response to this instruction.
- an action for specifying Wi-Fi as an access network is described. Therefore, the action selection unit 224 transmits the action and the policy ID of the policy to the flow management unit 24, and instructs the flow management unit 24 to create a flow entry (step S31).
- the operation of the flow management unit 24 that has received this instruction has been described with reference to FIG.
- the OFC 2 detects a new flow
- a notification that a new flow has been detected (flow detection notification) is transmitted to the control application unit 3.
- the control application unit 3 determines whether to permit communication of the new flow. Therefore, according to the present invention, it is possible to prevent occurrence of communication unintended by the user or the like.
- the flow detection notification includes flow source application and destination information. Accordingly, the user or the like can easily determine whether or not an unintended communication flow has occurred.
- the flow to be notified of the flow detection is determined by the policy instructed by the control application unit 3 in step S1 (see FIG. 6). Therefore, the control application unit 3 does not need to receive a flow detection notification for each detected new flow, and can receive a flow detection notification only when a new flow corresponding to a specified condition occurs.
- the OFC 2 controls the OFS 4 according to the open flow. Accordingly, the OFC 2 can control the operation of the OFS 4 widely.
- the control application unit 3 gives a policy to the OFC 2, and the OFC 2 can widely control the operation of the OFS 4 according to the policy.
- the control application unit 3 adds a policy for designating a flow to be notified of flow detection to the OFC 2 in step S1.
- a policy need not be used.
- the OFC 2 may transmit a flow detection notification to the control application unit 3 every time a new flow is detected. Even with such a configuration, it is possible to prevent communication unintended by the user or the like.
- the control application unit 3 when the control application unit 3 adds a policy for designating a flow to be notified of flow detection to the OFC 2 in step S1, the application ID of the flow transmission source is described in the policy.
- the case where this is done has been described as an example. That is, the case where the flow subject to flow detection notification is designated by the application ID of the transmission source has been described as an example.
- the control application unit 3 may specify the flow that is the target of the flow detection notification in another manner.
- the control application unit 3 may specify a flow that is a target of flow detection notification by a flow destination.
- the control application unit 3 may describe a destination to be specified as flow identification information in the search key in the policy.
- the control application unit 3 determines that a flow detection notification is transmitted when a new flow that matches the specified application ID and destination is detected by specifying both the flow application ID and the flow destination. May be.
- FIG. 9 is a block diagram showing the main part of the terminal device of the present invention.
- the terminal device of the present invention includes communication control means 91 and instruction information giving means 92.
- the communication control unit 91 controls a packet transfer unit (for example, OFS4) that transmits a packet.
- the instruction information providing unit 92 (for example, the control application unit 3) provides the communication control unit 91 with instruction information (for example, policy) indicating an instruction to the communication control unit 91.
- the communication control unit 91 When the communication control unit 91 detects a new flow, the communication control unit 91 sends a flow detection notification, which is a notification that the new flow has been detected, to the instruction information adding unit 92.
- the instruction information adding unit 92 determines whether to permit communication of the flow. Then, when it is determined that the communication is permitted, the instruction information providing unit 92 provides the communication control unit 91 with instruction information for instructing transmission of the flow packet through the access network specified by the instruction information adding unit 92. .
- Such a configuration can prevent communication unintended by the user or the like.
- the communication control unit 91 After the communication control unit 91 is provided with instruction information for instructing transmission of a flow packet using the access network designated by the instruction information adding unit 92 as a route, the communication interface corresponding to the access network receives the flow packet.
- the packet transfer unit may be controlled to transmit from the unit.
- the communication control means 91 may be configured to send the application software that is the flow transmission source and the flow destination information to the instruction information addition means 92 as the flow detection notification.
- the flow detection notification may be sent to the instruction information adding unit 92.
- the instruction information giving unit 92 gives the communication control unit 91 instruction information for instructing a flow that is a target of flow detection notification by designating either or both of application software that is a flow transmission source and a flow destination. It may be a configuration.
- the communication control means 91 may be configured to control the packet transfer means according to the open flow.
- the present invention is preferably applied to a terminal device that can communicate with the outside.
- Terminal device 2 OFC (communication control manager) 3 Control application part 4 OFS (packet transfer part) DESCRIPTION OF SYMBOLS 5 Protocol processing part 6 Application part 7a-7n Communication interface part 21 API management part 22 Policy management part 23 Statistics information management part 24 Flow management part 25 Node state management part 26 Protocol state management part 221 Policy table storage part 222 Policy entry management part 223 Policy search unit 224 Action selection unit
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
2 OFC(通信制御管理部)
3 制御アプリケーション部
4 OFS(パケット転送部)
5 プロトコル処理部
6 アプリケーション部
7a~7n 通信インタフェース部
21 API管理部
22 ポリシ管理部
23 統計情報管理部
24 フロー管理部
25 ノード状態管理部
26 プロトコル状態管理部
221 ポリシテーブル記憶部
222 ポリシエントリ管理部
223 ポリシ検索部
224 アクション選択部
Claims (10)
- パケットを送信するパケット転送手段を制御する通信制御手段と、
前記通信制御手段に対する指示を表す指示情報を前記通信制御手段に与える指示情報付与手段とを備え、
前記通信制御手段は、
新たなフローを検出した場合、当該新たなフローを検出した旨の通知であるフロー検出通知を前記指示情報付与手段に送り、
前記指示情報付与手段は、
前記フロー検出通知を受けると前記フローの通信を許可するか否かを決定し、通信を許可すると決定した場合に、前記フローのパケットを当該指示情報付与手段が指定するアクセス網を経路として送信することを指示する指示情報を前記通信制御手段に与える
ことを特徴とする端末装置。 - 通信制御手段は、
フローのパケットを指示情報付与手段が指定するアクセス網を経路として送信することを指示する指示情報を与えられた後に、当該フローのパケットを前記アクセス網に対応する通信インタフェース部から送信するようにパケット転送手段を制御する
請求項1に記載の端末装置。 - 通信制御手段は、
フロー検出通知として、フローの送信元となるアプリケーションソフトウェアおよびフローの宛先の情報を指示情報付与手段に送る
請求項1または請求項2に記載の端末装置。 - 指示情報付与手段は、
フロー検出通知の対象となるフローを指示する指示情報を通信制御手段に与え、
前記通信制御手段は、
前記指示情報で指示されたフローを新たに検出した場合に、フロー検出通知を前記指示情報付与手段に送る
請求項1から請求項3のうちのいずれか1項に記載の端末装置。 - 指示情報付与手段は、
フローの送信元となるアプリケーションソフトウェアおよびフローの宛先のいずれか一方あるいは両方を指定することによってフロー検出通知の対象となるフローを指示する指示情報を通信制御手段に与える
請求項4に記載の端末装置。 - 通信制御手段は、
オープンフローに従ってパケット転送手段を制御する
請求項1から請求項5のうちのいずれか1項に記載の端末装置。 - 通信制御手段が、
パケットを送信するパケット転送手段を制御し、
指示情報付与手段が、
前記通信制御手段に対する指示を表す指示情報を前記通信制御手段に与え、
前記通信制御手段が、
新たなフローを検出した場合、当該新たなフローを検出した旨の通知であるフロー検出通知を前記指示情報付与手段に送り、
前記指示情報付与手段が、
前記フロー検出通知を受けると前記フローの通信を許可するか否かを決定し、通信を許可すると決定した場合に、前記フローのパケットを当該指示情報付与手段が指定するアクセス網を経路として送信することを指示する指示情報を前記通信制御手段に与える
ことを特徴とする端末装置制御方法。 - 通信制御手段が、
フローのパケットを指示情報付与手段が指定するアクセス網を経路として送信することを指示する指示情報を与えられた後に、当該フローのパケットを前記アクセス網に対応する通信インタフェース部から送信するようにパケット転送手段を制御する
請求項7に記載の端末装置制御方法。 - パケットを送信するパケット転送手段を制御する通信制御手段と、前記通信制御手段に対する指示を表す指示情報を前記通信制御手段に与える指示情報付与手段とを備え、端末装置として用いられるコンピュータに搭載される端末装置制御プログラムであって、
前記コンピュータに、
前記通信制御手段が、新たなフローを検出した場合、当該新たなフローを検出した旨の通知であるフロー検出通知を前記指示情報付与手段に送るフロー検出通知処理、および、
前記指示情報付与手段が、前記フロー検出通知を受けると前記フローの通信を許可するか否かを決定し、通信を許可すると決定した場合に、前記フローのパケットを当該指示情報付与手段が指定するアクセス網を経路として送信することを指示する指示情報を前記通信制御手段に与える指示情報付与処理
を実行させるための端末装置制御プログラム。 - コンピュータに、
通信制御手段が、フローのパケットを指示情報付与手段が指定するアクセス網を経路として送信することを指示する指示情報を与えられた後に、当該フローのパケットを前記アクセス網に対応する通信インタフェース部から送信するようにパケット転送手段を制御する制御処理
を実行させる請求項9に記載の端末装置制御プログラム。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2015541420A JP6394606B2 (ja) | 2013-10-11 | 2014-09-03 | 端末装置、端末装置制御方法および端末装置制御プログラム |
US15/027,551 US10555217B2 (en) | 2013-10-11 | 2014-09-03 | Terminal device, terminal-device control method, and terminal-device control program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013-214024 | 2013-10-11 | ||
JP2013214024 | 2013-10-11 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015052866A1 true WO2015052866A1 (ja) | 2015-04-16 |
Family
ID=52812703
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/004518 WO2015052866A1 (ja) | 2013-10-11 | 2014-09-03 | 端末装置、端末装置制御方法および端末装置制御プログラム |
Country Status (3)
Country | Link |
---|---|
US (1) | US10555217B2 (ja) |
JP (1) | JP6394606B2 (ja) |
WO (1) | WO2015052866A1 (ja) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9521071B2 (en) * | 2015-03-22 | 2016-12-13 | Freescale Semiconductor, Inc. | Federation of controllers management using packet context |
JP7120059B2 (ja) * | 2019-02-05 | 2022-08-17 | 日本電信電話株式会社 | 負荷分散システム及び負荷分散方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008191862A (ja) * | 2007-02-02 | 2008-08-21 | Nec Corp | 通信装置および通信制御方法 |
JP2008546321A (ja) * | 2005-06-01 | 2008-12-18 | クゥアルコム・インコーポレイテッド | マルチホーミングマルチモード通信デバイスにおけるデータインターフェースの選択 |
JP2009177262A (ja) * | 2008-01-22 | 2009-08-06 | Softbank Mobile Corp | 携帯情報処理装置、携帯情報処理方法及び携帯情報処理プログラム |
WO2014038135A1 (ja) * | 2012-09-06 | 2014-03-13 | パナソニック株式会社 | 通信装置、転送制御方法及び転送制御プログラム |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4555592B2 (ja) * | 2004-03-31 | 2010-10-06 | 富士通株式会社 | パケット処理システム |
JP4454661B2 (ja) * | 2005-03-31 | 2010-04-21 | 富士通株式会社 | フレーム転送装置 |
JP5720668B2 (ja) * | 2010-02-16 | 2015-05-20 | 日本電気株式会社 | パケット転送装置、通信システム、処理規則の更新方法およびプログラム |
CN102783098B (zh) * | 2010-03-05 | 2016-01-20 | 日本电气株式会社 | 通信系统、路径控制设备、分组转发设备以及路径控制方法 |
JP5716741B2 (ja) * | 2010-06-09 | 2015-05-13 | 日本電気株式会社 | 通信システム、論理チャネル制御装置、制御装置、通信方法およびプログラム |
US20120099591A1 (en) * | 2010-10-26 | 2012-04-26 | Dell Products, Lp | System and Method for Scalable Flow Aware Network Architecture for Openflow Based Network Virtualization |
US9118716B2 (en) | 2010-12-09 | 2015-08-25 | Nec Corporation | Computer system, controller and network monitoring method |
US8873392B1 (en) * | 2011-06-09 | 2014-10-28 | Marvell International Ltd. | Method and apparatus for controlling the flow of packets in a data network |
BR112014004700A2 (pt) * | 2011-09-01 | 2017-03-28 | Nec Corp | terminal de comunicação, método de comunicação, sistema de comunicação e programa |
WO2013042373A1 (en) * | 2011-09-21 | 2013-03-28 | Nec Corporation | Communication apparatus, control apparatus, communication system, communication control method, communication terminal and program |
JP2015508950A (ja) * | 2012-01-30 | 2015-03-23 | 日本電気株式会社 | コントロール方法、コントロール装置、通信システムおよびプログラム |
WO2013146785A1 (ja) * | 2012-03-28 | 2013-10-03 | 日本電気株式会社 | 通信システム、通信装置、制御装置、通信装置の制御方法及びプログラム |
US9729424B2 (en) * | 2012-06-11 | 2017-08-08 | Futurewei Technologies, Inc. | Defining data flow paths in software-defined networks with application-layer traffic optimization |
US9306840B2 (en) * | 2012-09-26 | 2016-04-05 | Alcatel Lucent | Securing software defined networks via flow deflection |
US9252972B1 (en) * | 2012-12-20 | 2016-02-02 | Juniper Networks, Inc. | Policy control using software defined network (SDN) protocol |
US9461967B2 (en) * | 2013-07-18 | 2016-10-04 | Palo Alto Networks, Inc. | Packet classification for network routing |
US9350607B2 (en) * | 2013-09-25 | 2016-05-24 | International Business Machines Corporation | Scalable network configuration with consistent updates in software defined networks |
-
2014
- 2014-09-03 WO PCT/JP2014/004518 patent/WO2015052866A1/ja active Application Filing
- 2014-09-03 US US15/027,551 patent/US10555217B2/en active Active
- 2014-09-03 JP JP2015541420A patent/JP6394606B2/ja active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008546321A (ja) * | 2005-06-01 | 2008-12-18 | クゥアルコム・インコーポレイテッド | マルチホーミングマルチモード通信デバイスにおけるデータインターフェースの選択 |
JP2008191862A (ja) * | 2007-02-02 | 2008-08-21 | Nec Corp | 通信装置および通信制御方法 |
JP2009177262A (ja) * | 2008-01-22 | 2009-08-06 | Softbank Mobile Corp | 携帯情報処理装置、携帯情報処理方法及び携帯情報処理プログラム |
WO2014038135A1 (ja) * | 2012-09-06 | 2014-03-13 | パナソニック株式会社 | 通信装置、転送制御方法及び転送制御プログラム |
Also Published As
Publication number | Publication date |
---|---|
US20160242074A1 (en) | 2016-08-18 |
JP6394606B2 (ja) | 2018-09-26 |
US10555217B2 (en) | 2020-02-04 |
JPWO2015052866A1 (ja) | 2017-03-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10462260B2 (en) | Context-aware and proximity-aware service layer connectivity management | |
WO2014119715A1 (ja) | 通信端末、通信方法、プログラム、通信システムおよび情報処理装置 | |
US9535638B2 (en) | Directly transferring data between devices | |
JP2016119711A (ja) | 無線lanシステムにおける無線lan通信端末、その通信制御方法、及びプログラム | |
CN112566164B (zh) | 一种通信系统及服务质量控制方法 | |
WO2015052867A1 (ja) | 端末装置、端末装置制御方法および端末装置制御プログラム | |
US9838481B2 (en) | Provisioning of network communication parameters based on device type | |
JP6394606B2 (ja) | 端末装置、端末装置制御方法および端末装置制御プログラム | |
KR101541348B1 (ko) | Gtp 네트워크 기반 세션 관리 방법 및 장치 | |
US9942823B2 (en) | Communication terminal, communication method, and communication program | |
US20170127472A1 (en) | Method and wireless device for controlling disconnection of a wireless device in a wi-fi direct group of a wireless network | |
US10341453B2 (en) | Facilitating in-network content caching with a centrally coordinated data plane | |
WO2014034119A1 (en) | Access control system, access control method, and program | |
US20150156164A1 (en) | Communication system, communication control method, communication relay system, and communication relay control method | |
JP2023537134A (ja) | ネットワーク移行方法、装置及び機器 | |
JP2014207583A (ja) | ユーザ装置、及び通信制御方法 | |
WO2015052870A1 (ja) | 端末装置、端末装置制御方法、および端末装置制御プログラム | |
JP2013055467A (ja) | ゲートウェイ、制御装置、並びに端末制御システム及び方法 | |
JP6640065B2 (ja) | 通信装置、通信制御装置、通信方法、通信制御方法、及びプログラム | |
US20170019845A1 (en) | Communication terminal, communication method, and program-containing storage medium | |
JP2009049508A (ja) | 通信装置およびプログラム、並びに、ネットワーク選択方法 | |
WO2023280044A1 (zh) | 中继选择方法、中继信息传输方法、装置及终端 | |
WO2015052869A1 (ja) | 端末装置、端末装置制御方法、および端末装置制御プログラム | |
WO2014175250A1 (ja) | 通信端末、制御装置、通信システム、通信方法及びプログラム | |
KR101235782B1 (ko) | 단말기 원격 제어를 통한 통신망 보호 시스템 및 그 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14852896 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2015541420 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15027551 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14852896 Country of ref document: EP Kind code of ref document: A1 |