KR20120049457A - Method and apparatus for sharing device between users in ims application service - Google Patents

Abstract

The present invention relates to an application service provided through an Internet Protocol Multimedia Subsystem (IMS), and more particularly, to a method and apparatus for enabling one user's IMS device to be used by another user subscribed to the same application service. The present invention sets the authority to use the IMS device of another person, and enables the other person to use the IMS device as needed, thereby more efficiently using the IMS device and providing a more diverse service environment to the user. can do.

Description

METHOD AND APPARATUS FOR SHARING DEVICE BETWEEN USERS IN IMS APPLICATION SERVICE}

The present invention relates to an application service provided through an Internet Protocol Multimedia Subsystem (IMS), and more particularly, to a method and apparatus for enabling one user's IMS device to be used by another user subscribed to the same application service.

In general, an Internet Protocol Multimedia Subsystem (IMS) network is a communication network for providing a multimedia service and various additional services to a user using a Session Initiation Protocol (SIP). IMS itself provides basic multimedia services, but in terms of application services, it plays a large role as a channel for registering / managing a user's IMS device and delivering media and control signals between user (IMS device) and application service. Can be. Among these, IMS device registration is related, so we will look into this in more detail.

FIG. 1 briefly shows only a part related to device registration in the configuration of an IMS network for the sake of understanding. A user who wants to use a specific service through the IMS network must have a personal communication device that can access the IMS network, and must visit each telecommunication company or service agent and sign up for the service. Then, the telecommunication company or service agent installs the ISIM (IP Multimedia Services Identity Module) on the personal communication devices 10 and 20, where data such as a user ID and an encryption authentication key are stored. In addition, when a user joins the IMS network 80, information about the user is stored in the home subscriber server (HSS) 40, and when the user 10, 20 is connected to the IMS network 80, the IMS network 80 ) Performs user authentication and connection with the corresponding application servers 50, 60, 70 using the information stored in the HSS 40.

In the IMS network 80, servers independent of the IMS network 80, which are called application servers 50, 60, and 70, may be located. These servers may include independent services such as messaging services and presence services. To the user. The HSS 40 of the IMS network 80 stores information on which application service a user is subscribed to in a user profile, and then the server 30 of the S-CSCF server. The User Profile is provided to the S-CSCF server 30 upon request. The S-CSCF server 30 uses the application server 50 corresponding to the corresponding application service to the user accessing the IMS network 80 through 3rd party registration based on the information stored in the provided user profile. 60, 70). After the connection is made, application services are provided while data is exchanged between the IMS devices 10 and 20 and the application servers 50, 60 and 70, and these data are transmitted through the IMS network 80.

After a user subscribes to an IMS (application) service, he or she must connect a device to the IMS network 80 to use these services. This process is called registration, and the main entity involved in this is the S-CSCF server 30. That is, when the S-CSCF server 30 receives a REGISTER message from the IMS devices 10 and 20, the S-CSCF server 30 retrieves information on the corresponding user from the HSS 40 to perform user authentication and the like. Bind the address. The message or session request received by a specific user ID by this binding operation is delivered to the device address bound to this user ID. That is, due to such a binding operation, even if a user ID is entered as a reception address when a message or the like is transmitted / received between users, the corresponding device can be found and transmitted to the corresponding device in the IMS network.

On the other hand, the S-CSCF server 30 may provide the binding information in the form of one event package. This package contains all device addresses that are bound to a specific user ID and is called a 'reg' event package. The IMS devices 10 and 20 may receive a 'reg' event package by subscribing to a 'reg' event package.

As described above, in the conventional IMS network 80, ISIM is installed in all IMS devices 10 and 20 when subscribing to an IMS application service. The ISIM stores a user ID, an authentication key, and the like of the device. Since the IMS device uses the user ID registered in the ISIM to register the IMS network 80 or the IMS application service, it is impossible for another person to register and use the device owned by the other person in the IMS network 80 with its own address. .

As an alternative, a user who wants to use a device owned by another person can register in the IMS network instead of the device to be used as his device. However, in order to register another device using its own device, the address of the device to be registered (for example, IP address) must be entered in the contact header of the register message. In general, the address of the device is not fixed. Because it is dynamically allocated from the network, it is not easy for a third party to know the address of another person's device.

In order to solve the above problems, the present invention provides a method and apparatus for setting up an application server to allow a user who wants to use his or her IMS device with another person to allow a person to use the device. .

In addition, the present invention provides a method and apparatus for allowing a user to obtain the address of a corresponding device from an application server and to register on behalf of the device through his / her own device.

Meanwhile, the present invention provides a method for allowing an application server providing an Internet Protocol Multimedia Subsystem (IMS) application service to share an IMS device among users, wherein the first IMS device is shared from a first IMS device to a plurality of users. Receiving a sharing registration request message requesting registration with an IMS device, and corresponding to a user ID of at least one sharing user included in the sharing registration request message, and to a public IMS device that has permission to use the sharing user. And adding information about the first IMS device to a user event package including information about the first IMS device.

The present invention provides a method for sharing an IMS device between users by an IMS device provided with an IMS application service, the application server providing the IMS application service corresponding to the IMS device, and the user of the IMS device has a usage right Transmitting a subscription request message for a user event package including information on an IMS device, receiving a notification message including information of the user event package from the application server, and receiving the user event package information. Displaying a list of included IMS devices and information indicating whether each of the IMS devices included in the IMS device list is a public IMS device to which a plurality of users are entitled, and occupying a specific public IMS device selected by the user; A usage registration request message to the application server. And a process, wherein the specific public IMS device includes a step of transmitting a message for requesting to provide the IMS service application to the application server.

According to the present invention, by setting a right to use a device in the name of another person and allowing another person to use the device as necessary, the present invention can use the device more efficiently and provide a more diverse service environment to the user. . For example, in some IMS application services, such as CPM, assuming that the IMS devices available to the user are audio and television, the user may receive audio over audio and video over television. It may be economically burdensome for all users to purchase audio and television to use such a service. In this case, if the devices can be shared and used between each other, a service specialized in a multi-device environment can be used while reducing the economic burden on the user.

1 is a view showing the configuration of a general IMS network;
2 is a diagram showing the configuration of an IMS device according to an embodiment of the present invention;
3 is a diagram showing the configuration of an S-CSCF server according to an embodiment of the present invention;
4 to 6 are views illustrating an operation process of the S-CSCF server according to an embodiment of the present invention;
7 illustrates a message flow in accordance with an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the same components in the drawings are represented by the same reference numerals and symbols as much as possible even though they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In the following description, a device capable of receiving an IMS service is referred to as an IMS device, and a subscriber to the IMS service is referred to as a user. A user is assigned a unique user ID when subscribing to an IMS service. And the IMS device is registered so that only one user can use it, i.e., a personal IMS device registered in the IMS network using one user ID and available only in connection with the one user ID, Users can be classified as a public IMS device that is given permission to use and registered for public use. Hereinafter, a personal IMS device is called a personal device, a public IMS device is called a public device, and a user who can use the public IMS device is called a shared user. The user corresponding to the user ID assigned to the IMS device at the time of subscribing to the IMS service is called an owner.

According to the present invention, an owner of a specific IMS device may register a specific IMS device as a common device in each application server that provides an application service to the specific IMS device, so that others designated by the user can use the specific IMS device. Can be. This includes information indicating that a specific IMS device is a public device together with a user ID of a shared user who can use a particular IMS device in a RERESSTER message according to the present invention, and the corresponding application through the S-CSCF server 30. By having it delivered to the server, it is possible.

Accordingly, the application server records the specific IMS device as a common device in a user event package corresponding to the shared user specified in the RESISTER message, and the information about the user event package according to the request of the shared user. To the IMS device of the shared user. The user event package contains information about public IMS devices that the user has permission to use.

By sharing a user event package from an application server (SUBSCRIBE), a shared user can obtain the device address and status of a specific IMS device, and when the application service is to be provided through a specific IMS device, The specific IMS device can be registered to the application server so that the user ID is bound.

Accordingly, an IMS application service corresponding to the sharing user may be provided to the first IMS device at the request of the sharing user.

This is particularly effective when a personal device is not available for some reason, or when a public device is used together with a personal device in order to provide a higher quality service. In the latter case, when a video chat service is subscribed, text message transmission / reception is performed using a personal mobile phone, and video data transmission / reception and processing are performed using a home TV.

The entity configuration of the IMS network to which the present invention is applied may be similar to that of FIG. 1, and the operation of each conventional entity will also be effective. However, as the present invention is applied, each entity may be configured or operate as illustrated in FIGS. 2 to 7 and the following description.

2 and 3 illustrate an example of the configuration of an IMS device and an application server to which the present invention is applied. 2 is a diagram illustrating a configuration of an IMS device 100 according to an embodiment of the present invention, and FIG. 3 is a diagram illustrating a configuration of an application server 200 according to an embodiment of the present invention.

First, referring to FIG. 2, the IMS device 100 may include a controller 110, an Internet Protocol Multimedia Services Identity Module (ISIM) 120, a memory 130, a transceiver 140, and a user interface 150. Include.

The controller 110 controls the overall operation of the IMS device and controls the registration process according to the present invention. Accordingly, the controller 110 generates various messages used in the registration process, transmits them through the transceiver 140, and processes various messages received through the transceiver 140. The controller 110 provides various information used in the registration process to the user through the user interface 150 and proceeds with the registration process according to a user input input through the user interface 150.

The transceiver 140 transmits various data and messages under the control of the controller 110, and transmits the received data and messages to the controller 110.

The ISIM 120 stores data such as a user ID, an encryption authentication key, and device information required for the IMS service.

The user interface 150 includes various interfaces for receiving data from a user or providing data to the user. For example, it may include a key input unit, a display, a speaker, a microphone, and the like.

The memory unit 130 stores a program for processing and controlling the control unit 110, reference data, various kinds of updatable storage data, and the like, and is provided as a working memory of the control unit 110. According to an embodiment of the present invention, information about a user event package corresponding to the IMS device may be stored.

An application server is a server that provides various application services such as messaging services, presence services, and multimedia streaming services to an IMS user or an IMS device through an IMS network. 3, the application server 200 includes a registration processor 210, a user event package manager 220, a storage 230, and a communicator 240.

The registration processor 210 controls the usage event package manager 220, the communicator 240, and the storage 230 to process an overall registration process for the IMS device. Accordingly, the registration processing unit 210 requests various information necessary in the registration process to the external entity through the communication unit 240 and generates various messages to be transmitted to other entities in various registration processes. And it processes various information and various messages received through the communication unit 240. Accordingly, the registration processing unit 210 registers a specific IMS device as a public device, manages the status information of the public device, and binds the public device and the corresponding shared user according to a request of the shared user to perform the use registration for the public device. Or unregister the usage. In addition, the user event package manager 220 controls the user event package to be updated according to the registration process. In addition, the registration processing unit 210 manages the registration maintenance time of the public user for the public device. In addition, the registration processor 210 transmits the information on the user event package to the corresponding IMS device whenever the state of the common device is updated according to a subscription request for the user event package of the IMS device.

The user event package manager 220 generates, updates, deletes and manages a user event package under the control of the registration processor 210.

The communication unit 240 transmits various data and messages under the control of the registration processing unit 210, and transfers the received data and messages to the registration processing unit 210.

The storage unit 230 stores a program for processing and controlling the registration processing unit 210, reference data, various kinds of updatable storage data, and the like, and is provided as a working memory of the control unit 210. The storage unit 230 stores state information of the common device and a user event package corresponding to each IMS device.

The process of registering the IMS device 100 configured as described above with the application server 200 configured as described above as a common device according to the present invention is as follows.

In order to enable other users to use their IMS device 100, the owner of the IMS device must first perform registration of the IMS device with respect to the IMS network 80. 100 is preferably registered in the application server 200 as a shared device.

Accordingly, in an embodiment of the present invention, a shared header is added to a REGISTER message used when registering the IMS device 100 to the IMS network, and the corresponding IMS device 100 is added to the shared header. It can be included to the user who can share, that is, the user ID of the shared user. This shared header will be information indicating that the IMS device indicated by the register message will be registered as a public device.

The IMS device 100 receives a device address of the IMS device 100 from the IMS network 80 in the process of accessing the IMS network 80. When a sharing registration request for the IMS device 100 is input from the user through the user interface 150, the controller 110 may enter a menu window for inputting a user ID of a public user through the user interface 150, and an IMS. Provides a menu window for inputting the type of application service to use the device 100 as a common device. The user may directly input a user ID of a specific user who permits sharing with the IMS device 100, or may select one or more of user IDs of others already present in the memory unit 130 of the IMS device 100. have. The user may select one or more types of application services to use the IMS device 100 as a shared device. For example, the user may select the IMS device 100 to be used as a common device in the multimedia stream service and the message service. Alternatively, the IMS device 100 may be selected to be used as a common device in all application services to which the IMS device 100 is subscribed.

Accordingly, the controller 110 configures a register message including the shared header and includes the user ID input or selected by the user in the shared header. The feature tag corresponding to the application service selected by the user is included in the register message and then transmitted to the S-CSCF server 30.

Table 1 shows an example of a register message according to an embodiment of the present invention.

In Table 1, the shared header 'Shared' enters a user ID that allows the use of the IMS device. According to the example of Table 1, the address of the IMS device to be shared is 'sip: joe@pc34.example.com', the actual owner is Joe and the user ID 'sip: joe@example.com' is used. . The user IDs of the users allowed to use the device by Joe are Alice ('sip: alice@example.com') and Bob ('sip: bob@example.com'), respectively. .

Alice and Bob must be subscribed to at least one of the application services Joe subscribes to. That is, a user who is not subscribed to an application service subscribed to by the owner of the IMS device Joe cannot use the device. Because as will be described later, the register message is a third party registration (3rd party registration) is transmitted only to the application server of the application service to which the real owner of the device is subscribed.

Receiving the register message, the S-CSCF server 30 binds the user address (Joe) of the two headers and the device address of the contact header (Contact header) through the register message as in the conventional method. And manage this information.

The S-CSCF server 30 receives a user profile of a user (Joe) requesting registration from the HSS 40, an application service subscribed to by the user requesting registration, and a feature tag included in a register message. After checking the application services of the third party registration (3rd party registration) for the corresponding application services. Here, the third party registration means that the S-CSCF server 30 registers the application server on behalf of the user, and the S-CSCF server 30 generates a register message and transmits it to the application server. .

The use of third party registration varies by application service. For example, a Converged-IP Message (CPM) service uses third-party registration for informing an application server that a user is connected to the IMS network 80. In the present invention, in addition to the use as in the CPM, the user information that is allowed to use the IMS device is transferred to the application server, or a user having the use authority sends the request for use and discontinuance of the IMS device to the application server to the application server. It is used for the purpose of delivery. Therefore, when the register message received from the IMS device 100 includes the shared header, the S-CSCF server 30 should include the shared header in the register message for third party registration as it is. . The feature tag included in the register message received from the IMS device 100 is also included.

In order to provide convenience to the user, the application server 200 needs to check and manage a service use status and related information of a service subscriber (user) periodically or at a specific time point. In particular, in connection with the present invention, whether the application server 200 is currently connected to the IMS network, what IMS device is being used, and whether the use rights for the IMS device of another person are set, if applicable. You should check and manage the information about the device address of the IMS device. In the present invention, a user event package is defined in order to bundle and manage such a series of user information as a unit.

Table 2 shows an example of a user event package.

Referring to Table 2, the description of each item included in the user event package is as follows.

User element: Represents a user ID indicating which user's user event package.

Contact element: Displays IMS device information available as a user ID. It has a uri element as its child element.

id attribute: Since multiple IMS devices can be used as one user ID, an id value for identifying each IMS device is represented.

State attribute: Represents an available state of an IMS device. In other words, it may indicate whether the user occupies the corresponding IMS device. "Active" means that the IMS device is currently in use by someone or is available by the user corresponding to the user event package, and "pre-active" means that the IMS device is available. Indicates that permissions are present but not available. In addition, the active state indicates that the corresponding IMS device is occupied by a user, and the pre-active state indicates a state where the corresponding IMS device is not occupied. In order to use an IMS device, the user must switch the state of the device to "active" with a separate request.

According to another exemplary embodiment of the present invention, the active state may be configured to distinguish whether the active state is activated by the user corresponding to the corresponding user event package or the active state by another user. In the following description, it is assumed that these two states are not distinguished.

Event attribute: indicates what cause the IMS device is associated with the user ID for some reason. If it is “registered”, the IMS device is the user's own IMS device and the user himself performs registration and is associated with the user ID. Means that. If it is "shared", it means that the IMS device is not its own IMS device but is associated with the user ID because the device is licensed from the owner of the IMS device.

uri element: Represents the address of an IMS device.

The interpretation of the example in Table 2 is as follows. In an IMS application service, Joe can use two IMS devices with his user ID (“sip: joe@domain.com”). One is his personal IMS device (“sip: joe@pc34.example.com”) and the other is Alice's IMS device (“sip: alice@192.0.2.4”). Since their IMS device is "active", it is immediately available and the use of the IMS device is granted to the public device, that is, Alice's IMS device. Since the state of the common device is “free active”, Joe needs to switch the state of the IMS device to “active” through a separate usage registration request in order to use this IMS device.

The user may request his / her user event package from the application server 200 to check necessary information. The user transmits a SUBSCRIBE message to the application server 200 to receive the user event package using his or her IMS device. At this time, the event header is input as “user”. The application server 200 receiving the request transmits a NOTIFY message to the corresponding user after authenticating the user for the subscription requester, and the user event package of the subscription requester may be included in the body part of the NOTIFY message.

The application server 200 generally receives a register message from the S-CSCF server 30 through 3rd party registration in three cases.

1) Registration: When IMS device is registered in IMS network

2) Re-registration: When renewing registration for IMS network

3) Deregistration: In case of deregistration for IMS network

In the present invention, the registration is used not only for general purpose but also to set up another person's use authority for his or her own personal IMS device in the application server 200, that is, for shared registration, and for another person's IMS device. The authorized user is used to request the application server 200 to register the use of the corresponding IMS device.

In the present invention, the deregistration is also used for the purpose of releasing the registration of the use of the IMS device by a user who has the authority to use the IMS device of another person.

In the above, re-registration is generally used for extending or updating the use registration for the IMS network 80. Re-registration does not have any special meaning other than the use registration update in the present invention, and because the message format is also the same as Registration, it is treated in the same manner as Registration in the application server 200.

An operation process of the application server 200 according to an embodiment of the present invention will be described with reference to FIGS. 4 to 6. 4 is a diagram illustrating a process of registering a specific IMS device as a shared device in the application server 200 according to an embodiment of the present invention, and FIG. 5 is an IMS device registered as a shared device according to an embodiment of the present invention. Is a diagram illustrating a process of switching to an active state for use by a shared user. 6 illustrates a process of switching a state of a shared device to a pre-active state in order to stop using a shared device that is being used by a shared user according to an embodiment of the present invention.

In the following description, the first IMS device 710 is registered as a shared device, the second user of the second IMS device 720 is designated as a shared user, and the second IMS device 720 is designated to facilitate understanding of the present invention. The process of FIGS. 4 to 7 will be described on the assumption that the first IMS device 710 is registered to be used and deregistered to be used by the second user. The first IMS device 710 and the second IMS device 720 are configured similarly to the IMS device 100.

At the request of the first user, the first IMS device 710 transmits a register message to the S-CSCF server 30 that includes the second user of the second IMS device 720 as the shared user.

The S-CSCF server 30 corresponds to the application service specified by the feature tag included in the register message to perform the third party registration after performing an appropriate operation on the register message received from the first IMS device 710. The register message is transmitted to the application server 200.

Accordingly, the application server 200 receiving the register message from the S-CSCF server 30 in step 301 of Figure 4 checks whether the shared header is included in the register message in step 303, if the shared header is included, Proceed to step 305. If the shared message is not included in the register message, the process proceeds to A and performs the process shown in FIG. The inclusion of the shared header in the register message means that the shared registration request for registering the first IMS device 710 to the application server 200 as a common device through the corresponding register message is included.

In step 305, the application server 200 checks whether the user ID inputted in the shared header of the register message is its own application service subscriber. If it is not the user ID of the own application service subscriber, the application server 200 does not perform any operation with respect to the corresponding user ID. If the shared header of the register message includes the user ID of the own application service subscriber, the application server 200 proceeds to step 307 to check whether the IMS device of the corresponding user ID is connected to the application service. If not connected, the application server 200 waits until the IMS device corresponding to the user ID is connected to the application server 200. However, if the IMS device of the corresponding user ID does not access the application service until the validity period of the register message expires, the register message is discarded without performing any operation. In this embodiment, the user ID will be the user ID of the second user, and accordingly, the application server 200 will check whether the IMS device of the second user is connected to the application service.

If the IMS device corresponding to the user ID is in the state of accessing the application service, in step 309, the application server 200 includes a specific IMS device included in the register message in the user event package of the corresponding user ID, that is, the first IMS device 710. Add information about). At this time, the first IMS device 710 is added as a shared device to the user event package. That is, a contact element corresponding to the first IMS device 710, a related attribute, and an uri element are added, and an event attribute of the added contact element is 'shared' indicating that the shared device is a shared device, and the state of the shared device is free. Becomes active.

Steps 305, 307, and 309 are performed for each user ID when a plurality of user IDs are included in the shared header.

Meanwhile, the second user may subscribe (SUBSCRIBE) the user event package in order to check the public device that can be used by the second user. To this end, the second user transmits a SUBSCRIBE message to the application server 200 to subscribe to the user event package through his or her IMS device, that is, the second IMS device 720. The subscription message may be sent at the time the user requests, or may be automatically transmitted when the second IMS device 720 is connected to the application service.

The application server 200 receiving the subscription message constructs a NOTIFY message including information on a user event package corresponding to the second IMS device 720, and transmits a NOTIFY message to the second IMS device 720. Thereafter, whenever a new IMS device is added to a user event package or the status information of a public device existing in the user event package is updated, a NOTIFY message including information about the user event package is configured. The second IMS device 720.

As pointed out in the problem of the prior art, if the user can know the address of the IMS device of another person to use, it is possible to register the IMS device through their own IMS device to use in connection with their user ID. In this regard, the present invention defines a user event package, and presents a method for a user to request a user event package from the application server 200.

Upon receiving a NOTIFY message including information on the user event package, the second IMS device 720 provides the user with information about the public device. For example, a list of public devices included in the received user event package information and status information of each public device are displayed, so that the user can select a public device to use. At this time, the second IMS device 720 searches the log record of the register message for the common device in the active state, and confirms whether there is a registration of use by the second IMS device 720, so that the corresponding device has already been used by the second user. It can be displayed by distinguishing whether occupied by or occupied by another user.

The second user checks the list of public devices and the status information for each public device, selects a public device that is authorized to use, that is, a public device that is pre-active, and requests usage registration to occupy the selected public device. It may be possible to request re-registration to extend the period of occupancy for a common device already occupied. You can also request to unregister the use of a shared device that you already own. These requests are included in the register message and sent to the application server 200.

If the second user requests usage registration for a public device that is pre-active, or if the second user requests an extension of the occupancy period for a public device that is already occupied, the second IMS device 720 corresponds to the user event package information. Detect the device address of the shared device. The device address of the detected common device and the device address of the second IMS device 720 form a register message included in the contact header, and are transmitted to the application server 200 through the S-CSCF server 30. In this case, the shared header is not included in the register message. This is because the shared header is used only for setting sharing permission for the IMS device.

When the second user requests to release usage registration for the shared device already occupied by the second user, the second IMS device 720 detects the device address of the shared device from the user event package information. The device address of the detected common device and the device address of the second IMS device 720 are included in the contact header, and the register message in which the value of the Expires header is set to “0” is configured to configure the S-CSCF server ( Transfer to the application server 200 through 30).

The second IMS device 720 may request the application server 200 to provide an application service to a common device already occupied by the user, at the request of the user.

The operation of the application server 200 according to the register message transmission of the second IMS device 720 is as follows. First, an application server when a second user requests usage registration for a public device that is pre-active through the second IMS device 720 or requests for extension of an occupancy period for a public device already occupied by the second user ( An operation process of 200 will be described with reference to FIGS. 4 and 5.

As the second IMS device 720 transmits the register message, the application server 200 receives the register message from the S-CSCF server 30 in step 301 of FIG. 4, and shares the header with the register message received in step 303. Confirm that is not included, proceed to step A of FIG.

Referring to FIG. 5, in operation 401, the application server 200 determines whether a use registration release request is included in a register message. If the use registration release request is not included, the application server 200 proceeds to step 403, and includes a use registration release request. If so, the process proceeds to step B, and the operation process of FIG. 6 is performed. Whether to include the usage registration release request may be determined by checking the expiration field value of the register message.

In step 403, the application server 200 checks whether the device address included in the register message exists in the user event package corresponding to the second IMS device 720, and if so, proceeds to step 407 and, if not, proceeds to step 405. do. Herein, the device address can be confirmed from the contact header of the register message, and the user ID of the registration requester can be known from the To header of the register message.

If the register message does not include the shared header and the device address included in the register message does not exist in the user event package, the register message is a new registration request message for the second IMS device 720. Add information to the user event package.

If the corresponding device address is already recorded in the user event package, for example, if the device address is the device address of the first IMS device 710, in step 407, the state of the first IMS device 710 is pre-active. do. If the state of the common device is in the pre-active state, the register message is considered to be a message for requesting the use registration for the common device, and the state of the public device is changed to the active state in step 409. And the device address of the first IMS device 710 and the user ID of the second user are bound.

If the state of the public device is not the pre-active state, that is, the active state, the public device is already registered for use by someone, so the user ID of the user who occupies the public device is checked. If the user ID of the user who occupies the common device and the user ID included in the received register message match, the register message is a message for registration update, and thus the operation accordingly is performed. If the user ID of the user who occupies the corresponding public device and the user ID included in the received register message do not match, the register message is ignored, no special operation is performed, or an error message is sent to the second IMS device 720. Send.

Steps 403 to 409 are performed for each device address when a plurality of device addresses are included in the contact header of the received register message.

Next, a process of releasing the use registration for the currently occupied common device will be described with reference to FIG. The second user may discontinue use of the first IMS device 710, in which case the state of the first IMS device 710 is switched to a free active state so that other users can use the first IMS device 710. Should be. Accordingly, when the second user inputs a disable request for the first IMS device 710 to the second IMS device 720, the second IMS device 720 is a corresponding public device, that is, the first IMS device ( Detects the device address of 710). Then, the device address of the detected common device and the device address of the second IMS device 720 are included in the contact header, and a register message in which the value of the Expires header is set to “0” is configured to configure the S-CSCF server ( Transfer to the application server 200 through 30).

When the S-CSCF server 30 receives the register message from the second IMS device 720, the S-CSCF server 30 transmits the register message to the corresponding application server 200 through third party registration.

In step 301 of FIG. 4, if the application server 200 receives the register message from the S-CSCF server 30, in step 303, the application server 200 does not include the shared header, the process proceeds to step 401. Check the header value of the expiration header to see if it contains the deregistration request. If the header value of the expiration header is "0", the application server 200 determines that a deregistration request is included, and proceeds to step B and performs step 501 of FIG. 6.

In step 501, the application server 200 checks the event attribute value of the device address included in the register message in the user event package corresponding to the IMS device that has transmitted the received register message, and determines whether the corresponding IMS device is a public device or a personal device. Check it. That is, the application server 200 checks an event attribute value of the first IMS device 710 in the user event package corresponding to the second IMS device 720. If the event attribute value is "registered", the corresponding IMS device is registered as a personal device. If the event attribute value is "shared", the IMS device is registered as a public device.

If the event attribute value of the corresponding IMS device is “registered,” the application server 200 proceeds to step 505 and determines that the received register message is a message for requesting deregistration, and determines the user event package information of the corresponding IMS device. If the event attribute value of the corresponding IMS device is “shared”, the application server 200 determines that the received register message is a message requesting registration of use of the corresponding IMS device, Change the state of the IMS device to the free-active state.

7 illustrates a message flow according to the shared registration process, the use registration process, and the use registration release process according to the present invention. In FIG. 7, steps 603 to 611 correspond to a shared registration process, steps 617 to 625 correspond to a use registration process, and steps 629 to 639 correspond to a use registration release process.

Referring to FIG. 7, it is assumed that the first IMS device 710 is not registered in the IMS network 80 in step 601, but the second IMS device 720 is registered in the IMS network 80. This is an example and in fact, even if the first IMS device 710 is registered later than the second IMS device 720, it is irrelevant to the operation of the present invention. In step 603, the first IMS device 710 registers the first IMS device 710 as a shared device with the application server 200, and registers a register message including a shared header including a user ID of the second user. Send to server 30.

The S-CSCF server 30 transmits a 200OK message for the register message received in step 605 to the first IMS device 710 in step 605, and transmits a register message including a shared header in step 607. Send to

The application server 200 adds the information on the first IMS device 710 to the user event package corresponding to the second IMS device 720, that is, the user event package corresponding to the second user, and the first IMS device 710. ) Is set to the free-active state. In step 611, the 200-OK message is transmitted to the S-CSCF server 30 in response to the register message received in step 607.

In this case, if the application server 200 includes a feature tag indicating an application service provided by another application server in addition to the application service provided by the application server 200 in the register message received in step 603, the other application server. The mobile station may transmit a subscription message requesting a subscription to status information of the first IMS device 710. This is because when a specific shared user connected to the other application server occupies the first IMS device 710, the state of the first IMS device 710 becomes active, or a specific shared user uses the first IMS device 710. When the registration is released and the state of the first IMS device 710 is switched to pre-active, the application server 200 also changes the state of the first IMS device 710 appropriately.

In operation 613, the second IMS device 720 transmits a subscription message to the application server 200 in order to subscribe to the information on the user event packet corresponding to the second IMS device 720. Although the transmission time of the subscription message is illustrated as after the information on the first IMS device 710 is added to the user event package corresponding to the second user in the embodiment of FIG. 7, in the tense, the second IMS device 720 is applied to the application server. While connected to 200, it is possible at any time.

In response to the subscription request of the second IMS device 720, the application server 200 includes the information on the user event package corresponding to the second IMS device 720 in the notification message and transmits the information to the second IMS device 720 in step 615. do. Thereafter, the application server 200 transmits a notification message to the second IMS device 720 whenever the status information of the IMS device included in the user event package of the second IMS device 720 is changed.

According to the user's request, the second IMS device 720 configures a register message for requesting a use registration request for the first IMS device 710 with reference to the received event package information, and in step 617, the S-SCSF server 30. Send to The S-CSCF server 30 transmits a 200 OK message to the second IMS device 720 in step 619 in response to the register message received in step 617. In operation 621, the S-CSCF server 30 transmits the register message received in operation 617 to the application server 200.

In operation 623, the application server 200 changes the state information corresponding to the first IMS device 710 into an active state in the user event package corresponding to the second IMS device 720. In this case, if the shared user for the first IMS device 710 exists in addition to the second user among the service subscribers, the application server 200 may be applied to the first IMS device 710 included in the user event package corresponding to the shared user. The status information about the switch also becomes an active state.

In step 625, the 200 OK message corresponding to the register message received in step 621 from the S-CSCF server 30 is transmitted to the S-CSCF server 30. In addition, since the state information of the first IMS device 710 is changed in the user event package corresponding to the second IMS device 720, in operation 627, a notification message including information about the user event package is transmitted to the second IMS device 720. do.

When the second user completes the use of the first IMS device 710, the second user may request the application server 200 to release the use registration of the first IMS device 710. Accordingly, in operation 629, the second IMS device 720 constructs a register message for requesting release of usage registration of the device 710 and transmits the registered message to the S-SCSF server 30. The S-CSCF server 30 transmits a 200 OK message to the second IMS device 720 in step 631 as a response to the register message received in step 6297. The S-CSCF server 30 transmits the register message received in step 633 to step 629 to the application server 200.

Accordingly, the application server 200 changes the state of the first IMS device 710 to the pre-active state in the user event package corresponding to the second IMS device 720 in step 635. If the shared user for the first IMS device 710 exists in addition to the second user among the service subscribers, the state information of the first IMS device 710 included in the user event package corresponding to the shared user is also pre-active. Switch.

The 200 OK message corresponding to the register message received in step 639 is transmitted to the S-CSCF server 30. In addition, since the state information of the first IMS device 710 is changed in the user event package corresponding to the second IMS device 720, in operation 631, a notification message including information about the user event package is transmitted to the second IMS device 720. do.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. Therefore, the scope of the present invention should not be defined by the described embodiments, but should be determined by the equivalent of claims and claims.

Claims (24)

In a method for allowing an application server providing an Internet protocol Multimedia Subsystem (IMS) application service to share an IMS device among users,
Receiving a sharing registration request message requesting the first IMS device to register the first IMS device as a common IMS device to which a plurality of users are entitled;
Adding information about the first IMS device to a user event package corresponding to a user ID of at least one shared user included in the sharing registration request message and including information on a public IMS device to which the shared user has permission to use. IMS device sharing method between the user characterized in that it comprises a process of. The method of claim 1, further comprising providing an IMS application service corresponding to the shared user to the first IMS device according to a request of the shared user. 3. The method of claim 2, wherein the shared registration request message is a register message, a user ID of the shared user is included in a shared header of the register message, and the register message is stored in a serving call session control function (S-CSCF) server. 3rd party registration (3rd Method of sharing an IMS device between users, characterized in that delivered to the application server by party registration). The method of claim 2, wherein the user event package includes a device address of the first IMS device and state information indicating whether a user occupies the first IMS device.
A method for sharing IMS devices between users, the method comprising: determining whether the user occupies the first IMS device and managing the state information. The method of claim 4, wherein the adding of the information on the first IMS device comprises:
Checking whether a user ID matching the user ID of the shared user exists in the user ID of each subscriber subscribed to the IMS application service;
If the matching user ID exists, the device address of the first IMS device may be added to the user event package corresponding to the user ID of the shared user, and the state of the first IMS device may be occupied for the first IMS device. And setting the pre-active state to indicate the IMS device sharing between users. The method of claim 5, further comprising: receiving a usage registration request message for changing a state of the first IMS device from a second IMS device to a state in which the IMS application service can be provided;
If the user event package related to the second IMS device includes the information of the first IMS device, it indicates that the state of the first IMS device is occupied and the IMS corresponding to the user of the second IMS device. Transitioning to an active state in which application services can be provided;
And providing the IMS application service corresponding to the user of the second IMS device to the first IMS device. The method of claim 6, wherein the transition to the active state comprises:
If the user event package associated with the second IMS device includes information of the first IMS device, checking a state of the first IMS device;
If the state of the first IMS device is the pre-active state, switching the state of the first IMS device to the active state;
And switching the state of the first IMS device to an active state in each of all user event packages related to the first IMS device. The method of claim 7, further comprising: receiving a usage registration release request message for the first IMS device from the second IMS device;
Checking the state of the first IMS device when the user event package related to the second IMS device includes the information of the first IMS device;
As a result of the checking, if the state of the first IMS device is the active state and the switching to the active state is caused by the second IMS device, switching the state of the first IMS device to the pre-active state;
And converting a state of the first IMS device into an active state in each of all user event packages associated with the first IMS device. An application server device that provides an IMS (Internet protocol Multimedia Subsystem) application service and allows an IMS device to be shared among users,
A user event package manager configured to manage a user event package corresponding to each user provided with the IMS application service;
Receiving a sharing registration request message requesting a plurality of users to register the first IMS device as a common IMS device with rights to use by a first IMS device, the user ID of at least one shared user included in the sharing registration request message And a registration processor configured to control the user event package manager to add information about the first IMS device to a user event package including information on an IMS device to which the shared user has permission to use. Application server device. The apparatus of claim 9, wherein the registration processing unit provides an IMS application service corresponding to the shared user to the first IMS device according to a request of the shared user. 12. The method of claim 10, wherein the shared registration request message is a register message, a user ID of the shared user is included in a shared header of the register message, and the register message is stored in a serving call session control function (S-CSCF) server. 3rd party registration (3rd and the application server device is delivered to the application server by party registration. The apparatus of claim 10, wherein the user event package includes a device address of the first IMS device and state information indicating whether a user occupies the first IMS device.
And the registration processing unit determines whether the user occupies the first IMS device and manages the state information. The method according to claim 12, wherein the registration processing unit checks whether a user ID matching the user ID of the shared user exists in the user ID of each subscriber subscribed to the IMS application service to add information about the first IMS device. And if the matching user ID exists, adds the device address of the first IMS device to the user event package corresponding to the user ID of the shared user, and occupies the state of the first IMS device with respect to the first IMS device. The application server device, characterized in that the setting to the pre-active state that is possible. The user device of claim 13, wherein the registration processing unit receives a usage registration request message for changing a state of the first IMS device from a second IMS device to a state in which the IMS application service can be provided, and a user associated with the second IMS device. If the event package includes the information of the first IMS device, it indicates that the state of the first IMS device is occupied and that the IMS application service corresponding to the user of the second IMS device can be provided. Switching to a state and providing an IMS application service corresponding to a user of the second IMS device to the first IMS device. The method of claim 14, wherein the registration processing unit is configured to switch to the active state.
If the user event package associated with the second IMS device includes the information of the first IMS device, the state of the first IMS device is checked, and if the state of the first IMS device is the pre-active state, And converting a state of a 1IMS device into an active state and converting a state of the first IMS device into an active state in each of all user event packages associated with the first IMS device. The method of claim 15, wherein the registration processing unit receives a usage registration release request message for the first IMS device from the second IMS device, and the information on the first IMS device is included in a user event package associated with the second IMS device. Confirm the state of the first IMS device, and if the check result indicates that the state of the first IMS device is the active state and the switching to the active state is caused by the second IMS device, the state of the first IMS device is determined. Switching to a pre-active state, and switching the state of the first IMS device to an active state in each of the user event packages associated with the first IMS device. A method for sharing an IMS device among users by an IMS device provided with an Internet protocol Multimedia Subsystem (IMS) application service,
Transmitting a subscription request message for a user event package corresponding to the IMS device to the application server providing the IMS application service and including information on an IMS device to which a user of the IMS device has authority to use;
Receiving a notification message including information of the user event package from the application server;
Displaying a list of IMS devices included in the user event package information and information indicating whether each of the IMS devices included in the IMS device list is a common IMS device to which a plurality of users are entitled;
Sending a usage registration request message to the application server requesting the occupancy of the specific public IMS device selected by the user;
And transmitting a message requesting to provide the IMS application service to the specific public IMS device to the application server. 18. The method of claim 17, wherein the display displays status information indicating whether the user occupies each of the common IMS devices. 19. The method of claim 18, further comprising the step of sending a message to the application server requesting to stop the occupancy of the specific public IMS device. 19. The method of claim 18, further comprising: selecting at least one user ID to which the user is entitled to use the IMS device according to a user input;
Selecting at least one IMS application service that can be provided through the IMS device;
Generating a shared registration request message including the selected at least one IMS application service and a user ID and requesting to register the IMS device as an IMS public device;
And transmitting the shared registration request message to an IMS network. In the IMS device receiving an IMS (Internet protocol Multimedia Subsystem) application service and sharing the IMS device among users,
A transceiver for performing communication with an application server providing the IMS application service;
And transmits a subscription request message for a user event package corresponding to the IMS device to the application server through the transceiver, the user event package including information on an IMS device that the user of the IMS device has permission to use, and from the application server. Receive a notification message including the information of the user event package, and whether the list of IMS devices included in the user event package information and each IMS device included in the IMS device list is a common IMS device that has rights to a plurality of users. A message requesting to display the information indicating the information, to send a usage registration request message requesting the occupancy of the specific public IMS device selected by the user to the application server, and to provide the IMS application service to the specific public IMS device. It includes a control unit for transmitting to the application server IMS instrument of Jing. 22. The IMS device according to claim 21, wherein, during the display, status information indicating whether a user occupies each of the common IMS devices is displayed together. 22. The IMS device of claim 21, wherein the controller transmits a message to the application server requesting that the specific public IMS device be stopped. The method of claim 21, wherein the controller selects at least one or more user IDs to which the user is authorized to use the IMS device according to a user input, and provides at least one IMS application service that can be provided through the IMS device. Select, including the selected at least one IMS application service and a user ID, generate a sharing registration request message requesting to register the IMS device as an IMS public device, and send the shared registration request message to the IMS network IMS device characterized in that.

Images