An information transmission method, device and equipment

Abstract

The application provides an information transmission method, device and equipment, wherein the information transmission method is applied to a target session management function entity, and the method comprises the following steps: receiving a session context creation request message sent by a target access and mobility management function entity; obtaining a mobility management context of at least one session according to the session context creation request message; and performing mobility management according to the mobility management context; wherein the mobility management context comprises at least one of an access management context and a session management context. The present scheme can support the implementation that one-time mobility management for cross-distributed network nodes can be performed for at least one session, thereby avoiding the implementation that each time mobility management can be performed for only one session, so as to improve data migration efficiency, reduce switching delay, and well solve the problems of low data migration efficiency and high switching delay in the prior art information transmission scheme for mobility management.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to an information transmission method, apparatus and device. Background Technology

[0002] The current 5G mobile communication network system is designed with centralized control. With the development of the network, the trend of 6G network is a network architecture that combines centralized and distributed control. 6G will extend more network functions to the network edge and build distributed homogeneous nodes with different functional levels. Each distributed network node has complete control and data forwarding functions.

[0003] For the issue of UE mobility management across distributed network nodes in 6G distributed networks, if the traditional session-granular user context migration method is used, it will lead to problems such as low data migration efficiency and high UE (terminal) handover latency. Moreover, when the UE moves quickly, it may cause problems such as untimely handover and service interruption.

[0004] As stated above, while existing methods can solve cross-domain mobility management issues, their session-level user context switching leads to problems such as low data migration efficiency and high switching latency. Furthermore, current technologies only support session-level mobility management; specifically, each mobility management operation can only be performed on a single session.

[0005] In summary, existing information transmission schemes for mobility management can only be performed on one session at a time, resulting in problems such as low data migration efficiency and high handover latency. Summary of the Invention

[0006] The purpose of this application is to provide an information transmission method, apparatus, and device to solve the problems of low data migration efficiency and high handover latency in existing information transmission schemes for mobility management.

[0007] To address the aforementioned technical problems, embodiments of this application provide an information transmission method applied to a target session management function entity, comprising:

[0008] Receive a session context creation request message sent by the target access and mobility management function entity;

[0009] A request message is created based on the session context to obtain the mobility management context of at least one session;

[0010] Mobility management is performed based on the mobility management context.

[0011] The mobility management context includes at least one of an access management context and a session management context.

[0012] Optionally, the step of creating a request message based on the session context to obtain the mobility management context of at least one session includes:

[0013] If the session context creation request message carries the mobility management context of at least one session, the mobility management context of the at least one session is obtained from the session context creation request message.

[0014] If the session context creation request message does not carry the session's mobility management context, a session context request message for at least one session is sent to the target repository entity; a session context response message is received from the target repository entity, the session context response message carrying the mobility management context of the at least one session.

[0015] Optionally, the target warehouse entity is deployed in at least one of the following ways:

[0016] Add at least one network function as a warehouse entity to the control plane;

[0017] Extend the defined network functionality as a warehouse entity;

[0018] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0019] This application also provides an information transmission method applied to a target access and mobility management function entity, including:

[0020] Receive a handover resource allocation request message for at least one session from the source access and mobility management function entity;

[0021] Based on the resource allocation switching request message, a session context creation request message is sent to the target session management function entity corresponding to each session;

[0022] The session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session.

[0023] The mobility management context includes at least one of the following: access management context and session management context.

[0024] Optionally, if the session context creation request message carries the mobility management context of at least one of the sessions, before sending the session context creation request message to the target session management function entity corresponding to each session according to the handover resource allocation request message, the method further includes:

[0025] Based on the first information carried in the resource allocation switching request message, a first context retrieval request message is sent to the target warehouse entity;

[0026] Receive the first context acquisition response message from the target warehouse entity;

[0027] The first information includes at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session.

[0028] The first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session;

[0029] The first context acquisition response message carries at least one mobility management context of the session requested by the first context acquisition request message.

[0030] Optionally, the switch resource allocation request message carries at least one mobility management context of the session.

[0031] Optionally, if the session context creation request message does not carry the session's mobility management context, before sending the session context creation request message to the target session management function entity corresponding to each session according to the handover resource allocation request message, the method further includes:

[0032] Based on the second information carried in the resource allocation switching request message, a context acquisition notification is sent to the target warehouse entity;

[0033] The second information includes at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session;

[0034] The context acquisition notification carries at least one of the following: the terminal identification information, the session identification information of at least one session, and the node identification information of the network node corresponding to at least one session.

[0035] Optionally, the second information further includes: the access management context corresponding to the at least one session; the context acquisition notification is used to notify the target repository entity to acquire the session management context, and / or is not used to notify the target repository entity to acquire the access management context contained in the second information.

[0036] Optionally, the target warehouse entity is deployed in at least one of the following ways:

[0037] Add at least one network function as a warehouse entity to the control plane;

[0038] Extend the defined network functionality as a warehouse entity;

[0039] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0040] This application also provides an information transmission method applied to a target warehouse entity, including:

[0041] Receive third information sent by the target access and mobility management function entity;

[0042] Based on the third information, a context retrieval operation is performed;

[0043] The third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session;

[0044] Alternatively, the third information may include: a context acquisition notification; the context acquisition notification carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to the session.

[0045] Optionally, if the third information includes a first context acquisition request message, the step of performing the context acquisition operation based on the third information includes:

[0046] If the target warehouse entity does not store the mobility management context requested by the first context acquisition request message, a second context acquisition request message is sent to the source warehouse entity according to the first context acquisition request message;

[0047] Receive the second context acquisition response message from the source repository entity;

[0048] The second context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session.

[0049] The second context acquisition response message carries the mobility management context of at least one session requested by the second context acquisition request message; the mobility management context includes at least one of an access management context and a session management context.

[0050] Optionally, after performing the context acquisition operation based on the third information, the method further includes:

[0051] Based on the second context, obtain the response message and send the first context to the target access and mobility management function entity;

[0052] The first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0053] Optionally, sending a second context retrieval request message to the source repository entity based on the first context retrieval request message includes:

[0054] Based on the information carried in the request message obtained from the first context, the relevant information of the corresponding source repository entity is determined;

[0055] Based on the relevant information of the source repository entity, a second context retrieval request message is sent to the source repository entity.

[0056] Optionally, if the third information includes a context acquisition notification, the context acquisition operation based on the third information includes:

[0057] Based on the context, a notification is obtained, and a third context retrieval request message is sent to the source repository entity.

[0058] Receive the third context acquisition response message fed back by the source warehouse entity;

[0059] The third context acquisition request message carries at least one of the following: the terminal identification information, the session identification information of at least one session, and the node identification information of the network node corresponding to at least one session.

[0060] The third context acquisition response message carries the mobility management context of at least one session requested by the third context acquisition request message;

[0061] The mobility management context includes at least one of the following: access management context and session management context.

[0062] Optionally, the first warehouse entity is deployed in at least one of the following ways:

[0063] Add at least one network function as a warehouse entity to the control plane;

[0064] Extend the defined network functionality as a warehouse entity;

[0065] One of the warehouse entities is used to store at least one of the access management context and the session management context;

[0066] The first warehouse entity includes the target warehouse entity and / or the source warehouse entity.

[0067] This application also provides an information transmission method applied to a source warehouse entity, including:

[0068] Receive the context retrieval request message sent by the first entity;

[0069] Based on the context, obtain the request message and send a context retrieval response message to the first entity;

[0070] Wherein, the first entity includes: a target warehouse entity; the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message;

[0071] Alternatively, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition response message;

[0072] The context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message.

[0073] The mobility management context includes at least one of the following: access management context and session management context.

[0074] Optionally, the first warehouse entity is deployed in at least one of the following ways:

[0075] Add at least one network function as a warehouse entity to the control plane;

[0076] Extend the defined network functionality as a warehouse entity;

[0077] One of the warehouse entities is used to store at least one of the access management context and the session management context;

[0078] The first warehouse entity includes the target warehouse entity and / or the source warehouse entity.

[0079] This application also provides an information transmission method, applied to a source access and mobility management entity, including:

[0080] Send a fourth context retrieval request message to the source repository entity;

[0081] Receive the fourth context acquisition response message fed back by the source warehouse entity;

[0082] Based on the fourth context, obtain the response message and send a handover resource allocation request message for at least one session to the target access and mobility management function entity;

[0083] The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message.

[0084] The mobility management context includes at least one of: access management context and session management context;

[0085] The resource allocation switching request message carries the mobility management context of at least one session.

[0086] Optionally, the source repository entity is deployed in at least one of the following ways:

[0087] Add at least one network function as a warehouse entity to the control plane;

[0088] Extend the defined network functionality as a warehouse entity;

[0089] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0090] This application embodiment also provides an information transmission device, which is a target session management function entity, including a memory, a transceiver, and a processor:

[0091] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0092] The transceiver receives a session context creation request message sent by the target access and mobility management function entity.

[0093] A request message is created based on the session context to obtain the mobility management context of at least one session;

[0094] Mobility management is performed based on the mobility management context.

[0095] The mobility management context includes at least one of an access management context and a session management context.

[0096] Optionally, the step of creating a request message based on the session context to obtain the mobility management context of at least one session includes:

[0097] If the session context creation request message carries the mobility management context of at least one session, the mobility management context of the at least one session is obtained from the session context creation request message.

[0098] If the session context creation request message does not carry the session's mobility management context, the transceiver sends a session context request message for at least one session to the target repository entity; and the transceiver receives a session context response message from the target repository entity, the session context response message carrying the mobility management context of the at least one session.

[0099] Optionally, the target warehouse entity is deployed in at least one of the following ways:

[0100] Add at least one network function as a warehouse entity to the control plane;

[0101] Extend the defined network functionality as a warehouse entity;

[0102] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0103] This application embodiment also provides an information transmission device, which is a target access and mobility management function entity, including a memory, a transceiver, and a processor:

[0104] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0105] The transceiver receives a handover resource allocation request message for at least one session from the source access and mobility management function entity.

[0106] Through the transceiver, a session context creation request message is sent to the target session management function entity corresponding to each session according to the switching resource allocation request message;

[0107] The session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session.

[0108] The mobility management context includes at least one of the following: access management context and session management context.

[0109] Optionally, the operation further includes:

[0110] When the session context creation request message carries at least one mobility management context of the session, before sending the session context creation request message to the target session management function entity corresponding to each session according to the switching resource allocation request message, the transceiver sends a first context acquisition request message to the target repository entity according to the first information carried in the switching resource allocation request message.

[0111] The transceiver receives the first context acquisition response message from the target warehouse entity.

[0112] The first information includes at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session.

[0113] The first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session;

[0114] The first context acquisition response message carries at least one mobility management context of the session requested by the first context acquisition request message.

[0115] Optionally, the switch resource allocation request message carries at least one mobility management context of the session.

[0116] Optionally, the operation further includes:

[0117] If the session context creation request message does not carry the session's mobility management context, before sending the session context creation request message to the target session management function entity corresponding to each session according to the switching resource allocation request message, the transceiver sends a context acquisition notification to the target repository entity according to the second information carried in the switching resource allocation request message.

[0118] The second information includes at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session;

[0119] The context acquisition notification carries at least one of the following: the terminal identification information, the session identification information of at least one session, and the node identification information of the network node corresponding to at least one session.

[0120] Optionally, the second information further includes: the access management context corresponding to the at least one session; the context acquisition notification is used to notify the target repository entity to acquire the session management context, and / or is not used to notify the target repository entity to acquire the access management context contained in the second information.

[0121] Optionally, the target warehouse entity is deployed in at least one of the following ways:

[0122] Add at least one network function as a warehouse entity to the control plane;

[0123] Extend the defined network functionality as a warehouse entity;

[0124] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0125] This application embodiment also provides an information transmission device, which is a target warehouse entity, including a memory, a transceiver, and a processor:

[0126] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0127] The transceiver receives third information sent by the target access and mobility management function entity.

[0128] Based on the third information, a context retrieval operation is performed;

[0129] The third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session;

[0130] Alternatively, the third information may include: a context acquisition notification; the context acquisition notification carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to the session.

[0131] Optionally, if the third information includes a first context acquisition request message, the step of performing the context acquisition operation based on the third information includes:

[0132] If the target warehouse entity does not store the mobility management context requested by the first context acquisition request message, the transceiver sends a second context acquisition request message to the source warehouse entity according to the first context acquisition request message.

[0133] The transceiver receives the second context acquisition response message from the source warehouse entity.

[0134] The second context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session.

[0135] The second context acquisition response message carries the mobility management context of at least one session requested by the second context acquisition request message; the mobility management context includes at least one of an access management context and a session management context.

[0136] Optionally, the operation further includes:

[0137] After performing a context acquisition operation based on the third information, the transceiver sends a first context acquisition response message to the target access and mobility management function entity based on the second context acquisition response message.

[0138] The first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0139] Optionally, sending a second context retrieval request message to the source repository entity based on the first context retrieval request message includes:

[0140] Based on the information carried in the request message obtained from the first context, the relevant information of the corresponding source repository entity is determined;

[0141] Based on the relevant information of the source repository entity, a second context retrieval request message is sent to the source repository entity.

[0142] Optionally, if the third information includes a context acquisition notification, the context acquisition operation based on the third information includes:

[0143] Using the transceiver, a third context retrieval request message is sent to the source repository entity based on the context retrieval notification.

[0144] The transceiver receives the third context acquisition response message fed back by the source warehouse entity.

[0145] The third context acquisition request message carries at least one of the following: the terminal identification information, the session identification information of at least one session, and the node identification information of the network node corresponding to at least one session.

[0146] The third context acquisition response message carries the mobility management context of at least one session requested by the third context acquisition request message;

[0147] The mobility management context includes at least one of the following: access management context and session management context.

[0148] Optionally, the first warehouse entity is deployed in at least one of the following ways:

[0149] Add at least one network function as a warehouse entity to the control plane;

[0150] Extend the defined network functionality as a warehouse entity;

[0151] One of the warehouse entities is used to store at least one of the access management context and the session management context;

[0152] The first warehouse entity includes the target warehouse entity and / or the source warehouse entity.

[0153] This application embodiment also provides an information transmission device, which is a source warehouse entity, including a memory, a transceiver, and a processor:

[0154] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0155] The transceiver receives a context acquisition request message sent by the first entity.

[0156] Using the transceiver, a context retrieval request message is obtained based on the context retrieval request message, and a context retrieval response message is sent to the first entity.

[0157] Wherein, the first entity includes: a target warehouse entity; the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message;

[0158] Alternatively, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition response message;

[0159] The context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message.

[0160] The mobility management context includes at least one of the following: access management context and session management context.

[0161] Optionally, the first warehouse entity is deployed in at least one of the following ways:

[0162] Add at least one network function as a warehouse entity to the control plane;

[0163] Extend the defined network functionality as a warehouse entity;

[0164] One of the warehouse entities is used to store at least one of the access management context and the session management context;

[0165] The first warehouse entity includes the target warehouse entity and / or the source warehouse entity.

[0166] This application also provides an information transmission device, which is a source access and mobility management entity, including a memory, a transceiver, and a processor.

[0167] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0168] The transceiver sends a fourth context retrieval request message to the source repository entity.

[0169] The transceiver receives the fourth context acquisition response message from the source warehouse entity.

[0170] The transceiver obtains a response message based on the fourth context and sends a handover resource allocation request message for at least one session to the target access and mobility management function entity.

[0171] The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message.

[0172] The mobility management context includes at least one of: access management context and session management context;

[0173] The resource allocation switching request message carries the mobility management context of at least one session.

[0174] Optionally, the source repository entity is deployed in at least one of the following ways:

[0175] Add at least one network function as a warehouse entity to the control plane;

[0176] Extend the defined network functionality as a warehouse entity;

[0177] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0178] This application also provides an information transmission device applied to a target session management function entity, including:

[0179] The first receiving unit is used to receive a session context creation request message sent by the target access and mobility management function entity;

[0180] The first processing unit is configured to create a request message based on the session context to obtain the mobility management context of at least one session;

[0181] The second processing unit is used to perform mobility management based on the mobility management context;

[0182] The mobility management context includes at least one of an access management context and a session management context.

[0183] Optionally, the step of creating a request message based on the session context to obtain the mobility management context of at least one session includes:

[0184] If the session context creation request message carries the mobility management context of at least one session, the mobility management context of the at least one session is obtained from the session context creation request message.

[0185] If the session context creation request message does not carry the session's mobility management context, a session context request message for at least one session is sent to the target repository entity; a session context response message is received from the target repository entity, the session context response message carrying the mobility management context of the at least one session.

[0186] Optionally, the target warehouse entity is deployed in at least one of the following ways:

[0187] Add at least one network function as a warehouse entity to the control plane;

[0188] Extend the defined network functionality as a warehouse entity;

[0189] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0190] This application also provides an information transmission device applied to a target access and mobility management function entity, including:

[0191] The second receiving unit is used to receive a handover resource allocation request message for at least one session sent by the source access and mobility management function entity.

[0192] The first sending unit is configured to send a session context creation request message to the target session management function entity corresponding to each session, based on the switching resource allocation request message.

[0193] The session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session.

[0194] The mobility management context includes at least one of the following: access management context and session management context.

[0195] Optional, also includes:

[0196] The second sending unit is configured to send a first context acquisition request message to a target repository entity based on the first information carried in the switching resource allocation request message before sending the session context creation request message to the target session management function entity corresponding to each session according to the switching resource allocation request message, when the session context creation request message carries at least one mobility management context of the session.

[0197] The third receiving unit is used to receive the first context acquisition response message fed back by the target warehouse entity;

[0198] The first information includes at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session.

[0199] The first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session;

[0200] The first context acquisition response message carries at least one mobility management context of the session requested by the first context acquisition request message.

[0201] Optionally, the switch resource allocation request message carries at least one mobility management context of the session.

[0202] Optional, also includes:

[0203] The third sending unit is configured to send a context acquisition notification to the target repository entity based on the second information carried in the switching resource allocation request message before sending the session context creation request message to the target session management function entity corresponding to each session according to the switching resource allocation request message, in the case where the session context creation request message does not carry the session mobility management context.

[0204] The second information includes at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session;

[0205] The context acquisition notification carries at least one of the following: the terminal identification information, the session identification information of at least one session, and the node identification information of the network node corresponding to at least one session.

[0206] Optionally, the second information further includes: the access management context corresponding to the at least one session; the context acquisition notification is used to notify the target repository entity to acquire the session management context, and / or is not used to notify the target repository entity to acquire the access management context contained in the second information.

[0207] Optionally, the target warehouse entity is deployed in at least one of the following ways:

[0208] Add at least one network function as a warehouse entity to the control plane;

[0209] Extend the defined network functionality as a warehouse entity;

[0210] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0211] This application also provides an information transmission device applied to a target warehouse entity, including:

[0212] The fourth receiving unit is used to receive third information sent by the target access and mobility management function entity;

[0213] The third processing unit is used to perform a context acquisition operation based on the third information;

[0214] The third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session;

[0215] Alternatively, the third information may include: a context acquisition notification; the context acquisition notification carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to the session.

[0216] Optionally, if the third information includes a first context acquisition request message, the step of performing the context acquisition operation based on the third information includes:

[0217] If the target warehouse entity does not store the mobility management context requested by the first context acquisition request message, a second context acquisition request message is sent to the source warehouse entity according to the first context acquisition request message;

[0218] Receive the second context acquisition response message from the source repository entity;

[0219] The second context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session.

[0220] The second context acquisition response message carries the mobility management context of at least one session requested by the second context acquisition request message; the mobility management context includes at least one of an access management context and a session management context.

[0221] Optional, also includes:

[0222] The fourth sending unit is configured to send a first context acquisition response message to the target access and mobility management function entity based on the second context acquisition response message after performing a context acquisition operation based on the third information.

[0223] The first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0224] Optionally, sending a second context retrieval request message to the source repository entity based on the first context retrieval request message includes:

[0225] Based on the information carried in the request message obtained from the first context, the relevant information of the corresponding source repository entity is determined;

[0226] Based on the relevant information of the source repository entity, a second context retrieval request message is sent to the source repository entity.

[0227] Optionally, if the third information includes a context acquisition notification, the context acquisition operation based on the third information includes:

[0228] Based on the context, a notification is obtained, and a third context retrieval request message is sent to the source repository entity.

[0229] Receive the third context acquisition response message fed back by the source warehouse entity;

[0230] The third context acquisition request message carries at least one of the following: the terminal identification information, the session identification information of at least one session, and the node identification information of the network node corresponding to at least one session.

[0231] The third context acquisition response message carries the mobility management context of at least one session requested by the third context acquisition request message;

[0232] The mobility management context includes at least one of the following: access management context and session management context.

[0233] Optionally, the first warehouse entity is deployed in at least one of the following ways:

[0234] Add at least one network function as a warehouse entity to the control plane;

[0235] Extend the defined network functionality as a warehouse entity;

[0236] One of the warehouse entities is used to store at least one of the access management context and the session management context;

[0237] The first warehouse entity includes the target warehouse entity and / or the source warehouse entity.

[0238] This application also provides an information transmission device applied to a source warehouse entity, including:

[0239] The fifth receiving unit is used to receive the context acquisition request message sent by the first entity;

[0240] The fifth sending unit is used to send a context acquisition response message to the first entity based on the context acquisition request message;

[0241] Wherein, the first entity includes: a target warehouse entity; the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message;

[0242] Alternatively, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition response message;

[0243] The context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message.

[0244] The mobility management context includes at least one of the following: access management context and session management context.

[0245] Optionally, the first warehouse entity is deployed in at least one of the following ways:

[0246] Add at least one network function as a warehouse entity to the control plane;

[0247] Extend the defined network functionality as a warehouse entity;

[0248] One of the warehouse entities is used to store at least one of the access management context and the session management context;

[0249] The first warehouse entity includes the target warehouse entity and / or the source warehouse entity.

[0250] This application also provides an information transmission device applied to a source access and mobility management entity, including:

[0251] The sixth sending unit is used to send the fourth context retrieval request message to the source repository entity;

[0252] The sixth receiving unit is used to receive the fourth context acquisition response message fed back by the source warehouse entity;

[0253] The seventh sending unit is used to obtain a response message based on the fourth context and send a handover resource allocation request message for at least one session to the target access and mobility management function entity.

[0254] The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message.

[0255] The mobility management context includes at least one of: access management context and session management context;

[0256] The resource allocation switching request message carries the mobility management context of at least one session.

[0257] Optionally, the source repository entity is deployed in at least one of the following ways:

[0258] Add at least one network function as a warehouse entity to the control plane;

[0259] Extend the defined network functionality as a warehouse entity;

[0260] One of the warehouse entities is used to store at least one of the access management context and the session management context.

[0261] This application also provides a processor-readable storage medium storing a computer program for causing the processor to perform the above-described method.

[0262] The beneficial effects of the above technical solution in this application are as follows:

[0263] In the above scheme, the information transmission method receives a session context creation request message sent by the target access and mobility management function entity; obtains a mobility management context for at least one session based on the session context creation request message; and performs mobility management based on the mobility management context. The mobility management context includes at least one of an access management context and a session management context. This method supports enabling a single mobility management operation across distributed network nodes to target at least one session, avoiding the limitation that each mobility management operation can only target one session. This improves data migration efficiency, reduces handover latency, and effectively solves the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes. Attached Figure Description

[0264] Figure 1 This is a schematic diagram of the wireless communication system architecture according to an embodiment of this application;

[0265] Figure 2 This is a schematic diagram of the distributed autonomous 6G system architecture according to an embodiment of this application;

[0266] Figure 3 This is a schematic flowchart of the information transmission method according to an embodiment of this application. Figure 1 ;

[0267] Figure 4 This is a schematic flowchart of the information transmission method according to an embodiment of this application. Figure 2 ;

[0268] Figure 5 This is a schematic flowchart of the information transmission method according to an embodiment of this application. Figure 3 ;

[0269] Figure 6 This is a schematic flowchart of the information transmission method according to an embodiment of this application. Figure 4 ;

[0270] Figure 7 This is a schematic flowchart of the information transmission method according to an embodiment of this application. Figure 5 ;

[0271] Figure 8 This is a schematic diagram illustrating the specific implementation process of the information transmission method in this application embodiment. Figure 1 ;

[0272] Figure 9 This is a schematic diagram illustrating the specific implementation process of the information transmission method in this application embodiment. Figure 2 ;

[0273] Figure 10 This is a schematic diagram illustrating the specific implementation process of the information transmission method in this application embodiment. Figure 3 ;

[0274] Figure 11 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 1 ;

[0275] Figure 12 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 2 ;

[0276] Figure 13 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 3 ;

[0277] Figure 14 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 4 ;

[0278] Figure 15 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 5 ;

[0279] Figure 16 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 1 ;

[0280] Figure 17 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 2 ;

[0281] Figure 18 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 3 ;

[0282] Figure 19 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 4 ;

[0283] Figure 20 This is a schematic diagram of the information transmission device structure according to an embodiment of this application. Figure 5 . Detailed Implementation

[0284] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0285] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0286] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0287] It should be noted that the technical solutions provided in this application are applicable to a variety of systems, especially 5G systems. For example, applicable systems may include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G system (5GS).

[0288] Figure 1 This diagram illustrates a block diagram of a wireless communication system to which embodiments of this application may be applied. The wireless communication system includes a terminal device (also referred to simply as a terminal) and a network device.

[0289] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0290] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in an access network that communicates with a wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0291] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0292] The following section will first introduce the content related to the solutions provided in the embodiments of this application.

[0293] Regarding the trend of 6G distributed architecture:

[0294] A key trend in 6G network development is the shift from centralized to distributed network architecture. While 5G and previous generations of network architectures were originally designed with centralized control, the design of 6G networks, driven by both business and technological advancements, needs to consider a distributed architecture, with control gradually evolving towards a distributed approach.

[0295] Specifically, 6G networks will address diverse scenarios and network performance requirements across air, space, land, and sea. A centralized network architecture cannot uniformly meet the needs of all scenarios. To address this challenge, the 6G network architecture needs to move beyond centralized control and gradually evolve towards a distributed architecture. This involves extending more network functions to the network edge and constructing distributed, homogeneous Small Cloud Units (SCUs) with different functional levels. Each SCU (corresponding to the aforementioned distributed network nodes) is self-contained and possesses complete control and data forwarding functions. Multiple SCUs can form autonomous micro-networks across domains based on business needs, providing targeted network services according to specific business scenarios, user scale, geographical environment, and other requirements. For details on the distributed autonomous 6G system architecture, please refer to [link to relevant documentation]. Figure 2 .

[0296] Based on the above, embodiments of this application provide an information transmission method, apparatus, and device to address the problems of low data migration efficiency and high handover latency in existing information transmission schemes for mobility management. The method, apparatus, and device are based on the same concept, and since the principles underlying the problems solved are similar, their implementations can be mutually referenced; repeated details will not be elaborated further.

[0297] The information transmission method provided in this application embodiment is applied to a target session management function entity, such as... Figure 3As shown, it includes:

[0298] Step 31: Receive a session context creation request message sent by the target access and mobility management function entity;

[0299] Step 32: Create a request message based on the session context to obtain the mobility management context of at least one session;

[0300] Step 33: Perform mobility management based on the mobility management context; wherein the mobility management context includes at least one of the access management context and the session management context.

[0301] The information transmission method provided in this application embodiment receives a session context creation request message sent by a target access and mobility management function entity; obtains a mobility management context for at least one session based on the session context creation request message; and performs mobility management based on the mobility management context. The mobility management context includes at least one of an access management context and a session management context. This method supports enabling a single mobility management operation across distributed network nodes to target at least one session, avoiding the limitation that each mobility management operation can only target one session. This improves data migration efficiency, reduces handover latency, and effectively solves the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0302] The step of obtaining the mobility management context of at least one session based on the session context creation request message includes: if the session context creation request message carries the mobility management context of at least one session, obtaining the mobility management context of the at least one session from the session context creation request message; if the session context creation request message does not carry the mobility management context of a session, sending a session context request message for at least one session to the target repository entity; and receiving a session context response message from the target repository entity, wherein the session context response message carries the mobility management context of the at least one session.

[0303] This ensures that at least one session's mobility management context is obtained.

[0304] In this embodiment of the application, the target repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein, a repository entity is used to store at least one of access management context and session management context.

[0305] This allows for diverse deployment of warehouse entities.

[0306] This application also provides an information transmission method, applied to a target access and mobility management function entity, such as... Figure 4 As shown, it includes:

[0307] Step 41: Receive a handover resource allocation request message for at least one session from the source access and mobility management function entity;

[0308] Step 42: Based on the switching resource allocation request message, send a session context creation request message to the target session management function entity corresponding to each session; wherein, the session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session; the mobility management context includes at least one of: access management context and session management context.

[0309] The resource allocation switching request message may carry at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session, but is not limited to this.

[0310] The information transmission method provided in this application embodiment receives a handover resource allocation request message for at least one session sent by a source access and mobility management function entity; according to the handover resource allocation request message, it sends a session context creation request message to the target session management function entity corresponding to each session; wherein, the session context creation request message carries a mobility management context for at least one session; or, the session context creation request message does not carry a session's mobility management context; the mobility management context includes at least one of an access management context and a session management context; it can support the realization that a single mobility management operation across distributed network nodes can be performed for at least one session, avoiding the situation where each mobility management operation can only be performed for one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0311] Wherein, if the session context creation request message carries at least one mobility management context of the session, before sending the session context creation request message to the target session management function entity corresponding to each session according to the handover resource allocation request message, the method further includes: sending a first context acquisition request message to the target repository entity according to the first information carried in the handover resource allocation request message; receiving a first context acquisition response message fed back by the target repository entity; wherein, the first information includes at least one of: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the first context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0312] This ensures accurate transmission of subsequent resource allocation handover request messages. The "session identifier information of at least one session" can be represented as a "session identifier list," allowing this solution to retrieve information from multiple sessions at once. Regarding the "node identifier information of the network node corresponding to at least one session," this addresses the following: if the network nodes are different, it may be necessary to carry the original network node's network node identifier to avoid the problem of indistinguishable session identifiers within different nodes; for example, session identifier 1 of network node 1 and session identifier 1 of network node 2. Where the resource allocation handover request message carries the access management context of the at least one session, the first context acquisition request message is not used to request the access management context of the at least one session.

[0313] In this embodiment of the application, the switching resource allocation request message carries at least one mobility management context of the session.

[0314] This allows for the implementation of solutions that no longer require obtaining the mobility management context.

[0315] Wherein, if the session context creation request message does not carry the session's mobility management context, before sending the session context creation request message to the target session management function entity corresponding to each session according to the switching resource allocation request message, the method further includes: sending a context acquisition notification (message) to the target repository entity according to the second information carried in the switching resource allocation request message; wherein, the second information includes at least one of: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition notification carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session.

[0316] This allows the target repository entity to accurately obtain the relevant context, which may include at least one of the access management context and the session management context.

[0317] Furthermore, the second information also includes: the access management context corresponding to the at least one session; the context acquisition notification is used to notify the target repository entity to acquire the session management context, and / or is not used to notify the target repository entity to acquire the access management context contained in the second information.

[0318] This allows the target repository entity to be directly notified of the access management context without the target repository entity needing to obtain it separately.

[0319] The target repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of access management context and session management context.

[0320] This allows for diverse deployment of warehouse entities.

[0321] This application also provides an information transmission method applied to a target warehouse entity, such as... Figure 5 As shown, it includes:

[0322] Step 51: Receive third information sent by the target access and mobility management function entity;

[0323] Step 52: Perform a context acquisition operation based on the third information; wherein the third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; or, the third information includes: a context acquisition notification; the context acquisition notification carries at least one of terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session.

[0324] The information transmission method provided in this application embodiment receives third information sent by a target access and mobility management function entity; performs a context acquisition operation based on the third information; wherein the third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; or, the third information includes: a context acquisition notification; the context acquisition notification carries at least one of terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; it can support the realization that a single mobility management operation across distributed network nodes can be performed on at least one session, avoiding the situation where each mobility management operation can only be performed on one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0325] Wherein, when the third information includes a first context acquisition request message, the context acquisition operation based on the third information includes: when the target repository entity does not store the mobility management context requested by the first context acquisition request message, sending a second context acquisition request message to the source repository entity based on the first context acquisition request message; receiving a second context acquisition response message from the source repository entity; wherein, the second context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the second context acquisition response message carries the mobility management context of at least one session requested by the second context acquisition request message; the mobility management context includes at least one of access management context and session management context.

[0326] This allows for accurate acquisition of the relevant context; wherein, the mobility management context requested by the first context acquisition request message may include: the mobility management context corresponding to at least one of the terminal identification information and session identification information carried in the first context acquisition request message; and / or, the mobility management context requested by the second context acquisition request message may include: the mobility management context corresponding to at least one of the terminal identification information and session identification information carried in the second context acquisition request message, but is not limited thereto.

[0327] Furthermore, after performing the context acquisition operation based on the third information, the method further includes: sending a first context acquisition response message to the target access and mobility management function entity based on the second context acquisition response message; wherein the first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0328] This allows the target access and mobility management function entities to accurately obtain the requested mobility management context.

[0329] The step of sending a second context retrieval request message to the source repository entity based on the first context retrieval request message includes: determining the relevant information of the corresponding source repository entity based on the information carried in the first context retrieval request message; and sending the second context retrieval request message to the source repository entity based on the relevant information of the source repository entity.

[0330] This allows the corresponding source repository entity (node) to be located based on some information in the request message, and then the required mobility management context can be accurately obtained from the corresponding source repository entity. The "information carried in the first context acquisition request message" may include: network node identifier, UE identifier, session management function identifier (which may also carry session management function identifier information (which corresponds to the source repository entity)), etc., but is not limited to this.

[0331] In this embodiment of the application, when the third information includes a context acquisition notification, the step of performing a context acquisition operation based on the third information includes: sending a third context acquisition request message to the source repository entity based on the context acquisition notification; and receiving a third context acquisition response message from the source repository entity; wherein the third context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the third context acquisition response message carries the mobility management context of at least one session requested by the third context acquisition request message; the mobility management context includes at least one of access management context and session management context.

[0332] This allows for accurate acquisition of the relevant context (mobility management context). The mobility management context requested by the third context acquisition request message may include, but is not limited to, the mobility management context corresponding to at least one of the terminal identification information and session identification information carried in the third context acquisition request message.

[0333] The first repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of an access management context and a session management context; the first repository entity includes a target repository entity and / or a source repository entity.

[0334] This allows for diverse deployment of warehouse entities.

[0335] This application also provides an information transmission method applied to a source warehouse entity, such as... Figure 6 As shown, it includes:

[0336] Step 61: Receive the context retrieval request message sent by the first entity;

[0337] Step 62: Based on the context retrieval request message, send a context retrieval response message to the first entity; wherein, the first entity includes: a target repository entity, the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message; or, the first entity includes: a source access and mobility management function entity, the context retrieval request message includes: a fourth context retrieval request message; the context retrieval response message includes: a fourth context retrieval response message; the context retrieval request message carries at least one of terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context retrieval response message carries the mobility management context of at least one session requested by the context retrieval request message; the mobility management context includes at least one of: access management context and session management context.

[0338] The information transmission method provided in this application embodiment receives a context acquisition request message sent by a first entity; and sends a context acquisition response message to the first entity according to the context acquisition request message; wherein, the first entity includes: a target repository entity, the context acquisition request message includes: a second context acquisition request message; the context acquisition response message includes: a second context acquisition response message; or, the context acquisition request message includes: a third context acquisition request message; the context acquisition response message includes: a third context acquisition response message; or, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition... The response message; the context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message; the mobility management context includes at least one of: access management context and session management context; it can support the implementation of mobility management across distributed network nodes for at least one session, avoiding the situation where each mobility management can only be performed for one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0339] The first repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of an access management context and a session management context; the first repository entity includes a target repository entity and / or a source repository entity.

[0340] This allows for diverse deployment of warehouse entities.

[0341] This application also provides an information transmission method, applied to source access and mobility management entities, such as... Figure 7 As shown, it includes:

[0342] Step 71: Send a fourth context retrieval request message to the source repository entity;

[0343] Step 72: Receive the fourth context acquisition response message from the source warehouse entity;

[0344] Step 73: Based on the fourth context acquisition response message, send a handover resource allocation request message for at least one session to the target access and mobility management function entity; wherein, the fourth context acquisition request message carries at least one of terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message; the mobility management context includes at least one of access management context and session management context; the handover resource allocation request message carries the mobility management context of at least one session.

[0345] The mobility management context requested by the fourth context acquisition request message may include, but is not limited to, the mobility management context corresponding to at least one of the terminal identification information and session identification information carried in the fourth context acquisition request message.

[0346] The information transmission method provided in this application embodiment sends a fourth context acquisition request message to a source repository entity; receives a fourth context acquisition response message from the source repository entity; and, based on the fourth context acquisition response message, sends a handover resource allocation request message for at least one session to a target access and mobility management function entity. The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session. The fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message. The mobility management context includes at least one of: access management context and session management context. The handover resource allocation request message carries the mobility management context of at least one session. This method enables mobility management across distributed network nodes to be performed on at least one session, avoiding the limitation that each mobility management operation can only be performed on one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0347] The source repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of access management context and session management context.

[0348] This allows for diverse deployment of warehouse entities.

[0349] The information transmission method provided in the embodiments of this application will be illustrated by examples below.

[0350] To address the aforementioned technical problems, this application provides an information transmission method, specifically a mobility management method based on a data warehouse across distributed node unit domains. This method involves uniformly storing user context (corresponding to the aforementioned mobility management context) in a data warehouse (corresponding to the aforementioned target warehouse entity and source warehouse entity). During mobile handover, it is not necessary to obtain relevant context data separately from different network functions at the session granularity; instead, context data from multiple sessions can be obtained at once. Regarding the setting of the warehouse entity, the following schemes may be included:

[0351] Option 1: Deploy a new network function, such as a context data warehouse, on the control plane of a distributed network node for access and mobility management functions and session management functions to store and retrieve data, which may include access management context and / or session management context, etc.

[0352] Option 2: Deploy two new network functions on the control plane, one for access and mobility management functions and the other for session management functions, to store and retrieve data. This data may include access management context and / or session management context.

[0353] Option 3: Expand existing network functions, such as the Unified Data Warehouse (UDR), to add the ability to store context data.

[0354] Option 4: Of the three options above, it is also possible to only store and retrieve the session management context, which is not limited here.

[0355] Schemes 1 and 2 above correspond to adding at least one network function as a warehouse entity in the control plane; Scheme 3 above corresponds to extending the already defined network function as a warehouse entity.

[0356] The following example illustrates this scheme using Scheme 1 as an example.

[0357] Example 1

[0358] like Figure 8 As shown, the cross-domain mobility management process may include the following steps:

[0359] Step 0: The terminal notifies the S-wireless device of the decision to switch.

[0360] Step 1: The S-Radio device sends a handover request to the S-Access and Mobility Management (function);

[0361] Step 2: S-Access and Mobility Management (Function) performs distributed (network) node selection & T-Access and Mobility Management function selection; the symbol "&" represents and; Step 2 may specifically include: completing the selection of target distributed network nodes to obtain target distributed network nodes; and performing target access and mobility management function selection within the obtained target distributed network nodes.

[0362] Step 3: The S (source) access and mobility management function requests the selected T (target) access and mobility management function to allocate handover resources. The request message carries the UE identifier (corresponding to the terminal identifier information mentioned above) and the session identifier list (corresponding to the session identifier information of at least one session mentioned above). The target access and mobility management function entity receives the handover resource allocation request message for at least one session sent by the source access and mobility management function entity.

[0363] The UE identifier and session identifier list may include network identifier information that assigns the identifier (node ​​identifier information corresponding to the network node corresponding to at least one of the above sessions), used to distinguish the identifier information assigned to different network nodes; this information may also be carried independently of the UE identifier and session identifier list.

[0364] The context data warehouse can store the access management context. (1) If the context data warehouse stores the access management context, step 3 can carry the access management context or not.

[0365] (2) If the context data warehouse does not store the access management context, step 3 carries the access management context;

[0366] This solution does not specify how to determine whether the context data warehouse stores a management context.

[0367] Step 4: The T-Access and Mobility Management function requests the required context from the T-Context Data Warehouse (corresponding to the target warehouse entity mentioned above); corresponding to the first information carried in the aforementioned Switching Resource Allocation Request Message, a first context retrieval request message is sent to the target warehouse entity.

[0368] If step 3 already includes the access management context, then it is not necessary to request this information from the T-context data warehouse; otherwise, it is requested.

[0369] Step 5: If the T-context data warehouse does not store the required context, the T-context data warehouse can request the relevant context from the corresponding S-context data warehouse (corresponding to the aforementioned source warehouse entity) based on the node identifier information contained in the request message. The request message carries a UE identifier and a session identifier list; corresponding to the third information sent by the aforementioned target access and mobility management function entity; and perform a context acquisition operation based on the third information. The third information includes: a first context acquisition request message. Performing the context acquisition operation based on the third information includes: if the target warehouse entity does not store the mobility management context requested by the first context acquisition request message, sending a second context acquisition request message to the source warehouse entity based on the first context acquisition request message; and receiving a second context acquisition response message from the source warehouse entity. Sending the second context acquisition request message to the source warehouse entity based on the first context acquisition request message includes: determining the relevant information of the corresponding source warehouse entity based on the information carried in the first context acquisition request message; and sending the second context acquisition request message to the (corresponding) source warehouse entity based on the relevant information of the source warehouse entity.

[0370] The node identification information contained in the request message can be the node identification information (corresponding to the node identification information of the network node where the S-Context Data Warehouse is located) contained in the "UE Identifier" or "Session Identifier List", or it can be the node identification information obtained by querying other network functions based on this information ("UE Identifier" or "Session Identifier List"). There is no limitation here.

[0371] Step 6: The S-context data warehouse replies with the relevant context to the T-context data warehouse, which can respond to the access management context and the session context of all requests; corresponding to the above-mentioned receiving the context acquisition request message sent by the first entity; according to the context acquisition request message, a context acquisition response message is sent to the first entity; wherein, the first entity includes: the target warehouse entity, the context acquisition request message includes: the second context acquisition request message; the context acquisition response message includes: the second context acquisition response message.

[0372] Step 7: The T-Context Data Warehouse sends a response context to the T-Access and Mobility Management Function; corresponding to the above-mentioned obtaining a response message based on the second context, a first context acquisition response message is sent to the target Access and Mobility Management Function entity.

[0373] Step 8: T-Access and Mobility Management selects the target session management function (for each session); specifically, T-Access and Mobility Management can select the corresponding T-Session Management function at the granularity of each session.

[0374] Step 9: The T-Access and Mobility Management function sends a request (message) to the selected T-Session Management function to create a session context, the request carrying the relevant session context (i.e., the session context of the corresponding session); corresponding to the above-mentioned handover resource allocation request message, a session context creation request message is sent to the target session management function entity corresponding to each session; the session context creation request message carries at least one mobility management context of the session.

[0375] Step 9 can also combine multiple messages sent to different sessions of the same session management function into a single message, with the message carrying multiple session identifiers and session contexts; however, it is not limited to this.

[0376] The operations related to the T-session management function involved in steps 10-19 below correspond to the target session management function entity performing mobility management according to the mobility management context.

[0377] Step 10: Select the user face for the T-session management function, that is, select the T-user face function for the session;

[0378] Step 11: Establish a user plane between the T-session management function and the selected T-user plane function;

[0379] Step 11a: Optionally, an inter-domain forwarding path is established between the T-user plane function and the S-user plane function;

[0380] Step 12: The T-Session Management function sends a session context creation response (message) back to the T-Access and Mobility Management (function);

[0381] Step 13: T-Access and Mobility Management (Function) conducts response monitoring;

[0382] Step 14: T-Access and Mobility Management sends a handover request (message) to the T-Radio Device;

[0383] Step 15: The T-radio device sends a handover request confirmation message (for successful or failed sessions) to the T-access and mobility management system.

[0384] Step 16: T-Access and Mobility Management requests an update to the session context from the T-Session Management function;

[0385] Step 17: The T-session management function requests or notifies the S-session management function to update the session context;

[0386] Step 17a: Optionally, an indirect forwarding path is established between the T-session management function and the T-user plane function; and / or, an indirect forwarding path is established between the S-session management function and the S-user plane function.

[0387] Step 18: The T-Session Management function sends a response (message) (update context) to the T-Access and Mobility Management system;

[0388] Step 19: T-Access and Mobility Management sends a response (message) to S-Access and Mobility Management (regarding the handover of resource allocation).

[0389] Example 2

[0390] Steps 3-9 in Example 1 can be adjusted to steps 3-7 below. The subsequent steps of step 7 below are the same as steps 10-19 in Example 1. Figure 9 (Not shown in the text), and will not be elaborated further. The main difference between this example and Example 1 is that before interacting with the T-access and mobility management function, the S-access and mobility management function first interacts with the S-context data warehouse to obtain the relevant context, and carries the relevant information in subsequent interactions with the T-access and mobility management function.

[0391] Specifically, such as Figure 9 As shown, the solution in this example includes the following steps:

[0392] Step 0: The terminal notifies the S-wireless device of the decision to switch.

[0393] Step 1: The S-Radio device sends a handover request to the S-Access and Mobility Management (function);

[0394] Step 2: S-Access and Mobility Management (Function) performs distributed (network) node selection & T-Access and Mobility Management function selection; Step 2 may specifically include: completing the selection of target distributed network nodes to obtain target distributed network nodes; and performing target access and mobility management function selection within the obtained target distributed network nodes.

[0395] Step 3: The S-Access and Mobility Management function requests context from the S-Context Data Warehouse, carrying a list of session identifiers in the message; the source warehouse entity receives the context retrieval request message sent by the first entity; wherein, the first entity includes: the source access and mobility management function entity, and the context retrieval request message includes: the fourth context retrieval request message.

[0396] Step 4: S-Context Data Warehouse Response. Specifically, the S-Access and Mobility Management Function responds with the access management context and the session context of all requests; corresponding to the aforementioned source warehouse entity obtaining the context request message, it sends a context retrieval response message to the first entity; wherein, the first entity includes: the source access and mobility management function entity, and the context retrieval response message includes: the fourth context retrieval response message.

[0397] Step 5: The S-Access and Mobility Management (SAM) requests the allocation of handover resources from the selected T-Access and Mobility Management (TAM). The message carries the access management context and session management context, and may specifically carry all contexts. Corresponding to the above-mentioned response message obtained based on the fourth context, a handover resource allocation request message for at least one session is sent to the target SAM entity. The handover resource allocation request message may carry the mobility management context of at least one of the sessions.

[0398] Step 6: T-Access and Mobility Management selects the target session management function (for each session); specifically, T-Access and Mobility Management can select the corresponding T-Session Management function at the granularity of each session.

[0399] Step 7: The T-Access and Mobility Management function sends a request (message) to the selected T-Session Management function to create a session context, carrying the relevant session context (i.e., the session context of the corresponding session). Corresponding to the above-mentioned handover resource allocation request message, a session context creation request message is sent to the target session management function entity corresponding to each session; the session context creation request message carries at least one mobility management context of the session.

[0400] Example 3

[0401] Step 3-10 in Example 1 can be adjusted to step 3-11 below. The subsequent operations in step 11 below are the same as steps 11-19 in Example 1. Figure 10 (Not shown in the text), and will not be elaborated further. The main difference between this example and Example 1 is that the T-Access and Mobility Management function sends a request (message) to the T-Session Management function to create a session context. The request no longer carries the relevant session context (i.e., the session context of the corresponding session). Instead, the T-Session Management function requests and obtains it from the T-Context Data Warehouse.

[0402] Specifically, such as Figure 10 As shown, the solution in this example includes the following steps:

[0403] Step 0: The terminal notifies the S-wireless device of the decision to switch.

[0404] Step 1: The S-Radio device sends a handover request to the S-Access and Mobility Management (function);

[0405] Step 2: S-Access and Mobility Management (Function) performs distributed (network) node selection & T-Access and Mobility Management function selection; Step 2 may specifically include: completing the selection of target distributed network nodes to obtain target distributed network nodes; and performing target access and mobility management function selection within the obtained target distributed network nodes.

[0406] Step 3: The S-Access and Mobility Management function requests the allocation of handover resources from the selected T-Access and Mobility Management function, carrying the access management context and session identifier list in the request message; the target repository entity receives the handover resource allocation request message sent by the source access and mobility management function entity for at least one session.

[0407] Step 4: The T-Access and Mobility Management function notifies the T-Context Data Warehouse to obtain the relevant session context (session management context) and sends a list of session identifiers in the notification; corresponding to the second information carried in the aforementioned switching resource allocation request message, a context acquisition notification (message) is sent to the target warehouse entity.

[0408] Steps 5 and 6: The T-context data warehouse obtains the session context from the S-context data warehouse; specifically, the T-context data warehouse requests the S-context data warehouse to obtain the context (carrying the UE identifier & session identifier list), and the S-context data warehouse responds to the T-context data warehouse with the access management context and all requested session contexts; corresponding to the above-mentioned target warehouse entity receiving the third information sent by the target access and mobility management function entity; performing the context acquisition operation according to the third information; wherein, the third information includes: context acquisition notification; the context acquisition operation according to the third information includes: sending a third context acquisition request message to the source warehouse entity according to the context acquisition notification; receiving a third context acquisition response message fed back by the source warehouse entity. The source warehouse entity receives the context acquisition request message sent by the first entity; sending a context acquisition response message to the first entity according to the context acquisition request message; wherein, the first entity includes: the target warehouse entity, the context acquisition request message includes: a third context acquisition request message; the context acquisition response message includes: a third context acquisition response message.

[0409] Steps 7 and 8: The T-Access and Mobility Management (TAM) function selects a T-Session Management (TSM) function and sends a Session Context Creation Request (message). Specifically, the TAM function selects a target Session Management (SSM) function (for each session). The TAM function can select the corresponding TSM function at the granularity of each session. The TAM function sends a Session Context Creation Request (message) to the selected TSM function, but the request does not carry the relevant session context (i.e., the session context of the corresponding session). Corresponding to the above-mentioned Handover Resource Allocation Request message, a Session Context Creation Request message is sent to the target Session Management (SSM) entity corresponding to each session; the Session Context Creation Request message does not carry the session's mobility management context.

[0410] Steps 9 and 10: The T-Session Management function retrieves the session context from the T-Context Data Warehouse; specifically, the T-Session Management function requests the session context from the T-Context Data Warehouse, and the T-Context Data Warehouse responds with the session context to the T-Session Management function. Corresponding to the situation described above where the session context creation request message does not carry the session's mobility management context, a session context request message for at least one session is sent to the target warehouse entity; a session context response message is received from the target warehouse entity, the session context response message carrying the mobility management context of the at least one session.

[0411] Step 11: Select the user face for the T-session management function, that is, select the T-user face function for the session.

[0412] It should be noted that the related content among the above examples can be referred to each other, and the repeated parts will not be repeated.

[0413] Therefore, this solution relates to a cross-domain mobility management method based on a data warehouse, which enables the unified storage of user context in the data warehouse. During mobile handover, context data from multiple sessions can be retrieved from this context data warehouse. Specifically:

[0414] 1. Regarding the deployment of the data warehouse, it can be done by deploying a new network function in the control plane for access and mobility management functions and session management functions to store and retrieve data, which may include access management context and / or session management context, etc.; or by deploying two new network functions in the control plane for access and mobility management functions and session management functions respectively to store and retrieve data, which may include access management context and / or session management context; or by extending existing network functions, such as the Unified Data Warehouse (UDR), to add the ability to store context data; among these three methods, it is also possible to only store and retrieve session management context, which is not limited here.

[0415] 2. When the S-Access and Mobility Management function requests the allocation of handover resources from the T-Access and Mobility Management function, the access management context can be carried in the message or only the UE identifier can be carried. The T-Access and Mobility Management function then obtains the information from the T-Context Data Warehouse.

[0416] 3. Regarding the session context, it can be obtained from the S-Context Data Warehouse by the S-Access and Mobility Management functions, or it can be obtained from the T-Context Data Warehouse by the T-Access and Mobility Management functions, or it can be obtained from the T-Context Data Warehouse by the T-Session Management functions. No limitation is made here.

[0417] In summary, this solution can be implemented as a cross-domain (i.e., cross-network node) mobility management method based on a data warehouse, which can improve data migration efficiency, save signaling messages, and reduce handover latency. In particular, it is well-suited for mobility management problems in scenarios where UEs move rapidly.

[0418] This application also provides an information transmission device, which is a target session management function entity, such as... Figure 11 As shown, it includes a memory 111, a transceiver 112, and a processor 113:

[0419] Memory 111 is used to store computer programs; transceiver 112 is used to send and receive data under the control of processor 113; processor 113 is used to read the computer program in memory 111 and perform the following operations:

[0420] The transceiver 112 receives a session context creation request message sent by the target access and mobility management function entity.

[0421] A request message is created based on the session context to obtain the mobility management context of at least one session;

[0422] Mobility management is performed based on the mobility management context.

[0423] The mobility management context includes at least one of an access management context and a session management context.

[0424] The information transmission device provided in this application embodiment receives a session context creation request message sent by a target access and mobility management function entity; obtains a mobility management context for at least one session based on the session context creation request message; and performs mobility management based on the mobility management context. The mobility management context includes at least one of an access management context and a session management context. This enables a single mobility management operation across distributed network nodes to be performed on at least one session, avoiding the limitation that each mobility management operation can only be performed on one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0425] Specifically, transceiver 112 is used to receive and send data under the control of processor 113.

[0426] Among them, Figure 11 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 113) and memory (memory 111). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 112 may be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 113 is responsible for managing the bus architecture and general processing, and the memory 111 may store data used by the processor 113 during operation.

[0427] The processor 113 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0428] The step of obtaining the mobility management context of at least one session based on the session context creation request message includes: if the session context creation request message carries the mobility management context of at least one session, obtaining the mobility management context of the at least one session from the session context creation request message; if the session context creation request message does not carry the mobility management context of a session, sending a session context request message for at least one session to the target warehouse entity through the transceiver; and receiving a session context response message from the target warehouse entity through the transceiver, the session context response message carrying the mobility management context of the at least one session.

[0429] In this embodiment of the application, the target repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein, a repository entity is used to store at least one of access management context and session management context.

[0430] It should be noted that the device provided in this application embodiment can implement all the method steps implemented by the method embodiment on the target session management function entity side, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0431] This application also provides an information transmission device, which is a target access and mobility management function entity, such as... Figure 12 As shown, it includes a memory 121, a transceiver 122, and a processor 123:

[0432] Memory 121 is used to store computer programs; transceiver 122 is used to send and receive data under the control of processor 123; processor 123 is used to read the computer program in memory 121 and perform the following operations:

[0433] The transceiver 122 receives a handover resource allocation request message for at least one session sent by the source access and mobility management function entity.

[0434] The transceiver 122 sends a session context creation request message to the target session management function entity corresponding to each session according to the switching resource allocation request message.

[0435] The session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session.

[0436] The mobility management context includes at least one of the following: access management context and session management context.

[0437] The information transmission device provided in this application embodiment receives a handover resource allocation request message for at least one session sent by a source access and mobility management function entity; according to the handover resource allocation request message, it sends a session context creation request message to the target session management function entity corresponding to each session; wherein, the session context creation request message carries a mobility management context for at least one session; or, the session context creation request message does not carry a session mobility management context; the mobility management context includes at least one of an access management context and a session management context; it can support the realization that a single mobility management operation across distributed network nodes can be performed for at least one session, avoiding the situation where each mobility management operation can only be performed for one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing information transmission schemes for mobility management.

[0438] Specifically, transceiver 122 is used to receive and send data under the control of processor 123.

[0439] Among them, Figure 12In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 123) and memory (memory 121). The bus architecture may also link various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 122 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 123 is responsible for managing the bus architecture and general processing, and the memory 121 may store data used by the processor 123 during operation.

[0440] The processor 123 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0441] Furthermore, the operation further includes: when the session context creation request message carries at least one mobility management context of the session, before sending the session context creation request message to the target session management function entity corresponding to each session according to the handover resource allocation request message, sending a first context acquisition request message to the target repository entity through the transceiver according to the first information carried in the handover resource allocation request message; receiving a first context acquisition response message fed back by the target repository entity through the transceiver; wherein, the first information includes at least one of: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the first context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0442] The resource allocation switching request message carries at least one mobility management context of the session.

[0443] Furthermore, the operation further includes: if the session context creation request message does not carry the session's mobility management context, before sending the session context creation request message to the target session management function entity corresponding to each session according to the switching resource allocation request message, the transceiver sends a context acquisition notification to the target repository entity according to the second information carried in the switching resource allocation request message; wherein, the second information includes at least one of: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition notification carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session.

[0444] In this embodiment of the application, the second information further includes: the access management context corresponding to the at least one session; the context acquisition notification is used to notify the target repository entity to acquire the session management context, and / or is not used to notify the target repository entity to acquire the access management context contained in the second information.

[0445] The target repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of access management context and session management context.

[0446] It should be noted that the device provided in this application embodiment can implement all the method steps implemented in the method embodiment of the target access and mobility management function entity, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0447] This application also provides an information transmission device, wherein the information transmission device is a target warehouse entity, such as... Figure 13 As shown, it includes a memory 131, a transceiver 132, and a processor 133:

[0448] Memory 131 is used to store computer programs; transceiver 132 is used to send and receive data under the control of processor 133; processor 133 is used to read the computer program in memory 131 and perform the following operations:

[0449] The transceiver 132 receives third information sent by the target access and mobility management function entity.

[0450] Based on the third information, a context retrieval operation is performed;

[0451] The third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session;

[0452] Alternatively, the third information may include: a context acquisition notification; the context acquisition notification carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to the session.

[0453] The information transmission device provided in this application embodiment receives third information sent by a target access and mobility management function entity; and performs a context acquisition operation based on the third information; wherein the third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; or, the third information includes: a context acquisition notification; the context acquisition notification carries at least one of terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; it can support the realization that a single mobility management operation across distributed network nodes can be performed on at least one session, avoiding the situation where each mobility management operation can only be performed on one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing information transmission schemes for mobility management.

[0454] Specifically, transceiver 132 is used to receive and send data under the control of processor 133.

[0455] Among them, Figure 13 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 133) and memory (memory 131). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 132 can be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 133 is responsible for managing the bus architecture and general processing, and the memory 131 can store data used by the processor 133 during operation.

[0456] The processor 133 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0457] Wherein, when the third information includes a first context acquisition request message, the context acquisition operation based on the third information includes: when the target repository entity does not store the mobility management context requested by the first context acquisition request message, sending a second context acquisition request message to the source repository entity via the transceiver based on the first context acquisition request message; receiving a second context acquisition response message from the source repository entity via the transceiver; wherein the second context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the second context acquisition response message carries the mobility management context of at least one session requested by the second context acquisition request message; the mobility management context includes at least one of access management context and session management context.

[0458] Furthermore, the operation also includes: after performing a context acquisition operation based on the third information, sending a first context acquisition response message to the target access and mobility management function entity through the transceiver based on the second context acquisition response message; wherein the first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0459] The step of sending a second context retrieval request message to the source repository entity based on the first context retrieval request message includes: determining the relevant information of the corresponding source repository entity based on the information carried in the first context retrieval request message; and sending the second context retrieval request message to the source repository entity based on the relevant information of the source repository entity.

[0460] In this embodiment of the application, when the third information includes a context acquisition notification, the context acquisition operation based on the third information includes: sending a third context acquisition request message to the source repository entity via the transceiver according to the context acquisition notification; receiving a third context acquisition response message from the source repository entity via the transceiver; wherein the third context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the third context acquisition response message carries the mobility management context of at least one session requested by the third context acquisition request message; the mobility management context includes at least one of access management context and session management context.

[0461] The first repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of an access management context and a session management context; the first repository entity includes a target repository entity and / or a source repository entity.

[0462] It should be noted that the device provided in this application embodiment can implement all the method steps implemented in the above-mentioned method embodiment on the target warehouse entity side, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0463] This application also provides an information transmission device, which is a source warehouse entity, such as... Figure 14 As shown, it includes a memory 141, a transceiver 142, and a processor 143:

[0464] Memory 141 is used to store computer programs; transceiver 142 is used to send and receive data under the control of processor 143; processor 143 is used to read the computer program in memory 141 and perform the following operations:

[0465] The transceiver 142 receives a context acquisition request message sent by the first entity.

[0466] The transceiver 142 sends a context retrieval response message to the first entity based on the context retrieval request message.

[0467] Wherein, the first entity includes: a target warehouse entity; the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message;

[0468] Alternatively, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition response message;

[0469] The context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message.

[0470] The mobility management context includes at least one of the following: access management context and session management context.

[0471] The information transmission device provided in this application embodiment receives a context acquisition request message sent by a first entity; and sends a context acquisition response message to the first entity according to the context acquisition request message; wherein, the first entity includes: a target warehouse entity, the context acquisition request message includes: a second context acquisition request message; the context acquisition response message includes: a second context acquisition response message; or, the context acquisition request message includes: a third context acquisition request message; the context acquisition response message includes: a third context acquisition response message; or, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition... The response message; the context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message; the mobility management context includes at least one of: access management context and session management context; it can support the implementation of mobility management across distributed network nodes for at least one session, avoiding the situation where each mobility management can only be performed for one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0472] Specifically, transceiver 142 is used to receive and send data under the control of processor 143.

[0473] Among them, Figure 14 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 143) and memory (memory 141). The bus architecture may also link together various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 142 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 143 is responsible for managing the bus architecture and general processing, and the memory 141 may store data used by the processor 143 during operation.

[0474] The processor 143 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0475] The first repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of an access management context and a session management context; the first repository entity includes a target repository entity and / or a source repository entity.

[0476] It should be noted that the device provided in this application embodiment can implement all the method steps implemented in the above-mentioned source warehouse entity side method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0477] This application also provides an information transmission device, which is a source access and mobility management entity, such as... Figure 15 As shown, it includes a memory 151, a transceiver 152, and a processor 153:

[0478] Memory 151 is used to store computer programs; transceiver 152 is used to send and receive data under the control of processor 153; processor 153 is used to read the computer program in memory 151 and perform the following operations:

[0479] The transceiver 152 sends a fourth context retrieval request message to the source warehouse entity.

[0480] The transceiver 152 receives the fourth context acquisition response message fed back by the source warehouse entity.

[0481] The transceiver 152 obtains a response message based on the fourth context and sends a handover resource allocation request message for at least one session to the target access and mobility management function entity.

[0482] The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message.

[0483] The mobility management context includes at least one of: access management context and session management context;

[0484] The resource allocation switching request message carries the mobility management context of at least one session.

[0485] The information transmission device provided in this application embodiment sends a fourth context acquisition request message to a source repository entity; receives a fourth context acquisition response message from the source repository entity; and, based on the fourth context acquisition response message, sends a handover resource allocation request message for at least one session to a target access and mobility management function entity. The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session. The fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message. The mobility management context includes at least one of: access management context and session management context. The handover resource allocation request message carries the mobility management context of at least one session. This enables a single mobility management operation across distributed network nodes to be performed on at least one session, avoiding the limitation that each mobility management operation can only be performed on one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0486] Specifically, transceiver 152 is used to receive and send data under the control of processor 153.

[0487] Among them, Figure 15 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 153) and memory (memory 151). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 152 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 153 is responsible for managing the bus architecture and general processing, and the memory 151 may store data used by the processor 153 during operation.

[0488] The processor 153 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0489] The source repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of access management context and session management context.

[0490] It should be noted that the device provided in this application embodiment can implement all the method steps implemented in the above-mentioned source access and mobility management entity side method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0491] This application also provides an information transmission device applied to a target session management function entity, such as... Figure 16 As shown, it includes:

[0492] The first receiving unit 161 is used to receive a session context creation request message sent by the target access and mobility management function entity;

[0493] The first processing unit 162 is configured to create a request message based on the session context to obtain the mobility management context of at least one session;

[0494] The second processing unit 163 is used to perform mobility management according to the mobility management context;

[0495] The mobility management context includes at least one of an access management context and a session management context.

[0496] The information transmission device provided in this application embodiment receives a session context creation request message sent by a target access and mobility management function entity; obtains a mobility management context for at least one session based on the session context creation request message; and performs mobility management based on the mobility management context. The mobility management context includes at least one of an access management context and a session management context. This device supports enabling a single mobility management operation across distributed network nodes to target at least one session, avoiding the limitation that each mobility management operation can only target one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0497] The step of obtaining the mobility management context of at least one session based on the session context creation request message includes: if the session context creation request message carries the mobility management context of at least one session, obtaining the mobility management context of the at least one session from the session context creation request message; if the session context creation request message does not carry the mobility management context of a session, sending a session context request message for at least one session to the target repository entity; and receiving a session context response message from the target repository entity, wherein the session context response message carries the mobility management context of the at least one session.

[0498] In this embodiment of the application, the target repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein, a repository entity is used to store at least one of access management context and session management context.

[0499] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented by the method embodiment on the target session management function entity side, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0500] This application also provides an information transmission device applied to a target access and mobility management function entity, such as... Figure 17 As shown, it includes:

[0501] The second receiving unit 171 is used to receive a handover resource allocation request message for at least one session sent by the source access and mobility management function entity.

[0502] The first sending unit 172 is used to send a session context creation request message to the target session management function entity corresponding to each session according to the switching resource allocation request message;

[0503] The session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session.

[0504] The mobility management context includes at least one of the following: access management context and session management context.

[0505] The information transmission device provided in this application embodiment receives a handover resource allocation request message for at least one session sent by a source access and mobility management function entity; according to the handover resource allocation request message, it sends a session context creation request message to the target session management function entity corresponding to each session; wherein, the session context creation request message carries a mobility management context for at least one session; or, the session context creation request message does not carry a session mobility management context; the mobility management context includes at least one of an access management context and a session management context; it can support the realization that a single mobility management operation across distributed network nodes can be performed on at least one session, avoiding the situation where each mobility management operation can only be performed on one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing information transmission schemes for mobility management.

[0506] Furthermore, the information transmission device further includes: a second sending unit, configured to, when the session context creation request message carries at least one mobility management context of the session, send a first context acquisition request message to a target repository entity based on first information carried in the handover resource allocation request message before sending the session context creation request message to the target session management function entity corresponding to each session according to the handover resource allocation request message; a third receiving unit, configured to receive a first context acquisition response message fed back by the target repository entity; wherein, the first information includes at least one of: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the first context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0507] The resource allocation switching request message carries at least one mobility management context of the session.

[0508] Furthermore, the information transmission device further includes: a third sending unit, configured to, when the session context creation request message does not carry the session's mobility management context, before sending the session context creation request message to the target session management function entity corresponding to each session according to the handover resource allocation request message, send a context acquisition notification to the target repository entity according to the second information carried in the handover resource allocation request message; wherein, the second information includes at least one of: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition notification carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session.

[0509] In this embodiment of the application, the second information further includes: the access management context corresponding to the at least one session; the context acquisition notification is used to notify the target repository entity to acquire the session management context, and / or is not used to notify the target repository entity to acquire the access management context contained in the second information.

[0510] The target repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of access management context and session management context.

[0511] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the method embodiment of the target access and mobility management function entity, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0512] This application also provides an information transmission device applied to a target warehouse entity, such as... Figure 18 As shown, it includes:

[0513] The fourth receiving unit 181 is used to receive third information sent by the target access and mobility management function entity;

[0514] The third processing unit 182 is used to perform a context acquisition operation based on the third information;

[0515] The third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session;

[0516] Alternatively, the third information may include: a context acquisition notification; the context acquisition notification carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to the session.

[0517] The information transmission device provided in this application embodiment receives third information sent by a target access and mobility management function entity; and performs a context acquisition operation based on the third information; wherein the third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; or, the third information includes: a context acquisition notification; the context acquisition notification carries at least one of terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; it can support the realization that a single mobility management operation across distributed network nodes can be performed on at least one session, avoiding the situation where each mobility management operation can only be performed on one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing information transmission schemes for mobility management.

[0518] Wherein, when the third information includes a first context acquisition request message, the context acquisition operation based on the third information includes: when the target repository entity does not store the mobility management context requested by the first context acquisition request message, sending a second context acquisition request message to the source repository entity based on the first context acquisition request message; receiving a second context acquisition response message from the source repository entity; wherein, the second context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the second context acquisition response message carries the mobility management context of at least one session requested by the second context acquisition request message; the mobility management context includes at least one of access management context and session management context.

[0519] Furthermore, the information transmission device further includes: a fourth sending unit, configured to send a first context acquisition response message to the target access and mobility management function entity based on the second context acquisition response message after performing a context acquisition operation based on the third information; wherein the first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

[0520] The step of sending a second context retrieval request message to the source repository entity based on the first context retrieval request message includes: determining the relevant information of the corresponding source repository entity based on the information carried in the first context retrieval request message; and sending the second context retrieval request message to the source repository entity based on the relevant information of the source repository entity.

[0521] In this embodiment of the application, when the third information includes a context acquisition notification, the step of performing a context acquisition operation based on the third information includes: sending a third context acquisition request message to the source repository entity based on the context acquisition notification; and receiving a third context acquisition response message from the source repository entity; wherein the third context acquisition request message carries at least one of the terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the third context acquisition response message carries the mobility management context of at least one session requested by the third context acquisition request message; the mobility management context includes at least one of access management context and session management context.

[0522] The first repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of an access management context and a session management context; the first repository entity includes a target repository entity and / or a source repository entity.

[0523] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the method embodiment on the target warehouse entity side, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0524] This application also provides an information transmission device applied to a source warehouse entity, such as... Figure 19 As shown, it includes:

[0525] The fifth receiving unit 191 is used to receive the context acquisition request message sent by the first entity;

[0526] The fifth sending unit 192 is used to send a context acquisition response message to the first entity based on the context acquisition request message;

[0527] Wherein, the first entity includes: a target warehouse entity; the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message;

[0528] Alternatively, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition response message;

[0529] The context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message.

[0530] The mobility management context includes at least one of the following: access management context and session management context.

[0531] The information transmission device provided in this application embodiment receives a context acquisition request message sent by a first entity; and sends a context acquisition response message to the first entity according to the context acquisition request message; wherein, the first entity includes: a target warehouse entity, the context acquisition request message includes: a second context acquisition request message; the context acquisition response message includes: a second context acquisition response message; or, the context acquisition request message includes: a third context acquisition request message; the context acquisition response message includes: a third context acquisition response message; or, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition... The response message; the context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message; the mobility management context includes at least one of: access management context and session management context; it can support the implementation of mobility management across distributed network nodes for at least one session, avoiding the situation where each mobility management can only be performed for one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0532] The first repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of an access management context and a session management context; the first repository entity includes a target repository entity and / or a source repository entity.

[0533] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above-mentioned source warehouse entity side method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0534] This application also provides an information transmission device applied to source access and mobility management entities, such as... Figure 20 As shown, it includes:

[0535] The sixth sending unit 201 is used to send a fourth context retrieval request message to the source repository entity;

[0536] The sixth receiving unit 202 is used to receive the fourth context acquisition response message fed back by the source warehouse entity;

[0537] The seventh sending unit 203 is used to obtain a response message based on the fourth context and send a handover resource allocation request message for at least one session to the target access and mobility management function entity;

[0538] The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message.

[0539] The mobility management context includes at least one of: access management context and session management context;

[0540] The resource allocation switching request message carries the mobility management context of at least one session.

[0541] The information transmission device provided in this application embodiment sends a fourth context acquisition request message to a source repository entity; receives a fourth context acquisition response message from the source repository entity; and, based on the fourth context acquisition response message, sends a handover resource allocation request message for at least one session to a target access and mobility management function entity. The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session. The fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message. The mobility management context includes at least one of: access management context and session management context. The handover resource allocation request message carries the mobility management context of at least one session. This enables a single mobility management operation across distributed network nodes to be performed on at least one session, avoiding the limitation that each mobility management operation can only be performed on one session, thereby improving data migration efficiency, reducing handover latency, and effectively solving the problems of low data migration efficiency and high handover latency in existing mobility management information transmission schemes.

[0542] The source repository entity is deployed in at least one of the following ways: adding at least one network function as a repository entity to the control plane; extending an existing network function as a repository entity; wherein a repository entity is used to store at least one of access management context and session management context.

[0543] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above-mentioned source access and mobility management entity side method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0544] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0545] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0546] This application also provides a processor-readable storage medium storing a computer program for causing the processor to perform the methods described above for the target session management function entity side, target access and mobility management function entity side, target warehouse entity side, source warehouse entity side, or source access and mobility management entity side.

[0547] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0548] The implementation embodiments of the methods described above for the target session management function entity side, target access and mobility management function entity side, target repository entity side, source repository entity side, or source access and mobility management entity side are all applicable to the embodiments of the processor-readable storage medium and can achieve the same technical effect.

[0549] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0550] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0551] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0552] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0553] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. An information transmission method, applied to a target session management function entity, characterized in that, include: Receive a session context creation request message sent by the target access and mobility management function entity; A request message is created based on the session context to obtain the mobility management context of at least one session; Mobility management is performed based on the mobility management context. The mobility management context includes at least one of an access management context and a session management context.

2. The information transmission method according to claim 1, characterized in that, The step of creating a request message based on the session context to obtain the mobility management context of at least one session includes: If the session context creation request message carries the mobility management context of at least one session, the mobility management context of the at least one session is obtained from the session context creation request message. If the session context creation request message does not carry the session's mobility management context, a session context request message for at least one session is sent to the target repository entity; a session context response message is received from the target repository entity, the session context response message carrying the mobility management context of the at least one session.

3. The information transmission method according to claim 2, characterized in that, The target warehouse entity is deployed in at least one of the following ways: Add at least one network function as a warehouse entity to the control plane; Extend the defined network functionality as a warehouse entity; One of the warehouse entities is used to store at least one of the access management context and the session management context.

4. An information transmission method, applied to a target access and mobility management functional entity, characterized in that, include: Receive a handover resource allocation request message for at least one session from the source access and mobility management function entity; Based on the resource allocation switching request message, a session context creation request message is sent to the target session management function entity corresponding to each session; The session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session. The mobility management context includes at least one of the following: access management context and session management context.

5. The information transmission method according to claim 4, characterized in that, When the session context creation request message carries a mobility management context for at least one of the sessions, before sending the session context creation request message to the target session management function entity corresponding to each of the sessions according to the handover resource allocation request message, the method further includes: Based on the first information carried in the resource allocation switching request message, a first context retrieval request message is sent to the target warehouse entity; Receive the first context acquisition response message from the target warehouse entity; The first information includes at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session. The first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; The first context acquisition response message carries at least one mobility management context of the session requested by the first context acquisition request message.

6. The information transmission method according to claim 4 or 5, characterized in that, The switch resource allocation request message carries at least one mobility management context of the session.

7. The information transmission method according to claim 4, characterized in that, If the session context creation request message does not carry the session's mobility management context, before sending the session context creation request message to the target session management function entity corresponding to each session according to the handover resource allocation request message, the method further includes: Based on the second information carried in the resource allocation switching request message, a context acquisition notification is sent to the target warehouse entity; The second information includes at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of the network node corresponding to at least one session; The context acquisition notification carries at least one of the following: the terminal identification information, the session identification information of at least one session, and the node identification information of the network node corresponding to at least one session.

8. The information transmission method according to claim 7, characterized in that, The second information also includes: the access management context corresponding to the at least one session; the context acquisition notification is used to notify the target repository entity to acquire the session management context.

9. The information transmission method according to claim 5 or 7, characterized in that, The target warehouse entity is deployed in at least one of the following ways: Add at least one network function as a warehouse entity to the control plane; Extend the defined network functionality as a warehouse entity; One of the warehouse entities is used to store at least one of the access management context and the session management context.

10. An information transmission method applied to a target warehouse entity, characterized in that, include: Receive third information sent by the target access and mobility management function entity; Based on the third information, a context retrieval operation is performed; The third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; Alternatively, the third information may include: a context acquisition notification; the context acquisition notification carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to the session.

11. The information transmission method according to claim 10, characterized in that, When the third information includes a first context acquisition request message, the context acquisition operation based on the third information includes: If the target warehouse entity does not store the mobility management context requested by the first context acquisition request message, a second context acquisition request message is sent to the source warehouse entity according to the first context acquisition request message; Receive the second context acquisition response message from the source repository entity; The second context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session. The second context acquisition response message carries the mobility management context of at least one session requested by the second context acquisition request message; the mobility management context includes at least one of an access management context and a session management context.

12. The information transmission method according to claim 11, characterized in that, After performing the context acquisition operation based on the third information, the process further includes: Based on the second context, obtain the response message and send the first context to the target access and mobility management function entity; The first context acquisition response message carries the mobility management context of at least one session requested by the first context acquisition request message.

13. The information transmission method according to claim 11, characterized in that, The step of sending a second context retrieval request message to the source repository entity based on the first context retrieval request message includes: Based on the information carried in the request message obtained from the first context, the relevant information of the corresponding source repository entity is determined; Based on the relevant information of the source repository entity, a second context retrieval request message is sent to the source repository entity.

14. The information transmission method according to claim 10, characterized in that, When the third information includes a context acquisition notification, the context acquisition operation based on the third information includes: Based on the context, a notification is obtained, and a third context retrieval request message is sent to the source repository entity. Receive the third context acquisition response message fed back by the source warehouse entity; The third context acquisition request message carries at least one of the following: the terminal identification information, the session identification information of at least one session, and the node identification information of the network node corresponding to at least one session. The third context acquisition response message carries the mobility management context of at least one session requested by the third context acquisition request message; The mobility management context includes at least one of the following: access management context and session management context.

15. The information transmission method according to any one of claims 10 to 14, characterized in that, The first warehouse entity is deployed in at least one of the following ways: Add at least one network function as a warehouse entity to the control plane; Extend the defined network functionality as a warehouse entity; One of the warehouse entities is used to store at least one of the access management context and the session management context; The first warehouse entity includes the target warehouse entity and / or the source warehouse entity.

16. An information transmission method applied to a source warehouse entity, characterized in that, include: Receive the context retrieval request message sent by the first entity; Based on the context, obtain the request message and send a context retrieval response message to the first entity; Wherein, the first entity includes: a target warehouse entity; the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message; Alternatively, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition response message; The context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message. The mobility management context includes at least one of the following: access management context and session management context.

17. The information transmission method according to claim 16, characterized in that, The first warehouse entity is deployed in at least one of the following ways: Add at least one network function as a warehouse entity to the control plane; Extend the defined network functionality as a warehouse entity; One of the warehouse entities is used to store at least one of the access management context and the session management context; The first warehouse entity includes the target warehouse entity and / or the source warehouse entity.

18. An information transmission method, applied to a source access and mobility management entity, characterized in that, include: Send a fourth context retrieval request message to the source repository entity; Receive the fourth context acquisition response message fed back by the source warehouse entity; Based on the fourth context, obtain the response message and send a handover resource allocation request message for at least one session to the target access and mobility management function entity; The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message. The mobility management context includes at least one of: access management context and session management context; The resource allocation switching request message carries the mobility management context of at least one session.

19. The information transmission method according to claim 18, characterized in that, The source repository entity is deployed in at least one of the following ways: Add at least one network function as a warehouse entity to the control plane; Extend the defined network functionality as a warehouse entity; One of the warehouse entities is used to store at least one of the access management context and the session management context.

20. An information transmission device, wherein the information transmission device is a target session management function entity, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The transceiver receives a session context creation request message sent by the target access and mobility management function entity. A request message is created based on the session context to obtain the mobility management context of at least one session; Mobility management is performed based on the mobility management context. The mobility management context includes at least one of an access management context and a session management context.

21. An information transmission device, wherein the information transmission device is a target access and mobility management functional entity, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The transceiver receives a handover resource allocation request message for at least one session from the source access and mobility management function entity. Through the transceiver, a session context creation request message is sent to the target session management function entity corresponding to each session according to the switching resource allocation request message; The session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session. The mobility management context includes at least one of the following: access management context and session management context.

22. An information transmission device, wherein the information transmission device is a target warehouse entity, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The transceiver receives third information sent by the target access and mobility management function entity. Based on the third information, a context retrieval operation is performed; The third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; Alternatively, the third information may include: a context acquisition notification; the context acquisition notification carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to the session.

23. An information transmission device, wherein the information transmission device is a source warehouse entity, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The transceiver receives a context acquisition request message sent by the first entity. Using the transceiver, a context retrieval request message is obtained based on the context retrieval request message, and a context retrieval response message is sent to the first entity. Wherein, the first entity includes: a target warehouse entity; the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message; Alternatively, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition response message; The context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message. The mobility management context includes at least one of the following: access management context and session management context.

24. An information transmission device, wherein the information transmission device is a source access and mobility management entity, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The transceiver sends a fourth context retrieval request message to the source repository entity. The transceiver receives the fourth context acquisition response message from the source warehouse entity. The transceiver obtains a response message based on the fourth context and sends a handover resource allocation request message for at least one session to the target access and mobility management function entity. The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message. The mobility management context includes at least one of: access management context and session management context; The resource allocation switching request message carries the mobility management context of at least one session.

25. An information transmission device applied to a target session management function entity, characterized in that, include: The first receiving unit is used to receive a session context creation request message sent by the target access and mobility management function entity; The first processing unit is configured to create a request message based on the session context to obtain the mobility management context of at least one session; The second processing unit is used to perform mobility management based on the mobility management context; The mobility management context includes at least one of an access management context and a session management context.

26. An information transmission device applied to a target access and mobility management functional entity, characterized in that, include: The second receiving unit is used to receive a handover resource allocation request message for at least one session sent by the source access and mobility management function entity. The first sending unit is configured to send a session context creation request message to the target session management function entity corresponding to each session, based on the switching resource allocation request message. The session context creation request message carries at least one mobility management context of the session; or, the session context creation request message does not carry a mobility management context of the session. The mobility management context includes at least one of the following: access management context and session management context.

27. An information transmission device applied to a target warehouse entity, characterized in that, include: The fourth receiving unit is used to receive third information sent by the target access and mobility management function entity; The third processing unit is used to perform a context acquisition operation based on the third information; The third information includes: a first context acquisition request message; the first context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; Alternatively, the third information may include: a context acquisition notification; the context acquisition notification carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to the session.

28. An information transmission device applied to a source warehouse entity, characterized in that, include: The fifth receiving unit is used to receive the context acquisition request message sent by the first entity; The fifth sending unit is used to send a context acquisition response message to the first entity based on the context acquisition request message; Wherein, the first entity includes: a target warehouse entity; the context retrieval request message includes: a second context retrieval request message; the context retrieval response message includes: a second context retrieval response message; or, the context retrieval request message includes: a third context retrieval request message; the context retrieval response message includes: a third context retrieval response message; Alternatively, the first entity includes: a source access and mobility management function entity, the context acquisition request message includes: a fourth context acquisition request message; the context acquisition response message includes: a fourth context acquisition response message; The context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the context acquisition response message carries the mobility management context of at least one session requested by the context acquisition request message. The mobility management context includes at least one of the following: access management context and session management context.

29. An information transmission device applied to a source access and mobility management entity, characterized in that, include: The sixth sending unit is used to send the fourth context retrieval request message to the source repository entity; The sixth receiving unit is used to receive the fourth context acquisition response message fed back by the source warehouse entity; The seventh sending unit is used to obtain a response message based on the fourth context and send a handover resource allocation request message for at least one session to the target access and mobility management function entity. The fourth context acquisition request message carries at least one of the following: terminal identification information, session identification information of at least one session, and node identification information of at least one network node corresponding to at least one session; the fourth context acquisition response message carries the mobility management context of at least one session requested by the fourth context acquisition request message. The mobility management context includes at least one of: access management context and session management context; The resource allocation switching request message carries the mobility management context of at least one session.

30. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program for causing the processor to perform the method according to any one of claims 1 to 19.

Images