CN102164404B - Personal network's system and service implementation method thereof - Google Patents

Abstract

The present invention discloses a personal network system and a service realization method thereof. Specifically, the above-mentioned service realization method of the personal network system includes: a first device sends a service registration request message to a personal network server; The service ID carried in the request message judges that the service corresponding to the service ID is a published service; if it is a published service, the personal network server judges whether the service content indicated by the service registration request message is the same as the business content of the above-mentioned business that has been saved. Different versions; if different versions, the personal network server publishes the above-mentioned business content. Through the present invention, repeated registration of the same service can be rejected, thereby reducing the network burden caused by the repeated release of content to a certain extent, reducing the redundancy of service content published by devices in the personal network, and improving user experience.

Description

Personal network system and its business realization method

technical field

The present invention relates to the communication field, in particular, to a personal network system and a service realization method thereof.

Background technique

A personal network (Personal Network, PN) (also known as a personal area network (Personal Area Network, PAN) that accesses the Internet wirelessly) is a combination of digital products owned by individuals, such as home appliances, mobile terminals, etc. (referred to as personal network equipment PNE) ) into a network, so that these devices can connect to external networks through any device with network access (often wireless connection) (these devices that provide access are called personal network gateways: PNGateway), so that they can access Services and content provided by external networks.

The business derived from the access and management of personal networks by operators is called Converged Personal Network Services (CPNS). In the integrated personal network service, personal network devices can be connected to the operator's network through the personal network gateway (PNGateway), and consume various services (including services provided by the operator itself and other content providers, service providers, and services provided by other personal devices), as well as the services published by itself.

Due to the existence of a large number of personal network devices, it can be expected that if each personal network device releases services to the outside world, the network content will increase sharply. In addition, when considering these business contents, it will be found that many contents are provided repeatedly, especially for the same business such as songs. Downloads, picture downloads, etc. are often compressed and cropped to suit devices with different processing capabilities, forming different versions of the same content source.

This problem is particularly prominent in the field of converged personal network services, because a large part of converged personal network services utilizes wireless networks. Compared with fixed networks, wireless networks have more precious air interface resources and more fragile connections. On the other hand, due to differences in computing capabilities of personal network devices, it is necessary to provide multiple configuration options for different services to enhance user experience.

Contents of the invention

The main purpose of the present invention is to provide a personal network system and its service implementation method to at least solve the above problems.

According to one aspect of the present invention, a service implementation method of a personal network system is provided, including: the first device sends a service registration request message to the personal network server; the personal network server judges according to the service ID carried in the service registration request message The service corresponding to this service ID is a published service; if it is a published service, then the personal network server judges whether the service content indicated by the service registration request message is a different version from the business content of the above-mentioned business that has been saved; if it is a different version, Then the personal network server publishes the above-mentioned business content.

According to another aspect of the present invention, a personal network system is provided, including: a first device and a personal network server, wherein,

The first device is configured to send a service registration request message to the personal network server;

The personal network server is used to judge the service corresponding to the service ID as a released service according to the service ID carried in the above-mentioned service registration request message; Whether the indicated business content is a different version from the saved business content of the above-mentioned business; it is also used to publish the above-mentioned business content when the judgment result is a different version.

Through the present invention, due to making full use of the characteristics that many business contents in the personal network are repeatedly provided, through the service ID (globally unique service ID) of the service, other users (including the initial service provider) can customize different configurations for the initial service When the version is registered with the personal network server with the same business ID, it will be released only when it is judged to be a different version, which solves the problem in related technologies that a large number of personal network devices publish services to the outside world, and the network content will increase sharply, which may cause network congestion. , so that the repeated registration of the same service can be rejected, the network burden caused by the repeated publication of content can be reduced to a certain extent, and the redundancy of service content published by devices in the personal network can be reduced.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

FIG. 1 is a flow chart of a service realization method of a personal network system according to an embodiment of the present invention;

2 is a schematic diagram of a personal network system according to an embodiment of the present invention;

FIG. 3 is a system architecture diagram of a personal network system according to a preferred embodiment of the present invention;

Fig. 4 is a flow chart of issuing an initial service in a service realization method of a personal network system according to a preferred embodiment of the present invention;

FIG. 5 is a flow chart of publishing different versions of service content in the service implementation method of the personal network system according to an embodiment of the present invention;

Fig. 6 is a flow chart of selecting an appropriate version for use in the service implementation method of the personal network system according to the first embodiment of the present invention;

Fig. 7 is a flow chart of selecting an appropriate version to use in the service implementation method of the personal network system according to the second embodiment of the present invention; and,

Fig. 8 is a flow chart of selecting an appropriate version for use in the service implementation method of the personal network system according to the third embodiment of the present invention.

detailed description

Hereinafter, the present invention will be described in detail with reference to the drawings and examples. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

Fig. 1 is a flow chart of a service implementation method of a personal network system according to an embodiment of the present invention, including the following steps:

Step S102, the first device sends a service registration request message to the personal network server;

Step S104, the personal network server judges that the service corresponding to the service ID is a published service according to the service ID carried in the service registration request message;

Step S106, if it is a published service, the personal network server judges whether the service content indicated by the service registration request message is of a different version from the service content of the service already saved;

Step S108, if the versions are different, the personal web server publishes the business content.

This embodiment takes full advantage of the fact that many business contents in the personal network are repeatedly provided. Through the service ID (globally unique service ID) of the service, other users (including the initial service provider) customize different configuration versions of the initial service. When the same service ID is registered with the personal network server, it is judged to be of different versions before publishing, which solves the problem in related technologies that a large number of personal network devices publish services to the outside world, and the network content will increase sharply, which may cause network congestion. Using this embodiment can reject the repeated registration of the same service, can reduce the network load caused by the repeated publishing of content to a certain extent, and can reduce the redundancy of service content published by devices in the personal network.

Preferably, before step S102, it also includes:

The second device sends a service registration request message to the personal network server, wherein the service registration request message carries service description information, a default or empty service ID, and a default version number;

The personal network server detects that the service ID carried in the service registration request message is empty or default, and then judges that the service indicated by the service registration request message is a new service;

The personal network server assigns a service ID to the service, and initializes the version number of the service as the first version number;

The personal network server returns the service ID and the first version number of the service to the second device, and publishes the service.

Wherein, after the personal network server assigns a service ID to the service and initializes the version number of the service as the first version number, it further includes: the personal network server saves the service description information, the first version number and the provider information of the service.

This preferred embodiment provides a specific implementation scheme for the initial service provider to issue a new service initially. When the service is released initially, the personal network server assigns a globally unique service ID to the new service, after which other users (including the initial service provider) publish different versions of the same service with this service ID as the unique ID. The above-mentioned default service ID and default version number are pre-agreed.

Obviously, the above-mentioned first device and the second device may be the same device or different devices.

Preferably, when the first device is the second device, step S102 includes: the second device sends a service registration request message to the personal network server again, wherein the service registration request message carries service description information, new configuration information, service ID and default version number.

This preferred embodiment provides a specific implementation solution in which the initial service provider can issue different configuration versions of the service with the service ID of the service after releasing the service for the first time.

Preferably, when the first device and the second device are different devices, step S102 includes: the first device uses the service corresponding to the service ID, and customizes the service content of the service; The network server sends a service registration request message, wherein the service registration request message carries service description information, new configuration information, service ID and default version number.

This preferred embodiment provides a specific implementation plan for the non-initial service provider to customize and configure a certain version after obtaining the service content, and register the service content of this version with the personal network server.

Preferably, step S104 includes: the personal network server detects that the service ID carried in the service registration request message is non-null or non-default, and then judges that the service corresponding to the service ID is a published service.

Step S106 includes: the personal network server detects that the version number carried in the service registration request message is the default version number, then checks the version of the service content indicated by the service registration request message; Whether the business content is a different version.

Step S108 includes: if it is a different version, then the personal network server checks the legality of the different version of the business content; if the legality requirements are met, the personal network server assigns a second version number to the different version of the business content, and saves the second version number. Two version numbers, service description information, and new configuration information; the personal network server returns the service ID and the second version number to the first device, and publishes the different versions of the service content.

In this preferred embodiment, by checking the legality of different versions of the service content to be released, the release of illegal service content can be further avoided.

Preferably, step S106 further includes: if it is the same version as an existing service content, the personal network server returns the service ID and the found version number corresponding to the found service content to the first device. When it is judged that the registered service content to be released is the same version as one of the saved versions of the service, the service content is not released, thereby avoiding repeated release of the same version of the service content.

Preferably, step S108 further includes: if the legality requirement is not met, the personal network server returns the service ID and information that the service release is not legal to the first device. When it is judged that the registered business content to be released does not meet the legality requirements, the business content is not released, further avoiding the release of illegal business content.

Preferably, the above method further includes: the third device requests to use the service corresponding to the service ID; Select a version in the service content; the personal network server sends the service provision information corresponding to the selected version to the third device; the third device uses the service according to the service provision information.

This preferred embodiment provides a specific implementation scheme in which the personal network server can automatically select a certain configuration version of the service for the service user when the service user obtains the description of the service and wants to use the service.

Preferably, the above method further includes: the third device requests to use the service corresponding to the service ID; the personal network server inquires from the third device and obtains the processing capability and available network resources of the third device; the personal network server according to the acquired The processing ability and the available network resources of the third device can select a version from the business content of multiple versions of the stored business; the personal network server sends the service provision information corresponding to the selected version to the third device; the third device Provide information and use the business according to the business.

This preferred embodiment provides a specific implementation scheme in which the personal network server selects a certain configuration version of the service through negotiation with the service user when the service user obtains the description of the service and wants to use the service.

Preferably, the above method further includes: the third device requests to use the service corresponding to the service ID; the personal network server finds multiple versions of the service content of the stored service; the personal network server sends the service content corresponding to the multiple versions The service provides information to the third device; the third device selects one version from multiple versions according to its processing capability or available network resources or willingness to use, and uses the service according to the service provision information of the selected version.

This preferred embodiment provides that when the service user obtains the description of the service and wants to use the service, the personal network server provides the service user with multiple versions of the service, and the service user selects a specific implementation plan for using a version .

Obviously, the above-mentioned first device, second device and third device may be the same device or different devices.

The above three preferred embodiments provide three specific implementation schemes in which multiple configuration versions are selected for services according to differences in processing capabilities of network devices. The preferred embodiments above provide multiple configurations for service users to choose and use, which can flexibly select a service version suitable for their own terminal capabilities and locations for users, and improve the service experience of users.

Fig. 2 is a schematic diagram of a personal network system according to an embodiment of the present invention, and the personal network system includes:

The first device 10 is configured to send a service registration request message to the personal network server 20;

The personal network server 20 is used to judge that the service corresponding to the service ID is a released service according to the service ID carried in the service registration request message; it is also used to judge that the service registration is issued when the judgment result is a released service. Whether the business content indicated by the request message is a different version from the saved business content of the business; it is also used to publish the business content when the judgment result is a different version.

This embodiment takes full advantage of the fact that many business contents in the personal network are repeatedly provided. Through the service ID (globally unique service ID) of the service, other users (including the initial service provider) customize different configuration versions of the initial service. When the same service ID is registered with the personal network server, it is judged to be of different versions before publishing, which solves the problem in related technologies that a large number of personal network devices publish services to the outside world, and the network content will increase sharply, which may cause network congestion. Using this embodiment can reject the repeated registration of the same service, can reduce the network load caused by the repeated publishing of content to a certain extent, and can reduce the redundancy of service content published by devices in the personal network.

Fig. 3 is a system architecture diagram of a personal network system according to a preferred embodiment of the present invention, the personal network system includes:

PNE (Personal Network Equipment), as a consumer (ie user) and provider of services.

PN gateway (personal network gateway), as the connector and manager of the personal network. It is also PNE. PNE and PN gateways constitute a Personal Network (PN) in the smallest sense.

CPNS server (personal network server), responsible for business registration, release, search, subscription, authentication, etc.

It is worth noting that in the above architecture diagram, the above-mentioned components are logical entities, which can be flexibly deployed on different physical entities. For example, the PNE and the PN gateway may be the same physical entity, and the PNE may also partially implement the function of the CPNS server.

The business implementation method of the personal network system of the present invention includes the following aspects:

Step 1: The initial service provider publishes the initial service and obtains a globally unique service ID. The publisher may be any PNE, PN gateway, CP (ContentProvider, content provider), SP (ServiceProvider, service provider), etc., the publisher Register a new service with the CPNS server, and the CPNS server assigns a globally unique ID to the service. As shown in Figure 4, the following steps are included:

Step S401, the initial service provider PNEA sends a service registration request message to the CPNS server, the service registration request carries service description information, and a service ID of a default value (or the service ID is empty), a version of a default value No.

Step S402, the CPNS server checks the service registration request message, finds that the service ID is blank or a default value, and determines that the service is a new service;

Step S403, the CPNS server assigns a globally unique ID to the service: IDx, and initializes the version number of the service as VersionX1;

Step S404, the CPNS server saves the service description information, configuration version information and provider information of the service, and publishes the service;

Step S405, the CPNS server returns the service ID: IDx and version number VersionX1 to PNEA;

Step S406, PNEA saves the service ID: IDx and version number and VersionX1.

Step 2: Add different configuration services according to the globally unique service ID, and publish different versions of the service content. After the service is released, the initial service provider can release different configuration versions of the service with the global service ID of the service. Or, after obtaining the service content, other service consumers customize and configure it into a certain version, and request to register another customized version of the service under legal authorization according to the globally unique service ID of the initial service.

Step S501, PNEA wants to release a new version with different configurations of the service, so it sends a service registration request message to the CPNS server again, which carries: service description information, new configuration, and service ID, a version number of a default value;

Further, for non-initial service provider PNEB, the steps to provide a customized version are as follows:

In step 1, the PNEB uses the service whose service ID is IDx. The service is customized during use, for example: after downloading pictures, they are compressed to other sizes.

In step 2, the PNEB issues a service registration request message to the CPNS server, which carries: service description information, new configuration, service ID, and a version number of a default value.

Step S502, the CPNS server checks the service registration request message and finds that the service ID is not empty or is a non-default value, then it is determined that the service is a published service;

Step S503, the CPNS server checks the version number and finds that it is a default value, which means that this is a different version of the service, and performs a version check. The CPNS server can check the contents of different versions to determine whether they are different versions. If it is the same version, then proceed to step S504, if not, then proceed to step S505;

Step S504, save this version number, go to step S508.

In step S505, the CPNS server can check the legality of the version to determine whether the release of the version meets the legality requirements of the initial service version. If the legality requirement is not met, go to step S509, otherwise go to S506.

Step S506, after determining that the version can be released, the CPNS server assigns a version number VersionX2 to it, and saves the relevant information of the version;

Step S507, the CPNS server returns the service ID and version number VersionX2 of the service, and the PNEA or PNEB saves the service ID and version number VersionX2. The process ends.

In step S508, the CPNS server returns the service ID and the found version number. Optionally, the CPNS server may further provide the device information of this version for backup. The device saves the service version information. The process ends.

In step S509, the CPNS server returns the ID of the service and the information that the service release is illegal. The process ends.

Step 3: Select the appropriate configuration version for service consumption according to the capabilities of the device. After obtaining the description of the service, the service consumer can automatically match or negotiate or actively select a certain configuration version for consumption.

Step 3 can be implemented in a variety of ways:

Fig. 6 is the flow chart of selecting the appropriate version of the service implementation method of the personal network system of the first embodiment of the present invention. The situation where the service of a certain configuration version is automatically selected by the CPNS server for the service consumer includes the following steps:

Step S601, the device PNEC requests to use the service whose ID is IDx;

Step S602, the CPNS server searches for the service and finds that the service provides multiple versions;

Step S603, the CPNS server invokes the device management module to query the device processing capability and network connection status of the PNEC, and accordingly selects VersionX1;

Step S604, the CPNS server provides the service provision information (including the provider) where this version is located. PNEC uses the service according to this version of the information.

Fig. 7 is the flow chart of selecting the appropriate version of the service realization method of the personal network system of the second embodiment of the present invention to use, the situation that the service of a certain configuration version is selected through negotiation between the CPNS server and the service consumer, comprises the following steps:

Step S701, the device PNEC requests to use the service whose ID is IDx;

Step S702, the CPNS server searches for the service and finds that the service provides multiple versions;

Step S703, the CPNS server inquires the PNEC about the device processing capability and available network resources;

Step S704, after the CPNS server obtains the equipment capabilities and available network resources of the PNEC, it selects VersionX2 accordingly;

In step S705, the CPNS server provides the service providing information (including the provider) of this version to the PNEC. PNEC uses the service according to this version of the information.

Fig. 8 is a flow chart of selecting an appropriate version for use in the service realization method of the personal network system of the third embodiment of the present invention. The CPNS server actively provides multiple configuration versions, and the user chooses the situation by himself, including the following steps:

Step S801, the device PNEC requests to use the service whose ID is IDx;

Step S802, the CPNS server searches for the service and finds that the service provides multiple versions;

Step S803, the CPNS server returns a list to PNEC, which includes version information (including provider) of multiple versions;

Step S804, PNEC selects VersionX1 according to its own equipment capabilities or available network resources or willingness to use;

In step S805, the PNEC uses the service according to the service information of this version.

From the above description, it can be seen that the present invention achieves the following technical effects:

(1) Eliminate the redundancy of published business content and satisfy legal authority;

(2) Multiple configuration versions of services can be provided, and service users can more flexibly obtain service versions that are more suitable for their abilities and locations for consumption.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases, in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (13)

1. a service implementation method for personal network's system, is characterized in that, comprising:

First device sends service log-on request message to personal network's server;

According to the traffic ID of carrying in described service log-on request message, described personal network's server judges that business corresponding to described traffic ID is as issuing service;

If issuing service, then described personal network's server judges whether the business tine indicated by described service log-on request message is different editions with the business tine of the described business of having preserved;

If different editions, then described personal network's server issues described business tine;

Wherein, described traffic ID is overall unique traffic ID;

Wherein, also comprised before first device sends service log-on request message to personal network's server:

Second device sends service log-on request message to described personal network's server, wherein, carries business description information, default or empty traffic ID and default version number in described service log-on request message;

Described personal network's server detects that the traffic ID of carrying in described service log-on request message is for empty or default, then judge that the business indicated by described service log-on request message is new business;

Described personal network's server is described traffic assignments traffic ID, and the version number of business described in initialization is first version number;

Described personal network's server returns the described traffic ID of described business and described first version number to described second device, and issues described business.

2. method according to claim 1, is characterized in that, is described traffic assignments traffic ID at described personal network's server, and the version number of business described in initialization also comprises after being first version number:

Described personal network's server preserves the business description information of described business, described first version number and supplier's information.

3. method according to claim 1, is characterized in that, when described first device is described second device, first device sends service log-on request message to personal network's server and comprises:

Described second device sends service log-on request message to described personal network's server again, wherein, carries business description information, new configuration information, described traffic ID and default version number in described service log-on request message.

4. method according to claim 1, is characterized in that, when described first device and described second device are different device, first device sends service log-on request message to personal network's server and comprises:

Described first device uses the business corresponding to described traffic ID, and customizes the business tine of described business;

Described first device sends service log-on request message for the business after customization to described personal network's server, wherein, carries business description information, new configuration information, described traffic ID and default version number in described service log-on request message.

5. the method according to any one of Claims 1-4, is characterized in that, according to the traffic ID of carrying in described service log-on request message, described personal network's server judges that business corresponding to described traffic ID comprises as issuing service:

Described personal network's server detects that the traffic ID of carrying in described service log-on request message is non-NULL or non-default, then judge that business corresponding to described traffic ID is as issuing service.

6. the method according to any one of Claims 1-4, it is characterized in that, if issuing service, then described personal network's server judges whether the business tine indicated by described service log-on request message is that different editions comprises with the business tine of the described business of having preserved:

Described personal network's server detects that the version number of carrying in described service log-on request message is default version number, then carry out version checking to the described business tine indicated by described service log-on request message;

Judge whether described business tine is different editions with the existing business tine of the described business of preserving.

7. the method according to any one of Claims 1-4, is characterized in that, if different editions, then described personal network's server is issued described business tine and comprised:

If different editions, then described personal network's server carries out validity checking to the business tine of described different editions;

If meet legitimacy requirement, then described personal network's server is that the business tine of described different editions distributes the second edition number, and preserves the described second edition number, business description information, new configuration information;

Described personal network's server returns described traffic ID and the described second edition number to described first device, and issues the business tine of described different editions.

8. method according to claim 6, it is characterized in that, if issuing service, then described personal network's server judges whether the business tine indicated by described service log-on request message is that different editions also comprises with the business tine of the described business of having preserved:

If be same version with a described existing business tine, then described personal network's server returns version number corresponding to described traffic ID and the existing business tine found to described first device.

9. method according to claim 7, is characterized in that, if different editions, then described personal network's server is issued described business tine and also comprised:

If do not meet legitimacy requirement, then described personal network's server returns described traffic ID and the illegal information of service distribution to described first device.

10. method according to claim 1, is characterized in that, also comprises:

3rd device request uses the business corresponding to described traffic ID;

Described personal network's server selects a version according to the disposal ability of described 3rd device preserved and network connection status from the business tine of multiple versions of the described business of having preserved;

Described personal network's server sends the business corresponding to version selected provides information to described 3rd device;

Described 3rd device provides information to use described business according to described business.

11. methods according to claim 1, is characterized in that, also comprise:

3rd device request uses the business corresponding to described traffic ID;

Described personal network's server is inquired about to described 3rd device and is got disposal ability and the available network resource of described 3rd device;

Described personal network's server selects a version according to the disposal ability of described 3rd device got and available network resource from the business tine of multiple versions of the described business of having preserved;

Described personal network's server sends the business corresponding to version selected provides information to described 3rd device;

Described 3rd device provides information to use described business according to described business.

12. methods according to claim 1, is characterized in that, also comprise:

3rd device request uses the business corresponding to described traffic ID;

Described personal network's whois lookup is to the business tine of multiple versions of the described business of having preserved;

The business that described personal network's server sends corresponding to described multiple version provides information to described 3rd device;

Described 3rd device is according to its disposal ability or available network resource or use wish to select a version from described multiple version, and provides information to use described business according to the business of the version selected.

13. 1 kinds of personal network's systems, is characterized in that, comprising:

First device, for sending service log-on request message to personal network's server;

Personal network's server, for judging that according to the traffic ID of carrying in described service log-on request message business corresponding to described traffic ID is as issuing service; Also for when judged result be issuing service time, judge whether business tine indicated by described service log-on request message is different editions with the business tine of the described business of having preserved; Also for when judged result is different editions, issue described business tine;

Wherein, described traffic ID is overall unique traffic ID;

Described personal network's system, also comprises:

Second device, for sending service log-on request message to described personal network's server, wherein, carries business description information, default or empty traffic ID and default version number in described service log-on request message;

Described personal network's server, also for detecting that the traffic ID of carrying in described service log-on request message is for empty or default, then judge that the business indicated by described service log-on request message is new business; Also for being described traffic assignments traffic ID, and the version number of business described in initialization is first version number; Also for returning the described traffic ID of described business and described first version number to described second device, and issue described business.