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

Abstract

The present disclosure relates to an information transmission method, and a core network device, a communication system and a storage medium. The information transmission method comprises: a first core network device receiving first information sent by a second core network device, wherein the first information is associated with a user plane of a terminal. Therefore, a first core network device can actively acquire user-plane information of a terminal, thereby providing the conditions 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 sent by a second core network device, the first information being associated with a user plane of a terminal.

[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, the first information being associated with a user plane of a terminal.

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

[0009] According to a fourth aspect of the embodiments of the present disclosure, a first core network device is provided, including: a transceiver, configured to receive first information transmitted by a second core network device, the first information being associated with a user plane of a terminal.

[0010] According to a fifth aspect of the embodiments of the present disclosure, a second core network device is provided, including: a transceiver, configured to transmit first information to a first core network device, the first information being associated with a user plane of a terminal.

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

[0012] According to a seventh aspect of the embodiments of the present disclosure, a communication system is provided, including a first core network device and a second core network device, wherein the first core network device is configured to implement the information transmission method in the first aspect, and the second core network device is configured to implement the information transmission method in the second aspect.

[0013] According to an eighth aspect of the embodiments of the present disclosure, a storage medium is provided, the storage medium storing 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.

[0014] According to a ninth aspect of the embodiments of the present disclosure, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the information transmission method in any one of the first aspect, the second aspect or the third aspect is implemented. BRIEF DESCRIPTION OF DRAWINGS

[0015] 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.

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

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

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

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

[0020] FIG. 5 is an interaction schematic diagram of an information transmission method according to still another embodiment of the present disclosure;

[0021] FIG. 6A is a schematic diagram of an information transmission method according to an embodiment of the present disclosure;

[0022] FIG. 6B is a schematic diagram of an information transmission method according to an embodiment of the present disclosure;

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

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

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

[0026] FIG. 8B is a schematic diagram of a structure of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0027] Embodiments of the present disclosure provide an information transmission method, a core network device, a communication system, and a storage medium.

[0028] In a first aspect, an embodiment of the present disclosure provides an information transmission method, executed by a first core network device; the method comprises:

[0029] receiving first information sent by a second core network device, the first information being associated with a user plane of a terminal.

[0030] In the above embodiment, the first core network device can directly obtain 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.

[0031] In combination with some embodiments of the first aspect, in some embodiments, before receiving the first information sent by the second core network device, the method further comprises any one of the following:

[0032] sending a 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, or the first request is used to request to query information associated with the user plane of the terminal.

[0033] In the above embodiment, the first core network device can subscribe to the event associated with the user plane from the second core network device, or query the information associated with the user plane from the second core network device, thereby improving the flexibility of the first core network device in obtaining the user plane information.

[0034] In some embodiments combined with the first aspect, in some embodiments, the first request is used to subscribe to an event associated with a user plane of the terminal, and the method further comprises:

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

[0036] In the above embodiments, the second core network device can send the subscription result to the first core network device, so that the understanding of the subscription result by the first core network device and the second core network device remains consistent, providing a condition for reliable execution of the first core network device side service.

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

[0038] 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 report of the first event associated with the user plane to the first core network device through the first response, shortening the waiting time for the first core network device to obtain the user plane reachability of the terminal.

[0039] In some embodiments combined with the first aspect, 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.

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

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

[0042] terminal user plane reachability;

[0043] terminal user plane availability;

[0044] terminal user plane status;

[0045] terminal reachability;

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

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

[0048] terminal user plane status information;

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

[0050] In the above embodiment, the flexibility of the event identification is improved by using multiple information as the event identification.

[0051] In combination with some embodiments of the first aspect, in some embodiments, 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, and a 3GPP PS Data Off state change.

[0052] In the above embodiment, by extending the event filter, not only the accuracy of the detected event can be ensured, but also the reuse of the existing event identification is provided.

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

[0054] a reachability event of the terminal;

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

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

[0057] a user plane state event of the terminal;

[0058] a user plane state information event of the terminal;

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

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

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

[0062] 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.

[0063] In combination with some embodiments of the first aspect, in some embodiments, before sending the first request to the second core network device, the method further includes:

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

[0065] The second core network device receives a second response sent by the terminal, and the second response is used to indicate that the user plane connection establishment fails.

[0066] 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 the following: PDU session failure, TLS connection failure, LCS-UP connection binding failure, user plane unavailable, protocol error, and other reasons.

[0067] In the above embodiments, 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.

[0068] In some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following: event identifier, target event, 3GPP PS data off state indication information, PDU session identifier, PDU session state, allowed PDU session state, and timestamp.

[0069] In the above embodiments, 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.

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

[0071] The first information indicates any one of the following, and the stored user plane state of the terminal is updated: user plane state change of the terminal, user plane availability of the terminal, 3GPP PS Data Off change of the terminal, 3GPP PS Data Off deactivation of the terminal, PDU session establishment of the terminal, PDU session release of the terminal, and PDU session modification of the terminal.

[0072] In the above embodiments, when the first core network device determines the user plane state change of the terminal, the stored user plane state 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.

[0073] In a second aspect, the embodiments of the present disclosure provide an information transmission method, executed by a second core network device; the method includes:

[0074] The first core network device is sent first information, and the first information is associated with the user plane of the terminal.

[0075] In some embodiments of the second aspect, before the first information is sent to the first core network device, the method further includes:

[0076] receive a first request sent by the first core network device, wherein the first request is used for subscribing to an event associated with a user plane of the terminal, or the first request is used for requesting to query information associated with the user plane of the terminal.

[0077] With reference to some embodiments of the second aspect, in some embodiments, the first request is used for subscribing to an event associated with a user plane of the terminal, and the method further includes:

[0078] sending a first response to the first core network device, wherein the first response is used for indicating a first subscription result.

[0079] With reference to some embodiments of the second aspect, in some embodiments, the first response includes a report of a first event associated with the user plane of the terminal.

[0080] With reference to some embodiments of the second aspect, in some embodiments, 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 to which the first request subscribes, an event identifier, an event filter, and event report information.

[0081] With reference to some embodiments of the second aspect, in some embodiments, the event identifier is an identifier of any one of the following:

[0082] a user plane reachability of the terminal;

[0083] a user plane availability of the terminal;

[0084] a user plane status of the terminal;

[0085] a reachability of the terminal;

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

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

[0088] user plane status information of the terminal;

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

[0090] With reference to 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 event filter is used for indicating any one of the following: a reachability state change of the user plane, downlink traffic reaching the user plane of the terminal, a user plane status change, and a change of the 3GPP PS Data Off status.

[0091] In some embodiments of the second aspect, in some embodiments, the target event comprises at least one of:

[0092] a reachability event of the terminal;

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

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

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

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

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

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

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

[0100] In some embodiments of the second aspect, in some embodiments, the first information comprises at least one of: an event identity, a target event, a 3rd 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, a time stamp.

[0101] In some embodiments of the second aspect, in some embodiments, the first request is used to request to subscribe to an event associated with a user plane of the terminal, and before sending the first information to the first core network device, further comprising:

[0102] detecting the event associated with the user plane of the terminal.

[0103] In some embodiments of the second aspect, in some embodiments, detecting the event associated with the user plane of the terminal comprises:

[0104] receiving a second message sent by the terminal, wherein the second message comprises an identity of the terminal and second information associated with the user plane of the terminal;

[0105] detecting the event associated with the user plane of the terminal based on the second information.

[0106] In some embodiments of the second aspect, in some embodiments, 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 state, a PDU session state, an allowed PDU session state.

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

[0108] detecting that the terminal switches to a connection management, CM, connected state, determining that the event of detecting the user plane association of the terminal is detected;

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

[0110] 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.

[0111] In some embodiments combining with the second aspect, in some embodiments, the second message is any one of:

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

[0113] a registration request message;

[0114] a service request message;

[0115] a PDU session creation request message;

[0116] a PDU session modification request message;

[0117] a PDU session release request message.

[0118] In some embodiments combining with the second aspect, in some embodiments, the first request is used to request to query information of the user plane association of the terminal, and before sending the first information to the first core network device, the method further comprises:

[0119] querying the information of the user plane association of the terminal.

[0120] In a third aspect, the embodiments of the present disclosure provide an information transmission method, the method comprising:

[0121] sending, by a second core network device, first information to a first core network device, the first information being associated with a user plane of a terminal.

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

[0123] a transceiver, configured to receive first information sent by a second core network device, the first information being associated with a user plane of a terminal.

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

[0125] The transceiver is configured to send first information to the first core network device, the first information being associated with a user plane of the terminal.

[0126] In a sixth aspect, an embodiment of the present disclosure provides a communication device, comprising:

[0127] one or more processors;

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

[0129] In a seventh aspect, an embodiment of the present disclosure provides a communication system, comprising a first core network device and a second core network device, wherein the first core network device is configured to implement the information transmission method in the first aspect, and the second core network device is configured to implement the information transmission method in the second aspect.

[0130] In an eighth aspect, an embodiment of the present disclosure provides a storage medium, which stores instructions, when the instructions are executed on a communication device, causing the communication device to perform the information transmission method in any one of the first aspect, the second aspect, or the third aspect.

[0131] In a ninth aspect, an embodiment of the present disclosure provides a computer program product, comprising a computer program, when the computer program is executed by a processor, implementing the information transmission method in any one of the first aspect, the second aspect, or the third aspect.

[0132] It can be understood that the above information transmission method, first core network device, second 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 repeated here.

[0133] The embodiments of the present disclosure provide an information transmission method and a core network device, a communication system, and a storage medium. In some embodiments, the information transmission method and the information processing method, the communication method, and other terms can be replaced with each other, the sensing device and the information processing device, the communication device, and other terms can be replaced with each other, and the information processing system and the communication system can be replaced with each other.

[0134] 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 part of the 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 manners in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, part or all steps of different embodiments can be combined arbitrarily, an embodiment can be combined with optional implementation manners of other embodiments arbitrarily.

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

[0136] 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.

[0137] 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" and the like, can represent "one and only one", and can also represent "one or more", "at least one" and the like. For example, in the case of using articles such as "a", "an", "the" and the like in English, the noun after the article can be understood as singular expression, and can also be understood as plural expression.

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

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

[0140] 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 used to represent one or more of the following technical solutions: in some embodiments, A (A is executed regardless of B); in some embodiments, B (B is executed regardless of A); in some embodiments, A and B are selected from (A and B are selectively executed); in some embodiments, A and B (A and B are executed). When there are more branches such as A, B, C, and the like, the above is similar.

[0141] In some embodiments, "A or B" and the like can include the following technical solutions according to the case: in some embodiments, A (A is executed regardless of B); in some embodiments, B (B is executed regardless of A); in some embodiments, A and B are selected from (A and B are selectively executed). When there are more branches such as A, B, C, and the like, the above is similar.

[0142] In the embodiments of the present disclosure, the prefix words "first", "second" and the like are only used to distinguish different description objects, and do not constitute limitations on the position, order, priority, quantity or content of the description objects. The description of the description objects should be referred to the description in the context of the claims or embodiments, and should not be limited by the prefix words. For example, the description 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 thereby are in the same message or not, nor limit the order of "first field" and "second field". For another example, the description 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 quantity of the description object is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "device" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the description object is "device", and "first device" and "second device" can be the same device or different devices, and the types thereof can be the same or different; for another example, the description object is "information", and "first information" and "second information" can be the same information or different information, and the content thereof can be the same or different.

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

[0144] 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.

[0145] 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.

[0146] 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.

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

[0148] 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.

[0149] 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.

[0150] 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.

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

[0152] 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.

[0153] 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-transceiving 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.

[0154] 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 a plurality of devices or device groups including all or part of the first network element, the second network element, the third network element, respectively. 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.

[0155] In some embodiments, the first network element is, for example, a Location Management Function (LMF) network element.

[0156] In some embodiments, the third 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.

[0157] In some embodiments, the second network element is, for example, an Access and Mobility Management Function (AMF) network element, without limitation of the name. The AMF network element is a logical node function network element on the core network side, which is a terminal and wireless core network control plane access point, 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.

[0158] In some embodiments, the second network element is configured to provide an access and mobility management function.

[0159] In some embodiments, the second network element is, for example, a Sensing Function (SF) network element, without limitation of the name.

[0160] In some embodiments, the SF network element can be, for example, SF-C, SF-U, and 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, without limitation.

[0161] 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 node B (eNB) in a 5G communication system, a next generation eNB (ng-eNB), a next generation node B (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 base station (Open RAN), a cloud base station (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.

[0162] 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.

[0163] 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 FIG. 1. The number and form of each subject is arbitrary, and the connection relationship between the subjects is exemplary. The subjects can not be connected or can be connected, and the connection can be in any manner, can be direct connection or indirect connection, and can be wired connection or wireless connection.

[0164] 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), and the like can be applied.

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

[0166] 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.

[0167] 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.

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

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

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

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

[0172] 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.

[0173] 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.

[0174] 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:

[0175] #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.

[0176] 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".

[0177] 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".

[0178] 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.

[0179] 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".

[0180] 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.

[0181] 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.

[0182] 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.

[0183] 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.

[0184] The information transmission method provided by the embodiments of the present disclosure can be used by the LMF to query or subscribe to the reachability or availability of the user plane of the terminal to obtain the user plane status of the terminal.

[0185] FIG. 2 is an interaction diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG. 2, the embodiments of the present disclosure relate to an information transmission method, which can be used in the communication system 100, and the method comprises the following steps:

[0186] 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 second core network device.

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

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

[0189] In some embodiments, the second core network device can be, for example, an Access and Mobility Management Function (AMF) network element, or any other network element capable of implementing the access and mobility management function. The second core network device can be, for example, an SF network element, or any other network element capable of storing user context, without limitation.

[0190] In some embodiments, the second request is used to request to establish a user plane connection.

[0191] In some embodiments, the second request can be, for example, a user plane connection establishment command. In some embodiments, the first core network device can send the second request to the second core network device through a Namf_communication_N1N2TransferMessage message.

[0192] In some embodiments, the second 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.

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

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

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

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

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

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

[0199] 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 make any limitation in this regard.

[0200] 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 to use 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 the corresponding cause value.

[0201] 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 to use 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 the cause value "user plane not available".

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

[0203] In some embodiments, the second core network device can send the second response to the first core network device through a message delivered on the N1 interface, for example, through Namf_Communication_N1MessageNotify.

[0204] 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 (e.g., set to 0) as part of the UE context. Thereafter, the first core network device will not start the network-initiated user plane connection establishment procedure again, and if the location service is still needed, it can consider using other available positioning solutions.

[0205] Step S2103: The first core network device sends a first request to the second core network device.

[0206] In some embodiments, the first request is used to request subscription to events associated with the user plane of the terminal. 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. The first request can be, for example, an event exposure service subscription request.

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

[0208] 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 to which the first request subscribes, an event identifier, an event filter, and event report information.

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

[0210] 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.

[0211] 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.

[0212] In some embodiments, since the PDU session is implemented through a user plane, the target event to which the first core network device subscribes can also comprise 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.

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

[0214] In some embodiments, the event identifier can be a newly defined event identifier. For example, the event identifier can be an identifier of any one 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.

[0215] 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, the terminal 3GPP PS Data Off state change event identity, the terminal 3GPP PS Data Off state event identity, can be any identity that is distinguished from the existing event identities.

[0216] 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.

[0217] In some embodiments, when the event identity is an identity of a newly defined event, the parameter type in the filter of the event is associated with the user plane. For example, the parameter type can be any parameter that is applicable to the reachability of the user plane, and the parameter value in the filter of the event 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.

[0218] 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 that is 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 filter of the event 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.

[0219] 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 >.

[0220] 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 the current subscription request, and the like.

[0221] In some embodiments, the second core network device can store the received PDU session status and / or allowed PDU session status and / or Protocol Configuration Option (PCO), wherein the Protocol Configuration Option can contain the 3GPP PS data off status.

[0222] In some embodiments, the second core network device can also store the DNN, S-NSSAI and their corresponding PDU session ID received from the UE. Thus, the first core network device can query (retrieve) the user plane information of the terminal from the second core network device.

[0223] In some embodiments, the first request can be used to request to query the information associated with the user plane of the terminal.

[0224] 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 query request.

[0225] In some embodiments, the first core network device can use an existing message, such as Namf_Communication_UEContextTransfer, to request to query the 3GPP PS data off status and / or the user plane availability status and / or the PDU session ID of the terminal, etc., which are not limited by the present disclosure.

[0226] In some embodiments, the first core network device can also use a new message to send the first request to retrieve the information associated with the user plane of the terminal. For example, the Namf_Communication_UEContextRetrieve request can be used to request to query the information associated with the user plane of the terminal. For example, the 3GPP PS data off status and / or the user plane availability status and / or the PDU session ID of the terminal, etc., which are not limited by the present disclosure. The first core network device can include the 3GPP PS data off status indication and / or the user plane availability status indication, and / or the PDU session ID indication, as well as the DNN and S-NSSAI of the LMF, and the terminal identifier, etc., in the message.

[0227] In some embodiments, the first core network device can also send the first request directly to the second core network device without sending a user plane connection establishment request to the terminal through the second core network device when the positioning service needs to use the LCS-UPP.

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

[0229] Step S2104, the second core network device sends a first response to the first core network device.

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

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

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

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

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

[0235] In some embodiments, the first request is a query request, and the second core network device can query a locally stored context of the terminal, and send the first response to the first core network device according to a query result. For example, the first response can include a requested 3GPP PS data opening state and / or a customer plane availability status, and / or a PDU session ID.

[0236] In some embodiments, the second core network device can send the first response through a UE context transmission message. For example, the second core network device sends the first response to the first core network device through a Namf_Communication_UEContext Transfer message.

[0237] Step S2105, a user plane state changes, and the UE sends a second message to the second core network device.

[0238] In some embodiments, the second message includes an identifier of the terminal and second information, and the second information is associated with a user plane of the terminal.

[0239] In some embodiments, the second message can further include a DNN and an S-NSSAI requested by the terminal.

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

[0241] 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 second information to the second core network device to indicate that the user plane in the UE is available.

[0242] 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.

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

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

[0245] In some embodiments, the terminal can indicate whether the user plane is available or reachable to the second core network device by sending, to the second core network device: UL NAS TRANSPORT (S-NSSAI(s), DNN registered by the UE, 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)).

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

[0247] In some embodiments, the terminal can indicate whether the user plane is available (or reachable) to the second core network device by sending, to the second core network device: Registration Request (PDU session status, allowed PDU session status), or Service Request (PDU session status, allowed PDU session status).

[0248] In some embodiments, the terminal can indicate the 3GPP PS Data Off state in the message, such as indicating the 3GPP PS Data Off state as active or indicating the 3GPP PS Data Off state as inactive.

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

[0250] In some embodiments, the terminal can send the second information to the second 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 state in the extended protocol configuration options IE in the above requests.

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

[0252] 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 second core network device can directly send the PDU session establishment request, the PDU session release request, and the PDU session modification request to the first core network device.

[0253] In step S2106, the second core network device determines the first information.

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

[0255] In some embodiments, the second core network device determines the first information associated with the user plane of the terminal upon detecting an event associated with the user plane of the terminal.

[0256] In some embodiments, the second core network device determines the first information associated with the user plane of the terminal based on the second information upon detecting an event associated with the user plane of the terminal.

[0257] In some embodiments, the first request is used to request to subscribe to an event associated with the user plane of the terminal, and the second core network device can detect the event associated with the user plane of the terminal based on the second information.

[0258] 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 that the terminal switches to a connection management (CM) connected state.

[0259] In some embodiments, the event of the user plane association of the terminal can be at least one of a 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 3GPP PS Data Off state of the terminal, and terminal user plane status information.

[0260] In some embodiments, for a UE in a CM IDLE state, the second core network device receives a second message, for example, receives a registration request or a service request message from the UE including an indication of the user plane reachability of the UE.

[0261] In some embodiments, for a UE in a CM IDLE state, the second core network device receives a second message, for example, receives a registration request or a service request message from the UE including an indication of the user plane reachability of the UE, and determines that the event of the user plane association of the terminal is detected.

[0262] In some embodiments, for a UE in a CM IDLE state, the second core network device receives a second message, for example, receives a registration request or a service request message from the UE including an indication of the user plane reachability of the UE, and determines that the event of the user plane association of the terminal is detected.

[0263] 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 that the terminal requests to establish, modify, and / or release a PDU session.

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

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

[0266] 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 that the terminal reports its 3GPP PS Data Off state. 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 that the terminal reports its 3GPP PS Data Off state.

[0267] In some embodiments, the second core network device determines to detect the event of the user plane association of the terminal upon receiving the second message containing the 3GPP PS Data Off, for example, receiving the UL NAS TRANSPORT (3GPP PS Data Off).

[0268] The implementation of the parameter that can be contained in the UL NAS TRANSPORT can refer to the related description of the above S2105, and details are not described herein.

[0269] In some embodiments, after detecting the event of the user plane association of the terminal, the second core network device can further interact with the SMF to notify the SMF of the information. For example, the second core network device can notify the SMF of the received information through the Nsmf_PDUSession_CreateSMContext message or the Nsmf_PDUSession_UpdateSMContext message.

[0270] In some embodiments, in the interaction with the SMF, the second 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.

[0271] In some embodiments, the first request is used to request to query the information of the user plane association of the terminal, and the second core network device determines the first information, which can be the user plane association information of the terminal queried by the second core network device.

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

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

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

[0275] 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 of the user plane association.

[0276] In step S2107, the second core network device sends the first information to the first core network device.

[0277] In some embodiments, the first information is associated with a user plane status of the terminal.

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

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

[0280] In some embodiments, the first request sends the first information to the first core network device through a Namf_EventExposure_Notify message.

[0281] In some embodiments, the first request is used to request subscription to a user plane associated event of the terminal, and 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 UE user plane reachability change. The message can include an event ID, an idle state indication, and the like.

[0282] In some embodiments, the first request is used to request query of user plane associated information of the terminal, and the second core network device can send the user plane status associated information of the terminal to the first core network device through a terminal context transmission message, such as through a Namf_Communication_UEContext Transfer response.

[0283] In step S2108, the first core network device updates the locally stored user plane status of the terminal.

[0284] In some embodiments, the first core network device can update the locally stored user plane status of the terminal after the first information indicates a change in the user plane status of the terminal.

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

[0286] In some embodiments, the first core network device can update the locally stored user plane status 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, PDU session establishment of the terminal, PDU session release of the terminal, PDU session modification of the terminal, and the like, without limitation in the present disclosure.

[0287] 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: a 3GPP PS Data Off change of the terminal, a 3GPP PS Data Off deactivation of the terminal, a PDU session establishment of the terminal, a PDU session release of the terminal, a PDU session modification of the terminal, and the like, without limitation of the present disclosure.

[0288] 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.

[0289] The information transmission method related to the embodiments of the present disclosure can include at least one of steps S2101-S2108. For example, step S2103 can be implemented as an independent embodiment, step S2107 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+S2107 can be implemented as an independent embodiment, and the like.

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

[0291] In the present embodiment, when the first core network device decides to use LCS-UPP for positioning services, the availability or reachability of the user plane of the terminal can be subscribed or queried from the second core network device. Thus, the first core network device can actively obtain the user plane state of the terminal.

[0292] 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 embodiments of the present disclosure relate to an information transmission method, which can be used for a first core network device. The above method includes:

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

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

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

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

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

[0298] In step S3105, the first information sent by the second core network device is received.

[0299] In step S3106, the locally stored terminal user plane state is updated.

[0300] The steps S3105-S3106 can refer to the descriptions of the steps S2107-S2108 shown in FIG. 2 and the possible implementation manners, which will not be repeated here.

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

[0302] In the present embodiment or example, each step can be independently, arbitrarily combined or exchanged in order, the optional mode or optional example can be arbitrarily combined, and can be arbitrarily combined with any step of other embodiments or other examples.

[0303] FIG. 3B is a flow diagram of an information transmission method according to yet 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:

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

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

[0306] The steps S3201-S3202 can refer to the descriptions of the steps S2103-S2104 shown in FIG. 2 and the possible implementation manners, which will not be repeated here.

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

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

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

[0310] 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.

[0311] 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.

[0312] 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 method includes the following steps:

[0313] In step S3301, first information sent by a second core network device is received.

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

[0315] In some embodiments of the present disclosure, before receiving the first information sent by the second core network device, the method further includes:

[0316] The first request is used to subscribe to an event associated with the user plane of the terminal, or the first request is used to request to query information associated with the user plane of the terminal.

[0317] In some embodiments of the present disclosure, the first request is used to subscribe to the event associated with the user plane of the terminal, and the method further includes:

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

[0319] 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.

[0320] 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 of the first request subscription, an event identity, a filter of the event, and event report information.

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

[0322] a terminal user plane reachability;

[0323] a terminal user plane availability;

[0324] a terminal user plane status;

[0325] a terminal reachability;

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

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

[0328] a terminal user plane status information event;

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

[0330] 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 change of a user plane of the terminal, downlink traffic reaching a user plane of the terminal, a status change of a user plane of the terminal, and a 3GPP PS Data Off status change of the terminal.

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

[0332] a terminal reachability event;

[0333] a terminal user plane reachability event;

[0334] a terminal user plane availability event;

[0335] a terminal user plane status event;

[0336] a terminal user plane status information event;

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

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

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

[0340] In some embodiments of the present disclosure, before the above sending the first request to the second core network device, further comprising:

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

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

[0343] In some embodiments of the present disclosure, the second response includes a reason for the user plane connection establishment failure, and the reason for the user plane connection establishment failure 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.

[0344] 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 switched, PS, data off state, packet data unit, PDU, session identification, state of the PDU session, allowed state of the PDU session, and timestamp.

[0345] In some embodiments of the present disclosure, the above method further includes: the first information indicates any one of the following, and the stored user plane state of the terminal is updated: user plane state change of the terminal, user plane availability of the terminal, 3GPP PS Data Off change of the terminal, 3GPP PS Data Off deactivation of the terminal, PDU session establishment of the terminal, PDU session release of the terminal, and PDU session modification of the terminal.

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

[0347] Step S4101, forwarding a second request sent by a first core network device to a terminal.

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

[0349] In some embodiments, the terms “forward”, “transmit”, “transmit” and the like can be replaced with each other in some scenarios.

[0350] Step S4103, receiving the first request sent by the first core network device.

[0351] Step S4104, sending the first response to the first core network device.

[0352] The steps S4101-S3104 can refer to the descriptions of the steps S2101-S2104 and possible implementation manners thereof shown in FIG. 2, and details are not described herein again.

[0353] Step S4105, receiving the second message sent by the terminal.

[0354] The second message includes the identifier of the terminal and the second information associated with the user plane of the terminal.

[0355] Step S4106, determining the first information based on the second information.

[0356] Step S4107, sending the first information to the first core network device.

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

[0358] The steps S4105-S4107 can refer to the descriptions of the steps S2105-S2107 and possible implementation manners thereof shown in FIG. 2, and details are not described herein again.

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

[0360] In the present embodiment or example, 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.

[0361] 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:

[0362] Step S4201, receiving the first request sent by the first core network device.

[0363] Step S4202: sending a first response to the first core network device.

[0364] The steps S4201-S4202 can refer to the descriptions of the steps S2103-S2104 and possible implementation manners thereof in FIG. 2, and details are not described herein again.

[0365] Step S4203: receiving a second message sent by the terminal.

[0366] Step S4204: determining the first information based on the second information.

[0367] Step S4205: sending the first information to the first core network device.

[0368] The steps S4203-S4205 can refer to the descriptions of the steps S2105-S2107 and possible implementation manners thereof in FIG. 2, and details are not described herein again.

[0369] 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.

[0370] 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.

[0371] 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:

[0372] Step S4301: sending first information to a first core network device.

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

[0374] In some embodiments, before the step of sending the first information to the first core network device, the method further includes:

[0375] receiving a first request sent by the first core network device, where the first request is used to subscribe to an event associated with the user plane of the terminal, or the first request is used to request to query information associated with the user plane of the terminal.

[0376] In some embodiments, the first request is used for subscribing to an event associated with a user plane of the terminal, and the method further comprises:

[0377] sending a first response to the first core network device, the first response being used for indicating a subscription result.

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

[0379] 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 to which the first request subscribes, an identifier of the event, an event filter, and event report information.

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

[0381] terminal user plane reachability;

[0382] terminal user plane availability;

[0383] terminal user plane status;

[0384] terminal reachability;

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

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

[0387] terminal user plane status information;

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

[0389] 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 state change of the user plane of the terminal, and a change in the 3GPP PS Data Off status of the terminal.

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

[0391] a reachability event of the terminal;

[0392] a terminal user plane reachability event;

[0393] a terminal user plane availability event;

[0394] End user plane status event;

[0395] End user plane status information event;

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

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

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

[0399] In some embodiments, the first request is used to request subscription to an event associated with a user plane of the terminal, and before sending the first information to the first core network device, further comprising:

[0400] Detecting the event associated with the user plane of the terminal.

[0401] In some embodiments, the detecting the event associated with the user plane of the terminal comprises:

[0402] Receiving a second message sent by the terminal, wherein the second message comprises an identity of the terminal and second information associated with the user plane of the terminal;

[0403] Based on the second information, detecting the event associated with the user plane of the terminal.

[0404] In some embodiments, the second information comprises at least one of the following: PDU session identity, old PDU session identity, PDU session establishment request, PDU session release request, PDU session modification request, session and service continuity (SSC) mode, extended protocol configuration option, 3GPP PS Data Off status, PDU session status, and allowed PDU session status.

[0405] In some embodiments, the detecting the event associated with the user plane of the terminal comprises at least one of the following:

[0406] Detecting that the terminal switches to a connection management (CM) connected state, and determining that the event associated with the user plane of the terminal is detected;

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

[0408] 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.

[0409] In some embodiments, the second message is any of the following:

[0410] Uplink non-access stratum transport message;

[0411] a registration request message;

[0412] a service request message;

[0413] a PDU session creation request message;

[0414] a PDU session modification request message;

[0415] a PDU session release request message.

[0416] In some embodiments, the first request is used to request information associated with a user plane of the terminal, and before sending the first information to the first core network device, the method further comprises:

[0417] obtaining information associated with the user plane of the terminal.

[0418] In some embodiments, the first information comprises at least one of the following: event identification, target event, 3rd Generation Partnership Project (3GPP) Packet Switched (PS) data off state, packet data unit (PDU) session identification, PDU session state, allowed PDU session state, terminal identification, and timestamp.

[0419] FIG. 5 is an interaction diagram of an information transmission method according to another embodiment of the present disclosure. As shown in FIG. 5, the embodiments of the present disclosure relate to an information transmission method, which can be used in a communication system. The method comprises:

[0420] In step S5101, the second core network device sends first information to the first core network device.

[0421] The specific implementation of step S5101 can refer to the detailed description of any of the above embodiments, which will not be described here.

[0422] Hereinafter, the first core network device is taken as an example of LMF, and the second core network device is taken as an example of AMF to exemplarily introduce the above method.

[0423] As shown in FIG. 6A, FIG. 6A is a schematic diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG. 6A, the process of subscribing to an event exposure service by the LMF to the AMF can comprise the following steps:

[0424] 600. The LMF decides to use LCS-UPP for positioning service.

[0425] 601. 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.

[0426] Optionally, the LMF can send to the AMF: Namf_Communication_N1N2MessageTransfer to carry the user plane connection setup command.

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

[0428] 602. The UE sends to the LMF through the AMF a user plane connection setup failure response.

[0429] Optionally, if the UE determines that the user plane is not available, e.g. due to the UE setting the 3GPP PS data off to “active” state, or the UE determines to use control plane positioning or other positioning methods, e.g. due to user plane congestion or lack of user plane resources, the UE can send a user plane connection setup failure message containing a cause value “user plane not available”.

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

[0431] Optionally, the AMF can transfer the user plane connection setup failure (or user plane not available response to the LMF through the following message: Namf_Communication_N1MessageNotify.

[0432] Upon 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. user plane not available) or user plane availability as false (e.g. set to 0) as part of the UE context. The LMF will not initiate the network initiated user plane connection setup procedure again, and can consider using other available positioning solutions if location service is still needed.

[0433] Note: Steps 600-602 can trigger step 603, but step 603 can also be performed without steps 600-602 (i.e. steps 600-602 can be skipped and step 603 can be performed directly).

[0434] 603. The LMF sends to the AMF a subscription request.

[0435] The subscription request is for subscribing to the user plane information / user plane availability / user plane status / UE reachability of the UE.

[0436] Optionally, the subscription request can include UE ID, event ID, event filter, event reporting information.

[0437] 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 can be available for establishing a user plane connection.

[0438] Optionally, the new event ID can be a user plane ID / UE user plane availability ID / UE user plane status ID.

[0439] Optionally, the enhancement of the existing event ID can be an enhancement of UE reachability.

[0440] Optionally, for the new event ID, a new event filter can be defined as: Event UE reachability applicable to the user plane. Parameter value = UE user plane reachability status change or DL traffic can reach the UE user plane. If the parameter type is missing in the UE reachability filter in the user plane event subscription request, the parameter type can be interpreted as "user plane status change".

[0441] Optionally, to enhance the existing function, the event filter can be enhanced as: Event UE reachability applicable. For example, parameter type = control plane, value = UE reachability status change or UE reachability of DL traffic; parameter type = user plane, value = UE user plane reachability status change or DL traffic can reach the UE user plane.

[0442] Optionally, the Namf_EventExposure_Subscribe request sent by the LMF to the AMF can include: UE ID, event ID, event filter, event report information, etc.

[0443] 604. The AMF responds to the LMF.

[0444] Optionally, the AMF can respond to the subscription request before the expiration time.

[0445] Optionally, the first event report of "user plane UE reachability" (if available) can be included in the response.

[0446] 605. User plane status change.

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

[0448] 606. The AMF detects the reachability of the user plane.

[0449] Optionally, the AMF can detect whether the user plane is reachable according to one or more of the following criteria:

[0450] A. The AMF detects that the UE transitions to CM-CONNECTED state.

[0451] For a UE in CM-IDLE, the AMF receives (N1) NAS signaling, which means that the UE is available for DL traffic, e.g. the AMF receives a Registration Request or Service Request message from the UE.

[0452] Optionally, the UE can include its user plane reachability in these messages.

[0453] For example, UE -> AMF: Registration Request / Service Request (User plane reachability of the UE). Wherein, “->” is used to indicate sending, or transmission.

[0454] B. The AMF detects that the UE reports to the AMF its 3GPP PS data off status.

[0455] For example, the UE reports to the AMF its 3GPP PS data off status as “Deactivated” or “Inactive”.

[0456] 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.

[0457] 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)).

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

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

[0460] For both case a and case b, upon receiving this 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.

[0461] For example, the 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).

[0462] C. The AMF detects that the UE requests to establish / modify / release a PDU session.

[0463] To establish / modify / 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 option IE can be included.

[0464] For example, the UE can send a PDU session creation, modification or release request to the AMF in 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).

[0465] Optionally, after receiving the message from the UE, the AMF can also interact with the SMF to notify the received message through the Nsmf_PDUSession_CreateSMContext message or the Nsmf_PDUSession_UpdateSMContext message. 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)

[0466] 607. The AMF sends first information to the LMF.

[0467] For example, the AMF can send the first information to the LMF through the following message: Namf_EventExposure_Notify message to notify the LMF of the detected change in user plane UE reachability. The message includes an event ID and optionally an idle state indication.

[0468] That is, the AMF can send the first information AMF->LMF: Namf_EventExposure_Notify (AMF ID, UE ID, Event ID, IDLE state indication) to the LMF in the following way.

[0469] 608. The LMF updates the local stored UE reachability for the user plane.

[0470] As shown in FIG. 6B, FIG. 6B is a schematic diagram of an information transmission method provided in an embodiment of the present disclosure. Since the AMF can store the received PDU session status and / or allowed PDU session status Protocol Configuration Option (PCO) (including 3GPP PS data off status), and also store the DNN, S-NSSAI and their corresponding PDU session ID received from the UE. Therefore, in order to obtain the user plane availability / status, the LMF can retrieve (or query) the AMF.

[0471] As shown in FIG. 6B, the process of the LMF querying the user plane availability from the AMF can include the following steps:

[0472] 610. The LMF decides to use LCS-UPP for the positioning service.

[0473] 611. The LMF sends a user plane connection setup command to the UE through the AMF to establish a user plane connection between the UE and the LMF.

[0474] 612. The UE sends a user plane connection setup failure response to the LMF through the AMF.

[0475] 613. The user plane status changes.

[0476] 614. The AMF detects and updates the user plane availability.

[0477] Optionally, the AMF also stores the received PDU session status and / or allowed PDU session status, PCO (including 3GPP PS data off status), and also stores the DNN, S-NSSAI and PDU session ID as part of the UE context.

[0478] The above 603 and 604 can refer to 605 and 606 shown in FIG. 6A, which will not be described here.

[0479] 615. The LMF sends a query request to the AMF.

[0480] Optionally, after the LMF receives the response from the AMF in step 2 that the user plane is not available for the UE, the LMF can retrieve the 3GPP PS data off status and / or the user plane availability status of the AMF, and / or the PDU session ID.

[0481] Optionally, the LMF can use the existing message Namf_Communication_UEContextTransfer request to retrieve the 3GPP PS data off status and / or the user plane availability status, and / or the PDU session ID.

[0482] Optionally, the LMF can also use a new message to retrieve the above information. For example, the LMF includes the 3GPP PS data off status indication and / or the user plane availability status indication, and / or the PDU session ID indication in the message using the Namf_Communication_UEContextRetrieve request, as well as the DNN and S-NSSAI of the LMF, and the UE ID.

[0483] For example, the LMF can retrieve the user plane status of the UE from the AMF by the following way: LMF -> AMF: Namf_Communication_UEContextTransfer request (3GPP PS data off status indication and / or the user plane availability status indication, and / or the PDU session ID indication, DNN, S-NSSAI, UE ID).

[0484] 616. The AMF retrieves the locally stored UE context and responds to the LMF.

[0485] Optionally, the response returned by the LMF can include the requested 3GPP PS data on status and / or the user plane availability status, and / or the PDU session ID.

[0486] For example, the AMF can return the retrieval response to the LMF by the following way: AMF -> LMF: Namf_Communication_UEContextTransfer response.

[0487] Note: The order of steps 613-614 and steps 615-616 is not fixed. For example, step 615 can be performed first, and then steps 613, 614 and 616 are performed, and so on, which is not limited in the present disclosure.

[0488] 617. The LMF updates the locally stored UE reachability of the user plane.

[0489] FIG. 7A 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. 7A, the first core network device 7100 can include at least one of a transceiver module 7101, a processing module 7102, and the like. The first core network device 7100 can include:

[0490] The transceiver module 7101 is configured to receive first information sent by a second core network device, wherein the first information is associated with a user plane of a terminal.

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

[0492] send a 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, or the first request is used to request to query information associated with the user plane of the terminal.

[0493] In some embodiments of the present disclosure, the first request is used to subscribe to the event associated with the user plane of the terminal, and the transceiver module 7101 is further configured to:

[0494] receive a first response sent by the second core network device, wherein the first response is used to indicate a first subscription result.

[0495] 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.

[0496] 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.

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

[0498] terminal user plane reachability;

[0499] terminal user plane availability;

[0500] terminal user plane status;

[0501] terminal reachability;

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

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

[0504] terminal user plane status information;

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

[0506] In some embodiments of the present disclosure, 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 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 state change, a 3GPP PS Data Off state change.

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

[0508] a reachability event of the terminal;

[0509] a terminal user plane reachability event;

[0510] a terminal user plane availability event;

[0511] a terminal user plane state event;

[0512] a terminal user plane state information event;

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

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

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

[0516] In some embodiments of the present disclosure, the above transceiver 7101 is further configured to:

[0517] determine to use a location service user plane protocol LCS-UPP for a location service, send a second request to the terminal through the second core network device, the second request being used to request to establish a user plane connection;

[0518] receive a second response sent by the terminal through the second core network device, the second response being used to indicate that the user plane connection establishment fails.

[0519] 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 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.

[0520] In some embodiments of the present disclosure, the first information comprises 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.

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

[0522] The first information indicates any of the following: a change in the user plane status of the terminal, availability of the user plane of the terminal, a change in 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 the PDU session of the terminal, and modification of the PDU session of the terminal.

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

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

[0525] FIG. 7B is a structural schematic diagram of a second core network device according to another embodiment of the present disclosure. As shown in FIG. 7B, the second core network device 7200 can include at least one of a transceiver module 7201, a processing module 7202, and the like. The second core network device 7200 can include:

[0526] The transceiver module 7201 is configured to send first information to a first core network device, the first information being associated with a user plane of a terminal.

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

[0528] The transceiver module 7201 is further configured to receive a first request sent by the first core network device, wherein the first request is used to subscribe to an event associated with the user plane of the terminal, or the first request is used to request to query information associated with the user plane of the terminal.

[0529] In some embodiments of the present disclosure, the first request is used to subscribe to an event associated with the user plane of the terminal, and the transceiver module 7201 is further configured to:

[0530] The transceiver module 7201 is further configured to send a first response to the first core network device, the first response being used to indicate a first subscription result.

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

[0532] In some embodiments of the disclosure, 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.

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

[0534] a user plane reachability of the terminal;

[0535] a user plane availability of the terminal;

[0536] a user plane status of the terminal;

[0537] a reachability of the terminal;

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

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

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

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

[0542] In some embodiments of the disclosure, 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.

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

[0544] a reachability event of the terminal;

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

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

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

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

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

[0550] The terminal's 3GPP PS Data Off state

[0551] PDU session creation, modification, or release requests.

[0552] In some embodiments of this disclosure, the first information includes at least one of the following: an event identifier, a target event, 3GPP packet switching PS data off status indication information, a packet data unit (PDU) session identifier, the status of the PDU session, the status of the allowed PDU session, and a timestamp.

[0553] In some embodiments of this disclosure, the first request is used to request subscription to events associated with the user plane of the terminal, and the processing module 7202 is further used to:

[0554] An event associated with the user plane of the terminal was detected.

[0555] In some embodiments of this disclosure, it also includes:

[0556] The transceiver module 7201 described above is also used to receive a second message sent by the terminal, wherein the second message includes the identifier of the terminal and second information associated with the user plane of the terminal;

[0557] The aforementioned processing module 7202 is used to detect events associated with the user plane of the terminal based on the second information.

[0558] In some embodiments of this disclosure, the second information includes at least one of the following: PDU session identifier, old PDU session identifier, PDU session establishment request, PDU session release request, PDU session modification request, Session and Service Continuity (SSC) mode, Extended Protocol Configuration Options, 3GPP PS Data Off status, PDU session status, and allowed PDU session status.

[0559] In some embodiments of this disclosure, the detection of user plane-related events of the terminal includes at least one of the following:

[0560] The terminal was detected to have switched to the Connection Management (CM) connection state, and an event associated with the user plane of the terminal was detected.

[0561] The terminal reported its 3GPP PS data off state, and the user plane associated event of the terminal was detected.

[0562] If a terminal requests to establish, modify, and / or release a PDU session, an event is identified that indicates the terminal's user plane association.

[0563] In some embodiments of this disclosure, the second message is any one of the following:

[0564] uplink non-access stratum transport message;

[0565] registration request message;

[0566] service request message;

[0567] pdu session creation request message;

[0568] pdu session modification request message;

[0569] pdu session release request message.

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

[0571] query information associated with the user plane of the terminal.

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

[0573] 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 to be performed by the processing module. Alternatively, the processing module can be mutually replaced with a processor.

[0574] 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 any of the above methods or realize the functions of each unit or module 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 above 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.

[0575] 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, the hardware circuit can also be 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.

[0576] FIG. 8A is a structural schematic diagram of a communication device according to an embodiment of the present disclosure. The communication device 8100 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 8100 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.

[0577] As shown in FIG. 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 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 8100 is used to implement any of the above methods.

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

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

[0580] 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.

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

[0582] The communication device 8100 described in the above embodiments can be a terminal or a network device or a third entity, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 can not be limited by Figure 8A. 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.

[0583] Figure 8B is a structural schematic diagram of a chip according to an embodiment of the present disclosure. For the case where the communication device 8100 can be a chip or a chip system, the structural schematic diagram of the chip 8200 shown in Figure 8B can be referred to, but is not limited thereto.

[0584] The chip 8200 comprises one or more processors 8201, and the chip 8200 is configured to execute any of the above methods.

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

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

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

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

[0589] The disclosure further proposes a storage medium, and the storage medium stores instructions, and the instructions, when executed on the communication device 8100, cause the communication device 8100 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.

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

[0591] 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.

[0592] 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.

[0593] 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.

[0594] 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.

[0595] 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 sent by a second core network device, the first information being associated with a user plane of a terminal.

2. The method of claim 1, wherein, Before the receiving the first information sent by the second core network device, the method further comprises any one of the following: sending a 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, or the first request is used to request to query information associated with the user plane of the terminal.

3. The method of claim 2, wherein, When the first request is used to subscribe to the event associated with the user plane of the terminal, the method further comprises: receiving a first response sent by the second core network device, the first response being used to indicate 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 reachability; third generation partnership project (3GPP) packet switched (PS) data off status of the terminal; 3GPP PS Data Off status change of the terminal; terminal user plane status information; PDU session creation, modification, or release request.

7. The method of claim 5, wherein, The parameter type in the event filter is associated with the user plane, and the parameter value in the event filter is used to indicate 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, and 3GPP PS Data Off state change.

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; 3GPP PS Data Off status change event 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 the first request to the second core network device, the method further comprises: determining to use a location service user plane protocol (LCS-UPP) for a location service, sending a second request to the terminal through the second core network device, the second request being used to request to establish a user plane connection; receiving a second response sent by the terminal through the second core network device, the second response being used to indicate that the user plane connection establishment fails.

10. The method of claim 9, wherein, The second response comprises a user plane connection establishment failure cause, and the user plane connection establishment failure cause 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 causes.

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 one of the following: a user plane state change of the terminal, user plane availability of the terminal, 3GPP PS Data Off change of the terminal, 3GPP PS Data Off deactivation 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, The method is performed by a second core network device and includes: sending, to a first core network device, first information associated with a user plane of a terminal.

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

15. The method of claim 14, wherein, The first request is used to subscribe to an event associated with the user plane of the terminal, and the method further includes: sending, to the first core network device, a first response, the first response being used to indicate a first 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 13-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 one 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; 3GPP PS Data Off state change 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 a user plane, and a parameter value in the event filter is used to indicate any one of the following: reachability state change of the user plane, downlink traffic reachability of the user plane of the terminal, user plane state change, and 3GPP PS Data Off state change.

20. The method of any one of claims 17-19, wherein, The target event includes at least one of the following: reachability event of the terminal; terminal user plane reachability event; terminal user plane availability event; terminal user plane state event; terminal user plane state 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.

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, 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, allowed PDU session states, and a timestamp.

22. The method of any one of claims 14-21, wherein, The first request is used to request subscription to an event associated with a user plane of the terminal, and before the first information is sent to the first core network device, the method further includes: detecting an event associated with a user plane of the terminal.

23. The method of claim 22, wherein, The detecting of the event associated with the user plane of the terminal includes: receiving a second message sent by the terminal, wherein the second message includes an identifier of the terminal and second information associated with a user plane of the terminal; detecting an event associated with a user plane 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) mode, an extended protocol configuration option, a 3GPP PS Data Off state, a PDU session state, and allowed PDU session states.

25. The method of claim 23 or 24, wherein, The detecting of the event associated with the user plane of the terminal includes at least one of the following: detecting that the terminal switches to a connection management (CM) connected state, and determining that the event associated with the user plane of the terminal is detected; 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; 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.

26. The method of any one of claims 23-25, wherein, The second message is any of the following: an uplink non-access stratum (NAS) transport message; a registration request message; a service request message; a PDU session creation request message; a PDU session modification request message; a PDU session release request message.

27. The method of any one of claims 14-26, wherein, The first request is used to request information associated with a user plane of the terminal, and before the first information is sent to the first core network device, the method further includes: querying information associated with a user plane of the terminal.

28. An information transmission method, characterized by, The method is performed by a communication system, and the method includes: a second core network device sending first information associated with a user plane of a terminal to a first core network device.

29. A first core network device, comprising: The first core network device includes: a transceiver configured to receive first information associated with a user plane of a terminal sent by a second core network device.

30. A second core network device, comprising: The second core network device includes: a transceiver configured to send first information associated with a user plane of a terminal to a first core network device.

31. A communications device, characterized by includes: one or more processors; wherein the processor is configured to perform the information transmission method of any one of claims 1-27.

32. A storage medium, the storage medium storing instructions, wherein, When the instructions are run on a communication device, the instructions cause the communication device to perform the information transmission method of any one of claims 1-27.

33. A communication system, characterized by The application further provides a core network device, comprising a first core network device and a second core network device, wherein the first core network device is configured to perform the information transmission method according to any one of claims 1-12, and the second core network device is configured to perform the information transmission method according to any one of claims 13-27.

34. A computer program product, characterised in that, The application further provides a computer program, which, when executed by a processor, implements the information transmission method according to any one of claims 1-27.

Images