WO2025010596A1 - Message sending method, message receiving method, core network function, communication device, and storage medium - Google Patents

Abstract

The present disclosure relates to the technical field of communications, and particularly relates to a message sending method, a message receiving method, a core network function, a communication device, and a storage medium. The message sending method comprises: sending a first message to a first core network function, wherein the first message is used for triggering the processing for a user plane connection. According to the present disclosure, a terminal can send a first message to a first core network function in a core network, so as to trigger, by means of the first message, the processing for a user plane connection. Accordingly, the processing for the user plane connection can be triggered by the terminal, without being restricted to the situation that the processing for the user plane connection is triggered by an LMF, thereby improving the flexibility of the processing for the user plane connection.

Description

Message sending and receiving method, core network function, communication device and storage medium Technical Field

The present disclosure relates to the field of communication technology, and in particular to a message sending method, a message receiving method, a core network function, a communication device and a storage medium.

Background Art

The terminal and the network function communicate through the user plane, that is, there can be a user plane connection between the terminal and the network function. Communication through the user plane has some advantages, such as reducing some signaling processes, but there are some limitations in the processing of user plane connections.

Summary of the invention

The embodiments of the present disclosure propose message sending and receiving methods, core network functions, communication equipment and storage media to solve the technical problems existing in the processing of user plane connections in related technologies.

According to a first aspect of an embodiment of the present disclosure, a message sending method is proposed, which is executed by a terminal. The method includes: sending a first message to a first core network function, wherein the first message is used to trigger processing of a user plane connection.

According to a second aspect of an embodiment of the present disclosure, a message receiving method is proposed, which is executed by a first core network function. The method includes: receiving a first message sent by a terminal, wherein the first message is used to trigger processing of a user plane connection.

According to the third aspect of an embodiment of the present disclosure, a message receiving method is proposed, which is executed by a second core network function. The method includes: determining to process the user plane connection, and sending a third message to a third core network function, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

According to the fourth aspect of an embodiment of the present disclosure, a message receiving method is proposed, which is executed by a third core network function. The method includes: receiving a third message sent by a second core network function, wherein the third message is used to update a packet data unit session, or to release a packet data unit session, and when the second core network function determines to process a user plane connection, it triggers the sending of the third message.

According to the fifth aspect of an embodiment of the present disclosure, a message sending method is proposed, the method comprising: a terminal sends a first message to a first core network function, wherein the first message is used to trigger processing of a user plane connection; the first core network function sends a second message to a second core network function, wherein the second message includes a modification indication or a termination indication; the second core network function sends a third message to a third core network function, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

According to a sixth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: one or more processors; wherein the terminal is used to execute the message sending method described in the first aspect.

According to the seventh aspect of an embodiment of the present disclosure, a core network function is proposed, including: one or more processors; wherein the network device is used to execute the message receiving method described in the second aspect.

According to an eighth aspect of an embodiment of the present disclosure, a core network function is proposed, including: one or more processors; wherein the network device is used to execute the message receiving method described in the third aspect.

According to a ninth aspect of an embodiment of the present disclosure, a core network function is provided, including: one or more processors; Wherein, the network device is used to execute the message receiving method described in the fourth aspect.

According to the tenth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising: one or more processors; wherein the processor is used to call instructions so that the communication device executes the message sending method described in the first aspect, and the message receiving method described in the second aspect, the third aspect, and the fourth aspect.

According to the eleventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a terminal and a core network function, wherein the terminal is configured to implement the message sending method described in the first aspect, and the core network device is configured to implement the message receiving method described in the second aspect, the third aspect, and the fourth aspect.

According to the twelfth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the message sending method described in the first aspect, and the message receiving method described in the second aspect, the third aspect, and the fourth aspect.

According to an embodiment of the present disclosure, a terminal may send a first message to a first core network function in a core network, and trigger processing of a user plane connection through the first message, for example, the first core network function includes LMF. Accordingly, processing of the user plane connection may be triggered by the terminal, so that the processing of the user plane connection is not limited to being triggered by the LMF, thereby improving the flexibility of processing of the user plane connection.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

FIG2 is an interactive schematic diagram showing a message sending method according to an embodiment of the present disclosure.

FIG3 is a schematic flowchart of a message sending method according to an embodiment of the present disclosure.

FIG4 is a schematic flow chart of a message receiving method according to an embodiment of the present disclosure.

FIG5 is a schematic flow chart of a message receiving method according to an embodiment of the present disclosure.

FIG6 is a schematic flow chart of a message receiving method according to an embodiment of the present disclosure.

FIG. 7 is an interactive flow chart showing another message sending method according to an embodiment of the present disclosure.

FIG8 is an interaction flow chart showing yet another message sending method according to an embodiment of the present disclosure.

FIG9 is a schematic block diagram of a terminal according to an embodiment of the present disclosure.

FIG. 10 is a schematic block diagram showing a core network function according to an embodiment of the present disclosure.

FIG. 11 is a schematic block diagram showing a core network function according to an embodiment of the present disclosure.

FIG. 12 is a schematic block diagram showing a core network function according to an embodiment of the present disclosure.

FIG. 13 is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure.

FIG. 14 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure.

DETAILED DESCRIPTION

The embodiments of the present disclosure provide message sending and receiving methods, core network functions, communication equipment and storage media.

In a first aspect, an embodiment of the present disclosure proposes a message sending method, which is executed by a terminal, and the method includes: sending a first message to a first core network function, wherein the first message is used to trigger processing of a user plane connection.

In the above embodiment, the terminal may send a first message to the first core network function, and trigger the processing of the user plane connection through the first message. For example, the first core network function includes LMF. Accordingly, the processing of the user plane connection can be triggered by the terminal, so that the processing of the user plane connection is not limited to being triggered by the LMF, which improves the flexibility of the user plane connection processing.

In combination with some embodiments of the first aspect, in some embodiments, the processing of the user plane connection includes at least one of the following: modification; and termination.

In combination with some embodiments of the first aspect, in some embodiments, the first message further includes a reason for processing the user plane connection.

In combination with some embodiments of the first aspect, in some embodiments, the first message is sent in at least one of the following ways: user plane; control plane.

In combination with some embodiments of the first aspect, in some embodiments, the first message is sent via a control plane, and the first message is carried in at least one of the following: an uplink non-access layer transmission message; or a service request message.

In combination with some embodiments of the first aspect. In some embodiments, the first message is sent through the control plane, and the sending of the first message to the first core network function includes: sending the first message to the second core network function through the control plane, wherein the second core network function is used to send the first message to the first core network function.

In combination with some embodiments of the first aspect, in some embodiments, the first core network function includes a location management function, and/or the second core network function includes an access mobility management function.

In combination with some embodiments of the first aspect. In some embodiments, sending the first message to the first core network function includes at least one of the following: determining that there is a user plane connection, sending the first message to the first core network function through the user plane or the control plane; determining that there is no user plane connection, sending the first message to the first core network function through the control plane.

In a second aspect, an embodiment of the present disclosure proposes a message receiving method, which is executed by a first core network function, and the method includes: receiving a first message sent by a terminal, wherein the first message is used to trigger processing of a user plane connection.

In the above embodiment, the first core network function may receive the first message sent by the terminal, and trigger the processing of the user plane connection according to the first message. For example, the first core network function includes LMF. Accordingly, the processing of the user plane connection may be triggered by the terminal, so that the processing of the user plane connection is not limited to being triggered by the LMF, thereby improving the flexibility of the user plane connection processing.

In combination with some embodiments of the second aspect, in some embodiments, the processing of the user plane connection includes at least one of the following: modification; termination.

In combination with some embodiments of the second aspect, in some embodiments, the first message includes a reason for processing the user plane connection.

In combination with some embodiments of the second aspect, in some embodiments, the first message is received via at least one of the following methods: user plane; control plane.

In combination with some embodiments of the second aspect, in some embodiments, the first message is received via a control plane, and the first message is carried in at least one of the following: an uplink non-access layer transmission message; or a service request message.

In combination with some embodiments of the second aspect. In some embodiments, the first message is received via a control plane, The receiving a first message sent by the terminal includes: receiving the first message received from the terminal and sent by a second core network function.

In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending a second message to the second core network function, wherein the second message includes a modification indication or a termination indication.

In combination with some embodiments of the second aspect, in some embodiments, the first core network function includes a location management function, and/or the second core network function includes an access mobility management function.

In a third aspect, an embodiment of the present disclosure proposes a message receiving method, which is executed by a second core network function, and the method includes: determining to process the user plane connection, and sending a third message to a third core network function, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

In the above embodiment, since processing the user plane connection, such as modification or termination, will cause the packet data unit session to be affected, the second core network function in the core network can send a third message to the third core network function when determining that the user plane connection needs to be processed, so that the third core network function can update the packet data unit session according to the third message, or use it to release the packet data unit session. This is conducive to ensuring that the updated or released packet data unit session adapts to the modified or terminated user plane connection.

In combination with some embodiments of the third aspect, in some embodiments, the processing of the user plane connection includes at least one of the following: modification; termination.

In combination with some embodiments of the third aspect, the method further includes: receiving a first message sent by a terminal, wherein the first message is used to trigger processing of a user plane connection;

Send the first message to the first core network function.

In combination with some embodiments of the third aspect, in some embodiments, the first message includes a reason for processing the user plane connection.

In combination with some embodiments of the third aspect, in some embodiments, the first message is carried in at least one of the following sent by the terminal: an uplink non-access layer transmission message; a service request message.

In combination with some embodiments of the third aspect, in some embodiments, the method further includes: receiving a second message sent by the first core network function, where the second message is used by the second core network function to determine to process the user plane connection.

In combination with some embodiments of the third aspect, in some embodiments, the second message includes a modification indication or a termination indication.

In combination with some embodiments of the third aspect. In some embodiments, the third message includes: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

In combination with some embodiments of the third aspect. In some embodiments, the third message includes: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release a packet data unit session.

In combination with some embodiments of the third aspect, in some embodiments, the second core network function includes an access mobility management function, and/or the third core network function includes a session management function.

In a fourth aspect, an embodiment of the present disclosure proposes a message receiving method, which is executed by a third core network function, and the method includes: receiving a third message sent by a second core network function, wherein the third message is used to update a packet data unit session, or to release a packet data unit session, and when the second core network function determines to process the user plane connection, it triggers the sending of the third message.

In combination with some embodiments of the fourth aspect, in some embodiments, the processing of the user plane connection includes at least one of the following: modification; termination.

In combination with some embodiments of the fourth aspect. In some embodiments, the third message includes: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

In combination with some embodiments of the fourth aspect. In some embodiments, the third message includes: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release the packet data unit session.

In combination with some embodiments of the fourth aspect, in some embodiments, the second core network function includes an access mobility management function, and/or the third core network function includes a session management function.

In the fifth aspect, an embodiment of the present disclosure proposes a message sending method, the method comprising: a terminal sends a first message to a first core network function, wherein the first message is used to trigger processing of a user plane connection; the first core network function sends a second message to a second core network function, wherein the second message includes a modification indication or a termination indication; the second core network function sends a third message to a third core network function, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

In a sixth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the message sending method described in the first aspect and the optional implementation manner of the first aspect.

In the seventh aspect, an embodiment of the present disclosure proposes a core network function, including: one or more processors; wherein the network device is used to execute the message receiving method described in the second aspect and the optional implementation method of the second aspect.

In an eighth aspect, an embodiment of the present disclosure proposes a core network function, comprising: one or more processors; wherein the network device is used to execute the message receiving method described in the third aspect and the optional implementation manner of the third aspect.

In the ninth aspect, an embodiment of the present disclosure proposes a core network function, including: one or more processors; wherein the network device is used to execute the message receiving method described in the fourth aspect and the optional implementation method of the fourth aspect.

In the tenth aspect, an embodiment of the present disclosure proposes a communication device, wherein the communication device includes: one or more processors; one or more memories for storing instructions; wherein the processor is used to call the instructions so that the communication device executes the message sending method described in the first aspect, the optional implementation method of the first aspect, the message receiving method described in the second aspect, the third aspect and the fourth aspect, the optional implementation method of the second aspect, the optional implementation method of the third aspect and the optional implementation method of the fourth aspect.

In the eleventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal, a first core network function, a second core network function, and a third core network function; wherein the terminal is configured to execute the message sending method described in the first aspect and the optional implementation method of the first aspect, the first core network function is configured to execute the message sending method described in the second aspect and the optional implementation method of the second aspect, the second core network function is configured to execute the message sending method described in the third aspect and the optional implementation method of the third aspect, and the third core network function is configured to execute the message sending method described in the fourth aspect and the optional implementation method of the fourth aspect.

In the twelfth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the message sending method described in the first aspect, the optional implementation method of the first aspect, the second aspect, the third aspect and the fourth aspect, the optional implementation method of the second aspect, the optional implementation method of the third aspect and the optional implementation method of the fourth aspect.

In the thirteenth aspect, the embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the message sending method described in the first aspect and the optional implementation method of the first aspect, the second aspect, the third aspect and the fourth aspect, the optional implementation method of the second aspect, and the optional implementation method of the third aspect. and the message receiving method described in the optional implementation of the fourth aspect.

In the fourteenth aspect, an embodiment of the present disclosure proposes a computer program, which, when running on a computer, enables the computer to execute the message sending method described in the first aspect, the optional implementation method of the first aspect, the message receiving method described in the second aspect, the third aspect and the fourth aspect, the optional implementation method of the second aspect, the optional implementation method of the third aspect and the optional implementation method of the fourth aspect.

It is understandable that the above-mentioned terminal, core network function, communication device, communication system, storage medium, program product, and computer program are all used to execute the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, and will not be repeated here.

The embodiments of the present disclosure propose message sending and receiving methods, core network functions, communication devices and storage media. In some embodiments, the terms such as message sending method, message receiving method, information processing method, communication method, etc. can be replaced with each other, the terms such as terminal, core network function, information processing device, communication device, etc. can be replaced with each other, and the terms such as information processing system, communication system, etc. can be replaced with each other.

The embodiments of the present disclosure are not exhaustive, but are only illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined, for example, some or all of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

In each embodiment of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and/or descriptions between the embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment based on their internal logical relationships.

The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "one", "an", "the", "above", "said", "foregoing", "this", etc., may mean "one and only one", or may mean "one or more", "at least one", etc.

For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article can be understood as a singular expression or a plural expression.

In the embodiments of the present disclosure, “plurality” refers to two or more.

In some embodiments, terms such as "at least one of", "one or more", "a plurality of", "multiple" and the like can be used interchangeably.

In some embodiments, "at least one of A and B", "A and/or B", "A in one case, B in another case", "in response to one case A, in response to another case B", etc., may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, etc., the above is also similar.

In some embodiments, the description of "A or B" may include the following technical solutions according to the situation: in some embodiments, A (execute A independently of B); in some embodiments, B (execute B independently of A); in some embodiments, select from A and B to execute (A and B are selectively executed). The same is true for support time.

The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects, and do not constitute restrictions on the position, order, priority, quantity or content of the description objects. The statement of the description object refers to the description in the context of the claims or embodiments, and should not constitute unnecessary restrictions due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields", and the "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number, and can be one or more. Taking the "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes may be the same or different. For example, if the description object is "device", then the "first device" and the "second device" may be the same device or different devices, and their types may be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" may be the same information or different information, and their contents may be the same or different.

In some embodiments, “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

In some embodiments, terms such as "in response to ...", "in response to determining ...", "in the case of ...", "at the time of ...", "when ...", "if ...", "if ...", etc. can be used interchangeably.

In some embodiments, terms such as "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", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "no more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

In some embodiments, devices and the like can be interpreted as physical or virtual, and their names are not limited to those in the embodiments.

The recorded names, terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

In some embodiments, "network" may be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

In some embodiments, the terms "access network device (AN device), "radio access network device (RAN device)", "base station (BS)", "radio base station (radio base station)", "fixed station (fixed station)", "node", "access point (access point)", "transmission point (TP)", "reception point (RP)", "transmission/reception point (TRP)", "panel", "antenna panel (antenna panel)", "antenna array (antenna array)", "cell", "macro cell", "small cell (small cell)", "femto cell (femto cell)", "pico cell (pico cell)", "sector (sector)", "cell group (cell)", "serving cell", "carrier (carrier)", "component carrier (component carrier)", "bandwidth part (bandwidth part (BWP))" and so on can be used interchangeably.

In some embodiments, the term “terminal”, “terminal device”, “user equipment (UE)”, “user terminal”, “mobile station (MS)”, “mobile terminal (MT)”, “subscriber station”, “mobile single The terms mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client and the like may be used interchangeably.

In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the access network device, the core network device, or the network device and the communication between the terminals is replaced by the communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may also be configured to have a structure that has all or part of the functions of the terminal.

In some embodiments, acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

In some embodiments, data, information, etc. may be obtained with the user's consent.

In addition, each element, each row, or each column in the table of the embodiments of the present disclosure may be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns may also be implemented as an independent embodiment.

FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102, wherein the network device includes at least one of the following: an access network device and a core network function.

In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, 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, and at least one of a wireless terminal device in a smart home, but is not limited to these.

In some embodiments, the access network device 102 is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved Node B (eNB), a next generation evolved Node B (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, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

In some embodiments, the core network function may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual, It may also be physical. The core network includes, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

In some embodiments, the technical solution of the present disclosure may be applicable to the Open RAN architecture. In this case, the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

In some embodiments, the access network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be called a control unit (control unit). The CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.

It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. A person of ordinary skill in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or part of the subject, but are not limited thereto. The subjects shown in FIG1 are examples, and the communication system may include all or part of the subjects in FIG1 , or may include other subjects other than FIG1 , and the number and form of the subjects are arbitrary, and the subjects may be physical or virtual, and the connection relationship between the subjects is an example, and the subjects may be connected or disconnected, and the connection may be in any manner, and may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.

The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, the fourth generation mobile communication system (4G), the fifth generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access ... The present invention relates to wireless communication systems such as LTE, Wi-Fi (X), 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 (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), systems using other communication methods, and next-generation systems expanded based on them. In addition, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G, etc.) may also be applied.

In some embodiments, the terminal and the network function (also referred to as a core network unit) may communicate via a user plane. For example, taking the network function including a location management function (LMF) as an example, a user plane connection may be established between the terminal and the LMF, and the terminal and the LMF communicate via the user plane, including communicating via a user plane connection. For example, user plane positioning may be implemented by communicating between the terminal and the LMF via the user plane.

In some embodiments, LMF can trigger the processing of the user plane connection, but if the processing of the user plane connection can only be triggered by LMF, the flexibility is low, which is not conducive to the application of the processing of the user plane connection to more scenarios.

FIG2 is an interactive schematic diagram showing a message sending method according to an embodiment of the present disclosure.

As shown in FIG2 , the message sending method includes the following steps:

In step S201, the terminal sends a first message to a first core network function.

In some embodiments, the first core network function receives the first message.

In some embodiments, the first message is used to trigger processing of a user plane connection.

In some embodiments, the processing of the user plane connection includes at least one of: modifying; terminating.

In some embodiments, the first message further includes a reason for processing the user plane connection.

In some embodiments, the first message is sent via at least one of the following means: a user plane; a control plane.

In some embodiments, the first message is sent via a control plane, and the first message is carried in at least one of the following: an uplink non-access layer transmission message; a service request message.

In some embodiments, the first message is sent via a control plane.

In some embodiments, sending the first message to the first core network function includes: sending the first message to the second core network function through the control plane.

In some embodiments, the second core network function is configured to send the first message to the first core network function.

In some embodiments, the first core network function includes a location management function.

In some embodiments, the second core network function includes an access mobility management function.

In some embodiments, sending the first message to the first core network function includes: determining that there is a user plane connection, and sending the first message to the first core network function through the user plane or the control plane.

In some embodiments, sending the first message to the first core network function includes: determining that there is no user plane connection, and sending the first message to the first core network function through a control plane.

In step S202, the first core network function sends a second message to the second core network function.

In some embodiments, the second core network function receives the second message.

In some embodiments, the second message includes a modification indication or a termination indication.

In step S202, the second core network function sends a third message to the third core network function.

In some embodiments, the third message is used to update the packet data unit session, or to release the packet data unit session.

In some embodiments, the second core network function may send a third message to the third core network function when determining to process the user plane connection.

In some embodiments, the third message includes: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

In some embodiments, the third message includes: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release the packet data unit session.

The communication method involved in the embodiments of the present disclosure may include at least one of steps S201 to S203. For example, step S201 may be implemented as an independent embodiment, step S202 may be implemented as an independent embodiment, steps S201+S202 may be implemented as an independent embodiment, steps S201+S203 may be implemented as an independent embodiment, steps S202+S203 may be implemented as an independent embodiment, and steps S201+S202+S203 may be implemented as an independent embodiment, but are not limited thereto.

In some embodiments, steps S201 and S202 may be performed in an interchangeable order or simultaneously.

In some embodiments, steps S201 and S203 may be performed in an interchangeable order or simultaneously.

In some embodiments, steps S202 and S203 may be performed in an interchangeable order or simultaneously.

In some embodiments, steps S201 , S202 , and S203 may be executed in a swapped order or simultaneously.

In some embodiments, reference may be made to other optional implementations recorded before or after the description corresponding to FIG. 2 .

In the first aspect, an embodiment of the present disclosure proposes a message sending method. FIG3 is a schematic flow chart of a message sending method according to an embodiment of the present disclosure. The message sending method shown in this embodiment can be executed by a terminal. As shown in FIG3, the message sending method may include the following steps:

In step S301, a first message is sent to a first core network function, wherein the first message is used to trigger processing of a user plane connection.

It should be noted that the embodiment shown in FIG. 3 may be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific implementation may be selected as needed and the present disclosure is not limited thereto.

According to an embodiment of the present disclosure, a terminal may send a first message to a first core network function in a core network, and trigger processing of a user plane connection through the first message, for example, the first core network function includes LMF. Accordingly, processing of the user plane connection may be triggered by the terminal, so that the processing of the user plane connection is not limited to being triggered by the LMF, thereby improving the flexibility of processing of the user plane connection.

In some embodiments, the processing of the user plane connection includes at least one of: modification; termination.

For example, the terminal may send a first message to the LMF to trigger a user plane connection modification, and the first message may carry a user plane connection modification indication. The LMF may modify the user plane connection according to the first information. For example, the user plane connection modification includes the reselection of the LMF. The LMF may modify the LMF to which the terminal is connected through the user plane connection according to the first information. For example, the user plane connection between the terminal and LMF#1 is modified to a user plane connection between the terminal and LMF#2, where LMF#1 may be referred to as a source LMF and LMF#2 may be referred to as a target LMF. It should be noted that the source LMF and the target LMF may be different LMFs or may be the same LMF.

For example, the terminal may send a first message to the LMF to trigger the termination of the user plane connection, and the first message may carry a user plane connection termination indication. The LMF may terminate the user plane connection according to the first information, for example, the LMF may terminate the user plane connection with the terminal.

In some embodiments, the first message further includes a reason for processing the user plane connection.

For example, the terminal may also carry the reason for processing the user plane connection in the first message sent to the LMF, so that the LMF can determine the reason why the terminal triggers the processing of the user plane connection based on the first message, such as user plane connection congestion.

In some embodiments, the first message is sent via at least one of the following means: a user plane; a control plane.

The terminal sends a first message to the first core network function, which may be sent through the user plane or the control plane.

For example, the terminal sends a first message to the LMF through the user plane. When there is a user plane connection between the terminal and the LMF, the first message can be sent directly to the LMF through the user plane connection.

For example, the terminal sends a first message to the LMF through the control plane. Since the control plane connection exists between the terminal and the AMF (Access and Mobility Management Function), the terminal can first The first message is sent to AMF, and then AMF sends the first message to LMF.

The following uses several embodiments to exemplify how a terminal sends a first message through a user plane and sends a first message through a control plane.

In some embodiments, the first message is sent through the control plane, and sending the first message to the first core network function includes: sending the first message to the second core network function through the control plane, wherein the second core network function is used to send the first message to the first core network function.

In some embodiments, the first core network function includes a location management function (LMF), and/or the second core network function includes an access mobility management function (AMF).

Since the control plane connection exists between the terminal and the second core network function, the terminal can first send the first message to the second core network function, and then the second core network function sends the first message to the first core network function.

For example, the first core network function includes LMF, and the second core network function includes AMF. The terminal can send the first message to AMF, and AMF then sends the first message to LMF.

In some embodiments, the first message is sent through a control plane, and the first message is carried in at least one of the following:

Uplink non-access stratum transmission (UL NAS (Non Access Stratum) TRANSPORT) message;

Service request (SERVICE REQUEST) message.

For example, the terminal sends the first message to the LMF through the control plane, and the terminal may first send the first message to the AMF through the control plane. For example, the terminal may send the first message to the AMF through an uplink non-access layer transmission message. The AMF may send the first message carried by the uplink non-access layer transmission message to the LMF. The first message may be a newly added parameter (parameter) in the uplink non-access layer transmission message, or the first message may be a new type of value in a parameter already existing in the uplink non-access layer transmission message.

For example, the terminal sends the first message to the LMF through the control plane, and the terminal may first send the first message to the AMF through the control plane. For example, the terminal may send the first message to the AMF through a service request message. The AMF may send the first message carried by the service request message to the LMF. The first message may be a newly added parameter in the service request message, or the first message may be a value of a new type in a parameter already existing in the service request message.

It should be noted that, in addition to carrying the first message through the uplink non-access layer transmission message or service request, AMF can also carry the first message through other payload containers (payload container) and send it to LMF.

In some embodiments, sending the first message to the first core network function includes at least one of the following:

Determine that there is a user plane connection, and send a first message to the first core network function through the user plane or the control plane;

Determine that there is no user plane connection, and send a first message to the first core network function through the control plane.

For example, when the terminal needs to send a first message to the LMF, it can first determine whether there is a user plane connection. When the terminal resides in the network, although there may not be a user plane connection between the terminal and the LMF, there is generally a control plane connection between the terminal and the AMF.

Therefore, when the terminal determines that there is no user plane connection, the terminal can send the first message to the LMF through the control plane. For example, the terminal first sends the first message to the AMF through the control plane, and the AMF then sends the first message to the LMF.

When the terminal determines that there is a user plane connection, since there is generally also a control plane connection, the terminal can choose to send the first message to the LMF through the user plane or send the first message to the LMF through the control plane as needed.

In the second aspect, the embodiments of the present disclosure provide a message receiving method. The message sending method shown in this embodiment can be executed by the first core network function. As shown in Figure 4, the message receiving method may include the following steps:

In step S401, a first message sent by a terminal is received, wherein the first message is used to trigger processing of a user plane connection.

According to an embodiment of the present disclosure, a first core network function in a core network may receive a first message sent by a terminal, and trigger processing of a user plane connection according to the first message, for example, the first core network function includes an LMF. Accordingly, processing of a user plane connection may be triggered by the terminal, so that the processing of the user plane connection is not limited to being triggered by the LMF, thereby improving the flexibility of processing of the user plane connection.

In some embodiments, the processing of the user plane connection includes at least one of: modifying; terminating.

For example, the terminal may send a first message to the LMF to trigger a user plane connection modification, and the first message may carry a user plane connection modification indication. The LMF may modify the user plane connection according to the first information. For example, the user plane connection modification includes the reselection of the LMF. The LMF may modify the LMF to which the terminal is connected through the user plane connection according to the first information. For example, the user plane connection between the terminal and LMF#1 is modified to a user plane connection between the terminal and LMF#2, where LMF#1 may be referred to as a source LMF and LMF#2 may be referred to as a target LMF. It should be noted that the source LMF and the target LMF may be different LMFs or may be the same LMF.

For example, the terminal may send a first message to the LMF to trigger the termination of the user plane connection, and the first message may carry a user plane connection termination indication. The LMF may terminate the user plane connection according to the first information, for example, the LMF may terminate the user plane connection with the terminal.

In some embodiments, the first message includes a reason for processing the user plane connection.

For example, the terminal may also carry the reason for processing the user plane connection in the first message sent to the LMF, so that the LMF can determine the reason why the terminal triggers the processing of the user plane connection based on the first message, such as user plane connection congestion.

In some embodiments, the first message is received via at least one of the following: a user plane; a control plane.

The first core network function receives the first message sent, and may receive it through the user plane or the control plane.

For example, LMF receives a first message sent by the terminal through the user plane. When there is a user plane connection between LMF and the terminal, the first message sent by the terminal can be directly received through the user plane connection.

For example, LMF receives the first message sent by the terminal through the user plane. Since the control plane connection exists between the terminal and AMF, the terminal can first send the first message to AMF, and then LMF receives the first message from AMF.

In some embodiments, the first message is received through the control plane, and receiving the first message sent by the terminal includes: receiving the first message received from the terminal and sent by the second core network function.

In some embodiments, the first core network function includes a location management function (LMF), and/or the second core network function includes an access mobility management function (AMF).

Since the control plane connection exists between the terminal and the second core network function, the terminal can first send the first message to the second core network function, and the first core network function then receives the first message from the second core network function.

For example, the first core network function includes LMF, and the second core network function includes AMF. The terminal can send the first message to AMF, and LMF then receives the first message from AMF.

In some embodiments, the first message is received via a control plane, and the first message is carried in at least one of the following: an uplink non-access layer transmission message; a service request message.

For example, the terminal sends a first message to the LMF through the control plane, and the terminal may first send the first message to the AMF through the control plane. The AMF may send the first message carried by the uplink non-access layer transmission message to the LMF. For example, the AMF may carry the first message in the Namf_Communication_N1MessageNotify and send it to the LMF, and the LMF may receive the first message sent by the AMF. Among them, the first message may be a newly added parameter (parameter) in the uplink non-access layer transmission message, or the first message may be a value of a new type in a parameter already existing in the uplink non-access layer transmission message.

For example, the terminal sends the first message to the LMF through the control plane, and the terminal can first send the first message to the AMF through the control plane. The AMF can send the first message carried by the service request message to the LMF. For example, the AMF can carry the first message in Namf_Communication_N1MessageNotify and send it to the LMF, and the LMF can receive the first message sent by the AMF. Among them, the first message can be a newly added parameter in the service request message, or the first message can be a new type of value in a parameter already existing in the service request message.

It should be noted that, in addition to carrying the first message through the uplink non-access layer transmission message or service request, the terminal can also carry the first message through other payload containers (payload container) and send it to the AMF.

In some embodiments, the message receiving method further includes: sending a second message to a second core network function, wherein the second message includes a modification indication or a termination indication.

In the process of triggering the user plane connection processing according to the first message sent by the terminal, LMF can send a location user plane notification (Nlmf_Location_UPNotify) message to AMF.

For example, LMF may carry the second message in Nlmf_Location_UPNotify and send it to AMF. When the first message is used to trigger the modification of the user plane connection, the second message in Nlmf_Location_UPNotify may include a modification indication, and when the first message is used to trigger the termination of the user plane connection, the second message in Nlmf_Location_UPNotify may include a termination indication. Accordingly, AMF can accurately determine whether the processing of the user plane connection is modification or termination according to the second message.

It should be noted that, in addition to the second message, Nlmf_Location_UPNotify may also include other content, such as user plane information, reasons for modification, reasons for termination, etc.

In a third aspect, an embodiment of the present disclosure proposes a message receiving method. FIG5 is a schematic flow chart of a message receiving method according to an embodiment of the present disclosure. The message sending method shown in this embodiment can be executed by a second core network function. As shown in FIG5, the message receiving method can include the following steps:

In step S501, it is determined to process the user plane connection and send a third message to the third core network function, wherein the third message is used to update a packet data unit session (PDU (Packet Data Unit) session) or to release a packet data unit session.

In some embodiments, since the modification of the user plane connection or the termination of the user plane connection will affect the packet data unit session, the second core network function may send a third message to the third core network function when determining that the user plane connection needs to be processed. The third core network function may update the packet data unit session or release the packet data unit session based on the third message, so that the updated or released packet data unit session can adapt to the modified or terminated user plane connection.

In some embodiments, the method further includes: receiving a first message sent by a terminal, wherein the first message is used to trigger processing of a user plane connection; and sending the first message to a first core network function.

In some embodiments, the second core network function in the core network can receive the first message sent by the terminal, for example, receive the first message sent by the terminal through the control plane, and then send the first message to the second core network function, so that the second core network function triggers the user plane connection processing according to the first message. For example, the first core network function includes LMF. Accordingly, the processing of the user plane connection can be triggered by the terminal, so that the processing of the user plane connection is not limited to being triggered by LMF, which improves the flexibility of the user plane connection processing.

For example, the first message may be first sent by the terminal to a first core network function, such as LMF (for example, the terminal sends the first message to LMF through the user plane), and then sent by the first core network function to AMF. After receiving the first message, AMF may determine that the user plane connection needs to be processed, or, after receiving the second message (described in subsequent embodiments), it may determine that the user plane connection needs to be processed. In some embodiments, the processing of the user plane connection includes at least one of the following: modification; termination.

In some embodiments, the second core network function includes an access mobility management function (AMF), and/or the third core network function includes a session management function (Session Management Function, SMF).

In some embodiments, the first message includes a reason for processing the user plane connection.

For example, the first message received by the AMF may also carry the reason for processing the user plane connection, so that the AMF can determine the reason why the terminal triggers the processing of the user plane connection according to the first message, such as user plane connection congestion and other reasons. And the AMF can also send the first message to the LMF, for example, the AMF can carry the first message in Namf_Communication_N1MessageNotify and send it to the LMF, so that the LMF can also determine the reason why the terminal triggers the processing of the user plane connection according to the first message.

In some embodiments, the first message is sent via a control plane, and the first message is carried in at least one of the following sent by the terminal: an uplink non-access layer transmission message; a service request message.

For example, the terminal sends the first message to the LMF through the control plane, and the terminal may first send the first message to the AMF through the control plane. For example, the terminal may send the first message to the AMF through an uplink non-access layer transmission message. The AMF may send the first message carried by the uplink non-access layer transmission message to the LMF. The first message may be a newly added parameter (parameter) in the uplink non-access layer transmission message, or the first message may be a new type of value in a parameter already existing in the uplink non-access layer transmission message.

For example, the terminal sends the first message to the LMF through the control plane, and the terminal may first send the first message to the AMF through the control plane. For example, the terminal may send the first message to the AMF through a service request message. The AMF may send the first message carried by the service request message to the LMF. The first message may be a newly added parameter in the service request message, or the first message may be a value of a new type in a parameter already existing in the service request message.

It should be noted that, in addition to carrying the first message through the uplink non-access layer transmission message or service request, AMF can also carry the first message through other payload containers (payload container) and send it to LMF.

In some embodiments, the message receiving method further comprises: receiving a second message sent by the first core network function, the second message being used by the second core network function to determine to process the user plane connection. In some embodiments, the second message comprises a modification indication or a termination indication.

For example, the first core network function includes a location management function (LMF). When LMF triggers user plane connection processing based on the first message sent by the terminal, it can send a location user plane notification (Nlmf_Location_UPNotify) message to AMF.

For example, LMF may carry the second message in Nlmf_Location_UPNotify and send it to AMF. When the first message is used to trigger the modification of the user plane connection, the second message in Nlmf_Location_UPNotify may include a modification indication, and when the first message is used to trigger the termination of the user plane connection, the second message in Nlmf_Location_UPNotify may include a termination indication. Accordingly, AMF obtains the second message from Nlmf_Location_UPNotify sent by LMF, so that AMF can accurately determine whether the processing of the user plane connection is modification or termination according to the second message.

It should be noted that Nlmf_Location_UPNotify may include other information in addition to the second message. Content, such as user interface information, reason for modification, reason for termination, etc.

In some embodiments, the third message includes: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

When the AMF determines to process the user plane connection, the AMF may send a third message to the SMF, and the SMF may release the packet data unit session or update the packet data unit session according to the third message.

For example, AMF determines to modify the user plane connection based on the first message, and the third message sent to SMF may be Nsmf_PDUSession_Update_SMContext Request. SMF may update the packet data unit session based on the third message, or SMF may release the packet data unit session based on the third message.

In some embodiments, the third message includes: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release the packet data unit session.

When the AMF determines to process the user plane connection, the AMF may send a third message to the SMF, and the SMF may release the packet data unit session or update the packet data unit session according to the third message.

For example, AMF determines to terminate the user plane connection based on the first message, and the third message sent to SMF may be Nsmf_PDUSession_Release_SMContext Request. SMF can release the packet data unit session based on the third message.

In a fourth aspect, an embodiment of the present disclosure proposes a message receiving method. FIG6 is a schematic flow chart of a message receiving method according to an embodiment of the present disclosure. The message sending method shown in this embodiment can be executed by a third core network function. As shown in FIG6, the message receiving method can include the following steps:

In step S601, a third message sent by a second core network function is received, wherein the third message is used to update a packet data unit session or to release a packet data unit session. When the second core network function determines to process a user plane connection, sending the third message is triggered.

In some embodiments, the processing of the user plane connection includes at least one of: modifying; terminating.

In some embodiments, since processing of user plane connections, such as modification or termination, will cause the packet data unit session to be affected, the second core network function in the core network may send a third message to the third core network function when determining that the user plane connection needs to be processed, so that the third core network function can update the packet data unit session according to the third message, or use it to release the packet data unit session. This is beneficial to ensure that the updated or released packet data unit session adapts to the modified or terminated user plane connection.

For example, the second core network function may determine to process the user plane connection according to the first message sent by the terminal. For example, the terminal sends the first message to the second core network function through the control plane. The second core network function may further send the first message to the first core network function.

For example, the second core network function may determine to process the user plane connection according to the second message sent by the first core network function. For example, after receiving the first message, the first core network function may send the second message to the second core network function.

In some embodiments, the second core network function includes an access mobility management function (AMF), and/or the third core network function includes a session management function (SMF).

In some embodiments, the third message includes: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

When the AMF determines to process the user plane connection, the AMF may send a third message to the SMF, and the SMF may release the packet data unit session or update the packet data unit session according to the third message.

For example, AMF determines to modify the user plane connection according to the first message, and the third message sent to SMF can be Nsmf_PDUSession_Update_SMContext Request, SMF can update the packet data unit session according to the third message, or SMF can release the packet data unit session according to the third message.

In some embodiments, the third message includes: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release the packet data unit session.

When the AMF determines to process the user plane connection, the AMF may send a third message to the SMF, and the SMF may release the packet data unit session or update the packet data unit session according to the third message.

For example, AMF determines to terminate the user plane connection based on the first message, and the third message sent to SMF may be Nsmf_PDUSession_Release_SMContext Request. SMF can release the packet data unit session based on the third message.

FIG. 7 is an interactive flow chart showing another message sending method according to an embodiment of the present disclosure.

As shown in 7, the message sending method may include the following steps:

In step S7001, the terminal sends a first message to the LMF (for example, may be referred to as the source LMF), where the first message is used to trigger modification of the user plane connection.

For example, the terminal may send the first message to the source LMF through the user plane; or the terminal may send the first message to the source LMF through the control plane. Wherein, in the case of sending the first message to the source LMF through the control plane, the terminal may first send the first message to the AMF, and then the AMF may send the first message to the source LMF.

In step S7002, the source LMF sends a second message to the AMF, wherein the second message includes a modification indication. For example, the second message may be carried in Nlmf_Location_UPNotify and sent to the AMF. In some embodiments, the second message may also include user plane information, reasons for modification, and other contents.

In step S7003, after receiving the second message sent by the source LMF, the AMF can reselect an LMF (for example, it can be called the target LMF) for user plane positioning. The reselected LMF needs to be able to establish a user plane session, where the user plane session is used for positioning with the terminal.

In step S7004, after the terminal disconnects from the source LMF (eg, user plane connection), the terminal moves the connection (eg, user plane connection) to the reselected LMF. If AMF reallocation has already occurred, it can be skipped.

In step S7005, the AMF sends a message to the source LMF, such as Nlmf_Location_UPConfig Request, which includes a request for the source LMF to terminate a specific user plane connection between the terminal and the source LMF. Optionally, the message may also include reallocation information of the AMF.

In step S7006, if there are periodic and triggered terminal location event reports, the source LMF can call a message to the target LMF, such as Nlmf_Location_LocationContextTransfer Request, to provide the target AMF with the current location context of the terminal.

In step S7007, the target LMF notifies the source LMF of the result of the location context conversion operation.

In step S7008, if the user plane link to the source LMF is still activated, the source LMF may terminate the user plane connection with the terminal. The execution order of step S7008 is not limited to the situation shown in FIG7 , for example, it may also be executed before step S7001, or may be executed between step S7001 and step S7002.

In step S7009, the source LMF may send a message to the AMF, such as Nlmf_Location_UPConfig Response, to confirm the termination of the connection or to confirm the change of the AMF.

In step S7010, after completing the modification of the terminal user plane connection, AMF may send a third message to SMF, for example, the third message includes Nsmf_PDUSession_Update_SMContext Request, and the third message may Includes modification instructions and may also include reasons for the modification.

In step S7011, after receiving the third message, the SMF can execute the update procedure of the PDU Session, or can execute the release procedure (release procedure) of the PDU Session.

It should be noted that the message sending method and the message receiving method shown in the embodiments of the present disclosure may include at least one step from step S7001 to step S7011, and each step from step S7001 to step S7011 may be adjusted or deleted as needed.

FIG8 is an interaction flow chart showing yet another message sending method according to an embodiment of the present disclosure.

In step S8001, the terminal sends a first message to the LMF (for example, may be referred to as the source LMF), where the first message is used to trigger the termination of the user plane connection.

For example, the terminal may send the first message to the source LMF through the user plane; or the terminal may send the first message to the source LMF through the control plane. Wherein, in the case of sending the first message to the source LMF through the control plane, the terminal may first send the first message to the AMF, and then the AMF may send the first message to the source LMF.

In step S8002, the source LMF sends a second message to the AMF, wherein the second message includes a termination indication. For example, the second message may be carried in Nlmf_Location_UPNotify and sent to the AMF. In some embodiments, the second message may also include user plane information, a reason for termination, and the like.

Among them, when AMF receives the second message sent by the source LMF, it determines that LMF needs to be reselected, and can perform operations according to subsequent steps S8003 to S8011; when AMF receives the second message sent by the source LMF, it determines that LMF does not need to be reselected, and can execute subsequent steps S8008, S8010 and S8011, that is, there is no need to execute steps S8003 to S8007 and S8009.

In step S8003, after receiving the second message sent by the source LMF, the AMF can reselect an LMF (for example, it can be called the target LMF) for user plane positioning. The reselected LMF needs to be able to establish a user plane session, where the user plane session is used for positioning with the terminal.

In step S8004, after the terminal disconnects from the source LMF (eg, user plane connection), the terminal moves the connection (eg, user plane connection) to the reselected LMF. If AMF reallocation has already occurred, it can be skipped.

In step S8005, the AMF sends a message to the source LMF, such as Nlmf_Location_UPConfig Request, which includes a request for the source LMF to terminate a specific user plane connection between the terminal and the source LMF. Optionally, the message may also include reallocation information of the AMF.

In step S8006, if there are periodic and triggered terminal location event reports, the source LMF can call a message to the target LMF, such as Nlmf_Location_LocationContextTransfer Request, to provide the target AMF with the current location context of the terminal.

In step S8007, the target LMF notifies the source LMF of the result of the location context conversion operation.

In step S8008, if the user plane link to the source LMF is still activated, the source LMF may terminate the user plane connection with the terminal. The execution order of step S8004 is not limited to the situation shown in FIG8 , for example, it may also be executed before step S8001, or may be executed between step S8001 and step S8002.

In step S8009, the source LMF may send a message to the AMF, such as Nlmf_Location_UPConfig Response, to confirm the termination of the connection or to confirm the change of the AMF.

In step S8010, after completing the termination of the terminal user plane connection, the AMF may send a third message to the SMF, for example, the third message includes Nsmf_PDUSession_Update_SMContext Request or Nsmf_PDUSession_Release_SMContext Request, and the third message may include a termination indication and may also include The reasons for termination shall be included.

In step S8011, after receiving the third message, the SMF can execute the update process of the PDU Session, or can execute the release process of the PDU Session.

It should be noted that the message sending method and the message receiving method shown in the embodiments of the present disclosure may include at least one step from step S8001 to step S8011, and each step from step S8001 to step S8011 may be adjusted or deleted as needed.

In some embodiments, the names of information, etc. are not limited to the names recorded in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "code element", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

In some embodiments, "obtain", "obtain", "get", "receive", "transmit", "bidirectional transmission", "send and/or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high levels, obtaining by self-processing, autonomous implementation, etc.

In some embodiments, terms such as "send", "transmit", "report", "send", "transmit", "bidirectional transmission", "send and/or receive" can be used interchangeably.

Corresponding to the aforementioned embodiments of the message sending method and the message receiving method, the present disclosure also provides embodiments of a terminal and a network function.

An embodiment of the present disclosure further proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the message sending method described in the above-mentioned first aspect and the optional implementation manner of the first aspect.

Fig. 9 is a schematic block diagram of a terminal according to an embodiment of the present disclosure. As shown in Fig. 9 , the terminal includes a sending module 901 .

In some embodiments, the sending module is used to send a first message to the first core network function, wherein the first message is used to trigger processing of the user plane connection.

In some embodiments, the processing of the user plane connection includes at least one of: modifying; terminating.

In some embodiments, the first message further includes a reason for processing the user plane connection.

In some embodiments, the first message is sent via at least one of the following means: a user plane; a control plane.

In some embodiments, the first message is sent via a control plane, and the first message is carried in at least one of the following: an uplink non-access layer transmission message; a service request message.

In some embodiments, the first message is sent through the control plane, and the sending module is used to send the first message to the second core network function through the control plane, wherein the second core network function is used to send the first message to the first core network function.

In some embodiments, the first core network function includes a location management function, and/or the second core network function includes an access mobility management function.

In some embodiments, the sending module is used for at least one of the following: determining that there is a user plane connection, and sending a first message to the first core network function through the user plane or the control plane; determining that there is no user plane connection, and sending the first message to the first core network function through the control plane.

It should be noted that the modules included in the terminal are not limited to the modules shown in FIG. 9 , and may also include other Other modules, such as at least one of a receiving module, a processing module, a display module, etc., are not limited by the present disclosure.

An embodiment of the present disclosure further proposes a core network function, including: one or more processors; wherein the network device is used to execute the message receiving method described in the second aspect and the optional implementation manner of the second aspect.

Fig. 10 is a schematic block diagram showing a core network function according to an embodiment of the present disclosure. As shown in Fig. 10 , the core network function includes a receiving module 1001 .

In some embodiments, the receiving module is used to receive a first message sent by the terminal, wherein the first message is used to trigger processing of the user plane connection.

In some embodiments, the processing of the user plane connection includes at least one of: modifying; terminating.

In some embodiments, the first message includes a reason for processing the user plane connection.

In some embodiments, the first message is received via at least one of the following: a user plane; a control plane.

In some embodiments, the first message is received via a control plane, and the first message is carried in at least one of the following: an uplink non-access layer transmission message; a service request message.

In some embodiments, the first message is received through the control plane, and the receiving module is used to receive the first message received from the terminal and sent by the second core network function.

In some embodiments, the core network function further includes a sending module for sending a second message to a second core network function, wherein the second message includes a modification indication or a termination indication.

In some embodiments, the first core network function includes a location management function, and/or the second core network function includes an access mobility management function.

It should be noted that the modules included in the core network functions may not be limited to the modules shown in Figure 10, but may also include other modules, such as processing modules, etc., which are not limited in the present disclosure.

An embodiment of the present disclosure further proposes a core network function, including: one or more processors; wherein the network device is used to execute the message receiving method described in the third aspect and the optional implementation manner of the third aspect.

FIG11 is a schematic block diagram of a core network function according to an embodiment of the present disclosure. As shown in FIG11 , the core network function includes a processing module 1101 and a sending module 1102 .

In some embodiments, the processing module is used to determine to process the user plane connection, and the sending module is used to send a third message to a third core network function, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

In some embodiments, the processing of the user plane connection includes at least one of: modifying; terminating.

In some embodiments, the first message includes a reason for processing the user plane connection.

In some embodiments, the first message carries the second core network function sent in at least one of the following: an uplink non-access layer transmission message; a service request message.

In some embodiments, the receiving module is further used to receive a second message sent by the first core network function, wherein the second message includes a modification indication or a termination indication.

In some embodiments, the third message includes: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

In some embodiments, the third message includes: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release the packet data unit session.

In some embodiments, the second core network function includes an access mobility management function, and/or the third core network function includes a session management function.

It should be noted that the modules included in the core network functions may not be limited to the modules shown in Figure 11, but may also include other modules, such as processing modules, etc., which are not limited in the present disclosure.

An embodiment of the present disclosure also proposes a core network function, including: one or more processors; wherein the network device is used to execute the message receiving method described in the fourth aspect and the optional implementation manner of the fourth aspect.

FIG12 is a schematic block diagram of a core network function according to an embodiment of the present disclosure. As shown in FIG12 , the core network function includes a receiving module 1201 .

In some embodiments, the receiving module is used to receive a third message sent by the second core network function, wherein the third message is used to update the packet data unit session, or to release the packet data unit session, and when the second core network function determines to process the user plane connection, it triggers the sending of the third message.

In some embodiments, the processing of the user plane connection includes at least one of: modifying; terminating.

In some embodiments, the third message includes: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

In some embodiments, the third message includes: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release the packet data unit session.

In some embodiments, the second core network function includes an access mobility management function, and/or the third core network function includes a session management function.

It should be noted that the modules included in the core network functions may not be limited to the modules shown in Figure 12, but may also include other modules, such as processing modules, etc., which are not limited in the present disclosure.

For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

An embodiment of the present disclosure also proposes a message sending method, which includes: a terminal sends a first message to a first core network function, wherein the first message is used to trigger processing of a user plane connection; the first core network function sends a second message to a second core network function, wherein the second message includes a modification indication or a termination indication; the second core network function sends a third message to a third core network function, wherein the third message is used to update a packet data unit session, or to release a packet data unit session.

An embodiment of the present disclosure also proposes a communication device, comprising: one or more processors; wherein the processor is used to call instructions so that the communication device executes the message sending method described in the first aspect, the optional implementation method of the first aspect, and the message receiving method described in the second aspect, the third aspect, the fourth aspect, the optional implementation method of the second aspect, the optional implementation method of the third aspect, and the optional implementation method of the fourth aspect.

An embodiment of the present disclosure also proposes a communication system, including a terminal and a core network function, wherein the terminal is configured to implement the message sending method described in the first aspect and the optional implementation method of the first aspect, and the core network device is configured to implement the message receiving method described in the second aspect, the third aspect, the fourth aspect, the optional implementation method of the second aspect, the optional implementation method of the third aspect, and the optional implementation method of the fourth aspect.

The embodiment of the present disclosure also provides a storage medium, wherein the storage medium stores instructions. When running on a communication device, the communication device executes the message sending method described in the first aspect and the optional implementation method of the first aspect, and the message receiving method described in the second aspect, the third aspect, the fourth aspect, the optional implementation method of the second aspect, the optional implementation method of the third aspect, and the optional implementation method of the fourth aspect.

The embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device is proposed, the above device includes a unit or module for implementing each step performed by the terminal in any of the above methods. For another example, another device is also proposed, including a unit or module for implementing each step performed by a network device (such as an access network device, a network function node, a core network device, etc.) in any of the above methods.

It should be understood that the division of the units or modules in the above device is only a division of logical functions, which can be fully or partially integrated into one physical entity or physically separated in actual implementation. In addition, the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device. Alternatively, the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be implemented by designing the hardware circuits. The hardware circuits may be understood as one or more processors; for example, in one implementation, the hardware circuits are application-specific integrated circuits (ASICs), and the functions of some or all of the above units or modules may be implemented by designing the logical relationship of the components in the circuits; for another example, in another implementation, the hardware circuits may be implemented by programmable logic devices (PLDs), and Field Programmable Gate Arrays (FPGAs) may be used as an example, which may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured by configuring the configuration files, thereby implementing the functions of some or all of the above units or modules. All units or modules of the above devices may be implemented in the form of software called by the processor, or in the form of hardware circuits, or in the form of software called by the processor, and the remaining part may be implemented in the form of hardware circuits.

In the disclosed embodiments, the processor is a circuit with signal processing capability. In one implementation, the processor may be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the above hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.

FIG13 is a schematic diagram of the structure of a communication device 13100 proposed in an embodiment of the present disclosure. The communication device 13100 may be a network device (e.g., an access network device, a core network device, etc.), or a terminal (e.g., a user device, etc.), or a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. The communication device 13100 may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.

As shown in FIG. 13 , the communication device 13100 includes one or more processors 13101. The processor 13101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and the communication data, and the central processing unit may be used to process the communication device (e.g., the baseband processor). The processor 13101 is used to call instructions so that the communication device 13100 executes any of the above methods.

In some embodiments, the communication device 13100 further includes one or more memories 13102 for storing instructions. Optionally, all or part of the memory 13102 may also be outside the communication device 13100.

In some embodiments, the communication device 13100 further includes one or more transceivers 13103. When the communication device 13100 includes one or more transceivers 13103, the communication steps such as sending and receiving in the above method are executed by the transceiver 13103, and the other steps are executed by the processor 13101.

In some embodiments, the transceiver may include a receiver and a transmitter, and the receiver and the transmitter may be separate or integrated. Optionally, the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, etc. may be replaced with each other, the terms such as transmitter, transmission unit, transmitter, transmission circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.

Optionally, the communication device 13100 further includes one or more interface circuits 13104, which are connected to the memory 13102. The interface circuit 13104 can be used to receive signals from the memory 13102 or other devices, and can be used to send signals to the memory 13102 or other devices. For example, the interface circuit 13104 can read instructions stored in the memory 13102 and send the instructions to the processor 13101.

The communication device 13100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 13100 described in the present disclosure is not limited thereto, and the structure of the communication device 13100 may not be limited by FIG. 13. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

Fig. 14 is a schematic diagram of the structure of a chip 14200 provided in an embodiment of the present disclosure. In the case where the communication device 13100 may be a chip or a chip system, reference may be made to the schematic diagram of the structure of the chip 14200 shown in Fig. 14, but the present disclosure is not limited thereto.

The chip 14200 includes one or more processors 14201, and the processor 14201 is used to call instructions so that the chip 14200 executes any of the above methods.

In some embodiments, the chip 14200 further includes one or more interface circuits 14202, the interface circuits 14202 are connected to the memory 14203, the interface circuits 14202 can be used to receive signals from the memory 14203 or other devices, and the interface circuits 14202 can be used to send signals to the memory

14203 or other devices to send signals. For example, the interface circuit 14202 can read the instructions stored in the memory 14203 and send the instructions to the processor 14201. Optionally, the terms such as interface circuit, interface, transceiver pin, transceiver, etc. can be replaced with each other.

In some embodiments, the chip 14200 further includes one or more memories 14203 for storing instructions. Optionally, all or part of the memory 14203 may be outside the chip 14200.

The present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 13100, the communication device 13100 executes 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 temporary storage medium.

The present disclosure also proposes a program product, which, when executed by the communication device 13100, enables the communication device 13100 to execute any of the above methods. Optionally, the program product is a computer program product.

The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to execute any one of the above methods.

Claims (39)

A message sending method, characterized in that it is executed by a terminal, and the method comprises: A first message is sent to a first core network function, wherein the first message is used to trigger processing of a user plane connection. The method according to claim 1, wherein the processing of the user plane connection comprises at least one of the following: Revise; termination. The method according to claim 1 or 2 is characterized in that the first message also includes a reason for processing the user plane connection. The method according to any one of claims 1 to 3, characterized in that the first message is sent in at least one of the following ways: User plane; Control surface. The method according to claim 4, wherein the first message is sent through a control plane, and the first message is carried in at least one of the following: Uplink non-access layer transmission message; Service request message. The method according to claim 4 or 5, characterized in that the first message is sent through the control plane, and the sending the first message to the first core network function comprises: The first message is sent to a second core network function via a control plane, wherein the second core network function is used to send the first message to the first core network function. The method according to claim 6 is characterized in that the first core network function includes a location management function, and/or the second core network function includes an access mobility management function. The method according to any one of claims 4 to 7, characterized in that the sending the first message to the first core network function comprises at least one of the following: Determine that there is a user plane connection, and send the first message to the first core network function through the user plane or the control plane; Determine that there is no user plane connection, and send the first message to the first core network function through the control plane. A message receiving method, characterized in that it is executed by a first core network function, and the method includes: A first message sent by a receiving terminal is used to trigger processing of a user plane connection. The method according to claim 9, wherein the processing of the user plane connection comprises at least one of the following: Revise; termination. The method according to claim 9 or 10 is characterized in that the first message includes a reason for processing the user plane connection. The method according to any one of claims 9 to 11, wherein the first message is received in at least one of the following ways: User plane; Control surface. The method according to claim 12, wherein the first message is received through a control plane, and the first message is carried in at least one of the following: Uplink non-access layer transmission message; Service request message. The method according to claim 12 or 13, characterized in that the first message is received through a control plane, and the first message sent by the receiving terminal comprises: Receive the first message received from the terminal and sent by the second core network function. The method according to any one of claims 10 to 14, characterized in that the method further comprises: Send a second message to the second core network function, wherein the second message includes a modification indication or a termination indication. The method according to claim 14 or 15 is characterized in that the first core network function includes a location management function, and/or the second core network function includes an access mobility management function. A message receiving method, characterized in that it is performed by a second core network function, and the method includes: Determine to process the user plane connection, and send a third message to the third core network function, wherein the third message is used to update the packet data unit session or to release the packet data unit session. The method according to claim 17, wherein the processing of the user plane connection comprises at least one of the following: Revise; termination. The method according to claim 17 or 18, characterized in that the method further comprises: Receiving a first message sent by a terminal, wherein the first message is used to trigger processing of a user plane connection; Send the first message to the first core network function. The method according to claim 19 is characterized in that the first message includes a reason for processing the user plane connection. The method according to claim 19 or 20, characterized in that the first message is carried in at least one of the following sent by the terminal: Uplink non-access layer transmission message; Service request message. The method according to any one of claims 17 to 21, characterized in that the method further comprises: Receive a second message sent by the first core network function, wherein the second message is used by the second core network function to determine how to process the user plane connection. The method according to claim 22 is characterized in that the second message includes a modification indication or a termination indication. The method according to any one of claims 17 to 23, characterized in that the third message comprises: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session. The method according to any one of claims 17 to 23, characterized in that the third message comprises: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release the packet data unit session. The method according to any one of claims 17 to 25 is characterized in that the second core network function includes an access mobility management function, and/or the third core network function includes a session management function. A message receiving method, characterized in that it is performed by a third core network function, and the method includes: Receive a third message sent by a second core network function, wherein the third message is used to update a packet data unit session or to release a packet data unit session, and when the second core network function determines to process a user plane connection, it triggers sending the third message. The method according to claim 27, wherein the processing of the user plane connection comprises at least one of the following: Revise; termination. The method according to any one of claims 27 to 28, characterized in that the third message comprises: Nsmf_PDUSession_Update_SMContext Request, wherein the third message is used to update a packet data unit session, or to release a packet data unit session. The method according to any one of claims 27 to 28, characterized in that the third message comprises: Nsmf_PDUSession_Release_SMContext Request, wherein the third message is used to release the packet data unit session. The method according to any one of claims 27 to 30 is characterized in that the second core network function includes an access mobility management function, and/or the third core network function includes a session management function. A message sending method, characterized in that the method comprises: The terminal sends a first message to the first core network function, wherein the first message is used to trigger processing of the user plane connection; The first core network function sends a second message to the second core network function, wherein the second message includes a modification indication or a termination indication; The second core network function sends a third message to the third core network function, wherein the third message is used to update the packet data unit session or to release the packet data unit session. A terminal, characterized by comprising: one or more processors; The terminal is used to execute the message sending method according to any one of claims 1 to 8. A core network function, characterized by comprising: one or more processors; Wherein, the network device is used to execute the message receiving method described in any one of claims 9-16. A core network function, characterized by comprising: one or more processors; Wherein, the network device is used to execute the message receiving method described in any one of claims 17-26. A core network function, characterized by comprising: one or more processors; Wherein, the network device is used to execute the message receiving method described in any one of claims 27-31. A communication device, comprising: one or more processors; The processor is used to call instructions so that the communication device executes the message sending method described in any one of claims 1-8 and the message receiving method described in any one of claims 9-16, 17-26, and 27-31. A communication system, characterized in that it includes a terminal and a core network function, wherein the terminal is configured to implement the message sending method described in any one of claims 1-8, and the core network device is configured to implement the message receiving method described in any one of claims 9-16, 17-26, and 27-31. A storage medium storing instructions, characterized in that when the instructions are executed on a communication device, the communication device executes the message sending method described in any one of claims 1 to 8, and the message receiving method described in any one of claims 9 to 16, 17 to 26, and 27 to 31.