Communication method, communication device, communication system and storage medium

Abstract

The present disclosure relates to a communication method, a communication device, a communication system and a storage medium. The communication method comprises: a terminal being capable of receiving, via an access network device, a first message sent by a first core network device, wherein the first message is used for instructing the terminal to establish a protocol data unit (PDU) session related to the first core network device; alternatively, the terminal being capable of receiving, via the access network device, a second message sent by the first core network device, wherein the second message is sent by the first core network device on the basis of terminal information, and the second message is sent by the first core network device to the terminal via a user plane. Thus, the first core network device can communicate with the terminal via the user plane, thereby ensuring the service implementation effect.

Description

Communication methods, communication equipment, communication systems and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system and storage medium. Background Technology

[0002] In communication systems, Network Functions (NFs) and terminals typically interact via Non-Access Stratum (NAS) signaling to support the necessary controls for mobility and session management, as well as the security protection of communication services. In future communication networks, if new services requiring the transmission of large amounts of data (such as sensing and federated learning) are to be implemented, communication between the terminal and the Network Function (NF) will need to occur at the user plane, data plane, or service plane. Summary of the Invention

[0003] This disclosure provides a communication method, communication device, communication system, and storage medium.

[0004] The first aspect of this disclosure provides a communication method executed by a terminal, comprising: receiving a first message sent by a first core network device through an access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

[0005] A second aspect of this disclosure provides a communication method executed by a first core network device, comprising: sending a first message to a terminal via an access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

[0006] A third aspect of this disclosure provides a communication method executed by a fourth core network device, comprising: establishing a mapping relationship between a data network name (DNN) and a first function, wherein the first function is used to establish a protocol data unit (PDU) session between a terminal and the first core network device.

[0007] A fourth aspect of this disclosure provides a communication method executed by a first core network device, comprising: acquiring terminal information; and sending a second message to the terminal via an access network device based on the terminal information, wherein the second message is sent by the first core network device to the terminal through a user.

[0008] A fifth aspect of this disclosure provides a communication method executed by a third core network device, comprising: sending communication information of a fourth core network device to a first core network device, wherein the communication information is used by the first core network device to obtain or subscribe to terminal information from the fourth core network device, and the terminal information is used by the first core network device to send a second message to a terminal, the second message being sent by the first core network device to the terminal through a user; or, sending or notifying the first core network device of terminal information.

[0009] A sixth aspect embodiment of this disclosure provides a communication method performed by a fourth core network device, comprising: sending or notifying a terminal information to a first core network device, wherein the terminal information is used by the first core network device to send a second message to the terminal, the second message being sent by the first core network device to the terminal through a user.

[0010] A seventh aspect embodiment of this disclosure provides a communication method executed by a terminal, comprising: receiving a second message sent by a first core network device through an access network device, wherein the second message is sent by the first core network device through terminal information, and the second message is sent by the first core network device to the terminal through a user.

[0011] An eighth aspect embodiment of this disclosure provides a terminal, the terminal comprising: a transceiver module configured to receive a first message sent by a first core network device via an access network device, wherein the first message is configured to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device; or a transceiver module configured to receive a second message sent by the first core network device via an access network device, wherein the second message is sent by the first core network device through terminal information, and the second message is sent by the first core network device to the terminal via a user.

[0012] A ninth aspect embodiment of this disclosure provides a first core network device, comprising: a transceiver module for sending a first message to a terminal via an access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device; or a transceiver module for acquiring terminal information and, based on the terminal information, sending a second message to the terminal via the access network device, wherein the second message is sent by the first core network device to the terminal through the user.

[0013] A tenth aspect embodiment of this disclosure proposes a third core network device, comprising: a transceiver module, configured to send communication information of a fourth core network device to a first core network device, wherein the communication information is used by the first core network device to obtain or subscribe to terminal information from the fourth core network device, and the terminal information is used by the first core network device to send a second message to a terminal, the second message being sent by the first core network device to the terminal through a user; or to send or notify the first core network device of terminal information.

[0014] The eleventh aspect of this disclosure proposes a fourth core network device, which includes: a processing module for establishing a mapping relationship between a data network name (DNN) and a first function, wherein the first function is used to establish a protocol data unit (PDU) session between a terminal and the first core network device; or includes: a transceiver module for sending or notifying terminal information to the first core network device, wherein the terminal information is used by the first core network device to send a second message to the terminal, and the second message is sent by the first core network device to the terminal through the user.

[0015] The twelfth aspect of this disclosure provides a communication device comprising: one or more processors; wherein the processors are configured to perform the method as described in the first aspect above, or the method as described in the second aspect above, or the method as described in the third aspect above, or the method as described in the fourth aspect above, or the method as described in the fifth aspect above, or the method as described in the sixth aspect above, or the method as described in the seventh aspect above.

[0016] The thirteenth aspect of this disclosure provides a communication system including a terminal, a first core network device, a third core network device, and a fourth core network device. The terminal is configured to perform the method as described in the first aspect above, or the method as described in the seventh aspect above. The first core network device is configured to perform the method as described in the second aspect above, or the method as described in the fourth aspect above. The third core network device is configured to perform the method as described in the fifth aspect above. The fourth core network device is configured to perform the method as described in the third aspect above, or the method as described in the sixth aspect above.

[0017] The fourteenth aspect of this disclosure provides a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in the first aspect above, or the method as described in the second aspect above, or the method as described in the third aspect above, or the method as described in the fourth aspect above, or the method as described in the fifth aspect above, or the method as described in the sixth aspect above, or the method as described in the seventh aspect above.

[0018] The fifteenth aspect of this disclosure provides a computer program product including a computer program that, when executed by a processor, implements the method as described in the first aspect above, or the method as described in the second aspect above, or the method as described in the third aspect above, or the method as described in the fourth aspect above, or the method as described in the fifth aspect above, or the method as described in the sixth aspect above, or the method as described in the seventh aspect above.

[0019] In the solutions proposed in this disclosure, in the above embodiments, the terminal can receive a first message sent by the first core network device through the access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device; or the terminal can receive a second message sent by the first core network device through the access network device, wherein the second message is sent by the first core network device through terminal information, and the second message is sent by the first core network device through the user plane to the terminal. Thus, the first core network device can communicate with the terminal through the user plane, thereby ensuring the effective implementation of services. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0021] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0022] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

[0023] Figure 2B is an interactive schematic diagram of a communication method according to another embodiment of the present disclosure;

[0024] Figure 3A is an interactive schematic diagram of a communication method according to yet another embodiment of the present disclosure;

[0025] Figure 3B is an interactive schematic diagram of a communication method according to yet another embodiment of the present disclosure;

[0026] Figure 4A is an interactive schematic diagram of a communication method according to another embodiment of the present disclosure;

[0027] Figure 4B is an interactive schematic diagram of a communication method according to another embodiment of the present disclosure;

[0028] Figure 5 is an interactive schematic diagram of a communication method according to yet another embodiment of the present disclosure;

[0029] Figure 6A is an interactive schematic diagram of a communication method according to another embodiment of the present disclosure;

[0030] Figure 6B is an interactive schematic diagram of a communication method according to yet another embodiment of the present disclosure;

[0031] Figure 7A is a schematic diagram of an application in an embodiment of this disclosure;

[0032] Figure 7B is a schematic diagram of another application in an embodiment of this disclosure;

[0033] Figure 7C is a schematic diagram of another application in an embodiment of this disclosure;

[0034] Figure 7D is a schematic diagram of another application in an embodiment of this disclosure;

[0035] Figure 7E is a schematic diagram of another application in an embodiment of this disclosure;

[0036] Figure 8 is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;

[0037] Figure 9A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;

[0038] Figure 9B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0039] This disclosure provides communication methods, communication devices, communication systems, and storage media.

[0040] In a first aspect, embodiments of this disclosure propose a communication method, which is executed by a terminal, including: receiving a first message sent by a first core network device through an access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

[0041] In the above embodiments, the terminal can receive a first message sent by the first core network device through the access network device. The first message instructs the terminal to establish a Protocol Data Unit (PDU) session with the first core network device. Thus, the first core network device can communicate with the terminal through the user plane, thereby ensuring the effective implementation of services.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0043] Establish a PDU session based on the first message.

[0044] In the above embodiments, the terminal can establish a PDU session based on the first message, thereby realizing the timely and effective establishment of the PDU session, enabling the first core network device and the terminal to communicate correctly through the PDU session.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes at least one of the following:

[0046] Equipment information for the first core network equipment;

[0047] First indication information, wherein the first indication information is used to indicate the establishment of a PDU session;

[0048] Data network name: DNN;

[0049] Protocol type.

[0050] In the above embodiments, it is possible to effectively trigger the terminal to establish a PDU session and ensure that the PDU session can be established correctly to support communication between the first core network device and the terminal based on the PDU session.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the device information of the first core network device includes at least one of the following:

[0052] Types of equipment in the first core network;

[0053] The Internet Protocol (IP) address of the first core network device;

[0054] The fully qualified domain name (FQDN) of the first core network equipment;

[0055] The port number of the first core network device.

[0056] In the above embodiments, the terminal is able to correctly and comprehensively learn about the status of the first core network device with which it needs to establish a PDU session, thus supporting the correct establishment of the PDU session.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, establishing a PDU session based on the first message includes:

[0058] The access network device sends a third message to the second core network device, wherein the third message is used to request the second core network device to establish a PDU session related to the terminal and the first core network device.

[0059] In the above embodiments, it is possible to effectively request the second core network device to establish a PDU session, thereby effectively ensuring that the PDU session can be established in a timely manner to support communication between the first core network device and the terminal based on the PDU session.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0061] Based on the first message, determine the port information of the first core network device.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, the third message includes at least one of the following:

[0063] Port information of the first core network equipment;

[0064] DNN;

[0065] Request type;

[0066] The request information is used to request the second core network device to establish a PDU session between the terminal and the first core network device.

[0067] In the above embodiments, the third message may further include at least one of the following: port information of the first core network device, DNN (the DNN can be used to establish a PDU session for communication between the terminal and the first core network device via the user plane), request type, and request information, wherein the request information is used to request the second core network device to establish a PDU session related to the terminal and the first core network device. This effectively improves the accuracy and timeliness of PDU session establishment, enhances the performance of PDU session-based communication between the first core network device and the terminal, and greatly improves service implementation.

[0068] Secondly, embodiments of this disclosure propose a communication method executed by a first core network device, comprising: sending a first message to a terminal via an access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

[0069] In the above embodiments, the first core network device can send a first message to the terminal through the access network device, instructing the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device based on the first message. This enables the first core network device to effectively communicate with the terminal through the user plane, thereby ensuring the effective implementation of services.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, sending a first message to the terminal via an access network device includes:

[0071] If terminal information is not obtained, the first message is sent to the terminal through the access network equipment.

[0072] In the above embodiments, the first core network device can send a first message to the terminal without obtaining terminal information, thereby triggering the establishment of a Protocol Data Unit (PDU) session. The established PDU session can then be used for communication between the terminal and the first core network device via the user plane, ensuring that the terminal can correctly communicate with the first core network device and effectively adapting to personalized service scenarios, thus improving the flexibility of communication applications.

[0073] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes at least one of the following:

[0074] Equipment information for the first core network equipment;

[0075] First indication information, wherein the first indication information is used to indicate the establishment of a PDU session;

[0076] Data network name: DNN;

[0077] Protocol type.

[0078] In conjunction with some embodiments of the second aspect, in some embodiments, the device information of the first core network device includes at least one of the following:

[0079] Types of equipment in the first core network;

[0080] The Internet Protocol (IP) address of the first core network device;

[0081] The fully qualified domain name (FQDN) of the first core network equipment;

[0082] The port number of the first core network device.

[0083] Thirdly, embodiments of this disclosure propose a communication method executed by a fourth core network device, comprising: establishing a mapping relationship between a data network name (DNN) and a first function, wherein the first function is used to establish a protocol data unit (PDU) session between a terminal and a first core network device.

[0084] In the above embodiments, the fourth core network device can maintain the mapping relationship between the DNN and the first function. Therefore, when a PDU session is established with the assistance of the DNN, the correct establishment of the PDU session can be ensured, thereby greatly improving the communication performance between the terminal and the first core network device based on the PDU session.

[0085] In conjunction with some embodiments of the third aspect, in some embodiments, the user plane security policy of the PDU session is configured to at least one of the following:

[0086] Integrity protection;

[0087] Encryption protection.

[0088] In the above embodiments, the user plane security policy for PDU sessions is configured as at least one of the following: integrity protection; encryption protection. This improves both the security and accuracy of PDU-based session communication.

[0089] Fourthly, this disclosure provides a communication method, which is executed by a first core network device, including: acquiring terminal information; and sending a second message to the terminal through an access network device based on the terminal information, wherein the second message is sent by the first core network device to the terminal through the user.

[0090] In the above embodiments, the first core network device can obtain terminal information and, based on the terminal information, send a second message to the terminal through the access network device. The second message is sent by the first core network device to the terminal via the user plane. Therefore, having already obtained the terminal information, the first core network device can directly send the second message to the terminal, enabling communication between the terminal and the first core network device via the user plane. This ensures that the terminal can correctly communicate with the first core network device and is effectively applicable to personalized service scenarios, improving the flexibility of communication applications.

[0091] In conjunction with some embodiments of the fourth aspect, in some embodiments, obtaining terminal information includes:

[0092] Obtain or subscribe to terminal information from the fourth core network equipment.

[0093] In the above embodiments, the first core network device can effectively and timely obtain or subscribe to terminal information from the fourth core network device, thereby supporting the improvement of the efficiency and performance of communication between the terminal and the first core network device through the user plane.

[0094] In conjunction with some embodiments of the fourth aspect, in some embodiments, obtaining or subscribing to terminal information from the fourth core network device includes:

[0095] Send a fourth message to the third core network device, wherein the fourth message is used to request to obtain the communication information of the fourth core network device, and the third core network device stores the communication information of the fourth core network device;

[0096] Receive communication information sent by third core network devices;

[0097] Based on communication information, obtain or subscribe to terminal information from the fourth core network equipment.

[0098] In conjunction with some embodiments of the fourth aspect, in some embodiments, obtaining or subscribing to terminal information from the fourth core network device based on communication information includes:

[0099] Based on the communication information, a fifth message is sent to the fourth core network device, wherein the fifth message is used to request to obtain or subscribe to terminal information from the fourth core network device;

[0100] Receive terminal information sent or notified by the fourth core network device.

[0101] In the above embodiments, terminal information can be obtained in a timely and effective manner, thereby enabling the first core network device to communicate with the terminal through the user plane based on the terminal information, ensuring the effectiveness of service implementation.

[0102] In conjunction with some embodiments of the fourth aspect, in some embodiments, the communication information includes at least one of the following:

[0103] Equipment identification for the fourth core network equipment;

[0104] The Internet Protocol (IP) address of the fourth core network device;

[0105] The fully qualified domain name (FQDN) of the fourth core network device.

[0106] In the above embodiments, the first core network device and the fourth core network device are supported to communicate correctly and effectively, so that the first core network device can obtain terminal information in a timely and effective manner.

[0107] In conjunction with some embodiments of the fourth aspect, in some embodiments, obtaining terminal information includes:

[0108] Send a sixth message to the third core network device or the fifth core network device, wherein the sixth message is used to request to obtain or subscribe to terminal information from the third core network device or the fifth core network device;

[0109] Receive terminal information sent or notified by the third core network device or the fifth core network device.

[0110] In the above embodiments, the flexibility of terminal information acquisition can be improved, and it can be applied to personalized core network architectures to ensure that the first core network device can obtain the correct terminal information so as to support the first core network device and the terminal to communicate through the user plane.

[0111] In conjunction with some embodiments of the fourth aspect, in some embodiments, the fourth message, or the fifth message, or the sixth message includes at least one of the following:

[0112] :

[0113] Terminal identification information;

[0114] Data network name: DNN;

[0115] Single network slice selection auxiliary information S-NSSAI.

[0116] In the above embodiments, ensuring that the correct terminal information can be obtained greatly improves the communication effect between the first core network device and the terminal through the user plane.

[0117] In conjunction with some embodiments of the fourth aspect, in some embodiments, the terminal information includes at least one of the following:

[0118] The terminal's IP address;

[0119] Terminal port information.

[0120] In the above embodiments, the content contained in the terminal information can be flexibly determined, which greatly improves the flexibility of communication while ensuring the correctness of communication.

[0121] Fifthly, this disclosure provides a communication method performed by a third core network device, comprising: sending communication information of a fourth core network device to a first core network device, wherein the communication information is used by the first core network device to obtain or subscribe to terminal information from the fourth core network device, and the terminal information is used by the first core network device to send a second message to a terminal, the second message being sent by the first core network device to the terminal through a user; or, sending or notifying the first core network device of terminal information.

[0122] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes:

[0123] Receive a fourth message sent by the first core network device, wherein the fourth message is used to request to obtain the communication information of the fourth core network device stored by the third core network device.

[0124] In conjunction with some embodiments of the fifth aspect, in some embodiments, the communication information includes at least one of the following:

[0125] Equipment identification for the fourth core network equipment;

[0126] The Internet Protocol (IP) address of the fourth core network device;

[0127] The fully qualified domain name (FQDN) of the fourth core network device.

[0128] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes:

[0129] Receive the sixth message sent by the first core network device, wherein the sixth message is used to request to obtain or subscribe to terminal information from the third core network device.

[0130] In conjunction with some embodiments of the fifth aspect, in some embodiments, the fourth or sixth message includes at least one of the following:

[0131] Terminal identification information;

[0132] Data network name: DNN;

[0133] Single network slice selection auxiliary information S-NSSAI.

[0134] In conjunction with some embodiments of the fifth aspect, in some embodiments, the terminal information includes at least one of the following:

[0135] The terminal's IP address;

[0136] Terminal port information.

[0137] In a sixth aspect, embodiments of this disclosure propose a communication method executed by a fourth core network device, comprising: sending or notifying a terminal information to a first core network device, wherein the terminal information is used by the first core network device to send a second message to the terminal, the second message being sent by the first core network device to the terminal through a user.

[0138] In the above embodiments, the fourth core network device can send or notify the first core network device of terminal information to ensure that the first core network device can obtain the terminal information in a timely and effective manner so as to communicate with the terminal based on the terminal information.

[0139] In conjunction with some embodiments of the sixth aspect, in some embodiments the method further includes:

[0140] Receive the fifth message sent by the first core network device, wherein the fifth message is used to request to obtain or subscribe to terminal information from the fourth core network device.

[0141] In conjunction with some embodiments of the sixth aspect, in some embodiments, the fifth message includes at least one of the following:

[0142] Terminal identification information;

[0143] Data network name: DNN;

[0144] Single network slice selection auxiliary information S-NSSAI.

[0145] In conjunction with some embodiments of the sixth aspect, in some embodiments, the terminal information includes at least one of the following:

[0146] The terminal's IP address;

[0147] Terminal port information.

[0148] In a seventh aspect, embodiments of this disclosure propose a communication method executed by a terminal, comprising: receiving a second message sent by a first core network device through an access network device, wherein the second message is sent by the first core network device through terminal information, and the second message is sent by the first core network device to the terminal through a user.

[0149] In the above embodiments, the terminal can receive a second message sent by the first core network device through the access network device. The second message is sent by the first core network device through terminal information. Therefore, the first core network device can communicate with the terminal through the user plane based on the terminal information, thereby ensuring the effective implementation of services.

[0150] In conjunction with some embodiments of the seventh aspect, in some embodiments, the terminal information includes at least one of the following:

[0151] The terminal's Internet Protocol (IP) address;

[0152] Terminal port information.

[0153] Eighthly, embodiments of this disclosure provide a terminal, the terminal comprising: a transceiver module, configured to receive a first message sent by a first core network device through an access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device; or a transceiver module, configured to receive a second message sent by the first core network device through an access network device, wherein the second message is sent by the first core network device through terminal information, and the second message is sent by the first core network device to the terminal through a user.

[0154] In a ninth aspect, embodiments of this disclosure provide a first core network device, comprising: a transceiver module, configured to send a first message to a terminal via an access network device, wherein the first message is configured to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device; or a transceiver module, configured to acquire terminal information and, based on the terminal information, send a second message to the terminal via the access network device, wherein the second message is sent by the first core network device to the terminal via a user.

[0155] In a tenth aspect, embodiments of this disclosure propose a third core network device, comprising: a transceiver module, configured to send communication information of a fourth core network device to a first core network device, wherein the communication information is used by the first core network device to obtain or subscribe to terminal information from the fourth core network device, and the terminal information is used by the first core network device to send a second message to a terminal, the second message being sent by the first core network device to the terminal through a user; or to send or notify the first core network device of terminal information.

[0156] Eleventhly, embodiments of this disclosure propose a fourth core network device, which includes: a processing module for establishing a mapping relationship between a data network name (DNN) and a first function, wherein the first function is used to establish a protocol data unit (PDU) session between a terminal and the first core network device; or includes: a transceiver module for sending or notifying terminal information to the first core network device, wherein the terminal information is used by the first core network device to send a second message to the terminal, and the second message is sent by the first core network device to the terminal through the user.

[0157] In a twelfth aspect, embodiments of this disclosure provide a communication device, the communication device comprising: one or more processors; wherein the communication device is configured to execute the first aspect and optional implementations thereof, or to execute the second aspect and optional implementations thereof, or to execute the third aspect and optional implementations thereof, or to execute the fourth aspect and optional implementations thereof, or to execute the fifth aspect and optional implementations thereof, or to execute the sixth aspect and optional implementations thereof, or to execute the seventh aspect and optional implementations thereof.

[0158] In a thirteenth aspect, embodiments of this disclosure provide a communication system comprising: a terminal, a first core network device, a third core network device, and a fourth core network device; wherein the terminal is configured to perform the method described in the first aspect and its optional implementations, or to perform the method described in the seventh aspect and its optional implementations; the first core network device is configured to perform the method described in the second aspect and its optional implementations, or to perform the method described in the fourth aspect and its optional implementations; the third core network device is configured to perform the method described in the fifth aspect and its optional implementations; and the fourth core network device is configured to perform the method described in the third aspect and its optional implementations, or to perform the method described in the sixth aspect and its optional implementations.

[0159] In a fourteenth aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementations, or to perform the method described in the second aspect and its optional implementations, or to perform the method described in the third aspect and its optional implementations, or to perform the method described in the fourth aspect and its optional implementations, or to perform the fifth aspect and its optional implementations, or to perform the sixth aspect and its optional implementations, or to perform the seventh aspect and its optional implementations.

[0160] In a fifteenth aspect, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, causes the processor to perform the method described in the first aspect and its optional implementations, or to perform the method described in the second aspect and its optional implementations, or to perform the method described in the third aspect and its optional implementations, or to perform the method described in the fourth aspect and its optional implementations, or to perform the fifth aspect and its optional implementations, or to perform the sixth aspect and its optional implementations, or to perform the seventh aspect and its optional implementations.

[0161] In a sixteenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the method as described in the first aspect and optional implementations of the first aspect, or to perform the method as described in the second aspect and optional implementations of the second aspect, or to perform the method as described in the third aspect and optional implementations of the third aspect, or to perform the method as described in the fourth aspect and optional implementations of the fourth aspect, or to perform the fifth aspect and optional implementations of the fifth aspect, or to perform the sixth aspect and optional implementations of the sixth aspect, or to perform the seventh aspect and optional implementations of the seventh aspect.

[0162] In a seventeenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the method described according to the first aspect and optional implementations thereof, or configured to perform the method described according to the second aspect and optional implementations thereof, or configured to perform the method described according to the third aspect and optional implementations thereof, or configured to perform the method described according to the fourth aspect and optional implementations thereof, or configured to perform the method described according to the fifth and sixth aspects and optional implementations thereof, or configured to perform the method described according to the seventh aspect and optional implementations thereof, or configured to perform the method described according to the eighth aspect and optional implementations thereof.

[0163] It is understood that the aforementioned terminals, core network equipment, communication equipment, communication systems, storage media, computer program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0164] This disclosure provides a communication method, a communication device, a communication system, and a storage medium. In some embodiments, the terms "communication method" and "information processing method," "communication control method," etc., can be used interchangeably; the terms "communication method apparatus" and "information processing apparatus," "communication control apparatus," etc., can be used interchangeably; and the terms "transmission system" and "information processing system," "communication system," etc., can be used interchangeably.

[0165] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0166] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0167] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0168] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the aforementioned," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0169] In the embodiments disclosed herein, "multiple" refers to two or more.

[0170] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0171] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless 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). The same applies when there are more branches such as A, B, C, etc.

[0172] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0173] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0174] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0175] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0176] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0177] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network function", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "body", etc.

[0178] In some embodiments, "network" can be interpreted as devices included in the network, such as access network devices, core network devices, etc.

[0179] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)," "base station (BS)," "radio base station," or "fixed station." In some embodiments, it may also be understood as "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," or "bandwidth part (BWP)."

[0180] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "Narrow Band-Internet of Things (NB-IoT) device," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "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," etc.

[0181] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0182] 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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0183] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0185] Figure 1 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 may include a terminal 101, a core network device 102, and an access network device 103.

[0186] In some embodiments, terminal 101 may include, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0187] In some embodiments, the core network device 102 may be a single device including a first network function 1021, a second network function 1022, a third network function 1023, a fourth network function 1024, a fifth network function 1025, a sixth network function 1026, etc., or it may be multiple devices or a group of devices, each including all or some of the first network function 1021, the second network function 1022, the third network function 1023, the fourth network function 1024, the fifth network function 1025, and the sixth network function 1026. Network functions may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), the 5G Core Network (5GCN), and the Next Generation Core (NGC).

[0188] In some embodiments, the first network function 1021 is, for example, a Session Management Function (SMF), but the name is not limited thereto.

[0189] In some embodiments, the first network function 1021 is used to provide session management functions.

[0190] In some embodiments, the second network function 1022 is, for example, a Network Exposure Function (NEF), but the name is not limited thereto.

[0191] In some embodiments, the second network function 1022 is used to provide network openness functionality.

[0192] In some embodiments, the third network function 1023 is, for example, an Access and Mobility Management Function (AMF), though the name is not limited thereto.

[0193] In some embodiments, the third network function 1023 is used to provide access and mobility management functions.

[0194] In some embodiments, the fourth network function 1024 is, for example, a unified data management function (UDM), but the name is not limited thereto.

[0195] In some embodiments, the fourth network function 1024 is used to provide unified data management functions.

[0196] In some embodiments, the fifth network function 1025 is, for example, a policy control function (PCF), but the name is not limited thereto.

[0197] In some embodiments, the fifth network function 1025 is used to provide policy control functions.

[0198] In some embodiments, the sixth network function 1026 is, for example, a User Plane Function (UPF), but the name is not limited thereto.

[0199] In some embodiments, the sixth network function 1026 is used to provide user plane functionality.

[0200] In some embodiments, the third network function 1023 and the sixth network function 1026 may or may not be connected.

[0201] In some embodiments, the AMF and UPF may or may not be connected.

[0202] In some embodiments, the terminal 101 and the core network device 102 can be connected via the access network device 103. Optionally, the access network device 103 may be, for example, a node or device that connects the terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0203] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0204] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0205] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0206] To facilitate understanding, the terminology used in this disclosure will be introduced first.

[0207] 1. Access and mobility management function (AMF).

[0208] The Access Management Function (AMF) is a logical node function on the core network side. It serves as the core network control plane access point for terminals and radio devices. It receives all connection and session-related information from user equipment and performs registration, connection, reachability, and mobility management. Furthermore, the AMF provides a session management message transmission channel for terminal devices and session management function (SMF) devices, providing authentication and authorization functions for user access.

[0209] 2. Location Management Function (LMF).

[0210] The Location Management Function (LMF) is located on the local side of the radio access network (RAN) or the core network (CN) and is used to provide location management function services to the UE.

[0211] 3. Application Function (AF): Similar to an application server, it can interact with other core network control plane network functions (NFs) and provide service. AFs can exist for different application services and can be owned by operators or trusted third parties.

[0212] 4. Network Exposure Function (NEF): Located between the core network and external third-party application functionalities (and possibly some internal AFs), the NEF is responsible for managing all external applications that expose network data. The NEF provides corresponding security guarantees to ensure the security of external applications accessing the 3GPP network, and offers functions such as customizable Quality of Service (QoS) capabilities, mobility state event subscription, and AF request distribution.

[0213] 5. User plane function (UPF) includes routing and forwarding user data packets, data interaction with external data networks, QoS processing of the user plane, and implementation of flow control rules (such as gating, redirection, and traffic redirection).

[0214] 6. Unified data management (UDM) function.

[0215] UDM is responsible for the management of terminal device identification, subscription data, authentication data, and service registration management of terminal devices (such as the AMF currently providing services to the terminal device; if the terminal device switches to a different AMF, UDM will also send a deregistration message to the old AMF, requesting the old AMF to delete the user's relevant information).

[0216] 7. Policy control function (PCF): Supports a unified policy framework to manage network behavior, provides policy rules for network entities to implement, and accesses subscription information from a unified data warehouse.

[0217] 8. Unified Data Repository (UDR) function, used for UDM to store or read subscription data and PCF to store or read policy data.

[0218] 9. Radio Access Network (RAN): Used to control users' access to the mobile communication network wirelessly.

[0219] 10. Session Management Function (SMF): Used in conjunction with AMF to support customized mobility management solutions and to manage user sessions.

[0220] 11. Binding Support Function (BSF): This function is used when multiple PCFs are deployed in the network. The network function can find the corresponding PCF through the BSF service and by combining information such as user identifier and data network name.

[0221] 12. The Network Repository Function (NRF) provides support for NF service management, including registration, deregistration, authorization, and discovery.

[0222] 13. Short Message Service-Service Centre (SMS-SC): Its main functions include storing and forwarding short messages, processing status reports, and connecting to multiple Public Land Mobile Networks (PLMNs).

[0223] 14. Data Network (DN) refers to operator services, Internet access, or third-party services.

[0224] Optionally, in a communication system, Network Functions (NFs) and terminals typically interact via Non-Access Stratum (NAS) signaling to support the necessary controls for mobility and session management, as well as the security protection of communication services. In future communication networks, if new services requiring the transmission of large amounts of data (such as sensing and federated learning) are to be implemented, communication between the terminal and the Network Function (NF) will need to occur at the user plane, data plane, or service plane.

[0225] Optionally, to enable the terminal to support new services, it is necessary for the terminal and network functions to communicate through the user plane, thereby enabling services with high data transmission requirements to be implemented using the user plane. However, related technologies do not support communication between the terminal and network functions through the user plane, resulting in poor service implementation performance.

[0226] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiments of the present disclosure relate to a communication method, which can be used in a communication system 100, and is not limited thereto. Optionally, in this embodiment, an example is taken where the first core network device can obtain terminal information, wherein the terminal information can support communication between the first core network device and the terminal through the user plane, and is not limited thereto. The above method includes:

[0227] Step S2101: The first core network device obtains terminal information.

[0228] Optionally, in some embodiments, the first core network device may be, for example, an NF.

[0229] Optionally, in some embodiments, the NF can obtain terminal information.

[0230] Optionally, in some embodiments, terminal information may enable the NF and the terminal to communicate through the user plane.

[0231] Optionally, in some embodiments, the terminal information may be, for example, the terminal's Internet Protocol (IP) address and / or port information.

[0232] Optionally, in some embodiments, the NF can obtain the terminal's IP address. Alternatively, the NF can obtain the terminal's port information. Or, the NF can obtain both the terminal's IP address and port information; there is no limitation on this.

[0233] Optionally, in some embodiments, the first core network device may obtain or subscribe to terminal information from a third core network device, a fourth core network device, or a fifth core network device. The third core network device may be, for example, a UDM, the fourth core network device may be, for example, an SMF, and the fifth core network device may be, for example, a NEF or a BSF; there are no restrictions on this.

[0234] Optionally, in some embodiments, the first core network device may obtain or subscribe to terminal information from the third core network device.

[0235] Optionally, in some embodiments, the NF can obtain or subscribe to terminal information from the UDM.

[0236] Optionally, in some embodiments, the first core network device may obtain or subscribe to terminal information from the fourth core network device.

[0237] Optionally, in some embodiments, the NF can obtain or subscribe to terminal information from the SMF.

[0238] Optionally, in some embodiments, the first core network device may send a fourth message to the third core network device, wherein the fourth message is used to request to obtain the communication information of the fourth core network device, the third core network device stores the communication information of the fourth core network device, and receives the communication information sent by the third core network device, and obtains or subscribes to terminal information from the fourth core network device according to the communication information.

[0239] Optionally, in some embodiments, the first core network device can send a fifth message to the fourth core network device based on communication information. This fifth message is used to request to obtain or subscribe to terminal information from the fourth core network device, and to receive terminal information sent or notified by the fourth core network device. This enables timely and effective acquisition of terminal information, allowing the first core network device to communicate with the terminal via the user plane based on the terminal information, ensuring effective service delivery.

[0240] Optionally, in some embodiments, the third core network device can determine the communication information of the fourth core network device. Then, upon receiving a fourth message from the first core network device, the third core network device can determine, based on the fourth message, that the first core network device is requesting to obtain the communication information of the fourth core network device. Subsequently, the third core network device can send the communication information of the fourth core network device to the first core network device. This enables the first core network device to obtain the communication information of the fourth core network device in a timely and effective manner, supporting communication between the first and fourth core network devices to obtain terminal information from the fourth core network device.

[0241] Optionally, in some embodiments, the fourth core network device can determine terminal information, wherein the terminal information is used for communication between the first core network device and the terminal through the user plane, thereby enabling timely provision of terminal information to ensure that the first core network device and the terminal can communicate correctly based on the user plane.

[0242] Optionally, in some embodiments, the fourth core network device may receive a fifth message sent by the first core network device through the aforementioned "communication information", wherein the fifth message is used to request to obtain or subscribe to terminal information, and the fourth core network device may send or notify the first core network device of the terminal information when it determines the terminal information.

[0243] For example, the NF can obtain the SMF's communication information from the UDM. The NF can request the SMF's communication information from the UDM by sending a fourth message. The SMF's communication information can be used for communication between the NF and the SMF. The UDM can respond to the fourth message by sending the SMF's communication information to the NF. Then, the NF receives the SMF's communication information and uses it to communicate with the SMF, such as sending a fifth message to the SMF to request or subscribe to terminal information based on the fifth message. The SMF can respond to the fifth message by sending or notifying the NF of terminal information.

[0244] Optionally, in some embodiments, the communication information includes at least one of the following: the device identifier of the fourth core network device; the IP address of the fourth core network device; and the fully qualified domain name (FQDN) of the fourth core network device. This enables the first core network device and the fourth core network device to communicate correctly and effectively, allowing the first core network device to obtain terminal information in a timely and efficient manner.

[0245] Optionally, in some embodiments, the fourth core network device is used as an example of an SMF. The communication information of the SMF may include at least one of the following: the device identifier of the SMF, the IP address of the SMF, and the FQDN of the SMF.

[0246] Optionally, in some embodiments, the fourth message described above is used to request communication information of the fourth core network device from the third core network device, while the fifth message is used to request terminal information to be obtained or subscribed to from the fourth core network device. The fourth and fifth messages may each include at least one of the following: terminal identification information, DNN, and Single Network Slice Selection Assistance Information (S-NSSAI). This ensures that correct terminal information can be obtained, greatly improving the effectiveness of communication between the first core network device and the terminal through the user plane.

[0247] The terminal's identification information is used to identify the terminal. This identification information may include, for example, the terminal's Subscription Permanent Identifier (SUPI) or Generic Public Subscription Identity (GPSI).

[0248] Optionally, in some embodiments, during the process of acquiring terminal information, the first core network device may send a sixth message to the third core network device. This sixth message requests to acquire or subscribe to terminal information from the third core network device. Subsequently, the first core network device may receive the terminal information sent or notified by the third core network device. This improves the flexibility of terminal information acquisition, making it suitable for customized core network architectures and ensuring that the first core network device can acquire the correct terminal information to support communication between the first core network device and the terminal through the user plane.

[0249] For example, in the process of acquiring terminal information, the NF can send a sixth message to the UDM. This sixth message can be used to request or subscribe to terminal information from the UDM. The NF can then receive the terminal information sent or notified by the UDM. This improves the flexibility of terminal information acquisition, making it suitable for customized core network architectures and ensuring that the NF obtains the correct terminal information to support communication between the NF and the terminal through the user plane.

[0250] Optionally, in some embodiments, during the process of acquiring terminal information, the first core network device may send a sixth message to the fifth core network device. This sixth message requests to acquire or subscribe to terminal information from the fifth core network device. The first core network device may receive the terminal information sent or notified by the fifth core network device. This improves the flexibility of terminal information acquisition, making it suitable for customized core network architectures and ensuring that the first core network device can acquire the correct terminal information to support communication between the first core network device and the terminal through the user plane.

[0251] Optionally, in some embodiments, the fifth core network device can forward the sixth message to the third core network device, and the third core network device can receive the sixth message forwarded by the fifth core network device. The sixth message is used to request to obtain or subscribe to terminal information, and the third core network device can send or notify the first core network device of the terminal information through the fifth core network device.

[0252] Optionally, in some embodiments, the aforementioned fifth core network device can be NEF and / or BSF, and the first core network device can be NF. In this case, NF can send a sixth message to NEF to request NEF to obtain terminal information based on the sixth message. After receiving the sixth message, NEF can initiate a request to BSF to obtain or subscribe to terminal information. After determining the terminal information or having subscribed to terminal information, BSF can respond to the request initiated by NEF by sending or notifying NEF of the terminal information. NEF then receives the terminal information sent or notified by BSF and feeds the terminal information back to NF. No restrictions are placed on this.

[0253] Optionally, in some embodiments, the fifth core network device can be NEF, the first core network device can be NF, and the third core network device can be UDM. In this case, NF can send a sixth message to NEF to request NEF to obtain terminal information based on the sixth message. After receiving the sixth message, NEF can initiate a request to UDM to request to obtain or subscribe to terminal information. After determining the terminal information or having subscribed to terminal information, UDM can respond to the request initiated by NEF by sending or notifying NEF of the terminal information. NEF then receives the terminal information sent or notified by UDM and feeds the terminal information back to NF. There are no restrictions on this.

[0254] Optionally, in some embodiments, the sixth message may include at least one of the following: terminal identification information, DNN, and S-NSSAI. This ensures that terminal information can be correctly obtained and supports the accuracy of communication between the first core network device and the terminal through the user plane.

[0255] Optionally, in some embodiments, the NF can obtain the terminal's IP address based on the above method, and the NF can also obtain the pre-configured port information of the terminal, without limitation.

[0256] In step S2102, the first core network device sends a second message to the terminal through the access network device based on the terminal information.

[0257] Optionally, in some embodiments, the second message is sent by the first core network device to the terminal via the user.

[0258] Optionally, in some embodiments, after obtaining terminal information, the first core network device can send a second message to the terminal through the access network device based on the terminal information. Optionally, in some embodiments, the second message can also be a user plane message. In this case, the first core network device can send the second message to the terminal through the access network device using the terminal information after obtaining the terminal information.

[0259] Optionally, in some embodiments, the first core network device can send a second message to the terminal through an access network device. For example, the first core network device transmits the second message via a Non-Access Stratum (NAS) message, and the access network device can be used to forward the second message sent by the first core network device. For instance, the access network device receives the second message sent by the first core network device through terminal information and then forwards the second message to the terminal. In this process, the access network device may not perform parsing processing on the second message.

[0260] Optionally, in some embodiments, after obtaining the terminal information, the NF can send a second message to the UE through the base station based on the terminal information.

[0261] Optionally, in some embodiments, the second message is sent via terminal information.

[0262] Optionally, in some embodiments, the second message may be transmitted based on a connectionless protocol or a connection-oriented protocol.

[0263] Optionally, in some embodiments, the "connectionless transport protocol" may be, for example, the User Datagram Protocol (UDP). Optionally, in some embodiments, the "connection-oriented protocol" may be, for example, the Transmission Control Protocol (TCP).

[0264] Optionally, in some embodiments, the NF can use the received IP address and port information of the UE and send the second message directly to the UE via UDP. Optionally, in some embodiments, the NF can use the received IP address and port information of the UE and establish a connection with the UE via TCP. Then, the NF can send the second message according to the newly established connection.

[0265] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2102. For example, steps S2101 and S2102 may be implemented as independent embodiments, steps S2101+S2102 may be implemented as independent embodiments, etc., but are not limited thereto.

[0266] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0267] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0268] In this embodiment, the first core network device obtains terminal information and, based on the terminal information, sends a second message to the terminal through the access network device. Thus, the first core network device can obtain terminal information in a timely and accurate manner, and can communicate with the terminal through the user plane based on the terminal information, thereby ensuring the effective implementation of services.

[0269] It should be noted that in the following embodiments, the descriptions of the same or corresponding terms and method steps as in the above embodiments can be found in the above embodiments, and will not be repeated here.

[0270] Figure 2B is an interactive schematic diagram of a communication method according to another embodiment of the present disclosure. As shown in Figure 2B, the embodiments of the present disclosure relate to a communication method, which can be used in a communication system 100, and are not limited thereto. Optionally, in this embodiment, taking the example that the first core network device has not obtained terminal information, the first core network device can instruct the terminal to initiate the establishment of a Protocol Data Unit (PDU) session with the first core network device. This PDU session can be used for communication between the first core network device and the terminal through the user plane. The above method includes:

[0271] Step S2201: The first core network device sends a first message to the terminal through the access network device.

[0272] In other words, if the first core network device does not obtain terminal information, the first core network device can instruct the terminal to establish a PDU session related to the first core network device, so that the terminal and the first core network device can communicate based on the PDU session.

[0273] Optionally, in some embodiments, the first core network device can send the first message to the terminal through the access network device. For example, the first core network device transmits the first message via NAS messages, and the access network device can be used to forward the first message sent by the first core network device. For instance, the access network device receives the first message sent by the first core network device and then forwards the first message to the terminal. In this process, the access network device may not perform parsing processing on the first message.

[0274] Optionally, in some embodiments, the first core network device may be, for example, an NF (Network Function). The terminal may be, for example, a UE (User Equipment).

[0275] Optionally, in some embodiments, the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

[0276] Optionally, in some embodiments, the NF may send a first message to the UE to instruct the UE to establish a PDU session with the NF.

[0277] Optionally, in some embodiments, the NF can send the first message to the UE via UDM or SMS-SC.

[0278] Optionally, in some embodiments, the NF selects an appropriate SMS-SC based on the configured information.

[0279] Optionally, in some embodiments, the NF sends a submission trigger message to the SMS-SC (the submission trigger message may contain at least one of the following: GPSI, SUPI, NF information (e.g., NF type, NF IP address, NF FQDN), indication of establishing a PDU session related to the connection between the UE and the NF, DNN, protocol type, trigger reference number, validity period, priority, SMSF service node ID, Short Message Service (SMS) application port ID, trigger payload, and trigger indication). The submission trigger message may be an optional example of the first message.

[0280] Optionally, in some embodiments, Mobile Terminated Short Message Service (MT SMS) can be performed between the SMS-SC and the UE. Optionally, in some embodiments, the SMS-SC can perform MT SMS transmission. Optionally, in some embodiments, the SMS-SC can send a received commit trigger message (an optional example of the first message mentioned above) to the UE, thereby enabling the NF to send the first message to the UE via the SMS-SC.

[0281] Optionally, in some embodiments, the first message includes at least one of the following: device information of the first core network device; first indication information, wherein the first indication information is used to indicate the establishment of a PDU session; data network name (DNN); and protocol type. This effectively instructs the terminal to establish a PDU session related to the first core network device, ensuring that the PDU session can be correctly established to support communication between the first core network device and the terminal based on the PDU session.

[0282] The equipment information of the first core network device describes the device status of the first core network device. This equipment information may be, for example, the equipment information of an NF (Network Functions). The first indication information is used to indicate the establishment of a PDU session. This first indication information can be an indication field, configured with a value to indicate the establishment of a PDU session.

[0283] Optionally, in some embodiments, the device information of the first core network device includes at least one of the following: the type of the first core network device; the Internet Protocol (IP) address of the first core network device; the fully qualified domain name (FQDN) of the first core network device; and the port number of the first core network device. This enables the terminal to correctly and comprehensively obtain information about the first core network device with which it needs to establish a PDU session, supporting the correct establishment of the PDU session.

[0284] For example, if the first core network device is an NF, the device information of the NF can be at least one of the following: the type of the NF, the IP address of the NF, the FQDN of the NF, and the port number of the NF, without any restrictions.

[0285] Optionally, in some embodiments, the first core network device may send a first message to the terminal, and the terminal may establish a PDU session based on the first message, thereby realizing the timely and effective establishment of the PDU session, enabling the first core network device and the terminal to communicate correctly through the PDU session.

[0286] In step S2202, the terminal determines the port information of the first core network device based on the first message.

[0287] Optionally, in some embodiments, the first core network device can send a first message to the terminal through the access network device. The terminal can then receive the first message from the first core network device through the access network device and determine the port information of the first core network device based on the first message. Alternatively, in some embodiments, the NF can send a first message to the UE through the base station. The UE can then receive the first message from the NF through the base station and determine the port information of the NF based on the first message.

[0288] Optionally, in some embodiments, the first core network device can send the first message to the terminal via the access network device. For example, the first core network device transmits the first message via NAS messages, and the access network device can be used to forward the first message sent by the first core network device. For instance, the access network device receives the first message sent by the first core network device and then forwards it to the terminal. During this process, the access network device may not perform any parsing or processing on the first message. The terminal can then receive the first message forwarded by the access network device, without any restrictions.

[0289] Optionally, in some embodiments, the port information of the first core network device is, for example, the port number of the NF. Optionally, in some embodiments, the UE can determine the port number used for communicating with the NF based on the DNN, NF type, NF IP address, NF FQDN, and an indication of a PDU session related to establishing a connection between the UE and the NF. The UE can use the determined port number to communicate with the NF.

[0290] In step S2203, the terminal sends a third message to the second core network device through the access network device.

[0291] Optionally, in some embodiments, the second core network device may be an AMF.

[0292] Optionally, in some embodiments, the second core network device may be an SMF.

[0293] Optionally, in some embodiments, the third message is used to request the establishment of a PDU session, and the third message can be a Non-Access Stratum (NAS) message between the terminal and the second core network equipment. Optionally, in some embodiments, the UE can send a NAS message to the AMF to request the establishment of a PDU session.

[0294] Optionally, in some embodiments, the terminal can send a third message to the second core network device via the access network device. For example, the terminal transmits the third message via NAS messages, and the access network device can be used to forward the third message sent by the terminal. For instance, the access network device receives the third message sent by the terminal and then forwards it to the second core network device. During this process, the access network device may not parse or process the third message. Then, the second core network device can receive the third message forwarded by the access network device, without limitation.

[0295] Optionally, in some embodiments, the third message may include: port information of the first core network device. This ensures that the PDU session between the first core network device and the terminal is correctly established. Optionally, in some embodiments, the third message may also include at least one of the following: DNN (the DNN can be used to establish a PDU session for communication between the terminal and the first core network device via the user plane), request type, and request information, wherein the request information is used to request the second core network device to establish a PDU session related to the terminal and the first core network device. This effectively improves the accuracy and timeliness of PDU session establishment and enhances the performance of PDU session-based communication between the first core network device and the terminal.

[0296] In step S2204, the second core network device establishes a PDU session based on the third message.

[0297] Optionally, in some embodiments, the second core network device can receive a third message sent by the terminal through the access network device and establish a PDU session based on the third message. Optionally, in some embodiments, the second core network device can initiate interaction with other core network devices in the core network used to establish a PDU session to achieve the establishment of a PDU session. These other core network devices can be, for example, UPF, SMF, PCF, UDM, DN, etc., and are not limited thereto. Optionally, in some embodiments, the AMF can initiate interaction with core network devices such as UPF, SMF, PCF, UDM, and DN to establish a PDU session.

[0298] In step S2205, the first core network device communicates with the terminal through a PDU session.

[0299] After establishing a PDU session, the first core network device can communicate with the terminal through the PDU session to transmit service data. Optionally, in some embodiments, after establishing a PDU session, the NF can communicate with the UE through the PDU session to transmit service data.

[0300] Optionally, in some embodiments, if the first core network device triggers the establishment of a PDU session, the fourth core network device can maintain a mapping relationship between the DNN and the first function. The first function is used to establish a Protocol Data Unit (PDU) session related to the terminal and the first core network device. This mapping relationship indicates that there is a certain connection between the DNN and the first function, clarifying that the DNN can be used to establish a Protocol Data Unit (PDU) session related to the terminal and the first core network device. Therefore, when establishing a PDU session based on DNN assistance, the correct establishment of the PDU session can be ensured, thereby greatly improving the communication performance between the terminal and the first core network device based on the PDU session.

[0301] Optionally, in some embodiments, the fourth core network device is, for example, an SMF. The SMF can establish a mapping relationship between the DNN and the first function. That is, the SMF can maintain a mapping relationship between the DNN and the first function. The first function is used to establish a Protocol Data Unit (PDU) session between the UE and the NF. The PDU session is used for communication between the UE and the NF. This mapping relationship indicates that there is a certain connection between the DNN and the first function, and it is clear that the DNN can be used to establish a PDU session.

[0302] Optionally, in some embodiments, the user plane security policy for PDU sessions is configured as at least one of the following: integrity protection; encryption protection. This improves both the security and accuracy of PDU-based session communication.

[0303] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2205. For example, steps S2201, S2202, S2203, S2204, and S2205 may be implemented as independent embodiments, steps S2201+S2202 may be implemented as independent embodiments, steps S2202+S2203 may be implemented as independent embodiments, steps S2201+S2202+S2203 may be implemented as independent embodiments, steps S2201+S2203+S2204+S2205 may be implemented as independent embodiments, and so on, but not limited thereto.

[0304] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0305] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0306] In this embodiment, the first core network device sends a first message to the terminal via the access network device. This first message instructs the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device. Based on the first message, the terminal determines the port information of the first core network device. Then, the terminal sends a third message to the second core network device via the access network device. This third message requests the second core network device to establish a PDU session between the terminal and the first core network device. The first core network device then communicates with the terminal through this PDU session. This enables the timely and effective establishment of a PDU session between the terminal and the first core network device, allowing the first core network device to communicate with the terminal based on the PDU session and ensuring effective service delivery.

[0307] Figure 3A is an interactive schematic diagram illustrating a communication method according to yet another embodiment of the present disclosure. As shown in Figure 3A, the embodiments of the present disclosure relate to a communication method that can be used in a terminal. The method includes:

[0308] Step S3101: Receive a first message sent by the first core network device through the access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

[0309] Optionally, in some embodiments, the method further includes:

[0310] Establish a PDU session based on the first message.

[0311] Optionally, in some embodiments, the first message includes at least one of the following:

[0312] Equipment information for the first core network equipment;

[0313] First indication information, wherein the first indication information is used to indicate the establishment of a PDU session;

[0314] Data network name: DNN;

[0315] Protocol type.

[0316] Optionally, in some embodiments, the device information of the first core network device includes at least one of the following:

[0317] Types of equipment in the first core network;

[0318] The Internet Protocol (IP) address of the first core network device;

[0319] The fully qualified domain name (FQDN) of the first core network equipment;

[0320] The port number of the first core network device.

[0321] Optionally, in some embodiments, establishing a PDU session based on the first message includes:

[0322] The access network device sends a third message to the second core network device, wherein the third message is used to request the second core network device to establish a PDU session related to the terminal and the first core network device.

[0323] Optionally, in some embodiments, the method further includes:

[0324] Based on the first message, determine the port information of the first core network device.

[0325] Optionally, in some embodiments, the third message includes at least one of the following:

[0326] Port information of the first core network equipment;

[0327] DNN;

[0328] Request type;

[0329] The request information is used to request the second core network device to establish a PDU session between the terminal and the first core network device.

[0330] The communication method involved in the embodiments of this disclosure may include step S3101. For example, step S3101 may be implemented as a standalone embodiment, but is not limited thereto.

[0331] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0332] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0333] Figure 3B is an interactive schematic diagram illustrating a communication method according to yet another embodiment of the present disclosure. As shown in Figure 3B, the embodiments of the present disclosure relate to a communication method that can be used in a terminal. The method includes:

[0334] Step S3201: Receive a second message sent by the first core network device through the access network device. The second message is sent by the first core network device through terminal information and is sent by the first core network device through the user to the terminal.

[0335] Optionally, in some embodiments, the terminal information includes at least one of the following:

[0336] The terminal's IP address;

[0337] Terminal port information.

[0338] The communication method involved in the embodiments of this disclosure may include step S3201. For example, step S3201 may be implemented as a standalone embodiment, but is not limited thereto.

[0339] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0340] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0341] Figure 4A is an interactive schematic diagram illustrating a communication method according to another embodiment of the present disclosure. As shown in Figure 4A, the embodiments of the present disclosure relate to a communication method that can be used in a first core network device. The method includes:

[0342] Step S4101: Send a first message to the terminal through the access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

[0343] Optionally, in some embodiments,

[0344] Optionally, in some embodiments, sending a first message to the terminal via the access network device includes:

[0345] If terminal information is not obtained, the first message is sent to the terminal through the access network equipment.

[0346] Optionally, in some embodiments, the first message includes at least one of the following:

[0347] Equipment information for the first core network equipment;

[0348] First indication information, wherein the first indication information is used to indicate the establishment of a PDU session;

[0349] Data network name: DNN;

[0350] Protocol type.

[0351] Optionally, in some embodiments, the device information of the first core network device includes at least one of the following:

[0352] Types of equipment in the first core network;

[0353] The Internet Protocol (IP) address of the first core network device;

[0354] The fully qualified domain name (FQDN) of the first core network equipment;

[0355] The port number of the first core network device.

[0356] The communication method involved in the embodiments of this disclosure may include step S4101. For example, step S4101 may be implemented as a standalone embodiment, but is not limited thereto.

[0357] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0358] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0359] Figure 4B is an interactive schematic diagram of a communication method according to another embodiment of the present disclosure. As shown in Figure 4B, the embodiments of the present disclosure relate to a communication method that can be used in a first core network device. The method includes:

[0360] Step S4201: Obtain terminal information.

[0361] Step S4202: Based on the terminal information, a second message is sent to the terminal through the access network device, wherein the second message is sent by the first core network device to the terminal through the user.

[0362] Optionally, in some embodiments, obtaining terminal information includes:

[0363] Obtain or subscribe to terminal information from the fourth core network equipment.

[0364] Optionally, in some embodiments, obtaining or subscribing to terminal information from the fourth core network device includes:

[0365] Send a fourth message to the third core network device, wherein the fourth message is used to request to obtain the communication information of the fourth core network device, and the third core network device stores the communication information of the fourth core network device;

[0366] Receive communication information sent by third core network devices;

[0367] Based on communication information, obtain or subscribe to terminal information from the fourth core network equipment.

[0368] Optionally, in some embodiments, obtaining or subscribing to terminal information from the fourth core network device based on communication information includes:

[0369] Based on the communication information, a fifth message is sent to the fourth core network device, wherein the fifth message is used to request to obtain or subscribe to terminal information from the fourth core network device;

[0370] Receive terminal information sent or notified by the fourth core network device.

[0371] Optionally, in some embodiments, the communication information includes at least one of the following:

[0372] Equipment identification for the fourth core network equipment;

[0373] The Internet Protocol (IP) address of the fourth core network device;

[0374] The fully qualified domain name (FQDN) of the fourth core network device.

[0375] Optionally, in some embodiments, obtaining terminal information includes:

[0376] Send a sixth message to the third core network device or the fifth core network device, wherein the sixth message is used to request to obtain or subscribe to terminal information from the third core network device or the fifth core network device;

[0377] Receive terminal information sent or notified by the third core network device or the fifth core network device.

[0378] Optionally, in some embodiments, the fourth message, or the fifth message, or the sixth message includes at least one of the following:

[0379] Terminal identification information;

[0380] Data network name: DNN;

[0381] Single network slice selection auxiliary information S-NSSAI.

[0382] Optionally, in some embodiments, the terminal information includes at least one of the following:

[0383] The terminal's IP address;

[0384] Terminal port information.

[0385] The communication method involved in the embodiments of this disclosure may include at least one of steps S4201 to S4202. For example, steps S4201 and S4202 may be implemented as independent embodiments, steps S4201+S4202 may be implemented as independent embodiments, etc., but are not limited thereto.

[0386] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0387] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0388] Figure 5 is an interactive schematic diagram illustrating a communication method according to yet another embodiment of the present disclosure. As shown in Figure 5, the embodiments of the present disclosure relate to a communication method that can be used in a third core network device. The method includes:

[0389] Step S5101: Send communication information of the fourth core network device to the first core network device, wherein the communication information is used by the first core network device to obtain or subscribe to terminal information from the fourth core network device, and the terminal information is used by the first core network device to send a second message to the terminal, the second message being sent by the first core network device to the terminal through the user; or, send or notify the terminal information to the first core network device.

[0390] Optionally, in some embodiments, the method further includes:

[0391] Receive a fourth message sent by the first core network device, wherein the fourth message is used to request to obtain the communication information of the fourth core network device stored by the third core network device.

[0392] Optionally, in some embodiments, the communication information includes at least one of the following:

[0393] Equipment identification for the fourth core network equipment;

[0394] The Internet Protocol (IP) address of the fourth core network device;

[0395] The fully qualified domain name (FQDN) of the fourth core network device.

[0396] Optionally, in some embodiments, the method further includes:

[0397] Receive the sixth message sent by the first core network device, wherein the sixth message is used to request to obtain or subscribe to terminal information from the third core network device.

[0398] Optionally, in some embodiments, the fourth or sixth message includes at least one of the following:

[0399] Terminal identification information;

[0400] Data network name: DNN;

[0401] Single network slice selection auxiliary information S-NSSAI.

[0402] Optionally, in some embodiments, the terminal information includes at least one of the following:

[0403] The terminal's IP address;

[0404] Terminal port information.

[0405] The communication method involved in the embodiments of this disclosure may include step S5101. For example, step S5101 may be implemented as a standalone embodiment, but is not limited thereto.

[0406] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0407] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0408] Figure 6A is an interactive schematic diagram illustrating a communication method according to another embodiment of the present disclosure. As shown in Figure 6A, the embodiments of the present disclosure relate to a communication method that can be used in a fourth core network device. The method includes:

[0409] Step S6101: Establish a mapping relationship between the data network name DNN and the first function, wherein the first function is used to establish a protocol data unit (PDU) session between the terminal and the first core network device.

[0410] Optionally, in some embodiments, the user plane security policy for the PDU session is configured to at least one of the following:

[0411] Integrity protection;

[0412] Encryption protection.

[0413] The communication method involved in the embodiments of this disclosure may include step S6101. For example, step S6101 may be implemented as a standalone embodiment, but is not limited thereto.

[0414] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0415] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0416] Figure 6B is an interactive schematic diagram illustrating a communication method according to yet another embodiment of the present disclosure. As shown in Figure 6B, the embodiments of the present disclosure relate to a communication method that can be used in a fourth core network device. The method includes:

[0417] Step S6201: Send or notify terminal information to the first core network device, wherein the terminal information is used by the first core network device to send a second message to the terminal, and the second message is sent by the first core network device to the terminal through the user.

[0418] Optionally, in some embodiments, the method further includes:

[0419] Receive the fifth message sent by the first core network device, wherein the fifth message is used to request to obtain or subscribe to terminal information from the fourth core network device.

[0420] Optionally, in some embodiments, the fifth message includes at least one of the following:

[0421] Terminal identification information;

[0422] Data network name: DNN;

[0423] Single network slice selection auxiliary information S-NSSAI.

[0424] Optionally, in some embodiments, the terminal information includes at least one of the following:

[0425] The terminal's IP address;

[0426] Terminal port information.

[0427] The communication method involved in the embodiments of this disclosure may include step S6201. For example, step S6201 may be implemented as a standalone embodiment, but is not limited thereto.

[0428] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0429] In the embodiments disclosed herein, each step and its optional implementation can also be carried out independently.

[0430] Examples of the above embodiments are illustrated below:

[0431] This disclosure provides a method for obtaining terminal information through network functions, and also provides a security protocol data unit (PDU) session establishment mechanism for connecting network functions.

[0432] The example uses the UE as the terminal, the NF and UDM as core network devices, and the UE's IP address as terminal information.

[0433] As shown in Figure 7A, which is an application diagram of an embodiment of this disclosure, the NF can obtain SMF information (an optional example of the communication information described above) from the UDM. This SMF information is used by the NF to communicate with the SMF.

[0434] 1a. NF sends an SMF information request message to UDM.

[0435] Optionally, in some embodiments, the SMF information request message (an optional example of the fourth message described above) may be referred to as an SMF information Request.

[0436] Optionally, in some embodiments, in order to send messages to the UE via the user, the NF may need to obtain the UE's IP address from the SMF. To obtain SMF information (e.g., SMF ID, SMF address information (including the SMF's IP address and Fully Qualified Domain Name (FQDN))), the NF sends an SMF information request message to the UDM. This SMF information request message includes the UE ID (e.g., Subscription Permanent Identifier (SUPI), Generic Public Subscription Identity (GPSI)), Data Network Name (DNN), and Single Network Slice Selection Assistance Information (S-NSSAI).

[0437] 2a. UDM sends an SMF information response message to NF.

[0438] Optionally, in some embodiments, the SMF information response message may be referred to as an SMF information response.

[0439] Optionally, in some embodiments, the UDM sends SMF information to the NF. For example, the UDM may return SMF information (e.g., SMFID, SMF IP address, SMF FQDN) to the NF.

[0440] As shown in Figure 7B, which is a schematic diagram of another application in an embodiment of this disclosure, the NF obtains the UE's IP address from the UDM, SMF, or BSF.

[0441] 1b. The NF sends a UE IP address request message (an optional example of the fifth or sixth message above) or a UE IP address subscription message (an optional example of the fifth or sixth message above) to the UDM / SMF / BSF.

[0442] Optionally, in some embodiments, in order to send messages to the UE via the user, the NF can request or subscribe to the UE's IP address from the UDM, SMF, or BSF. The UE's IP address request message or the UE's IP address subscription message may include the UE ID, DNN, and S-NSSAI.

[0443] 2b. The UDM / SMF / BSF sends the UE's IP address response message or the UE's IP address notification message to the NF.

[0444] Optionally, in some embodiments, the UDM, SMF, or BSF can send a UE IP address response message or a UE IP address notification message to the NF to send the UE's IP address. If the UE's IP address is not found, the NF can be notified that "UE IP address acquisition failed".

[0445] Optionally, in some embodiments, the UDM, SMF, or BSF can send the UE's port information to the NF.

[0446] As shown in Figure 7C, which is a schematic diagram of another application in an embodiment of this disclosure, the NF can obtain SMF information from the UDM, which is used for communication between the NF and the SMF. The NF can retrieve the UE's IP address through the NEF.

[0447] 1c. The NF sends a UE IP address request message to the NEF (an optional example of the sixth message mentioned above).

[0448] Optionally, in some embodiments, the NF sends a UE IP address request message to the NEF. This UE IP address request message includes the UE ID, DNN, and S-NSSAI.

[0449] 2c. NEF license.

[0450] Optionally, in some embodiments, the NEF authorizes the NF request. If authorization is unsuccessful (e.g., the NF is not authorized to obtain the UE's IP address according to the protocol), the NEF replies to the NF with a result value indicating authorization failure. Otherwise, the NEF continues with the following steps.

[0451] Optionally, in some embodiments, option 1 can be performed:

[0452] 3c. The NEF sends a UE IP address request message to the BSF.

[0453] Optionally, in some embodiments, the NEF sends a UE IP address request message to the BSF. The UE IP address request message includes UEID, DNN, and S-NSSAI.

[0454] Optionally, in some embodiments, the NEF sends the UE's IP address subscription message to the BSF.

[0455] 4c. The BSF sends the UE's IP address response message to the NEF.

[0456] Optionally, in some embodiments, the BSF sends a response message to the NEF regarding the UE's IP address. If the UE's IP address is not found, it indicates that the UE's IP address was not found.

[0457] Optionally, in some embodiments, the NEF sends the UE's IP address notification message to the BSF.

[0458] Optionally, in some embodiments, option 2 may be performed:

[0459] Optionally, in some embodiments, the BSF sends the UE's IP address and port information to the NEF.

[0460] 3c. NEF sends a UE IP address request message to UDM.

[0461] Optionally, in some embodiments, the NEF sends a UE IP address request message to the UDM. The UE IP address request message includes the UE ID, DNN, and S-NSSAI. If the UE's IP address is not found, it indicates that the UE's IP address was not found.

[0462] Optionally, in some embodiments, the NEF sends the UE's IP address subscription message to the BSF.

[0463] 4c. UDM sends the UE's IP address response message to NEF.

[0464] Optionally, in some embodiments, the UDM sends a response message for the UE's IP address to the NEF. If the UE's IP address is not found, it indicates that the UE's IP address was not found.

[0465] Optionally, in some embodiments, the UDM sends the UE's IP address notification message to the NEF.

[0466] Optionally, in some embodiments, the UDM sends the UE's IP address and port information to the NEF.

[0467] 5c. The NEF sends the UE's IP address response message to the NF.

[0468] Optionally, in some embodiments, the NEF sends the UE's IP address to the NF.

[0469] After obtaining the UE's IP address, the UE's port information can also be obtained. This port information can be pre-configured.

[0470] Optionally, in some embodiments, the NF can use the received IP address and port information of the UE and send messages directly to the UE via UDP.

[0471] Optionally, in some embodiments, the NF can use the received UE's IP address and port information to establish a connection with the UE via TCP. Then, the NF can send messages based on the newly established connection (an optional example of the second message described above).

[0472] As shown in Figure 7D, which is another application diagram in an embodiment of this disclosure, the NF can initiate a PDU session establishment process. If the NF cannot obtain the UE's IP address from the core network, the network function can trigger the terminal to establish a PDU session and enable the terminal to actively subscribe to NF notifications.

[0473] 1d. NF sends a request message to UDM by calling the Nudm_UECM_Get service.

[0474] Optionally, in some embodiments, the NF can invoke the Nudm_UECM_Get service to obtain the UE's Short Message Service Function (SMSF) identity information. The NF can obtain the GPSI from the UDM before requesting the Nudm_UECM_Get service.

[0475] 2d. UDM sends a response message to NF by calling the Nudm_UECM_Get service.

[0476] Optionally, in some embodiments, the UDM can invoke the Nudr_DM_Query service to obtain the UE SMSF identity information. The UDM can send a response message to the NF by invoking the Nudm_UECM_Get service, and this response message may contain the UE SMSF identity information.

[0477] 3d and NF submit a trigger message to SMS-SC (an optional example of the first message mentioned above).

[0478] Optionally, in some embodiments, the NF selects an appropriate SMS-SC based on the configured information.

[0479] Optionally, in some embodiments, the NF can act as a Machine-Type Communication Interworking Function (MTC-IWF) entity and send a submission trigger message to the SMS-SC (which may include GPSI, SUPI, NF information (e.g., NF type, NF IP address, NF FQDN), an indication of establishing a PDU session related to the connection between the UE and the NF, the DNN associated with the NF, protocol type, trigger reference number, validity period, priority, SMSF service node ID, Short Message Service (SMS) application port ID, trigger payload, and trigger indication).

[0480] Optionally, in some embodiments, utilizing local policies (e.g., a dedicated DNN should use a dedicated port number, and an indication of establishing a PDU session related to the connection between the UE and the NF should use a dedicated port number), the UE can determine the port number used for communicating with the NF based on the NF-related DNN, NF type, NF IP address, NF FQDN, and the indication of establishing a PDU session related to the connection between the UE and the NF. The UE can then use the determined port number to communicate with the NF.

[0481] 4d. Send a commit trigger confirmation message to NF via SMS-SC.

[0482] Optionally, in some embodiments, the SMS-SC sends a commit trigger confirmation message to the NF to confirm that the SMS commit has been accepted by the SMS-SC.

[0483] 5d, SMS-SC and UE conduct Mobile Terminated Short Message Service (MT SMS).

[0484] Optionally, in some embodiments, SMS_SC performs MT SMS transmission.

[0485] Optionally, in some embodiments, SMS_SC may send the submission trigger message received in step 3d to the UE.

[0486] 6d. SMS-SC sends a message transmission report message to NF.

[0487] Optionally, in some embodiments, SMS_SC provides NF with a message transmission report message indicating the triggering transmission result (e.g., success, unknown, or failure, and the reason for failure).

[0488] 7d. The UE executes actions based on the trigger message.

[0489] Optionally, in some embodiments, the UE may perform an action in response to a trigger.

[0490] Optionally, in some embodiments, the UE can use the received DNN or a pre-configured DNN to establish a PDU session related to the connection between the UE and the NF.

[0491] Optionally, in some embodiments, if communication with the UE needs to be conducted via the user plane, the NF can subscribe to UDM notifications of port information updates. The UDM can notify the NF of the UE's updated port information and the UE's IP address by calling the Nudm_SDM_Notification service to send a notification message.

[0492] As shown in Figure 7E, Figure 7E is another application diagram of an embodiment of this disclosure. Figure 7E provides a user plane-based UE and network functional safety interaction mechanism.

[0493] 1e. The UE sends a PDU session establishment request message to the AMF (an optional example of the third message mentioned above).

[0494] Optionally, in some embodiments, the UE may send a NAS message (UE-requested DNN, request type, N1SM container (PDU session establishment request, port management information container)) to the AMF.

[0495] Optionally, in some embodiments, the following mechanism can be used to establish a connection with NFs and to select the DNN requested by the UE in the NAS message.

[0496] Optionally, in some embodiments, in order to establish a connection with NFs, the UE can set the requested DNN to the DNN received from the embodiment of FIG7D above.

[0497] 2e. AMF should be selected as SMF.

[0498] Optionally, in some embodiments, the AMF can select the SMF based on the DNN carried in the PDU session establishment request message.

[0499] 3e. The AMF sends an Nsmf_PDUSession_CreateSMContext request message to the selected SMF.

[0500] Optionally, in some embodiments, the Nsmf_PDUSession_CreateSMContext request message is, for example, the Nsmf_PDUSession_CreateSMContext Request.

[0501] Optionally, in some embodiments, the AMF sends an Nsmf_PDUsession_CreateSMContext request message to the selected SMF.

[0502] Optionally, in some other embodiments, the AMF sends an Nsmf_PDUsession_UpdateSMContext request message to the selected SMF.

[0503] Optionally, in some embodiments, the AMF may send the aforementioned DNN to the SMF.

[0504] 4e. SMF can query and / or update subscription data.

[0505] Optionally, in some embodiments, the SMF can query session management subscription data by calling the Nudm_SDM_Get service and subscribe to it, so as to be notified when the subscription data is modified by calling the Nudm_SDM_Subscribe service. Optionally, in some embodiments, the UDM can obtain the aforementioned information from the UDR.

[0506] 5e. SMF sends an Nsmf_PDUSession_CreateSMContext response message to AMF.

[0507] Optionally, in some embodiments, the Nsmf_PDUSession_CreateSMContext response message is, for example, the Nsmf_PDUSession_CreateSMContext Response.

[0508] Optionally, in some embodiments, the SMF sends an Nsmf_PDUSession_CreateSMContext response message to the AMF. This message may include: a reason, the SM context ID, or the N1SM container (an indication (or reason) of refusing to establish a PDU session). Alternatively, the SMF may send an Nsmf_PDUSession_UpdateSMContext response message to the AMF, depending on the request message received in step 3e.

[0509] 6e. Initiate PDU session authentication and / or authorization.

[0510] Optionally, in some embodiments, optional secondary authentication and / or authorization are included.

[0511] 7e(a) SMF selects PCF.

[0512] 7e(b) SMF establishes SM policy association or initiates modification of SM policy association.

[0513] Optionally, in some embodiments, if Dynamic Policy Control and Charging (PCC) is used for a PDU session, the SMF performs PCF selection based on the DNN.

[0514] 8e, SMF should be selected as UPF.

[0515] Optionally, in some embodiments, the SMF is selected as the UPF.

[0516] 9e. SMF initiates modification of SM policy association.

[0517] Optionally, in some embodiments, the SMF may initiate a modification of the SM policy association to send the assigned UE IP address to the PCF.

[0518] 10e(a) The SMF sends an N4 session establishment or modification request message to the selected UPF.

[0519] 10e(b) The UPF sends an N4 session establishment or modification response message to the SMF.

[0520] Optionally, in some embodiments, if the request type indicates "initial request", the SMF initiates an N4 session establishment process with the selected UPF.

[0521] 11e. SMF sends Namf_Communication_N1N2Message to AMF.

[0522] Optionally, in some embodiments, Namf_Communication_N1N2Message transmits messages, such as Namf_Communication_N1N2MessageTransfer.

[0523] Optionally, in some embodiments, the SMF sends an N2 short message to the AMF, which may carry information that the AMF forwards to the (R)AN, including user plane security information determined by the SMF.

[0524] Optionally, in some embodiments, the SMF stores mapping information between the DNN and its functions locally (i.e., some DNNs are used to establish PDU sessions associated with NFs). If a DNN is involved in establishing a PDU session with an NF, the SMF applies the following policies: User plane integrity protection (i.e., UP integrity protection is applied to all traffic on the PDU session) and User Plane (UP) confidentiality protection (i.e., UP encryption protection is applied to all traffic on the PDU session) (wherein, user plane confidentiality protection is optional. For example, user plane confidentiality protection should be used whenever regulations permit).

[0525] 12e. AMF sends an N2PDU session establishment request message (including NAS message) to (R)AN.

[0526] Optionally, in some embodiments, the AMF sends an N2PDU session establishment request message to the (R)AN.

[0527] 13e, (R)AN configuration: resources dedicated to the AN (accepting PDU session establishment).

[0528] Optionally, in some embodiments, (R)AN to UE: (R)AN may publish a dedicated signaling exchange with the UE, which is related to information received from the SMF.

[0529] 14e, (R)AN sends an N2PDU session establishment response message to AMF.

[0530] Optionally, in some embodiments, (R)AN sends an N2PDU session establishment response message (user plane execution policy notification) to the AMF.

[0531] Optionally, in some embodiments, the UE may send the first uplink data to the UPF.

[0532] 15e. The AMF sends an Nsmf_PDUSession_UpdateSMContext request message to the SMF.

[0533] Optionally, in some embodiments, the Nsmf_PDUSession_UpdateSMContext request message may be referred to as the Nsmf_PDUSession_UpdateSMContext Request.

[0534] Optionally, in some embodiments, the AMF sends an Nsmf_PDUsession_UpdateSMContext request message (containing SMS context ID, N2 SMS information, and request type) to the SMF. The AMF forwards the N2 SMS information received from the (R)AN to the SMF.

[0535] Optionally, in some embodiments, the NEF also utilizes information received from the UDM (including an AF-specific UE identifier represented as an external identifier) ​​to respond to an application function (AF).

[0536] This disclosure also provides embodiments of an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., a RAN) in any of the above methods.

[0537] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0538] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using 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 and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0539] Figure 8 is a schematic diagram of the structure of a communication device proposed in an embodiment of this disclosure. As shown in Figure 8, the communication device 8100 may include at least one of a transceiver module 8101, a processing module 8102, etc.

[0540] In some embodiments, the communication device 8100 is a terminal, wherein...

[0541] The transceiver module 8101 is used to receive a first message sent by the first core network device through the access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device; or the transceiver module 8101 is used to receive a second message sent by the first core network device through the access network device, wherein the second message is sent by the first core network device through terminal information, and the second message is sent by the first core network device through the user to the terminal.

[0542] Optionally, in some embodiments, wherein:

[0543] The processing module 8102 is used to establish a PDU session based on the first message.

[0544] Optionally, in some embodiments, the first message includes at least one of the following:

[0545] Equipment information for the first core network equipment;

[0546] First indication information, wherein the first indication information is used to indicate the establishment of a PDU session;

[0547] Data network name: DNN;

[0548] Protocol type.

[0549] Optionally, in some embodiments, the device information of the first core network device includes at least one of the following:

[0550] Types of equipment in the first core network;

[0551] The Internet Protocol (IP) address of the first core network device;

[0552] The fully qualified domain name (FQDN) of the first core network equipment;

[0553] The port number of the first core network device.

[0554] Optionally, in some embodiments, the transceiver module 8101 is used to send a third message to the second core network device through the access network device, wherein the third message is used to request the second core network device to establish a PDU session related to the terminal and the first core network device.

[0555] Optionally, in some embodiments, wherein:

[0556] The processing module 8102 is used to determine the port information of the first core network device based on the first message.

[0557] Optionally, in some embodiments, the third message includes at least one of the following:

[0558] Port information of the first core network equipment;

[0559] DNN;

[0560] Request type;

[0561] The request information is used to request the second core network device to establish a PDU session between the terminal and the first core network device.

[0562] Optionally, in some embodiments, the transceiver module 8101 is configured to receive a second message sent by the first core network device through the access network device, wherein the second message is sent by the first core network device through terminal information, or the second message is sent by the first core network device through the user to the terminal.

[0563] Optionally, in some embodiments, the terminal information includes at least one of the following:

[0564] The terminal's IP address;

[0565] Terminal port information.

[0566] Optionally, the transceiver module described above is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, which will not be elaborated here.

[0567] Optionally, the above processing module is used to perform at least one of the other steps executed by the terminal in any of the above methods, which will not be elaborated here.

[0568] In some embodiments, the communication device 8100 is a first core network device, wherein...

[0569] The transceiver module 8101 is used to send a first message to the terminal through the access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device; or the transceiver module 8101 is used to obtain terminal information and, based on the terminal information, send a second message to the terminal through the access network device, wherein the second message is sent by the first core network device to the terminal through the user.

[0570] Optionally, in some embodiments, the transceiver module 8101 is used to determine that terminal information has not been obtained and to send a first message to the terminal through the access network device.

[0571] Optionally, in some embodiments, the first message includes at least one of the following:

[0572] Equipment information for the first core network equipment;

[0573] First indication information, wherein the first indication information is used to indicate the establishment of a PDU session;

[0574] Data network name: DNN;

[0575] Protocol type.

[0576] Optionally, in some embodiments, the device information of the first core network device includes at least one of the following:

[0577] Types of equipment in the first core network;

[0578] The Internet Protocol (IP) address of the first core network device;

[0579] The fully qualified domain name (FQDN) of the first core network equipment;

[0580] The port number of the first core network device.

[0581] Optionally, in some embodiments, the transceiver module 8101 is used to obtain or subscribe to terminal information from the fourth core network device.

[0582] Optionally, in some embodiments, wherein:

[0583] The transceiver module 8101 is used to send a fourth message to the third core network device, wherein the fourth message is used to request to obtain the communication information of the fourth core network device, and the third core network device stores the communication information of the fourth core network device; receive the communication information sent by the third core network device; and obtain or subscribe to terminal information from the fourth core network device according to the communication information.

[0584] Optionally, in some embodiments, wherein:

[0585] The transceiver module 8101 is used to send a fifth message to the fourth core network device according to the communication information. The fifth message is used to request to obtain or subscribe to terminal information from the fourth core network device and to receive terminal information sent or notified by the fourth core network device.

[0586] Optionally, in some embodiments, the communication information includes at least one of the following:

[0587] Equipment identification for the fourth core network equipment;

[0588] The Internet Protocol (IP) address of the fourth core network device;

[0589] The fully qualified domain name (FQDN) of the fourth core network device.

[0590] Optionally, in some embodiments, wherein:

[0591] The transceiver module 8101 is used to send a sixth message to the third core network device or the fifth core network device. The sixth message is used to request to obtain or subscribe to terminal information from the third core network device or the fifth core network device, and to receive terminal information sent or notified by the third core network device or the fifth core network device.

[0592] Optionally, in some embodiments, the fourth message, or the fifth message, or the sixth message includes at least one of the following:

[0593] Terminal identification information;

[0594] Data network name: DNN;

[0595] Single network slice selection auxiliary information S-NSSAI.

[0596] Optionally, in some embodiments, the terminal information includes at least one of the following:

[0597] The terminal's Internet Protocol (IP) address;

[0598] Terminal port information.

[0599] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the first core network device in any of the above methods, which will not be elaborated here.

[0600] Optionally, the above processing module is used to perform at least one of the other steps performed by the first core network device in any of the above methods, which will not be elaborated here.

[0601] In some embodiments, the communication device 8100 is a third core network device, wherein...

[0602] The transceiver module 8101 is used to send communication information of the fourth core network device to the first core network device. The communication information is used by the first core network device to obtain or subscribe to terminal information from the fourth core network device. The terminal information is used by the first core network device to send a second message to the terminal. The second message is sent by the first core network device to the terminal through the user. Alternatively, it can be used to send or notify the terminal information to the first core network device.

[0603] Optionally, in some embodiments, wherein:

[0604] The transceiver module 8101 is used to receive a fourth message sent by the first core network device, wherein the fourth message is used to request to obtain the communication information of the fourth core network device stored by the third core network device.

[0605] Optionally, in some embodiments, the communication information includes at least one of the following:

[0606] Equipment identification for the fourth core network equipment;

[0607] The Internet Protocol (IP) address of the fourth core network device;

[0608] The fully qualified domain name (FQDN) of the fourth core network device.

[0609] Optionally, in some embodiments, the transceiver module 8101 is configured to receive a sixth message sent by the first core network device, wherein the sixth message is used to request to obtain or subscribe to terminal information from the third core network device.

[0610] Optionally, in some embodiments, the fourth or sixth message includes at least one of the following:

[0611] Terminal identification information;

[0612] Data network name: DNN;

[0613] Single network slice selection auxiliary information S-NSSAI.

[0614] Optionally, in some embodiments, the terminal information includes at least one of the following:

[0615] The terminal's IP address;

[0616] Terminal port information.

[0617] Optionally, the transceiver module described above is used to perform at least one of the communication steps such as sending and / or receiving performed by the third core network device in any of the above methods, which will not be elaborated here.

[0618] Optionally, the above processing module is used to perform at least one of the other steps performed by the third core network device in any of the above methods, which will not be elaborated here.

[0619] In some embodiments, the communication device 8100 is a fourth core network device, wherein...

[0620] The transceiver module 8101 is used to send or notify terminal information to the first core network device. The terminal information is used by the first core network device to send a second message to the terminal, which is sent by the first core network device through the user to the terminal; or

[0621] The processing module 8102 is used to establish a mapping relationship between the data network name (DNN) and the first function, wherein the first function is used to establish a protocol data unit (PDU) session between the terminal and the first core network device.

[0622] Optionally, in some embodiments, the user plane security policy for the PDU session is configured to at least one of the following:

[0623] Integrity protection;

[0624] Encryption protection.

[0625] Optionally, in some embodiments, the transceiver module 8101 is configured to receive a fifth message sent by the first core network device, wherein the fifth message is used to request to obtain or subscribe to terminal information from the fourth core network device.

[0626] Optionally, in some embodiments, the fifth message includes at least one of the following:

[0627] Terminal identification information;

[0628] DNN;

[0629] Single network slice selection auxiliary information S-NSSAI.

[0630] Optionally, in some embodiments, the terminal information includes at least one of the following:

[0631] The terminal's IP address;

[0632] Terminal port information.

[0633] Optionally, the transceiver module described above is used to perform at least one of the communication steps such as sending and / or receiving performed by the fourth core network device in any of the above methods, which will not be elaborated here.

[0634] Optionally, the above processing module is used to perform at least one of the other steps performed by the fourth core network device in any of the above methods, which will not be elaborated here.

[0635] Figure 9A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure. The communication device 9100 can be the terminal described above, or it can be the network device described above. The communication device 9100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 9100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0636] As shown in Figure 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The communication device 9100 is used to execute any of the above methods.

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

[0638] In some embodiments, the communication device 9100 further includes one or more transceivers 9103. When the communication device 9100 includes one or more transceivers 9103, the transceivers 9103 perform at least one of the communication steps such as sending and / or receiving in the above method, and the processor 9101 performs other steps.

[0639] In some embodiments, a transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

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

[0641] The communication device 9100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 9100 described in this disclosure is not limited thereto, and the structure of the communication device 9100 may not be limited by FIG. 9A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components 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, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (9) others, etc.

[0642] Figure 9B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. For cases where the communication device 9100 can be a chip or a chip system, please refer to the schematic diagram of the chip 9200 shown in Figure 9B, but it is not limited thereto.

[0643] Chip 9200 includes one or more processors 9201, which are used to perform any of the above methods.

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

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

[0646] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0647] In some embodiments, chip 9200 further includes one or more memories 9203 for storing instructions. Optionally, all or part of the memories 9203 may be located outside of chip 9200.

[0648] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 9100, cause the communication device 9100 to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0649] This disclosure also provides a program product that, when executed by the communication device 9100, causes the communication device 9100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0650] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0651] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

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

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

[0654] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method is executed by a terminal, and the method includes: The terminal receives a first message from the first core network device through the access network device, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

2. The method as described in claim 1, characterized in that, The method further includes: Based on the first message, establish the PDU session.

3. The method according to any one of claims 1-2, characterized in that, The first message includes at least one of the following: Equipment information of the first core network device; First indication information, wherein the first indication information is used to indicate the establishment of the PDU session; Data network name: DNN; Protocol type.

4. The method as described in claim 3, characterized in that, The device information of the first core network device includes at least one of the following: The type of the first core network device; The Internet Protocol (IP) address of the first core network device; The fully qualified domain name (FQDN) of the first core network device; The port number of the first core network device.

5. The method according to any one of claims 2-4, characterized in that, The step of establishing the PDU session based on the first message includes: The access network device sends a third message to the second core network device, wherein the third message is used to request the second core network device to establish the PDU session between the terminal and the first core network device.

6. The method as described in claim 5, characterized in that, The method further includes: Based on the first message, determine the port information of the first core network device.

7. The method according to any one of claims 5-6, characterized in that, The third message includes at least one of the following: Port information of the first core network device; DNN; Request type; The request information is used to request the second core network device to establish the PDU session between the terminal and the first core network device.

8. A communication method, characterized in that, The method is executed by a first core network device, and the method includes: The access network device sends a first message to the terminal, wherein the first message is used to instruct the terminal to establish a Protocol Data Unit (PDU) session related to the first core network device.

9. The method as described in claim 8, characterized in that, The step of sending the first message to the terminal via the access network device includes: If it is determined that terminal information has not been obtained, a first message is sent to the terminal through the access network device.

10. The method according to any one of claims 8-9, characterized in that, The first message includes at least one of the following: Equipment information of the first core network device; First indication information, wherein the first indication information is used to indicate the establishment of the PDU session; Data network name: DNN; Protocol type.

11. The method as described in claim 10, characterized in that, The device information of the first core network device includes at least one of the following: The type of the first core network device; The Internet Protocol (IP) address of the first core network device; The fully qualified domain name (FQDN) of the first core network device; The port number of the first core network device.

12. A communication method, characterized in that, The method is executed by the fourth core network device, and the method includes: Establish a mapping relationship between the data network name (DNN) and the first function, wherein the first function is used to establish a protocol data unit (PDU) session between the terminal and the first core network device.

13. The method as described in claim 12, characterized in that, The user plane security policy for the PDU session is configured to at least one of the following: Integrity protection; Encryption protection.

14. A communication method, characterized in that, The method is executed by a first core network device, and the method includes: Obtain terminal information; Based on the terminal information, a second message is sent to the terminal through the access network device, wherein the second message is sent by the first core network device to the terminal through the user.

15. The method as described in claim 14, characterized in that, The acquisition of terminal information includes: Obtain or subscribe to the terminal information from the fourth core network device.

16. The method as described in claim 15, characterized in that, The step of obtaining or subscribing to the terminal information from the fourth core network device includes: Send a fourth message to the third core network device, wherein the fourth message is used to request to obtain the communication information of the fourth core network device, and the third core network device stores the communication information of the fourth core network device; Receive the communication information sent by the third core network device; Based on the communication information, the terminal information is obtained or subscribed to from the fourth core network device.

17. The method as described in claim 16, characterized in that, The step of obtaining or subscribing to the terminal information from the fourth core network device based on the communication information includes: Based on the communication information, a fifth message is sent to the fourth core network device, wherein the fifth message is used to request to obtain or subscribe to the terminal information from the fourth core network device; Receive the terminal information sent or notified by the fourth core network device.

18. The method according to any one of claims 16-17, characterized in that, The communication information includes at least one of the following: The device identifier of the fourth core network device; The Internet Protocol (IP) address of the fourth core network device; The fully qualified domain name (FQDN) of the fourth core network device.

19. The method as described in claim 14, characterized in that, The acquisition of terminal information includes: Send a sixth message to a third core network device or a fifth core network device, wherein the sixth message is used to request to obtain or subscribe to the terminal information from the third core network device or the fifth core network device; Receive the terminal information sent or notified by the third core network device or the fifth core network device.

20. The method according to any one of claims 16-19, characterized in that, The fourth message, or the fifth message, or the sixth message includes at least one of the following: The terminal's identification information; Data network name: DNN; Single network slice selection auxiliary information S-NSSAI.

21. The method according to any one of claims 14-20, characterized in that, The terminal information includes at least one of the following: The IP address of the terminal; The port information of the terminal.

22. A communication method, characterized in that, The method is executed by a third core network device, and the method includes: Sending communication information of a fourth core network device to a first core network device, wherein the communication information is used by the first core network device to obtain or subscribe to terminal information from the fourth core network device, and the terminal information is used by the first core network device to send a second message to the terminal, the second message being sent by the first core network device to the terminal through the user; or, Send or notify the terminal information to the first core network device.

23. The method as described in claim 22, characterized in that, The method further includes: The system receives a fourth message sent by the first core network device, wherein the fourth message is used to request the acquisition of the communication information of the fourth core network device stored by the third core network device.

24. The method according to any one of claims 22-23, characterized in that, The communication information includes at least one of the following: The device identifier of the fourth core network device; The Internet Protocol (IP) address of the fourth core network device; The fully qualified domain name (FQDN) of the fourth core network device.

25. The method as described in claim 22, characterized in that, The method further includes: The system receives a sixth message sent by the first core network device, wherein the sixth message is used to request to obtain or subscribe to the terminal information from the third core network device.

26. The method according to any one of claims 23-25, characterized in that, The fourth message or the sixth message includes at least one of the following: The terminal's identification information; Data network name: DNN; Single network slice selection auxiliary information S-NSSAI.

27. The method according to any one of claims 22-26, characterized in that, The terminal information includes at least one of the following: The IP address of the terminal; The port information of the terminal.

28. A communication method, characterized in that, The method is executed by the fourth core network device, and the method includes: Sending or notifying terminal information to the first core network device, wherein the terminal information is used by the first core network device to send a second message to the terminal, and the second message is sent by the first core network device to the terminal through the user.

29. The method as described in claim 28, characterized in that, The method further includes: The system receives a fifth message sent by the first core network device, wherein the fifth message is used to request to obtain or subscribe to the terminal information from the fourth core network device.

30. The method as described in claim 29, characterized in that, The fifth message includes at least one of the following: The terminal's identification information; Data network name: DNN; Single network slice selection auxiliary information S-NSSAI.

31. The method according to any one of claims 28-30, characterized in that, The terminal information includes at least one of the following: The IP address of the terminal; The port information of the terminal.

32. A communication method, characterized in that, The method is executed by a terminal, and the method includes: The access network device receives a second message sent by the first core network device, wherein the second message is sent by the first core network device through terminal information and by the first core network device through the user plane.

33. The method as described in claim 32, characterized in that, The terminal information includes at least one of the following: The IP address of the terminal; The port information of the terminal.

34. A communication device, characterized in that, The communication device is used to perform the method as described in any one of claims 1-7, 8-11, 12-13, 14-21, 22-27, 28-31, or 32-33.

35. A communication system, characterized in that, The system includes a terminal, a first core network device, a third core network device, and a fourth core network device, wherein the terminal is used to perform the method as described in any one of claims 1-7 or 32-33, the first core network device is used to perform the method as described in any one of claims 8-11 or 14-21, the third core network device is used to perform the method as described in any one of claims 22-27, and the fourth core network device is used to perform the method as described in any one of claims 12-13 or 28-31.

36. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the method as described in any one of claims 1-33.

37. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-33.

Images