WO2011002163A2

WO2011002163A2 - Inter-user equipment transfer method

Info

Publication number: WO2011002163A2
Application number: PCT/KR2010/003642
Authority: WO
Inventors: 김래영; 김태현; 김현숙
Original assignee: 엘지전자 주식회사
Priority date: 2009-06-30
Filing date: 2010-06-07
Publication date: 2011-01-06
Also published as: WO2011002163A3; KR20110001696A

Abstract

The present specification provides an inter-user equipment transfer method which transfers a portion or the entirety of a medium and/or of a service control authority to another terminal when a session, constituted by one or more media from among a plurality of media such as audio, video, text, etc., is in progress between one terminal and a service provider. The method comprises a step of transmitting, to a network entity, a group generation request message containing at least an indicator of the group to be generated, so as to generate a group. The method further includes a step of transmitting, to the network entity, a notification request message for at least one of state information and capability information of each of the terminals which belong to the group. In addition, the method further comprises a step of receiving a notification message containing information on the state and capability of each terminal when each terminal is registered/unregistered to/from an IMS or information on the state or capability of the terminal is changed. In addition, the method further comprises a step of selecting, on the basis of the information on the state or capability, a terminal from among the terminals of the group to move the session.

Description

How to move between terminals

The present invention relates to a method of moving between terminals of a media flow and / or service control right.

In general, in a network based on IP Multimedia Subsystem (IMS), a session between a first terminal and a service provider or between the first terminal and the second terminal is controlled and performed by an application server.

In recent years, the spread of terminals has increased, and users are using a plurality of terminals.

As described above, in a situation where a user uses a plurality of terminals, a part or all of the media flows and / or service control authority of the user's first session, which are conducted through the first terminal, are transferred to the second terminal of the user. Research is underway on the technologies that can be delivered.

As described above, the transfer of some or all of the media flow and / or the service control right constituting the session between the terminals is called an inter-UE transfer (IUT). This will be described with reference to FIG. 1.

1 is a conceptual diagram illustrating a movement between terminals according to the prior art.

Referring to the left side of FIG. 1A, the first user owns a plurality of terminals, for example, User Equipment (UE) -1, UE-2, and UE-3 shown. And the first user is in session with a remote end, such as a service provider, with voice and video media via UE-1. SCC AS (Service Centralization and Continuity Application Server) is shown to control the session.

In this situation, the first user wishes to proceed with the session with the remote end through his UE-2 and UE-3, respectively. For example, if the UE-1 is a cellular phone, the UE-2 is an ear set or a headset having a communication function, and the UE-3 is a head up display (HUD) with a communication function. The first user wishes to conduct a voice media session via the earset or headset and conduct the video media session with the remote end via the head-up display.

Then, the voice media flow is moved to the UE- 2 in the session consisting of the voice and video media that has already been conducted through UE- 1 as shown in the right side of FIG. 1 (a), and the video media flow is moved to the UE-. Is moved to 3. In this case, even after the voice and video media flows are moved to the UE- 2 and the UE- 3, the UE- 1 maintains the control right for the media flows.

In this case, the UE- 1 is called a controller UE, and the UE- 2 and UE- 3 are called a controllee UE. The session including the voice and video media and in which the UE-1, UE-2, and UE-3 participate is called a collaborative session.

Meanwhile, referring to the left side of FIG. 1B, the first user is conducting a session for the voice media through the UE-2 and a session for the video media through the UE-3.

In this case, the UE-1 has control authority over the voice media flow on the UE-2 and the video media flow on the UE-3, but the control authority is transferred to the UE-2 as shown in the right side of FIG. Move it. This makes the UE-2 the controller UE for the cooperative session in which the UE-2 and UE-3 participate, including the voice and video media.

On the other hand, the IUT is a concept made between a plurality of terminals within the same user, or by extending such a concept to move part or all of the media flow and / or service control authority between terminals belonging to different users. There is also research going on.

As described above, in order for the UE-1 to perform the IUT operation, the UE-1 is informed whether each target terminal, for example, the aforementioned UE-2 and UE-3 is registered in the network. You must lose.

In addition, in order for the UE-1 to perform the IUT operation, the capability information of each target terminal, for example, the aforementioned UE-2 and UE-3, for example, hardware resource information (ie, a speaker microphone and a camera). , Information about a screen), configuration information of the hardware (ie, resolution information, etc.), information on supportable media, codec information, and the like should be known to the UE-1.

To this end, conventionally, the process of moving between terminals as shown in FIG.

2 shows a process of moving between terminals according to the prior art.

As can be seen with reference to FIG. 2, user A uses ID A_IMPU1 and owns a plurality of terminals, eg, UE-A1 11, UE-A2 12, and UE-A3 13. User B uses B_IMPU1 as an ID and owns a plurality of terminals, for example, UE-B1 21 and UE-B2 22.

In addition, FIG. 2 illustrates a home network to which the A user and the B user subscribe. The home network includes an IMS (IP Multimedia Subsystem) node and an SCC AS.

In FIG. 2, user A is in session with the remote end and voice and video media via UE-A1 11, and user A is to UE-B2 22 owned by user B. FIG. We want to move the video media flow while maintaining session continuity. A detailed description will be given below with reference to FIG. 2.

1-2) The UE-A1 11 registers with its home network a REGISTER message and receives an acknowledgment message. In this case, registration means that the UE notifies its current location to the home network.

3) The UE-A1 11 is an IMS node of the home network in order to obtain status / capability information of UEs registered as the user A, A_IMPU1, that is, UE_A2 12 and UE_A3 12. 51) SUBSCRIBE message is sent to request information subscription subscription to other terminals.

4) The IMS node 51 sends a message to the UE-A1 to accept the request for information notification subscription for the UE registered with the user ID A_IMPU1.

5) In order for the UE-A1 11 to acquire status / capability information of UEs registered as the B user's ID and B_IMPU1, that is, UE_B1 21 and UE_B2 22, the IMS node 51 Send a SUBSCRIBE message to the user, and requests to subscribe to the information notification for the terminal owned by the user B.

6) The IMS node 51 sends a message to the UE-A1 11 that accepts the information notification subscription request for the UE registered as the user B, B_IMPU1.

7a-7d) When the UE-A1 11 transmits a session initiation request message (eg, SIP-based INVITE message) to perform a session connection consisting of voice and video media with the remote end 30, the IMS node. 51 transmits to the remote end 30 via the SCC AS 52 based on the subscriber information of the user A.

8a-8d) When the remote end 30 transmits a session start acceptance message (eg, SIP based 200 OK) to the UE-A1 11, a session composed of the voice and video media is established.

9 to 10) Meanwhile, the UE-B1 21 of the B user transmits and registers a REGISTER message on his home network.

11-12) As the UE-B1 21 registers, the IMS node 51 transmits a NOTIFY message including state / capability information of the UE-B1 21 to the UE-A1.

13 to 14) Meanwhile, the UE-B2 22 of the B user transmits and registers a REGISTER message on his home network.

15 to 16) As the UE-B2 22 registers, the IMS node 51 transmits a NOTIFY message including state / capability information of the UE-B2 22 to the UE-A1 11. do.

17) It is determined that the video media flow of the UE-A1 () is moved, and the UE-B2 22 is selected as the target UE among the UE_B1 21 and the UE_B2 22 of the B user.

18a-18b) The UE-A1 11 transmits a move request message, for example, a Media Transfer request message, to the SCC AS 52 to move the video media flow to the UE-B2 22.

19a to 19b) the SCC AS 52 delivers the movement request message to the UE-B2 22.

20a to 20b) Since the UE-B2 22 cannot participate in the inter-terminal movement operation in a situation, the UE-B2 22 transmits a rejection message for the movement request message to the SCC AS 52.

21a to 21b) The SCC AS 52 sends a message indicating that the movement of the video media flow has failed to the UE-A1 11.

Up to now, the movement between terminals of the same owner or between terminals of different owners has been described. As can be seen above, in order to perform the inter-terminal movement operation, the state / capability information of the terminals must be obtained from the IMS network. In order to obtain the state / capability information as described above, each terminal must exchange an IMS network with an information notification subscription / accept message for each of the IP multimedia public identity (IMPU).

However, transmitting the information notification subscription / accept message for each IMPU induces signaling overhead between the UE and the IMS network.

In addition, such signaling overhead increases as the number of users interworking with each other for the inter-terminal movement operation increases, and as the number of IMPUs used by one user increases.

In addition, as can be seen in Figure 2, even if there is a terminal that does not want to participate in the inter-terminal movement operation or can not participate in the inter-terminal movement operation, that is, the UE-B2 (22), the terminal to move the media flow, namely Since the UE-A1 11 does not know such a situation, the movement between the terminals ends in failure. And such a failure causes unnecessary signaling overhead.

Accordingly, an object of the present invention is to solve the above problems.

In other words, an object of the present invention is to reduce the transmission of the information notification subscription / acceptance message.

In addition, another object of the present invention is to enable the movement between terminals can be performed without failure.

In order to achieve the above object, the present specification proposes a method of managing the terminals that interoperate with each other in a group for an inter-UE transfer operation. In addition, by allowing the user to subscribe to the information notification service by using the identifier of the group, it is possible to efficiently obtain the status / capability information of the terminals belonging to the group.

In addition, the present specification proposes a method for adding the members of the group for each terminal.

Specifically, in order to achieve the above object, the present specification provides a session comprising one or more media of voice, video, and text media in a remote stage and in progress, in which part or all of the media and one or more of service control rights are different. It provides a method of moving to a terminal. The method includes sending a group create request message for group creation to a network entity. Here, the group creation request message includes at least an identifier of the group to be created. In addition, the group creation request message includes at least information on a group administrator managing the group. The method also includes sending a notification request message for one or more of state and capability information of each terminal belonging to the group to the network entity. The method may further include receiving a notification message including information on the state and capability of each terminal when the terminal is registered or registered in the IMS or when the state or capability information of each terminal is changed. Steps. And the method comprises selecting, based on the information on the status and capability, a terminal to which a part or all of the media or a service control authority is to be moved among the terminals in the group.

The method includes receiving, via the network entity, a member addition request message for the group from another terminal; Determining whether to accept the member addition request sent by the other terminal for the group; If it is determined to allow the acceptance, the method may further include sending an acceptance message to the network entity.

The method may further include after receiving the accept message, receiving a notification message from the network entity, the notification message including information about the status and capabilities of the other terminal.

The member addition request message for the group may include one or more of a user ID used by the other terminal and an ID of the other terminal. The group creation request message may further include information about terminals belonging to the group. Information about the terminals belonging to the group may include at least one of a user ID used by the terminals and IDs of the terminals.

After transmitting the group creation request message, the method may further include transmitting a member addition request message to the network entity to add a member to the group. The member addition request message may include at least one of a user ID used by a terminal belonging to the group and an ID of the terminal.

The network entity may include one or more of an S-CSCF, an SCC AS, and a group management server.

On the other hand, in order to achieve the above object, the present specification provides a server for moving the terminal to the part or all of the media or the service control authority in the ongoing state of the remote end and the session consisting of one or more media, voice, video, text media Provides a way to control.

The control method includes the server receiving a group creation request message for creating a group from the first terminal. Here, the group creation request message includes at least an identifier of the group to be created. In addition, the group creation request message includes at least information on a group administrator managing the group. The method may further include receiving, from the first terminal, a notification request message for one or more of state and capability information of another terminal belonging to the group. The method may further include a notification message including information on the state and capability of the other terminal when the other terminal registers or registers with the IMS or when the state or capability information of the other terminal changes. The method may further include transmitting to. The method may further comprise receiving, from the first terminal, a movement request message for all or part of a media flow constituting the session or a service control right. The movement request message includes an identifier of at least one target terminal among terminals belonging to the group. The method may further include transmitting a session start request message to the target terminal and transmitting an update request message of the session to the remote terminal based on the movement request message.

The present invention manages the terminals that interoperate with each other in a group for inter-UE transfer operation, and by subscribing to an information notification service with an identifier of the group, the states of the terminals belonging to the group. Make it easy to obtain ability information.

The present invention reduces signaling overhead between the terminal and the IMS network when acquiring state / capability information of another terminal from the IMS network in order to perform the inter-terminal movement operation.

In addition, the present invention allows to add the members of the group for each terminal, so that it is possible to easily select only the terminal that you want to participate in the inter-terminal movement operation.

The present invention is more effective as the number of users linked to each other for movement between terminals. Also, the more IDs a user owns, the better.

2 shows a process of moving between terminals according to the prior art.

3 and 4 are flowcharts illustrating a method of generating an IUT group and obtaining state / capability information of a terminal according to the first embodiment of the present invention.

5 is a flowchart illustrating a modified example of a method for generating an IUT group and obtaining state / capability information of a terminal according to the first embodiment of the present invention.

6 and 7 are flowcharts illustrating another modified method of generating an IUT group and obtaining state / capability information of a terminal according to the first embodiment of the present invention.

8 and 9 are flowcharts illustrating a method for moving between terminals according to a second embodiment of the present invention.

10 and 11 are flowcharts illustrating a modification of the method for moving between terminals according to the second embodiment of the present invention.

12 and 13 are flowcharts illustrating another modified example of a method for moving between terminals according to the second embodiment of the present invention.

14 is a block diagram of the UE 100 and the SCC AS 520 according to the present invention.

It is to be noted that the technical terms used herein are merely used to describe particular embodiments, and are not intended to limit the present invention. In addition, the technical terms used in the present specification should be interpreted as meanings generally understood by those skilled in the art unless they are specifically defined in this specification, and are overly inclusive. It should not be interpreted in the sense of or in the sense of being excessively reduced. In addition, when the technical terms used herein are incorrect technical terms that do not accurately represent the spirit of the present invention, it should be replaced with technical terms that can be understood correctly by those skilled in the art. In addition, the general terms used in the present invention should be interpreted as defined in the dictionary or according to the context before and after, and should not be interpreted in an excessively reduced sense.

Also, the singular forms used herein include the plural forms unless the context clearly indicates otherwise. In the present application, terms such as “consisting of” or “having” should not be construed as necessarily including all of the various components, or various steps described in the specification, and some of the components or some of the steps are included. It should be construed that it may not be, or may further include additional components or steps.

In addition, terms including ordinal numbers, such as first and second, as used herein may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.

When a component is said to be "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but other components may be present in between. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings, and the same or similar components will be given the same reference numerals regardless of the reference numerals, and redundant description thereof will be omitted. In addition, in describing the present invention, when it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, it should be noted that the accompanying drawings are only for easily understanding the spirit of the present invention and should not be construed as limiting the spirit of the present invention by the accompanying drawings. The spirit of the present invention should be construed to extend to all changes, equivalents, and substitutes in addition to the accompanying drawings.

In the accompanying drawings, although a user equipment (UE) is illustrated as an example, the illustrated UE may be referred to in terms of terminal, mobile equipment (ME), and the like. In addition, the UE may be a portable device such as a laptop, a mobile phone, a PDA, a smart phone, a multimedia device, or a non-portable device such as a PC or a vehicle-mounted device.

Definition of Terms

Before describing with reference to the drawings, in order to help the understanding of the present invention, terms used herein will be briefly defined.

1) IP Multimedia Subsystem (IMS) is a network technology that enables Packet Switching (PS) based on Internet Protocol (IP) not only to a wired terminal but also to a wireless terminal. It is proposed to connect both wired and wireless terminals through IP (All-IP).

This IMS-based network includes an HSS (Home Subscriber Server) that includes a database that stores user subscriber information, and other entities. In addition, the IMS-based network includes a CSCF (call session control function) for processing procedures for control signaling, registration, and session. The CSCF may include P-CSCF (Proxy-CSCF), S-CSCF (Serving-CSCF), and I-CSCF (Interrogating-CSCF). The P-CSCF operates as a first access point for user equipment (UE) in an IMS based network. The S-CSCF then handles the session within the IMS network. That is, the S-SCSF is an entity responsible for routing signaling and routes a session in an IMS network. The I-CSCF then acts as an access point with other entities in the IMS network.

2) Under the IMS, the IP-based session is controlled by the Session Initiation Protocol (SIP). The SIP is a protocol for controlling a session. The SIP is a protocol for identifying terminals to communicate with each other to find a location, creating a multimedia session with each other, or deleting a created session. Refers to the specified signaling protocol. Such SIP uses a SIP Uniform Resource Identifier (URI), which is similar to an email address, to distinguish each user, thereby providing a service without being dependent on an Internet Protocol (IP) address.

3) IP Multimedia Public Identity (IMPU): A user using an IMS-based UE has one or more public user IDs, or IMPUs, in order to communicate with other users. Also, multiple UEs may share one IMPU. In addition, one user (strictly a subscriber) may use multiple IMPUs. The IMPU follows a SIP Uniform Resource Identifier (URI) or Tel URI format.

4) Public Service Identity (PSI): A PSI refers to a service or a specific resource created for a service on an application server (AS). The PSI follows a SIP Uniform Resource Identifier (URI) or Tel URI format.

5) Instance-ID (Instance-ID): This is an identifier for identifying a specific terminal among the terminals using the same IMPU.

6) Registration: refers to a process in which the UE notifies the home network of information related to its current location. That is, it refers to a process of accessing the home network by transmitting its current location and other information.

7) Application Server (AS): A server that provides various multimedia services

8) Multi-Media Session Continuity: Supporting UE mobility or mobility between UEs while maintaining continuity for an ongoing session.

9) Service Centralization and Continuity Application Server (SCC AS): Application server that supports multimedia session persistence

10) Collaborative Session: A logical set of IMS sessions spanning two or more terminals, which are combined into one IMS session by anchoring on the SCC AS.

11) Controller UE: A UE that controls the Collaborative Session. Such a controller UE may provide a media flow for the collaborative session.

12) Controllee UE: A UE that provides media flow for the Collaborative Session.

13) Remote End: Partner UE or partner application server to communicate with UE

14) Inter-UE Transfer (IUT): Means to move some or all of the media flows in a session or service control authority between terminals.

15) UE status / capability information: i) UE registration information, ii) capability-related information such as media type, codec, etc. supported by the UE, iii) configuration-related information such as screen size, iv) the access network related information to which the UE is currently connected.

In the above, the terms used in the present specification have been defined.

Hereinafter, to facilitate understanding of the proposed method in the present specification, the concept will be described in brief.

Description of the concept of the proposed solution here

In the present invention, for inter-UE transfer operation, terminals interworking with each other are managed as an IUT group. In addition, by allowing the user to subscribe to the information notification service using the identifier of the group, it is possible to easily obtain the status / capability information of the terminals belonging to the group.

The identifier of the IUT group follows the format of a Public Service Identifier.

Definitions and features of the IUT group are as follows.

IUT group: A group consisting of information on terminals interworking with each other for inter-UE transfer operation, and members are managed on a per-unit basis. In this case, a specific terminal may serve as a group administrator of the group. In addition, a particular IMPU may serve as an administrator of the group. In this case, when there are a plurality of terminals using the specific IMPU, the priority of the group manager role between the terminals may be designated. For example, if the UE-A, UE-B, UE-C using the IMPU1 exists and the IMPU1 wants to perform the group manager role, the UE-C, UE-A, UE-B are in the group manager role. Can be prioritized.

One terminal may be a member of a plurality of IUT groups.

Only some terminals of a plurality of terminals belonging to the same user may be made members of a specific IUT group. For example, among UEs of user A, UE-A1 may be made a member of IUT Group1, UE-A2 and UE-A3 may be made a member of IUT_Group2, and UE-A4 may not belong to any IUT group.

Only some terminals of a plurality of terminals using the same IMPU may be made members of a specific IUT group. For example, among UEs using IMPU1, UE-A and UE-B may be made members of IUT Group1, UE-C may be made members of IUT_Group2, and UE-D may not belong to any IUT group.

In the case of a terminal using a plurality of IMPUs, only some of the IMPUs used can be made members of a specific IUT group. For example, if UE-A uses three IMPUs such as IMPU1, IMPU2, and IMPU3, it can be made a member of IUT_Group1 for UE-A using IMPU1 and a member of IUT_Group2 for UE-A using IMPU2. UE-A using IMPU3 may not belong to any IUT group.

Meanwhile, the following three methods can be used as an identifier of a member to be added when adding a member constituting an IUT group.

As a first method, use IMPU to add members. That is, all terminals using the corresponding IMPU can be added as members of the IUT group.

As a second method, use the Instance-ID to add members. For example, only the specific terminal may be added to the IUT group using the Instance-ID of the specific terminal. In this way, when adding a member in a terminal unit, information on which IMPU to use when the terminal participates in an IUT operation must be provided together. Thus, even when one terminal uses a plurality of IMPUs, it is possible to identify which IMPU the terminal is to join as a member of the IUT group. For example, suppose UE-1 uses IMPU1 and IMPU2. In this case, in order to participate in the IUT operation as a member of the group called IUT_Group1 only when using IMPU1, the Instance-ID for UE-1 and the information about IMPU1 need to be provided.

As a third method, a group identifier can be used to add members. That is, when all the member terminals in the first IUT group want to add to the second IUT group, the identifier of the first IUT group may be used.

In addition to the above identifiers, various identifiers such as a globally routable user agent URI (GRUU) may be used as a member identifier of the IUT group.

Hereinafter, the present invention will be described with reference to the drawings. However, hereinafter, the method proposed in the present invention will be mainly described, and other details will not be described in detail. However, not described below, but is not to be excluded from this specification, it should be construed as being included herein.

Hereinafter, with reference to the accompanying drawings an embodiment according to the present invention will be described in detail.

3 and 4, user A uses ID A_IMPU1 and owns a plurality of terminals, eg, UE-A1 110 and UE-A2 120. User B uses B_IMPU1 as an ID and owns a plurality of terminals, for example, UE-B1 and UE-B2.

3 and 4 illustrate a home network to which the A user and the B user subscribe. The home network includes an IMS node 510 and an SCC AS 520. The IMS node 510 may be an S-CSSF or an application server (AS). Meanwhile, although the home network is illustrated as being divided into the IMS node 510 and the SCC AS 520, the IMS node 510 and the SCC AS 520 are physically implemented as one server. It may only be logically separated. In addition, the function of the SCC AS 520 may be mounted in the IMS node 510 and exist as one server. May be present.

The UE-A1, the UE-A2, the UE-B1, and the UE-B2 may include two or more communication modules. The communication module is a module such as CDMA, TDMA, FDMA, GSM, GPRS, WCDMA, IEEE 802.16, Bluetooth, infrared communication, IEEE 802.11, UWB, Zigbee, Wireless USB, and the like. One of the above communication modules may be one module, and the second communication module may be the same or different module as the first communication module.

As can be seen with reference to FIGS. 3 and 4, a process in which UEs belonging to user A and user B joins a group for a terminal-to-terminal movement operation is shown. The situation in which a UE is added to the group is shown. In this process, user A uses A_IMPU1 as an ID for two UEs owned by UE-A1 and UE-A2, and user B uses two UEs owned by UE-B1 and UE-B2. Use B_IMPU1 as the ID for. In addition, the user C uses C_IMPU1 as an ID for two UEs owned by UE-C1 and UE-C2.

1-2) The UE-A1 110 transmits a registration request message, for example, a REGISTER message, to the IMS node 510 and receives an acknowledgment message in order to register in its home network. In this case, registration means that the UE informs its home network of its location.

3-4) The IMS node 510 performs 3rd-party registration with the SCC AS 520 based on the A user's subscription information.

5) The UE-A1 110 transmits a group creation request message for generating an IUT group called IUT_Group1 as a group identifier to the SCC AS 520 for an inter-terminal mobility (IUT) operation. The group creation request message includes an identifier parameter of the group requested to be created, such as a Group ID parameter, an administrator information parameter of the group, such as a Group Administrator parameter. In this case, the Group ID parameter includes IUT_Group1, which is an identifier of the requested group, and the Group Administrator parameter includes an identifier of the UE-A1, for example, UE-A1. In this case, the Group Administrator parameter may be set to IMPU, such as A_IMPU1. The UE-A1 110 may already know the address of the SCC AS 520 or obtain it through the registration process.

6) The SCC AS 520 sends a response message to the UE-A1 110 in response to the group creation request message from the UE-A1 110. The SCC AS 520 recognizes the UE-A1 110 as an administrator of the group and manages information on the created group.

7) The UE-A1 110, which is a group manager of a group having an identifier of IUT_Group1, transmits a group member add request message to the SCC AS 520 in order to add a new member to the created IUT group. The group member add request message includes an identifier of a member added to the group. For example, as illustrated, A_IMPU1, which is an identifier of user A, and B_IMPU1, which is an identifier of user B, are included. Accordingly, all terminals using the identifier A_IMPU1, for example, UE-A1 and UE-A2 and all terminals using the identifier B_IMPU1, for example, UE-B1 and UE-B2, are members of the IUT_Group1.

8) The SCC AS 520 transmits a response to the group member addition request message to the UE-A1 110.

The SCC AS 520 may include the following group management table.

In the group management table, for example, Member1 means all terminals using a user ID of A_IMPU1. The group management table is merely an example and can be transformed into any table capable of managing a group.

9) The UE-A1 110 transmits an information notification subscription request message, for example, a SUBSCRIBE message, to the SCC AS 520 in order to obtain status / capability information about terminals belonging to the IUT_Group1.

10) The SCC AS 520 sends an acceptance message to the UE-A1 110 with respect to the information notification subscription request message.

11 to 12) Meanwhile, the UE-B1 210 transmits a registration request message, for example, a REGISTER message, to an IMS node 510 of its home network and receives an acknowledgment message.

13 to 14) The IMS node 510 performs 3rd-party registration with the SCC AS 520 based on the subscription information of the B user.

15-16) As the UE-B1 210 using the B_IMPU1 registers, the SCC AS 520 transmits state / capability information of the UE-B1 210 to the UE-A1 110. . The state / capability information of the UE-B1 210 is included in a notification message, eg, a NOTIFY message.

17) The UE-B1 210 transmits an information notification subscription request message, for example, a SUBSCRIBE message, to the SCC AS 520 in order to obtain status / capability information about terminals belonging to the IUT_Group1.

18) The SCC AS 520 sends an acceptance message for the information notification subscription request message to the UE-B1 210.

19 to 20) The SCC AS 520 transmits a notification message, for example, a NOTIFY message, which includes state / capability information of the registered UE-A1, to the UE-B1 210.

21-22) Meanwhile, the UE-B2 220 transmits a registration request message, for example, a REGISTER message, to the IMS node 510 of its home network and receives an acknowledgment message.

23-24) The IMS node 510 performs 3rd-party registration with the SCC AS 520 based on the subscription information of the B user.

25 to 26) As the UE-B2 220 using the B_IMPU1 registers, the SCC AS 520 includes state / capability information of the UE-B2 220 to the UE-A1 110. Send a notification message, eg a NOTIFY message.

27 to 28) As the UE-B2 220 using the B_IMPU1 registers, the SCC AS 520 includes state / capability information of the UE-B2 220 to the UE-B1 210. Send a notification message, eg a NOTIFY message.

29) The UE-B2 220 transmits an information notification subscription request message, for example, a SUBSCRIBE message, to the SCC AS 520 in order to obtain status / capability information about terminals belonging to the IUT_Group1.

30) The SCC AS 520 transmits an acceptance message to the UE-B2 220 for the information notification subscription request message.

31 to 32) the SCC AS 520 transmits a notification message including a state / capability information of the UE-A1 110 to the UE-B2 220, for example, a NOTIFY message.

33 to 34) The SCC AS 520 transmits a notification message and a NOTIFY message including state / capability information of the registered UE-B1 210 to the UE-B2 220.

Meanwhile, the UE-C1 310 of the C user transmits a registration request message, for example, a REGISTER message, to the IMS node 510 of its home network, and receives an acknowledgment message.

37-38) The IMS node 510 performs 3rd-party registration with the SCC AS 520 based on the subscription information of the C user.

39a) The UE-C1 310 transmits a member add request message or a join request message for the group to the SCC AS 520 in order to join the IUT group having the IUT_Group1 identifier. In this case, the UE-C1 310 includes UE-C1, which is its identifier, and an identifier of the C user, for example, C_IMPU1, in the member addition request message.

39b) The SCC AS 520 sends the member add request message or the join request message for the group received from the UE-C1 310 to the UE-A1 110, which is a Group Administrator of IUT_Group1.

40a) The UE-A1 110 transmits an acceptance message for the member addition request received from the SCC AS to the SCC AS 520. For this reason, the UE-C1 310 using the identifier C_IMPU1 becomes a member of IUT_Group1. The SCC AS 520 updates the aforementioned group management table as follows.

40b) The SCC AS 520 transmits an acceptance message for the member addition request message to the UE-C1 310.

41-42) As the UE-C1 310 is added to the group, the SCC AS 520 notifies the UE-A1 110 including the status / capability information of the UE-C1 310. Send a message, for example a NOTIFY message.

43 to 44) As the UE-C1 310 is added to the group, the SCC AS 520 notifies the UE-B1 210 of the notification message including the state / capability information of the UE-C1, for example. Send a NOTIFY message.

45 to 46) As the UE-C1 310 is added to the group, the SCC AS 520 notifies the UE-B2 220 of the notification message including the state / capability information of the UE-C1, for example. Send a NOTIFY message.

47) The UE-C1 310 transmits an information notification subscription request message, for example, a SUBSCRIBE message, to the SCC AS 520 in order to obtain status / capability information about terminals belonging to the group.

48) The SCC AS 520 sends an acceptance message for the information notification subscription request message to the UE-C1 310.

49 to 50) the SCC AS 520 transmits a notification message, for example, a NOTIFY message, containing the state / capability information of the registered UE-A1 110 to the UE-C1 310.

51 to 52) the SCC AS 520 transmits a notification message including a state / capability information of the registered UE-B1 210 to the UE-C1 310, for example, a NOTIFY message.

53 to 54) The SCC AS 520 transmits a notification message including a state / capability information of the registered UE-B2 220 to the UE-C1 310, for example, a NOTIFY message.

Until now, the SCC AS 520 processes the information notification subscription request for the status / capability information and provides the status / capability information. However, a network entity such as the IMS node or the S-CSCF may provide the request. have.

Meanwhile, although a method for obtaining an identifier for an IUT group to which the user or the terminal intends to participate is not specified, a method for obtaining an identifier for the group includes a IMPU belonging to an IUT group to be known. Can be obtained by sending to the SCC AS managing group information. For example, if the UE-B1 transmits a query for obtaining an identifier for the IUT group to which the UE using A_IMPU1 belongs to the SCC AS 520 prior to step 17, the SCC AS 520 transmits the IUT_Group1 to the UE-B1. You can tell B1.

In the process, operations such as group creation and member addition, such as steps 5 to 8 and steps 39a to 40b, may use an interface between a terminal and the SCC AS 520, in which case the interface may be a DM (ie OMA DM). ), Ut interface and the like can be implemented. When using such an interface, the message can be delivered through protocols such as XCAP and HTTP.

According to a modification illustrated in FIG. 5, as in step 5, the group creation request message may include a list of members to be added to the group.

That is, the group creation request and the group member addition request may not be made in a separate process as in the process of 5 to 8 of the first embodiment of FIGS. 3 and 4, but may be made in one process as in 5 to 6 of FIG. 5. have.

Details of each illustrated process can be easily understood by those skilled in the art from the contents of FIGS. 3 and 4, and thus, the contents of FIGS. 3 and 4 will be applied mutatis mutandis.

6 and 7, the group management server 600 is in charge of managing information about the group. That is, although the SCC AS 520 is described in FIG. 3, FIG. 4, and FIG. 5 as the information management of the group, the group management server 600 is in charge of this modification. The group management server 600 manages member information in the group. In addition, the group management server 600 is responsible for the update notification service for the managed group.

Specifically, each process is described as follows.

5) The UE-A1 110 transmits a group creation request message for generating an IUT group having IUT_Group1 as a group identifier to the group management server 600 for an inter-terminal mobility (IUT) operation. The group creation request message includes an identifier parameter of the group requested to be created, such as a Group ID parameter, an administrator information parameter of the group, such as a Group Administrator parameter. In this case, the Group ID parameter includes IUT_Group1, which is an identifier of the requested group, and the Group Administrator parameter includes an identifier of the UE-A1, for example, UE-A1. In this case, the Group Administrator parameter may be set to IMPU, such as A_IMPU1.

6) The group management server 600 transmits a response message to the UE-A1 110 in response to the group creation request message from the UE-A1 110. The group management server 600 recognizes the UE-A1 110 as an administrator of the group and manages information on the created group.

7) The UE-A1 110, which is a group manager of a group having an identifier of IUT_Group1, transmits a group member add request message to the group management server 600 in order to add a new member to the created IUT group. The group member add request message includes an identifier of a member added to the group. For example, as illustrated, A_IMPU1, which is an identifier of user A, and B_IMPU1, which is an identifier of user B, are included. Accordingly, all terminals using the identifier A_IMPU1, for example, UE-A1 and UE-A2, and all terminals using the identifier B_IMPU1, for example, UE-B1 and UE-B2, become members of the IUT_Group1.

8) The group management server 600 transmits a response to the group member addition request message to the UE-A1 110.

The group management server 600 may include the group management table described above with reference to FIG. 3.

10) In order for the SCC AS 520 to provide the information notification service for the IUT_Group1 requested by the UE-1 110, information about the IUT_Group1 is required. Accordingly, the group management server 600 requests information about IUT_Group1.

11) The group management server 600 transmits information on IUT_Group1 to the SCC AS 520. The SCC AS 520 stores information on the acquired IUT_Group1.

12) Then, the SCC AS 520 sends an acceptance message to the UE-A1 110 with respect to the information notification subscription request message received from the UE-1 110.

13 to 14) Meanwhile, the SCC AS 520 transmits an update notification request message to the group management server 600 so as to request that the SCC AS 520 be informed whenever the information on the group is changed, and the group management server ( 600 transmits an accept message to the SCC AS 520. That is, the SCC AS 520 receives the information on the group in step 11, but if the information is updated in the group management server 600, in order to be notified of the updated information, the update notification request message Send it.

Meanwhile, the UE-B1 210 transmits a registration request message, for example, a REGISTER message, to an IMS node 510 of its home network and receives an acknowledgment message.

17 to 42) These processes are the same as the processes of 13 to 38 shown in FIGS. 3 and 4. Therefore, the contents of FIGS. 3 and 4 shall apply mutatis mutandis.

43a) The UE-C1 310 transmits a member add request message or a join request message for the group to the group management server 600 in order to join the IUT group having the IUT_Group1 identifier. In this case, the UE-C1 310 includes UE-C1, which is its identifier, and an identifier of the C user, for example, C_IMPU1, in the member addition request message.

43b) The group management server 600 sends the member add request message or the join request message for the group received from the UE-C1 310 to the UE-A1 110, which is a Group Administrator of IUT_Group1.

44a) The UE-A1 110 transmits an acceptance message for the member addition request received from the group management server to the group management server 600. For this reason, the UE-C1 310 using the identifier C_IMPU1 becomes a member of IUT_Group1. The group management server 600 updates the aforementioned group management table.

44b) The group management server 600 transmits an acceptance message for the member addition request message to the UE-C1 310.

45 to 46) As the UE-C1 310 is added to the group, the group management server 600 transmits a message notifying the update of the group to the SCC AS 520.

47 to 48) As the SCC AS 520 recognizes that the UE-C1 310 is added to the group, the SCC AS 520 sends the UE-C1 310 to the UE-A1 110. Sends a notification message, for example, NOTIFY message containing the status / capability information of the other. Further details of each process shown can be easily understood by those skilled in the art from the contents of Figs. 3 and 4 shall apply mutatis mutandis.

Meanwhile, the interface between the UEs, for example, the UE-A1, the UE-A2, and the group management server 600 may be implemented through a DM (i.e. OMA DM) or a Ut interface. Using these interfaces, messages can be exchanged through protocols such as XCAP and HTTP.

In addition, a protocol for exchanging messages between the SCC AS 520 and the group management server 600 may be SIP, Diameter, HTTP, and the like.

6 and 7 may be combined with the modified example of FIG. 5. That is, the group creation request and the group member addition request for the group management server 600 may be performed in one process.

8 and 9, user A uses ID A_IMPU1 and owns a plurality of terminals, eg, UE-A1 110, UE-A2 120, and UE-A3 130. User B uses B_IMPU1 as an ID and owns a plurality of terminals, for example, UE-B1 210 and UE-B2 220.

8 and 9, in a state where user A conducts a session consisting of voice and video media between the remote end 300 through the UE-A1 110, the user A belongs to the user B. In other words, the process of moving the video media flow while maintaining the persistence of the session to the UE-B1 210 is shown. To this end, the user B adds only a specific terminal, ie, the UE-B1 210, that he or she wants to participate in, among the UE-B1 210 and the UE-B2 220 owned by the user, as a group member. .

1 to 10) These processes are the same as the processes of 1 to 10 shown in Figs. Therefore, the contents of FIGS. 3 and 4 shall apply mutatis mutandis. 8 and 9, unlike FIG. 3 and FIG. 4, only the A_IMPU1 is included as an identifier of a member to be added to the group member add request message.

11a-11d) The user A wishes to conduct a session consisting of voice and video media with the remote end 300 via the UE-A1 110. Accordingly, the UE-A1 110 sends a session initiation request message (eg, a SIP-based INVITE message) to the IMS node 510, and the IMS node 510 sends the session initiation request message to the A user. The SCC AS 520 is transmitted to the remote terminal 300 based on the subscriber information of the SCC AS 520. The session initiation request message includes information on media in the session, that is, information on voice and video. Information about the media is included in the SDP body.

An example of a format included in the SDP body is described below with reference to RFC 4566 document.

m = <media> <port> / <number of ports> <proto> <fmt> ...

For example, m = video 49170/2 RTP / AVP 31 can be used.

As another example, the format of the SDP may be as follows.

12a to 12d) The remote end 300 transmits a session start accept message 200 OK to the UE-A1 110 with respect to the session start request message. This establishes a session consisting of voice and video media between the UE-A1 110 and the remote end 300.

13 to 14) Meanwhile, the UE-B1 210 transmits a registration request message, for example, a REGISTER message, to an IMS node 510 of its home network and receives an acknowledgment message.

15 to 16) The IMS node 510 performs 3rd-party registration with the SCC AS 520 based on the subscription information of the B user.

17a) the UE-B1 210 sends a member add request message to the SCC AS 520 in order to join the IUT group having the IUT_Group1 identifier. In this case, the UE-B1 210 includes its identifier, for example, UE-B1 and B_IMPU1, which is its user ID, in the member addition request message.

17b) the SCC AS 520 sends a member addition request message received from the UE-B1 210 to the UE-A1 110, which is a Group Administrator of IUT_Group1.

18a) The UE-A1 110 transmits an acceptance message for the member addition request received from the SCC AS 520 to the SCC AS 520. For this reason, the UE-B1 210 becomes a member of IUT_Group1.

18b) the SCC AS 520 transmits an acceptance message for the member addition request message to the UE-B1 210.

19 to 20) As the UE-B1 210 registers, the SCC AS 520 transmits state / capability information of the UE-B1 210 to the UE-A1 110. The state / capability information of the UE-B1 210 is included in a notification message, eg, a NOTIFY message.

23-24) The IMS node 510 performs 3rd-party registration with the SCC AS 520 based on the subscription information of the B user. For reference, unlike the UE-B1, the UE-B2 does not participate in the inter-terminal movement operation, and thus does not send the member addition request message as in step 17a.

25) Meanwhile, if the user A decides to move the ongoing video media flow through the UE-A1 110, the UE-A1 110 targets the UE-B1 210 of the user B as a target UE. To select.

26a to 26b) the UE-A1 110 moves to the SCC AS 520 through the IMS node 510 to transfer the video media flow to the UE-B1 210, for example, a media transfer. Send the request message. In addition, the movement request message includes a parameter for a target terminal, for example, a target UE parameter. The move request message includes a parameter for the media to be moved, for example, a media parameter. In some cases, the movement request message may further include various parameters required for media flow movement, such as parameters for a source terminal, for example, a source UE parameter.

27a to 27b) the SCC AS 520 delivers the movement request message to the UE-B1 210 through the IMS node 510.

28a to 28b) The UE-B1 210 transmits a request accept message to the SCC AS 520 through the IMS node 510 with respect to the movement request message. In this case, since the UE-B1 210 has subscribed to the group for IUT, the UE-B1 210 accepts the movement request message.

29a to 29b) the SCC AS 520 sends a session update request message (eg, Re-INVITE) to the remote end 300 through the IMS node 510 including a change according to the movement of the video media flow. send.

30a to 30b) The remote end 300 transmits a session update accept message to the session update request from the SCC AS 520. This establishes a session consisting of video media between the UE-B1 and the remote end 300.

31a to 31b) the SCC AS 520 transmits a session transfer completion message, for example, a media transfer completion message, to the UE-A1 110.

Then, the UE-A1 110 proceeds with the session consisting of only the voice media with the remote end 300. However, even after the UE-A1 110 moves the video media flow to the UE-B1 210, the UE-A1 110 has control over a collaborative session composed of the voice media and the video media. That is, the UE-A1 110 becomes a controller terminal and a controller UE, and the UE-B1 210 becomes a controlled terminal, that is, a Controllee UE.

As described above with respect to steps 5 to 8 and steps 17a to 18b, operations such as group creation and group member addition may use an interface between a UE and the SCC AS, in which case the interface may be a DM (ie OMA DM), Ut. It can be implemented through an interface. When using such an interface, the message can be delivered through protocols such as XCAP and HTTP.

10 and 11, as in step 5, the group creation request message may include a list of members to be added to the group.

That is, as in steps 5 to 8 of the second embodiment of FIG. 8 and FIG. 9, the group creation request and the group member addition request may be performed in one process instead of a separate process.

Details of each illustrated process can be easily understood by those skilled in the art from the contents of FIGS. 8 and 9, and will not be described in detail, and the contents of FIGS. 8 and 9 will be applied mutatis mutandis.

12 and 13, the group management server 600 is responsible for information management of the group. That is, although the SCC AS 520 has been described in FIG. 8, 9, 10, and 11 as the information management of the group, the group management server 600 is in charge of this modification. The group management server 600 manages member information in the group. In addition, the group management server 600 is responsible for the update notification service for the managed group.

To this end, the group management server 600 may include the aforementioned group management table.

Details of each illustrated process can be easily understood by those skilled in the art from the contents of FIGS. 3 and 4 to 10 and 11, and will not be described in detail.

12 and 13 may be combined with the modifications of FIGS. 10 and 11. That is, the group creation request and the member addition request for the group management server 600 may be made in one process.

The method according to the invention described thus far can be implemented in software, hardware, or a combination thereof. For example, the method according to the present invention may be stored in a storage medium (eg, internal memory, flash memory, hard disk, etc.) and may be executed by a processor (eg a microprocessor). It can be implemented as codes or instructions within a program. This will be described with reference to FIG. 14.

As shown in FIG. 14, the UE 100 includes a storage means 101, a controller 102, and a transceiver 103. The SCC AS 520 includes a storage means 521, a controller 522, and a transceiver 523.

The storage means 101, 521 store the method according to the first to second embodiments shown in FIGS. 3 and 4 to 12 and 13.

The

controllers

102 and 522 control the storage means 101 and 521 and the transceivers 522 and 523. Specifically, the

controllers

102 and 522 respectively execute the methods stored in the storage means 101 and 521. The

controllers

102 and 522 transmit the aforementioned signals through the transceivers 103 and 523.

In the above described exemplary embodiments of the present invention by way of example, but the scope of the present invention is not limited to these specific embodiments, the present invention is in various forms within the scope of the spirit and claims of the present invention Can be modified, changed, or improved.

Claims

An inter-terminal movement method of moving a part or all of the media to another terminal while a session consisting of one or more media including voice, video, and text media is in progress with a remote end.

Sending a group creation request message to the network entity, the group creation request message including at least an identifier of a group to be created for group creation;

Transmitting a notification request message for at least one of state and capability information of each terminal belonging to the group to the network entity; The notification request message includes an identifier of the group,

Receiving a notification message including information on the state and capability of each terminal when each terminal is registered or registered in the IMS or when the state or capability information of each terminal is changed;

Selecting a part or all of the media, or a terminal to which a service control authority is to be moved among terminals in the group based on the information on the state and capability.
The method of claim 1,

Receiving a member addition request message for the group from another terminal through the network entity;

Determining whether to accept the member addition request sent by the other terminal for the group;

And if it is determined to allow the acceptance, sending an acceptance message to the network entity.
The method of claim 2, wherein after sending the accept message:

And receiving a notification message from the network entity, the notification message including information on the state and capability of the terminal added to the group.
The method of claim 2, wherein the member add request message for the group

And at least one of a user ID used by terminals to be added to the group and IDs of the terminals.
The method of claim 1, wherein the group creation request message is

The method of moving between terminals further comprising information on terminals to be added to the group.
The method of claim 5,

The information about the terminals to be added to the group comprises at least one of a user ID used by the terminals and the ID of the terminals.
The method of claim 1, after transmitting the group creation request message,

And transmitting a member add request message to the network entity to add a member to the group.
The method of claim 7, wherein the member add request message is

And at least one of a user ID used by terminals to be added to the group and IDs of the terminals.
The method of claim 1, wherein the network entity

S-CSCF, SCC AS, group management server, characterized in that it comprises one or more of the server.
A method of controlling a terminal-to-terminal movement of a part or all of the media or a service control right in a remote stage with a session consisting of one or more media including voice, video, and text media,

Receiving, by the server, a group creation request message for creating a group from a first terminal, wherein the group creation request message includes at least an identifier of the group to be created;

Receiving a notification request message for at least one of state and capability information of another terminal belonging to the group from the first terminal;

When the other terminal is registered or registered in the IMS or when the state or capability information of the other terminal is changed, transmitting a notification message including information on the state and capability of the other terminal to the first terminal. Wow;

Receiving a move request message for all or part of a media flow or a service control right from the first terminal; The movement request message includes an identifier of at least one target terminal among terminals belonging to the group, and

Transmitting a session initiation request message to the target terminal based on the movement request message; And transmitting the update request message of the session to the remote end.
The method of claim 10,

Receiving a member add request message for the group from a second terminal;

Transmitting the member addition request message to the first terminal; And

And transmitting an acceptance message to the second terminal when receiving the member addition acceptance message for the group from the first terminal.
The method of claim 11, wherein after passing the accept message:

And transmitting a notification message to the first terminal, the notification message including information on the status and capabilities of the terminals added as members by the second terminal to the first terminal.
12. The method of claim 11, wherein the member add request message for the group is

And at least one of a user ID used by terminals to be added to the group and IDs of the terminals.
The method of claim 10, wherein the group creation request message is

The method of controlling the movement between terminals in the server, characterized in that it further comprises information about the terminals to be added to the group.
The method of claim 10, after receiving the group creation request message,

And receiving a member addition request message from the first terminal, the member adding request message including at least one of a user ID and IDs of the terminals used by the terminals to be added to the group. How to.