Communication method, communication device, communication system, storage medium, and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium, and a program product. The method is performed by a first node, and comprises: sending first information to a second node, wherein the first information is used for registering the first node in the second node, and the first node supports asynchronous type communication. By means of the solution of the present disclosure, a network device supporting asynchronous type communication can be deployed in a communication network.

Description

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

[0001] This disclosure relates to the field of wireless communication, and more particularly to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] Communication systems are offering increasingly diverse services. Some services may have low latency requirements and / or do not require immediate processing. Communication systems need to be able to support the implementation of such services. Summary of the Invention

[0003] This disclosure relates to a communication method, communication device, communication system, storage medium, and program product.

[0004] According to a first aspect of the present disclosure, a communication method is provided. The method is performed by a first node. The method includes: sending first information to a second node, wherein the first information is used to register the first node with the second node; wherein the first node supports asynchronous communication.

[0005] According to a second aspect of the present disclosure, a communication method is provided. The method is performed by a second node. The method includes: receiving first information sent by a first node, wherein the first information is used to register the first node in the second node; wherein the first node supports asynchronous communication.

[0006] According to a third aspect of the present disclosure, a communication method is provided. The method is applied to a communication system. The communication system includes a first node and a second node. The method includes: the first node sending first information to the second node, wherein the first information is used to register the first node with the second node; wherein the first node supports asynchronous communication.

[0007] According to a fourth aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication method as described in the first or second aspect.

[0008] According to a fifth aspect of this disclosure, a communication system is provided. The communication system includes a first node and a second node. The first node is configured to perform the communication method as described in the first aspect. The second node is configured to perform the communication method as described in the second aspect.

[0009] According to a sixth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in the first or second aspect.

[0010] According to a seventh aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in the first or second aspect.

[0011] According to an eighth aspect of the present disclosure, a computer program is provided. When the computer program is run on a computer, it causes the computer to perform the communication method as described in the first or second aspect.

[0012] According to a ninth aspect of this disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication method as described in the first or second aspect.

[0013] According to embodiments of this disclosure, network devices that support asynchronous communication can be deployed in a communication network.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

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

[0017] Figure 2 is a schematic diagram of an exemplary architecture of a communication system provided according to an embodiment of the present disclosure.

[0018] Figure 3 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0019] Figure 4A is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0020] Figure 4B is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0021] Figure 4C is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0022] Figure 4D is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0023] Figure 4E is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0024] Figure 4F is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0025] Figure 5A is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0026] Figure 5B is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0027] Figure 5C is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0028] Figure 6 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0029] Figure 7A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0030] Figure 7B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0031] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0032] In a first aspect, embodiments of this disclosure provide a communication method. The method is performed by a first node. The method includes: sending first information to a second node, wherein the first information is used to register the first node with the second node; wherein the first node supports asynchronous communication.

[0033] In the above embodiments, the first node can register itself with the second node using first information. In this way, when the first node is deployed in the network, the second node can obtain and save the first node's information. Thus, other nodes in the network can discover and select the first node through the second node, finding the first node that supports asynchronous communication. This enables the network to support and implement asynchronous communication for services, improving network transmission efficiency and enhancing the transmission capacity and flexibility of the communication system.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, asynchronous communication may be delayed transmission of service signaling and / or service data.

[0035] In the above embodiments, asynchronous communication can delay the transmission of at least one of service signaling and service data. Thus, after the first node is registered with the second node, it can be used to implement asynchronous communication for signaling and / or data, improving the transmission capacity and flexibility of the communication system at the control plane, user plane, and data plane.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first node supporting asynchronous communication may have at least one of the following capabilities: the ability to store service signaling and / or service data; and the ability to transmit service signaling and / or service data.

[0037] In the above embodiments, the first node, when supporting asynchronous communication, can store and / or transmit service signaling and / or service data. Thus, in asynchronous communication, the first node can first store service signaling and / or service data, and then transmit the stored service signaling and / or service data to the corresponding network function and / or terminal after a certain period of time. In this way, the first node can achieve delayed transmission of service signaling and / or service data, improving the transmission capacity and flexibility of the communication system.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the first information may indicate the configuration file of the first node.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the configuration file may include at least one of the following: identification information of the first node; service types supported by the first node; type of the first node; identification information of the network where the first node is located; identification information related to network slices of the first node; addressing information of the first node; capability information of the first node; priority information of the first node; identification information of the network element set where the first node is located; identification information of the service set where the first node is located; service-specific authorization information of the first node; location information of the first node; location information of the services supported by the first node; load information of the first node; storage duration of the first node; AI support of the first node for asynchronous communication; and identification information of events subscribed by AF for asynchronous communication.

[0040] In the above embodiments, the first information used to register the first node may include one or more pieces of information related to the first node. Based on this information, the configuration file of the first node is stored in the second node. The first node can register with the second node. During the discovery and selection process of the first node by other nodes in the network, the second node can provide other nodes with a first node possessing corresponding parameters and / or capabilities based on various information in the first node's registration information. This ensures that a suitable first node is used to provide services, thereby ensuring the service performance of the services provided by the first node.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the service types supported by the first node may include at least one of the following: immersive communication, ultra-reliable low-latency communication, massive MIMO, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information of the first node may include at least one of the following: storage of service signaling; transmission of service signaling; storage of service data; transmission of service data; storage of model data; transmission of model data.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the priority information of the first node may include at least one of the following: priority related to service type; priority related to network; priority related to consumer; priority related to network status; and priority related to data.

[0044] In the above embodiments, the priority information of the first node can indicate priorities related to service type, network, consumer, network status, data, etc. The priority of the first node selected can differ in different scenarios. Thus, the priority information allows the first node determined by the second node to be more suitable for the corresponding scenario, thereby improving network efficiency.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first information may be carried in at least one of the following: a registration request message, wherein the first information indicates a new configuration file of the first node; an update request message, wherein the first information indicates an updated configuration file of the first node.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include: sending second information to a second node, wherein the second information is used to indicate that the first node is unavailable.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the second information may be carried in the deregistration request message.

[0048] In the above embodiments, the second information allows the first node to be set as unavailable in the second node. Thus, in scenarios such as maintenance of the first node or the first node leaving the network, the second node can omit the first node.

[0049] In a second aspect, embodiments of this disclosure provide a communication method. This method is executed by a second node. The method includes: receiving first information sent by a first node, wherein the first information is used to register the first node with the second node; wherein the first node supports asynchronous communication.

[0050] In the above embodiments, the first node can register itself with the second node using first information. In this way, when the first node is deployed in the network, the second node can obtain and save the first node's information. Thus, other nodes in the network can discover and select the first node through the second node, finding the first node that supports asynchronous communication. This enables the network to support and implement asynchronous communication for services, improving network transmission efficiency and enhancing the transmission capacity and flexibility of the communication system.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, asynchronous communication may be delayed transmission of service signaling and / or service data.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the first node supporting asynchronous communication may have at least one of the following capabilities: the ability to store service signaling and / or service data; and the ability to transmit service signaling and / or service data.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the first information may indicate the configuration file of the first node.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the configuration file may include at least one of the following: identification information of the first node; service types supported by the first node; type of the first node; identification information of the network where the first node is located; identification information related to network slices of the first node; addressing information of the first node; capability information of the first node; priority information of the first node; identification information of the network element set where the first node is located; identification information of the service set where the first node is located; service-specific authorization information of the first node; location information of the first node; location information of the services supported by the first node; load information of the first node; storage duration of the first node; AI support of the first node for asynchronous communication; and identification information of events subscribed by AF for asynchronous communication.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the service types supported by the first node may include at least one of the following: immersive communication, ultra-reliable low-latency communication, massive MIMO, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information of the first node may include at least one of the following: storage of service signaling; transmission of service signaling; storage of service data; transmission of service data; storage of model data; transmission of model data.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the priority information of the first node may include at least one of the following: priority related to service type; priority related to network; priority related to consumer; priority related to network status; and priority related to data.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the first information may be carried in at least one of the following: a registration request message, wherein the first information indicates a new configuration file of the first node; an update request message, wherein the first information indicates an updated configuration file of the first node.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: saving the configuration file of the first node.

[0060] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: receiving second information sent by the second node, wherein the second information is used to indicate that the first node is unavailable; and deleting the configuration file of the first node.

[0061] In conjunction with some embodiments of the second aspect, in some embodiments, the second information may be carried in the deregistration request message.

[0062] In a third aspect, embodiments of this disclosure provide a communication method. The method is applied to a communication system. The communication system includes a first node and a second node. The method includes: the first node sending first information to the second node, wherein the first information is used to register the first node with the second node; and wherein the first node supports asynchronous communication.

[0063] In a fourth aspect, embodiments of this disclosure provide a communication device. This communication device implements a first node. The communication device includes a transceiver module. The transceiver module is configured to send first information to a second node, wherein the first information is used to register the first node in the second node; wherein the first node supports asynchronous communication.

[0064] In conjunction with some embodiments of the fourth aspect, in some embodiments, asynchronous communication may be delayed transmission of service signaling and / or service data.

[0065] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first node supporting asynchronous communication may have at least one of the following capabilities: the ability to store service signaling and / or service data; and the ability to transmit service signaling and / or service data.

[0066] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information may indicate the configuration file of the first node.

[0067] In conjunction with some embodiments of the fourth aspect, in some embodiments, the configuration file may include at least one of the following: identification information of the first node; service types supported by the first node; type of the first node; identification information of the network where the first node is located; identification information related to network slices of the first node; addressing information of the first node; capability information of the first node; priority information of the first node; identification information of the network element set where the first node is located; identification information of the service set where the first node is located; service-specific authorization information of the first node; location information of the first node; location information of the services supported by the first node; load information of the first node; storage duration of the first node; AI support of the first node for asynchronous communication; and identification information of events subscribed by AF for asynchronous communication.

[0068] In conjunction with some embodiments of the fourth aspect, in some embodiments, the service types supported by the first node may include at least one of the following: immersive communication, ultra-reliable low-latency communication, massive MIMO, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing.

[0069] In conjunction with some embodiments of the fourth aspect, in some embodiments, the capability information of the first node may include at least one of the following: storage of service signaling; transmission of service signaling; storage of service data; transmission of service data; storage of model data; transmission of model data.

[0070] In conjunction with some embodiments of the fourth aspect, in some embodiments, the priority information of the first node may include at least one of the following: priority related to service type; priority related to network; priority related to consumer; priority related to network status; and priority related to data.

[0071] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information may be carried in at least one of the following: a registration request message, wherein the first information indicates a new configuration file of the first node; an update request message, wherein the first information indicates an updated configuration file of the first node.

[0072] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module may also be configured to: send second information to a second node, wherein the second information is used to indicate that the first node is unavailable.

[0073] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information may be carried in the deregistration request message.

[0074] In a fifth aspect, embodiments of this disclosure provide a communication device. This communication device implements a second node. The communication device includes a transceiver module. The transceiver module is configured to: receive first information sent by a first node, wherein the first information is used to register the first node in the second node; wherein the first node supports asynchronous communication.

[0075] In conjunction with some embodiments of the fifth aspect, in some embodiments, asynchronous communication may be delayed transmission of service signaling and / or service data.

[0076] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first node supporting asynchronous communication may have at least one of the following capabilities: the ability to store service signaling and / or service data; and the ability to transmit service signaling and / or service data.

[0077] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information may indicate the configuration file of the first node.

[0078] In conjunction with some embodiments of the fifth aspect, in some embodiments, the configuration file may include at least one of the following: identification information of the first node; service types supported by the first node; type of the first node; identification information of the network where the first node is located; identification information related to network slices of the first node; addressing information of the first node; capability information of the first node; priority information of the first node; identification information of the network element set where the first node is located; identification information of the service set where the first node is located; service-specific authorization information of the first node; location information of the first node; location information of the services supported by the first node; load information of the first node; storage duration of the first node; AI support of the first node for asynchronous communication; and identification information of events subscribed by AF for asynchronous communication.

[0079] In conjunction with some embodiments of the fifth aspect, in some embodiments, the service types supported by the first node may include at least one of the following: immersive communication, ultra-reliable low-latency communication, massive MIMO, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing.

[0080] In conjunction with some embodiments of the fifth aspect, in some embodiments, the capability information of the first node may include at least one of the following: storage of service signaling; transmission of service signaling; storage of service data; transmission of service data; storage of model data; transmission of model data.

[0081] In conjunction with some embodiments of the fifth aspect, in some embodiments, the priority information of the first node may include at least one of the following: priority related to service type; priority related to network; priority related to consumer; priority related to network status; and priority related to data.

[0082] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information may be carried in at least one of the following: a registration request message, wherein the first information indicates a new configuration file of the first node; an update request message, wherein the first information indicates an updated configuration file of the first node.

[0083] In conjunction with some embodiments of the fifth aspect, in some embodiments, the communication device described above may further include a processing module. The processing module is configured to: store the configuration file of the first node.

[0084] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may also be configured to: receive second information sent by the second node, wherein the second information is used to indicate that the first node is unavailable; the processing module may also be configured to: delete the configuration file of the first node.

[0085] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second information may be carried in the deregistration request message.

[0086] In a sixth aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first, second, and possible embodiments thereof.

[0087] In a seventh aspect, embodiments of this disclosure provide a communication system. The communication system includes a first node and a second node. The first node is configured to perform the communication method as described in any of the first aspect and its possible embodiments. The second node is configured to perform the communication method as described in any of the second aspect and its possible embodiments.

[0088] In an eighth aspect, embodiments of this disclosure provide a storage medium storing instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first, second, and possible embodiments thereof.

[0089] In a ninth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any of the first, second, and possible embodiments thereof.

[0090] In a tenth aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication methods described in any of the first, second, and possible implementations thereof.

[0091] In an eleventh aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in any of the first, second, and possible embodiments thereof.

[0092] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the methods provided 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.

[0093] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information processing method, and information transmission method can be used interchangeably; terms such as communication device, communication equipment, network equipment, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.

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

[0095] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various 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.

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

[0097] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "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.

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

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

[0100] 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 whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0101] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); 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, and C.

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

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

[0104] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

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

[0106] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0107] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0108] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "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," and "bandwidth part (BWP)" can be used interchangeably.

[0109] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "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", and "client" can be used interchangeably.

[0110] In some embodiments, access network devices, core network devices, or network devices can be replaced with 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 with 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, uplink link, downlink link, etc., can be replaced with sidelink link.

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

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

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

[0114] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0115] Figure 1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a first node 101 and a second node 102.

[0116] In some embodiments, the first node 101 may support asynchronous type communication (ATC) functionality.

[0117] In some embodiments, the first node 101 may be, for example, an ATC data repository (ATCDR).

[0118] In some embodiments, the first node 101 may be, for example, an ATC repository function (ATCRF).

[0119] In some embodiments, the first node 101 may be, for example, an ATC function (ATCF).

[0120] In some embodiments, the first node 101 may be, for example, an ATC buffering function (ATCBF).

[0121] In some embodiments, the second node 102 may be used to store network function (NF) profiles, provide NF discovery and selection services, etc.

[0122] In some embodiments, the second node 102 may be, for example, a network repository function (NRF).

[0123] In some embodiments, the first node 101 and the second node 102 can be deployed in the core network. For example, the first node 101 and the second node 102 can be deployed in a 5GS communication system, especially in a 5G core network (5GC). For example, the first node 101 and the second node 102 can be deployed in a 6GS communication system, especially in a 6G core network (6GC).

[0124] In some implementation sets, at least one of the first node 101 and the second node 102 may be located outside the core network.

[0125] In some embodiments, the terminal includes, but is not limited to, 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.

[0126] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, 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), radio 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 Wi-Fi system.

[0127] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0128] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0129] In some embodiments, the communication system 100 described above may be a 5G communication system or a 6G communication system. It should be noted that the communication system 100 may also be other communication systems, such as a 4G communication system, and this disclosure does not specifically limit it in this regard.

[0130] Figure 2 is an exemplary architecture diagram of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 2, the communication system 100 may include a first NF 201, a second NF 202, a third NF 203, a fourth NF 204, and a fifth NF 205.

[0131] In some embodiments, the first NF 201 may be a control plane network function, a user plane network function, or a data plane network function. In some embodiments, the second NF 202 and the third NF 203 may be control plane network functions. In some embodiments, the fourth NF 204 may be a user plane network function or a data plane network function. In some embodiments, the fifth NF 205 may be a network function in the core network or a network function deployed by a third party.

[0132] In some embodiments, the first NF 201 located on the control plane, user plane, or data plane may be the first node 101.

[0133] In some embodiments, the second NF 202 located on the control plane may be the second node 102.

[0134] In some embodiments, each of the first NF 201, the second NF 202, the third NF 203, the fourth NF 204, and the fifth NF 205 can provide services through a service-based interface.

[0135] In some embodiments, the communication system 100 may further include an access network device 206 and a terminal 207. The terminal 207 may communicate with the core network, for example, through the access network device 206.

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

[0137] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or some of the main components in the communication system 100, but are not limited thereto. The main components shown in FIG1 are illustrative. The communication system 100 may include all or some of the main components in FIG1, or may include other main components other than those in FIG1. ​​The number and form of each main component are arbitrary. Each main component may be physical or virtual. The connection relationship between the main components is illustrative. The main components 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.

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

[0139] Here, we will explain the important concepts involved in the disclosed embodiments.

[0140] 1. 6G Use Cases

[0141] Communication technology is evolving from 5G to 6G. For 6G communication systems, in addition to enhancements in system architecture and functionality, support for more use cases and scenarios has been proposed.

[0142] In some embodiments, the proposed use cases for 6G communication technology include: immersive communication, ultra-reliable low-latency communication, massive MIMO, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing.

[0143] In some embodiments, immersive communication is an extension of enhanced mobile broadband (eMBB) in 5G. Immersive communication covers use cases that provide users with rich, interactive video (immersive) experiences, including interactions with machine interfaces.

[0144] In some embodiments, immersive communication is used in a range of environments, including hotspots, towns, and rural areas, creating additional and new demands compared to eMBB in 5G.

[0145] In some embodiments, typical use cases for immersive communication include immersive extended reality (XR), remote multi-sensory presentation, and holographic communication. Supporting mixed data streams of video, audio, and other environmental data in a time-synchronized manner is an integral part of immersive communication, and also includes independent support for sound.

[0146] In some embodiments, across various environments, the ability to achieve enhanced spectral efficiency and a consistent service experience is critical, along with the need to balance higher data rates and greater mobility. Specific immersive communication use cases requiring responsive and precise interaction with real and virtual objects also need to support high reliability and low latency, as well as large system capacity for simultaneous connections of a large number of devices.

[0147] In some embodiments, the use cases for Hyper-Reliable and Low-Latency Communication (URLLC) extend the use cases of Ultra-Reliable and Low-Latency Communication (URLLC) in 5G. The use cases covered by URLLC are expected to have more stringent requirements in terms of reliability and latency. This is typically used for time synchronization operations, where failure to meet these requirements can lead to serious consequences for the application.

[0148] In some embodiments, typical use cases for ultra-reliable low-latency communication include communications for full automation, control, and operation in industrial environments. These communication types facilitate a variety of applications, such as machine interaction, emergency services, telemedicine, and monitoring of power transmission and distribution.

[0149] In some embodiments, use cases for ultra-reliable low-latency communication may require support for enhanced reliability and low latency, and depending on the use case, may also require precise location and connection density.

[0150] In some embodiments, massive communication is used in 5G for massive machine-type communication (mMTC). Massive communication involves connecting large-scale devices or sensors for a wide range of use cases and applications.

[0151] In some embodiments, typical use cases for large-scale communications include expansion and new applications in smart cities, transportation, logistics, health, energy, environmental monitoring, agriculture, and other areas where various IoT devices, either without batteries or with long-life batteries, are required.

[0152] In some embodiments, large-scale communication use cases may require support for high connection density, and depending on the use case, may also require different data rates, low power consumption, mobility, extended coverage, and high security and reliability.

[0153] In some embodiments, ubiquitous connectivity is used to improve connectivity and, more importantly, to bridge the digital divide. Connectivity can be improved, particularly through interoperability with other systems. A key focus of ubiquitous connectivity use cases is addressing currently uncovered or difficult-to-reach areas, especially rural, remote, and sparsely populated regions.

[0154] In some embodiments, typical use cases for ubiquitous connectivity include, but are not limited to, IoT and mobile broadband communications.

[0155] In some embodiments, the use cases of integrated artificial intelligence and communication can support distributed computing and artificial intelligence (AI) applications. Typical use cases for integrated artificial intelligence and communication include autonomous driving, automated collaboration between devices for assistive medical applications, the transfer of heavy computational operations across devices and networks, and the creation and prediction of digital twins.

[0156] In some embodiments, the use cases of integrated communications intelligence may require support for high regional traffic capacity and high data rates for user experience, as well as low latency and high reliability, depending on the specific use case. Beyond communications, the use cases of integrated communications intelligence are expected to include a range of new capabilities related to the integration of AI and computing functions, including the acquisition, preparation, and processing of data from different sources; distributed AI model training, model sharing, and distributed inference across international mobile telecommunications (IMT) systems; and the orchestration and linking of computing resources.

[0157] In some embodiments, integrated sensing and communication use cases facilitate new applications and services that require sensing capabilities. This helps provide wide-area, multi-dimensional sensing, providing spatial information about unconnected objects and connected devices, as well as their movement and surrounding environment.

[0158] In some embodiments, use cases for integrated communication and sensing include navigation, activity detection and motion tracking (e.g., gesture recognition, fall detection, vehicle / pedestrian detection), environmental monitoring (e.g., rain / pollutant detection), and providing sensing data / information related to the surrounding environment for use in AI, XR, and digital twin applications.

[0159] In some embodiments, along with the provided communication capabilities, the use cases of integrated communication and sensing need to support high-precision positioning and sensing-related capabilities, including range / rate / angle estimation, object and presence detection, positioning, imaging, and mapping.

[0160] It should be noted that each of the 6G use cases described above can also be considered a corresponding type of service. For example, the service in the immersive communication use case can be an immersive communication service. For example, the service in the ultra-reliable low-latency communication use case can be an ultra-reliable low-latency communication service. For example, the service in the massive MIMO use case can be a massive MIMO service. For example, the service in the ubiquitous connectivity use case can be a ubiquitous connectivity service. For example, the service in the integrated intelligent communication use case can be an integrated intelligent communication service. For example, the service in the integrated communication sensing use case can be an integrated communication sensing service.

[0161] 2. Asynchronous communication

[0162] Some communication information transmitted in a communication system may not have strict latency requirements or real-time processing requirements. In order to implement the transmission of this type of communication information in a targeted manner, the concept of asynchronous communication was proposed.

[0163] Asynchronous communication is designed to meet the service and communication requirements of communication systems. Asynchronous communication can be understood as a mechanism, feature, or function. It involves delaying the transmission of communication information. In some embodiments, when using asynchronous communication, the communication system, particularly the core network, can delay the transmission of communication information.

[0164] In some embodiments, when asynchronous communication is employed, the core network can store or buffer the communication information after acquiring it, and then transfer or synchronize the stored or buffered information at an appropriate time. For example, communication information from a specific network function to a terminal can use an asynchronous communication mechanism. The communication information from the network function can be stored in the core network after arriving at the core network, and the core network will then transmit the communication information to the terminal at an appropriate time. Similarly, communication information from one network function to another can use an asynchronous communication mechanism. The communication information from the former can be stored in the core network after arriving at the core network, and the core network will then transmit the communication information to the latter at an appropriate time. Thus, the asynchronous communication mechanism enables delayed transmission of communication information.

[0165] In some embodiments, asynchronous communication may target communication information that includes service signaling and / or service data. In one example, asynchronous communication may be applied to the transmission of service signaling. In another example, asynchronous communication may be applied to the transmission of service data.

[0166] For the core network to support asynchronous communication, at least some network functions within the core network need to have the capability to support asynchronous communication. Therefore, how to deploy network functions that support asynchronous communication within the network is a problem that urgently needs to be solved.

[0167] Figure 3 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to the communication system 100. As shown in Figure 3, the communication method of this embodiment includes steps S301 to S309.

[0168] In some embodiments, this disclosure relates to a first node 101 and a second node 102. In some embodiments, the first node 101 may be an ATCDR. In some embodiments, the second node 102 may be an NRF. It should be noted that the first node 101 and the second node 102 may also be other network functions, and this disclosure does not specifically limit them.

[0169] In step S301, the first node 101 sends the first information to the second node 102.

[0170] In some embodiments, the first node 101 may send first information. In some embodiments, the first information may be sent by the first node 101, but is not limited thereto, and may also be sent by other entities.

[0171] In some embodiments, the second node 102 may receive the first information. In some embodiments, the first information may be received by the second node 102, but is not limited thereto, and may also be received by other entities.

[0172] In some embodiments, when the first node 101 is deployed in the network, the first node 101 can register with the second node 102. The first node 101 registered with the second node 102 can be discovered and selected by other network functions.

[0173] In some embodiments, the first information may be used to register the first node 101 to the second node 102. In some embodiments, in order to register the first node 101 to the second node 102, the first information may be used to indicate the configuration file of the first node. In some embodiments, the first information may be used to provide the configuration file of the first node 101 to the second node 102. In some embodiments, the first information may be used to notify the second node 102 that the first node 101 has been deployed. In some embodiments, the first information may be used to instruct the second node 102 to notify other nodes that the first node 101 is available.

[0174] In some embodiments, the first node 101 may support asynchronous communication. In some embodiments, the first node 101 may have the capability or functionality for asynchronous communication.

[0175] In some embodiments, the first node 101 supporting asynchronous communication may have at least one of the following capabilities: the ability to store business information and the ability to transmit business information.

[0176] In some embodiments, service information may include at least one of the following: service signaling and service data. In some embodiments, service signaling may be service signaling in a first service employing asynchronous communication. For example, service signaling may be signaling on the control plane. In some embodiments, service data may be service data of a first service employing asynchronous communication. For example, service data may include data from at least one of the control plane, user plane, and data plane.

[0177] In some embodiments, storing service information may include storing service signaling and / or service data. In one example, the first node 101 may have the capability to store service signaling and / or service data provided to network functions and / or terminals. In one example, in asynchronous communication, the first node 101 may store service signaling and / or service data provided to network functions and / or terminals.

[0178] In some embodiments, transmitting service information may include transmitting service signaling and / or service data. In one example, the first node 101 may have the capability to trigger the transmission or synchronization of service signaling and / or service data to network functions and / or terminals. In one example, in asynchronous communication, the first node 101 may transmit or synchronize service signaling and / or service data to network functions and / or terminals.

[0179] In some embodiments, the first node 101 may be an instance of ATCDR, and the first information may be used to provide the profile of the ATCDR instance to the second node 102.

[0180] In some embodiments, the configuration file of the first node 101 may include at least one of the following: identification information of the first node 101; service types supported by the first node 101; type of the first node 101; identification information of the network where the first node 101 is located; identification information related to network slices of the first node 101; addressing information of the first node 101; capability information of the first node 101; priority information of the first node 101; identification information of the network element set where the first node 101 is located; identification information of the service set where the first node 101 is located; service-specific authorization information of the first node 101; location information of the first node 101; location information of the services supported by the first node 101; load information of the first node 101; storage duration of the first node 101; AI support of the first node 101 for asynchronous communication; and identification information of events subscribed to by the application function (AF) for asynchronous communication. In some embodiments, the first information may include some or all of the contents of the above configuration file of the first node 101.

[0181] In some embodiments, the identification information of the first node 101 can be used to identify the first node 101. In some embodiments, the identification information of the first node 101 may include the identifier of the first node 101. In some embodiments, the first node 101 may be an ATCDR instance, then the identification information of the first node 101 may include the identifier of the ATCDR instance.

[0182] In some embodiments, the first node 101 can support various service types. In some embodiments, the service types supported by the first node 101 may include at least one of the following: immersive communication, ultra-reliable low-latency communication, large-scale communication, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing. It should be noted that the first node 101 may also support other service types, but this disclosure does not specifically limit these types.

[0183] In some embodiments, the first node 101 may be of a different type.

[0184] In some embodiments, the type of the first node 101 may include a primary node, a secondary node, or a service node. In some embodiments, multiple first nodes 101 may be deployed in the network, and these first nodes 101 may form a hierarchical architecture. In one example, one of the multiple first nodes 101 may be a primary node, and the others may be secondary nodes. The primary node may be connected to one or more secondary nodes. In this case, the type of the first node 101 may be either a primary node or a secondary node. In some embodiments, the type of the first node 101 may be a service node. A first node 101 acting as a service node can provide services to one or more service areas. It is understood that a first node 101 acting as a primary node may be a service node, or a first node 101 acting as a secondary node may be a service node; conversely, a first node 101 acting as a service node may be either a primary node or a secondary node, and this disclosure does not specifically limit this.

[0185] In some embodiments, the type of the first node 101 can be classified according to the type of network it belongs to. For example, the type of the first node 101 may include: serving a public land mobile network (PLMN), serving a stand-alone non-public network, serving both a PLMN and an SNPN. In one example, one or more service areas served by the first node 101 may be located in a PLMN. In another example, one or more service areas served by the first node 101 may be located in an SNPN. In yet another example, one or more service areas served by the first node 101 may be partially located in a PLMN and partially located in an SNPN.

[0186] In some embodiments, the type of the first node 101 may include at least one of the following: the first node 101 supports a third-party device identifier, the first node 101 supports a device identifier assigned by an operator, the first node 101 supports both a third-party device identifier and an operator-assigned device identifier. In some embodiments, the device associated with asynchronous type communication may include operator equipment, third-party equipment, etc. In some embodiments, the device may be provided by a third party. In one example, the first node 101 may support a device provided by a third party. In some embodiments, the device identifier may be assigned by a third party. In one example, the first node 101 may support a device identifier assigned by a third party. In some embodiments, the device may be provided by an operator. In one example, the first node 101 may support a device provided by an operator. In some embodiments, the device identifier may be assigned by a third party. In one example, the first node 101 may support a device identifier assigned by an operator.

[0187] In some embodiments, where the first node 101 supports a third-party device identifier, the type of the first node 101 may include the third party supported by the first node 101. In one example, the configuration file of the first node 101 may include identification information of the third party supported by the first node 101.

[0188] In some embodiments, where the first node 101 supports a carrier's device identifier, the type of the first node 101 may include the carriers supported by the first node 101. In one example, the configuration file of the first node 101 may include identification information of the carriers supported by the first node 101.

[0189] In some embodiments, the type of the first node 101 can be classified according to the service types supported by the first node 101. In some embodiments, the first node 101 can support at least one of the following service types: immersive communication, ultra-reliable low-latency communication, massive MIMO, ubiquitous connectivity, integrated intelligent communication, and integrated intelligent communication sensing. In some embodiments, the type of the first node 101 can also be associated with a subtype within each service type. In one example, for immersive communication, the type of the first node 101 can further be one or more services such as XR, remote multi-sensory presentation, and holographic systems. In one example, for ultra-reliable low-latency communication, the type of the first node 101 can further be one or more services such as machine interaction, emergency services, and telemedicine. In one example, for massive MIMO, the type of the first node 101 can further be one or more services such as 6G IoT, intelligent agent machine interaction, emergency services, and telemedicine. In one example, for ubiquitous connectivity, the type of the first node 101 can further be one or more services such as non-3GPP connections, satellite connections, and mobile broadband communication. In one example, for integrated intelligent communication, the first node 101 can be further classified as supporting one or more of the following services: autonomous driving, automated collaboration between devices for medical assistance applications, transfer of heavy computational operations across devices and networks, and creation and prediction of digital twins. In another example, for integrated sensing communication, the first node 101 can be further classified as supporting one or more of the following services: navigation, activity detection and motion tracking, environmental monitoring, and provision of sensing data / information related to the surrounding environment.

[0190] In some embodiments, the identification information of the network where the first node 101 resides can be used to identify the network where the first node 101 resides. In one example, the first node 101 may be located in a PLMN, in which case the identification information of the network where the first node 101 resides may include the PLMN's identifier. In one example, the first node 101 may be located in an SNPN, in which case the identification information of the network where the first node 101 resides may include both the PLMN's identifier and the SNPN's identifier, or only the SNPN's identifier. In one example, the SNPN's identifier may be the SNPN's network identifier (NID).

[0191] In some embodiments, the network slice-related identification information of the first node 101 can be used to identify the network slice in which the first node 101 is located. In some embodiments, the network slice-related identification information may include at least one of the following: single network slice selection assistance information (S-NSSAI) and network slice instance identifier (NSI ID).

[0192] In some embodiments, the addressing information of the first node 101 can be used to enable addressing and communication with the first node 101. In some embodiments, the addressing information of the first node 101 may include at least one of the following: a fully qualified domain name (FQDN) or an Internet protocol (IP) address.

[0193] In some embodiments, the capability information of the first node 101 can be used to indicate the capabilities (or functions) of the first node 101. In some embodiments, the capability information of the first node 101 may include at least one of the following: storage of service signaling, transmission of service signaling, storage of service data, transmission of service data, storage of model data, and transmission of model data.

[0194] In some embodiments, in addition to business signaling and business data, the capability information of the first node 101 related to asynchronous communication may also include model data storage, model data transmission, etc. In some embodiments, the model may be a model that supports asynchronous communication. For example, the model type may be an AI model, a machine learning (ML) model, etc. In some embodiments, model data may include at least one of the following: data for model training, data for model inference, and data obtained based on model inference.

[0195] In some embodiments, the priority of the first node 101 can be used to determine the scenario in which the first node 101 is preferentially applied among multiple situations. It is understood that the first node 101 can have different priorities for multiple scenarios. This means that during the discovery and selection process of the first node 101, the first node 101 with the higher priority can be preferentially selected based on its priority.

[0196] In some embodiments, the priority information of the first node 101 may include at least one of the following: priority related to service type; priority related to network; priority related to consumer; priority related to network status; and priority related to data.

[0197] In some embodiments, priority can be related to service type. In some embodiments, the first node 101 can have the same or different priorities for different service types. For example, for the first node 101, the priority of the first service type is higher than the priority of the second service. Then, for the first service type, the first node 101 can be selected preferentially. For example, the first node 101 can be preferentially used to implement the service of the first service type. For example, the first service can be one of the following: immersive communication service, ultra-reliable low-latency communication service, large-scale communication service, ubiquitous connectivity service, integrated intelligent communication service, and integrated intelligent communication service; the second service can be another service among the following: immersive communication service, ultra-reliable low-latency communication service, large-scale communication service, ubiquitous connectivity service, integrated intelligent communication service, and integrated intelligent communication service.

[0198] In some embodiments, priority can be network-dependent. In some embodiments, the first node 101 can have the same or different priorities for PLMNs and SNPNs. For example, the priority of the first node 101 corresponding to the PLMN can be higher than its priority corresponding to the SNPN. For example, the priority of the first node 101 corresponding to the PLMN can be lower than its priority corresponding to the SNPN. In some embodiments, the first node 101 can have the same or different priorities among multiple PLMNs. In some embodiments, the first node 101 can have the same or different priorities among multiple SNPNs. For example, the first node 101 can be preferentially selected for networks with high priority. For example, the first node 101 can be preferentially used for networks with high priority.

[0199] In some embodiments, priority can be associated with a consumer. In some embodiments, the consumer (or consumer network function) can be a network exposure function (NEF) or a network function in the core network. For example, services employing asynchronous communication can be provided to network functions located outside the core network (e.g., AF). Since the network function outside the core network connects to the core network via the NEF, the consumer can be either the NEF or the AF. For example, if services employing asynchronous communication are provided to network functions located within the core network, then the consumer can be that network function. In some embodiments, consumers within the core network and consumers outside the core network can have the same or different priorities. For example, the priority of a consumer within the core network can be higher than the priority of a consumer outside the core network. For example, for consumers with high priority, the first node 101 can be preferentially selected. For example, the first node 101 can be preferentially used for consumers with high priority.

[0200] In some embodiments, priority may be related to network state. In some embodiments, network state may be used to reflect network load. In some embodiments, network state may include overload, high load, and low load. For example, for a load state with high priority, the first node 101 may be preferentially selected. For example, the first node 101 may be preferentially used for a load state with high priority. In one example, overload, high load, and low load may have the same or different priorities. In some embodiments, network state may include one or more congestion states. In one example, different congestion states may have the same or different priorities. For example, for a congestion state with high priority, the first node 101 may be preferentially selected. For example, the first node 101 may be preferentially used for a congestion state with high priority.

[0201] In some embodiments, priority may be data-related. In some embodiments, the data in asynchronous communication may include at least one of the following: terminal-related data, network function-related data, and service data. In one example, terminal-related data may include data from a terminal and / or data sent to a terminal. In one example, terminal-related data may include data from a network function and / or data sent to a network function. In one example, service data may be service-related data using asynchronous communication. The first node 101 may have the same or different priorities for different types of data. For example, if the first node 101 has a higher priority for terminal-related data than for network function-related data, then the first node 101 may be preferentially selected for terminal-related data. Conversely, if the first node 101 has a lower priority for terminal-related data than for network function-related data, then the first node 101 may be preferentially selected for network function-related data.

[0202] In some embodiments, the priority information of the first node 101 can be used to indicate the priority of the first node 101 in the process of processing asynchronous communication. In some embodiments, the priority information of the first node 101 may include at least one of the following: priority related to service type; priority related to network; priority related to consumer; priority related to network state; and priority related to data. In one example, the first node 101 can process asynchronous communication of each service type according to the priority related to service type. For example, the first node 101 can prioritize processing asynchronous communication of service types with high priority. In one example, the first node 101 can process asynchronous communication of each network according to the priority related to network. For example, the first node 101 can prioritize processing asynchronous communication of networks with high priority. In one example, the first node 101 can process asynchronous communication of each consumer according to the priority related to consumer. For example, the first node 101 can prioritize processing asynchronous communication of consumers with high priority. In one example, the first node 101 can process asynchronous communication of each network state according to the priority related to network state. For example, the first node 101 can prioritize the processing of asynchronous communication types with high-priority network states. In one example, the first node 101 can prioritize the processing of asynchronous communication types for each data type based on the priority associated with that data. For example, the first node 101 can prioritize the processing of asynchronous communication types for data with high-priority values.

[0203] In some embodiments, the identification information of the network element set to which the first node 101 belongs can be used to identify the network element set. In some embodiments, multiple first nodes 101 can be deployed in the same service area. These first nodes 101 can then constitute a network element set. In some embodiments, the first node 101 can be an ATCDR, which can belong to an ATCDR set. In this case, the identification information of the network element set can include the identifier of the ATCDR set.

[0204] In some embodiments, the identification information of the service set to which the first node 101 belongs can be used to identify the service set. The service set can be a collection of one or more first nodes 101 for a specific service type. For example, for a given service type, one or more first nodes 101 can be deployed, and these first nodes 101 can constitute a service set for that service type. In one example, if the service type is immersive communication, then all first nodes 101 in the service set to which the first node 101 belongs can be used to implement immersive communication services. In another example, if the service type is large-scale communication, then all first nodes 101 in the service set to which the first node 101 belongs can be used to implement large-scale communication services.

[0205] In some embodiments, service authorization information specific to the first node 101 can be used to identify specially authorized services. In some embodiments, certain services may require special authorization. The first node 101 can authorize and support these services. In some embodiments, the service authorization information may indicate immersive communication services. For example, the service authorization information may include a service identifier for the immersive communication service, thereby authorizing such immersive communication services. In some embodiments, the service authorization information may include service capabilities registered by the first node 101 in the PLMN and / or SNPN, or within the service area of ​​the PLMN and / or SNPN.

[0206] In some embodiments, the location information of the first node 101 can be used to indicate the location of the first node 101. In some embodiments, the location of the first node 101 can be determined based on the deployment of the first node 101. For example, the location information of the first node 101 can be determined by the operator during the deployment of the first node 101. In some embodiments, the type of location can include geographic location, administrative region location, or other types of region. In one example, the location can be a geographic location, then the location information of the first node 101 can include the geographic coordinates of the first node 101. For example, the location information can include at least one of the following: longitude value, latitude value, and altitude value. In one example, the location can be an administrative region location, then the location information of the first node 101 can include the region code of the administrative region where the first node 101 is located. In one example, the location can be represented by a data center, then the location information of the first node 101 can include the identifier or name of the data center to which the first node 101 belongs.

[0207] In some embodiments, the location information of the first node 101 may include a service area. In some embodiments, the service area may be indicated by geographic location, administrative region location, service area identifier, or other means.

[0208] In some embodiments, the location information of the first node 101 may include a priority list of service areas. In some embodiments, multiple service areas may have the same or different priorities. The location information of the first node 101 may include a priority list, which may include the priority values ​​of these service areas. In one example, a service area with a higher priority may correspond to a lower priority value; a service area with a lower priority may correspond to a higher priority value.

[0209] In some embodiments, the location information may further include network functions that communicate directly or indirectly with the first node 101. In some embodiments, the location information may also indicate the location of one or more other network functions. These network functions may communicate directly or indirectly with the first node 101.

[0210] In some embodiments, the location information of the service supported by the first node 101 can be used to indicate the location of the service supported by the first node 101. In some embodiments, the location information may include at least one of the following: cell identifier and tracking area identifier. In one example, the location information may include one or more cell identifiers. These cell identifiers can be used to identify the cell supported by the service for which the first node 101 supports. In one example, the location information may include one or more tracking area identifiers (TAIs). These cell identifiers can be used to identify the tracking area supported by the service for which the first node 101 supports. In some embodiments, the location information may include the identifier of a specific area. For example, the location information may include the identifier of a campus, industrial park, port, office building, etc.

[0211] In some embodiments, the load information of the first node 101 can be used to indicate the load of the first node 101. In some embodiments, the load information can indicate the load status, such as overload, high load, low load, etc. In some embodiments, the load information can indicate the congestion status, such as congested, not congested, etc. In some embodiments, the load information can indicate a time window associated with the first node 101. For example, the time window can be a time window in which the first node 101 is under low load or not congested. For example, the time window can be a time window in which the first node 101 is in an available state.

[0212] In some embodiments, asynchronous communication on the first node 101 can be enabled or activated. Conversely, asynchronous communication on the first node 101 can be disabled or inactivated. When asynchronous communication is enabled or activated, the first node 101 can implement the functions of asynchronous communication, including at least one of the following: storage and / or transmission of service signaling, storage and / or transmission of service data, and storage and / or transmission of model data. In some embodiments, the storage duration of the first node 101 can refer to the storage duration of service signaling, service data, model data, etc., on the first node 101.

[0213] In some embodiments, the storage duration of the first node 101 can be a maximum duration. In other words, the storage duration of the first node 101 indicated in the configuration file can be the maximum duration for which the first node 101 stores service signaling, service data, model data, etc. In some embodiments, the storage duration of the first node 101 can be a preset duration. In other words, the storage duration of the first node 101 indicated in the configuration file can be a preset duration for which the first node 101 stores service signaling, service data, model data, etc.

[0214] In some embodiments, the storage duration of the first node 101 may be the same or different depending on the situation. In some embodiments, the first node 101 may have the same or different storage durations for service signaling, service data, and model data. For example, the storage duration of the first node 101 for service signaling may be less than the storage duration for service data. For example, the storage duration of the first node 101 for service data and the storage duration for model data may be the same. In some embodiments, the first node 101 may have the same or different storage durations for different service types. For example, the storage duration of the first node 101 for large-scale communication service types may be greater than the storage duration for immersive communication service types. For example, the storage duration of the first node 101 for communication intelligence integration service types and the storage duration for communication sensing integration service types may be the same. In some embodiments, the first node 101 may have the same or different storage durations for different data transmission targets. For example, the storage duration of the first node 101 for data sent to terminals may be greater than the storage duration for data sent to network functions.

[0215] In some embodiments, the configuration file of the first node 101 may include AI support for the first node 101. In some embodiments, the first node 101 may support AI technology for asynchronous communication. For example, the first node 101 may support model training, model inference, and other processing based on AI / ML models. In some embodiments, the first node 101 may or may not support asynchronous communication using AI technology. In some embodiments, the configuration file of the first node 101 may include an identifier list, which may include identifiers of the first node 101 that support AI technology for asynchronous communication.

[0216] In some embodiments, AI support for the first node 101 may include supporting AI-based analysis for determining the first node 101. In some embodiments, the configuration file of the first node 101 may include indication information that instructs the first node 101 to support AI-based analysis for self-discovery and selection. In some embodiments, AI support for the first node 101 may include supporting AI-based analysis for storage. In some embodiments, the configuration file of the first node 101 may include indication information that instructs the first node 101 to support AI-based analysis for storing at least one of business signaling, business data, and model data.

[0217] In some embodiments, the AI ​​support of the first node 101 may include its own priority for AI technology applications. In some embodiments, the configuration file of the first node 101 may include a priority list. The priority list may include the priority of each first node 101 for implementing asynchronous communication based on AI technology. For example, in the case of implementing asynchronous communication using AI technology, the first node 101 with higher priority may be selected first. In some embodiments, the priority list may be obtained based on AI functionality.

[0218] In some embodiments, the configuration file of the first node 101 may include identification information of events subscribed to by the AF for asynchronous communication. For example, the event identification information may include an event ID. In some embodiments, this identification information may be used to represent events of asynchronous communication subscribed to by the AF. In some embodiments, the asynchronous communication-related events subscribed to by the AF may be diverse in different services or application scenarios. In one example, for an immersive communication service, the AF providing the immersive communication service may subscribe to corresponding events from the first node 101 through the event ID, such as the storage of multimedia data in the immersive communication service, the start of transmission of stored multimedia data to the corresponding terminal, the amount of stored multimedia data reaching a preset value, etc. In one example, when the AF requests to establish a session for an immersive communication service using asynchronous communication, it may send the event ID of the event subscribed to for asynchronous communication to the first node 101 through NEF or directly. Subsequently, during the execution of the asynchronous communication function by the first node 101, if it is determined that the event identified by the event ID has been triggered, the first node 101 may send a notification to the AF to indicate that the event has occurred.

[0219] In some embodiments, the AF can be an agent AF. In some embodiments, the agent AF can reside in a PLMN or SNPN network. In some embodiments, the agent AF can communicate with the AF and can be used to implement at least some of the functions of the AF. In some embodiments, the agent AF can be deployed by an operator or by a third party (e.g., an application provider).

[0220] In some embodiments, the configuration file of the first node 101 may be determined based on operator policies and / or OAM configuration. In some embodiments, the configuration file of the first node 101 may be determined by the operator. In one example, during the operator's deployment of the first node 101, the configuration file of the first node 101 may be determined based on operator policies. In some embodiments, the configuration file of the first node 101 may be determined by the Operations Administration and Management (OAM) function. In some embodiments, when the first node 101 is deployed to the network, OAM may provide the configuration file to the first node 101. In some embodiments, when the first node 101 is deployed to the network, the first node 101 may determine its own configuration file according to the OAM configuration.

[0221] In some embodiments, the first information may be carried in the registration request message. In some embodiments, when the first node 101 is deployed, the first node 101 may send a registration request message to the second node 102 to register the first node 101 with the second node 102. In some embodiments, when the first node 101 becomes operational for the first time, the first node 101 may send a registration request message to the second node 102 to register the first node 101 with the second node 102. The registration request message may include the first information. It is understood that the first information in the registration request message at this time may indicate a new configuration file for the first node.

[0222] In some embodiments, the registration request message may be an Nnrf_NFManagement_NFRegister request message.

[0223] In step S302, the second node 102 stores the configuration file of the first node 101.

[0224] In some embodiments, the second node 102 may obtain the configuration file of the first node 101 from the first information and store the configuration file of the first node 101.

[0225] In some embodiments, the second node 102 may mark the first node 101 as available. In some embodiments, the second node 102 may mark the first node 101 as having service support available.

[0226] In step S303, the second node 102 sends a response message to the first node 101.

[0227] In some embodiments, the second node 102 may send a response message. In some embodiments, the response message may be sent by the second node 102, but is not limited to this; it may also be sent by other entities.

[0228] In some embodiments, the first node 101 may receive a response message. In some embodiments, the response message may be received by the first node 101, but is not limited thereto, and may also be received by other entities.

[0229] In some embodiments, the response message may be sent by the second node 102 if the second node 102 stores the configuration file of the first node 101 and marks the first node 101 as available. In some embodiments, the response message may be used to indicate acceptance of the registration of the first node 101.

[0230] In some embodiments, the response message may be a registration response message to a registration request message. In some embodiments, the registration response message may be an Nnrf_NFManagement_NFRegister response message.

[0231] Through steps S301 to S303 above, the first node 101 can be registered on the second node 102. Thus, the second node 102 can obtain and store the configuration file of the first node 101.

[0232] In step S304, the first node 101 sends the first information to the second node 102.

[0233] The optional implementation of step S304 can be found in the optional implementation of step S301 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0234] In some embodiments, the first information may be used to provide an updated configuration file for the first node 101.

[0235] In some embodiments, the first node 101 may be triggered to provide an updated configuration file to the second node 102. In some embodiments, the updated configuration file may be provided by an OAM system. For example, the OAM system may provide a new or updated configuration file to the first node 101. In this case, the first node 101 may send first information to the second node 102. In some embodiments, the first node 101 may receive a status monitoring report from another node and send first information based on the status monitoring report. In some embodiments, the first node 101 may determine to send first information on its own. In some embodiments, the first node 101 may determine to send first information taking into account AI-assisted information.

[0236] In some embodiments, the content of the updated configuration file of the first node 101 may be the same as or different from the content of the configuration file of the first node 101 stored in the second node 102. For example, the updated configuration file of the first node 101 may include newly added configuration content. For example, the updated configuration file of the first node 101 may include changes to previously configured content. For example, the updated configuration file of the first node 101 may include deletions of previously configured content.

[0237] In some embodiments, the updated configuration file may include at least one of the following: identification information of the first node 101; service types supported by the first node 101; type of the first node 101; identification information of the network where the first node 101 is located; identification information related to network slices of the first node 101; addressing information of the first node 101; capability information of the first node 101; priority information of the first node 101; identification information of the network element set where the first node 101 is located; identification information of the service set where the first node 101 is located; service-specific authorization information of the first node 101; location information of the first node 101; location information of the services supported by the first node 101; load information of the first node 101; storage duration of the first node 101; AI support of the first node 101 for asynchronous communication; and identification information of events subscribed by AF for asynchronous communication.

[0238] In some embodiments, the first information may include the entire contents of the configuration file of the first node 101. In some embodiments, the first information may include only the parts of the configuration file of the first node 101 that have changed.

[0239] In some embodiments, the first information may be carried in the update request message. In some embodiments, the first node 101 may send an update request message to the second node 102 to update the configuration file of the first node 101. The update request message may include the first information. It is understood that the first information in the update request message at this time may indicate the updated configuration file of the first node.

[0240] In step S305, the second node 102 updates the configuration file of the first node 101.

[0241] In some embodiments, the second node 102 can update the configuration file of the first node 101 based on the first information. In some embodiments, the second node 102 can obtain and store the updated configuration file from the first information.

[0242] In step S306, the second node 102 sends a response message to the first node 101.

[0243] The optional implementation of step S306 can be found in the optional implementation of step S303 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0244] In some embodiments, the response message may be an update response message to an update request message. In some embodiments, the update response message may be an Nnrf_NFManagement_NFUpdate response message.

[0245] Through steps S304 to S306 above, the configuration file of the first node 101 on the second node 102 can be updated. Thus, the second node 102 can obtain and store the updated configuration file of the first node 101.

[0246] In step S307, the first node 101 sends the second information to the second node 102.

[0247] In some embodiments, the first node 101 may send second information. In some embodiments, the second information may be sent by the first node 101, but is not limited thereto, and may also be sent by other entities.

[0248] In some embodiments, the second node 102 may receive the second information. In some embodiments, the second information may be received by the second node 102, but is not limited thereto, and may also be received by other entities.

[0249] In some embodiments, when the first node 101 is disconnected from the network, the first node 101 can register with the second node 102. For example, the first node 101 can be shut down. For example, the first node 101 can disconnect from the network. When the first node 101 is disconnected from the network, the first node 101 becomes unavailable.

[0250] In some embodiments, the second information may be used to indicate that the first node 101 is unavailable. In some embodiments, the second information may be used to instruct the second node 102 to delete the configuration file of the first node 101. In some embodiments, the second information may be used to instruct the second node 102 to mark the configuration file of the first node 101 as unavailable. In some embodiments, the second information may be used to instruct the second node 102 to notify other nodes that the first node 101 is unavailable.

[0251] In some embodiments, the second information may be carried in the deregistration request message. In some embodiments, the deregistration request message may be used to request the first node 101 to deregister from the second node 102.

[0252] In some embodiments, the deregistration request message may be an Nnrf_NFManagement_NFDeregister request message.

[0253] In step S308, the second node 102 determines that the first node 101 is unavailable.

[0254] In some embodiments, upon receiving the second information, the second node 102 may determine that the first node 101 is unavailable.

[0255] In some embodiments, the second node 102 may mark the first node 101 as unavailable.

[0256] In some embodiments, the second node 102 may delete the configuration file of the first node 101 according to the management policy of the first node 101. In other words, the second node 102 may no longer store the unusable configuration file of the first node 101.

[0257] In step S309, the second node 102 sends a response message to the first node 101.

[0258] In some embodiments, the second node 102 may send a response message. In some embodiments, the response message may be sent by the second node 102, but is not limited to this; it may also be sent by other entities.

[0259] In some embodiments, the first node 101 may receive a response message. In some embodiments, the response message may be received by the first node 101, but is not limited thereto, and may also be received by other entities.

[0260] In some embodiments, the response message may be sent by the second node 102 if the second node 102 marks the first node 101 as unavailable. In some embodiments, the response message may be used to indicate acceptance of the first node 101's deregistration.

[0261] In some embodiments, the response message may be a deregistration response message to a deregistration request message. In some embodiments, the registration response message may be an Nnrf_NFManagement_NFDeregister response message.

[0262] Through steps S307 to S309 above, the first node 101 can be deregistered with the second node 102. Thus, the second node 102 can mark the first node 101 as unavailable. The first node 101 will no longer be used to provide services in the network.

[0263] The communication method of this embodiment can be implemented through steps S301 to S309.

[0264] In some embodiments, the first node 101 may register with the second node 102, and the second node 102 may obtain and store the configuration file of the first node 101.

[0265] In some embodiments, referring to system 100 shown in FIG2, first node 101 may be first NF 201, and second node 102 may be second NF 202. Fifth NF 205 may send a request to implement asynchronous communication. Third NF 203 may determine policies and / or rules for services employing asynchronous communication based on the request from fifth NF 205. Fifth NF 205 or third NF 203 may send a request to second NF 202 to realize the discovery and selection of first NF 201. Through the discovery and selection process, fifth NF 205 or third NF 203 may determine first NF 201 and send a message to first NF 201. First NF 201 may implement asynchronous communication based on the message from fifth NF 205 or third NF 203.

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

[0267] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0268] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0269] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0270] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0271] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0272] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0273] In some embodiments, the terms "service", "business", and "traffic" can be used interchangeably.

[0274] The communication method involved in the embodiments of this disclosure may include at least one of steps S301 to S309. For example, step S301 may be implemented as a standalone embodiment, step S304 may be implemented as a standalone embodiment, the combination of steps S301 and S302 may be implemented as a standalone embodiment, and the combination of steps S304 and S305 may be implemented as a standalone embodiment, but is not limited thereto.

[0275] In some embodiments, steps S302, S303, S304, S305, S306, S307, S308, and S309 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S301, S302, S303, S305, S306, S307, S308, and S309 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0276] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0277] Figure 4A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4A, the method includes steps S4101 and S4102.

[0278] In step S4101, the first node 101 sends the first information to the second node 102.

[0279] The optional implementations of step S4101 can be found in the optional implementations of steps S301 and S304 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0280] In step S4102, the second node 102 sends a response message to the first node 101.

[0281] The optional implementations of step S4102 can be found in the optional implementations of steps S303 and S306 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0282] Figure 4B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4B, the method includes steps S4201 and S4203.

[0283] In step S4201, the first node 101 sends the first information to the second node 102.

[0284] The optional implementation of step S4201 can be found in the optional implementation of step S301 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0285] In step S4202, the second node 102 stores the configuration file.

[0286] The optional implementation of step S4202 can be found in the optional implementation of step S302 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0287] In step S4203, the second node 102 sends a response message to the first node 101.

[0288] The optional implementation of step S4203 can be found in the optional implementation of step S303 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0289] Figure 4C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4C, the method includes steps S4301 and S4303.

[0290] In step S4301, the first node 101 sends the first information to the second node 102.

[0291] The optional implementation of step S4301 can be found in the optional implementation of step S304 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0292] In step S4302, the second node 102 updates the configuration file.

[0293] The optional implementation of step S4302 can be found in the optional implementation of step S305 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0294] In step S4303, the second node 102 sends a response message to the first node 101.

[0295] The optional implementation of step S4303 can be found in the optional implementation of step S306 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0296] Figure 4D is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4D, the method includes steps S4401 and S4403.

[0297] In step S4401, the first node 101 sends the second information to the second node 102.

[0298] The optional implementation of step S4401 can be found in the optional implementation of step S307 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0299] In step S4402, the second node 102 determines that the first node is unavailable.

[0300] The optional implementation of step S4402 can be found in the optional implementation of step S308 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0301] In step S4403, the second node 102 sends a response message to the first node 101.

[0302] The optional implementation of step S4403 can be found in the optional implementation of step S309 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0303] Figure 4E is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4E, the method includes steps S4501 and S4502.

[0304] In step S4501, the first node 101 sends the first information to the second node 102.

[0305] The optional implementations of step S4501 can be found in the optional implementations of steps S301 and S304 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0306] In step S4502, the first node 101 sends the second information to the second node 102.

[0307] The optional implementation of step S4502 can be found in the optional implementation of step S307 in Figure 3, as well as other related parts in the embodiments involved in Figure 3, which will not be repeated here.

[0308] Figure 4F is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4F, the method includes step S4601.

[0309] In step S4601, the first node 101 sends the first information to the second node 102.

[0310] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0311] In the following, the technical solutions of the embodiments of this disclosure will be described by way of specific implementation.

[0312] This disclosure proposes support for asynchronous communication to enable large-scale data processing in 6G, particularly for service data (or communication information) that does not have strict latency requirements or instant processing requirements.

[0313] In some embodiments, ATCDR to NRF (i.e., second node) is implemented through the configuration file of ATCDR (i.e., first node) to support 6G communication services. For example, a suitable NF is found to cache and / or store service signaling and / or service data and / or service sessions to support ATC features.

[0314] In some embodiments, the ATC in 6G instructs the 6GC to perform delayed synchronization of service signaling and / or service data for the NF or UE. For 6GS (e.g., 6GC NF and UE), the ATC is optional.

[0315] In some embodiments, 6GC supports asynchronous communication, for example, activated asynchronous communication includes at least one of the following functions: (1) the ability to store service signaling and / or service data provided to the NF or UE, wherein the ATCDR is used to store the service signaling and / or service data of the ATC; (2) the ability to trigger the transmission and / or synchronization of service signaling and / or service data to the forwarding NF or UE, wherein the ATCDR is used to transmit and / or synchronize the service signaling and / or service data of the ATC.

[0316] In some embodiments, the ATCDR profile registered in the NRF includes at least one of the following:

[0317] -ATCDR instance identifier;

[0318] - Signaling and / or data for the service types supported by ATC, and the type or name of the 6G service supported by ATCDR, including at least one of the following:

[0319] - Immersive communication, such as high-definition map data related to business positioning;

[0320] - Ultra-reliable low-latency communication;

[0321] - Massive communications, such as 6G IoT, AIoT service requests including inventory and / or commands;

[0322] - Ubiquitous connectivity, such as transmission over non-terrestrial networks (NTNs) outside the coverage area;

[0323] - Integrated communication intelligence, for example, providing non-real-time AI models;

[0324] - Integrated communication and sensing, for example, updating sensing reports;

[0325] -ATCDR type, for example:

[0326] - The primary ATCDR, or an ATCDR that provides services to one or more service areas of a PLMN or SNPN;

[0327] - Alternatively, ATCDR supports third-party identification devices / operator-assigned devices / or both;

[0328] -ATCDR supports all service types, or one or more services;

[0329] - PLMN ID in the case of PLMN, and PLMN ID and NID in the case of SNPN;

[0330] - Network slice related identifiers, such as S-NSSAI, NSI ID;

[0331] -ATCDR's FQDN or IP address;

[0332] -ATCDR capability information:

[0333] - The types of information cached / stored to support ATC features, such as business signaling, and / or business data, and / or general model data;

[0334] -ATCDR priority information, for example:

[0335] - ATCDR priority for different service types;

[0336] - Different PLMNs or SNPNs prioritize ATCDR for MC services;

[0337] - Consumer's ATCDR priority information, such as NEF or local NEF;

[0338] - ATCDR priority for different network states, such as load or congestion status;

[0339] -ATCDR priority for UE data, NF data, or service data;

[0340] -ATCDR set identifier: More than one ATCDR deployed in the same service area is considered as a set;

[0341] - The ATCDR service set ID of the ATCDR service instance, if the ATCDR set is deployed based on service type;

[0342] -ATCDR dedicated service authorization information, including services that can be authorized and supported by ATCDR, and the service capabilities registered with ATCDR in PLMN or SNPN, or in the service area of ​​PLMN or SNPN;

[0343] - Location information of the ATCDR, such as the service areas supported by the ATCDR, the priority values ​​or lists of service areas, and the location information of the NFs it communicates with.

[0344] -ATCDR supports the cell ID, TAI, or campus ID for the services it supports;

[0345] -ATCDR load information, such as load or congestion status;

[0346] - The lifetime of signaling and / or signaling storage when ATC is enabled by ATCDR;

[0347] - AI-supported ATCDR IDs for ATC features, such as AI-based ATCDR selection or data storage, and / or priority lists for AI / ML functions;

[0348] - The agent AF provides the event ID for ATC-supported subscriptions.

[0349] Figure 5A is an interactive schematic diagram of an exemplary embodiment of the communication method provided according to an embodiment of the present disclosure. This embodiment relates to an ATCDR registration process. As shown in Figure 5A, the communication method includes steps S5101 to S5103.

[0350] In step S5101, when the ATCDR service first becomes operational, the ATCDR (i.e., the ATCDR instance) sends an Nnrf_NFManagement_NFRegister request message to the NRF to notify the NRF about the ATCDR configuration file of the ATCDR.

[0351] In some embodiments, the provided ATCDR configuration file is as described above.

[0352] In step S5102, the NRF stores the ATCDR configuration file for ATCDR and marks ATCDR service support as available.

[0353] In step S5103, the NRF learns that the ATCDR registration has been accepted through the Nnrf_NFManagement_NFRegister response message.

[0354] Figure 5B is an interactive schematic diagram of an exemplary embodiment of the communication method provided according to an embodiment of the present disclosure. This embodiment relates to an ATCDR configuration file update process. As shown in Figure 5B, the communication method includes steps S5201 to S5203.

[0355] In step S5201, the ATCDR (i.e., the ATCDR instance) sends an Nnrf_NFManagement_NFUpdate request message (updated ATCDR profile) to the NRF to notify the NRF of the updated MCF profile of the ATCDR (e.g., its update capability). In some embodiments, this may be triggered by the OAM system, or by a received status monitoring report or internal determination, for example, taking into account AI-assisted information.

[0356] In step S5202, NRF updates and stores the ATCDR configuration file.

[0357] In step S5203, the NRF learns that the ATCDR update has been accepted through the Nnrf_NFManagement_NFUpdate response message.

[0358] Figure 5C is an interactive schematic diagram of an exemplary embodiment of the communication method provided according to an embodiment of the present disclosure. This embodiment relates to an ATCDR deregistration process. As shown in Figure 5C, the communication method includes steps S5301 to S5303.

[0359] In step S5301, when the ATCDR is about to be gracefully shut down or disconnected from the network, the ATCDR (i.e., the ATCDR instance) sends an Nnrf_NFManagement_NFDeregister request message to the NRF to notify the NRF of the ATCDR's unavailability.

[0360] In step S5302, the NRF marks the ATCDR as unavailable. In some embodiments, the NRF may remove the ATCDR configuration file according to the ATCDR management policy.

[0361] In step S5303, the NRF learns that the ATCDR deregistration has been accepted through the Nnrf_NFManagement_NFDeregister response message.

[0362] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0363] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus including units or modules for implementing the steps performed by the first node in any of the above methods. Furthermore, another apparatus is proposed, including units or modules for implementing the steps performed by the second node in any of the above methods.

[0364] 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 a configuration file, 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.

[0365] 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, microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or 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 by an application-specific integrated circuit (ASIC) or a programmable logic device, 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), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

[0366] Figure 6 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 6, the communication device 600 may include at least one of the following: a transceiver module 601 and a processing module 602.

[0367] In some embodiments, the communication device 600 may be a first node 101. In some embodiments, the transceiver module 601 may be configured to send first information to a second node, wherein the first information is used to register the first node in the second node; wherein the first node supports asynchronous communication. Optionally, the transceiver module 601 may be used to perform at least one of the communication steps (e.g., steps S301, S303, S304, S306, S307, S309, but not limited thereto) performed by the first node 101 in any of the above methods, which will not be elaborated here.

[0368] In some embodiments, the communication device 600 may be a second node 102. In some embodiments, the transceiver module 601 may be configured to: receive first information sent by a first node, wherein the first information is used to register the first node in the second node; wherein the first node supports asynchronous communication. Optionally, the transceiver module 601 may be used to perform at least one of the communication steps (e.g., steps S301, S303, S304, S306, S307, S309, but not limited thereto) performed by the second node 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module 602 may be used to perform at least one of the other steps (e.g., steps S302, S305, S308, but not limited thereto) performed by the second node 102 in any of the above methods, which will not be elaborated here.

[0369] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting and receiving modules may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0370] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0371] Figure 7A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 7100 can be a terminal (e.g., a user equipment), a network device (e.g., a core network device, an access network device), a chip, chip system, or processor that supports the implementation of any of the above methods by the MC device, a chip, chip system, or processor that supports the implementation of any of the above methods by the terminal, or a chip, chip system, or processor that supports the implementation of any of the above methods by the network device. The communication device 7100 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.

[0372] As shown in Figure 7A, the communication device 7100 includes one or more processors 7101. The processor 7101 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. Optionally, the communication device 7100 can be used to execute any of the above methods. Optionally, one or more processors 7101 can be used to invoke instructions to cause the communication device 7100 to execute any of the above methods.

[0373] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceivers 7102 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S301, S303, S304, S306, S307, S309, but not limited thereto), and the processor 7101 performs at least one of other steps (e.g., steps S302, S305, S308, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0374] In some embodiments, the communication device 7100 further includes one or more memories 7103 for storing data. Optionally, all or part of the memories 7103 may be located outside the communication device 7100. In optional embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuits 7104 are connected to the memories 7103 and can be used to receive data from the memories 7103 or other devices, and to send data to the memories 7103 or other devices. For example, the interface circuits 7104 can read data stored in the memories 7103 and send the data to the processor 7101.

[0375] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7A. 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.; (6) others, etc.

[0376] Figure 7B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the chip 7200 shown in Figure 7B, but it is not limited thereto.

[0377] Chip 7200 includes one or more processors 7201. Chip 7200 is used to perform any of the above methods.

[0378] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Optionally, all or part of the memories 7203 may be located outside chip 7200. Optionally, interface circuit 7202 is connected to memory 7203, and interface circuit 7202 can be used to receive data from memory 7203 or other devices, and interface circuit 7202 can be used to send data to memory 7203 or other devices. For example, interface circuit 7202 can read data stored in memory 7203 and send the data to processor 7201.

[0379] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S301, S303, S304, S306, S307, S309, but not limited thereto). The interface circuit 7202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 7202 performing data interaction between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of other steps (e.g., steps S302, S305, S308, but not limited thereto).

[0380] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0381] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 7100, cause the communication device 7100 to perform any of the methods described above. 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.

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

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

[0384] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only.

[0385] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

A communication method performed by a first node, wherein The method includes: Send first information to the second node, wherein the first information is used to register the first node in the second node; The first node supports asynchronous communication. The method of claim 1, wherein, The asynchronous type of communication refers to the delayed transmission of service signaling and / or service data. The method according to claim 1 or 2, wherein, The first node supporting asynchronous communication has at least one of the following capabilities: The ability to store business signaling and / or business data; The ability to transmit service signaling and / or service data. The method of any one of claims 1 to 3, wherein, The first information indicates the configuration file of the first node. The method of claim 4, wherein, The configuration file includes at least one of the following: The identification information of the first node; The first node supports the following service types; The type of the first node; The identification information of the network where the first node is located; The identification information related to the network slice of the first node; The addressing information of the first node; The capability information of the first node; The priority information of the first node; The identification information of the network element set to which the first node is located; The identification information of the service set to which the first node belongs; The specific business authorization information of the first node; The location information of the first node; The location information of the services supported by the first node; Load information of the first node; The storage duration of the first node; The first node supports AI for asynchronous communication. Application Functionality (AF) identifies the events subscribed to for asynchronous communication. The method of claim 5, wherein, The first node supports at least one of the following service types: immersive communication, ultra-reliable low-latency communication, large-scale communication, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing. The method according to claim 5 or 6, wherein The capability information of the first node includes at least one of the following: Storage of business signaling; Transmission of service signaling; Storage of business data; Transmission of business data; Storage of model data; Transmission of model data. The method of any one of claims 5 to 7, wherein, The priority information of the first node includes at least one of the following: Priorities related to business type; Network-related priorities; Priorities related to consumers; Priorities related to network status; Data-related priorities. The method of any one of claims 4 to 8, wherein, The first information is carried in at least one of the following: A registration request message, wherein the first information indicates a new configuration file for the first node; An update request message, wherein the first information indicates the updated configuration file of the first node. The method of any one of claims 1 to 9, wherein, The method further includes: Send a second message to the second node, wherein the second message is used to indicate that the first node is unavailable. The method of claim 10, wherein, The second information is carried in the registration request message. A communication method, performed by a second node, wherein The method includes: Receive first information sent by the first node, wherein the first information is used to register the first node in the second node; The first node supports asynchronous communication. The method of claim 12, wherein, The asynchronous type of communication refers to the delayed transmission of service signaling and / or service data. The method according to claim 12 or 13, wherein The first node supporting asynchronous communication has at least one of the following capabilities: The ability to store business signaling and / or business data; The ability to transmit service signaling and / or service data. The method according to any one of claims 12 to 14, wherein, The first information indicates the configuration file of the first node. The method of claim 15, wherein, The configuration file includes at least one of the following: The identification information of the first node; The first node supports the following service types; The type of the first node; The identification information of the network where the first node is located; The identification information related to the network slice of the first node; The addressing information of the first node; The capability information of the first node; The priority information of the first node; The identification information of the network element set to which the first node is located; The identification information of the service set to which the first node belongs; The specific business authorization information of the first node; The location information of the first node; The location information of the services supported by the first node; Load information of the first node; The storage duration of the first node; The first node supports AI for asynchronous communication. Application Functionality (AF) identifies the events subscribed to for asynchronous communication. The method of claim 16, wherein, The first node supports at least one of the following service types: immersive communication, ultra-reliable low-latency communication, large-scale communication, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing. The method according to claim 16 or 17, wherein The capability information of the first node includes at least one of the following: Storage of business signaling; Transmission of service signaling; Storage of business data; Transmission of business data; Storage of model data; Transmission of model data. The method of any one of claims 16-18, wherein The priority information of the first node includes at least one of the following: Priorities related to business type; Network-related priorities; Priorities related to consumers; Priorities related to network status; Data-related priorities. The method of any one of claims 15 to 19, wherein, The first information is carried in at least one of the following: A registration request message, wherein the first information indicates a new configuration file for the first node; An update request message, wherein the first information indicates the updated configuration file of the first node. The method of any one of claims 15 to 20, wherein, The method further includes: Save the configuration file of the first node. The method of any one of claims 12 to 21, wherein, The method further includes: Receive second information sent by the second node, wherein the second information is used to indicate that the first node is unavailable; Delete the configuration file for the first node. The method of claim 22, wherein, The second information is carried in the registration request message. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1-11 and 12-23. A communication system comprising a first node, a second node, wherein The first node is configured to implement the communication method as described in any one of claims 1 to 11, and the second node is configured to implement the communication method as described in any one of claims 12 to 23. A storage medium storing instructions, the instructions comprising: When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-11, 12-23. A program product comprising at least one of a program, instructions, characterized in that When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method as described in any one of claims 1-11 and 12-23.

Images