CN110336683B

CN110336683B - Session migration method and device

Info

Publication number: CN110336683B
Application number: CN201910652033.7A
Authority: CN
Inventors: 张伦泳
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2019-07-18
Filing date: 2019-07-18
Publication date: 2021-08-17
Anticipated expiration: 2039-07-18
Also published as: CN110336683A

Abstract

The invention discloses a method and a device for session migration. The method comprises the following steps: responding to a target group query request sent by a second data management entity, and obtaining a query result, wherein the target group comprises an identifier of a first type target terminal and an identifier of the target group, and the query request comprises: the method comprises the steps that identification of a target group, the network type of a calling terminal and the network type of a first type of target terminal are set, and the network type of the calling terminal is different from that of the first type of target terminal; if the query result is determined that the target group is stored in the first data management entity, the service information of the target group is transferred to the second data management entity; and sending a session change request to the mobile management entity so as to enable the session corresponding to the target group to be transferred to the second session management entity. Through service information migration and session migration, the calling terminal can join the target group, so that two terminals with different network types can share data, and the flow limitation of a third-party server is avoided.

Description

Session migration method and device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for session migration.

Background

At present, people widely use social software such as WeChat and QQ for communication and communication, and in the communication process, data files with different formats and sizes can be shared according to different user requirements.

However, when sharing a data file through these social software, it is usually necessary for a sharer to upload the data file to a third-party server (for example, a server of the social software), and then for a sharee to download the data file from the third-party server, so as to achieve the purpose of sharing, where a terminal used by the sharer and a terminal used by the sharee are not in the same communication network, for example: the sharer uses a terminal in the fifth generation communication network, and the sharee uses a terminal in the fourth generation communication network. If the storage space occupied by the data file to be shared by the sharer is too large, the data file is limited by the data flow of the third-party server when being uploaded to the third-party server, namely the size of the uploaded file exceeds the preset flow threshold of the third-party server, so that the data file cannot be uploaded to the third-party server, the sharer cannot share the data file, the sharee cannot receive the data file, and the customer experience degree is poor.

Disclosure of Invention

Therefore, the invention provides a session migration method and device, which aim to solve the problem that two types of users in different network types cannot share data files due to the fact that the two types of users are limited by the flow of a third-party server in the prior art.

In order to achieve the above object, a first aspect of the present invention provides a session migration method applied to a first data management entity, the method including: responding to a target group query request sent by a second data management entity, and obtaining a query result, wherein the target group comprises an identifier of a first type target terminal and an identifier of the target group, and the query request comprises: the method comprises the steps that identification of a target group, the network type of a calling terminal and the network type of a first type of target terminal are set, and the network type of the calling terminal is different from that of the first type of target terminal; if the query result is determined that the target group is stored in the first data management entity, the service information of the target group is transferred to the second data management entity; and sending a session change request to the mobile management entity so as to enable the session corresponding to the target group to be transferred to the second session management entity.

The step of migrating the service information of the target group to the second data management entity comprises the following steps: receiving a service migration request sent by a second data management entity; and sending a service migration response to the second data management entity, wherein the service migration response carries service information of the target group, the service information comprises a service ordering relation, and the service ordering relation comprises an internal group identifier and an identifier of the first type of target terminal.

After migrating the service information of the target group to the second data management entity, and before sending the session change request to the mobility management entity, the method further includes: and deleting the corresponding relation between the internal group identifier and the first type of target terminal, deleting the corresponding relation between the internal group identifier and the first session identifier corresponding to the target group, and establishing the corresponding relation between the internal group identifier, the identifier of the target group and the identifier of the second data management entity.

Wherein, the query result further includes: and if the query result indicates that the target group is not stored in the first data management entity and the target group is not stored in the second data management entity, determining that the calling terminal fails to join the target group.

In order to achieve the above object, a second aspect of the present invention provides a session migration method applied to a mobility management entity, the method including: receiving a session change request sent by a first data management entity; according to the session change request, migrating the session corresponding to the target group to a second session management entity; wherein the first data management entity is configured to: responding to a target group query request sent by a second data management entity, and obtaining a query result, wherein the target group comprises an identifier of a first type target terminal and an identifier of the target group, and the query request comprises: the method comprises the steps that identification of a target group, the network type of a calling terminal and the network type of a first type of target terminal are set, and the network type of the calling terminal is different from that of the first type of target terminal; if the query result is determined that the target group is stored in the first data management entity, the service information of the target group is transferred to the second data management entity; and sending a session change request to the mobile management entity.

Wherein, according to the session change request, the step of migrating the session corresponding to the target group to the second session management entity includes: closing a first session corresponding to the target group according to the session change request; sending a session establishment request to a second session management entity, wherein the session establishment request comprises the identifier of the first type of target terminal and the internal group identifier; and responding to a session establishment response forwarded by the second session management entity and sent by the user plane of the second packet data network, and establishing a second session of the target group, wherein the session establishment response comprises: an internal group identifier and an identification of the second session; updating the first session identifier of each target terminal in the target group into a second session identifier; and sending a session switching completion message to the second data management entity.

Wherein, the step of closing the first session corresponding to the target group comprises: forwarding a session change request to a first session management entity, wherein the session change request comprises an identifier of a first session and an internal group identifier, and the first session management entity is used for interacting with a user plane of a first packet data network and deleting the identifier of the first session; and determining to close the first session corresponding to the target group in response to a session change completion message returned by the first session management entity.

After the step of sending the session handover complete message to the second data management entity, the method further includes: updating the second session identifier of each target terminal in the target group into a third session identifier in response to the updated service information of the target group sent by the second session management entity; the updated service information of the target group comprises a service order relation, and the service order relation comprises an internal group identifier, a third session identifier, an identifier of the calling terminal and an identifier of the first type of target terminal.

In order to achieve the above object, a third aspect of the present invention provides an apparatus for session migration, including: an obtaining module, configured to obtain a query result in response to a target group query request sent by a second data management entity, where the target group includes an identifier of a first type of target terminal and an identifier of the target group, and the query request includes: the method comprises the steps that identification of a target group, the network type of a calling terminal and the network type of a first type of target terminal are set, and the network type of the calling terminal is different from that of the first type of target terminal; the service migration module is used for migrating the service information of the target group to the second data management entity after the target group is determined to be stored in the first data management entity; and the first session migration module is used for sending a session change request to the mobile management entity so as to enable the session corresponding to the target group to be migrated to the second session management entity.

In order to achieve the above object, a fourth aspect of the present invention provides an apparatus for session migration, including: the receiving module is used for receiving a session change request sent by a first data management entity; the session migration module is used for migrating the session corresponding to the target group to the second session management entity according to the session change request; the first data management entity comprises the following modules: an obtaining module, configured to obtain a query result in response to a target group query request sent by a second data management entity, where the target group includes an identifier of a first type of target terminal and an identifier of the target group, and the query request includes: the method comprises the steps that identification of a target group, the network type of a calling terminal and the network type of a first type of target terminal are set, and the network type of the calling terminal is different from that of the first type of target terminal; the second service migration module is used for migrating the service information of the target group to the second data management entity after determining that the query result is that the target group is stored in the first data management entity; and the sending module is used for sending the session change request to the mobile management entity.

The invention has the following advantages: by inquiring the identification of the target group, the target group is known to be stored in the first data management entity, the obtained service information of the target group is migrated to the second data management entity, and the session corresponding to the target group is migrated to the second session management entity, so that two terminals (namely, a first-class target terminal and a calling terminal) with different network types can be added into the same target group for group communication, the calling terminal can directly share data with the first-class target terminal without passing through the transfer of a third-party server, and the problem that a large data file cannot be shared due to the flow limitation of the third-party server is avoided.

The corresponding relation among the internal group identifier, the identification of the target group and the identification of the second data management entity is established, so that after the session migration is completed, when a first type of target terminal wants to join the target group, a joining request can be directly sent to the second data management entity, and the terminal can be rapidly joined into the target group.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention.

Fig. 1 is a flow chart of a session migration method according to a first embodiment of the present invention;

fig. 2 is a flow chart of a session migration method according to a second embodiment of the present invention;

fig. 3 is a flow chart of a session migration method according to a third embodiment of the present invention;

fig. 4 is a flowchart of a method for migrating a session corresponding to a target group to a second session management entity according to a third embodiment of the present invention;

fig. 5 is a block diagram of a session migration apparatus according to a fourth embodiment of the present invention;

fig. 6 is a block diagram of an apparatus for session migration according to a fifth embodiment of the present invention;

fig. 7 is a block diagram of a session migration system according to a sixth embodiment of the present invention.

In the drawings:

501: the obtaining module 502: service migration module

503: the first session migration module 601: receiving module

602: the second session migration module 603: transmission module

Detailed Description

The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present invention, are given by way of illustration and explanation only, not limitation.

A first embodiment of the invention relates to a method of session migration. The method and the device are used for enabling the two terminals with different network types to share data in a group communication mode, namely the data can be shared without passing through a third-party server, and the problem that large data files cannot be shared due to flow limitation of the third-party server is solved.

The following describes details of the implementation of the session migration method in this embodiment in detail, and the following is only for facilitating understanding of details of the implementation of this solution and is not necessary for implementing this solution.

Fig. 1 is a flowchart of a session migration method in this embodiment, which can be used for a first data management entity. The method may include the following steps.

In step 101, in response to the target group query request sent by the second data management entity, a query result is obtained.

The target group comprises an identifier of a first type of target terminal and an identifier of the target group, and the query request comprises: the network type of the calling terminal is different from the network type of the first type of target terminal.

In a specific implementation, after receiving a target group query request sent by a second data management entity, a first data management entity queries a stored group according to an identifier of the target group, and determines whether information of the target group exists. For example, in a fifth Generation Mobile Communication network (5G), if a 5G terminal establishes group Communication, information of a group is stored in a Unified Data Management (UDM) entity, and after receiving a target group query request, The UDM entity queries all groups in The UDM entity according to an Identifier (ID) of The target group to obtain a query result, where The query result includes two types: the information of the target group is stored in the UDM, or the information of the target group is not stored in the UDM.

It should be noted that, in The query request, The network type of The calling terminal is different from The network type of The first type of target terminal, for example, The network types of a fourth Generation Mobile Communication network (4G) terminal and a 5G terminal are 4G and 5G, respectively. If the calling terminal is a 4G terminal and the first-class target terminal is a 5G terminal, indicating that the 4G terminal wants to join a 5G group; if the calling terminal is a 5G terminal and the first type target terminal is a 4G terminal, it indicates that the 5G terminal wishes to join a 4G group.

In one specific implementation, the query result further includes: and if the target group is not stored in the first data management entity and the target group is not stored in the second data management entity, determining that the calling terminal fails to join the target group.

It should be noted that, before the first data management entity receives the target group query request sent by the second data management entity, the second data management entity already performs self-check and obtains a self-check result, and if it is determined that the target group is stored in the second data management entity according to the self-check result, the second data management entity sends a query success message to the home server, so that the calling terminal is successfully added to the target group; and if the information of the target group is not stored in the second data management entity, sending a target group query request to the first data management entity for querying. If the information of the target group is not inquired in the two data management entities, the target group does not exist, an inquiry failure response is returned to the second data management entity, and the second data management entity sends a 'target group joining failure message' to the home server corresponding to the calling terminal, so that the home server can forward the 'target group joining failure message' to the calling terminal and inform the calling terminal of the failure of joining the target group.

In a specific implementation, the first data management entity may be an UDM in a 5G network, the Home Server may be a Home Subscriber Server (HSS) in a 4G network, and the second data management entity may be a data management entity having both an UDM function and an HSS function, and the second data management entity has a function of cross-network communication, that is, communication between the 4G network and the 5G network may be implemented.

It should be noted that the UDM entity may further identify that the HSS + UDM entity is an entity with an inter-network communication function according to an identifier (e.g., a device number, a device address, etc.) of the HSS + UDM entity.

In step 102, if it is determined that the query result is that the target group is stored in the first data management entity, the service information of the target group is migrated to the second data management entity.

It should be noted that the service information of the target group includes the service context information and the service subscription relationship of the target group; and the service context information includes: forwarding rules (e.g., store-and-forward rules, direct forwarding rules, etc.) applicable to the Internal Group Identifier (IGI) of the target Group, priority levels (e.g., if there are multiple data to be forwarded, the priority level of the data of the target Group when being forwarded), priority scheduling policy, Quality of Service (QoS) parameter, charging preference policy, whether encrypted transmission is required, etc.; the QoS parameters may include time delay, jitter, packet loss number, etc.; the charging preferential strategy is a preferential rule defined by an operator; the priority scheduling strategy may employ the following scheduling algorithm: a First Input First Output (FIFO) Scheduling algorithm or a Round-Robin Scheduling (RRS) Scheduling algorithm, etc.

In a specific implementation, a service migration request sent by a second data management entity is received; and sending a service migration response to the second data management entity, wherein the service migration response carries service information of the target group, the service information comprises a service ordering relation, and the service ordering relation comprises an internal group identifier and an identifier of the first type of target terminal.

It should be noted that the service Subscription relationship may use a multi-tuple to represent the corresponding relationship between the internal group Identifier and the first type of target terminal, such as a multi-tuple (IGI, SUPI _5 ue1, SUPI _5 ue2, … …, SUPI _5 ue), where IGI represents the internal group Identifier of the target group for uniquely identifying the target group, SUPI represents the User Permanent Identifier (Subscription Permanent Identifier, SUPI), 5 ue represents the terminal (5G User, 5 ue) in the 5G network, SUPI _5 ue represents the terminal in the fifth generation communication network having the Subscription Permanent Identifier, SUPI _5 ue1 represents the first 5G terminal in the target group, SUPI _5 ue2 represents the 2 nd 5G terminal, … …, SUPI _5 ue represents the nth 5G terminal in the target group, where n is greater than or equal to 2.

Note that the SUPI may be replaced by any one of a Subscription hidden Identifier (Subscription hidden Identifier, SUCI), a Temporary Mobile Subscriber Identity (TMSI), a Subscriber telephone number, or an International Mobile Subscriber Identity (IMSI).

In step 103, a session change request is sent to the mobility management entity, so that the session corresponding to the target group is migrated to the second session management entity.

It should be noted that, after receiving the Session change request, the mobility Management entity performs signaling interaction with a Session Management Function (SMF) entity and a User Plane Function (UPF) entity according to the Session change request, and then migrates the Session corresponding to the target group to the second Session Management entity. In a specific implementation, the Mobility Management entity may be an Access and Mobility Management Function (AMF) entity in the 5G communication Network, and the second session Management entity may be an entity having both an SMF Function and a Packet Data Network Gateway Control plane (PGW _ C) Function.

In this embodiment, by querying the identifier of the target group, it is known that the target group is stored in the first data management entity, and then the obtained service information of the target group is migrated to the second data management entity, and the session corresponding to the target group is migrated to the second session management entity, so that two terminals (i.e., the first-class target terminal and the calling terminal) with different network types can be added to the same target group, and group communication is performed, so that the calling terminal can directly share data with the first-class target terminal without passing through the transfer of the third-party server, and the problem that a large data file cannot be shared due to the traffic limitation of the third-party server is avoided.

A second embodiment of the present invention is directed to a method of session migration. The second embodiment is substantially the same as the first embodiment, and mainly differs therefrom in that: after the first data management entity completes the migration of the service information, the corresponding relationship between the internal group identifier and the first type target terminal is also required to be deleted, and the corresponding relationship between the internal group identifier and the first session identifier corresponding to the target group is deleted; and meanwhile, establishing a corresponding relation among the internal group identifier, the identification of the target group and the identification of the second data management entity.

Fig. 2 is a flowchart of a session migration method in this embodiment, which can be applied to a first data management entity. The method may include the following steps.

In step 201, in response to the target group query request sent by the second data management entity, a query result is obtained.

In step 202, if it is determined that the query result is that the target group is stored in the first data management entity, the service information of the target group is migrated to the second data management entity.

It should be noted that steps 201 to 202 in this embodiment are the same as steps 101 to 102 in the first embodiment, and are not described herein again.

In step 203, the correspondence between the internal group identifier and the first type of target terminal is deleted, and the correspondence between the internal group identifier and the first session identifier corresponding to the target group is deleted.

In a specific implementation, the correspondence between the internal group identifier and the first type target terminal may be represented by tuple a (internal group identifier, first type target terminal 1, first type target terminal 2, … …, first type target terminal n); the correspondence of the internal group identifier to the first session identification corresponding to the target group may be represented using a binary set (internal group identifier, first session identification).

For example, if the first type of target terminal is a mobile terminal in a 5G network, the tuple a may be represented as (IGI, SUPI _5 ue1, SUPI _5 ue2, … …, SUPI _5 ue), and the tuple (internal group Identifier, first session Identifier) may be represented as (IGI, SID), where SID represents a Security Identifier (SID).

It should be noted that, since the service information of the target group has been migrated to the second data management entity, the first data management entity does not need to store the above corresponding relationship, and by deleting the above corresponding relationship, the first data management entity can save the storage space for storing other useful information.

In step 204, a correspondence between the internal group identifier, the identification of the target group and the identification of the second data management entity is established.

In a specific implementation, by establishing a tuple B (an internal group identifier, an identifier of a target group, an identifier of a second data management entity), the first data management entity can know a specific storage location of the migrated target group, that is, the migrated target group is stored in the second data management entity, so that when a subsequent first-class target terminal wishes to join the target group, the join request can be forwarded to the corresponding second data management entity.

For example, if the first type of target terminal is a mobile terminal in a 5G network, the multi-group B may be represented as (IGI, group ID, HSS + UDM _ ID), where the specific meaning of each abbreviation is: the group ID indicates an identifier of a target group, and the HSS + UDM _ ID indicates an identifier of a second Data Management entity having both an HSS function and an UDM function, where the HSS indicates a Home Subscriber Server (HSS), the UDM indicates Unified Data Management (UDM), and the ID indicates an identifier.

It should be noted that, the above method for representing the corresponding relationship between the variables by using the tuple may set different representation modes according to actual requirements, and is not limited to the above illustration, and other representation modes of the corresponding relationship that are not illustrated are also within the protection scope of the present invention, and are not described herein again.

In step 205, a session change request is sent to the mobility management entity, so that the session corresponding to the target group is migrated to the second session management entity.

It should be noted that step 205 in this embodiment is the same as step 103 in the first embodiment, and is not described herein again.

In this embodiment, by establishing the corresponding relationship between the internal group identifier, the identifier of the target group, and the identifier of the second data management entity, after the session migration is completed, if a first type of target terminal wishes to join the target group, the join request may be directly sent to the second data management entity, so that the first type of target terminal can join the target group quickly. Furthermore, through service migration and session migration of the target group, terminals of two different network types (namely, the first-class target terminal and the calling terminal) can be added into the same target group to perform group communication, so that the calling terminal can directly share data with the first-class target terminal without transfer of a third-party server, and the problem that a large data file cannot be shared due to flow limitation of the third-party server is avoided.

A third embodiment of the present invention is directed to a method of session migration. Fig. 3 is a flowchart of a session migration method in this embodiment, which can be used for a mobility management entity. The method may include the following steps.

In step 301, a session change request sent by a first data management entity is received.

The session change request includes the internal group identifier of the target group and the session identifier corresponding to the target group.

Wherein the first data management entity is configured to: responding to a target group query request sent by a second data management entity, and obtaining a query result, wherein the target group comprises an identifier of a first type target terminal and an identifier of the target group, and the query request comprises: the method comprises the steps that identification of a target group, the network type of a calling terminal and the network type of a first type of target terminal are set, and the network type of the calling terminal is different from that of the first type of target terminal; if the query result is determined that the target group is stored in the first data management entity, the service information of the target group is transferred to the second data management entity; and sending a session change request to the mobile management entity.

It should be noted that, the main functional roles of the first data management entity are already described in the first embodiment and the second embodiment, and are not described herein again.

In step 302, the session corresponding to the target group is migrated to the second session management entity according to the session change request.

It should be noted that, through signaling interaction between the mobility management entity and the first session management entity, the second session management entity, and the user plane of the second packet data network, the original session corresponding to the target group is deleted, a new session corresponding to the target group is established, and then the session corresponding to the target group is migrated to the second session management entity, and the session identifier of the target group is updated at the same time.

In a specific implementation, a specific flow of migrating the session corresponding to the target group to the second session management entity is shown in fig. 4, and may specifically include the following sub-steps:

in step 401, the first session corresponding to the target group is closed according to the session change request.

In a specific implementation, a session change request is forwarded to a first session management entity, wherein the session change request includes an identifier of a first session and an internal group identifier, and the first session management entity is configured to interact with a user plane of a first packet data network and delete the identifier of the first session; and determining to close the first session corresponding to the target group in response to a session change completion message returned by the first session management entity.

It should be noted that the internal group identifier is a unique global parameter for identifying the target group, the target group establishes the first session on the first session management entity, and the correspondence between the first session identifier and the internal group identifier may be represented by a binary group (internal group identifier, first session identifier). For example, in a 5G communication network, the first session management entity is an SMF entity and the duplet may be represented as (IGI, SID).

For example: in the 5G communication Network, the mobility management entity may be an AMF entity, the first session management entity may be an SMF entity, the second session management entity may be an entity having both an SMF function and a PGW _ C function, and the User plane of the first Packet Data Network may be an entity having both an UPF function and a Packet Data Network Gateway User plane (PGW _ U) function. Specifically, the AMF forwards the session change request to the SMF + PGW _ C, where the session change request includes an SID and an IGI, and the SMF + PGW _ C is configured to interact with a user plane of the first packet data network, delete the first session, and delete the first Session Identifier (SID); and receiving a session change completion message returned by the SMF + PGW _ C, and determining that the first session corresponding to the target group is closed, namely the first session is deleted.

In step 402, a session establishment request is sent to the second session management entity.

Wherein the session establishment request comprises an identification of the first type of target terminal and an internal group identifier. For example, in the 5G communication network, the session establishment request includes a tuple (IGI, SUPI _5 ue1, SUPI _5 ue2, … …, SUPI _5 ue), where IGI is an internal group identifier, SUPI _5 ue1 represents the identifier of the first type target terminal 1, SUPI _5 ue2 represents the identifier of the first type target terminal 2, … …, SUPI _5 ue represents the identifier of the first type target terminal n, and so on.

It should be noted that the tuple (IGI, SUPI _5 rule 1, SUPI _5 rule 2, … …, SUPI _5 rule) is obtained by the AMF entity by receiving a message sent by the UDM when the target group is initially created.

In step 403, the second session of the target group is established in response to the session establishment response sent by the user plane of the second packet data network and forwarded by the second session management entity.

Wherein the session establishment response comprises: an internal group identifier and an identification of the second session.

It should be noted that the correspondence between the second session and the target group is represented by a tuple (internal group identifier, identifier of the second session), so that the first type target terminal of the target group can correspond to the second session, that is, the correspondence between each first type target terminal and the second session is obtained by a tuple (internal group identifier, first type target terminal 1, first type target terminal 2, … …, first type target terminal n) and the tuple (internal group identifier, identifier of the second session). For example, in a 5G communication network, the duplet included in the session establishment response is (IGI, SID _ 5G).

In step 404, the first session identifier of each target terminal in the target group is updated to be the second session identifier.

It should be noted that, after the second session is successfully established, the session identifier corresponding to each first-class target terminal in the target group also needs to be updated. If the binary group is used for representation, the original binary group (the internal group identifier, the identifier of the first session) is updated to (the internal group identifier, the identifier of the second session), so that each first-class target terminal in the target group indirectly knows that the second session is successfully established. For example, in a 5G communication network, the duplet included in the session establishment response is (IGI, SID _5G), i.e. the original duplet (IGI, SID) is updated to the duplet (IGI, SID _ 5G).

In step 405, a session handover complete message is sent to the second data management entity.

For example, in the 5G communication network, the second data management entity is an entity having both an HSS function and a UDM function, and the mobility management entity sends a session handover completion message to the second data management entity, so that the second data management entity knows that the session of the target group has been successfully handed over to the second session management entity, so as to facilitate a subsequent terminal having a network type different from the first type of target terminal to join in the target group.

It should be noted that after the session handover of the target group is completed, if a calling terminal of a network type different from the first type of target terminal requests to join the target group, it is known that the target group is already stored in the second data management entity when the query is performed by using the identifier of the target group. After receiving a group joining request sent by a home server corresponding to a calling terminal, a second data management entity sends a query success message to the home server, so that the home server returns a redirection message to the calling terminal, wherein the redirection message indicates that a target group is stored in the second data management entity, and the calling terminal is required to send a group joining request to the second data management entity.

In a specific implementation, after the step of sending the session handover completion message to the second data management entity, the updated service information of the target group sent by the second session management entity is received, and the second session identifier of each target terminal in the target group is updated to be the third session identifier.

It should be noted that, if the first type of target terminal is a 5G terminal and the calling terminal is a 4G terminal, when a 4G terminal needs to join a target group of a 5G terminal for the first time, the target group needs to be migrated to the second data management entity (i.e., HSS + UDM), and the session of the target group needs to be migrated to the second session management entity (i.e., SMF + PGW _ C), and the session identifier is updated to be the second session identifier, i.e., SID _ 5G. After the 4G terminal successfully joins the target group, the session identifier is updated to be a third session identifier, i.e., SID _4G &5G, again, so as to distinguish the identifier of the session of the target group that the 4G terminal did not participate in originally. The third session identifier is used for indicating that the target group has successfully added the calling terminal, and the type of the calling terminal is different from that of the first type of target terminal. If a second 4G terminal requests to join the target group, the second 4G terminal can be joined to the target group without migrating the target group directly through interaction between the second data management entity and the second session management entity, and the user plane of the second packet data network. The operation steps of joining the group are simplified, and the efficiency is improved.

The updated service information of the target group includes a service subscription relationship, and the service subscription relationship includes: an internal group identifier, a third session identity, an identity of the calling terminal and an identity of the first type of target terminal.

In particular, the service subscription relationship may be represented using a tuple (internal group identifier, identification of the first type target terminal, identification of the calling terminal) and a tuple (internal group identifier, third session identification). For example, after the 4G calling terminal requests to join the target group consisting of the 5G terminals, the service subscription relationship for indicating that the 4G calling terminal has successfully subscribed to the session service of the target group is represented by using the multi-tuple (IGI, SUPI _5GUE1, SUPI _5GUE2, … …, SUPI _5GUEn, SUPI _4GUE) and the two-tuple (IGI, SID _4G &5G), and the 4G calling terminal can perform data communication with the first type target terminals in the target group through the target group, and share the data file.

It should be noted that each terminal added to the target group may exit the target group in an active on-hook manner, and further release the radio link resource. Or the SMF releases the Radio link Resource by setting an idle timer, for example, setting the duration of the timer to be 5 seconds, and if the duration of no data transmission in the target group exceeds 5 seconds, the SMF may notify each terminal in the target group to execute a link connection reconfiguration message of a Radio Resource Control (RRC) layer, so as to automatically release the Radio link Resource, but still maintain the connection relationship of the call session.

In the embodiment, the session change request sent by the first data management entity is received; and according to the session change request, the session corresponding to the target group is migrated to the second session management entity, so that the calling terminal of the network type different from the first type of target terminal can be added into the target group, and then the two terminals of different network types can share data in a group communication mode, so that the data can be shared without passing through a third-party server, and the problem that a large data file cannot be shared due to the flow limitation of the third-party server is avoided.

The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included, which are all within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.

The fourth embodiment of the present invention relates to a device for session migration, and specific implementation of the device may refer to the related description of the first embodiment, and repeated details are not repeated. It should be noted that, the specific implementation of the apparatus in this embodiment may also refer to the related description of the second embodiment, but is not limited to the above two examples, and other unexplained examples are also within the protection scope of the apparatus.

As shown in fig. 5, the apparatus mainly includes: an obtaining module 501, configured to obtain a query result in response to a target group query request sent by a second data management entity, where the target group includes an identifier of a first type of target terminal and an identifier of the target group, and the query request includes: the method comprises the steps that identification of a target group, the network type of a calling terminal and the network type of a first type of target terminal are set, and the network type of the calling terminal is different from that of the first type of target terminal; a service migration module 502, configured to migrate service information of a target group to a second data management entity after determining that the target group is stored in a first data management entity; the first session migration module 503 is configured to send a session change request to the mobility management entity, so that a session corresponding to the target group is migrated to the second session management entity.

A fifth embodiment of the present invention relates to a session migration apparatus, and specific implementation of the apparatus may refer to the related description of the third embodiment, and repeated details are not repeated, but the apparatus is not limited to the third embodiment, and other unexplained embodiments are also within the protection scope of the apparatus.

As shown in fig. 6, the apparatus mainly includes: a receiving module 601, configured to receive a session change request sent by a first data management entity; a second session migration module 602, configured to migrate, according to the session change request, the session corresponding to the target group to the second session management entity; the first data management entity comprises the following modules: an obtaining module 501, configured to obtain a query result in response to a target group query request sent by a second data management entity, where the target group includes an identifier of a first type of target terminal and an identifier of the target group, and the query request includes: the method comprises the steps that identification of a target group, the network type of a calling terminal and the network type of a first type of target terminal are set, and the network type of the calling terminal is different from that of the first type of target terminal; a service migration module 502, configured to migrate the service information of the target group to the second data management entity after determining that the query result is that the target group is stored in the first data management entity; a sending module 603, configured to send a session change request to the mobility management entity.

It should be noted that each module referred to in this embodiment is a logical module, and in practical applications, one logical unit may be one physical unit, may be a part of one physical unit, and may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present invention, elements that are not so closely related to solving the technical problems proposed by the present invention are not introduced in the present embodiment, but this does not indicate that other elements are not present in the present embodiment.

A sixth embodiment of the present invention relates to a system for session migration, and as shown in fig. 7, the system specifically includes: a first class of target terminals 801(5G terminals), a mobility management entity 802(AMF), a first session management entity 803(SMF), a first data management entity 804(UDM), a second data management entity 805(HSS + UDM), a second session management entity 806(SMF + PGW _ C), a user plane 807(UPF + PGW _ U) of the second packet data network, a home server 808(HSS) corresponding to the calling terminal, a control plane 809 of the packet data network, a serving gateway 810, a network node 811, the calling terminal 812(4G terminal), a user plane 813(UPF) of the first packet data network.

In step 701, a user group consisting of only 5G terminals is created through interaction among the 5G terminals, AMF, SMF and UDM.

It should be noted that the group uses the UPF as a data relay, so that the communication between the group members does not pass through the data network, that is, the communication between the group members is completed in the communication network, and a third-party server is not needed for relay. When creating a group, the identifier of the group may be set or may not be set. If the group has no set group identification, all the 5G terminals can be added into the group; if the group is set with the identification (such as group ID) of a specific group, the group is indicated to have designated group members, and other 5G terminals except the designated group members cannot join the group.

In step 702, each 5G terminal in the group performs group communication through the UPF.

For example, there are n 5G terminals in the group, and the corresponding identifiers are 5GUE1, 5GUE2, … …, and 5GUEn, respectively, where n is a natural number greater than or equal to 2.

In step 703, the calling terminal (i.e., 4G terminal) sends a join request message to the HSS with the group as a target group.

It should be noted that the request to join message includes a service access code (for indicating that group mode communication is desired), an identifier of the target group, and an identifier of the called terminal included in the target group.

In step 704, the HSS recognizes that the identifier of the called terminal (e.g. the mobile phone number of the terminal) is a service access identifier in a 5G network, and forwards the join group request to the second data management entity (HSS + UDM).

In step 705, the HSS + UDM retrieves whether there is locally corresponding group information using the identification of the group submitted by the HSS, i.e. the group ID. If so, go to step 718; if not, step 706 is performed.

In step 706, the HSS + UDM sends a group query request to the UDM corresponding to the 5G terminal in the target group, and queries whether a group identified by the group ID exists.

In step 707, the UDM queries according to the group ID to obtain a query result, and returns the query result to the HSS + UDM.

Specifically, if the query result is that the UDM does not have the group ID, the HSS + UDM returns a group joining failure message to the HSS, the HSS forwards the group joining failure message to the MME, the MME returns a call failure message to the 4G terminal, and the process ends; if the query results in a UDM with the group ID, then step 708 is performed.

In step 708, the HSS + UDM sends a service migration request to the UDM requesting to migrate the service information of the group corresponding to the group ID to the HSS + UDM, where the service information includes the service context information of the group and the service subscription relationship.

It should be noted that the service subscription relationship may use a tuple to represent the correspondence between the group and each terminal, for example, (IGI, SUPI _5GUE1, SUPI _5GUE2, … …, SUPI _ 5GUE), where IGI represents the internal group identifier of the target group to uniquely identify the target group, SUPI _5GUE1 represents the first 5G terminal in the group, SUPI _5GUE2 represents the 2 nd 5G terminal in the group, … …, SUPI _5GUE represents the n th 5G terminal in the group, where n is a natural number greater than or equal to 2; the service context information includes: forwarding rules (e.g., store-and-forward rules, direct forwarding rules, etc.) applicable to the IGI of the target group, priority (e.g., if there are multiple data to be forwarded, the priority of the data of the target group when being forwarded), priority scheduling policy, Quality of Service (QoS) parameter, charging preference policy, whether encrypted transmission is required, etc.; the QoS parameters may include time delay, jitter, packet loss number, etc.; the charging preferential strategy is a preferential rule defined by an operator; the priority scheduling strategy may employ the following scheduling algorithm: FIFO first-in first-out Scheduling algorithm, Round-Robin Scheduling (RRS), etc.

In step 709, the UDM transmits the service information of the target group corresponding to the IGI to the HSS + UDM.

It should be noted that the group ID is set by the calling terminal that creates the group, and the IGI is automatically assigned by the UDM, and in the whole session migration system, the IGI is a unique and unchangeable global parameter for identifying the target group.

In step 710, the UDM sends a session change command to the AMF.

Wherein the session change command comprises: group ID corresponding binary (IGI, SID), SID represents session ID corresponding to target group.

It should be noted that, while sending the session change command to the AMF, the UDM needs to delete the tuple (IGI, SUPI _5GUE1, SUPI _5GUE2, … …, SUPI _5GUEn) and the tuple (IGI, SID), but establish a new correspondence, i.e. the tuple (IGI, group ID, HSS + UDM _ ID), where HSS + UDM _ ID represents the identifier of HSS + UDM, so that when a subsequent 5G terminal wishes to join the target group, the joining request can be forwarded to the corresponding HSS + UDM.

In step 711, the AMF interacts with the SMF and the UPF according to the received session change instruction sent by the UDM, and closes the session corresponding to the SID in the duplet (IGI, SID).

Specifically, the AMF forwards the session change request to the SMF + PGW _ C, where the session change request includes an identifier of the first session and an IGI, and the SMF + PGW _ C is configured to interact with a user plane of the first packet data network and delete the identifier of the first session; and receiving a session change completion message returned by the SMF + PGW _ C, and determining that the first session corresponding to the target group is closed.

In step 712, the AMF initiates a session setup request to SMF + PGW _ C.

The session establishment request includes a tuple (IGI, SUPI _5 ue1, SUPI _5 ue2, … …, SUPI _5 ue).

It should be noted that the tuple is obtained by receiving a message sent by the UDM when the AMF creates the target group in step 701.

In step 713, the SMF + PGW _ C and the UPF + PGW _ U interactively establish a second session, generate a tuple (IGI, SUPI _5 rule 1, SUPI _5 rule 2, … …, SUPI _5 rule), and update the session ID corresponding to the target group, i.e. update the original SID to SID _ 5G.

In step 714, SMF + PGW _ C returns a doublet (IGI, SID _5G) to AMF.

In step 715, the AMF updates the session ID of each 5G terminal in the target group, i.e. replaces the duplet (IGI, SID) of 5GUE1, 5GUE2, … …, 5GUEn with the duplet (IGI, SID _ 5G).

In step 716, group communication is performed between the 5G terminals (i.e., 5GUE1, 5GUE2, … …, 5GUEn) in the target group, and the relay device of the group communication is changed from the original UPF to UPF + PGW _ U.

In step 717, the AMF returns a session change complete message to the HSS + UDM.

In step 718, the HSS + UDM returns a query success message to the HSS.

In step 719, the HSS returns a redirect message to the MME.

It should be noted that, according to the redirection message, the MME is made aware that the HSS + UMD is required to send the join group request.

In step 720, the MME sends a join group request to the HSS + UMD.

Wherein the join group request includes a group ID of the target group.

In step 721, the HSS + UMD adds the 4G terminal corresponding to the MME to the target group and updates the tuple (IGI, SUPI _5 ue1, SUPI _5 ue2, … …, SUPI _5 ue) to (IGI, SUPI _5 ue1, SUPI _5 ue2, … …, SUPI _5 ue, SUPI _4 ue), and at the same time, (IGI, SID _5G) to (IGI, SID _4G & 5G).

In step 722, the HSS + UMD returns a join group success message to the MME.

Wherein, the join group success message includes a multi-tuple (IGI, SUPI _5GUE1, SUPI _5GUE2, … …, SUPI _5GUEn, SUPI _4GUE) and a two-tuple (IGI, SID _4G & 5G).

In step 723, the MME sends a join session request to SMF + PGW _ C.

Wherein the join session request includes a duplet (IGI, SID _4G & 5G).

In step 724, the SMF + PGW _ C interacts with the HSS + UDM to complete the service authentication of the target group.

In step 725, the SMF + PGW _ C interacts with the UPF + PGW _ U, and adds the 4G terminal to the session corresponding to the target group.

In step 726, the SMF + PGW _ C returns a join group session success message to the MME. Meanwhile, the updated session context is sent to the AMF.

Wherein the session context includes a duplet (IGI, SID _4G & 5G).

In step 727, the MME sends a join success message to the 4G terminal. Meanwhile, the AMF updates the session ID of each 5G terminal (i.e. 5gu 1, 5gu 2, … …, 5 gu) in the target group one by one, i.e. updates the duplet (IGI, SID _5G) of all 5G terminals in the target group to (IGI, SID _4G & 5G).

In step 728, the 4G terminal performs group communication with each 5G terminal in the target group.

In the embodiment, the obtained service information of the target group is transferred to the second data management entity through the message interaction of the first data management entity and the second data management entity; through the message interaction among the first data management entity, the mobile management entity and the first session management entity, the session corresponding to the target group is migrated to the second session management entity, all the service information and the session of the target group are changed through the migration, so that terminals (namely a first type target terminal and a calling terminal) of two different network types can be added into the same target group for group communication, the calling terminal can directly share data with the first type target terminal without the transfer of a third-party server, and the problem that large data files cannot be shared due to the flow limitation of a third-party server is avoided.

It will be understood that the above embodiments are merely exemplary embodiments taken to illustrate the principles of the present invention, which is not limited thereto. It will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the spirit and substance of the invention, and these modifications and improvements are also considered to be within the scope of the invention.

Claims

1. A method of session migration, applied to a first data management entity, the method comprising:

responding to a target group query request sent by a second data management entity, and obtaining a query result, wherein the target group comprises an identifier of a first type target terminal and an identifier of the target group, and the query request comprises: the second data management entity has the function of cross-network communication;

if the query result is determined that the target group is stored in the first data management entity, migrating the service information of the target group to the second data management entity;

and sending a session change request to a mobile management entity so as to enable the session corresponding to the target group to be migrated to a second session management entity.

2. The method of session migration according to claim 1, wherein the step of migrating the service information of the target group to the second data management entity includes:

receiving a service migration request sent by the second data management entity;

and sending a service migration response to the second data management entity, wherein the service migration response carries service information of the target group, the service information comprises a service ordering relationship, and the service ordering relationship comprises an internal group identifier and an identifier of the first type of target terminal.

3. The method for session migration according to claim 1, wherein after the migrating the service information of the target group to the second data management entity and before the sending the session change request to the mobility management entity, further comprising:

deleting the corresponding relation between the internal group identifier and the first type of target terminal, deleting the corresponding relation between the internal group identifier and the first session identifier corresponding to the target group, and establishing the corresponding relation between the internal group identifier, the identifier of the target group and the identifier of the second data management entity.

4. The method of session migration according to any of claims 1 to 3, wherein the query result further comprises:

and if the query result indicates that the target group is not stored in the first data management entity and the target group is not stored in the second data management entity, determining that the calling terminal fails to join the target group.

5. A method for session migration, applied to a mobility management entity, the method comprising:

receiving a session change request sent by a first data management entity;

migrating the session corresponding to the target group to a second session management entity according to the session change request;

wherein the first data management entity is configured to:

and sending a session change request to the mobile management entity.

6. The method of session migration according to claim 5, wherein the step of migrating the session corresponding to the target group to a second session management entity according to the session change request includes:

closing a first session corresponding to the target group according to the session change request;

sending a session establishment request to a second session management entity, wherein the session establishment request comprises the identifier of the first type target terminal and an internal group identifier;

establishing a second session of the target group in response to a session establishment response sent by a user plane of a second packet data network forwarded by the second session management entity, the session establishment response comprising: an internal group identifier and an identification of the second session;

updating the first session identifier of each target terminal in the target group to the second session identifier;

and sending a session switching completion message to the second data management entity.

7. The method of session migration according to claim 6, wherein the step of closing the first session corresponding to the target group comprises:

forwarding the session change request to a first session management entity, wherein the session change request includes an identifier of the first session and an internal group identifier, and the first session management entity is configured to interact with a user plane of a first packet data network and delete the identifier of the first session;

and determining to close the first session corresponding to the target group in response to a session change completion message returned by the first session management entity.

8. The method of session migration according to claim 6 or 7, wherein after the step of sending the session switch completion message to the second data management entity, the method further comprises:

updating the second session identifier of each target terminal in the target group to a third session identifier in response to the updated service information of the target group sent by the second session management entity;

the updated service information of the target group comprises a service subscription relationship, wherein the service subscription relationship comprises an internal group identifier, a third session identifier, an identifier of the calling terminal and an identifier of the first type of target terminal.

9. An apparatus for session migration, comprising:

an obtaining module, configured to obtain a query result in response to a target group query request sent by a second data management entity, where the target group includes an identifier of a first type of target terminal and an identifier of the target group, and the query request includes: the second data management entity has the function of cross-network communication;

the service migration module is used for migrating the service information of the target group to the second data management entity after determining that the target group is stored in the first data management entity;

and the first session migration module is used for sending a session change request to the mobile management entity so as to enable the session corresponding to the target group to be migrated to the second session management entity.

10. An apparatus for session migration, comprising:

the receiving module is used for receiving a session change request sent by a first data management entity;

the session migration module is used for migrating the session corresponding to the target group to a second session management entity according to the session change request, and the second data management entity has the function of cross-network communication;

wherein the first data management entity comprises the following modules:

an obtaining module, configured to obtain a query result in response to a target group query request sent by a second data management entity, where the target group includes an identifier of a first type of target terminal and an identifier of the target group, and the query request includes: the method comprises the steps that identification of a target group, a network type of a calling terminal and a network type of a first type of target terminal are carried out, and the network type of the calling terminal is different from the network type of the first type of target terminal;

the second service migration module is used for migrating the service information of the target group to the second data management entity after determining that the query result is that the target group is stored in the first data management entity;

and the sending module is used for sending the session change request to the mobile management entity.