JP5555191B2 - Network system - Google Patents

Description

The present invention relates generally to network systems , and more specifically to network systems suitable for the future Internet.

The current network environment faces serious challenges due to the emergence of new technologies and new needs. In the near future, not only will there be more mobile (wireless) user units, but there will also be more machine-to-machine type communication devices. In this specification, the term “machine-to-machine type communication” refers to a form of data communication between elements that do not require human interaction or human intervention (eg, a low power sensor or electronic tag and a management device). Communication). Almost all such mobile communication devices will be connected to the Internet. As a result, the future Internet will be a collection of many different types of network technologies (eg, wired networks, wireless LANs, cellular (3G and LTE) networks, sensor networks, etc.). Therefore, an integrated network system is required for future mobile environments.

  In many cases, users are interested in information or services relating to actual events such as videos or descriptions within a web page. In other words, the user is interested in the data and content rather than the topological location of the data and content. Therefore, content-centric or service-centric communication technologies will be needed for future Internet services. Furthermore, user-centric communication technology must be supported for the future Internet, as each user may have multiple devices online simultaneously.

  The current Internet communication architecture interacts based on a single protocol (Internet Protocol (IP)) (eg, everything on IP, IP on everything). However, the current Internet architecture has a problem in using IP addresses. In particular, an IP address serves as both a host identifier (ID) and a locator. In other words, the IP address is used in the network layer to specify a position on a specific topology, that is, as a locator for routing a packet, and an ID for identifying an interface by a network host (and thus an identification of a communication session). Information) is also used in the transport layer and application layer. Basically, current Internet architecture requires that the IP address remain unchanged during the session. This means that changing the IP address indicates that the IDs of both endpoints have changed, indicating that the communication session has ended. The two roles of IP address are not appropriate for future mobile environments. This is because the mobility request requires a change of the IP address. To solve the problem with the dual role of IP address, the roles of locator and identifier should be separated to avoid aborting the communication session.

  Many solutions have been proposed to support the mobility of communication devices in current Internet architectures (eg, Mobile IPv6 (MIPv6), Proxy Mobile IPv6 (PMIPv6), Network Mobility (NEMO), etc.). However, since these solutions only provide a form of patch-on, these solutions do not integrate well with mobility control for various types of mobile communication devices, and therefore These add complexity and reduce network performance.

  Therefore, there is debate about radically changing the current Internet architecture. In particular, IDs including Host Identify Protocol (HIP), Site Multi-homing by IPv6 Intermediation (SHIM6), Locator / Identifier Separation Protocol (LISP), Host Name and Identifier System (HNIS), and Mobile-Oriented Future Internet (MOFI) / Various techniques for locator separation (separation of ID and locator) have been proposed.

  The current Internet architecture is convenient for communications directed to end-to-end messages in which packets are exchanged between end hosts. However, most Internet traffic today is content-oriented or data-oriented, and Internet users are interested in information, data, content or services about real-world events, not locations or devices. Video streaming is a major contributor to global Internet traffic growth in recent years, accounting for 50% of total traffic. Trends in communication scenarios indicate that “what” is being exchanged is more important than “where” information is. The Internet should therefore be fundamentally replaced with a new architecture. There are several protocols for content distribution. For example, Content-Centric Network (CCN) and Publish / Subscribe Internet Routing Paradigm (PSIRP). For example, CCN is disclosed in Non-Patent Document 1 and Non-Patent Document 2.

Future Content Network Group, "Why do we need a Content-centric Future Internet?", Online, found on January 29, 2011, (http://www.future-internet.eu/fileadmin/documents/prague_documents/FIA-FCN_Internet_Architecture_20090507 .pdf) Gareth Tyson, "A Middleware Approach to Building Content-Centric Applications", online, found on January 29, 2011, (http://eprints.comp.lancs.ac.uk/2337/1/PhD.pdf)

  Although the proposed ID / locator separation technology and the proposed content delivery networking architecture are both revolutionary steps for the future Internet, they still have some limitations. Proposed ID / locator separation technologies (HIP, SHIM6, LISP, HNIS and MOFI) focus only on end-to-end communication and are not designed to handle content delivery networking. Also, the proposed ID / locator separation technique is not insufficient to support a huge number of devices. In the proposed ID / locator separation technology, all of the ID / location information has to be managed in order to link and map the device to the ID. However, the conventional management technology is a machine including a low power sensor and an electronic tag. It has been developed without considering the increase in to-machine type communication devices.

  On the other hand, in the proposed content delivery networking architecture (CCN and PSIRP), the network system delivers content of interest to the user, but does not achieve the object-aware networking features. In other words, the proposed content distribution network side only pays attention to the content that the communication requesting user wants to watch or listen to, the communication receiving user, the device of the communication receiving user, or a specific service (the communication requesting user benefits) Do not consider). In this specification, the term “object-aware networking” refers to, for example, each communication requesting user's intention (eg, communication receiving user, communication receiving device and specific service (communication requesting user benefiting). Also means a form of information exchange or service that the network side considers in addition to the content that the communication requesting user wants to see and listen to. In this context, the term “object” is intended to include not only content but also users, devices and services. Although current Internet traffic is content-oriented, future Internet architectures must support various types of communication models including user-to-user, user-to-service and user-to-content.

Therefore, according to the present invention, users, devices, and contents are associated with their position indicators, but the position indicators are different from their names or IDs, and the communication requesting user specifies the desired contents. A network system is provided that is convenient for both base communication and end-to-end communication in which a communication requesting user designates a communication receiving user or a communication receiving device.

According to the present invention, a network system comprising a plurality of subscriber domains (10), a plurality of object provider domains (20), a network operator domain (30), and a message routing server device (40), A plurality of first users are subscribed to each of the subscriber domains (10), and each of the first users owns or manages at least one first user device (11); Each of the subscriber domains (10) includes a first proxy device (12), and the first proxy device (12) includes the subscriber domain (where the first proxy device (12) is arranged). 10) acts as a default gateway and an access router for the first user equipment (11) of the first user subscribed to 10) A plurality of second users are subscribed to each of the object provider domains (20), and each of the second users has a user name and a user ID that are universally unique to the second users. And each of the second users owns or manages at least one second user device (21), and each of the second user devices (21) is the second user device. (21) has a universally unique device name and device ID, and each device name includes the user name of the second user for the second user device (21). Each of which includes an indicator indicating the network operator domain (30) to which the second user is subscribed, each of the object provider domains (20) being a second proxy device The second proxy device (23) includes the second user of the second user who is subscribed to the object provider domain (20) in which the second proxy device (23) is disposed. For each user device (21), each of the second proxy devices (23) has a second proxy address, and each of the object provider domains (20) An object source server (22) for storing metadata information essential for using the content, each content having a content name, the content name being universally unique to the content, Object provider in which the object source server (22) to be stored is arranged A network operator domain (30) linked to the domain domain (20), each of the object provider domains (20) being a second user subscribing to the object provider domain (20) A provider domain memory (23M) for storing information for each of the second user equipment (21), wherein the information for each of the second user equipment is a device name of the second user equipment, A device ID of the second user device, a user name of the second user for the second user device, a user ID of the second user for the second user device, a communication type indicator indicating the type of communication, and a second The second proxy device of the second proxy device of the object provider domain (20) to which the user Each of the network operator domains (30) is linked to some of the plurality of subscriber domains (10) and some of the plurality of object provider domains (20); A first user subscribing to a subscriber domain (10) linked to a network operator domain (30) and a second subscribing to an object provider domain (20) linked to a network operator domain (30) The user has subscribed to the network operator domain (30), and each of the network operator domains (30) includes a directory server device (31) including a directory server memory (31M), and the directory server memory (31M). ) Information for each second user subscribing to the network operator domain (30) is stored, the information for each second user is the user name of the second user, the user of the second user The directory server memory (31M) includes the ID and the second proxy address of the second proxy device of the object provider domain (20) to which the second user is subscribed. ) Stored for each of the publishable contents stored therein, and the information for each of the publishable contents includes a content name of the content, metadata information for the content, and an object for storing the content Second proxy device of the object provider domain (20) where the source server (22) is located Each of the directory server devices (31) has a directory server address, and the message routing server device (40) includes a plurality of network operator domains (30). A message routing server memory (40M), which stores information for each network operator domain (30) and information for each network operator domain (30) Shows the relationship between the indicator of the network operator domain (30) included in the user name, device name or content name and the directory server address of the directory server device (31) in the network operator domain (30). The message routing server device (40) has a network operator domain included in the user name, device name, or content name included in the message based on the information stored in the message routing server memory (40M). A network system for specifying the directory server address from the indicator of (30) is provided.

According to the present invention, users, devices and content are associated with these location indicators (second proxy addresses), but the location indicators are different from their names or IDs. The network system is convenient for both content-based communication in which a communication requesting user specifies desired content and end-to-end communication in which the communication requesting user specifies a communication receiving user or a communication receiving device. Content, devices or users and their locations are managed in each of the network operator domain (30) and each of the object provider domains (20), and an indicator of the network operator domain included in the device name, user name or content name; The relationship of the directory server device (31) in the network operator domain (30) is managed by the message routing server device (40). When the device name, user name or content name is indicated in the message, the location of the device, user or content can be identified.

1 is a schematic diagram showing a network system according to the present invention. It is the schematic which shows the said network system with which object registration is performed. It is a figure which shows the registration table produced by object registration. It is a figure which shows another one registration table produced by object registration. FIG. 2 is a schematic diagram illustrating the network system in which a user intention analysis process for a content-based communication service is executed. It is a figure which shows the cache table used with the said network system . It is a figure which shows another one cache table used with the said network system . It is a figure which shows the mapping table used with the said network system . It is the schematic which shows the said network system in which a user intention analysis process is performed for a user-to-user communication service. It is a figure which shows the management table used with the said network system . It is a figure which shows another one management table used with the said network system . It is the schematic which shows the said network system in which a user intention analysis process is performed for a user-to-user communication service. 1 is a schematic diagram illustrating a network system in which object subscription / data delivery processing is performed for a content-based communication service. FIG. It is the schematic which shows the network system with which an object application and data delivery process are performed for an end-to-end communication service.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
"Network System Overview"
FIG. 1 shows a layout of a network system according to the present invention. This network system is suitable for the future Internet. This network includes a plurality of subscriber domains 10, a plurality of object provider domains 20, a plurality of network operator domains 30, and a server device 40. The server device 40 is hereinafter referred to as a global name resolution server (GNRS). Called.

  Each of the subscriber domains 10 may be a physical network and a user access network to which a plurality of users can subscribe (belong). Therefore, each of the subscriber domains 10 has a plurality of user devices 11 that can communicate by wire or wirelessly. Such user access networks may include, for example, home networks, company networks, campus networks, and mobile broadband access networks. The user device 11 may be a normal computer, a tablet computer, a mobile phone, and a machine-to-machine type communication device including a sensor and an electronic tag. One user may have one user device 11 or multiple user devices 11.

  Each of the object provider domains 20 can also be referred to as a publisher domain and may be a network owned by a content provider or portal service provider. Each of the object provider domains 20 can have a plurality of object source servers 22 or a plurality of user devices 21. Each of the object source servers 22 stores various content data related to content that would be requested by a communication requesting user belonging to any one of the subscriber domains 10. Each object source server 22 stores metadata information for content data. Metadata information is systematic information that describes or describes an information resource, indicates its location, or facilitates reading, using, or managing it. The metadata information indicates, for example, a title, a short outline of the content, a content creator, a creation date, a file size, a content type (moving image, still image, text or music), and a file format. Thus, the metadata information has information elements that are indispensable for the use of the content associated with the metadata information. One user may have one user device 21 or may have a plurality of user devices 21.

  Each of the object provider domains 20 is a logical network as viewed from a communication requesting user who wants to communicate to obtain services or content. This is because each domain 20 is referred to as an object provider domain because the domain 20 is owned by a content provider or portal service provider and has at least one device that will satisfy the request of the communication requesting user. It means that there is. A domain 10 can also be an object provider domain 20 if one of the subscriber domains 10 is owned by a content provider or portal service provider and has at least such a device.

  Each network operator domain 30 is a physical network owned by a global or wide area network operator. Such network operators may be Internet service providers (ISPs) or mobile broadband network operators that provide wired or wireless physical networking. As shown in FIG. 1, at least one object provider domain 20 and at least one subscriber domain 10 are linked to each network operator domain 30. A user of the user object provider domain 20 or the subscriber domain 10, that is, a subscriber (affiliation) is a subscriber of the object provider domain 20 or the network operator domain 30 to which the subscriber domain 10 is linked. (Member).

  Each of the subscriber domains 10 has a proxy server device 12 called a subscriber object proxy (SOP). The SOP (first proxy device) 12 is a functional entity that is operated under the control of a machine-readable program, and is a subscriber (user device 11) in the subscriber domain 10 in which the SOP 12 is located. Acts as a default gateway and access router.

  As described in detail later, the SOP 12 is a feature for executing a user-intent-resolution process. When the SOP 12 requests a content-based communication service from the user equipment 11 in the subscriber domain 10 and receives an object request message indicating the content name, the user intent analysis process may include metadata information used for the content and The address of the POP 23 to be routed by communication is specified. When the SOP 12 requests an end-to-end communication service from the user equipment 11 in the subscriber domain 10 and receives an object request message indicating the user name and the type of communication or indicating only the device name, the user intention analysis processing is performed. The device ID of the communication destination (one of the user devices 21) to be routed by communication is specified.

  Each SOP 12 stores the user IDs of all users who are subscribed to the subscriber domain 10 in which the SOP 12 is located. Further, each SOP 12 stores the device IDs of the devices of all users who are subscribed to the subscriber domain 10 in which the SOP 12 is arranged.

  Each SOP 12 has an SOP cache memory (first proxy cache memory) 12C shown in FIG. 6, and the SOP cache memory 12C has an SOP cache table. The SOP cache table records the content name of content (content data) stored in one of the object source servers 22 in the object provider domain 20, the content data, and metadata information for the content data. For each content, the content name, content data, and metadata information are associated as one information set in the SOP cache table. In content-based communication, when the SOP 12 receives content data from one of the object provider domains 20 that transmitted the content data in response to a request by the communication requesting user device 11, each set is cached in the SOP cache memory 12C. .

  In addition, the SOP cache table includes the user name and user ID of the user of one object provider domain 20, the device name and device ID of the user device 21 owned or managed by the user, and the communication supported by the user device 21. Records the communication type indicator indicating the type (for example, e-mail transmission, VoIP (voice over IP), device-to-device communication, server client communication, etc.) and the POP address of the POP 23 of the object provider domain 20 where the user device 21 is located. To do. For each device, the user name, user ID, communication type indicator, device name, device ID, and POP address are associated as one information set in the SOP cache table. In the end-to-end communication, when the SOP 12 receives a set from one object provider domain 20 that has transmitted such a set, each set is cached in the SOP cache memory 12C.

  Each of the object provider domains 20 has a proxy server device 23 called a publisher object proxy (POP). The POP (second proxy device) 23 is a functional entity operated under the control of a machine-readable program, and an object such as a content provider network or a portal service provider network on which the POP 23 is arranged. It acts as a default gateway and access router for subscribers of provider domain 20 (at least one of object source server 22 and user equipment 21).

  Each POP has a POP memory (provider domain memory) 23M shown in FIG. 3, and the POP memory 23M has a POP registration table. The POP registration table includes the content name of content (content data) stored in the object source server 22 in the object provider domain 20 in which the POP 23 is located, the address of the object source server 22, and metadata for the content data. Record information and internal use flags or public flags. For each content, the content name, the address of the object source server, the metadata information, and the flag are associated as one information set in the POP registration table. Each set is permanently stored in the POP memory 23M by object registration described later.

  Also, as shown in FIG. 11, the POP memory 23M has a POP subscriber management table. The POP subscriber management table includes the user name and user ID of the user of one object provider domain 20 in which the POP 23 is arranged, the device name and device ID of the user device 21 owned or managed by the user, the user device 21 Record the communication type indicator indicating the type of communication supported by the POP 23, and the POP address of the POP 23. For each device, the user name, user ID, communication type indicator, device name, device ID and POP address are associated as one information set in the POP subscriber management table. In this way, each POP 23 stores the user IDs of all users who are subscribed to the object provider domain 20 in which the POP 23 is located, and the users who are subscribed to the object provider domain 20 in which the POP 23 is located. All device IDs of the device are stored.

  Each network operator domain 30 has a directory server 31 called an object directory server (ODS). The ODS 31 is operated by a global or wide area network operator under the control of a machine readable program.

Each ODS 31 has an ODS memory (directory server memory) 31M shown in FIG. 4, and the ODS memory 31M has an ODS registration table. The ODS registration table includes the content name of the content stored in the object source server 22 of the object provider domain 20 to which the network operator domain 30 in which the ODS 31 is arranged is linked, and the address of the POP 23 for routing to the object source server 22. As well as metadata information for the content. For each content, the content name, the address of the object source server, and the metadata information are associated as one information set in the ODS registration table. Each set is permanently stored in the ODS memory 31M by object registration.

  As shown in FIG. 10, the ODS memory 31M has an ODS subscriber management table. The ODS subscriber management table stores the user name and user ID of a user who subscribes to the object provider domain 20 linked to the network operator domain 30 where the ODS 31 is located, and the user's device in the object provider domain 20. The POP address of the POP 23 for routing is recorded. For each user, the user name, user ID and POP address are associated as one information set in the ODS subscriber management table. Thus, each ODS 31 stores the user IDs and locations of all users who are subscribed to the object provider domain 20 linked to the network operator domain 30 where the ODS 31 is located.

  Each ODS 31 has an ODS cache memory (directory server cache memory) 31C shown in FIG. 7, and the ODS cache memory 31C has an ODS cache table. The ODS cache table includes a content name of content (content data) stored in one object source server 22 in the object provider domain 20 linked to another network operator domain 30 in which another ODS 31 is arranged, its object source The address of the POP 23 for routing to the server 22 and the metadata information for the content data are recorded. For each content, the content name, POP address, and metadata information are associated as one information set in the ODS cache table. When the ODS 31 receives metadata information and a POP address from the GNRS 40 in a user intention analysis process for content-based communication, each set is cached in the ODS cache memory 12C.

  The ODS cache table includes the user name and user ID of a user who subscribes to the object provider domain 20 linked to another network operator domain 30 in which another ODS 31 is arranged, and a user owned or managed by the user. Record the device name and device ID of the device 21, a communication type indicator indicating the type of communication supported by the user device 21, and the POP address of the POP 23 for routing to the user's device in the object provider domain 20. To do. For each user, the user name, user ID, communication type indicator, device name, device ID, and POP address are associated as one information set in the ODS cache table. When the ODS 31 receives the contents of a set from the GNRS 40 in the user intention analysis process for end-to-end communication, each set is cached in the ODS cache memory 12C.

The information set cached in each element (SOP cache memory 12C and ODS cache memory 31C) can be erased according to an appropriate method. For example,
(i) A cached set is deleted when a predetermined time has elapsed after storage.
(ii) When the cache memory is full or nearly full and the new set is to be cached, the oldest cached set is erased to accept the new set.
(iii) The least frequently used set is erased when the cache memory is full or nearly full and a new set is to be cached.

  The network operator domain 30 also includes a plurality of routers 32 for routing signals to other domains.

In the network system according to the embodiment of the present invention, each of a user and a device must be given a global name and ID in order to identify the user and the device. Thus, the user has a user name (as a global name) and a user ID and is identified by the user name or user ID, and the device has a device name (as a global name) and device ID, and the device name or It is specified by the device ID. Further, the content has a content name (as a global name) and is specified by the content name. A global name is a unique name that is globally significant and can be used from anywhere. The global name must be a string that is shown in a variable-length character set and can be read and remembered by humans. On the other hand, although the ID is a globally unique character string, it may not be stored in humans. Each global name can be indicated by the communication requesting user (human) in the early stages of communication, while each ID is used in the communication protocol.

Table 1 shows rules regarding the structure of global names and IDs in the network system according to the embodiment of the present invention.

  In Table 1, the first character “u”, “d” or “c” is a kind of separator for facilitating understanding of the intention of the communication requesting user. That is, “u”, “d”, and “c” represent a user name, a device name, and a content name, respectively.

In the global user name or global device name in Table 1, the part “user_name” is a unique user that is significant in the network operator domain 30 to which the user is subscribed (also significant in the subscriber domain 10 or the object provider domain 20). Name. In the global user name or global device name, the portion “subscribe_name” is a unique name of a global or wide area network operator operating the network operator domain 30 to which the user is subscribed. Thus, the portion “subscribe_name” indicates the network operator domain 30 to which the user or device is subscribed. In the global device name, the part “ device_name ” is a unique device name that is significant in the network operator domain 30 to which the device is subscribed (also significant in the subscriber domain 10 or the object provider domain 20). It should be noted that the part “user_name” is included in each global device name as well as each global user name. In each global device name, the part “user_name” indicates the owner or administrator of the device.

  In the global content name of Table 1, the part “URI” is a Uniform Resource Identifier excluding the “http” or “https” scheme. In order for a communication requesting user to access a website and receive specific content data (eg, video, still image, text or music) from the website, the specific content data on the website corresponding to the “URI” The global content name is used when you want to specify it. As can be seen from Table 1, the global content name also includes the part “subscribe_name” (more specifically, docomo.com). In the case of website access for receiving specific content data, the part “subscribe_name” in each of the global content names indicates a network operator domain 30 linked to the object provider domain 20 to which the website belongs. As understood from the above, the term “content” as “object” refers to specific content data on a website.

  In the following description, the term “global” may be omitted from the global name.

  A GNRS (message routing server device) 40 is linked to a plurality of network operator domains 30. The GNRS 40 has a GNRS memory (message sending to the server memory) 40M to store the GNRS mapping table shown in FIG. The GNRS mapping table manages the relationship between the indicator of the network operator domain 30 included in the user name or content name and the ODS 31 of the network operator domain 30. More specifically, the GNRS mapping table stores a plurality of information sets, and each information set has an address of ODS 31 and “subscribe_name”. As described above, “subscribe_name” is the name of the network operator who operates the network operator domain 30, and can be regarded as an indicator of the network operator domain 30. The part “subscribe_name” is included in all of the device name, user name, and content name. When the device name, user name or content name is indicated in the message, the GNRS 40 determines the address of the ODS 31 based on the GNRS mapping table and routes the message to the network operator domain 30 having the ODS 31.

"Register object"
With reference to FIG. 2, the operation of object registration in the network system will be described. As described above, each of the object source servers 22 stores various content data related to content satisfying a communication requesting user subscribed to any one of the subscriber domains 10. The object registration process is executed for the purpose of registering contents for the purpose of use within the object provider domain 20 or for the purpose of extensive use within the network system .

  Each operation staff of the object source server 22 is responsible for the content stored in the object source server 22 in the POP 23 (more precisely, the content data) for public (public use) or internal use (personal use). The object source server 22 can be operated to instruct the object source server 22 to send an object disclosure or personal use message to the POP 23 in the object provider domain 20 (step S1). .

  The object publication or personal use message has a content name, metadata information, a POP address of the POP 23 that is a message destination, and an internal use flag or a public flag. This message has a source address indicating the address of the object source server 22 storing the content.

If the operations staff desires that the object (content) be used only within the object provider domain 20, the operations staff chooses to add an internal use flag to the object publication or personal use message. As a result, the object source server 22 transmits an object disclosure or personal use message having an internal use flag to the POP 23 (step S1). When the POP 23 receives this message having the internal use flag, the POP 23 does not transfer the object disclosure or personal use message to any ODS 31, and the contents indicated by the object disclosure or personal use message are stored in the POP registration table (FIG. 3 Stored in). That content can only be used by subscribers in the object provider domain 20.

On the other hand, if the operation staff desires that the object (content) is widely disclosed, the operation staff chooses to add the disclosure flag to the object disclosure or personal use message . As a result, the object source server 22 transmits an object disclosure or personal use message having a disclosure flag to the POP 23 (step S1). Upon receiving this message having the public flag, the POP 23 stores the contents indicated by the object public or personal use message in its POP registration table (shown in FIG. 3). As shown in FIG. 3, in the POP registration table, each content name is associated with an address of the object source server, metadata information, and a public flag or an internal use flag. Then, the POP 23 transfers the object disclosure or personal use message to the ODS 31 of the network operator domain 30 to which the object provider domain 20 having the POP 23 is linked (step S2).

The public or personal use message, content name, indicates the metadata information, and the POP address POP23 this message is sent. Unlike the message from the object source server, this message may have no public flag because the object publication or personal use message sent from the POP 23 in step S2 shows only the contents that can be published. The object publication or personal use message sent from the POP 23 in step S2 indicates the location of the object provider domain 20 that can supply the content name, metadata information, and content. The location may be represented by the POP address of the POP 23 of the object provider domain 20 where the content is stored.

  When the object disclosure or personal use message is received from the POP 23 in step S2, the ODS 31 registers the content in the ODS 31 as a public object. More specifically, the ODS 31 stores the content indicated by the object disclosure or personal use message in its ODS registration table (shown in FIG. 4). The content can be published for subscribers in the subscriber domain 10 to which the network operator domain 30 is linked. As shown in FIG. 4, in the ODS registration table, each content name is associated with a position and metadata information.

  In addition, if there are many requests from a subscriber in a subscriber domain 10 linked to another network operator domain 30 for some publishable content, the POP 23 is linked to that subscriber domain 10. An object disclosure or personal use message is transmitted to the ODS 31 of another network operator domain 30, and the ODS 31 registers the content in the ODS 31 as a publicly available content (step S3). This message has the form as described above with respect to step S2. The ODS 31 stores the contents indicated by the object disclosure or personal use message in the same manner as described above in the ODS registration table (shown in FIG. 4). The content can be published for the subscriber in the subscriber domain 10 from which the subscriber sent the request.

"User intention analysis process"
Based on the global name (content name, user name or device name) of the object specified by the user (communication requesting user), the user intent analysis process determines what the user (communication requesting user) is looking for or communicates. Specify where the counterpart user's device (communication destination) is located. More specifically, when the specified object name is a content name, the user intention analysis process specifies specific metadata information. When the specified object is a user name or a device name, the user intention analysis specifies a device ID. In other words, the user intention analysis process translates the user intention (global name of the object) into specific metadata information or a specific device ID.

  The user intention analysis process is executed for both a content-based communication service and a user-to-user communication service. Details will be described below.

"User intention analysis for content-based communication services"
In content-based communication services (eg, website access, peer-to-peer communication, real-time streaming, file transfer services, etc.), when a user specifies a content name, the user intent analysis process identifies specific metadata information. This user intention analysis process will be described with reference to FIG.

  In the user intention analysis process for the content-based communication service, a user (communication requesting user) subscribing to (belonging to) any one of the subscriber domains 10 (for example, 10a in FIG. 5) is specified. If the user who is interested in the content that can be published (for example, moving image, still image, text, or music), the communication requesting user operates the user device 11 (for example, 11a in FIG. 5) of the communication requesting user, The user apparatus 11a is instructed to transmit an object request message to the SOP 12 (for example, 12a in FIG. 5) of the subscriber domain 10a to which the user is subscribed (step S11). In this command, the communication requesting user designates a content name (“c: URI:” as shown in Table 1) that the user is interested in. In this case, the user device 11a of the communication requesting user generates an object request message having a flag (that is, a C-flag) indicating the content name and indicating that the message requests a content-based communication service. Methods for name designation are, for example, typing, copy and paste, and clicking. The communication requesting user acquires the content name in advance by keyword search using a search engine, for example.

  When the object request message transmitted in step S11 is received, the SOP 12a determines whether or not the content name indicated by the object request message is cached in the SOP cache table (shown in FIG. 6) of the SOP 12a. When the SOP cache table stores the content name, the SOP 12a reads the content data and metadata information associated with the content name in the SOP cache table, and sends the content data to the user device 11a of the communication requesting user. And its metadata information is transmitted (step S12). The user device 11a of the communication requesting user uses the content data, so that the communication requesting user can enjoy the benefits from the content. In this case, the user intention analysis process ends, and the process does not proceed to an object application / data distribution service described later.

  If the cached information regarding the content name is not in the SOP cache table of the SOP 12a, the ODS 31 (for example, FIG. 5) in the network operator domain 30 (for example, 30a in FIG. 5) to which the subscriber domain 10a where the SOP 12a is located is linked. 5 31a), the SOP 12a transmits an object search request message (object-lookup-request message) (step S13). This is because the metadata information of the content and the position (POP address) of the object provider domain 20 to which the content is supplied are acquired. The position is represented by the POP address of the POP 23 of the object provider domain 20 to which the content is supplied. The object search request message indicates the content name sent by the object request message, and is accompanied by the C-flag sent by the object request message.

  When the object search request message transmitted in step S13 is received from the SOP 12a, the ODS 31a determines whether or not the content name indicated by the object search request message is cached in the ODS cache table (shown in FIG. 7) of the ODS 31a. . Further, the ODS 31a determines whether or not the content name indicated by the object search request message is stored in the ODS registration table shown in FIG. 4 (if this determination is affirmative, the content is stored in the object provider domain 20, for example, stored in the object source server 22 of the object provider domain 20a of FIG. 5, for example, the object source server 22a of FIG. If the information related to the content name is in the ODS cache table or the ODS registration table of the ODS 31a, the ODS 31a reads the POP address and metadata information associated with the content name in the ODS cache table or the ODS registration table. Then, the ODS 31a responds to the SOP 12a by transmitting an object-lookup-response message to the SOP 12a (step S14). This message indicates the metadata information of the requested content and the POP address of the POP 23 of the object provider domain 20 to which the requested content is provided.

  If there is no information about the content name in the ODS cache table or the ODS registration table, the ODS 31a transfers an object search request message to the GNRS 40 (step S15). When the object search request message is received from the ODS 31a, the GNRS 40 analyzes the part “subscribe_name” (see Table 1) in the content name indicated by the object search request message. Then, the GNRS 40 searches the content name portion “subscribe_name” in the GNRS mapping table (shown in FIG. 8), specifies the ODS address associated with the portion “subscribe_name”, and thereby requests the requested content. The address of the ODS 31 (for example, 31b of FIG. 5) of one network operator domain 30 (for example, the network operator domain 30b of FIG. 5) to which the object provider domain 20 (for example, 20b of FIG. 5) can be linked. get.

  Knowing the ODS address, the GNRS 40 transfers an object search request message to the ODS 31b to obtain metadata information and a POP address (step S16). Upon receiving the object search request message, the ODS 31b searches the ODS registration table (shown in FIG. 4) for the content name indicated by the object search request message, and the POP address and metadata information associated with the content name. Is read. The ODS 31b transmits an object search response message to the GNRS 40 (step S17). This message indicates the metadata information of the requested content and the POP address of the POP 23 (for example, 23b of FIG. 5) of the object provider domain 20 (for example, 20b of FIG. 5) to which the requested content is provided.

  Upon receiving the object search response message transmitted from the ODS 31b in step S17, the GNRS 40 transfers the object search response message to the ODS 31a that transmitted the object search request message (step S18). When the ODS 31a receives the object search response message transmitted from the GNRS 40 in step S17, the ODS 31a stores the metadata information and the POP address indicated by the object search response message in the ODS cache table (shown in FIG. 7) as cache information. Remember. In this storage operation, the ODS 31a also stores the content name indicated by the object search request message so that the content name is associated with the metadata information and the POP address in the ODS cache table. In this way, the ODS cache table has new cache information regarding content names, metadata information and POP addresses.

  Furthermore, when the object search response message transmitted from GNRS 40 in step S17 is received, ODS 31a transfers the object search response message to SOP 12a that transmitted the object search request message (step S19). Thus, after step S14 or S19, the SOP 12 is the user's intention (that is, the metadata information of the requested content and the POP address of the POP 23 of the object provider domain 20 in which the requested content is stored). know. The SOP 12 transmits metadata information to the user device 11 that has transmitted the object request message (step S20). Therefore, prior to receiving the content data, the user device 11 receives metadata information including elements necessary for using the content data. This speeds up or facilitates the use of content data (for example, activation of an application program and selection of a file format). Thereafter, the process proceeds to an object application / data distribution service described later.

"User intention analysis for user-to-user communication services"
The overall operation of the user intention analysis process for the user-to-user communication service is similar to the overall operation of the user intention analysis process in the content-based communication service described above. However, in this operation, a communication destination user name or device name is first designated by the communication requesting user instead of the content name. This user intention analysis processing will be described with reference to FIG. 9 and FIG.

  In user intent analysis processing for user-to-user communication services (eg, email transmission, VoIP, device-to-device communication, server client communication, etc.), any one of the subscriber domains 10 (eg, 10a in FIG. 5) If a user (communication requesting user) subscribing to (belonging to) wants to communicate with a specific communication partner user or one of the communication devices 21 owned by the communication partner user, the communication requesting user By operating the user device 11 (for example, 11a in FIG. 9) of the communication requesting user, the object request message is transmitted to the SOP 12 (for example, 12a in FIG. 9) of the subscriber domain 10a to which the communication requesting user is subscribed. Thus, the user apparatus 11a is instructed (step S31). In this command, the communication requesting user can specify the user name of the communication partner user (for example, “u: user_name @ subscribe_name” as shown in Table 1) or the device name of the communication device 21 owned by the communication partner user (for example, As shown in Table 1, d: device_name # user_name @ subscribe_name) is specified. In this case, the user apparatus 11a of the communication requesting user generates an object request message indicating a user name or a device name and having a flag (that is, an E-flag) indicating that the message requests an end-to-end communication service. . If the object request message indicates a user name, the object request message also indicates the type of communication (eg, e-mail transmission, VoIP, etc.) that the communication requesting user wants to use.

  As described above, the communication requesting user can specify the name of the communication receiving user. This is useful when the communication requesting user does not know the device name of a single device of the communication receiving user that he wishes to communicate with. In addition, the communication requesting user wants to communicate with the communication receiving user in a specific method (for example, VoIP), but the device name of the specific device that can support the specific method among a plurality of devices of the communication receiving user. This is also useful if you don't know. Alternatively, the communication requesting user may specify the device name of the communication receiving device. This is convenient when the communication requesting user already knows the specific device name of the communication destination. Methods for name designation are, for example, typing, copy and paste, and clicking.

  Upon receiving the object request message indicating the receiving user name transmitted in step S31, the SOP 12a receives the user name indicated by the object request message and associated with the type of communication indicated by the object request message. Is cached in the SOP cache table (shown in FIG. 6) of the SOP 12a. If the SOP cache table stores a username associated with the type of communication indicated by the object request message, the SOP 12a reads the device ID and POP address associated with that username in the SOP cache table; The user intention analysis process ends. When the object request message indicating the receiving device name transmitted in step S31 is received, the SOP 12a determines whether or not the device name indicated by the object request message is cached in the SOP cache table of the SOP 12a. If the device name is stored in the SOP cache table, the SOP 12a reads the device ID and the POP address associated with the device name in the SOP cache table, and the user intention analysis process ends. In either case, the process proceeds to an object application / data distribution service described later. The SOP 12a does not transmit the device ID or the POP address to the user device 11a of the communication requesting user.

If the cached information regarding the recipient user name or the recipient device name is not in the SOP cache table of the SOP 12a, the network operator domain 30 (for example, FIG. 9) to which the subscriber domain 10a where the SOP 12a is located is linked. The SOP 12a transmits an object search request message to the ODS 31 in 30a) (for example, 31a in FIG. 9) (step S33). This is because the device ID of the communication destination and the position (POP address) where the communication destination is arranged are acquired. The location can be represented by the POP address of the POP 23 of the object provider domain 20 where the communication destination is located (subscribed). The object search request message also indicates the combination of user name and communication type sent by the object request message or the device name alone, with the E-flag sent by the object request message.

  When the object search request message indicating the receiving user name transmitted in step S33 is received from the SOP 12a, the ODS 31a associates the user name indicated by the object search request message with the type of communication indicated by the object search request message. It is determined whether or not the stored user name is stored in the ODS cache table (shown in FIG. 7) of the ODS 31a. If information about the user name associated with the type of communication is in the ODS cache table of ODS 31a, ODS 31a reads the POP address and device ID associated with the user name in the table. Then, the ODS 31a responds to the SOP 12 by transmitting an object search response message to the SOP 12a (step S34). When the object search request message indicating the device name of the receiving user device transmitted in step S33 is received from the SOP 12a, the ODS 31a determines whether the device name indicated by the object search request message is stored in the ODS cache table of the ODS 31a. Judge. If there is information about the device name in the ODS cache table of the ODS 31a, the ODS 31a reads the POP address and device ID associated with the device name in the table. Then, the ODS 31a responds to the SOP 12 by transmitting an object search response message to the SOP 12a (step S34). In any case, the object search response message transmitted in step S34 indicates the device ID of the communication destination and the POP address of the POP 23 of the object provider domain 20 to which the requested communication destination is subscribed. The user intention analysis process ends, and the process proceeds to an object application / data distribution service described later. The object search response message sent in step S34 may further indicate the user name, user ID, communication type, and device name, and upon receiving this message, the SOP 12a is indicated by the message in its SOP cache table. The contents may be cached.

  When the ODS cache table of the ODS 31a does not store the information indicated by the object search request message transmitted in step S33, the ODS 31a indicates that the communication receiving user indicated by the object search request message is a subscriber of the network operator ( That is, it is determined whether or not the network operator domain 30a in which the ODS 31 exists is a linked object provider domain 20, for example, a subscriber 20a in FIG. More specifically, if the object search request message indicates the user name, the ODS 31a determines whether the user name is stored in the ODS subscriber management table (shown in FIG. 10) of the ODS 31a. The ODS subscriber management table records the global names of all users subscribed to the network operator domain 30a and the POP addresses of the object provider domain 20 to which the users are subscribed. If the object search request message indicates the device name, the ODS 31a analyzes the part “user_name” in the device name (see Table 1), and whether or not the user name is stored in the ODS subscriber management table of the ODS 31a. to decide. If the communication receiving user indicated by the object search request message is a network operator subscriber (stored in the ODS subscriber management table), the ODS 31a is associated with the user name in the ODS subscriber management table. The POP address and the user ID are read out, and an object search response message indicating the POP address and the user ID is generated. Thereafter, the ODS 31a transmits this object search response message to the SOP 12a that has transmitted the object search request message (step S35).

When the object search response message transmitted in step S35 is received from the ODS 31a, if the object request message first transmitted in step S31 indicates the user name and the communication type, the SOP 12a receives the response in the object search response message. An object search request message is generated that indicates the user ID of the side user and the type of communication, and that has the POP address of the POP 23 (for example, 23a in FIG. 9) indicated by the object search response message as the destination. When the object request message first transmitted in step S31 indicates the device name, the SOP 12a indicates the user ID of the receiving user and the device name in the object search response message, and the POP 23a indicated by the object search response message. An object search request message destined for the POP address is generated. Thereafter, the ODS 31a transmits this object search request message to the POP 23a having this POP address (step S36).

Upon receiving the object search request message sent in step S36, the POP 23a, in its POP subscriber management table (shown in FIG. 11), the user ID and the communication type or device name indicated in the object search request message. And the user name, device name, device ID and POP address associated with the user ID and communication type or device name are read out in the POP subscriber management table. Thereafter, the POP 23a generates an object search response message indicating the user name, user ID, communication type, device name, device ID, and POP address, and transmits this object search response message to the SOP 12a (step S37).

  During the transfer of the object search response message transmitted from the POP 23a in step S37, the ODS 31a relays this message and stores the contents indicated by this message as cache information in its ODS cache table (shown in FIG. 7). To do. In this way, the ODS cache table has new cache information regarding the user name, user ID, communication type, device name, device ID and POP address.

  When receiving the object search response message transmitted in step S37 from the POP 23a, the SOP 12a stores the content indicated by this message in its SOP cache table (shown in FIG. 6) as cache information. In this way, the SOP cache table has new cache information regarding the user name, user ID, communication type, device name, device ID, and POP address. The SOP 12a knows the device ID of the communication destination and the POP address of the POP 23 of the object provider domain 20 to which the requested communication destination is subscribed. The user intention analysis process ends, and the process proceeds to an object application / data distribution service described later.

On the other hand, if there is no information in the ODS subscriber management table or the ODS cache table regarding the user name or device name indicated by the object search request message transmitted from the SOP 12a in step S33, the ODS 31a sends an object search request message to the GNRS 40. Is transferred (step S40 in FIG. 12). When receiving the object search request message from the ODS 31a, the GNRS 40 analyzes the part “subscribe_name” in the user name or device name (see Table 1) indicated by the object search request message. The GNRS 40 then searches the GNRS mapping table (shown in FIG. 8) for the portion “subscribe_name” in the user name or device name to identify the ODS address associated with the portion “subscribe_name”, thereby The ODS 31 (for example, FIG. 9) of one network operator domain 30 (for example, the network operator domain 30b of FIG. 9) to which the object provider domain 20 (for example, 20b of FIG. 9) to which the communication receiving user is subscribed is linked. 31b) is obtained.

  Knowing the ODS address, the GNRS 40 transfers an object search request message to the ODS 31b (step S41). When receiving the object search request message, the ODS 31b converts the user name indicated by the object search request message or the part “user_name” in the device name indicated by the object search request message into its ODS subscriber management table (shown in FIG. 10). Search). The ODS subscriber management table records the global names of all users who subscribe to the network operator domain 30b and the POP addresses of the object provider domain 20 to which the users are subscribed. The ODS 31b reads the POP address and user ID associated with the user name in the ODS subscriber management table, and transmits an object search response message to the GNRS 40 (step S42). This message indicates the user ID of the communication receiving user and the POP address of the POP 23 (for example, 23b of FIG. 12) of the object provider domain 20 (for example, 20b of FIG. 12) to which the communication receiving user belongs.

  When receiving the object search response message from the ODS 31b transmitted in step S42, the GNRS 40 transfers the object search response message to the ODS 31a that transmitted the object search request message (step S43). The ODS 31a also transfers the object search response message to the SOP 12a that has transmitted the object search request message (step S44).

When the object search response message transmitted in step S44 is received from the ODS 31a, if the object request message first transmitted in step S31 indicates the user name and the communication type, the SOP 12a receives the response in the object search response message. An object search request message is generated that indicates the user ID of the side user and the type of communication thereof, and that is addressed to the POP address of the POP 23 (for example, 23b in FIG. 12) indicated by the object search response message. When the object request message first transmitted in step S31 indicates the device name, the SOP 12a indicates the user ID of the receiving user and the device name in the object search response message, and the POP 23a indicated by the object search response message. An object search request message destined for the POP address is generated. Thereafter, the ODS 31a transmits this object search request message to the POP 23b having this POP address (step S45).

Upon receipt of the object search request message transmitted in step S45, the POP 23b, in the POP subscriber management table (shown in FIG. 11), the user ID and the communication type or device name indicated in the object search request message. And the user name, device name, device ID and POP address associated with the user ID and communication type or device name are read out in the POP subscriber management table. Thereafter, the POP 23a generates an object search response message indicating the user name, user ID, communication type, device name, device ID, and POP address, and transmits this object search response message to the SOP 12a (step S46).

  During the transfer of the object search response message transmitted from the POP 23b in step S46, the ODS 31a relays this message, and stores the contents indicated by this message as cache information in its ODS cache table (shown in FIG. 7). To do. In this way, the ODS cache table has new cache information regarding the user name, user ID, communication type, device name, device ID and POP address.

  When receiving the object search response message transmitted in step S46 from the POP 23b, the SOP 12a stores the contents indicated by this message in its SOP cache table (shown in FIG. 6) as cache information. In this way, the SOP cache table has new cache information regarding the user name, user ID, communication type, device name, device ID, and POP address. The SOP 12a knows the device ID of the communication destination and the POP address of the POP 23 of the object provider domain 20 to which the requested communication destination is subscribed. The user intention analysis process ends, and the process proceeds to an object application / data distribution service described later.

  Therefore, after step S34, S36 or S46, the SOP 12 knows the user's intention (that is, the device ID of the device of the communication receiving user and the POP address of the POP 23 of the object provider domain 20 to which the communication receiving user belongs).

"Object application / data distribution"
The operation of the object application / data distribution process of this network system will be described. Object application / data distribution processing is also performed for both content-based communication services and user-to-user communication services. Details will be described below. In the object application / data distribution process, “subscribe” means applying to use (view or listen to) a content or service.

"Object application and data distribution for content-based communication services"
Prior to the object application / data distribution process for the content-based communication service, the above-described user intention analysis process for the content-based communication service is completed, and the user device 11 of the communication requesting user (for example, 11a in FIG. 13). ) First sent the object request message (eg, 12a in FIG. 13) must know the user's intention, ie, the POP address of the object provider domain 20 (eg, 20b in FIG. 13). In this state, as shown in FIG. 13, the SOP 12a transmits an object application request message to the POP 23 (for example, POP 23b in FIG. 13) specified by the POP address acquired in the user intention analysis process (step S51). ). This object application request message indicates the content name used in the object request message. The object application request message also indicates the device ID of the user device 11 of the communication requesting user.

  Upon receiving an object-subscribe-request message from the SOP 12a, the POP 23b searches the POP registration table (shown in FIG. 3) for the content name and the object source server address associated with the content name. Thus, the address of the object source server 22 (for example, 22b in FIG. 13) that can provide the requested content is obtained.

  Knowing the address of the object source server, the POP 23b transfers the object application request message to the object source server 22b (step S52). When receiving the object application request message indicating the content name, the object source server 22b searches the object source server 22b for the content data associated with the content name, and the user device 11a transmitted in the object application request message. The requested content data is transmitted to the user device 11a of the communication requesting user according to the device ID (step S53). In this way, the communication requesting user can use the content executed based on the content data and the metadata information.

  The router 32 that relays the content data between the user device 11 of the communication requesting user and the POP 23 may create a copy of the content data, or cache the copy together with the content name. This can improve the download speed when other users who are subscribed to the same network operator domain 30 request the same content.

  The SOP 12 that transferred the content data to the user device 11 of the communication requesting user in step S53 (this SOP also transferred the metadata information to the user device 11 of the communication requesting user in step S20 in the user intention analysis process) is the content data. And a copy of the metadata information and cache those copies along with the content name for the subscriber domain 10 where the SOP 12 is located. The result of this caching is included in the SOP cache table (shown in FIG. 6) described in relation to steps S11 and S12 in the user intention analysis process. Therefore, when the user equipment 11 of another communication requesting user in the same subscriber domain 10 sends another object request message requesting the same content to the SOP 12, the SOP 12 sends an object search request message to the ODS 31. The content data can be transmitted to the user device 11 without transmitting the object application request message to the POP23.

"Object application and data distribution for user-to-user communication services"
Prior to the object application / data distribution process for the user-to-user communication service, the above-described user intention analysis process for the user-to-user communication service is completed, and the user device 11 (for example, FIG. 11a) first sends the object request message to the SOP 12 (for example, 12a in FIG. 14), which is the object of the user, that is, the object provider domain 20 (for example, FIG. 14 (20b) POP address) must be known. In this state, as shown in FIG. 14, the SOP 12 transmits an object application request message to the POP 23 (for example, POP 23b in FIG. 14) specified by the POP address acquired in the user intention analysis process (step S61). ). This object application request message indicates the device ID of the communication destination acquired in the user intention analysis process. This object application request message also indicates the device ID and communication type of the user apparatus 11 (for example, 11a in FIG. 14) of the communication requesting user, and facilitates end-to-end negotiation between the user apparatus 11a and the user apparatus 21b. To.

  Upon receiving the object application request message transmitted from the SOP 12a in step S61, the POP 23b specifies a communication destination (for example, the user device 21b in FIG. 14) using the device ID indicated by the object application request message, and performs communication. The object application request message is transferred to the destination (step S62). After end-to-end negotiation between the user device 11a and the user device 21b using both device IDs, communication starts according to the type of communication indicated by the object application request message (step S63). For example, the device 21b of the communication receiving user transmits data based on a request from the device 11a of the communication requesting user. Alternatively, both devices use VoIP communication.

  Unlike content-based communication services, transmitted data must not be copied or cached by an intermediate router 32 if the user at the communication destination does not want to disclose the data.

  If the type of communication requested by the communication requesting user is email transmission, it is not necessary to identify the device of the communication receiving user. Therefore, in the case of e-mail transmission, the e-mail server address is used as the device ID for the communication receiving user, and when the communication type indicates e-mail transmission, the e-mail server address is used as the device ID as described above. It is stored in the SOP cache table, ODS cache table and POP subscriber management table. In this case, instead of the object application / data distribution process described above, the SOP 12 transmits an e-mail indicating a device ID (e-mail server address) to the POP 23, and the POP 23 transfers the e-mail using the e-mail server address.

According to embodiments of the present invention, users, devices and content are associated with these location indicators (POP addresses), but the location indicators are different from their names or IDs. This network system is convenient for both content-based communication in which a communication requesting user specifies desired content and end-to-end communication in which the communication requesting user specifies a communication receiving user or a communication receiving device. The relationship between contents, devices or users and their locations is managed in each of the network operator domain 30 and each of the object provider domains 20, and the network operator domain indicator included in the device name, user name or content name, and the ODS 31 The address relationship is managed by the GNRS 40. When the device name, user name or content name is specified in the message, the location of the device, user or content can be specified. In addition, because the appropriate entity caches the received data, the download speed can be improved when other users request the same content.

  Furthermore, if the communication requesting user does not know the specific device name of the communication receiving user, but the communication requesting user knows the user name and specifies the type of communication, the appropriate user device is specified as the communication partner. sell. This is convenient because a single user often manages or owns multiple communication devices.

10: Subscriber domain,
11: User device,
12: SOP (Subscriber Object Proxy, Subscriber Object Proxy, first proxy device),
12C: SOP cache memory (first proxy cache memory),
20: Object provider domain,
21: User device,
22: Object source server
23: POP (Publisher Object Proxy, Publisher Object Proxy, second proxy device),
23M: POP memory (provider domain memory),
30: Network operator domain,
31: ODS (object Directory Server, directory server device ),
31C: ODS cache memory (directory server cache memory),
31M: ODS memory (directory server memory),
32: Router
40: GNRS (Global Name Resolution Server),
40M: GNRS memory.

Claims (17)

A network system comprising a plurality of subscriber domains (10), a plurality of object provider domains (20), a network operator domain (30), and a message routing server device (40),
A plurality of first users are subscribed to each of the subscriber domains (10), and each of the first users owns or manages at least one first user device (11);
Each of the subscriber domains (10) includes a first proxy device (12), and the first proxy device (12) includes the subscriber domain (where the first proxy device (12) is arranged). 10) acts as a default gateway and access router for the first user equipment (11) of the first user subscribed to 10),
A plurality of second users are subscribed to each of the object provider domains (20), and each of the second users has a user name and a user ID that are universally unique to the second users. Each of the second users owns or manages at least one second user device (21), and each of the second user devices (21) has its second user device (21). ) Have a universally unique device name and device ID, each device name including the user name of the second user for the second user device (21), each of the user name and device name Includes an indicator indicating the network operator domain (30) to which the second user is subscribed,
Each of the object provider domains (20) includes a second proxy device (23), and the second proxy device (23) includes the object provider domain () in which the second proxy device (23) is disposed. 20) acts as a default gateway and access router for the second user equipment (21) of the second user subscribed to 20), each of the second proxy equipment (23) having a second proxy address Have
Each of the object provider domains (20) includes an object source server (22) for storing content and metadata information essential for using the content. Each content has a content name, and the content name Includes an indicator that indicates the network operator domain (30) that is universally specific to the content and that is linked to the object provider domain (20) where the object source server (22) that stores the content is located ,
Each of the object provider domains (20) has a provider domain memory (23M) that stores information for each of the second user devices (21) of a second user that is subscribed to the object provider domain (20). And the information for each of the second user equipment includes a device name of the second user equipment, a device ID of the second user equipment, a user name of the second user for the second user equipment, A second user's user ID for the second user device, a communication type indicator indicating the type of communication, and a second proxy device second of the object provider domain (20) to which the second user is subscribed. Contains the proxy address,
Each of the network operator domains (30) is linked to some of the plurality of subscriber domains (10) and some of the plurality of object provider domains (20), to the network operator domain (30) The first user subscribing to the linked subscriber domain (10) and the second user subscribing to the object provider domain (20) linked to the network operator domain (30) (30)
Each of the network operator domains (30) includes a directory server device (31) including a directory server memory (31M), and each of the directory server memories (31M) subscribes to the network operator domain (30). Stores information for the second user, the information for each second user includes the user name of the second user, the user ID of the second user, and the object to which the second user is subscribed Including the second proxy address of the second proxy device of the provider domain (20), the directory server memory (31M) for each of the publishable content stored in the object source server (22) Information for each of the publishable content is stored in the content Content name, metadata information for the content, and a second proxy address of a second proxy device of the object provider domain (20) in which the object source server (22) storing the content is located, Each of the directory server devices (31) has a directory server address,
The message routing server device (40) is linked to the plurality of network operator domains (30) and includes a message routing server memory (40M). The message routing server memory (40M) is connected to each network operator domain (30). The information for each network operator domain (30) is stored in the network operator domain (30) with an indicator of the network operator domain (30) included in the user name, device name or content name. Describes the relationship of the directory server address of the directory server device (31),
Based on the information stored in the message routing server memory (40M), the message routing server device (40) is an indicator of the network operator domain (30) included in the user name, device name, or content name included in the message. The directory server address from
Network system . When one of the first proxy devices (12) requests a content-based communication service from one of the first user devices (11) and receives a first request message indicating a content name, the first proxy device (12) The proxy device (12) requests a content-based communication service and transmits a second request message indicating the content name to the directory server device (31) linked to the first proxy device (12). The directory server device (31) determines whether the content name is stored in the directory server memory (31M),
When the directory server memory (31M) stores the content name, the directory server device (31) stores metadata information for the content associated with the content name in the directory server memory (31M). The second proxy address is read out, and a response message indicating the metadata information and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) Notifying the metadata information to the first user device (11) that has transmitted the first request message;
The network system according to claim 1. When the directory server memory (31M) does not store the content name, the directory server device (31) transfers the second request message to the message routing server device (40), and the message routing server device Identifies a directory server address from an indicator of the network operator domain (30) included in the content name based on information stored in the message routing server memory (40M), and has the directory server address. The second request message is transferred to the directory server device (31) of
Upon receiving the second request message, the other directory server device (31), in the directory server memory (31M), the metadata information for the content associated with the content name and the second Read the proxy address, and send a response message indicating the metadata information and the second proxy address to the message routing server device (40),
When the response message is received from the other directory server device (31), the message routing server device (40) and the directory server device (31) send the response to the first first proxy device (12). The message is transferred, and the first proxy device (12) notifies the metadata information to the first user device (11) which has transmitted the first request message.
The network system according to claim 2. When the directory server device (31) transfers the response message to the first proxy device (12), the directory server device (31) uses the content name as the metadata information and the second proxy address. Cache with,
The network system according to claim 3. Each of the provider domain memories (23M) has each of the contents that can be published stored in the object source server (22) arranged in the object provider domain (20) in which the provider domain memory (23M) is arranged. The information for each of the content that can be stored and published includes the content name of the content and the address of the object source server (22) that stores the content,
After the first proxy device (12) knows the second proxy address, the first proxy device (12) sends the content name to the second proxy device having the second proxy address. Send a message indicating
Upon receiving this message from the first proxy device, the second proxy device identifies the address of the object source server (22) associated with the content name in the provider domain memory (23M), and Sending a request to send content having a content name to the first user device (11) to the object source server (22);
The network system according to any one of claims 2 to 4. When the object source server (22) transmits the content having the content name to the first user device (11), the first proxy device (12) relays the content, and the content name and the content Cache its content along with metadata information,
The network system according to claim 5. The object source server (22) associates the content stored in the object source server (22) with a public flag or an internal use flag, and the object provider domain (20) in which the object source server (22) is arranged. ) In the provider domain memory (23M)
The publish flag indicates that the content can be published to other domains, and the internal use flag indicates that the content should be used in the object provider domain (20).
The network system according to any one of claims 1 to 6. A first request in which one of the first proxy devices (12) requests an end-to-end communication service from one of the first user devices (11) and indicates a user name and a communication type of a communication partner user Upon receiving the message, the first proxy device (12) requests an end-to-end communication service from the directory server device (31) linked to the first proxy device (12), and sends the user name. The directory server device (31) determines whether the user name is stored in the directory server memory (31M);
When the directory server memory (31M) stores the user name, the directory server device (31) stores the user ID associated with the user name and the second name in the directory server memory (31M). The proxy address is read, and a response message indicating the user ID and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) transmits the second proxy address. A third request message indicating the user ID of the communication partner user and the type of communication is transmitted to a second proxy device (23) having:
Upon receiving the third request message, the second proxy device (23) reads out the device ID associated with the user ID and the type of communication in the provider domain memory (23M), and performs the communication Sending a further response message to the first proxy device (12) indicating a device ID of the second user device of the correspondent user suitable for the type of
The network system according to claim 1. When the directory server memory (31M) does not store the user name, the directory server device (31) transfers the second request message to the message routing server device (40), and the message routing server device Identifies the directory server address from the indicator of the network operator domain (30) included in the user name based on the information stored in the message routing server memory (40M), and has the directory server address. The second request message is transferred to the directory server device (31) of
Upon receipt of the second request message, the other directory server device (31), in the directory server memory (31M) of the other directory server device (31), a user ID associated with the user name. And the second proxy address is read and a response message indicating the user ID and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) Sending a third request message indicating the user ID of the communication partner user and the type of communication to a second proxy device (23) having a second proxy address;
Upon receiving the third request message, the second proxy device (23) reads out the device ID associated with the user ID and the type of communication in the provider domain memory (23M), and performs the communication Sending a further response message to the first proxy device (12) indicating a device ID of the second user device of the correspondent user suitable for the type of
The network system according to claim 8. The further response message includes a user name and a user ID of the communication partner user, a device name and a device ID of the second user device of the communication partner user, and a type of communication used in the second user device. And the directory server address of the directory server device (31) of the network operator domain (30) to which the communication partner user has subscribed,
When the second proxy device (23) sends the further response message to the first proxy device (12), the directory server device (31) and the first proxy device (12) Cache the name, the user ID, the type of communication, the device name, the device ID and the directory server address;
The network system according to claim 8 or 9. After the first proxy device (12) knows the device ID of the second user device of the communication partner user, the first proxy device sends a message or email indicating the device ID to the second user device. Send to proxy device (23),
The network system according to any one of claims 8 to 10. One of the first proxy devices (12) requests an end-to-end communication service from one of the first user devices (11) and indicates a device name of a second user device of a communication partner user When the request message is received, the first proxy device (12) requests an end-to-end communication service from the directory server device (31) linked to the first proxy device (12). A second request message indicating a name, and the directory server device (31) determines whether or not a user name included in the device name is stored in the directory server memory (31M);
When the directory server memory (31M) stores the user name, the directory server device (31) stores the user ID associated with the user name and the second name in the directory server memory (31M). The proxy address is read, and a response message indicating the user ID and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) transmits the second proxy address. A third request message indicating the user ID of the communication partner user and the device name is transmitted to a second proxy device (23) having:
Upon receiving the third request message, the second proxy device (23) reads out the device ID associated with the user ID and the device name in the provider domain memory (23M), and the device name Sending a further response message to the first proxy device (12) indicating a device ID of the second user device of the communicating party user having
The network system according to claim 1. When the directory server memory (31M) does not store the user name, the directory server device (31) transfers the second request message to the message routing server device (40), and the message routing server device Identifies the directory server address from the indicator of the network operator domain (30) included in the user name based on the information stored in the message routing server memory (40M), and has the directory server address. The second request message is transferred to the directory server device (31) of
Upon receipt of the second request message, the other directory server device (31), in the directory server memory (31M) of the other directory server device (31), a user ID associated with the user name. And the second proxy address is read and a response message indicating the user ID and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) Sending a third request message indicating the user ID and the device name of the communication partner user to a second proxy device (23) having a second proxy address;
Upon receiving the third request message, the second proxy device (23) reads out the device ID associated with the user ID and the device name in the provider domain memory (23M), and the device name Sending a further response message to the first proxy device (12) indicating a device ID of the second user device of the communicating party user having
The network system according to claim 12. The further response message includes a user name and a user ID of the communication partner user, a device name and a device ID of the second user device of the communication partner user, and a type of communication used in the second user device. And the directory server address of the directory server device (31) of the network operator domain (30) to which the communication partner user has subscribed,
When the second proxy device (23) sends the further response message to the first proxy device (12), the directory server device (31) and the first proxy device (12) Cache the name, the user ID, the type of communication, the device name, the device ID and the directory server address;
The network system according to claim 12 or 13. After the first proxy device (12) knows the device ID of the second user device of the communication partner user, the first proxy device sends a message or email indicating the device ID to the second user device. Send to proxy device (23),
The network system according to any one of claims 12 to 14. When one of the first proxy devices (12) requests a content-based communication service from one of the first user devices (11) and receives a first request message indicating a content name, the first proxy device (12) The proxy device (12) requests a content-based communication service and transmits a second request message indicating the content name to the directory server device (31) linked to the first proxy device (12). The directory server device (31) determines whether the content name is stored in the directory server memory (31M),
When the directory server memory (31M) stores the content name, the directory server device (31) stores metadata information for the content associated with the content name in the directory server memory (31M). The second proxy address is read out, and a response message indicating the metadata information and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) Notifying the metadata information to the first user device (11) that sent the first request message;
A first request in which one of the first proxy devices (12) requests an end-to-end communication service from one of the first user devices (11) and indicates a user name and a communication type of a communication partner user Upon receiving the message, the first proxy device (12) requests an end-to-end communication service from the directory server device (31) linked to the first proxy device (12), and sends the user name. A second request message indicating that the directory server device (31) determines whether the user name is stored in the directory server memory (31M);
When the directory server memory (31M) stores the user name, the directory server device (31) stores the user ID associated with the user name and the second name in the directory server memory (31M). The proxy address is read, and a response message indicating the user ID and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) transmits the second proxy address. A third request message indicating the user ID of the communication partner user and the type of communication is transmitted to a second proxy device (23) having:
Upon receiving the third request message, the second proxy device (23) reads out the device ID associated with the user ID and the type of communication in the provider domain memory (23M), and performs the communication Sending a further response message to the first proxy device (12) indicating the device ID of the second user device of the correspondent user suitable for the type of
One of the first proxy devices (12) requests an end-to-end communication service from one of the first user devices (11) and indicates a device name of a second user device of a communication partner user When the request message is received, the first proxy device (12) requests an end-to-end communication service from the directory server device (31) linked to the first proxy device (12). A second request message indicating a name, and the directory server device (31) determines whether or not a user name included in the device name is stored in the directory server memory (31M);
When the directory server memory (31M) stores the user name, the directory server device (31) stores the user ID associated with the user name and the second name in the directory server memory (31M). The proxy address is read, and a response message indicating the user ID and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) transmits the second proxy address. A third request message indicating the user ID of the communication partner user and the device name is transmitted to a second proxy device (23) having:
Upon receiving the third request message, the second proxy device (23) reads out the device ID associated with the user ID and the device name in the provider domain memory (23M), and the device name Sending a further response message to the first proxy device (12) indicating a device ID of the second user device of the communicating party user having
The network system according to claim 1. When the directory server memory (31M) does not store the content name indicated in the first request message, the directory server device (31) sends the second request to the message routing server device (40). The message routing server device identifies the directory server address from the network operator domain (30) indicator included in the content name based on the information stored in the message routing server memory (40M). Then, the second request message is transferred to another directory server device (31) having the directory server address,
Upon receiving the second request message, the other directory server device (31), in the directory server memory (31M), the metadata information for the content associated with the content name and the second Read the proxy address, and send a response message indicating the metadata information and the second proxy address to the message routing server device (40),
When the response message is received from the other directory server device (31), the message routing server device (40) and the directory server device (31) send the response to the first first proxy device (12). The first proxy device (12) notifies the metadata information to the first user device (11) that transmitted the first request message;
When the directory server memory (31M) does not store the user name indicated in the first request message, the directory server device (31) sends the second request to the message routing server device (40). The message routing server device identifies the directory server address from the network operator domain (30) indicator included in the user name based on the information stored in the message routing server memory (40M). Then, the second request message is transferred to another directory server device (31) having the directory server address,
Upon receipt of the second request message, the other directory server device (31), in the directory server memory (31M) of the other directory server device (31), a user ID associated with the user name. And the second proxy address is read and a response message indicating the user ID and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) Sending a third request message indicating the user ID of the communication partner user and the type of communication to a second proxy device (23) having a second proxy address;
Upon receiving the third request message, the second proxy device (23) reads out the device ID associated with the user ID and the type of communication in the provider domain memory (23M), and performs the communication Sending a further response message to the first proxy device (12) indicating the device ID of the second user device of the correspondent user suitable for the type of
When the directory server memory (31M) does not store the user name included in the device name indicated in the first request message, the directory server device (31) performs the message routing server device (40). The message routing server device transmits an indicator of the network operator domain (30) included in the user name based on the information stored in the message routing server memory (40M). The directory server address is identified from the server, and the second request message is transferred to another directory server device (31) having the directory server address.
Upon receipt of the second request message, the other directory server device (31), in the directory server memory (31M) of the other directory server device (31), a user ID associated with the user name. And the second proxy address is read and a response message indicating the user ID and the second proxy address is transmitted to the first proxy device (12), and the first proxy device (12) Sending a third request message indicating the user ID and the device name of the communication partner user to a second proxy device (23) having a second proxy address;
Upon receiving the third request message, the second proxy device (23) reads out the device ID associated with the user ID and the device name in the provider domain memory (23M), and the device name Sending a further response message to the first proxy device (12) indicating a device ID of the second user device of the communicating party user having
The network system according to claim 16.

Images