Information transmission method, core network device, communication system, and storage medium

Abstract

The present disclosure relates to an information transmission method, a core network device, a communication system, and a storage medium. The information transmission method comprises: a first core network device receiving first information, wherein the first information is associated with a user plane of a terminal, and the first information is sent by a second core network device, or is sent by the second core network device by means of a third core network device. Therefore, the first core network device can actively obtain user plane information of the terminal, thereby providing a condition for the first core network device to reliably execute a service.

Description

Information transmission method, core network device, communication system and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and particularly relates to an information transmission method, a core network device, a communication system and a storage medium. BACKGROUND

[0002] A user plane in a communication system can be used to transmit user data between a terminal and a core network device. When the terminal activates a 3rd Generation Partnership Project (3GPP) Packet Switching (PS) Data Off function, the user plane will no longer be used to transmit network protocol (Internet Protocol, IP) data packets related to a 3GPP network, unless the data belongs to 3GPP PS Data Off Exempt Services related data.

[0003] SUMMARY

[0004] Embodiments of the present disclosure provide an information transmission method, a core network device, a device, a chip system, a storage medium, a computer program and a computer program product, which can be applied in the technical field of communication, and are used to solve the technical problem of how an LMF obtains the reachability of a user plane of a terminal when the terminal does not request to establish a user plane connection.

[0005] The present disclosure provides an information transmission method, a core network device, a communication system and a storage medium.

[0006] According to a first aspect of the embodiments of the present disclosure, an information transmission method is provided, which is executed by a first core network device, and includes: receiving first information, wherein the first information is associated with a user plane of a terminal, and the first information is sent by a second core network device or by the second core network device through a third core network device.

[0007] According to a second aspect of the embodiments of the present disclosure, an information transmission method is provided, which is executed by a second core network device, and includes: sending first information to a first core network device, or sending the first information to the first core network device through a third core network device, wherein the first information is associated with a user plane of a terminal.

[0008] According to a third aspect of the embodiments of the present disclosure, a method for information transmission is provided, which is performed by a third core network device, and includes: receiving first information sent by a second core network device, and sending the first information to a first core network device, wherein the first information is associated with a user plane of the terminal.

[0009] According to a fourth aspect of the embodiments of the present disclosure, a method for information transmission is provided, which is performed by a communication system, and includes: sending, by a second core network device, first information to a first core network device, or sending, by the second core network device, the first information to the first core network device through a third core network device, wherein the first information is associated with a user plane of the terminal.

[0010] According to a fifth aspect of the embodiments of the present disclosure, a first core network device is provided, which includes: a transceiver module, configured to receive first information, wherein the first information is associated with a user plane of a terminal, and the first information is sent by a second core network device or sent by the second core network device through a third core network device.

[0011] According to a sixth aspect of the embodiments of the present disclosure, a second core network device is provided, which includes: a transceiver module, configured to send first information to a first core network device, or send the first information to the first core network device through a third core network device, wherein the first information is associated with a user plane of the terminal.

[0012] According to a seventh aspect of the embodiments of the present disclosure, a third core network device is provided, which includes: a transceiver module, configured to receive first information sent by a second core network device, and send the first information to a first core network device, wherein the first information is associated with a user plane of the terminal.

[0013] According to an eighth aspect of the embodiments of the present disclosure, a communication device is provided, which includes: one or more processors; and wherein the processor is configured to invoke instructions to cause the communication device to perform the information transmission method of any one of the first aspect, the second aspect or the third aspect.

[0014] According to a ninth aspect of the embodiments of the present disclosure, a communication system is provided, which includes a first core network device, a second core network device and a third core network device, wherein the first core network device is configured to implement the information transmission method of the first aspect, the second core network device is configured to implement the information transmission method of the second aspect, and the third core network device is configured to implement the information transmission method of the third aspect.

[0015] According to a tenth aspect of the embodiments of the present disclosure, a storage medium is provided, which stores instructions, and wherein when the instructions run on a communication device, the communication device performs the information transmission method of any one of the first aspect, the second aspect or the third aspect.

[0016] According to a first aspect of the embodiments of the present disclosure, a method for information transmission is provided. The method comprises: a first core network device receiving a first message from a first terminal device, the first message comprising a first identifier of the first terminal device and a first identifier of a second terminal device; the first core network device determining a first identifier of the first core network device based on the first identifier of the first terminal device and the first identifier of the second terminal device; the first core network device sending a second message to the second terminal device, the second message comprising the first identifier of the first terminal device, the first identifier of the second terminal device and the first identifier of the first core network device. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background art, the drawings needed to be used in the embodiments of the present disclosure or the background art will be described below.

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background art, the drawings needed to be used in the embodiments of the present disclosure or the background art will be described below.

[0019] FIG. 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure;

[0020] FIG. 2A is a schematic diagram of an interaction of a method for information transmission according to an embodiment of the present disclosure;

[0021] FIG. 2B is a schematic diagram of an interaction of a method for information transmission according to an embodiment of the present disclosure;

[0022] FIGS. 3A-3C are schematic diagrams of a flow of a method for information transmission according to another embodiment of the present disclosure;

[0023] FIGS. 4A-4C are schematic diagrams of a flow of a method for information transmission according to yet another embodiment of the present disclosure;

[0024] FIGS. 5A-5C are schematic diagrams of a flow of a method for information transmission according to yet another embodiment of the present disclosure;

[0025] FIGS. 6A-6B are schematic diagrams of an interaction of a method for information transmission according to yet another embodiment of the present disclosure;

[0026] FIGS. 7A-7B are schematic diagrams of an interaction of a method for information transmission according to an embodiment of the present disclosure;

[0027] FIG. 8A is a schematic diagram of a structure of a first core network device according to an embodiment of the present disclosure;

[0028] FIG. 8B is a schematic diagram of a structure of a second core network device according to another embodiment of the present disclosure;

[0029] FIG. 8C is a schematic diagram of a structure of a third core network device according to another embodiment of the present disclosure;

[0030] FIG. 9A is a schematic diagram of a structure of a communication device according to an embodiment of the present disclosure;

[0031] FIG. 9B is a structural schematic diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] The present disclosure provides an information transmission method, a core network device, a communication system, and a storage medium.

[0033] In a first aspect, an information transmission method is provided, which is performed by a first core network device. The method comprises:

[0034] receiving first information associated with a user plane of a terminal, wherein the first information is sent by a second core network device or sent by the second core network device through a third core network device.

[0035] In the above embodiment, the first core network device can directly or indirectly receive the first information associated with the user plane of the terminal from the second core network device, so that the first core network device can obtain the user plane information of the terminal when the terminal does not actively establish a user plane connection. This provides a reliable basis for the first core network device to use the user plane and improves the reliability of services based on the user plane.

[0036] In some embodiments of the first aspect, before receiving the first information, the method further comprises:

[0037] sending a first request to the second core network device, or sending the first request to the second core network device through the third core network device.

[0038] The first request is used to subscribe to an event associated with the user plane of the terminal.

[0039] In the above embodiment, the first core network device can directly or indirectly subscribe to the event associated with the user plane from the second core network device, which improves the flexibility of obtaining the user plane information.

[0040] In some embodiments of the first aspect, the method further comprises:

[0041] receiving a first response sent by the second core network device, or receiving the first response sent by the second core network device through the third core network device, wherein the first response is used to indicate a first subscription result.

[0042] In the above embodiment, the second core network device can directly or indirectly send the subscription result to the first core network device, so that the first core network device and the second core network device have the same understanding of the subscription result, which provides a condition for reliable execution of services on the first core network device side.

[0043] In some embodiments combined with the first aspect, in some embodiments, the first response comprises a report of a first event associated with a user plane of the terminal.

[0044] In the above embodiments, after receiving the first request, if the event associated with the user plane can be detected, the second core network device can send the first report of the event associated with the user plane to the first core network device through the first response, thereby shortening the waiting time for the first core network device to obtain the user plane reachability of the terminal.

[0045] In some embodiments combined with the first aspect, the first request comprises at least one of the following: an identifier of the terminal, a data network name (DNN), single network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identifier, a target event subscribed by the first request, an event identifier, an event filter, and event report information.

[0046] In the above embodiments, the first request can comprise multi-dimensional information, thereby providing conditions for the second core network device to accurately determine the event subscribed by the first core network device or the information queried.

[0047] In some embodiments combined with the first aspect, in some embodiments, the event identifier is an identifier of any one of the following:

[0048] User plane reachability of the terminal;

[0049] User plane availability of the terminal;

[0050] User plane status of the terminal;

[0051] Terminal reachability;

[0052] 3rd Generation Partnership Project (3GPP) packet switched (PS) Data Off state of the terminal;

[0053] 3GPP PS Data Off state change of the terminal;

[0054] User plane status information of the terminal;

[0055] PDU session creation, modification, or release request.

[0056] In the above embodiments, the event identifier can be multiple information, thereby improving the flexibility of the event identifier.

[0057] In some embodiments combined with the first aspect, in some embodiments, a parameter type in the event filter is associated with the user plane, and a parameter value in the event filter is used to indicate any one of the following: a reachability state change of the user plane of the terminal, downlink traffic reaching the user plane of the terminal, a user plane state change, and a 3GPP PS Data Off state change.

[0058] In the above embodiment, through the extended event filter, not only the accuracy of the detected event can be guaranteed, but also the condition for multiplexing the identification of the existing event is provided.

[0059] In some embodiments of the first aspect, in some embodiments, the target event includes at least one of:

[0060] a terminal reachability event;

[0061] a terminal user plane reachability event;

[0062] a terminal user plane availability event;

[0063] a terminal user plane status event;

[0064] a terminal user plane status information event;

[0065] a 3GPP PS Data Off state change event of the terminal;

[0066] a 3GPP PS Data Off state of the terminal,

[0067] a PDU session creation, modification or release request.

[0068] In the above embodiment, the first core network device can subscribe to multiple events associated with the user plane of the terminal from the second core network device, thereby improving the flexibility of the subscription request implementation.

[0069] In some embodiments of the first aspect, in some embodiments, before sending the first request, further comprising:

[0070] determining to use a location service user plane protocol LCS-UPP for positioning service, sending, through the third core network device, a second request to the terminal, the second request being used to request to establish a user plane connection;

[0071] receiving, through the third core network device, a second response sent by the terminal, wherein the second response is used to indicate that the user plane connection establishment fails.

[0072] In some embodiments of the first aspect, in some embodiments, the second response includes a user plane connection establishment failure reason, and the user plane connection establishment failure reason is any one of: a PDU session failure, a transport layer security TLS connection failure, a LCS-UP connection binding failure, a user plane unavailability, a protocol error, and other reasons.

[0073] In the above embodiment, the second response can indicate multiple reasons for the user plane connection failure, thereby providing accurate and reliable basis for the first core network device to perform the positioning service.

[0074] In some embodiments of the first aspect, the first information includes at least one of the following: an event identifier, a target event, 3rd Generation Partnership Project, 3GPP, Packet Switched, PS, Data Off status indication information, a Packet Data Unit, PDU, session identifier, a status of a PDU session, an allowed PDU session status, and a timestamp.

[0075] In the above embodiment, the first information includes multi-dimensional information, thereby providing reliable basis for the first core network device to accurately determine the user plane reachability of the terminal.

[0076] In some embodiments of the first aspect, the method further includes:

[0077] The first information indicates any of the following, and the stored user plane status of the terminal is updated: a change in the user plane status of the terminal, the user plane of the terminal is available, a change in 3GPP PS Data Off of the terminal, 3GPP PS Data Off of the terminal is deactivated, a PDU session of the terminal is established, a PDU session of the terminal is released, and a PDU session of the terminal is modified.

[0078] In the above embodiment, when the first core network device determines the change in the user plane status of the terminal, the stored user plane status of the terminal can be updated, thereby providing accurate basis for the first core network device to perform the user plane service and improving the reliability of the service of the first core network device.

[0079] In a second aspect, the embodiments of the present disclosure provide a method for transmitting information, executed by a second core network device; the method includes:

[0080] The first information is sent to the first core network device, or the first information is sent to the first core network device through a third core network device, wherein the first information is associated with the user plane of the terminal.

[0081] In some embodiments of the second aspect, before the first information is sent, the method further includes:

[0082] The first request is received, wherein the first request is sent by the first core network device or by the first core network device through the third core network device, and the first request is used to subscribe to an event associated with the user plane of the terminal.

[0083] In some embodiments of the second aspect, the method further includes:

[0084] sending a first response to the first core network device, or sending the first response to the first core network device through the third core network device, the first response being used to indicate a subscription result.

[0085] In combination with some embodiments of the second aspect, in some embodiments, the first response includes a report of a first event associated with a user plane of the terminal.

[0086] In combination with some embodiments of the second aspect, in some embodiments, the first request includes at least one of the following: an identity of the terminal, a data network name (DNN), a single-network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identity, a target event of the first request subscription, an identity of the event, an event filter, and event report information.

[0087] In combination with some embodiments of the second aspect, in some embodiments, the identity of the event is an identity of any one of the following:

[0088] a user plane reachability of the terminal;

[0089] a user plane availability of the terminal;

[0090] a user plane status of the terminal;

[0091] a reachability of the terminal;

[0092] a 3rd generation partnership project (3GPP) packet switched (PS) data off (Data Off) status of the terminal;

[0093] a change of the 3GPP PS Data Off status of the terminal;

[0094] a user plane status information of the terminal;

[0095] a PDU session creation, modification, or release request.

[0096] In combination with some embodiments of the second aspect, in some embodiments, a parameter type in the event filter is associated with the user plane, and a parameter value in the filter of the event is used to indicate any one of the following: a reachability state change of the user plane, a downlink traffic reachability of the user plane of the terminal, a user plane status change, and a 3GPP PS Data Off status change.

[0097] In combination with some embodiments of the second aspect, in some embodiments, the target event includes at least one of the following:

[0098] a reachability event of the terminal;

[0099] a user plane reachability event of the terminal;

[0100] a user plane availability event of the terminal;

[0101] terminal user plane status event;

[0102] terminal user plane status information event;

[0103] terminal 3GPP PS Data Off status change event;

[0104] terminal 3GPP PS Data Off status,

[0105] PDU session creation, modification or release request.

[0106] In some embodiments in combination with the second aspect, the first information comprises at least one of: an event identity, a target event, 3rd Generation Partnership Project, 3GPP, Packet Switched, PS, Data Off status indication information, a packet data unit, PDU, session identity, a status of the PDU session, allowed PDU session status, a timestamp.

[0107] In some embodiments in combination with the second aspect, the method further comprises:

[0108] detecting an event of a user plane association of the terminal.

[0109] In some embodiments in combination with the second aspect, detecting the event of the user plane association of the terminal comprises:

[0110] receiving a second message sent by the third core network device, wherein the second message comprises an identity of the third core network device, an identity of the terminal, and second information associated with a user plane of the terminal.

[0111] detecting the event of the user plane association of the terminal based on the second information.

[0112] In some embodiments in combination with the second aspect, the second information comprises at least one of: a PDU session identity, an old PDU session identity, a PDU session establishment request, a PDU session release request, a PDU session modification request, a Session and Service Continuity, SSC, mode, an extended protocol configuration option, a 3GPP PS Data Off status, a PDU session status, and allowed PDU session status.

[0113] In some embodiments in combination with the second aspect, detecting the event of the user plane association of the terminal comprises at least one of:

[0114] detecting that the terminal reports its 3GPP PS Data Off status, and determining that the event of the user plane association of the terminal is detected;

[0115] detecting that the terminal requests to establish, modify and / or release a PDU session, determining an event of detecting that a user plane association of the terminal is established.

[0116] In a third aspect, the embodiments of the present disclosure provide a method for information transmission, executed by a third core network device, comprising:

[0117] receiving first information sent by a second core network device, and sending the first information to a first core network device, wherein the first information is associated with a user plane of the terminal.

[0118] In combination with some embodiments of the third aspect, in some embodiments, before the sending the first information to the first core network device, the method further comprises:

[0119] receiving a first request sent by the first core network device, and sending the first request to the second core network device, wherein the first request is used to subscribe to an event associated with the user plane of the terminal.

[0120] In combination with some embodiments of the third aspect, in some embodiments, the method further comprises:

[0121] receiving a first response sent by the second core network device, and sending the first response to the first core network device, wherein the first response is used to indicate a subscription result.

[0122] In combination with some embodiments of the third aspect, in some embodiments, the first response comprises a report of a first event associated with the user plane of the terminal.

[0123] In combination with some embodiments of the third aspect, in some embodiments, the first request comprises at least one of the following: an identifier of the terminal, a data network name (DNN), a single network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identifier, a target event subscribed by the first request, an event identifier, a filter of the event, and event report information.

[0124] In combination with some embodiments of the third aspect, in some embodiments, the event identifier is an identifier of any one of the following:

[0125] user plane reachability of the terminal;

[0126] user plane availability of the terminal;

[0127] user plane status of the terminal;

[0128] terminal reachability of the terminal;

[0129] 3rd generation partnership project (3GPP) packet switched (PS) data off status of the terminal.

[0130] Terminal 3GPP PS Data Off state change;

[0131] Terminal user plane status information;

[0132] PDU session creation, modification or release request.

[0133] In some embodiments in combination with the third aspect, in some embodiments, the parameter type in the event filter is associated with a user plane, and the parameter value in the filter of the event is used to indicate any one of: a reachability state change of a user plane of the terminal, downlink traffic reachability of a user plane of the terminal, a user plane state change of the terminal, a 3GPP PS Data Off state change of the terminal.

[0134] In some embodiments in combination with the third aspect, in some embodiments, the target event includes at least one of:

[0135] Terminal reachability event;

[0136] Terminal user plane reachability event;

[0137] Terminal user plane availability event;

[0138] Terminal user plane status event;

[0139] Terminal user plane status information event;

[0140] Terminal 3GPP PS Data Off state change event;

[0141] Terminal 3GPP PS Data Off state,

[0142] PDU session creation, modification or release request.

[0143] In some embodiments in combination with the third aspect, in some embodiments, the method further includes:

[0144] receiving a third message sent by the terminal, wherein the third message includes an identity of the terminal and third information associated with a user plane of the terminal;

[0145] detecting, based on the third information, an event associated with the user plane of the terminal;

[0146] sending a second message to the second core network device, wherein the second message includes an identity of the third core network device, an identity of the terminal and second information, and the second information is associated with the user plane of the terminal.

[0147] In some embodiments of the third aspect, in some embodiments, the detecting, based on the second information, the event associated with the user plane of the terminal comprises:

[0148] detecting that the terminal reports a 3GPP PS data off state, determining that the event associated with the user of the terminal is detected;

[0149] detecting that the terminal requests to establish, modify and / or release a PDU session, determining that the event associated with the user of the terminal is detected.

[0150] In some embodiments of the third aspect, in some embodiments, the third message is any one of the following:

[0151] an uplink non-access stratum transmission message;

[0152] a registration request message;

[0153] a service request message;

[0154] a PDU session creation request message;

[0155] a PDU session modification request message;

[0156] a PDU session release request message.

[0157] In some embodiments of the third aspect, in some embodiments, the third information and the second information each comprises at least one of the following: an old PDU session identifier, a PDU session establishment request, a PDU session release request, a PDU session modification request, a session and service continuity indication (SSC), an extended protocol configuration option, a 3GPP PS Data Off state, a PDU session state, and an allowed PDU session state.

[0158] In a fourth aspect, the embodiments of the present disclosure provide a method for transmitting information, executed by a communication system, the method comprising: sending, by a second core network device, first information to a first core network device, or sending, by the second core network device through a third core network device, the first information to the first core network device, wherein the first information is associated with a user plane of a terminal.

[0159] In a fifth aspect, the embodiments of the present disclosure provide a first core network device, comprising:

[0160] a transceiver, configured to receive first information, wherein the first information is associated with a user plane of a terminal, and the first information is sent by a second core network device or sent by the second core network device through a third core network device.

[0161] In a sixth aspect, the embodiments of the present disclosure provide a second core network device, comprising:

[0162] transmit, to the first core network device, first information, or transmit, to the first core network device via the third core network device, the first information, wherein the first information is associated with a user plane of the terminal.

[0163] In a seventh aspect, an embodiment of the present disclosure provides a third core network device, which comprises:

[0164] a transceiver configured to receive first information transmitted by a second core network device and transmit the first information to a first core network device, wherein the first information is associated with a user plane of the terminal.

[0165] In an eighth aspect, an embodiment of the present disclosure provides a communication device, which comprises:

[0166] one or more processors;

[0167] The processor is configured to perform the information transmission method in any one of the first aspect, the second aspect, or the third aspect.

[0168] In a ninth aspect, an embodiment of the present disclosure provides a communication system, which comprises a first core network device, a second core network device, and a third core network device, wherein the first core network device is configured to implement the information transmission method in the first aspect, the second core network device is configured to implement the information transmission method in the second aspect, and the third core network device is configured to implement the information transmission method in the third aspect.

[0169] In a tenth aspect, an embodiment of the present disclosure provides a storage medium, which stores instructions, and when the instructions are executed on a communication device, the communication device performs the information transmission method in any one of the first aspect, the second aspect, or the third aspect.

[0170] In an eleventh aspect, an embodiment of the present disclosure provides a computer program product, which comprises a computer program, and when the computer program is executed by a processor, the computer program implements the information transmission method in any one of the first aspect, the second aspect, or the third aspect.

[0171] It can be understood that the above information transmission method, first core network device, second core network device, third core network device, communication device, chip system, storage medium, computer program, and computer program product are all used to execute the method provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved are referred to the beneficial effects in the corresponding method, which will not be described here.

[0172] The embodiments of the present disclosure provide information transmission methods, core network devices, communication systems, and storage media. In some embodiments, the information transmission method can be replaced by the information processing method, the communication method, and other terms. The sensing device can be replaced by the information processing device, the communication device, and other terms. The information processing system and the communication system can be replaced by each other.

[0173] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, some or all steps of different embodiments can be combined arbitrarily, an embodiment can be combined with the optional implementation of other embodiments.

[0174] In the embodiments of the present disclosure, the terms and / or descriptions between the embodiments are consistent and can be referred to each other if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0175] The terms used in the embodiments of the present disclosure are only for the purpose of describing the specific embodiments, and not as a limitation on the present disclosure.

[0176] In the embodiments of the present disclosure, unless otherwise specified, the elements expressed in singular form, such as "one", "a", "the", "above", "said", "preceding", "this", etc., can represent "one and only one", or "one or more", "at least one", etc. For example, in the case of using articles such as "a", "an", "the" in English, the noun after the article can be understood as singular expression, or as plural expression.

[0177] In the embodiments of the present disclosure, "a plurality of" means two or more.

[0178] In some embodiments, the terms "at least one of", "one or more", "a plurality of", "multiple", and the like can be replaced by each other.

[0179] In some embodiments, "at least one of A, B", "A and / or B", "in one case A, in another case B", "responsive to case A, responsive to case B" and the like, can be interpreted to include both cases, A and B, in some embodiments, A (A is performed regardless of B), in some embodiments, B (B is performed regardless of A), in some embodiments, selected from the group consisting of A and B (the selection between A and B is an option), in some embodiments, A and B (both A and B are performed).

[0180] In some embodiments, "A or B" and the like, can be interpreted to include both cases, A and B, in some embodiments, A (A is performed regardless of B), in some embodiments, B (B is performed regardless of A), in some embodiments, selected from the group consisting of A and B (the selection between A and B is an option).

[0181] In some embodiments, the prefix words "first", "second" and the like in the disclosure do not limit the position, order, priority, number or content of the described objects, and the description of the described objects should be understood in the context of the claims or embodiments, and should not be construed as redundant limitations. For example, the described object is "field", and the ordinal words before "field" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified by them are in the same message or not, nor do they limit the order of "first field" and "second field". For another example, the described object is "level", and the ordinal words before "level" in "first level" and "second level" do not limit the priority between "levels". For another example, the number of described objects is not limited by ordinal words, and can be one or more. For example, "first device", where the number of "devices" can be one or more. In addition, objects modified by different prefix words can be the same or different, for example, the described object is "device", and "first device" and "second device" can be the same device or different devices, and their types can be the same or different; for another example, the described object is "information", and "first information" and "second information" can be the same information or different information, and their contents can be the same or different.

[0182] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0183] In some embodiments, the terms "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0184] In some embodiments, the terms "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", "above", and the like can be replaced with each other, and the terms "less than", "less than or equal to", "not greater than", "fewer than", "fewer than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", "below", and the like can be replaced with each other.

[0185] In some embodiments, the apparatuses and devices can be interpreted as physical or virtual, and their names are not limited to the names described in the embodiments, and in some cases can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", and the like.

[0186] In some embodiments, "network" can be interpreted as an apparatus included in the network, for example, an access network device, a core network device, and the like.

[0187] In some embodiments, an “access network device (AN device)” can also be referred to as a “radio access network device (RAN device),” a “base station (BS),” a “radio base station,” a “fixed station,” and in some embodiments can also be understood as a “node,” an “access point,” a “transmission point (TP),” a “reception point (RP),” a “transmission / reception point (TRP),” a “panel,” an “antenna panel,” an “antenna array,” a “cell,” a “macro cell,” a “small cell,” a “femto cell,” a “pico cell,” a “sector,” a “cell group,” a “serving cell,” a “carrier,” a “component carrier,” a “bandwidth part (BWP),” and the like.

[0188] In some embodiments, a "terminal" or "terminal device" can be referred to as a "user equipment" (UE), a "user terminal," a "mobile station" (MS), a "mobile terminal" (MT), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, and / or the like.

[0189] In some embodiments, data, information and / or the like can be obtained in compliance with laws and regulations of a country where a location is situated.

[0190] In some embodiments, data, information and / or the like can be obtained after consent of a user is obtained.

[0191] FIG. 1 is an architecture diagram of a communication system, according to an embodiment of the present disclosure. As shown in FIG. 1, the communication system 100 can include a terminal 101, a core network device 102, and an access network device 103.

[0192] In some embodiments, the terminal 101 can include at least one of a mobile phone, a wearable device, an Internet of Things device, a communication-capable automobile, a smart automobile, a tablet (Pad), a wireless-transmitting computer, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and the like, but is not limited thereto.

[0193] In some embodiments, the core network device 102 can be one device including the first network element, the second network element, the third network element, and the like, or can be a plurality of devices or device groups including all or part of the first network element, the second network element, the third network element, and the like. The network element can be virtual or physical. The core network includes at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0194] In some embodiments, the first network element is, for example, a Location Management Function (LMF) network element, and the name is not limited thereto.

[0195] In some embodiments, the first network element is configured to be responsible for location management of the terminal, including calculation and feedback of location information, management of a positioning process, provision of assistance data, and the like.

[0196] In some embodiments, the first network element is, for example, a Sensing Function (SF) network element, or can be any network element capable of implementing a sensing function, and the name is not limited thereto.

[0197] In some embodiments, the SF network element, which can be, for example, SF-C, SF-U, SF-D. Among them, SF-C can send and receive sensing information through the control plane, and collect and process sensing measurement data. SF-U can send and receive sensing information through the user plane, and collect and process sensing measurement data. SF-D can send and receive sensing information through the data plane, and collect and process sensing measurement data. SF-C and / or SF-U and / or SF-D can be used in combination. SF-C, SF-U, and SF-D can be different modules in the SF network element, or SF-C, SF-U, and SF-D can be different SF network elements, and no limitation is made thereto.

[0198] In some embodiments, the second network element is, for example, a session management function (SMF) network element, and the name is not limited thereto. The SMF network element is a functional network element on the core side, which can be used to be responsible for processing the establishment, modification and release process of user session, and ensuring that the UE can effectively establish and maintain the data transmission channel.

[0199] In some embodiments, the third network element is, for example, an access and mobility management function (AMF) network element, and the name is not limited thereto. The AMF network element is a logical node functional network element on the core network side, which is the access point of the terminal and the core network control plane, receives all connection and session related information from the user equipment, and performs registration, connection, reachability, and mobility management. In addition, the AMF network element provides a session management message transmission channel for the terminal device and the session management function (SMF) device, and provides authentication and authorization functions when the user accesses.

[0200] In some embodiments, the third network element is used to provide access and mobility management functions.

[0201] In some embodiments, the terminal 101 can be connected with the core network device 102 through an access network device 103, which is optionally a node or device for accessing the terminal to the wireless network, and the access network device 103 can include at least one of an evolved NodeB (eNB) in a 5G communication system, a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open RAN, a Cloud RAN, a base station in other communication systems, an access node in a wireless fidelity (WiFi) system, and the like, but is not limited thereto.

[0202] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of the present disclosure. It can be known by those skilled in the art that, as the system architecture evolves and new business scenarios appear, the technical solutions proposed in the embodiments of the present disclosure are also applicable to similar technical problems.

[0203] The following embodiments of the present disclosure can be applied to the communication system 100 shown in FIG. 1 or part of the subject, but are not limited thereto. The subjects shown in FIG. 1 are exemplary, and the communication system can include all or part of the subjects in FIG. 1, or other subjects other than those in FIG. 1. The number and form of each subject is arbitrary, and the connection relationship between the subjects is exemplary. The subjects can be connected or not connected, and the connection can be in any manner, can be direct connection or indirect connection, and can be wired connection or wireless connection.

[0204] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other communication methods, next-generation system expanded based on them, or the like. Further, a plurality of systems can be combined (for example, combination of LTE or LTE-A and 5G, or the like).

[0205] Optionally, the process of establishing a user plane connection between the terminal 101 and the core network device 102 can include the following steps:

[0206] 1. The UE sends a user plane connection setup request to the LMF via the AMF, requesting to establish a user plane connection with the LMF. For the user plane connection setup procedure initiated by the network, this step is skipped.

[0207] 2. For the user plane connection setup procedure initiated by the network, the LMF sends a user plane connection setup command to the UE via the AMF. Upon receiving the user plane connection setup command, the UE shall establish a Packet Data Unit (PDU) session for the LCS (Location Services) - UPP (User Plane Protocol) if no PDU session is established. If a PDU session is already established for the LCS-UPP, this operation is skipped.

[0208] 3. The UE performs a TLS (Transport Layer Security) connection resume procedure with the LMF.

[0209] 4. The UE and the LMF perform a TLS connection binding procedure.

[0210] a. The UE sends a user plane connection binding request to the LMF via the established TLS connection.

[0211] b. The LMF binds the TLS connection with the UE identity.

[0212] c. If successful, the LMF sends a user plane connection binding accept message to the UE via the TLS connection; for the failure case, the LMF sends a user plane connection binding reject message to the UE.

[0213] 5. If the UE receives the user plane connection binding accept message, the UE sends a user plane connection setup complete message to the LMF via the AMF.

[0214] 6. If the UE fails to establish the PDU session (steps 3-4 will be skipped), or the UE fails to establish the TLS connection (step 4 will be skipped), or the UE receives the user plane connection binding reject message, the UE shall send a user plane connection setup failure message to the LMF via the AMF. In the user plane connection setup failure message, a failure cause information element (IE) shall be included, which can be set to one of the following cause values:

[0215] #1 for indicating PDU session failure, #2 for indicating TLS connection failure, #3 for indicating LCS-UP connection binding failure, #4 for indicating User plane not available, or #111 for indicating Protocol error, or other unspecified cause.

[0216] If the UE fails to use an established PDU session for LCS-UP or fails to establish a PDU session for LCS-UP, the UE shall send a user plane connection establishment failure message containing the cause value "#1".

[0217] If the UE fails to establish a TLS connection for LCS-UP, the UE shall send a user plane connection establishment failure message containing the cause value "#2".

[0218] Upon receiving the LCS-UP connection binding reject message from the LMF, the UE shall send a user plane connection establishment failure message containing the cause value "#3" to acknowledge the binding failure received from the LMF.

[0219] If the UE determines that the user plane is not available, e.g., due to the UE setting the status of the 3GPP PS Data Off function to "active", the UE shall send a user plane connection establishment failure message containing the cause value "#4".

[0220] Upon receiving the user plane connection establishment failure message from the UE, if the cause value "#4" is not contained in the user plane connection establishment failure message, the LMF can perform a network initiated user plane connection creation procedure.

[0221] If the cause value "#4" is contained in the user plane connection establishment failure message, the LMF shall not initiate a network initiated user plane connection creation procedure and can consider using other available positioning solutions if the location service is still needed until the LMF receives a user plane connection establishment request message from the UE.

[0222] For the newly added cause value, the UE can report its user plane not available status to the LMF through the user plane connection establishment failure message. In order to update the UE's user plane status, the UE needs to send a user plane connection establishment request to the LMF.

[0223] However, the UE sends the user plane connection establishment request only when the UE considers that the user plane needs to be used to transmit uplink data. If the user plane status of the UE changes, but the UE considers using the control plane to transmit uplink data, or the user plane status of the UE changes without the need to send uplink data, the UE can not send the user plane connection establishment request message. At this time, the LMF cannot obtain the user plane status of the UE, and considers that the user plane positioning of the UE is always unavailable once the UE reports that its user plane connection is unavailable.

[0224] The information transmission method provided by the embodiments of the present disclosure can be used for the communication system 100, and the embodiments of the present disclosure take the case that there is an interface between the first core network device and the second core network device as an example for description. The method comprises the following steps:

[0225] FIG. 2A is an interaction schematic diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG. 2A, the embodiments of the present disclosure relate to an information transmission method, which can be used for the communication system 100. The embodiments of the present disclosure take the case that there is an interface between the first core network device and the second core network device as an example for description. The method comprises the following steps:

[0226] In step S2101, the first core network device determines to use LCS-UPP for positioning service, and sends a second request to the terminal through the third core network device.

[0227] In some embodiments, the first core network device can be, for example, a Location Management Function (LMF) network element, or can also be any network element capable of implementing the location management function.

[0228] In some embodiments, the first core network device can be, for example, a Sensing Function (SF) network element, or can also be any network element capable of implementing the sensing function.

[0229] In some embodiments, the third core network device can be, for example, an Access and Mobility Management Function (AMF) network element, or can also be any network element capable of implementing the access and mobility management function. The third core network device can also be, for example, an SF network element, or can also be any network element capable of storing user context, and no limitation is made in this regard.

[0230] In some embodiments, the second request is used to request to establish a UP connection.

[0231] In some embodiments, the second request can be, for example, a user plane connection establishment command.

[0232] In some embodiments, the first core network device can transmit the second request to the third core network device through a Namf_communication_N1N2TransferMessage message.

[0233] In some embodiments, the third core network device can send the second request to the terminal through a downlink (DL) Non-Access Stratum (NAS) transport message, for example, a DL NAS TRANSPORT message.

[0234] In some embodiments, the third core network device can send the second request to the terminal through the access network device.

[0235] In step S2102, the first core network device receives the second response sent by the terminal through the third core network device.

[0236] In some embodiments, the terminal receives the second request and performs a user plane connection establishment procedure.

[0237] In some embodiments, the terminal determines not to perform or cannot perform the user plane connection establishment procedure due to reasons such as unavailability of the user plane, preference for using the control plane for positioning, congestion of the user plane, or insufficient resources of the user plane, and the user plane connection establishment fails.

[0238] In some embodiments, the second response can be used to indicate a user plane connection establishment failure.

[0239] In some embodiments, the second response can include a reason for the user plane connection establishment failure.

[0240] In some embodiments, the reason for the user plane connection establishment failure can be a PDU session failure; or the reason for the user plane connection establishment failure can also be a Transport Layer Security (TLS) connection failure; or the reason for the user plane connection establishment failure can also be a LCS-UP connection binding failure; or the reason for the user plane connection establishment failure can also be unavailability of the user plane; or the reason for the user plane connection establishment failure can also be a protocol error or other reasons, and the present disclosure does not limit the same.

[0241] In some embodiments, if the terminal determines that the user plane is unavailable, for example, due to the UE activating a 3GPP PS data off function, or the terminal prefers to use the control plane for positioning or other positioning methods, or due to congestion of the user plane or insufficient resources of the user plane, the terminal sends a second response containing a corresponding reason value.

[0242] In some embodiments, if the terminal determines that the user plane is not available, for example, due to the UE activating the 3GPP PS data off function, or the terminal prefers control plane positioning or other positioning methods, or due to user plane congestion or insufficient user plane resources, the terminal sends a second response containing a cause value "user plane not available".

[0243] In some embodiments, the terminal can send the second response to the third core network device through an uplink (UL) message, for example, through an UL NAS TRANSPORT message.

[0244] In some embodiments, the third core network device can send the second response to the first core network device by notifying a message delivered on the N1 interface, for example, through Namf_communication_N1MessageNotify.

[0245] In some embodiments, after receiving the user plane connection establishment failure message sent by the terminal, the third core network device can send a user plane connection establishment failure response to the first core network device.

[0246] In some embodiments, after the first core network device receives the second response, it can know that the user plane of the UE is not available, and can store / update the user plane status (i.e. the user plane is not available) or the user plane availability as false (for example, set to 0) as part of the UE context. After that, the first core network device will not start the network-initiated user plane connection establishment process again, and if the location service is still needed, it can consider using other available positioning solutions.

[0247] Step S2103, the first core network device sends a first request to the second core network device.

[0248] In some embodiments, the first request is used to request to subscribe to events associated with the user plane of the terminal.

[0249] In some embodiments, the first request sent by the first core network device to the second core network device can be referred to as a subscription request, which is used to subscribe to events associated with the user plane of the terminal. For example, the first request can be an event exposure service subscription request.

[0250] In some embodiments, the first request can be an event exposure subscription request (Namf_EventExposure_Subscribe request).

[0251] In some embodiments, the first request comprises at least one of the following: an identification (ID) of the terminal, a data network name (DNN), a single network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session ID, a target event to which the first request subscribes, an event ID, an event filter, and event report information.

[0252] In some embodiments, the second core network device can determine the terminal to which the user plane subscribed by the first core network device based on at least one of the following: the ID of the terminal, the DNN, the S-NSSAI, and the PDU session ID.

[0253] In some embodiments, the target event to which the first request subscribes is used to describe which event or events the first core network device subscribes to.

[0254] In some embodiments, the target event can comprise at least one of the following: a terminal reachability event; a terminal user plane reachability event; a terminal user plane availability event; a terminal user plane status event; a terminal user plane status information event; a terminal 3GPP PS Data Off state change event; a terminal 3GPP PS Data Off state, terminal user plane status information; a PDU session creation, modification, or release request.

[0255] In some embodiments, since the PDU session is implemented through the user plane, the target event to which the first core network device subscribes can also include a PDU session associated event. For example, a PDU session establishment event for the terminal, a PDU session release event for the terminal, or a PDU session modification event for the terminal, etc., which are not limited in the present disclosure.

[0256] In some embodiments, the event ID can be an event ID that can indicate when downlink data can be sent to the UE through the user plane, or can also be an event ID that can indicate when the UE can be used to establish a user plane connection.

[0257] In some embodiments, the event ID can be a newly defined event ID. For example, the event ID can be an ID of any of the following: a terminal user plane reachability event; a terminal user plane availability event; a terminal user plane status event; a terminal user plane status information event; a terminal 3GPP PS Data Off state change event; a terminal 3GPP PS Data Off state, terminal user plane status information; a PDU session creation, modification, or release request.

[0258] In some embodiments, the terminal user plane reachability event identity, the terminal user plane availability event identity, the terminal user plane status event identity, the terminal user plane status information event identity, and the terminal's 3GPP PS Data Off state change event, the terminal's 3GPP PS Data Off state event identity, can be any identity distinguished from the existing event identities.

[0259] In some embodiments, the event identity can be an identity of an existing event that is multiplexed. For example, the event identity can be a terminal reachability event identity.

[0260] In some embodiments, when the event identity is a newly defined event identity, the parameter type in the event filter is associated with the user plane. For example, the parameter type can be any parameter applicable to the reachability of the user plane, and the parameter value in the event filter can be used to indicate any of the following: a change in the reachability of the user plane of the terminal, downlink (DL) traffic reaching the user plane of the terminal, a change in the state of the user plane of the terminal, a change in the 3GPP PS Data Off state of the terminal, and the like.

[0261] In some embodiments, when the event identity is an identity of an existing event that is multiplexed, the corresponding event filter needs to be enhanced to be a filter applicable to filtering the user plane reachability event of the UE. For example, when the event identity is a terminal reachability event identity, the corresponding event filter is: parameter type = control plane, value = UE control plane reachability state change or DL traffic UE reachability; parameter type = user plane, value = UE user plane reachability state change or DL traffic UE user plane reachability.

[0262] In some embodiments, in addition to the existing filter: "<parameter type = application identifier, value = application identifier 1>, <parameter type = subscriber permanent identifier (SUPI), value = SUPI 1>", the following new event filters can be added: <parameter type = DNN, value = DNN 1>, <parameter type = S-NSSAI, value = S-NSSAI 1>, <data type = LMF Id, value = LMF Id 1>.

[0263] In some embodiments, the event report information is used to indicate when and / or how the second core network device reports the event report. For example, the event report information can include the frequency of reporting the event report, the number of events reported at a time, the validity period of this subscription, and the like.

[0264] In some embodiments, the first core network device can also send, without sending a user plane connection establishment request (user plane connection establishment command) to the terminal via the third core network device, a first request (such as a Namf_EventExposure_Subscribe request) to the second core network device when a positioning service needs to use the LCS-UPP.

[0265] That is, the first core network device can directly perform S2103 without performing S2101 and S2102.

[0266] In step S2104, the second core network device sends a first response to the first core network device.

[0267] In some embodiments, the first response is used to indicate a subscription result.

[0268] In some embodiments, the first request is used to request to subscribe to an event associated with a user plane of the terminal, and the first response is used to indicate a subscription result.

[0269] In some embodiments, the first response can be an event exposure subscription response (Namf_EventExposure_Subscribe response).

[0270] In some embodiments, the second core network device can send, to the first core network device via the first response, a first report of an event associated with a user plane of the terminal, which is subscribed to in the first request. For example, a first event report including “terminal user plane reachability” is sent.

[0271] In some embodiments, the second core network device can send the first response to the first core network device before the expiration time.

[0272] In some embodiments, the second core network device can determine the expiration time according to a protocol agreement or configuration information.

[0273] In step S2105, a user plane state changes, and the UE sends a third message to the third core network device.

[0274] In the third message, an identifier of the terminal and third information associated with a user plane of the terminal are included.

[0275] In some embodiments, the third message can also include a DNN and an S-NSSAI requested by the terminal.

[0276] In some embodiments, the user plane status change can be from an unavailable state to an available state, or from an available state to an unavailable state.

[0277] In some embodiments, the UE can determine that the user plane is available, because the 3GPP PS data off is "deactivated", or there is no congestion in the user plane of the UE, or the UE determines to use the user plane to transmit data. Thus, the UE can send the third information to the third core network device to indicate that the user plane in the UE is available.

[0278] In some embodiments, the UE can determine that the user plane is unavailable, because the 3GPP PS data off is "activated", or there is congestion in the user plane of the UE, or the UE determines to use other plane than the user plane to transmit data. Thus, the UE can send the second information to the second core network device to indicate that the user plane in the UE is unavailable.

[0279] In some embodiments, the UE can send the third information to the third core network device through the access network device.

[0280] In some embodiments, the UE can send the third information to the third core network device through an uplink (UL) non-access stratum (NAS) message.

[0281] In some embodiments, the terminal can indicate whether the user plane is available (or reachable) to the second core network device by sending an UL NAS TRANSPORT (S-NSSAI(s), UE registered DNN, PDU session identity, old PDU session identity, PDU session establishment request or PDU session modification request or PDU session release request (PDU session identity), SSC mode, extended protocol configuration options (3GPP PS Data Off)) to the second core network device.

[0282] In some embodiments, the terminal can send the third information to the third core network device through a registration request (Registration request) or a service request (Service Request) message. For example, the terminal can include an indication of the reachability of the user plane of the terminal and / or an indication of the reachability of the terminal in the above message.

[0283] In some embodiments, the terminal can indicate the state of the 3GPP PS data off in the above message, such as indicating that the state of the 3GPP PS data off is in an activated state, or indicating that the state of the 3GPP PS data off is in a deactivated state.

[0284] In some embodiments, the terminal can indicate whether the user plane in the UE is available or not to the second core network device by including the 3GPP PS Data Off status in the allowed PDU session status IE in the registration request or the service request.

[0285] In some embodiments, the terminal can send the third information to the third core network device by any of the PDU session establishment request, the PDU session modification request, and the PDU session release request. For example, the terminal can include the indication of the 3GPP PS Data Off status in the extended protocol configuration options IE in the above requests.

[0286] In some embodiments, the third information can include at least one of the following: the PDU session identity, the old PDU session identity, the PDU session establishment request, the PDU session release request, the PDU session modification request, the Session and Service Continuity (SSC) mode, the extended protocol configuration options, the 3GPP PS Data Off status, the PDU session status, and the allowed PDU session status.

[0287] In some embodiments, the PDU session establishment request, the PDU session release request, and the PDU session modification request can further include the PDU session identity that the terminal requests to establish, release, or modify, so that the third core network device can directly send the PDU session establishment request, the PDU session release request, and the PDU session modification request to the second core network device.

[0288] In step S2106, the third core network device sends a second message to the second core network device.

[0289] In some embodiments, the second message is used to inform the second core network device of the terminal-related information received by the third core network device.

[0290] In some embodiments, the second message includes the identity of the third core network device, the identity of the terminal, and the second information, and the second information is associated with the user plane of the terminal.

[0291] In some embodiments, the second information can include at least one of the following: the PDU session identity, the old PDU session identity, the PDU session establishment request, the PDU session release request, the PDU session modification request, the Session and Service Continuity (SSC) mode, the extended protocol configuration options, the 3GPP PS Data Off status, the PDU session status, and the allowed PDU session status.

[0292] In some embodiments, after receiving the third message sent by the terminal, the third core network device can first detect the event associated with the user plane of the terminal. And after detecting the event associated with the user plane of the terminal, the second message is sent to the second core network device.

[0293] In some embodiments, the event associated with the user plane of the terminal can be at least one of: reachability event, terminal user plane reachability event, terminal user plane availability event, terminal user plane status event, terminal user plane status information event, 3GPP PS Data Off state of the terminal, and terminal user plane status information.

[0294] In some embodiments, the third core network device can determine that the event associated with the user plane of the terminal is detected in a case that the terminal reports its 3GPP PS Data Off state.

[0295] In some embodiments, the third core network device can determine that the event associated with the user plane of the terminal is detected in a case that the third message containing 3GPP PS Data Off is received, for example, UL NAS TRANSPORT (3GPP PS Data Off) is received.

[0296] In some embodiments, the implementation of the parameters that can be contained in the UL NAS TRANSPORT can refer to the related description of S2105 above, and will not be repeated here.

[0297] In some embodiments, the third core network device can determine that the event associated with the user plane of the terminal is detected in a case that the terminal requests to establish, modify and / or release a PDU session.

[0298] In some embodiments, the second core network device can determine that the event associated with the user plane of the terminal is detected in a case that a message containing PDU session establishment, modification and / or release PDU session or registration request or service request is received.

[0299] In some embodiments, the implementation of the parameters contained in the registration request or service request can refer to the related description of S2105 above, and will not be repeated here.

[0300] In some embodiments, the third core network device can determine that the user plane of the terminal (or the terminal) is available or reachable in a case that the terminal reports that it has deactivated the 3GPP PS Data Off function, or in a case that the terminal requests to establish, modify or release a PDU session. Therefore, the second message can be sent to the second core network device.

[0301] In some embodiments, after detecting the event of the user plane association of the terminal, the third core network device can further interact with the SMF to inform the SMF of the information. For example, the third core network device can inform the second core network device of the received information through an Nsmf_PDUSession_CreateSMContext message or an Nsmf_PDU Session_UpdateSMContext message.

[0302] In some embodiments, in the interaction with the SMF, the third core network device can send at least one of the following information to the SMF: DNN, S-NSSAI, PDU session ID, old PDU session ID, PDU session establishment request / PDU session modification request / PDU session release request.

[0303] In some embodiments, the second message can be, for example, an Nsmf_PDUSession_CreateSMContext / Nsmf_PDU Session_UpdateSMContext (DNN, S-NSSAI, PDU session identifier, old PDU session identifier, PDU session creation request / PDU session modification request / PDU session release request), which is not limited in the present disclosure.

[0304] In step S2107, the second core network device detects an event of a user plane association of the terminal.

[0305] In some embodiments, after receiving the second message, the second core network device can perform event detection on the second information based on the first request.

[0306] In some embodiments, the second core network device can determine that the event of the user plane association of the terminal is detected in a case where the second information contains a 3GPP PS data off state.

[0307] In some embodiments, the second core network device can determine that the event of the user plane association of the terminal is detected in a case where the second information contains a request of the terminal to establish, modify and / or release a PDU session.

[0308] In some embodiments, after receiving the second information, the second core network device can update the context of the terminal.

[0309] In step S2108, the second core network device sends first information to the first core network device.

[0310] In some embodiments, the first information is associated with the user plane state of the terminal.

[0311] In some embodiments, the second core network device can send the first information to the first core network device through the first message.

[0312] In some embodiments, the first message comprises the second core network device identifier, the terminal identifier and the first information.

[0313] In some embodiments, the second core network device can send the first information to the first core network device through an event exposure notification, such as through a Namf_EventExposure_Notify message, to notify the detected user plane reachability of the UE.

[0314] In some embodiments, the first message can be: Nsmf_EventExposure_Notify (event identifier, detected event, terminal identifier, PDU session identifier, timestamp)

[0315] In some embodiments, the second core network device can also notify the first core network device of the detected event associated with the user plane of the terminal by notifying the first core network device to update the SM context.

[0316] In some embodiments, the first message can also be: Nsmf_PDUSession_SMContextStatusNotify or Nsmf_PDU Session_StatusNotify.

[0317] In some embodiments, the Nsmf_PDUSession_SMContextStatusNotify or Nsmf_PDU Session_StatusNotify can comprise: PDU session identifier, PDU session status, allowed PDU session status, etc.

[0318] In some embodiments, the first information comprises at least one of the following: event identifier, target event, 3GPP PS Data Off state indication information, PDU session identifier, PDU session status, allowed PDU session status, and timestamp.

[0319] In some embodiments, the PDU session status is used to indicate whether the PDU session is activated.

[0320] In some embodiments, the allowed PDU session status is used to indicate whether the activated PDU session is allowed to be used.

[0321] In some embodiments, the timestamp can be the time when the second core network device detects the event, or can also be the time when the second core network device queries the information associated with the user plane.

[0322] The first core network device updates the locally stored UE user plane reachability, in step S2109.

[0323] In some embodiments, the first core network device can update the locally stored user plane state of the terminal after the first information indicates that the user plane state of the terminal changes.

[0324] In some embodiments, the first core network device can update the locally stored user plane state of the terminal after the first information indicates that the user plane of the terminal is available.

[0325] In some embodiments, the first core network device can update the locally stored user plane state of the terminal after the first information indicates any of the following: change of 3GPP PS Data Off of the terminal, deactivation of 3GPP PS Data Off of the terminal, establishment of a PDU session of the terminal, release of a PDU session of the terminal, modification of a PDU session of the terminal, and the like, without limitation in the present disclosure.

[0326] In some embodiments, the first core network device can update the locally stored PDU session state of the terminal after the first information indicates any of the following: change of 3GPP PS Data Off of the terminal, deactivation of 3GPP PS Data Off of the terminal, establishment of a PDU session of the terminal, release of a PDU session of the terminal, modification of a PDU session of the terminal, and the like, without limitation in the present disclosure.

[0327] In some embodiments, the first core network device can send a user plane connection establishment request to the UE after determining that the UE user plane is reachable.

[0328] The information transmission method according to the embodiments of the present disclosure can include at least one of steps S2101-S2109. For example, step S2103 can be implemented as an independent embodiment, step S2108 can be implemented as an independent embodiment, steps S2103+S2104 can be implemented as an independent embodiment, steps S2101+S2102+S2103+S2104 can be implemented as an independent embodiment, steps S2101+S2102+S2103+S2108 can be implemented as an independent embodiment, and the like.

[0329] In the present embodiment or example, each step can be independent, arbitrarily combined or exchanged in order, optional modes or examples can be arbitrarily combined, and can be arbitrarily combined with any step of other embodiments or other examples, without contradiction.

[0330] In this embodiment, when deciding to use the LCS-UPP to perform the positioning service, the first core network device can subscribe to the availability or reachability of the user plane of the terminal by the second core network device, so as to obtain the user plane state of the terminal without the terminal actively creating a user plane connection.

[0331] FIG. 2B is an interaction diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG. 2B, the embodiment of the present disclosure relates to an information transmission method, which can be used in the communication system 100. In this embodiment, the interface between the first core network device and the second core network device is taken as an example for description, and the above method comprises the following steps:

[0332] In step S2201, the first core network device determines to use the LCS-UPP to perform the positioning service, and sends a second request to the terminal through the third core network device.

[0333] In step S2202, the first core network device receives the second response sent by the terminal through the third core network device.

[0334] The steps S2201-S2202 and the optional implementation manners thereof described above can refer to the steps S2101 and S2102 shown in FIG. 2A, which will not be described herein again.

[0335] In step S2203, the first core network device sends a first request to the second core network device through the third core network device.

[0336] In some embodiments, the first core network device can send the first request to the third core network device through a Namf_EventExposure_Subscribe request message.

[0337] In some embodiments, the first core network device can send the first request to the third core network device through a Namf_EventExposure_Subscribe request (terminal identifier, LMF identifier, target event to be subscribed, event identifier, event filter, event report information).

[0338] In some embodiments, the third core network device can send the first request to the second core network device through a Nsmf_EventExposure_Subscribe request message.

[0339] In some embodiments, the third core network device can send the first request to the second core network device through a Nsmf_EventExposure_Subscribe request (terminal identifier, AMF identifier, target event to be subscribed, event identifier, event filter, event report information).

[0340] Step S2204, the second core network device sends the first response to the first core network device through the third core network device.

[0341] In some embodiments, the second core network device can send the first response to the third core network device through an Nsmf_EventExposure_Subscriberesponse message.

[0342] In some embodiments, the second core network device can send the first response to the third core network device through an Nsmf_EventExposure_Subscriberesponse (subscription correlation ID 2, expiration time 2, event report 2).

[0343] In some embodiments, the subscription correlation ID 2 is a correlation ID subscribed by the third core network device to the second core network device.

[0344] In some embodiments, the expiration time can be agreed upon by a protocol or pre-configured, which is not limited in the present disclosure.

[0345] In some embodiments, the terms of “expiration time”, “expired time”, “valid time” and the like can be replaced with each other in some scenarios.

[0346] In some embodiments, the event report 2 is a report of an event subscribed by the third core network device generated by the second core network device.

[0347] In some embodiments, the third core network device can send the first response to the first core network device through an Namf_EventExposure_Subscriberesponse (subscription correlation ID 1, expiration time 1, event report 1).

[0348] In some embodiments, the subscription correlation ID 1 is a correlation ID subscribed by the first core network device to the third core network device.

[0349] In some embodiments, the event report 1 is a report of an event subscribed by the first core network device generated by the third core network device.

[0350] Step S2205, the user plane state changes, and the UE sends a third message to the third core network device.

[0351] Step S2206, the third core network device sends a second message to the second core network device.

[0352] In some embodiments, the second message can be an Nsmf_EventExposure_Notify (event ID, detected event, terminal ID, PDU session ID, timestamp)

[0353] In some embodiments, the second message can be Nsmf_EventExposure_Notify (event ID, detected event, terminal ID, PDU session ID, timestamp).

[0354] At step S2207, the second core network device detects an event of user plane association of the terminal.

[0355] The above steps S2203-S2207 and optional implementation manners thereof can refer to the steps S2103 and S2107 shown in FIG. 2A, and will not be described herein again.

[0356] At step S2208, the second core network device sends the first information to the first core network device through the third core network device.

[0357] In some embodiments, the second core network device can send the first information to the third core network device through an Nsmf_EventExposure_Notify message.

[0358] In some embodiments, the second core network device can send the first information to the third core network device through an Nsmf_EventExposure_Notify (event ID, detected event, terminal ID, PDU session ID, timestamp).

[0359] In some embodiments, after receiving the first information, the third core network device can send the first information to the first core network device through an Namf_EventExposure_Notify message.

[0360] In some embodiments, after receiving the first information, the third core network device can send the first information to the first core network device through an Namf_EventExposure_Notify (event ID, detected event, terminal ID, PDU session ID, timestamp).

[0361] At step S2209, the first core network device updates the reachability of the UE user plane stored locally.

[0362] The above step S2209 and optional implementation manners thereof can refer to the step S2109 shown in FIG. 2A, and will not be described herein again.

[0363] The information transmission method related to the embodiments of the present disclosure can include at least one of steps S2201-S2209. For example, step S2203 can be implemented as an independent embodiment, step S2208 can be implemented as an independent embodiment, steps S2203+S2204 can be implemented as an independent embodiment, steps S2201+S2202+S2203+S2204 can be implemented as an independent embodiment, steps S2201+S2202+S2203+S2208 can be implemented as an independent embodiment, and the like.

[0364] In the present embodiment or example, each step can be independently combined or exchanged in order, optional modes or examples can be combined, and any step of other embodiments or other examples can be combined, without contradiction.

[0365] In the present embodiment, when the first core network device decides to use the LCS-UPP for positioning services, the availability or reachability of the user plane of the terminal can be subscribed to the second core network device, so that the user plane state of the terminal can be obtained without the terminal actively creating a user plane connection.

[0366] FIG. 3A is a flow diagram of an information transmission method according to another embodiment of the present disclosure. As shown in FIG. 3A, the present embodiment relates to an information transmission method, which can be used for a first core network device. The above method includes:

[0367] Step S3101, determining to use the LCS-UPP for positioning services, and sending a second request to the terminal through a third core network device.

[0368] Step S3102, receiving a second response sent by the terminal through the third core network device.

[0369] Step S3103, sending a first request to the second core network device.

[0370] Step S3104, receiving a first response sent by the second core network device.

[0371] The above steps S3101-S3104 can refer to the specific descriptions of steps S2101-S2104 and possible implementation modes shown in FIG. 2A, which will not be repeated here.

[0372] Step S3105, receiving first information sent by the second core network device.

[0373] Step S3106, updating the locally stored user plane state of the terminal.

[0374] The steps S3105-S3106 can refer to the descriptions of steps S2108-S2109 and possible implementation manners shown in FIG. 2A, and details are not described herein.

[0375] The information transmission method related to the embodiments of the present disclosure can include at least one of steps S3101-S3106. For example, step S3103 can be implemented as an independent embodiment, step S3105 can be implemented as an independent embodiment, steps S3103+S3104 can be implemented as an independent embodiment, steps S3103+S3104+S3105 can be implemented as an independent embodiment, and the like, but are not limited thereto.

[0376] In the embodiments or examples, each step can be independently, arbitrarily combined or exchanged in sequence, optional manners or optional examples can be arbitrarily combined, and can be arbitrarily combined with any step of other embodiments or other examples, without contradiction.

[0377] FIG. 3B is an interaction diagram of an information transmission method according to another embodiment of the present disclosure. As shown in FIG. 3B, the embodiments of the present disclosure relate to an information transmission method, which can be used for a first core network device. The method includes the following steps:

[0378] In step S3201, a first request is sent to a second core network device through a third core network device.

[0379] In step S3202, a first response sent by the second core network device is received through the third core network device.

[0380] The steps S3201-S3202 can refer to the descriptions of steps S2203-S2204 and possible implementation manners shown in FIG. 2B, and details are not described herein.

[0381] In step S3203, first information sent by the second core network device is received through the third core network device.

[0382] In step S3204, a locally stored terminal user plane state is updated.

[0383] The steps S3203-S3204 can refer to the descriptions of steps S2208-S2209 and possible implementation manners shown in FIG. 2B, and details are not described herein.

[0384] The information transmission method related to the embodiments of the present disclosure can include at least one of steps S3201-S3204. For example, step S3201 can be implemented as an independent embodiment, step S3202 can be implemented as an independent embodiment, steps S3201+S3202 can be implemented as an independent embodiment, steps S3201+S3202+S3203 can be implemented as an independent embodiment, and the like, but are not limited thereto.

[0385] In the present embodiment or example, each step can be independently combined or exchanged in order, optional modes or examples can be combined, and any step of other embodiments or other examples can be combined, without contradiction.

[0386] FIG. 3C is a flow diagram of an information transmission method according to another embodiment of the present disclosure. As shown in FIG. 3C, the embodiments of the present disclosure relate to an information transmission method, which can be used in a first core network device. The above method includes:

[0387] Step S3301, receiving first information.

[0388] The first information is associated with a user plane of a terminal.

[0389] The first information is sent by a second core network device or sent by the second core network device through a third core network device.

[0390] In some embodiments of the present disclosure, before the above-mentioned receiving first information, the method further includes:

[0391] sending a first request to the second core network device; or,

[0392] sending a first request to the second core network device through the third core network device;

[0393] The first request is used to subscribe to an event associated with the user plane of the terminal.

[0394] In some embodiments of the present disclosure, the above method further includes:

[0395] receiving a first response sent by the second core network device, or receiving a first response sent by the second core network device through the third core network device, the first response being used to indicate a first subscription result.

[0396] In some embodiments of the present disclosure, the first response includes a report of a first event associated with the user plane of the terminal.

[0397] In some embodiments of the present disclosure, the first request comprises at least one of the following: an identity of the terminal, a data network name (DNN), a single-network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identity, a target event of the first request subscription, an event identity, a filter of the event, and event report information.

[0398] In some embodiments of the present disclosure, the event identity is an identity of any one of the following:

[0399] a user plane reachability of the terminal;

[0400] a user plane availability of the terminal;

[0401] a user plane status of the terminal;

[0402] a terminal reachability of the terminal;

[0403] a 3rd generation partnership project (3GPP) packet switched (PS) data off (Data Off) status of the terminal;

[0404] a 3GPP PS Data Off status change of the terminal;

[0405] a user plane status information of the terminal;

[0406] a PDU session creation, modification, or release request.

[0407] In some embodiments of the present disclosure, a parameter type in the event filter is associated with a user plane, and a parameter value in the filter of the event is used to indicate any one of the following: a reachability state change of a user plane of the terminal, downlink traffic reaching the user plane of the terminal, a user plane status change of the terminal, and a 3GPP PS Data Off status change of the terminal.

[0408] In some embodiments of the present disclosure, the target event comprises at least one of the following:

[0409] a reachability event of the terminal;

[0410] a user plane reachability event of the terminal;

[0411] a user plane availability event of the terminal;

[0412] a user plane status event of the terminal;

[0413] a user plane status information event of the terminal;

[0414] a 3GPP PS Data Off status change event of the terminal;

[0415] a 3GPP PS Data Off status of the terminal,

[0416] PDU session creation, modification or release request.

[0417] In some embodiments of the present disclosure, before the first request is sent, the method further comprises:

[0418] It is determined that a positioning service user plane protocol (LCS-UPP) is used for positioning service, and a second request is sent to the terminal through the third core network device, the second request being used for requesting to establish a user plane connection;

[0419] The second response sent by the terminal is received through the third core network device, and the second response is used for indicating that the user plane connection establishment fails.

[0420] In some embodiments of the present disclosure, the second response includes a user plane connection establishment failure reason, and the user plane connection establishment failure reason is any one of the following: PDU session failure, transport layer security (TLS) connection failure, LCS-UP connection binding failure, user plane unavailability, protocol error, and other reasons.

[0421] In some embodiments of the present disclosure, the first information includes at least one of the following: the event identifier, the target event, third generation partnership project (3GPP) packet switched (PS) data off state indication information, a packet data unit (PDU) session identifier, a state of the PDU session, an allowed state of the PDU session, and a timestamp.

[0422] In some embodiments of the present disclosure, the method further comprises:

[0423] The first information indicates any one of the following, and the user plane state of the terminal is updated: a user plane state of the terminal changes, a user plane of the terminal is available, a 3GPP PS Data Off of the terminal changes, a 3GPP PS Data Off of the terminal is deactivated, a PDU session of the terminal is established, a PDU session of the terminal is released, and a PDU session of the terminal is modified.

[0424] FIG. 4A is a flow diagram of an information transmission method according to another embodiment of the present disclosure. As shown in FIG. 4A, the present embodiment of the present disclosure relates to an information transmission method, which can be used for a second core network device. The method comprises:

[0425] Step S4101, receiving a first request sent by a first core network device.

[0426] Step S4102, sending a first response to the first core network device.

[0427] The steps S4101-S4102 can refer to the descriptions of the steps S2103-S2104 and possible implementation manners shown in FIG. 2A, and details are not described herein again.

[0428] In step S4103, a second message sent by the third core network device is received.

[0429] The second message includes an identifier of the third core network device, an identifier of the terminal, and second information, and the second information is associated with a user plane of the terminal.

[0430] In step S4104, an event associated with the user plane of the terminal is detected.

[0431] In step S4105, first information is sent to the first core network device.

[0432] The first information is associated with the user plane of the terminal.

[0433] The steps S4103-S4105 can refer to the descriptions of the steps S2105-S2108 and possible implementation manners shown in FIG. 2A, and details are not described herein again.

[0434] The information transmission method related to the embodiments of the present disclosure can include at least one of the steps S4101-S4105. For example, the step S4101 can be implemented as an independent embodiment, the step S4105 can be implemented as an independent embodiment, the steps S4101+S4102 can be implemented as an independent embodiment, the steps S4101+S4102+S4103+S4105 can be implemented as an independent embodiment, and the like.

[0435] In the embodiments or examples, each step can be independently, arbitrarily combined or exchanged in sequence, and optional manners or optional examples can be arbitrarily combined, and can be arbitrarily combined with any step of other embodiments or other examples.

[0436] FIG. 4B is a flow diagram of an information transmission method according to yet another embodiment of the present disclosure. As shown in FIG. 4B, the embodiments of the present disclosure relate to an information transmission method, which can be used for a second core network device. The method includes the following steps:

[0437] In step S4201, a first request sent by a first core network device is received by a third core network device.

[0438] In step S4202, a first response is sent to the first core network device by the third core network device.

[0439] The steps S4201-S4202 can refer to the descriptions of the steps S2203-S2204 and possible implementation manners shown in FIG. 2B, and details are not described herein again.

[0440] In step S4203, a second message sent by the third core network device is received.

[0441] The second message includes an identifier of the third core network device, an identifier of the terminal, and second information, and the second information is associated with the user plane of the terminal.

[0442] In step S4204, an event associated with the user plane of the terminal is detected.

[0443] In step S4205, the first core network device is sent the first information through the third core network device.

[0444] The steps S4203-S4205 can refer to the descriptions of the steps S2205-S2208 and possible implementation manners shown in FIG. 2B, and details are not described herein again.

[0445] The information transmission method related to the embodiments of the present disclosure can include at least one of the steps S4201-S4205. For example, the step S4201 can be implemented as an independent embodiment, the step S4205 can be implemented as an independent embodiment, the steps S4201+S4202 can be implemented as an independent embodiment, the steps S4201+S4202+S4203+S4205 can be implemented as an independent embodiment, and the like, but are not limited thereto.

[0446] In the embodiments or examples, each step can be independently, arbitrarily combined or exchanged in sequence, and optional modes or examples can be arbitrarily combined, without contradiction, and can be arbitrarily combined with any step of other embodiments or other examples.

[0447] FIG. 4C is a flow diagram of an information transmission method according to another embodiment of the present disclosure. As shown in FIG. 4C, the embodiments of the present disclosure relate to an information transmission method, which can be used for a second core network device. The method includes the following steps:

[0448] In step S4301, first information is sent to a first core network device, or the first information is sent to the first core network device through a third core network device.

[0449] The first information includes an identifier of the second core network device, an identifier of the terminal, and first information, and the first information is associated with the user plane of the terminal.

[0450] In some embodiments of the present disclosure, before the first information is sent, the method further includes the following steps:

[0451] receiving a first request, wherein the first request is sent by the first core network device or sent by the first core network device through a third core network device, and the first request is used to subscribe to an event associated with a user plane of a terminal.

[0452] In some embodiments of the present disclosure, the method further includes:

[0453] sending a first response to the first core network device or sending the first response to the first core network device through the third core network device, wherein the first response is used to indicate a subscription result.

[0454] In some embodiments of the present disclosure, the first response includes a report of a first event associated with the user plane of the terminal.

[0455] In some embodiments of the present disclosure, the first request includes at least one of the following: an identifier of the terminal, a data network name (DNN), single network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identifier, a target event to which the first request subscribes, an event identifier, a filter of the event, and event report information.

[0456] In some embodiments of the present disclosure, the event identifier is an identifier of any one of the following:

[0457] terminal user plane reachability;

[0458] terminal user plane availability;

[0459] terminal user plane status;

[0460] terminal reachability;

[0461] a third generation partnership project (3GPP) packet switched (PS) data off (Data Off) status of the terminal;

[0462] a change in the 3GPP PS Data Off status of the terminal;

[0463] terminal user plane status information;

[0464] a PDU session creation, modification, or release request.

[0465] In some embodiments of the present disclosure, a parameter type in the filter of the event is associated with the user plane, and a parameter value in the filter of the event is used to indicate any one of the following: a change in a reachability state of the user plane of the terminal, downlink traffic reaching the user plane of the terminal, a change in a user plane status of the terminal, and a change in the 3GPP PS Data Off status of the terminal.

[0466] In some embodiments of the present disclosure, the target event includes at least one of the following:

[0467] a reachability event of the terminal;

[0468] a user plane reachability event of the terminal;

[0469] a user plane availability event of the terminal;

[0470] a user plane status event of the terminal;

[0471] a user plane status information event of the terminal;

[0472] a 3GPP PS Data Off state change event of the terminal;

[0473] a 3GPP PS Data Off state of the terminal,

[0474] a PDU session creation, modification or release request.

[0475] In some embodiments of the disclosure, the first information includes at least one of the following: an event identifier, a target event, a 3rd Generation Partnership Project, 3GPP, Packet Switched, PS, Data Off state, a Packet Data Unit, PDU, session identifier, a state of the PDU session, an allowed PDU session state, an identifier of the terminal, a timestamp.

[0476] In some embodiments of the disclosure, the method further includes:

[0477] detecting an event of a user plane association of the terminal.

[0478] In some embodiments of the disclosure, the event of the user plane association of the terminal includes:

[0479] receiving a second message sent by the third core network device, wherein the second message includes an identifier of the third core network device, an identifier of the terminal and second information, and the second information is associated with a user plane of the terminal;

[0480] detecting, based on the second information, the event of the user plane association of the terminal.

[0481] In some embodiments of the disclosure, the second information includes at least one of the following: a PDU session identifier, an old PDU session identifier, a PDU session establishment request, a PDU session release request, a PDU session modification request, a Session and Service Continuity, SSC, indication, an extended protocol configuration option, a 3GPP PS Data Off state, a PDU session state, and an allowed PDU session state.

[0482] In some embodiments of the disclosure, the event of the user plane association of the terminal includes at least one of the following:

[0483] detecting that the terminal reports a 3GPP PS data off state, determining that the event of detecting the user plane association of the terminal is detected;

[0484] detecting that the terminal requests to establish, modify and / or release a PDU session, determining that the event of detecting the user plane association of the terminal is detected.

[0485] FIG. 5A is a flow diagram of a method of information transmission, according to another embodiment of the present disclosure. As shown in FIG. 5A, the embodiments of the present disclosure relate to a method of information transmission, which can be used in a third core network device. The above method includes:

[0486] Step S5101, forwarding a second request sent by the first core network device to the terminal.

[0487] Step S5102, forwarding a second response sent by the terminal to the first core network device.

[0488] In some embodiments, the terms of “forwarding”, “transmitting”, “transferring” and the like can be replaced with each other in some scenarios.

[0489] Step S5103, forwarding a first request sent by the first core network device to the second core network device.

[0490] Step S5104, forwarding a first response sent by the first core network device to the second core network device.

[0491] Step S5105, receiving a third message sent by the UE.

[0492] Step S5106, sending a second message to the second core network device.

[0493] Step S5107, forwarding a first information sent by the second core network device to the first core network device.

[0494] The above steps S5101-S5107 can refer to the specific descriptions of steps S2201-S2206, S2208 and possible implementation manners thereof shown in FIG. 2B respectively, which will not be described here again.

[0495] The method of information transmission related to the embodiments of the present disclosure can include at least one of steps S5101-S5107. For example, step S5103 can be implemented as an independent embodiment, step S5105 can be implemented as an independent embodiment, steps S5103+S5104 can be implemented as an independent embodiment, steps S5103+S5104+S5105+S5106+S5107 can be implemented as an independent embodiment, and the like, but are not limited thereto.

[0496] In the embodiments or examples, each step can be independent, combined arbitrarily or exchanged in sequence, optional mode or optional example can be combined arbitrarily, and can be combined arbitrarily with any step of other embodiments or other examples without contradiction.

[0497] FIG. 5B is a flow diagram of an information transmission method according to another embodiment of the present disclosure. As shown in FIG. 5B, the embodiment of the present disclosure relates to an information transmission method, which can be used for a third core network device. The above method includes:

[0498] Step S5201, forwarding a first request sent by the first core network device to the second core network device.

[0499] Step S5202, forwarding a first response sent by the first core network device to the second core network device.

[0500] Step S5203, receiving a third message sent by the UE.

[0501] Step S5204, sending a second message to the second core network device.

[0502] Step S5205, forwarding a first information sent by the second core network device to the first core network device.

[0503] The above steps S5201-S5205 can refer to the specific descriptions of steps S2203-S2206 and S2208 and possible implementation manners shown in FIG. 2B respectively, which will not be described here.

[0504] The information transmission method related to the embodiment of the present disclosure can include at least one of steps S5201-S5205. For example, step S5201 can be implemented as an independent embodiment, step S5205 can be implemented as an independent embodiment, steps S5201+S5202 can be implemented as an independent embodiment, steps S5201+S5202+S5204+S5205 can be implemented as an independent embodiment, and the like, but not limited thereto.

[0505] In the embodiments or examples, each step can be independent, combined arbitrarily or exchanged in sequence, optional mode or optional example can be combined arbitrarily, and can be combined arbitrarily with any step of other embodiments or other examples without contradiction.

[0506] FIG. 5C is an interaction diagram of an information transmission method according to another embodiment of the present disclosure. As shown in FIG. 5C, the embodiment of the present disclosure relates to an information transmission method, which can be used for a third core network device. The above method includes:

[0507] In step S5301, the first information sent by the second core network device is received, and the first information is sent to the first core network device.

[0508] The first information includes an identifier of the second core network device, an identifier of the terminal, and the first information. The first information is associated with a user plane of the terminal.

[0509] In some embodiments of the present disclosure, before the first information is sent to the first core network device, the above further includes:

[0510] The first request sent by the first core network device is received, and the first request is sent to the second core network device. The first request is used to subscribe to an event associated with the user plane of the terminal.

[0511] In some embodiments of the present disclosure, the above method further includes:

[0512] The first response sent by the second core network device is received, and the first response is sent to the first core network device. The first response is used to indicate a subscription result.

[0513] In some embodiments of the present disclosure, the first response includes a report of a first event associated with the user plane of the terminal.

[0514] In some embodiments of the present disclosure, the first request includes at least one of the following: an identifier of the terminal, a data network name (DNN), single network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identifier, a target event subscribed by the first request, an event identifier, an event filter, and event report information.

[0515] In some embodiments of the present disclosure, the event identifier is an identifier of any of the following:

[0516] Terminal user plane reachability;

[0517] Terminal user plane availability;

[0518] Terminal user plane status;

[0519] Terminal terminal reachability;

[0520] Third generation partnership project (3GPP) packet switched (PS) data off (Data Off) state of the terminal;

[0521] 3GPP PS Data Off state change of the terminal;

[0522] Terminal user plane status information;

[0523] PDU session creation, modification, or release request.

[0524] In some embodiments of the present disclosure, the parameter type in the above event filter is associated with a user plane, and the parameter value in the filter of the event is used to indicate any one of: a reachability state change of a user plane of the terminal, downlink traffic reaching the user plane of the terminal, a state change of the user plane of the terminal, and a 3GPP PS Data Off state change of the terminal.

[0525] In some embodiments of the present disclosure, the above target event includes at least one of:

[0526] a reachability event of the terminal;

[0527] a terminal user plane reachability event;

[0528] a terminal user plane availability event;

[0529] a terminal user plane state event;

[0530] a terminal user plane state information event;

[0531] a 3GPP PS Data Off state change event of the terminal;

[0532] a 3GPP PS Data Off state of the terminal,

[0533] a PDU session creation, modification or release request.

[0534] In some embodiments of the present disclosure, the above method further includes:

[0535] receiving a third message sent by the terminal, wherein the third message includes an identifier of the terminal and third information associated with a user plane of the terminal;

[0536] detecting, based on the third information, an event associated with the user plane of the terminal;

[0537] sending a second message to the second core network device, wherein the second message includes an identifier of the third core network device, an identifier of the terminal and second information, and the second information is associated with the user plane of the terminal.

[0538] In some embodiments of the present disclosure, the above detecting, based on the second information, an event associated with the user plane of the terminal includes:

[0539] detecting that the terminal reports its 3GPP PS Data Off state, and determining that the event associated with the user of the terminal is detected;

[0540] detecting that the terminal requests to establish, modify and / or release a PDU session, and determining that the event associated with the user of the terminal is detected.

[0541] In some embodiments of the present disclosure, the third message is any one of the following:

[0542] an uplink non-access stratum transport message;

[0543] a registration request message;

[0544] a service request message;

[0545] a PDU session creation request message;

[0546] a PDU session modification request message;

[0547] a PDU session release request message.

[0548] In some embodiments of the present disclosure, the third information and the second information respectively include at least one of the following: an old PDU session identifier, a PDU session establishment request, a PDU session release request, a PDU session modification request, a session and service continuity indication SSC, an extended protocol configuration option, a 3GPP PS Data Off state, a PDU session state, and an allowed PDU session state.

[0549] FIG. 6A is an interaction diagram of an information transmission method according to still another embodiment of the present disclosure. As shown in FIG. 6A, the embodiment of the present disclosure relates to an information transmission method, which can be used in a communication system. The method includes:

[0550] In step S6101, the second core network device sends first information to the first core network device.

[0551] The specific implementation of step S6101 can refer to the detailed description of any of the above embodiments, which will not be repeated here.

[0552] FIG. 6B is an interaction diagram of an information transmission method according to still another embodiment of the present disclosure. As shown in FIG. 6B, the embodiment of the present disclosure relates to an information transmission method, which can be used in a communication system. The method includes:

[0553] In step S6201, the second core network device sends first information to the first core network device through the third core network device.

[0554] The specific implementation of step S6201 can refer to the detailed description of any of the above embodiments, which will not be repeated here.

[0555] The following takes the first core network device as LMF, the second core network device as SMF, and the third core network device as AMF as an example to exemplarily introduce the above method.

[0556] As shown in FIG. 7A, FIG. 7A is a schematic diagram of an information transmission method provided in an embodiment of the present disclosure. As shown in FIG. 7A, there is an interface between the LMF and the SMF, and the process in which the LMF subscribes to the event exposure service of the SMF can include the following steps:

[0557] 700. The LMF decides to use LCS-UPP for the positioning service.

[0558] 701. The LMF sends a user plane connection establishment command to the UE through the AMF to establish a user plane connection between the UE and the LMF.

[0559] Optionally, the LMF can send the AMF: Namf_communication_N1N2MessageTransfer to carry the user plane connection establishment command.

[0560] Optionally, the AMF can carry the user plane connection establishment command by sending the UE: DL NAS TRANSPORT.

[0561] 702. The UE sends a user plane connection establishment failure response to the LMF through the AMF.

[0562] Optionally, if the UE determines that the user plane is not available, for example, because the UE sets the 3GPP PS data off to the “active” state, or the UE determines to use the control plane positioning or other positioning methods, for example, because of user plane congestion or insufficient user plane resources, the UE can send a user plane connection establishment failure message containing the reason value “user plane not available”.

[0563] Optionally, the user plane connection establishment failure (or user plane not available) response can be sent through the following message: UL NAS TRANSPORT.

[0564] Optionally, the AMF can transmit the user plane connection establishment failure (or user plane not available response) to the LMF through the following message: Namf_Communication_N1MessageNotify.

[0565] After receiving the message, the LMF knows that the user plane of the UE is not available, and can store / update the user plane status (i.e., the user plane is not available) or the user plane availability as false (for example, set to 0) as part of the UE context. The LMF will not start the network-initiated user plane connection establishment process again, and if the location service is still needed, other available positioning solutions can be considered.

[0566] Note: Steps 700-702 can trigger step 703, but step 703 can also be performed without steps 700-702 (i.e., steps 700-702 can be skipped and step 703 can be performed directly).

[0567] 703. The LMF sends a subscription request to the SMF.

[0568] Wherein the subscription request is used to subscribe to the UE's user plane information / user plane availability / user plane status / UE reachability.

[0569] Optionally, the subscription request can include a UE ID, an event ID, an event filter, and event reporting information.

[0570] Optionally, the event ID can be a new event ID or an enhancement of an existing event ID. This event ID can indicate when downlink data can be sent to the UE over the user plane and / or indicate when the UE is available for establishing a user plane connection.

[0571] Optionally, the user plane status information / user plane availability / 3GPP PS data off status can be a new event ID or an enhancement of an existing event ID. This event indicates when the UE is reachable for sending downlink data to the UE over the user plane / when the UE is available for establishing a user plane connection.

[0572] Optionally, the user plane status information is an existing event that includes a PDU session ID, a user plane inactivity timer, and a PDU session status. The user plane availability / 3GPP PS data off status can be part of the existing user plane status information event.

[0573] Optionally, the new event ID, such as user plane availability, or 3GPP PS data off status, etc.

[0574] In addition to the above events, the LMF can also subscribe to other events, such as PDU session establishment and / or PDU session release events. Optionally, in addition to the existing filter: “<Parameter Type = Application Identifier, Value = Application Identifier 1>, <Parameter Type = SUPI, Value = SUPI 1>”, the following new event filter can be added: <Parameter Type = DNN, Value = DNN 1>, <Parameter Type = S-NSSAI, Value = S-NSSAI 1>, <Data Type = LMF Id, Value = LMF Id 1>.

[0575] Optionally, the LMF can subscribe to user plane related events to the SMF by the following way: LMF -> SMF: Nsmf_EventExposure_Subscribe request (UE ID, LMF ID, Event Report Target, Event ID, Event Filter, Event Report Information) where "->" is used to indicate sending, or transmission.

[0576] 704. The SMF responds to the LMF.

[0577] Optionally, the SMF can respond to the subscription request before the expiry time.

[0578] Optionally, the response can include the first event report of "User Plane UE Reachability" (if available).

[0579] For example, the SMF can send the response to the LMF by the following way: SMF -> LMF: Nsmf_EventExposure_Subscribe response (Subscription Correlation ID, Expiry Time, Event Report)

[0580] 705. User Plane Status Changes.

[0581] For example, the user plane status changes to an available status (or reachability status) due to 3GPP PS Data Off being deactivated, or there is no congestion in the user plane of the UE, etc.

[0582] 706. The AMF detects reachability of the user plane.

[0583] Optionally, the AMF can detect whether the user plane is reachable based on one or more of the following criteria:

[0584] A. The AMF detects that the UE reports its 3GPP PS Data Off status to the AMF.

[0585] For example, the UE reports its 3GPP PS Data Off status to the AMF as "deactivated" or "deactivated".

[0586] a. The 3GPP PS Data Off status can be included in the Extended Protocol Configuration Options IE of the PDU Session Establishment Request / PDU Session Modification Request / PDU Session Release Request.

[0587] For example: UE -> AMF: UL NAS Transport (S-NSSAI, UE Requested DNN, PDU Session ID, Old PDU Session ID, PDU Session Establishment Request / PDU Session Modification Request / PDU Session Release Request (PDU Session ID), SSC Mode, Extended Protocol Configuration Options (3GPP PS Data Off)).

[0588] b. The Allowed PDU Session Status IE in the Registration Request / Service Request message indicates the 3GPP PS data off status as "Deactivated" status.

[0589] For example: UE -> AMF: Registration Request / Service Request (PDU Session Status, Allowed PDU Session Status).

[0590] For case a and case b, upon receiving the message from the UE, the AMF can also interact with the SMF to inform the SMF about the received message through the Nsmf_PDUSession_CreateSMContext message or the Nsmf_PDU Session_UpdateSMContext message.

[0591] For example, AMF -> SMF: Nsmf_PDUSession_CreateSMContext / Nsmf_PDUSession_UpdateSMContext Request (DNN, S-NSSAI, PDU Session ID, old PDU Session ID, PDU Session Establishment Request / PDU Session Modification Request / PDU Session Release Request).

[0592] B. The AMF detects that the UE requests to establish / modification / release a PDU session.

[0593] To establish / modification / release a PDU session, the UE can send a PDU Session Establishment Request / PDU Session Modification Request / PDU Session Release Request to the AMF. In the above PDU Session Establishment, Modification or Release Request, the PDU Session ID, SSC mode, Extended Protocol Configuration Options IE can be included.

[0594] For example, the UE can send a PDU Session Create, Modification or Release Request to the AMF by the following way: UE -> AMF: UL NAS TRANSPORT (S-NSSAI, UE requested DNN, PDU Session Identity, old PDU Session Identity, PDU Session Establishment Request / PDU Session Modification Request / PDU Session Release Request (PDU Session Identity), SSC mode).

[0595] 707. The AMF interacts with the SMF.

[0596] Optionally, the AMF can inform the SMF about the received message through the Nsmf_PDUSession_CreateSMContext message or the Nsmf_PDU Session_UpdateSMContext message.

[0597] AMF->SMF: Nsmf_PDUSession_CreateSMContext / Nsmf_PDUSession_UpdateSMContext request (DNN, S-NSSAI, PDU session ID, old PDU session ID, PDU session establishment request / PDU session modification request / PDU session release request)

[0598] 708. The SMF detects at least one subscription event.

[0599] Optionally, the SMF detects at least one subscription event based on the received Nsmf_PDUSession_CreateSMContext / Nsmf_PDUSession_UpdateSMContext message.

[0600] 709. The SMF sends a subscription event to the LMF.

[0601] Optionally, the SMF can send the Nsmf_EventExposure_Notify message to the LMF to notify the LMF of the detected subscription event (i.e., at least one of the user plane status information / user plane availability / 3GPP PS data off status, PDU session establishment and / or PDU session release event). The message includes event ID, detected event, UE ID, PDU session ID, timestamp.

[0602] SMF->LMF: Nsmf_EventExposure_Notify (event ID, detected event, UE ID, PDU session ID, timestamp).

[0603] Optionally, the LMF updates the local storage UE reachability of the user plane.

[0604] As shown in FIG. 7B, FIG. 7B is a schematic diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG. 7B, there is no interface between the LMF and the SMF, and the process of the LMF subscribing to the event exposure service of the SMF can include the following steps:

[0605] 710. The LMF decides to use LCS-UPP for positioning service.

[0606] 711. The LMF sends a user plane connection establishment command to the UE through the AMF to establish a user plane connection between the UE and the LMF.

[0607] 712. The UE sends a user plane connection establishment failure response to the LMF through the AMF.

[0608] 713. The LMF sends a subscription request to the AMF and obtains a response from the AMF.

[0609] Optionally, the LMF can send a Namf_EventExposure_Subscribe request to the SMF to subscribe to the UE's user plane status information / user plane availability / 3GPP PS data off status, the AMF responds to the LMF.

[0610] For example, LMF->AMF: Namf_EventExposure_Subscribe request (UE ID, LMF ID, Event reporting target, Event ID, Event filter, Event reporting information)

[0611] AMF->LMF: Namf_EventExposure_Subscribe response (Subscription correlation ID 1, Expiry time 1, Event reporting 1).

[0612] 714. The AMF subscribes to target events with the SMF.

[0613] Optionally, AMF->SMF: Nsmf_EventExposure_Subscribe request (UE ID, AMF ID, Event reporting target, Event ID, Event filter, Event reporting information).

[0614] Then, SMF->AMF: Nsmf_EventExposure_Subscribe response (Subscription correlation ID 2, Expiry time 2, Event reporting 2).

[0615] Optionally, the SMF sends a Nsmf_EventExposure_Notify message to the AMF to notify the AMF of the detected subscription event (i.e., at least one of the user plane status information / user plane availability / 3GPP PS data off status, PDU session establishment, and / or PDU session release event). The message includes the event ID, the detected event, the UE ID, the PDU session ID, the timestamp.

[0616] Optionally, SMF->AMF: Nsmf_EventExposure_Notify (Event ID, Detected event, UE ID, PDU session ID, Timestamp).

[0617] 715. User plane status changes.

[0618] 716. The AMF detects the reachability of the user plane.

[0619] 717. The AMF interacts with the SMF.

[0620] 718. The SMF detects at least one subscription event.

[0621] 719a. The SMF sends the subscription event to the AMF.

[0622] 719b. The AMF sends the subscription event to the LMF.

[0623] Upon receiving the event report from the SMF, the AMF sends a Namf_EventExposure_Notify message to the LMF to notify the LMF of the detected event.

[0624] For example, AMF -> LMF: Namf_EventExposure_Notify (event ID, detected event, UE ID, PDU session ID, timestamp).

[0625] FIG. 8A is a schematic diagram of a structure of a first core network device according to an embodiment of the present disclosure. As shown in FIG. 8A, the first core network device 8100 can include at least one of a transceiver module 8101, a processing module 8102, and the like. The first core network device 8100 can include:

[0626] The transceiver module 8101 is configured to receive first information, wherein the first information includes an identifier of a second core network device, an identifier of a terminal, and first information associated with a user plane of the terminal, the first information being sent by the second core network device or by the second core network device through a third core network device.

[0627] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0628] send a first request to the second core network device; or

[0629] send the first request to the second core network device through the third core network device.

[0630] The first request is used to subscribe to an event associated with the user plane of the terminal.

[0631] In some embodiments of the present disclosure, the transceiver module 8101 is further configured to:

[0632] receive a first response sent by the second core network device or received by the second core network device through the third core network device, the first response being used to indicate a first subscription result.

[0633] In some embodiments of the present disclosure, the first response includes a report of a first event associated with the user plane of the terminal.

[0634] In some embodiments of the disclosure, the first request comprises at least one of the following: an identity of the terminal, a data network name (DNN), a single-network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identity, a target event to which the first request subscribes, an event identity, a filter of the event, and event report information.

[0635] In some embodiments of the disclosure, the event identity is an identity of any one of the following:

[0636] a user plane reachability of the terminal;

[0637] a user plane availability of the terminal;

[0638] a user plane status of the terminal;

[0639] a reachability of the terminal;

[0640] a 3rd generation partnership project (3GPP) packet switched (PS) Data Off status of the terminal;

[0641] a change of the 3GPP PS Data Off status of the terminal;

[0642] a user plane status information of the terminal;

[0643] a PDU session creation, modification or release request.

[0644] In some embodiments of the disclosure, a parameter type in the event filter is associated with a user plane, and a parameter value in the filter of the event is used to indicate any one of the following: a reachability state change of the user plane of the terminal, downlink traffic reaching the user plane of the terminal, a user plane status change, and a change of the 3GPP PS Data Off status.

[0645] In some embodiments of the disclosure, the target event comprises at least one of the following:

[0646] a reachability event of the terminal;

[0647] a user plane reachability event of the terminal;

[0648] a user plane availability event of the terminal;

[0649] a user plane status event of the terminal;

[0650] a user plane status information event of the terminal;

[0651] a change of the 3GPP PS Data Off status event of the terminal;

[0652] a 3GPP PS Data Off status of the terminal,

[0653] PDU session creation, modification or release request.

[0654] In some embodiments of the present disclosure, the transceiver 8101 is further configured to:

[0655] determine that a positioning service is to be performed using a location service user plane protocol (LCS-UPP), and send, to the terminal via the third core network device, a second request for establishing a user plane connection;

[0656] receive, from the terminal via the third core network device, a second response indicating that the user plane connection fails to be established.

[0657] In some embodiments of the present disclosure, the second response includes a cause of the user plane connection failing to be established, and the cause of the user plane connection failing to be established is any one of the following: a PDU session fails, a transport layer security (TLS) connection fails, an LCS-UP connection binding fails, a user plane is unavailable, a protocol error, or another cause.

[0658] In some embodiments of the present disclosure, the first information includes at least one of the following: an event identity, a target event, third generation partnership project (3GPP) packet switched (PS) data off state indication information, a packet data unit (PDU) session identity, a state of the PDU session, an allowed PDU session state, and a time stamp.

[0659] In some embodiments of the present disclosure, the processing module 8102 is further configured to:

[0660] The first information indicates any one of the following: a user plane state of the terminal changes, a user plane of the terminal is available, a 3GPP PS Data Off of the terminal changes, a 3GPP PS Data Off of the terminal is deactivated, a PDU session of the terminal is established, a PDU session of the terminal is released, and a PDU session of the terminal is modified.

[0661] In some embodiments, the transceiver can include a sending module and / or a receiving module, and the sending module and the receiving module can be separate or integrated together. Alternatively, the transceiver can be mutually replaced with a transceiver.

[0662] In some embodiments, the processing module can be one module, or can include multiple sub-modules. Alternatively, the multiple sub-modules perform all or part of the steps required by the processing module to perform. Alternatively, the processing module can be mutually replaced with a processor.

[0663] FIG. 8B is a structural schematic diagram of a second core network device according to another embodiment of the present disclosure. As shown in FIG. 8B, the second core network device 8200 can include at least one of a transceiver module 8201, a processing module 8202, and the like. The second core network device 8200 can include:

[0664] The transceiver module 8201 is configured to send first information to a first core network device, or send the first information to the first core network device through a third core network device, wherein the first information includes an identifier of the second core network device, an identifier of a terminal, and first information, and the first information is associated with a user plane of the terminal.

[0665] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0666] receive a first request, wherein the first request is sent by the first core network device or by the first core network device through the third core network device, and the first request is used to subscribe to an event associated with the user plane of the terminal.

[0667] In some embodiments of the present disclosure, the transceiver module 8201 is further configured to:

[0668] send a first response to the first core network device, or send the first response to the first core network device through the third core network device, and the first response is used to indicate a subscription result.

[0669] In some embodiments of the present disclosure, the first response includes a report of a first event associated with the user plane of the terminal.

[0670] In some embodiments of the present disclosure, the first request includes at least one of the following: an identifier of the terminal, a data network name (DNN), single network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identifier, a target event to which the first request subscribes, an identifier of an event, an event filter, and event report information.

[0671] In some embodiments of the present disclosure, the identifier of the event is an identifier of any one of the following:

[0672] terminal user plane reachability;

[0673] terminal user plane availability;

[0674] terminal user plane status;

[0675] terminal reachability;

[0676] a third generation partnership project (3GPP) packet switched (PS) data off state of the terminal;

[0677] Terminal 3GPP PS Data Off state change;

[0678] Terminal user plane state information;

[0679] PDU session creation, modification or release request.

[0680] In some embodiments of the present disclosure, the parameter type in the event filter is associated with the user plane, and the parameter value in the filter of the event is used to indicate any of the following: a reachability state change of the user plane, downlink traffic reachability of the user plane of the terminal, a user plane state change, a 3GPP PS Data Off state change.

[0681] In some embodiments of the present disclosure, the target event includes at least one of the following:

[0682] Terminal reachability event;

[0683] Terminal user plane reachability event;

[0684] Terminal user plane availability event;

[0685] Terminal user plane state event;

[0686] Terminal user plane state information event;

[0687] Terminal 3GPP PS Data Off state change event;

[0688] Terminal 3GPP PS Data Off state,

[0689] PDU session creation, modification or release request.

[0690] In some embodiments of the present disclosure, the first information includes at least one of the following: event identification, target event, third generation partnership project 3GPP packet switching PS data off state indication information, packet data unit PDU session identification, PDU session state, allowed PDU session state, and timestamp.

[0691] In some embodiments of the present disclosure, the processing module 8202 is further configured to:

[0692] Detect an event associated with the user plane of the terminal.

[0693] In some embodiments of the present disclosure, further comprising:

[0694] The transceiver module 8201 is also configured to receive a second message sent by the third core network device, where the second message includes an identifier of the third core network device, an identifier of the terminal, and second information associated with the user plane of the terminal.

[0695] The processing module 8202 is configured to detect the event associated with the user plane of the terminal based on the second information.

[0696] In some embodiments of the present disclosure, the second information includes at least one of the following: a PDU session identifier, an old PDU session identifier, a PDU session establishment request, a PDU session release request, a PDU session modification request, a session and service continuity (SSC) mode, an extended protocol configuration option, a 3GPP PS Data Off state, a PDU session state, and an allowed PDU session state.

[0697] In some embodiments of the present disclosure, the processing module is further configured to perform at least one of the following:

[0698] detecting that the terminal reports a 3GPP PS Data Off state, and determining that the event associated with the user plane of the terminal is detected;

[0699] detecting that the terminal requests to establish, modify, and / or release a PDU session, and determining that the event associated with the user plane of the terminal is detected.

[0700] FIG. 8C is a structural schematic diagram of a third core network device according to another embodiment of the present disclosure. As shown in FIG. 8C, the third core network device 8300 can include at least one of a transceiver module 8301, a processing module 8302, and the like. The third core network device 8300 can include:

[0701] The transceiver module 8301 is configured to receive first information sent by a second core network device, and send the first information to a first core network device, where the first information includes an identifier of the second core network device, an identifier of the terminal, and first information associated with the user plane of the terminal.

[0702] In some embodiments of the present disclosure, the transceiver module 8301 is further configured to:

[0703] receive a first request sent by the first core network device, and send the first request to the second core network device, where the first request is used to subscribe to the event associated with the user plane of the terminal.

[0704] In some embodiments of the present disclosure, the transceiver module 8301 is further configured to:

[0705] receive the first response sent by the second core network device, and send the first response to the first core network device, the first response being used for indicating a subscription result.

[0706] In some embodiments of the present disclosure, the first response includes a report of a first event associated with a user plane of the terminal.

[0707] In some embodiments of the present disclosure, the first request includes at least one of the following: an identifier of the terminal, a data network name (DNN), single-network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identifier, a target event to which the first request subscribes, an event identifier, an event filter, and event report information.

[0708] In some embodiments of the present disclosure, the event identifier is an identifier of any one of the following:

[0709] terminal user plane reachability;

[0710] terminal user plane availability;

[0711] terminal user plane status;

[0712] terminal terminal reachability;

[0713] a third generation partnership project (3GPP) packet switched (PS) data off (Data Off) state of the terminal;

[0714] a change in the 3GPP PS Data Off state of the terminal;

[0715] terminal user plane status information;

[0716] a PDU session creation, modification, or release request.

[0717] In some embodiments of the present disclosure, a parameter type in the event filter is associated with a user plane, and a parameter value in the event filter is used to indicate any one of the following: a reachability state change of the user plane of the terminal, downlink traffic reachability of the user plane of the terminal, a user plane state change of the terminal, and a change in the 3GPP PS Data Off state of the terminal.

[0718] In some embodiments of the present disclosure, the target event includes at least one of the following:

[0719] a reachability event of the terminal;

[0720] a terminal user plane reachability event;

[0721] a terminal user plane availability event;

[0722] Terminal user plane status event;

[0723] Terminal user plane status information event;

[0724] Terminal 3GPP PS Data Off status change event;

[0725] Terminal 3GPP PS Data Off status,

[0726] PDU session creation, modification or release request.

[0727] In some embodiments of the present disclosure, the transceiver 8301 is further configured to receive a third message sent by the terminal, where the third message includes an identifier of the terminal and third information associated with the user plane of the terminal.

[0728] The processing module 8302 is further configured to detect an event associated with the user plane of the terminal based on the third information.

[0729] The transceiver 8301 is further configured to send a second message to the second core network device, where the second message includes an identifier of the third core network device, an identifier of the terminal and second information associated with the user plane of the terminal.

[0730] In some embodiments of the present disclosure, the processing module 8302 is further configured to perform at least one of the following:

[0731] Detecting that the terminal reports its 3GPP PS Data Off status, determining that the event associated with the user of the terminal is detected;

[0732] Detecting that the terminal requests to establish, modify and / or release a PDU session, determining that the event associated with the user of the terminal is detected.

[0733] In some embodiments of the present disclosure, the third message is any of the following:

[0734] Uplink non-access stratum transmission message;

[0735] Registration request message;

[0736] Service request message;

[0737] PDU session creation request message;

[0738] PDU session modification request message;

[0739] PDU session release request message.

[0740] In some embodiments of the present disclosure, the third information and the second information respectively include at least one of the following: an old PDU session identifier, a PDU session establishment request, a PDU session release request, a PDU session modification request, a session and service continuity indication (SSC), an extended protocol configuration option, a 3GPP PS Data Off status, a PDU session status, and an allowed PDU session status.

[0741] In some embodiments, the transceiving module can include a transmitting module and / or a receiving module, which can be separate or integrated together. Alternatively, the transceiving module can be mutually replaced with a transceiver.

[0742] In some embodiments, the processing module can be one module or include multiple sub-modules. Alternatively, the multiple sub-modules perform all or part of the steps required to be performed by the processing module. Alternatively, the processing module can be mutually replaced with a processor.

[0743] It should be understood that the division of each unit or module in the above apparatus is only a logical function division, and all or part of them can be integrated into a physical entity or physically separated in actual implementation. In addition, the units or modules in the apparatus can be implemented in the form of processor calling software: for example, the apparatus includes a processor, the processor is connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to realize the functions of any of the above methods or the units or modules of the above apparatus, wherein the processor is a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be realized by the design of hardware circuit. The above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are realized by the design of the logical relationship of elements in the circuit; for another example, in another implementation, the above hardware circuit is a programmable logic device (PLD), and a field programmable gate array (FPGA) is taken as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of part or all of the units or modules. All units or modules of the above apparatus can be all implemented in the form of processor calling software, or all implemented in the form of hardware circuit, or part implemented in the form of processor calling software and the remaining part implemented in the form of hardware circuit.

[0744] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), or the like. In another implementation, the processor can implement certain functions through a logical relationship of hardware circuits, and the logical relationship of the hardware circuits is fixed or can be reconfigured. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads instructions to implement the functions of the above part or all units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0745] FIG. 9A is a structural schematic diagram of a communication device according to an embodiment of the present disclosure. The communication device 9100 can be a terminal, a network device, a chip, a chip system, or a processor supporting the terminal to implement any of the above methods, or a chip, a chip system, or a processor supporting the network device to implement any of the above methods. The communication device 9100 can be used to implement the methods described in the above method embodiments, and specific implementation can be referred to the description in the above method embodiments.

[0746] As shown in FIG. 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process data of the programs. The communication device 9100 is used to implement any of the above methods.

[0747] In some embodiments, the communication device 9100 further includes one or more memories 9102 for storing instructions. Optionally, all or part of the memories 9102 can also be outside the communication device 9100.

[0748] In some embodiments, the communication device 9100 further includes one or more transceivers 9103. When the communication device 9100 includes one or more transceivers 9103, the transceiver 9103 performs at least one of the communication steps such as transmitting and / or receiving in the above-described methods, and the processor 9101 performs other steps.

[0749] In some embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Optionally, the terms transceiver, transceiving unit, transceiver, transceiving circuit, etc. can be replaced with each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced with each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced with each other.

[0750] In some embodiments, the communication device 9100 can include one or more interface circuits 9104. Optionally, the interface circuit 9104 is connected with the memory 9102, and the interface circuit 9104 can be used to receive signals from the memory 9102 or other devices, and can be used to send signals to the memory 9102 or other devices. For example, the interface circuit 9104 can read the instructions stored in the memory 9102 and send the instructions to the processor 9101.

[0751] The communication device 9100 described in the above embodiments can be a terminal or a network device or a third entity, but the scope of the communication device 9100 described in the present disclosure is not limited thereto, and the structure of the communication device 9100 can not be limited by FIG. 9A. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be: 1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, optionally, the set of ICs can also include storage components for storing data, programs; (3) an ASIC, such as a Modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0752] FIG. 9B is a structural schematic diagram of a chip according to an embodiment of the present disclosure. For the case where the communication device 9100 can be a chip or a chip system, the structural schematic diagram of a chip 9200 shown in FIG. 9B can be referred to, but is not limited thereto.

[0753] The chip 9200 comprises one or more processors 9201, and the chip 9200 is configured to execute any of the above methods.

[0754] In some embodiments, the chip 9200 further comprises one or more interface circuits 9202. Optionally, the interface circuit 9202 is connected with the memory 9203, and the interface circuit 9202 can be configured to receive signals from the memory 9203 or other devices, and the interface circuit 9202 can be configured to send signals to the memory 9203 or other devices. For example, the interface circuit 9202 can read instructions stored in the memory 9203 and send the instructions to the processor 9201.

[0755] In some embodiments, the interface circuit 9202 performs at least one of the communication steps such as sending and / or receiving in the above methods, and the processor 9201 performs other steps.

[0756] In some embodiments, the terms of interface circuit, interface, transceiver pin, transceiver, etc. can be replaced with each other.

[0757] In some embodiments, the chip 9200 further comprises one or more memories 9203 configured to store instructions. Optionally, all or part of the memory 9203 can be outside the chip 9200.

[0758] The disclosure further proposes a storage medium, and the storage medium stores instructions, and the instructions, when executed on the communication device 9100, cause the communication device 9100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices. Optionally, the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a transitory storage medium.

[0759] The disclosure further proposes a program product, and the program product, when executed by the communication device 9100, causes the communication device 9100 to execute any of the above methods. Optionally, the program product is a computer program product.

[0760] The disclosure further proposes a computer program, and the computer program, when executed on a computer, causes the computer to execute any of the above methods.

[0761] In the embodiments described above, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer programs are loaded on a computer and executed, all or part of the processes or functions described in the embodiments of the present disclosure are produced. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer programs can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer programs can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (such as floppy disk, hard disk, magnetic tape), optical media (such as high-density digital video disc (digital video disc, DVD)), or semiconductor media (such as solid state disk (solid state disk, SSD)) and the like.

[0762] Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether the functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. A skilled person can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present disclosure.

[0763] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0764] The above is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present disclosure, which should be covered within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. A method of information transmission, characterized in that, The method is performed by a first core network device, and the method comprises: receiving first information, wherein the first information is associated with a user plane of a terminal, and the first information is sent by a second core network device or by the second core network device through a third core network device.

2. The method of claim 1, wherein, Before the receiving of the first information, the method further comprises: sending a first request to the second core network device; or sending the first request to the second core network device through the third core network device. The first request is used for subscribing to an event associated with the user plane of the terminal.

3. The method of claim 2, wherein, The method further comprises: receiving a first response sent by the second core network device or by the second core network device through the third core network device, wherein the first response is used for indicating a first subscription result.

4. The method of claim 3, wherein, The first response comprises a report of a first event associated with the user plane of the terminal.

5. The method of any one of claims 2-4, wherein, The first request comprises at least one of the following: an identifier of the terminal, a data network name (DNN), single-network slice selection assistance information (S-NSSAI), a packet data unit (PDU) session identifier, a target event subscribed by the first request, an event identifier, an event filter, and event report information.

6. The method of claim 5, wherein, The event identifier is an identifier of any one of the following: terminal user plane reachability; terminal user plane availability; terminal user plane status; terminal terminal reachability; third generation partnership project (3GPP) packet switched (PS) data off (Data Off) status of the terminal; change of 3GPP PS Data Off status of the terminal; terminal user plane status information; PDU session creation, modification, or release request.

7. The method of claim 5, wherein, A parameter type in the event filter is associated with the user plane, and a parameter value in the event filter is used for indicating any one of the following: reachability state change of the user plane of the terminal, downlink traffic reaching the user plane of the terminal, user plane state change of the terminal, and change of 3GPP PS Data Off status of the terminal.

8. The method of any one of claims 5-7, wherein, The target event comprises at least one of the following: reachability event of the terminal; terminal user plane reachability event; terminal user plane availability event; terminal user plane status event; terminal user plane status information event; change of 3GPP PS Data Off status of the terminal; 3GPP PS Data Off status of the terminal, PDU session creation, modification, or release request.

9. The method of any one of claims 5-8, wherein, Before the sending of the first request, the method further comprises: determining to use a location service user plane protocol (LCS-UPP) for positioning service, sending a second request to the terminal through the third core network device, wherein the second request is used for requesting establishment of a user plane connection; receiving a second response sent by the terminal through the third core network device, wherein the second response is used for indicating failure of establishment of the user plane connection.

10. The method of claim 9, wherein, The second response includes a user plane connection establishment failure cause, and the user plane connection establishment failure cause is any of the following: PDU session failure, transport layer security (TLS) connection failure, LCS-UP connection binding failure, user plane unavailability, protocol error, or other cause.

11. The method of any one of claims 5-10, wherein, The first information includes at least one of the following: the event identifier, the target event, third generation partnership project (3GPP) packet switched (PS) data off state indication information, a packet data unit (PDU) session identifier, a state of the PDU session, an allowed state of the PDU session, and a timestamp.

12. The method of any one of claims 1-11, wherein, The method further includes: The first information indicates any of the following: a change in a user plane state of the terminal, user plane availability of the terminal, a change in 3GPP PS Data Off of the terminal, deactivation of 3GPP PS Data Off of the terminal, PDU session establishment of the terminal, PDU session release of the terminal, and PDU session modification of the terminal.

13. An information transmission method characterized by comprising: The method is performed by a second core network device, and includes: sending first information to a first core network device or sending the first information to the first core network device through a third core network device, wherein the first information is associated with a user plane of the terminal.

14. The method of claim 13, wherein, Before the first information is sent, the method further includes: receiving a first request, wherein the first request is sent by the first core network device or by the first core network device through the third core network device, and the first request is used to subscribe to an event associated with the user plane of the terminal.

15. The method of claim 14, wherein, The method further includes: sending a first response to the first core network device or sending the first response to the first core network device through the third core network device, wherein the first response is used to indicate a subscription result.

16. The method of claim 15, wherein, The first response includes a report of a first event associated with the user plane of the terminal.

17. The method of any one of claims 14-16, wherein, The first request includes at least one of the following: an identifier of the terminal, a data network name (DNN), single network slice selection assistance information (S-NSSAI), a PDU session identifier, a target event subscribed by the first request, an event identifier, an event filter, and event report information.

18. The method of claim 17, wherein, The event identifier is an identifier of any of the following: terminal user plane reachability; terminal user plane availability; terminal user plane state; terminal reachability; third generation partnership project (3GPP) packet switched (PS) data off (Data Off) state of the terminal; change in 3GPP PS Data Off state of the terminal; terminal user plane state information; PDU session creation, modification, or release request.

19. The method of claim 17, wherein, A parameter type in the event filter is associated with the user plane, and a parameter value in the event filter is used to indicate any of the following: a change in reachability state of the user plane of the terminal, downlink traffic reachability to the user plane of the terminal, a change in user plane state of the terminal, and a change in 3GPP PS Data Off state of the terminal.

20. The method of any one of claims 17-19, wherein, The target event includes at least one of the following: A reachability event of the terminal; A user plane reachability event of the terminal; A user plane availability event of the terminal; A user plane status event of the terminal; A user plane status information event of the terminal; A 3GPP PS Data Off state change event of the terminal; A 3GPP PS Data Off state of the terminal, A PDU session creation, modification or release request.

21. The method of any one of claims 17-20, wherein, The first information includes at least one of the following: the event identifier, the target event, a 3rd Generation Partnership Project, 3GPP, Packet Switched, PS, Data Off state, a Packet Data Unit, PDU, session identifier, a state of the PDU session, an allowed PDU session state, an identifier of the terminal, a timestamp.

22. The method of any one of claims 14-21, wherein, The method further includes: detecting an event of a user plane association of the terminal.

23. The method of claim 22, wherein, The detecting the event of the user plane association of the terminal includes: receiving a second message sent by the third core network device, wherein the second message includes an identifier of the third core network device, an identifier of the terminal and second information, and the second information is related to a user plane association of the terminal; detecting the event of the user plane association of the terminal based on the second information.

24. The method of claim 23, wherein, The second information includes at least one of the following: a PDU session identifier, an old PDU session identifier, a PDU session establishment request, a PDU session release request, a PDU session modification request, a Session and Service Continuity, SSC, indication, an extended protocol configuration option, a 3GPP PS Data Off state, a PDU session state, an allowed PDU session state.

25. The method of claim 23 or 24, wherein, The detecting the event of the user plane association of the terminal includes at least one of the following: detecting that the terminal reports its 3GPP PS Data Off state, and determining that the event of the user plane association of the terminal is detected; detecting that the terminal requests to establish, modify and / or release a PDU session, and determining that the event of the user plane association of the terminal is detected.

26. An information transmission method, characterized by, The method is performed by a third core network device, and the method includes: receiving first information sent by a second core network device, and sending the first information to a first core network device, wherein the first information is related to a user plane association of the terminal.

27. The method of claim 26, wherein, Before the sending the first information to the first core network device, the method further includes: receiving a first request sent by the first core network device, and sending the first request to the second core network device, wherein the first request is used to subscribe to an event related to the user plane association of the terminal.

28. The method of claim 27, wherein, The method further includes: receiving a first response sent by the second core network device, and sending the first response to the first core network device, wherein the first response is used to indicate a subscription result.

29. The method of claim 28, wherein, The first response includes a report of a first event related to the user plane association of the terminal.

30. The method of any one of claims 27-29, wherein, The first request includes at least one of the following: an identifier of the terminal, a Data Network Name, DNN, a Single-Network Slice Selection Assistance Information, S-NSSAI, a Packet Data Unit, PDU, session identifier, a target event subscribed by the first request, an event identifier, an event filter, and event report information.

31. The method of claim 30, wherein, The event identifier is an identifier of any one of the following: End user plane reachability; End user plane availability; End user plane status; End end reachability; Third generation partnership project, 3GPP, packet switched, PS, data off status of the terminal; 3GPP PS data off status change of the terminal; End user plane status information; PDU session creation, modification or release request.

32. The method of claim 30, wherein, The parameter type in the event filter is associated with the user plane, and the parameter value in the filter of the event is used to indicate any of the following: a reachability state change of the user plane of the terminal, downlink traffic reaching the user plane of the terminal, a user plane state change of the terminal, and a 3GPP PS data off state change of the terminal.

33. The method of any one of claims 30-32, wherein, The target event includes at least one of the following: Reachability event of the terminal; End user plane reachability event; End user plane availability event; End user plane status event; End user plane status information event; 3GPP PS data off state change event of the terminal; 3GPP PS data off state of the terminal, PDU session creation, modification or release request.

34. The method of any one of claims 27-33, wherein, The method further includes: Receiving a third message sent by the terminal, wherein the third message includes an identifier of the terminal and third information associated with the user plane of the terminal; Based on the third information, detecting an event associated with the user plane of the terminal; Sending a second message to the second core network device, wherein the second message includes an identifier of the third core network device, an identifier of the terminal and second information associated with the user plane of the terminal.

35. The method of claim 34, wherein, The detection of the event associated with the user plane of the terminal based on the second information includes at least one of the following: Detecting that the terminal reports its 3GPP PS data off state, and determining that the event associated with the user of the terminal is detected; Detecting that the terminal requests to establish, modify and / or release a PDU session, and determining that the event associated with the user of the terminal is detected.

36. The method of claim 34 or 35, wherein, The third message is any of the following: Uplink non-access stratum transmission message; Registration request message; Service request message; PDU session creation request message; PDU session modification request message; PDU session release request message.

37. The method of any one of claims 34-36, wherein, The third information and the second information respectively include at least one of the following: old PDU session identifier, PDU session establishment request, PDU session release request, PDU session modification request, session and service continuity indication, SS, extended protocol configuration option, 3GPP PS data off state, PDU session state, and allowed PDU session state.

38. An information transmission method, characterized by, The method is performed by a communication system, and the method includes: The second core network device sends first information to the first core network device or sends the first information to the first core network device through the third core network device, wherein the first information is associated with the user plane of the terminal.

39. A first core network device, comprising: The first core network device includes: The transceiver module is configured to receive first information, wherein the first information is associated with a user plane of the terminal, and the first information is transmitted by the second core network device or transmitted by the second core network device through the third core network device.

40. A second core network device, comprising: The second core network device comprises: The transceiver module is configured to transmit first information to the first core network device or transmit the first information to the first core network device through the third core network device, wherein the first information is associated with a user plane of the terminal.

41. A third core network device, comprising: The third core network device comprises: The transceiver module is configured to receive first information transmitted by the second core network device and transmit the first information to the first core network device, wherein the first information is associated with a user plane of the terminal.

42. A communications device, characterized by Comprise: One or more processors; The processor is configured to perform the information transmission method in any one of claims 1-37.

43. A storage medium, the storage medium storing instructions, wherein, When the instructions run on the communication device, the communication device performs the information transmission method in any one of claims 1-37.

44. A communication system, characterized by Comprise a first core network device, a second core network device and a third core network device, wherein the first core network device is configured to perform the information transmission method in any one of claims 1-12, the second core network device is configured to perform the information transmission method in any one of claims 13-25, and the third core network device is configured to perform the information transmission method in any one of claims 26-37.

45. A computer program product, characterised in that, Comprise a computer program, which is executed by a processor to implement the information transmission method in any one of claims 1-37.

Images