Information indication method and communication device

Abstract

Disclosed are an information indication method and a communication device, the method comprising: a source base station sending first indication information, the first indication information comprising model transmission information, the model transmission information being used for indicating a state of user plane model transmission. Accordingly, the target base station obtains the state transmitted by the user plane model through the first indication information, so that the terminal obtains the required model from the target base station, and subsequent use of the model by the terminal is guaranteed.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an information indication method and a communication device. Background Art

[0002] Due to the size limitation of artificial intelligence (AI) / machine learning (ML) models, the number of models that can be stored on the terminal side is limited, so the terminal side usually needs to obtain the AI / ML model from the network side. One possible solution for model transmission is to transmit the model between the terminal and the base station through the data radio bearer (DRB), but this solution still faces some problems to be solved in the mobility scenario, such as how to ensure the continuity of model transmission. Summary of the invention

[0003] The embodiments of the present application provide an information indication method and a communication device to optimize potential problems in the process of using the DRB transmission model and ensure the quality of model transmission.

[0004] On the one hand, an embodiment of the present application provides an information indication method, the method comprising:

[0005] Sending first indication information, where the first indication information includes model transfer information, where the model transfer information is used to indicate a state of user plane model transfer.

[0006] Optionally, the model transfer information includes one or more of the following: identifier information, type information, and purpose information;

[0007] The identifier information is used to indicate one or more of the following: a DRB identifier, a QoS flow identifier, and a PDU session identifier;

[0008] The type information is used to indicate the type of the identifier information;

[0009] The purpose information is used to indicate the purpose of the identifier information.

[0010] Optionally, the model transfer information further includes: transfer status information, and the transfer status information is used to indicate the transfer status of the model.

[0011] Optionally, the transfer status information includes: model segmentation information, and the model segmentation information includes one or more of the following: segmentation mode, segment number, and packet sequence number.

[0012] Optionally, the first indication information further includes one or more of the following: data mapping relationship, model related information;

[0013] The data mapping relationship is used to indicate one or more of the following relationships: a mapping relationship between model data and QoS flow, a mapping relationship between QoS flow and DRB, and a mapping relationship between QoS flow and PDU session;

[0014] The model related information includes one or more of the following: model information, model function information, transfer parameter information, and LCM information of the model.

[0015] Optionally, the data mapping relationship is statically configured by a protocol or configured by a network side.

[0016] Optionally, the model information includes one or more of the following: a model identifier, and model attribute information.

[0017] Optionally, the method further comprises: sending model data, wherein the model data is included in a data packet transmitted via an Xn interface or a NG interface.

[0018] Optionally, the header of the data packet includes: model dynamic information corresponding to the model data, and the model dynamic information includes one or more of the following: model identifier, model attribute information, model segmentation information, and LCM information of the model.

[0019] Optionally, the method further includes: receiving first response information, the first response information including one or more of the following: confirmation information, objection information, feedback information.

[0020] Optionally, the method further includes: sending second indication information, wherein the second indication information is used to indicate PDU session information related to the model transfer.

[0021] Optionally, the PDU session information related to the model transfer includes: a PDU session identifier and status information; the status information is used to indicate that the PDU session identifier is used, or is used for model transfer, or is released.

[0022] Optionally, the method also includes: receiving a second response message, the second response message including any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier information.

[0023] On the other hand, an embodiment of the present application further provides an information indication method, the method comprising:

[0024] First indication information is received, where the first indication information includes model transfer information, where the model transfer information is used to indicate a state of user plane model transfer.

[0025] Optionally, the first indication information further includes one or more of the following: data mapping relationship, model related information;

[0026] The data mapping relationship is used to indicate one or more of the following: a mapping relationship between model data and QoS flow, a mapping relationship between QoS flow and DRB, and a mapping relationship between QoS flow and PDU session;

[0027] The model related information includes one or more of the following: model information, model function information, transfer parameter information, and LCM information of the model.

[0028] Optionally, the model information includes one or more of the following: a model identifier, and model attribute information.

[0029] Optionally, the method further includes: receiving model data, wherein the model data is included in a data packet transmitted via the Xn interface or the NG interface.

[0030] Optionally, the method further includes: sending a first response message, wherein the first response message includes one or more of the following: confirmation information, objection information, and feedback information.

[0031] Optionally, the method further includes: sending second indication information, wherein the second indication information is used to indicate PDU session information related to the model.

[0032] Optionally, the PDU session information related to the model transfer includes: a PDU session identifier and status information; the status information is used to indicate that the PDU session identifier is used, or is used for model transfer, or is released.

[0033] Optionally, the method also includes: receiving a second response message, the second response message including any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier.

[0034] On the other hand, an embodiment of the present application further provides an information indication method, the method comprising:

[0035] Receive second indication information, where the second indication information is used to indicate PDU session information related to the model.

[0036] Optionally, the PDU session information related to the model transfer includes: a PDU session identifier and status information; the status information is used to indicate that the PDU session identifier is used, or is used for model transfer, or is released.

[0037] Optionally, the method also includes: sending a second response information, the second response information including any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier information.

[0038] On the other hand, an embodiment of the present application further provides a communication device, comprising: a first sending module, used to send first indication information, the first indication information comprising model transfer information, and the model transfer information is used to indicate the status of user plane model transfer.

[0039] Optionally, the device further includes: a first receiving module, configured to receive first response information, wherein the first response information includes one or more of the following: confirmation information, objection information, and feedback information.

[0040] On the other hand, an embodiment of the present application further provides a communication device, comprising: a second receiving module, used to receive first indication information, the first indication information comprising model transfer information, and the model transfer information is used to indicate the status of user plane model transfer.

[0041] Optionally, the device further includes: a second sending module, configured to send first response information, wherein the first response information includes one or more of the following: confirmation information, objection information, and feedback information.

[0042] On the other hand, an embodiment of the present application further provides a communication device, comprising: a third receiving module, used to receive second indication information, wherein the second indication information is used to indicate PDU session information related to the model.

[0043] Optionally, the device also includes: a third sending module, used to send a second response information, the second response information including any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, recommended PDU session identifier information.

[0044] On the other hand, an embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the above-mentioned information indication method are executed.

[0045] On the other hand, an embodiment of the present application further provides a communication device, including a memory and a processor, wherein the memory stores a computer program that can be executed on the processor, and the processor executes the steps of the above-mentioned information indication method when running the computer program.

[0046] The information indication method and communication device provided in the embodiment of the present application send first indication information including model transfer information to the target base station through the source base station. Accordingly, the target base station obtains the state of user plane model transfer through the first indication information, so that after the terminal completes the handover, it can continue to obtain the required model from the target base station, ensuring the subsequent use of the model by the terminal.

[0047] Furthermore, the transmission status information of the model (such as model segmentation information) is sent to the target base station through the first indication information, and the affected model segment and subsequent model segments are sent to the target base station. This not only enables the terminal to continue to obtain the required model from the target base station after the switching is completed, thereby ensuring subsequent use; it also avoids the retransmission of model data that has been successfully transmitted from the source base station, effectively saving air interface resource overhead.

[0048] Furthermore, by sending second indication information to the core network for indicating protocol data unit (PDU) session information related to model transmission, the core network can avoid conflicts with PDU session identifiers allocated by the base station for model transmission when allocating PDU session identifiers for other services, thereby facilitating session management of the core network.

[0049] Furthermore, the second indication information for indicating the PDU session information related to the model transfer can be sent to the core network by the source base station or by the target base station, thereby improving the flexibility of the solution. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 is a flow chart of the information indication method provided by an embodiment of the present application;

[0051] Figure 2 is another flow chart of the information indication method provided in the embodiment of the present application;

[0052] Figure 3 is another flow chart of the information indication method provided in the embodiment of the present application;

[0053] Figure 4 is another flow chart of the information indication method provided in the embodiment of the present application;

[0054] Figure 5 is another flow chart of the information indication method provided in the embodiment of the present application;

[0055] Figures 6 to 11 This is a specific application example of the information indication method provided in the embodiment of the present application;

[0056] Fig.12 is a structural diagram of a communication device provided in an embodiment of the present application;

[0057] Fig.13 is a structural diagram of another communication device provided in an embodiment of the present application;

[0058] Fig.14 is a structural diagram of another communication device provided in an embodiment of the present application;

[0059] Fig.15 It is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] In order to make the above-mentioned purposes, features and beneficial effects of the present application more obvious and easy to understand, the specific embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0061] The communication systems to which the embodiments of the present application are applicable include, but are not limited to, Long Term Evolution (LTE) systems, fifth-generation (5G) systems, new radio (NR) systems, and future evolution systems such as sixth generation (6G), seventh generation (7G), etc., or multiple communication convergence systems. Among them, the 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system.

[0062] The technical solution of the present application is also applicable to different network architectures, including but not limited to relay network architecture, dual connection architecture, vehicle-to-everything (V2X) architecture, device-to-device (D2D) architecture, and other architectures.

[0063] The devices in the embodiments of the present application include network devices and may also include terminals. The network devices may also be referred to as access network devices, for example, may be base stations (BS) (also referred to as base station devices), base station controllers (BSC), and core network devices.

[0064] A network device is a device deployed in a Radio Access Network (RAN) to provide wireless communication functions. For example, the equipment that provides base station functions in the second-generation (2nd-Generation, 2G) network includes the Base Transceiver Station (Base Transceiver Station, BTS), the equipment that provides base station functions in the third-generation (3rd-Generation, 3G) network includes the Node B (NodeB), the equipment that provides base station functions in the fourth-generation (4th-Generation, 4G) network includes the evolved Node B (evolved NodeB, eNB), and in the wireless local area network (Wireless Local Area Networks, WLAN), the equipment that provides base station functions is the access point (Access Point, AP), and the equipment that provides base station functions in the 5G new radio (New Radio, NR) is the next generation Node Basestation (next generation Node Basestation, gNB), and the evolved Node B (ng-eNB), wherein the gNB and the terminal communicate using NR technology, and the ng-eNB and the terminal communicate using evolved universal terrestrial radio access (Evolved Universal Terrestrial Radio Access, E-UTRA) technology, and both gNB and ng-eNB can be connected to the 5G core network. The base station in the embodiment of the present application also includes equipment that provides base station functions in future new communication systems, etc.

[0065] The base station controller in the embodiment of the present application may also be referred to as a base station controller device, which is a device for managing base stations, such as a base station controller (BSC) in a 2G network, a radio network controller (RNC) in a 3G network, and may also refer to a device for controlling and managing base stations in future new communication systems.

[0066] The core network devices in the embodiments of the present application mainly include access and mobility management function (AMF), session management function (SMF), network repository function (NRF), user plane function (UPF) and other network element devices. These network element devices handle mobility management, application session management and application content flow through the core network.

[0067] The terminal in the embodiment of the present application may also be referred to as a terminal device, and may refer to various forms of terminal devices, such as user equipment (terminal), access terminal, user unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., and the embodiment of the present application is not limited to this.

[0068] It should be noted that the brackets used in this specification may mean "for example". For example, model update (such as model parameter update) refers to "model parameter update" as an example of "model update. That is, "model update" in this specification may be but is not limited to "model parameter update".

[0069] In mobility scenarios, the terminal side usually needs to obtain the AI / ML model from the network side, and the AI / ML model is usually stored on the base station. Compared with the transmission method through the signaling radio bearer (SRB), the model transmitted between the terminal and the base station through the data radio bearer (DRB) has the advantages of low signaling overhead, no need to consider the control plane (CP) segmentation and the impact on other CP messages, and can provide reliable quality of service (QoS) requirements.

[0070] However, the following problems need to be solved: (1) The end point of the user plane (UP) needs to be migrated from (User Plane Function) to the base station; (2) The target base station needs to distinguish between the AI / ML model transmission service and the normal service that needs to be transmitted to the core network, that is, the target base station needs to know the DRB of the transmission model, and then distinguish this type of DRB from the DRB carrying normal services, so that the target base station can complete the model transmission.

[0071] In addition, during the switching process, not only the continuity of model transmission must be guaranteed, but also redundant retransmissions must be reduced as much as possible, that is, the retransmission of model data that has already been transmitted in the source cell in the target cell must be reduced, thereby reducing the waste of air interface resources.

[0072] In addition, it is necessary to further ensure that the model transfer has consistent transmission quality.

[0073] In response to one or more requirements for model transmission in the above-mentioned mobile scenarios, an embodiment of the present application provides an information indication method and a communication device to realize model transmission and ensure the transmission quality of the model.

[0074] The present application scheme involves information interaction between a source base station and a target base station, a source base station and a core network, and a target base station and a core network, which are described in detail below.

[0075] For example, Figure 1 The figure shows a flow chart of the information indication method provided in an embodiment of the present application.

[0076] This embodiment shows the interaction process between the source base station and the target base station, which is as follows:

[0077] In step 11, the source base station sends first indication information to the target base station, where the first indication information includes model transfer information, and the model transfer information is used to indicate a state of user plane model transfer.

[0078] In a non-limiting embodiment, the model transfer information may include one or more of the following: identifier information, type information, and purpose information.

[0079] The identifier information is used to indicate one or more of the following: DRB identifier, QoS flow identifier, PDU session identifier;

[0080] The type information is used to indicate the type of the identifier information;

[0081] The purpose information is used to indicate the purpose of the identifier information.

[0082] For example, in one embodiment, the above-mentioned model transmission information only includes identifier information. This situation can be regarded as an implicit indication method, that is, the identifier information indicates a special DRB, and / or a special QoS flow, and / or a special PDU session.

[0083] For another example, in another embodiment, the model transfer information includes the above-mentioned identifier information and type information. The type information may indicate whether the identifier indicated by the identifier information is a normal identifier or a special identifier. A special identifier indicates that the identifier corresponds to a related identifier of the model transfer, and a normal identifier indicates that the identifier is not a related identifier of the corresponding model transfer.

[0084] Exemplarily, a normal DRB id indicates a DRB that is not used for model transfer, and a special DRB id indicates a DRB that is used for model transfer.

[0085] For another example, in another embodiment, the model transfer information includes the above-mentioned identifier information and purpose information. In this case, the purpose information may indicate that the identifier indicated by the identifier information is used to transfer the model, or indicate that the starting and ending points of the data transfer of the identifier indicated by the identifier information are the base station, rather than the UPF (User Plane Function), etc.

[0086] In another non-limiting embodiment, the model transfer information may further include: transfer status information, where the transfer status information is used to indicate the transfer status of the model.

[0087] The transfer status information may include model segmentation information, and the model segmentation information may include one or more of the following: segmentation mode, segment number, and packet sequence number.

[0088] The segmentation method is used to indicate how the model is segmented, such as segmenting the model according to a segmentation algorithm or segmentation rule. For example, segmentation by layer: one layer as a segment or multiple layers as a segment, or segmentation according to the model structure, or segmentation according to a fixed size or volume or size, or segmentation according to a fixed number, etc.

[0089] The above segmentation according to a fixed size / volume / size means that the size / volume / size of the model segment meets the condition of the set size / volume / size.

[0090] The fixed data segmentation means that no matter how big the model is, it is divided into a fixed number of segments. The segment number can be one or more of the following: the maximum model segment number, the latest model segment number, the transmitted model segment number, the remaining model segment number to be transmitted, etc.

[0091] The different model segmentation information mentioned above are illustrated as follows:

[0092] For example, segmentation method: segmentation by layer, each segment includes one layer, segment number: maximum model segment number x; it means that the model information of the layers with segment number x and before have been transmitted successfully, and the model information of the layers after segment number x (including the model layer where segment x is located) has not been transmitted successfully.

[0093] For another example, segmentation method: segmentation by layer, each segment includes multiple layers, segment number: latest model segment number x, it means that the information of the segment models before segment number x has been successfully transmitted, and the information of other segment models with segment number x and after x has not been successfully transmitted.

[0094] For another example, segmentation method: segment by fixed number, segment number: transmitted model segment number 1, 2, 4, x, it means that the information of the segment models with segment numbers 1, 2, 4, x has been successfully transmitted, and the information of other segment models has not been successfully transmitted.

[0095] For another example, segmentation method: segmentation by layer, segment number: the remaining model segment number that needs to be transmitted<x1,x2> , it means that the model information from model x1 to x2 layers has not been transmitted successfully.

[0096] The packet sequence number refers to a Packet Data Convergence Protocol (PDCP) PDU sequence number, ie, a PDCP SN; or the PDCP SN of the earliest affected data packet; or the PDCP SNs of multiple affected data packets.

[0097] It should be noted that the above-mentioned first indication information may include model transfer information of one or more models.

[0098] Based on the above first indication information, after the terminal switches from the source cell to the target cell, it can continue to obtain the corresponding model from the target base station to ensure the subsequent use of the model.

[0099] In another non-limiting embodiment, the first indication information may further include one or more of the following: data mapping relationship, model related information.

[0100] The data mapping relationship is used to indicate one or more of the following: the mapping relationship between model data (referring to model application layer data) and QoS flow, the mapping relationship between QoS flow and DRB, and the mapping relationship between QoS flow and PDU session.

[0101] It should be noted that the above data mapping relationship can be statically configured by the protocol; or flexibly configured on the network side, such as the base station itself configuring, or the core network configuring and sending it to the base station through an NG interface message, which is not limited to this embodiment of the present application.

[0102] Accordingly, based on the data mapping relationship, the QoS delivered by the model can be kept consistent during the terminal movement process, thereby improving user experience.

[0103] Model related information refers to information about the model transfer process affected by the switch, and the model related information may include but is not limited to one or more of the following: model information, model function information, transfer parameter information, model life cycle management (LCM) information, etc.

[0104] The following is a detailed description of each item in the above model related information.

[0105] The model information refers to the information of the affected model, which may include but is not limited to one or more of the following: model identifier, model attribute information, etc.

[0106] The model identifier refers to the identification information of the affected model, that is, the Model ID.

[0107] Model attribute information may include, but is not limited to, one or more of the following:

[0108] 1) Functional information refers to the function of the model identified by the Model ID, such as channel status information (CSI) compression feedback function, beam management function, positioning function, etc.

[0109] It should be noted that if the function information contains multiple models, "function information + model information" can also be used to identify a model.

[0110] 2) Input information refers to the characteristics of the model’s input data, such as type, dimension, precision, data distribution characteristics, etc.

[0111] 3) Output information refers to the characteristics of the model's output data, such as type, dimension, accuracy, etc.

[0112] 4) Model structure information refers to the network structure information used by the model, for example, it may include one or more of the following information: network structure, such as Convolutional Neural Network (CNN), Deep Neural Networks (DNN), Long Short-Term Memory (LSTM), etc.; convolution kernel configuration, such as 2D convolution, 3D convolution; convolution kernel size, such as 3x3, 5x5, etc.; number of model layers; number of neurons in each layer; model complexity, such as model volume (such as megabytes); number of floating-point operations per second (FLOPs); power consumption; number of operations, etc.;

[0113] 5) Model configuration information or applicable conditions may include: scenarios and / or areas to which the model is applicable; the scenarios may include, for example, stationary, moving (for example, the moving speed may be: high speed, medium speed, low speed); the areas may include, for example, random access (RA) / tracking area (TA) / cell (Cell) / beam (Beam) / synchronization signal block (SSB) configuration, etc.

[0114] 6) Model monitoring parameters refer to the parameters that need to be monitored for model delivery, which may include one or more of the following: monitoring indicators, triggering events, monitoring data reporting methods, monitoring decisions, etc. Among them:

[0115] The monitoring indicators may include system indicators and intermediate indicators, wherein the system indicators may include one or more of the following: Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), Packet Error Rate (PER), Latency, Throughput, etc.; the intermediate indicators may include SGCS (cosine similarity, etc.;

[0116] Trigger events refer to the conditions that trigger model monitoring-related behaviors, such as falling below the configured RSRP threshold, triggering monitoring data reporting or decision events, etc.

[0117] The monitoring data reporting mode refers to the state at the time of reporting (such as connected state, non-connected state) and / or the target object of reporting (such as reporting to the base station or the core network);

[0118] Monitoring decision refers to the subject of monitoring decision, that is, who makes the decision. For example, the terminal can make the decision and report it to the network (NW) for approval; or the terminal can report the monitoring data to the NW for decision, and the NW makes a decision based on the monitoring data.

[0119] 7) Model version information, used to indicate the model version, such as V1, V2; or time information + version information, such as 2023R1, 2023R2; or other forms, etc.

[0120] 8) Model vendor information refers to the vendor information of the model, such as HW, CATT, ZTE, Nokia, etc.; or device number information; or hardware address information, etc.

[0121] The model function information is used to indicate the function of the model identified by the model. It should be noted that in some cases, such as when the model function and the model correspond one-to-one, the model function information can also be used to implicitly indicate the model information, in which case the above model information does not need to be provided; or the model function information is implicitly included in the model information, in which case the model function information does not need to be provided.

[0122] Among them, the transmission parameter information is used to indicate the guaranteed transmission parameters required by the target base station transmission model. Exemplarily, the transmission parameter information here is QoS parameters, such as transmission rate, delay, jitter, packet loss rate and other requirements, so that the target base station can provide the model transmission service with the same quality as the source base station.

[0123] The LCM information of the model may indicate: initial model deployment, or model update, or model transfer for model training, model reasoning, model monitoring, model selection / activation / deactivation / switching / fallback, etc. The model update may include partial model update (such as model parameter update) / full model update (such as model structure and model parameter update), etc.

[0124] Accordingly, after the terminal completes the handover, the target base station can continue to pass the model data affected by the handover to the terminal according to the above-mentioned first indication information and the corresponding model data saved, so as to ensure the subsequent use of the model by the terminal. The model data transmitted by the target base station to the terminal can be included in the data packet transmitted by the Uu interface (the interface between the terminal and the base station).

[0125] Taking into account that in some cases, the model data may only be stored in some base stations, and the target base station to which the terminal is to switch may not store the model data being transmitted by the source base station, for this reason, in another non-limiting embodiment, the source base station may also send the model data to be transmitted to the target base station, so that the terminal can obtain the corresponding model data from the target base station after switching to the target base station.

[0126] For example, Figure 2 Shown is another flow chart of the information indication method provided in an embodiment of the present application.

[0127] and Figure 1 Compared with the embodiment shown, in this embodiment, in addition to the source base station sending the first indicator information to the target base station in step 11, the source base station also sends model data to the target base station in step 12.

[0128] The above-mentioned model data refers to the model data affected by the switching, for example, it may be: all the model data, or only the model data affected by the switching, or the affected model data and the model data that has not been subsequently transmitted, etc.

[0129] The model data can be included in the data packet transmitted by the Xn interface (the interface between the two base stations), that is, sent directly by the source base station to the target base station, or included in the data packet transmitted by the NG interface (the interface between the wireless access network and the core network), that is, sent by the source base station to the core network, and then sent by the core network to the target base station. This embodiment of the present application is not limited to this.

[0130] Furthermore, the packet header of the data packet carrying the model data may include model dynamic information corresponding to the model data, and the model dynamic information may include one or more of the following: model identifier, model segmentation information, and LCM information of the model. This information is similar to some corresponding information in the first indication information introduced above, and will not be repeated here. The so-called model dynamic information means that the information corresponds to the model data carried in the data packet, that is, depending on the different model data carried, the corresponding model dynamic information will also change accordingly.

[0131] By transmitting the model data to the target base station, the target base station can continue to complete the model transmission process that was not completed in the source base station without saving the corresponding model data. Moreover, with the assistance of the model dynamic information, the source base station can only send the affected model segment and subsequent model segment to the target base station, avoiding the retransmission of the model data that has been successfully transmitted before, effectively saving the air interface resource overhead.

[0132] In another non-limiting embodiment, Figure 3 As shown, after receiving the above-mentioned first indication information, the target base station can also send a first response information to the source base station in step 13, and the first response information includes one or more of the following: confirmation information, objection information, and feedback information.

[0133] Among them, confirmation information refers to agreement with the first instruction information; objection information refers to disagreement with the first instruction information.

[0134] Among them, other feedback information may include but is not limited to:

[0135] (1) The target base station supports or does not support the model. The target base station supports the model, which means that the target base station also stores the model; the target base station does not support the model, which means that the target base station does not store the model;

[0136] (2) The target base station supports / does not support the segmentation method used by the source base station for the model. Similar to the above, the target base station supports the segmentation method used by the source base station for the model, which means that the target base station can also segment the model using this segmentation method; the target base station does not support the segmentation method used by the source base station for the model, which means that the target base station does not support the segmentation method used by the source base station, or the segmentation method used by the target base station is different from the segmentation method used by the source base station for the model.

[0137] It should be noted that, in the case where the first indication information includes relevant information of multiple models, the first response information may include confirmation / rejection / other feedback information of some or all models.

[0138] Accordingly, the source base station may decide how to send the model data to the target base station and which model segments to send according to the first response information sent by the target base station.

[0139] It should be noted that the source base station may not rely on the above-mentioned first response information, but may decide how to send model data to the target base station and which model segments to send based on the relevant configuration information of the model. This embodiment of the present application does not limit this.

[0140] Since the PDU session identifier used for model transfer is configured by the source base station itself, in order to avoid conflicts when the core network allocates the PDU session identifier to the radio access network (Radio Access Network, RAN), that is, allocating the PDU session identifier that has been used by the transferred model, in another non-limiting embodiment, the base station can also send a second indication information to the core network, and the second indication information is used to indicate the PDU session information related to the model transfer.

[0141] In a specific implementation, the second indication information may be sent to the core network by the source base station or the target base station.

[0142] For example, Figure 4 Shown is another flow chart of the information indication method provided in an embodiment of the present application.

[0143] In step 41, the source base station or the target base station sends a second indication information to the core network, where the second indication information is used to indicate PDU session information related to model transfer, and specifically may include a PDU session identifier and status information. The status information is used to indicate that the PDU session identifier is used, or is used for model transfer, or is released.

[0144] Further, in a non-limiting embodiment, as Figure 5 shown, in step 42, the core network may also return second response information to the source base station or the target base station. The second response information includes, but is not limited to, any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, recommended PDU session identifier information, etc. Among them:

[0145] The confirmation information of the PDU session identifier is used to indicate that the core network agrees to use the PDU session identifier to transmit the model;

[0146] The objection information of the PDU session identifier is used to indicate that the core network does not agree to use the PDU session identifier to transmit the model;

[0147] The recommended PDU session identifier information is used to indicate that the core network recommends using the PDU session identifier to transmit the model.

[0148] It should be noted that the core network element that receives the second indication information and sends the second response information may be, but is not limited to, any one of the following: AMF, SMF, NRF, UPF, etc.

[0149] The above second indication information and second response information can be sent through NG interface messages. Specifically, it can be carried in the existing NG interface messages or new messages can be added. The embodiments of this application do not make limitations on this.

[0150] Next, an example is given to further elaborate on the specific application of the information indication method provided in this application.

[0151] Example 1:

[0152] Exemplarily, as Figure 6 shown, in step 61, after making a handover decision, the source base station sends a handover request message HANDOVER REQUEST to the target base station. The handover request message carries first indication information, and the first indication information includes: <PDU session identifier x, model transfer information, layer-by-layer segmentation number: Ln, model identifier y>.

[0153] In step 62, the target base station returns a handover request response message HANDOVER REQUEST ACK to the source base station. The handover request response message carries first response information, and the first response information indicates that the target base station supports the segmentation method of model y segmented by layer.

[0154] Correspondingly, in step 63, after the handover is completed, the terminal obtains the model data of layer Ln and later from the target base station.

[0155] It can be seen that by using the solution of this embodiment, after the handover of the terminal is completed, the target base station can continue to transmit the model data affected by the handover to the terminal according to the first indication information and the corresponding model saved by itself, so as to ensure the subsequent use of the model by the terminal.

[0156] Example 2:

[0157] Exemplarily, as Figure 7 shown, in step 71, after making a handover decision, the source base station sends a handover request message HANDOVER REQUEST to the target base station. The handover request message carries the first indication information, and the first indication information includes: <PDU session identifier x, type information of x, transfer parameter information, per-layer segment number: Ln, model identifier y>.

[0158] In step 72, the target base station returns a handover request response message HANDOVER REQUEST ACK to the source base station. The handover request response message carries the first response information, and the first response information indicates that it does not support model y.

[0159] Correspondingly, the source base station receives the above handover request response message, and then in step 73, the source base station sends model data to the target base station. Specifically, it can send the model data from layer Ln and after through the GPRS Tunnelling Protocol for the user plane (GTP-U) data packet of the user plane, and add the model identifier and model segment information in the GTP-U data packet header.

[0160] In step 74, after the handover is completed, the terminal obtains the model data from layer Ln and after from the target base station.

[0161] It can be seen that by using the solution of this embodiment, although the target base station does not save the model data transmitted by the source base station to the terminal, the source base station can forward the untransmitted model data and related information to the target base station. Thus, after the terminal completes the handover, it can continue to obtain the required model from the target base station, ensuring the subsequent use of the model. At the same time, the target base station obtains the affected model segments and subsequent model segments from the source base station and transmits them to the terminal after the handover is completed, avoiding retransmitting the model data that has been successfully transmitted before and saving the overhead of air interface resources.

[0162] Example 3:

[0163] Exemplarily, as Figure 8As shown, in step 81, the source base station sends a handover request message HANDOVER REQUEST to the target base station. The handover request message carries first indication information, and the first indication information includes: <PDU session identifier x, model transfer information, per-layer segmentation number: Ln, model identifier y>.

[0164] In step 82, the target base station returns a handover request response message HANDOVER REQUEST ACK. The handover request response message carries first response information, and the first response information indicates that it supports the model with model identifier y and does not support the per-layer segmented model segmentation method.

[0165] Since the target base station does not support the per-layer segmented model segmentation method, in this case, there can be multiple processing methods.

[0166] For example, in a non-limiting embodiment, the target base station converts and maps to the segmentation method of the target model according to the segmentation method of the source model. Correspondingly, in step 82 above, the first response information includes remapping information to indicate the conversion relationship of the segmentation method.

[0167] Correspondingly, the source base station receives the above handover request response message, and then in step 83, the source base station sends the model data of layer Ln and later through a GTP-U data packet, and adds a model identifier and model segmentation information in the GTP-U data packet header.

[0168] Since the segmentation method has changed, therefore, in step 84, the source base station sends an RRC reconfiguration message to the terminal, and the remapping information is carried in the message.

[0169] After the handover is completed, in step 85, the terminal obtains the corresponding model data from the target base station according to the remapping information.

[0170] For another example, in another non-limiting embodiment, step 83' is executed. The source base station forwards the affected model segments and the subsequent model segments to the target base station. The source base station sends the model data through a GTP-U data packet, and adds a model identifier and model segmentation information in the GTP-U data packet header.

[0171] Correspondingly, after the handover is completed, in step 84', the terminal obtains the model data of layer Ln and later from the target base station. At this time, the segmentation method is still segmented according to the segmentation method of the source base station, but only the affected model segments and the subsequent model segments are forwarded by the target base station to the terminal.

[0172] It can be seen that, using the solution of this embodiment, when the target base station saves the model transmitted by the source base station to the terminal but does not support the model segmentation method of layer segmentation, the source base station can forward the untransmitted model data and related information to the target base station, so that the terminal can continue to obtain the required model from the target base station after the handover is completed, ensuring the subsequent use of the model. At the same time, the target base station obtains the affected model segmentation and subsequent model segmentation from the source base station and transmits them to the terminal after the handover is completed, thereby avoiding the retransmission of the model data that has been successfully transmitted before, saving air interface resource overhead.

[0173] Example 4:

[0174] For example, Fig. 9 As shown, in step 91, the source base station / target base station sends a second indication message to the core network element AMF, wherein the second indication message includes a PDU session identifier x and indicates that the PDU session identifier x has been used to transfer the model.

[0175] In step 92, the AMF returns a second response message to the source base station / target base station, indicating ACK.

[0176] Afterwards, the core network triggers the establishment of a PDU session and allocates a PDU session identifier other than x to the PDU session, thereby avoiding a conflict with the PDU session identifier x used for the transfer model.

[0177] Example 5:

[0178] For example, Fig.10 As shown, in step 101, the source base station / target base station sends a second indication message to the core network element AMF, wherein the second indication message includes a PDU session identifier x and indicates that the PDU session identifier x has been used to transfer the model.

[0179] In step 102, the AMF returns a second response message to the source base station / target base station, indicating the recommended PDU session identifier m.

[0180] In step 103, the source base station uses the PDU session identifier m to transfer the model to the terminal.

[0181] It should be noted that the above-mentioned source base station and target base station may send the second indication information to the core network during the switching process or before the switching is completed, which is not limited in this embodiment of the present application.

[0182] It can be seen that through the interaction between the above-mentioned source base station / target base station and the core network element, the conflict between the PDU session identifier allocated by the base station for model transmission and the PDU session identifier allocated by the core network for other data transmission can be avoided, which facilitates the core network's management of the session.

[0183] Example 6:

[0184] Exemplarily, as Fig.11 shown, in step 111, after making a handover decision, the source base station sends a handover request message HANDOVER REQUEST to the target base station. The handover request message carries first indication information, and the first indication information includes: <PDU session identifier x, type information of x, transfer parameter information, layer-by-layer segmentation number: Ln, model identifier y>.

[0185] In step 112, the target base station returns a handover request response message HANDOVER REQUEST ACK to the source base station. The handover request response message carries first response information, and the first response information indicates that it does not support the segmentation method of layer-by-layer segmentation of model y.

[0186] Correspondingly, the source base station receives the above handover request response message, and then in step 113, the source base station forwards the affected model segments and subsequent model segments to the target base station. The model data can specifically be encapsulated in a GPRS tunnelling protocol for the user plane (GTP-U) data packet in the user plane, and the model identifier and model segment information are added to the GTP-U data packet header.

[0187] Meanwhile, in step 114, the source base station sends second indication information to the core network element AMF. The second indication information includes: PDU session identifier x, status information: used to transfer the model.

[0188] In step 115, the core network element AMF returns second response information to the source base station, indicating ACK. After that, the core network triggers the establishment of a PDU session, and allocates a PDU session identifier other than x for this PDU session, so as to avoid conflicts with the PDU session identifier x used to transfer the model.

[0189] It should be noted that the target base station can also send second indication information to the core network element AMF, that is Fig.11 step 114' in, to indicate the PDU session information related to the model of the target base station. For example, the second indication information sent by the target base station includes: PDU session identifier a, status information: used to transfer the model. Correspondingly, in step 115', the core network element AMF returns second response information to the target base station. In addition, the second indication information sent by the target base station to the core network element AMF indicates the PDU session identifier used by the target base station to transfer the model. For example, it can be PDU session identifier a, or PDU session identifier x, which is specifically determined by the target base station.

[0190] After the handover is completed, in step 116, the terminal obtains the model data of layer Ln and subsequent layers from the target base station.

[0191] In addition, it should be noted that after the source base station completes the transfer model, it also needs to release the corresponding PDU session. At this time, the source base station can send a second indication message to the AMF again. The second indication message includes: PDU session identifier x, status information: released.

[0192] Correspondingly, the AMF may also send a second response message to the source base station in response to the second indication message.

[0193] Similarly, assuming that the target base station transfer model uses the PDU session identifier a, the corresponding PDU session needs to be released after the transfer model is completed. At this time, the target base station can send a second indication message to the AMF again, and the second indication message includes: PDU session identifier a, status information: released.

[0194] In another possible example, the target base station may send a third indication message to the source base station to indicate the target base station to transfer the PDU session identifier a allocated for the model. The indication information may be carried in the first response message, such as sent via a switching request response message, or sent via other messages or new messages of the Xn or NG interface, which is not limited to this embodiment of the present application.

[0195] The source base station sends the second indication information to the core network, and the second indication information may include the PDU session identifier a used by the target base station.

[0196] It should be noted that, in a non-limiting embodiment, the second indication information may include both the PDU session identifier x used by the source base station transfer model and the PDU session identifier a used by the target base station transfer model.

[0197] After the handover is completed, the model transfer process of the terminal in the target base station is completed, and the target base station can send a second indication message to the core network to indicate that the PDU session a is released.

[0198] It can be seen that the solution of the embodiment of the present application can not only ensure the continuity of model transmission during the switching process, but also avoid the conflict between the PDU session identifier allocated by the base station for model transmission and the PDU session identifier allocated by the core network for other data transmission, thereby facilitating the core network's management of the session.

[0199] It should be noted that the serial numbers of the steps in the above embodiments do not limit the execution order of the steps.

[0200] It is understandable that the information indication method of each of the above embodiments can be implemented in the form of a software program, which runs in a processor integrated in a chip or chip module. The method can also be implemented in the form of software combined with hardware, which is not limited in this application.

[0201] Accordingly, the embodiment of the present application further provides a communication device, exemplarily, as Fig.12 As shown, the communication device 120 includes:

[0202] The first sending module 121 is used to send first indication information, where the first indication information includes model transfer information, and the model transfer information is used to indicate a state of user plane model transfer.

[0203] In another non-limiting embodiment, the first sending module 121 may also be used to send model data, where the model data is included in a data packet transmitted via the Xn interface or the NG interface.

[0204] In another non-limiting embodiment, the communication device 120 may further include: a first receiving module (not shown) for receiving first response information, wherein the first response information includes one or more of the following: confirmation information, objection information, and feedback information.

[0205] In another non-limiting embodiment, the first sending module 121 may also be used to send second indication information, where the second indication information is used to indicate PDU session information related to model transfer.

[0206] In another non-limiting embodiment, the first receiving module is also used to receive a second response message, and the second response message includes any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier information.

[0207] The above-mentioned communication device may be a base station, such as a source base station.

[0208] Accordingly, the embodiment of the present application further provides a communication device, exemplarily, as Fig.13 As shown, the communication device 130 includes:

[0209] The second receiving module 131 is used to receive first indication information, where the first indication information includes model transfer information, and the model transfer information is used to indicate a state of user plane model transfer.

[0210] In another non-limiting embodiment, the communication device 130 may further include a second sending module (not shown) for sending a first response message, wherein the first response message includes one or more of the following: confirmation information, objection information, and feedback information.

[0211] The above-mentioned communication device may be a base station, such as a target base station.

[0212] Accordingly, the embodiment of the present application further provides a communication device, exemplarily, as Fig.14 As shown, the communication device 140 includes:

[0213] The third receiving module 141 is used to receive second indication information, where the second indication information is used to indicate PDU session information related to the model.

[0214] In another non-limiting embodiment, the communication device 140 may further include a third sending module (not shown) for sending a second response message, wherein the second response message includes any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier information.

[0215] The above-mentioned communication device can be a core network element device, such as AMF, SMF, NRF, UPF, etc.

[0216] For other related descriptions of the above communication devices, please refer to Figures 1 to 11 The relevant description in will not be repeated here.

[0217] In a specific implementation, the above-mentioned device may correspond to a chip with corresponding functions in a network device and / or a user device, such as a SOC (System-On-a-Chip), a baseband chip, a chip module, etc.

[0218] In a specific implementation, each module / unit included in each device or product described in the above embodiments may be a software module / unit or a hardware module / unit, or may be partially a software module / unit and partially a hardware module / unit. For example, for each device or product applied to or integrated in a chip, each module / unit included therein may be implemented in the form of hardware such as circuits, or at least some of the modules / units may be implemented in the form of software programs, which run on a processor integrated inside the chip, and the remaining (if any) modules / units may be implemented in the form of hardware such as circuits; for each device or product applied to or integrated in a chip module, each module / unit included therein may be implemented in the form of hardware such as circuits, and different modules / units may be located in the same component (such as a chip, circuit module, etc.) or different components of the chip module, or at least some of the modules / units may be implemented in the form of hardware such as circuits. The element can be implemented in the form of a software program, which runs on a processor integrated inside the chip module, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated in the terminal, the various modules / units contained therein can be implemented in the form of hardware such as circuits, and different modules / units can be located in the same component (for example, chip, circuit module, etc.) or in different components in the terminal, or, at least some modules / units can be implemented in the form of a software program, which runs on a processor integrated inside the terminal, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits.

[0219] The present application also discloses a storage medium, which is a computer-readable storage medium and stores a computer program, which can be executed when the computer program is run. Figures 1 to 10 The storage medium may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc. The storage medium may also include a non-volatile memory (non-volatile) or a non-transitory memory, etc.

[0220] Please refer to Fig.15 The embodiment of the present application also provides a hardware structure diagram of a communication device. The communication device includes a processor 1501, a memory 1502 and a transceiver 1503.

[0221] Processor 1501 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application. Processor 1501 may also include multiple CPUs, and processor 1501 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, or processing cores for processing data (such as computer program instructions).

[0222] The memory 1502 may be a ROM or other types of static storage devices that can store static information and instructions, a RAM or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, and the embodiments of the present application do not impose any restrictions on this. The memory 1502 may exist independently (in this case, the memory 1502 may be located outside the device or inside the device), or it may be integrated with the processor 1501. Among them, the memory 1502 may contain a computer program code. The processor 1501 is used to execute the computer program code stored in the memory 1502, thereby realizing the method provided in the embodiments of the present application.

[0223] The processor 1501, the memory 1502 and the transceiver 1503 are connected via a bus. The transceiver 1503 is used to communicate with other devices or communication networks. Optionally, the transceiver 1503 may include a transmitter and a receiver. The device used to implement the receiving function in the transceiver 1503 can be regarded as a receiver, and the receiver is used to perform the receiving steps in the embodiment of the present application. The device used to implement the sending function in the transceiver 1503 can be regarded as a transmitter, and the transmitter is used to perform the steps in the method embodiment of the present application.

[0224] when Fig.15The schematic diagram of the structure shown is used to illustrate the structure of the communication device involved in the above embodiment. The processor 1501 is used to control and manage the actions of the communication device. For example, the processor 1501 is used to support the communication device to execute Figures 1 to 11 All or part of the steps in any figure, and / or actions performed by the communication device in other processes described in the embodiments of the present application. The processor 1501 can communicate with other network entities through the transceiver 1503, for example, communicating with the above-mentioned network devices. The memory 1502 is used to store program codes and data of the communication device.

[0225] It should be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article indicates that the associated objects before and after are in an "or" relationship.

[0226] The "plurality" appearing in the embodiments of the present application refers to two or more.

[0227] The first, second, etc. descriptions appearing in the embodiments of the present application are only used for illustration and distinction of the description objects. There is no order, nor do they indicate any special limitation on the number of devices in the embodiments of the present application, and cannot constitute any limitation on the embodiments of the present application.

[0228] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0229] The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination thereof. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means.

[0230] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0231] In the several embodiments provided in the present application, it should be understood that the disclosed methods, devices and systems can be implemented in other ways. For example, the device embodiments described above are merely schematic; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0232] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0233] In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, or each unit can be physically arranged separately, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0234] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the method described in each embodiment of the present application.

[0235] Although the present application is disclosed as above, the present application is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present application. Therefore, the protection scope of the present application shall be subject to the scope defined by the claims.

Claims

1. An information indication method, characterized in that: The method comprises: Sending first indication information, where the first indication information includes model transfer information, where the model transfer information is used to indicate a state of user plane model transfer.

2. The method according to claim 1, characterized in that The model transfer information includes one or more of the following: identifier information, type information, and purpose information; The identifier information is used to indicate one or more of the following: a DRB identifier, a QoS flow identifier, and a PDU session identifier; The type information is used to indicate the type of the identifier information; The purpose information is used to indicate the purpose of the identifier information.

3. The method according to claim 1 or 2, characterized in that: The model transfer information further includes: transfer status information, and the transfer status information is used to indicate the transfer status of the model.

4. The method according to claim 3, characterized in that The transfer status information includes: model segmentation information, and the model segmentation information includes one or more of the following: segmentation mode, segment number, and packet sequence number.

5. The method according to claim 1, characterized in that The first indication information also includes one or more of the following: data mapping relationship, model related information; The data mapping relationship is used to indicate one or more of the following relationships: a mapping relationship between model data and QoS flow, a mapping relationship between QoS flow and DRB, and a mapping relationship between QoS flow and PDU session; The model related information includes one or more of the following: model information, model function information, transfer parameter information, and LCM information of the model.

6. The method according to claim 5, characterized in that The data mapping relationship is statically configured by the protocol or configured by the network side.

7. The method according to claim 5, characterized in that The model information includes one or more of the following: a model identifier and model attribute information.

8. The method according to claim 1, characterized in that The method further comprises: Send model data, wherein the model data is included in a data packet transmitted via the Xn interface or the NG interface.

9. The method according to claim 8, characterized in that The header of the data packet includes: model dynamic information corresponding to the model data, and the model dynamic information includes one or more of the following: Model identifier, model attribute information, model segmentation information, and model LCM information.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: A first response message is received, where the first response message includes one or more of the following: confirmation message, objection message, and feedback message.

11. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: Send second indication information, where the second indication information is used to indicate PDU session information related to model transfer.

12. The method according to claim 11, characterized in that The PDU session information related to the model transfer includes: PDU session identifier and status information; The state information is used to indicate that the PDU session identifier is used, used for model transfer, or released.

13. The method according to claim 12, characterized in that The method further comprises: Receive a second response message, the second response message including any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier information.

14. An information indication method, characterized in that: The method comprises: First indication information is received, where the first indication information includes model transfer information, where the model transfer information is used to indicate a state of user plane model transfer.

15. The method according to claim 14, characterized in that The first indication information also includes one or more of the following: data mapping relationship, model related information; The data mapping relationship is used to indicate one or more of the following: a mapping relationship between model data and QoS flow, a mapping relationship between QoS flow and DRB, and a mapping relationship between QoS flow and PDU session; The model related information includes one or more of the following: model information, model function information, transfer parameter information, and LCM information of the model.

16. The method according to claim 15, characterized in that The model information includes one or more of the following: a model identifier and model attribute information.

17. The method according to claim 14, characterized in that The method further comprises: Receive model data, where the model data is included in a data packet transmitted via the Xn interface or the NG interface.

18. The method according to claim 14, characterized in that The method further comprises: Sending a first response message, where the first response message includes one or more of the following: confirmation message, objection message, and feedback message.

19. The method according to any one of claims 14 to 18, characterized in that The method further comprises: Send second indication information, where the second indication information is used to indicate PDU session information related to the model.

20. The method according to claim 19, characterized in that The PDU session information related to the model transfer includes: PDU session identifier and status information; The state information is used to indicate that the PDU session identifier is used, used for model transfer, or released.

21. The method according to claim 20, characterized in that The method further comprises: Receive a second response message, the second response message including any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier.

22. An information indication method, characterized in that: The method comprises: Receive second indication information, where the second indication information is used to indicate PDU session information related to the model.

23. The method according to claim 22, characterized in that The PDU session information related to the model transfer includes: PDU session identifier and status information; The state information is used to indicate that the PDU session identifier is used, used for model transfer, or released.

24. The method according to claim 23, characterized in that The method further comprises: Send a second response message, the second response message including any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier information.

25. A communication device, characterized in that: The communication device comprises: The first sending module is used to send first indication information, where the first indication information includes model transfer information, and the model transfer information is used to indicate a state of user plane model transfer.

26. The communication device according to claim 25, characterized in that The device also includes: The first receiving module is used to receive first response information, where the first response information includes one or more of the following: confirmation information, objection information, and feedback information.

27. A communication device, characterized in that: The communication device comprises: The second receiving module is used to receive first indication information, where the first indication information includes model transfer information, and the model transfer information is used to indicate a state of user plane model transfer.

28. The communication device according to claim 27, characterized in that The device also includes: The second sending module is used to send first response information, where the first response information includes one or more of the following: confirmation information, objection information, and feedback information.

29. A communication device, characterized in that: The communication device comprises: The third receiving module is used to receive second indication information, where the second indication information is used to indicate PDU session information related to the model.

30. The communication device according to claim 29, characterized in that The device also includes: The third sending module is used to send a second response information, wherein the second response information includes any one of the following information: confirmation information of the PDU session identifier, objection information of the PDU session identifier, objection information of the PDU session identifier and recommended PDU session identifier information, and recommended PDU session identifier information.

31. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the computer program executes the steps of the method according to any one of claims 1 to 13, or the steps of the method according to any one of claims 14 to 21, or the steps of the method according to any one of claims 22 to 24.

32. A communication device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program executable on the processor, and when the processor executes the computer program, the processor executes the steps of the method described in any one of claims 1 to 13, or executes the steps of the method described in any one of claims 14 to 21, or executes the steps of the method described in any one of claims 22 to 24.

Images