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 wherein the first node supports MC service. Through the scheme of the present disclosure, a network device supporting MC service 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] As people's lives and work become increasingly intelligent, more and more massive communication (MC) devices will be deployed. MC services are typically implemented based on a large number of MC devices. 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 MC services.

[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 with the second node; wherein the first node supports MC services.

[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 MC services.

[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 this 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 supporting MC services 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 MC services.

[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, enabling the first node to provide services.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the first information may include at least one of the following: identification information of the first node; type of the first node; capabilities of the first node; identification information of the network in which the first node resides; identification information related to the network slice of the first node; addressing information of the first node; capacity information of the first node; priority information of the first node; identification information of the set of network elements in which the first node resides; identification information of the set of services in which the first node resides; service authorization information specific to the first node; MC services supported by the first node; MC service parameters; location information of the first node; location information of the services supported by the first node; load information of the first node; identification information of the owner of the MC device identifier; identification information of the group in which the first node resides; external identification information of the MC services supported by the first node; support for artificial intelligence (AI) by the first node; multi-network support capability of the first node; identification information of events subscribed to by the application function (AF) for the MC service; identification information of the AF supported by the first node for the MC service.

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

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the type of the first node may include at least one of the following: a primary node, a secondary node, and a service node; wherein the primary node is connected to at least one secondary node; and wherein the service node provides services for one or more service areas.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the capabilities of the first node may include at least one of the following: the first node's ability to support device types; the first node's ability to support service types; and the first node's ability to support topology types.

[0038] In the above embodiments, the capabilities of the first node can be related to device type, and / or service type, and / or topology type. Thus, during the discovery and selection of the first node through the second node, the first node can be determined based on capabilities related to device type, service type, topology type, etc. This ensures that the first node possesses the corresponding capabilities.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the capacity information of the first node may include at least one of the following: the number of devices for the MC service; the number of messages for the MC service; the number of tasks for the MC service; and the number of sessions within the service area of ​​the MC service.

[0040] In the above embodiments, the capacity information of the first node may include the number of devices, the number of messages, the number of tasks, the number of sessions, etc. Thus, during the discovery and selection of the first node through the second node, a first node with the corresponding capacity in terms of devices, messages, tasks, and sessions can be identified, thereby ensuring that the corresponding MC services are implemented based on the first node.

[0041] 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 device type; priority related to topology type; priority related to network; priority related to consumer; priority related to network status; and priority related to single-device services and packet-based device services.

[0042] In the above embodiments, the priority information of the first node can indicate priorities related to service type, device type, topology type, network, consumer, network status, and single-device service / packet-device service. 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.

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

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

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

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

[0047] 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 MC services.

[0048] In the above embodiments, when the first node is deployed in the network, it registers 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, thereby achieving the first node's registration. Thus, other nodes in the network can discover and select the first node through the second node, enabling the first node to provide services.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the first information may include at least one of the following: identification information of the first node; type of the first node; capabilities of the first node; identification information of the network in which the first node resides; identification information related to the network slice of the first node; addressing information of the first node; capacity information of the first node; priority information of the first node; identification information of the network element set in which the first node resides; identification information of the service set in which the first node resides; service authorization information specific to the first node; MC services supported by the first node; MC service parameters; location information of the first node; location information of the services supported by the first node; load information of the first node; identification information of the owner of the MC device identifier; identification information of the group in which the first node resides; external identification information of the MC services supported by the first node; AI support of the first node; multi-network support capability of the first node; identification information of events subscribed by the AF for the MC service; identification information of the AF supported by the first node for the MC service.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the type of the first node may include at least one of the following: a primary node, a secondary node, and a service node; wherein the primary node is connected to at least one secondary node; and wherein the service node provides services for one or more service areas.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the capabilities of the first node may include at least one of the following: the first node's ability to support device types; the first node's ability to support service types; and the first node's ability to support topology types.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the capacity information of the first node may include at least one of the following: the number of devices for the MC service; the number of messages for the MC service; the number of tasks for the MC service; and the number of sessions within the service area of ​​the MC service.

[0053] 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 device type; priority related to topology type; priority related to network; priority related to consumer; priority related to network status; and priority related to single-device services and packet-based services.

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

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

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

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

[0058] 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; wherein the first node supports MC services.

[0059] In a fourth aspect, embodiments of this disclosure provide a communication device. 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 with the second node; wherein the first node supports MC services.

[0060] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information may include at least one of the following: identification information of the first node; type of the first node; capabilities of the first node; identification information of the network in which the first node resides; identification information related to the network slice of the first node; addressing information of the first node; capacity information of the first node; priority information of the first node; identification information of the network element set in which the first node resides; identification information of the service set in which the first node resides; service authorization information specific to the first node; MC services supported by the first node; MC service parameters; location information of the first node; location information of the services supported by the first node; load information of the first node; identification information of the owner of the MC device identifier; identification information of the group in which the first node resides; external identification information of the MC services supported by the first node; AI support of the first node; multi-network support capability of the first node; identification information of events subscribed by the AF for the MC service; identification information of the AF supported by the first node for the MC service.

[0061] In conjunction with some embodiments of the fourth aspect, in some embodiments, the type of the first node may include at least one of the following: a primary node, a secondary node, and a service node; wherein the primary node is connected to at least one secondary node; and wherein the service node provides services for one or more service areas.

[0062] In conjunction with some embodiments of the fourth aspect, in some embodiments, the capabilities of the first node may include at least one of the following: the first node's ability to support device types; the first node's ability to support service types; and the first node's ability to support topology types.

[0063] In conjunction with some embodiments of the fourth aspect, in some embodiments, the capacity information of the first node may include at least one of the following: the number of devices for the MC service; the number of messages for the MC service; the number of tasks for the MC service; and the number of sessions within the service area of ​​the MC service.

[0064] 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 device type; priority related to topology type; priority related to network; priority related to consumer; priority related to network status; and priority related to single-device services and packet-based services.

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

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

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

[0068] In a fifth aspect, embodiments of this disclosure provide a communication device. 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 with a second node; wherein the first node supports MC services.

[0069] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information may include at least one of the following: identification information of the first node; type of the first node; capabilities of the first node; identification information of the network in which the first node resides; identification information related to the network slice of the first node; addressing information of the first node; capacity information of the first node; priority information of the first node; identification information of the network element set in which the first node resides; identification information of the service set in which the first node resides; service authorization information specific to the first node; MC services supported by the first node; MC service parameters; location information of the first node; location information of the services supported by the first node; load information of the first node; identification information of the owner of the MC device identifier; identification information of the group in which the first node resides; external identification information of the MC services supported by the first node; AI support of the first node; multi-network support capability of the first node; identification information of events subscribed by the AF for the MC service; identification information of the AF supported by the first node for the MC service.

[0070] In conjunction with some embodiments of the fifth aspect, in some embodiments, the type of the first node may include at least one of the following: a primary node, a secondary node, and a service node; wherein the primary node is connected to at least one secondary node; and wherein the service node provides services for one or more service areas.

[0071] In conjunction with some embodiments of the fifth aspect, in some embodiments, the capabilities of the first node may include at least one of the following: the first node's ability to support device types; the first node's ability to support service types; and the first node's ability to support topology types.

[0072] In conjunction with some embodiments of the fifth aspect, in some embodiments, the capacity information of the first node may include at least one of the following: the number of devices for the MC service; the number of messages for the MC service; the number of tasks for the MC service; and the number of sessions within the service area of ​​the MC service.

[0073] 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 device type; priority related to topology type; priority related to network; priority related to consumer; priority related to network status; and priority related to single-device services and packet-based services.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0108] In some embodiments, the first node 101 can be used to implement functions such as management, control, and billing triggering of large-scale communication services.

[0109] In some embodiments, the first node 101 may be, for example, a massive communication function (MCF). In some embodiments, the MCF may also be referred to as a massive communication management function (MCMF).

[0110] In some embodiments, the second node 102 can be used to maintain the NF profile of available network function (NF) instances and the services supported by the NF instances.

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

[0112] In some embodiments, the MC service may include AIoT services, such as 5G AIoT services or 6G AIoT services. In some embodiments, the first node 101 may be an AIoT controller. In one example, the first node 101 may be an AIoT function (AIoTF) or an AIoT management function (AIoTMF).

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

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

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

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

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

[0118] 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 network function (NF) 201, a second NF 202, a third NF 203, a fourth NF 204, and a fifth NF 205.

[0119] In some embodiments, the first NF 201, 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. In some embodiments, the fourth NF 204 may be 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.

[0120] In some embodiments, the first NF 201 on the control plane may be a first node 101. In some embodiments, the second NF 202 on the control plane may be a second node 102.

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

[0122] In some embodiments, the communication system 100 may further include an access network device 206 and an MC device 207. The MC device 207 may, for example, communicate with the first NF 201 through the access network device 206.

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

[0124] 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 may be in any way, such as direct connection or indirect connection, wired connection or wireless connection.

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

[0126] In recent years, the Internet of Things (IoT) has received significant attention in the wireless communications world. With the widespread application of IoT technology in wireless communications, higher demands are being placed on the size, complexity, and power performance of IoT devices. More things are expected to be interconnected to improve productivity and enhance quality of life. Further reductions in the size, complexity, and power of IoT devices enable the deployment of billions, or even hundreds of billions, of IoT devices for various applications, providing added value throughout the value chain. However, IoT devices often require built-in energy storage devices such as batteries. This necessitates battery replacements or charging, increasing maintenance costs and reducing convenience. In some scenarios, this can even lead to security risks, such as in wireless sensors in the power industry and the oil industry.

[0127] To address the above issues, a novel IoT technology, namely Ambient IoT (AIoT), is proposed. Devices employing AIoT technology can be referred to as AIoT devices. AIoT devices can be powered through energy capture. For example, an AIoT device can capture energy in the form of electromagnetic waves, light, sound waves, etc., from its surrounding environment to provide electrical power. In some embodiments, AIoT devices may have limited energy storage capabilities.

[0128] In some embodiments, AIoT devices can be categorized into three types. The first type of AIoT device has neither energy storage capability nor independent signal generation capability. The second type of AIoT device has energy storage capability but lacks independent signal generation capability. The third type of AIoT device has both energy storage capability and independent signal generation capability. For the first and second types of AIoT devices, signals can be generated through backscattering.

[0129] In some embodiments, the overall architecture of AIoT includes AIoT devices, readers, AIoT controllers, and application functions (AF).

[0130] In some embodiments, multiple connection topologies exist for AIoT devices. In some embodiments, a first connection topology (or Topology 1, first type of topology) may be: base station <—> AIoT device. In some embodiments, the AIoT device can directly communicate bidirectionally with the base station. Communication between the base station and the AIoT device may include AIoT service-related data and / or signaling. In some embodiments, a second connection topology (or Topology 2, second type of topology) may be: base station <—> intermediate node <—> AIoT device. In some embodiments, user equipment (UE) can be used as an intermediate node under network control. In some embodiments, the AIoT device can communicate bidirectionally with an intermediate node located between the AIoT device and the base station. The intermediate node can forward information between the base station and the AIoT device. In some embodiments, a third connection topology (or Topology 3, third type of topology) may be: base station <—> auxiliary node <—> AIoT device <—> base station. In some embodiments, the AIoT device can send data and / or signaling to the base station and can receive data and / or signaling from the auxiliary node. In some embodiments, the AIoT device can receive data and / or signaling from the base station and can send data and / or signaling to the auxiliary node. In some embodiments, the fourth link topology (or Topology 4, fourth type of topology) can be: UE <—> AIoT device. In some embodiments, the AIoT device can communicate bidirectionally with the UE. In some embodiments, the communication between the AIoT device and the UE can include AIoT service data and / or signaling.

[0131] In different connection topologies, readers can be implemented by different types of devices. For example, a reader can be a base station, an intermediate node, a UE, etc. Massive communication (MC) is a development direction of 6G technology. In massive communication services, the number and types of devices participating in the communication will increase. It is understood that MC services can also have other names, and this disclosure does not specifically limit them.

[0132] In some embodiments, devices employing MC technology can be categorized into low-capability devices and high-capability devices based on their capabilities. In some embodiments, a low-capability device may be a device with relatively weak computing and / or communication capabilities. In one example, a low-capability device may be characterized by small size, low complexity, and low power consumption. Low-capability devices may include, for example, narrowband IoT (NB-IoT) and AIoT. In some embodiments, a high-capability device may be a device with relatively strong computing and / or communication capabilities. A high-capability device employing MC technology may, for example, have a lower network interaction frequency.

[0133] In some embodiments, MC services may include 6G IoT services. In some embodiments, 6G IoT services may include services related to high-capability devices, services related to low-capability devices, 6G AIoT services, and IoT services supported by 6G UEs. In some embodiments, MC services may also include 5G AIoT services.

[0134] In some embodiments, MCFs can be used to manage, monitor, and bill large-scale communication services. When deploying an MCF in a network, the MCF needs to be registered with the NRF to facilitate the selection of a suitable MCF for MC service requests. The selected MCF can support MC service sessions, support the transmission of messages and / or data for MC services, and support the monitoring and statistics of MC service events and usage.

[0135] Therefore, how to register MCF in NRF is an urgent problem to be solved.

[0136] 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 a communication system 100. As shown in Figure 3, the communication method of this embodiment includes steps S301 to S309.

[0137] 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 MCF (Multi-Functional Network Function). In some embodiments, the second node 102 may be an NRF (Network Functional Network Function). 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.

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

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

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

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

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

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

[0144] In some embodiments, the first information may include configuration information of the first node 101, which is used to indicate the configuration file of the first node 101.

[0145] 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; type of the first node 101; capabilities of the first node 101; identification information of the network to which the first node 101 resides; identification information related to network slices of the first node 101; addressing information of the first node 101; capacity information of the first node 101; priority information of the first node 101; identification information of the network element set to which the first node 101 resides; identification information of the service set to which the first node 101 resides; service authorization information specific to the first node 101; MC services supported by the first node 101; MC service parameters; 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; identification information of the owner of the MC device identifier; identification information of the group to which the first node 101 resides; external identification information of the MC services supported by the first node 101; support for artificial intelligence (AI) by the first node 101; multi-network support capability of the first node 101; application functions. The first information (AF) refers to the identification information of events subscribed to by the MC service; the first node 101 refers to the identification information of AFs supported by the MC service. In some embodiments, the first information may include the contents of the configuration file of the first node 101 mentioned above.

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

[0147] In some embodiments, the first node 101 can have different types. For example, 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 can be deployed in the network, and these first nodes 101 can form a hierarchical architecture. In one example, one of the multiple first nodes 101 can be a primary node, and the other first nodes 101 can be secondary nodes. The primary node can be connected to one or more secondary nodes. In this case, the type of the first node 101 can be either a primary node or a secondary node. In some embodiments, the type of the first node 101 can be a service node. A first node 101 acting as a service node can provide services to one or more service areas.

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

[0149] In some embodiments, the first node 101 may have various capabilities. In some embodiments, the capabilities of the first node 101 may include at least one of the following: the first node 101's ability to support device types; the first node 101's ability to support service types; and the first node 101's ability to support topology types.

[0150] In some embodiments, the first node 101's support capability for device types includes at least one of the following: supporting third-party device identifiers and supporting device identifiers assigned by the operator. In some embodiments, the device type of the MC device may include operator devices, third-party devices, etc. In some embodiments, the MC device may be provided by a third party. In one example, the first node 101 may support MC devices provided by a third party. In some embodiments, the device identifier of the MC device may be assigned by a third party. In one example, the first node 101 may support device identifiers assigned by a third party. In some embodiments, the MC device may be provided by an operator. In one example, the first node 101 may support MC devices provided by an operator. In some embodiments, the identifier of the MC device may be assigned by a third party. In one example, the first node 101 may support device identifiers assigned by the operator.

[0151] In some embodiments, where the first node 101 supports third-party device identifiers, the first node 101's support for device types may further include the third parties supported by the first node 101. In one example, the configuration file of the first node 101 may include identification information of the third parties supported by the first node 101.

[0152] In some embodiments, where the first node 101 supports the device identifier of an operator, the device type support capability of the first node 101 may further include the operators supported by the first node 101. In one example, the configuration file of the first node 101 may include the identification information of the operators supported by the first node 101.

[0153] In some embodiments, the service type support capability of the first node 101 can be used to determine the service types supported by the first node 101. In some embodiments, the service type support capability of the first node 101 may be to support all service types. For example, the first node 101 may support all service types related to large-scale communication. In some embodiments, the service type support capability of the first node 101 may be to support some service types. For example, the first node 101 may support one or more of the service types related to large-scale communication.

[0154] In some embodiments, the topology type support capability of the first node 101 can be used to determine the topology types supported by the first node 101. In some embodiments, the topology types related to AIoT services may include: Topology 1, Topology 2, Topology 3, and Topology 4. In one example, the topology type support capability of the first node 101 may be to support at least one of Topology 1, Topology 2, Topology 3, and Topology 4.

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

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

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

[0158] In some embodiments, the capacity information of the first node 101 can be used to indicate the capacity of the first node 101. In some embodiments, the capacity information of the first node 101 may include at least one of the following: the number of devices for the MC service; the number of messages for the MC service; the number of tasks for the MC service; and the number of sessions within the service area of ​​the MC service. In some embodiments, the capacity of the first node 101 may be related to the number of devices for the MC service. For example, the capacity of the first node 101 may include the maximum number of MC devices for the MC service supported by the first node 101. For example, the capacity of the first node 101 may include the maximum number of MC devices for each MC service supported by the first node 101. In some embodiments, the capacity of the first node 101 may be related to the number of messages for the MC service. For example, the capacity of the first node 101 may include the maximum number of messages for the MC service supported by the first node 101. For example, the capacity of the first node 101 may include the maximum number of messages for each MC service supported by the first node 101. In some embodiments, the capacity of the first node 101 may be related to the number of tasks for the MC service. For example, the capacity of the first node 101 may include the maximum number of tasks for the MC service supported by the first node 101. For example, the capacity of the first node 101 may include the maximum number of tasks supported by each MC service. In some embodiments, the capacity of the first node 101 may be related to the number of sessions within the service area of ​​the MC service. For example, the capacity of the first node 101 may include the maximum number of sessions supported by the first node 101 within the service area. For example, the capacity of the first node 101 may include the maximum number of sessions supported by the first node 101 within each service area. For example, the capacity of the first node 101 may include the maximum number of sessions supported by each MC service within the service area. For example, the capacity of the first node 101 may include the maximum number of sessions supported by each MC service within each service area.

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

[0160] 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 device type; priority related to topology type; priority related to network; priority related to consumer; priority related to network status; and priority related to single device service and packet device service.

[0161] In some embodiments, priority can be related to service type. In some embodiments, the MC service can have multiple service types. 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. Therefore, 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.

[0162] In some embodiments, priority may be related to device type. In some embodiments, MC devices may have different device types. The first node 101 may adopt the same or different priorities for different device types. In some embodiments, the first node 101 may have different priorities for MC devices with device identifiers assigned by a third party and MC devices with device identifiers assigned by the operator. For example, MC devices with device identifiers assigned by the operator may have a high priority, and MC devices with device identifiers assigned by a third party may have a low priority. Therefore, for MC devices with device identifiers assigned by the operator, the first node 101 may be preferentially selected. For example, the first node 101 may be preferentially used for MC services related to MC devices with device identifiers assigned by the operator.

[0163] In some embodiments, priority can be related to topology type. In some embodiments, the first node 101 can adopt the same or different priorities for different topology types. In some embodiments, topology types can include topology 1, topology 2, topology 3, and topology 4. In one example, any two topology types among topology 1, topology 2, topology 3, and topology 4 can have the same or different priorities. In some embodiments, topology types can include: MC devices communicating directly with the first node 101, and MC devices communicating indirectly with the first node 101 through another node. This other node can be, for example, an access and mobility management function (AMF). In one example, direct communication can have a higher priority than indirect communication. In some embodiments, topology types can include: uplink and downlink paths being the same, and uplink and downlink paths being different. For example, in topology 1, topology 2, and topology 4, the uplink and downlink paths of the AIoT device can be the same. For example, in topology 3, the uplink and downlink paths of the AIoT device can be different. In one example, the priority of a topology structure with the same uplink and downlink paths can be higher than the priority of a topology structure with different uplink and downlink paths. For example, for a topology type with high priority, the first node 101 can be selected first. For example, the first node 101 can be preferentially used for a topology type with high priority.

[0164] In some embodiments, priority can be network-related. In some embodiments, PLMN and SNPN can have the same or different priorities. For example, the priority of PLMN can be higher than that of SNPN. For example, the priority of PLMN can be lower than that of SNPN. In some embodiments, multiple PLMNs can have the same or different priorities. In some embodiments, multiple SNPNs can have the same or different priorities. For example, for a network with a high priority, the first node 101 can be preferentially selected. For example, the first node 101 can be preferentially used for a network with a high priority.

[0165] In some embodiments, priority can be associated with a consumer. In some embodiments, a consumer (or consumer network function) can be a network exposure function (NEF) or a network function in the core network. For example, MC services can be provided to network functions located outside the core network (e.g., AF). Since network functions outside the core network are connected to the core network via NEF, the consumer can be either a NEF or an AF. For example, if MC services 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.

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

[0167] In some embodiments, priority can be associated with single-device services and packet-device services. In some embodiments, the priority of a service associated with a single MC device can be equal to or different from the priority of a service associated with multiple MC devices. In one example, the priority of a single-device service can be higher than that of a packet-device service. For example, for a single-device service, the first node 101 can be preferentially selected. For example, the first node 101 can be preferentially used for single-device services with high priority. In one embodiment, the priority of a single-device service can be lower than that of a packet-device service. For example, for a packet-device service, the first node 101 can be preferentially selected. For example, the first node 101 can be preferentially used for packet-device services with high priority.

[0168] In some embodiments, the priority information of the first node 101 can be used to indicate the priority of the first node 101 in processing MC services. 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 device type; priority related to topology type; priority related to network; priority related to consumer; priority related to network state; and priority related to single-device services and packet-device services. In one example, the first node 101 can process MC services of each service type according to the priority related to service type. For example, the first node 101 can prioritize processing MC services of service types with high priority. In one example, the first node 101 can process MC services of each device type according to the priority related to device type. For example, the first node 101 can prioritize processing MC services of device types with high priority. In one example, the first node 101 can process MC services of each topology type according to the priority related to topology type. For example, the first node 101 can prioritize processing MC services of topology types with high priority. In one example, the first node 101 can process the MC services of each network according to network-related priorities. For example, the first node 101 can prioritize processing the MC services of networks with high priority. In another example, the first node 101 can process the MC services of each consumer according to consumer-related priorities. For example, the first node 101 can prioritize processing the MC services of consumers with high priority. In yet another example, the first node 101 can process the MC services of each network state according to network state priorities. For example, the first node 101 can prioritize processing the MC services of network states with high priority. In yet another example, the first node 101 can process the MC services according to priorities related to single-device services and packet-switched device services. For example, the first node 101 can prioritize processing single-device services or packet-switched device services with high priority.

[0169] 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 MCF (Multi-Functional Function), and the MCF can belong to an MCF set. In this case, the identification information of the network element set can include the identifier of the MCF set. In some embodiments, the first node 101 can be an AIoTF (Automatic IoT Function), and the AIoTF can belong to an AIoTF set. In this case, the identification information of the network element set can include the identifier of the AIoTF set.

[0170] 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 some embodiments, the first node 101 can be an MCF (Multi-Family Provider), and the identification information of the service set can include an MCF service set identifier.

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

[0172] In some embodiments, the configuration file of the first node 101 may include the MC services supported by the first node 101. In some embodiments, the first node 101 may support one or more types of MC services. For example, the configuration file of the first node 101 may include the types of MC services supported by the first node 101. In some embodiments, the type of MC service may be represented by the service name of the MC service. For example, the type of MC service supported by the first node 101 may be indicated by a service identifier. In some embodiments, the first node 101 may support one or more service types, then the configuration file of the first node 101 may include type information and / or service names of the MC services supported by the first node 101.

[0173] In some embodiments, the configuration file of the first node 101 may include MC service parameters. MC service parameters may include parameters related to MC services. In some embodiments, MC service parameters may include a data network name (DNN) and / or a list of DNNs. In some embodiments, MC service parameters may include the endpoint address of the first node 101 for each service supported by the first node 101. For example, if the first node 101 is an MCF (Multi-Functional Function), then the MC service parameters may include a notification endpoint for notifications of services supported by the MCF. In some embodiments, MC service parameters may include network functions and / or consumers that subscribe to state. In some embodiments, MC service parameters may include parameters served or controlled by the first node 101.

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

[0175] In some embodiments, the location information of the first node 101 may include the service area of ​​the MC service. In some embodiments, the service area may be indicated by geographical location, administrative region location, service area identifier, etc.

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

[0177] In some embodiments, the location information may further include network functions supported by the first node 101 for direct or indirect communication with MC services. 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 to implement MC services.

[0178] In some embodiments, the location information of the service supported by the first node 101 can be used to indicate the location of the MC 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 cells supported by the first node 101 for the MC service. 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 first node 101 for the MC service. 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.

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

[0180] In some embodiments, the identification information of the owner of the MC device identifier can be used to identify the owner of the MC device identifier. In some embodiments, the owner of the MC device identifier can be the operator or application function that assigns the identifier to the MC device. In some embodiments, the owner of the MC device identifier can be the payer of the MC service or service type.

[0181] In some embodiments, the first node 101 may be in a group. The group containing the first node 101 may be indicated by a group identifier. In some embodiments, the group may be determined based on the range of MC devices. For example, first nodes 101 corresponding to MC devices within a certain area may be located in the same group. In some embodiments, the group may be determined based on the type of MC device. For example, first nodes 101 corresponding to MC devices of the same device type may be located in the same group. For example, first nodes 101 corresponding to MC devices of one or more predetermined device types may be located in the same group. In some embodiments, the group may be determined based on the device identifier of the MC device. For example, first nodes 101 corresponding to MC devices indicated by one or more device identifiers may be located in the same group.

[0182] In some embodiments, the configuration file of the first node 101 may include external identification information of the MC services supported by the first node 101. In some embodiments, the external identification information may include at least one of the following: a range of external identifiers and a range of external group identifiers. In some embodiments, the range of external identifiers may include the range of external identifiers of the MC devices supported by the first node 101. In some embodiments, the range of external identifiers may include the range of external group identifiers of the MC devices supported by the first node 101.

[0183] 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 example, the first node 101 may support model training, model inference, and other processing based on AI / ML (machine learning) models. In some embodiments, the first node 101 may support the use of AI technology to implement MC (Machine Learning) services, or it may not support the use of AI technology to implement MC services. 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.

[0184] In some embodiment sets, AI support for the first node 101 may include supporting the determination of the first node 101 based on AI analysis. In some embodiments, the configuration file of the first node 101 may include indication information that may instruct the first node 101 to support the discovery and selection of itself based on AI analysis.

[0185] 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 MC applications based on AI technology. For example, in the case of implementing MC applications 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.

[0186] In some embodiments, the multi-network support capability of the first node 101 may refer to the ability of the first node 101 to support different networks. In some embodiments, the multi-network support capability of the first node 101 may include: multi-network interaction capability, roaming interaction capability, and public / private network support capability.

[0187] In some embodiments, multi-network interaction capability refers to whether the first node 101 supports MC services across multiple networks. In some embodiments, MC services may involve multiple networks, and the multi-network interaction capability of the first node 101 can support such MC services. In one example, the first node 101 can support MC services across multiple PLMNs. In another example, the first node 101 can support MC services across multiple SNPNs.

[0188] In some embodiments, the roaming interaction capability of the first node 101 can refer to whether the first node 101 supports roaming exchange between implementing networks. In some embodiments, MC services can roam between different networks, then the first node 101 can support roaming exchange of MC services between networks. In one example, the first node 101 can support roaming exchange between multiple PLMNs. In some embodiments, the first node 101 can support roaming exchange between multiple SNPNs. In some embodiments, the first node 101 can support roaming exchange between PLMNs and SNPNs.

[0189] In some embodiments, the public / private network support capability of the first node 101 may refer to the first node 101's support for public and / or private networks. In some embodiments, the public / private network support capability of the first node 101 may include at least one of the following: the first node 101's support for public networks, and the first node 101's support for private networks. In one example, the first node 101 may support public networks or not support public networks. In one example, the first node 101 may support private networks or not support private networks.

[0190] In some embodiments, the configuration file of the first node 101 may include identification information for events subscribed to by the AF for the MC service. For example, the event identification information may include an event ID. In some embodiments, this identification information may be used to represent events of the MC service subscribed to by the AF.

[0191] In some embodiments, the identification information of the AFs supported by the first node 101 for the MC service can be used to identify the AFs supported by the first node 101. In some embodiments, the configuration file of the first node 101 may include an AF identifier list. The AF identifier list may include identifiers of one or more AFs supported by the first node 101 for the MC service.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0207] In some embodiments, under certain circumstances, 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 the OAM system. For example, the OAM function 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.

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

[0209] In some embodiments, the updated configuration file may include at least one of the following: identification information of the first node 101; type of the first node 101; capabilities 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; capacity 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 authorization information specific to the first node 101; MC services supported by the first node 101; MC service parameters; 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; identification information of the owner of the MC device identifier; identification information of the group where the first node 101 is located; external identification information of the MC services supported by the first node 101; AI support of the first node 101; roaming switching capability of the first node 101; identification information of events subscribed by the AF for the MC service; identification information of the AF supported by the first node 101 for the MC service.

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

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

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

[0213] In some embodiments, the second node 102 may update the configuration file of the first node 101 based on the first information. In some embodiments, the second node 102 may store the updated configuration file.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0228] In some embodiments, the second node 102 may remove 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.

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

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

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

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

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

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

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

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

[0237] In some embodiments, referring to the system 100 shown in FIG2, the first node 101 may be a first NF 201, and the second node 102 may be a second NF 202. The fifth NF 205 may send a request to implement MC services. The third NF 203 may determine policies and / or rules for MC services based on the request from the fifth NF 205. The fifth NF 205 or the third NF 203 may send a request to the second NF 202 to realize the discovery and selection of the first NF 201. Through the discovery and selection process, the fifth NF 205 or the third NF 203 may determine the first NF 201 and send a message to the first NF 201. The first NF 201 may configure the fourth NF 204, and / or access network device 206, and / or MC device 207 to implement MC services based on the message from the fifth NF 205 or the third NF 203.

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

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

[0240] 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.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0284] In some embodiments, this disclosure provides an MCF configuration file. The MCF (i.e., the first node) registers with the NRF (i.e., the second node) to support large-scale communication services (e.g., AIoT services), such as finding suitable network functions to support MC service sessions, supporting the transmission of MC messages and data, and supporting the monitoring and counting of MC service events and usage.

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

[0286] -MCF (e.g., AIoTF) instance ID;

[0287] -MCF (e.g., AIoTF) type or capability, for example,

[0288] - The primary MCF, or an MCF serving one or more service areas of a PLMN or SNPN;

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

[0290] -MCF supports all business types, or one or more business types;

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

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

[0293] -MCF's FQDN or IP address;

[0294] -MCF capacity information,

[0295] -Number of devices for MCF services;

[0296] -Number of messages in the MCF service;

[0297] - The number of tasks in the MC service (a task can include one or more messages);

[0298] - Sessions within the service area of ​​the MCF business;

[0299] -MCF priority information, for example,

[0300] -MC business type MCF priority;

[0301] -MC service device type MCF priority, including AF or operator-assigned device ID;

[0302] -MC service topology type MCF priority, including topology for communication between device and BS node, topology for communication between device and UE, topology for direct communication with MCF or indirect communication with MCF through AMF, and topology for communication between device and UL and DL using different modes.

[0303] - For MC services, different PLMNs or SNPNs have different MCF priorities;

[0304] - Consumer's MCF priority information, such as NEF or local NEF;

[0305] - MCF priority for different network states, such as overload or congestion;

[0306] -MCF priority for single-device services or group-based services;

[0307] -MCF set ID, if more than one MCF is deployed in the same service area, it is considered as a set;

[0308] - The MCF service collection ID of the MCF service instance, if the MCF collection is deployed based on service type;

[0309] -MCF-specific business authorization information, including businesses that can be authorized and supported by MCF, and business capabilities registered with MCF in PLMN or SNPN, or in the service area of ​​PLMN or SNPN;

[0310] - The type or name of the MC services supported by MCF;

[0311] -MC service parameters, such as DNN or DNN list, notification endpoints for notifications supported by MC services, such as which NF or consumer subscription status, or MC service parameters served or controlled by MCF.

[0312] - Location information for the MCF, such as service area, priority value or list of service areas, and location information of the NF that the MCF supports for direct or indirect communication with MC services;

[0313] -MCF supports the cell ID, TAI, or campus ID for its services;

[0314] -Identification information of the MC device ID holder, such as the device ID assigned by the operator or AF, or the payer for the MC service or service type;

[0315] -MCF group ID, the range, type, or ID of the MC device;

[0316] - The scope of external identifiers or the scope of external group identifiers for MC services supported by MCF;

[0317] - AI-supported MCF IDs for MC business, such as MCFs selected based on AI analysis, or priority lists from AI or ML functions;

[0318] -MCF's multi-network support capabilities, including multi-network interaction capabilities, and / or roaming interaction capabilities, and / or public and private network support capabilities;

[0319] -AF refers to the time ID for MC service subscriptions;

[0320] - A list of AF IDs supported by MCF for MC services.

[0321] 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 MCF registration process. As shown in Figure 5A, the communication method includes steps S5101 to S5103.

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

[0323] In step S5102, the NRF stores the MCF configuration file and marks MCF service support as available.

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

[0325] 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 MCF configuration file update process. As shown in Figure 5B, the communication method includes steps S5201 to S5203.

[0326] In step S5201, the MCF (i.e., the MCF instance) sends an Nnrf_NFManagement_NFUpdate request message (updated MCF profile) to the NRF to notify the NRF of the updated MCF profile (e.g., with updated capacity). 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.

[0327] In step S5202, NRF updates and stores the MCF configuration file.

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

[0329] 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 MCF deregistration process. As shown in Figure 5C, the communication method includes steps S5301 to S5303.

[0330] In step S5301, when the MCF is about to gracefully shut down or disconnect from the network, the MCF (i.e., the MCF instance) sends an Nnrf_NFManagement_NFDeregister request message to the NRF to notify the NRF of the unavailability of the MCF.

[0331] In step S5302, the NRF marks the MCF as unavailable. In some embodiments, the NRF can remove the MCF configuration file according to the MCF management policy.

[0332] In step S5303, the NRF learns that the MCF deregistration has been accepted via the Nnrf_NFManagement_NFDeregister response message.

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

[0334] 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 that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

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

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

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

[0338] 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 to the second node; wherein the first node supports MC services. Optionally, the transceiver module 601 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the first node 101 in any of the above methods (e.g., steps S301, S303, S304, S306, S307, S309, but not limited thereto), which will not be elaborated here.

[0339] 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 to the second node; wherein the first node supports MC services. 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.

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

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

[0342] 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 an MC device, 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 MC device in implementing any of the above methods, a chip, chip system, or processor that supports the terminal in implementing any of the above methods, or a chip, chip system, or processor that supports the network device in implementing any of the above methods. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0356] 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

1. A communication method, executed 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 to the second node; The first node supports large-scale communication (MC) services.

2. The method according to claim 1, wherein, The first information includes at least one of the following: The type of the first node; The capabilities of the first node; Capacity 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 MC services supported by the first node; MC service parameters; 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 identification information of the owner of the MC device identifier; The identifier information of the group to which the first node belongs; External identification information of the MC services supported by the first node; The first node supports artificial intelligence (AI); The first node's multi-network support capability; Application Function AF identifies the event information for MC service subscriptions; The first node identifies the AF that the MC service supports; The identification information 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.

3. The method according to claim 2, wherein, The type of the first node includes at least one of the following: master node, auxiliary node, and service node; The master node is connected to at least one of the auxiliary nodes; The service node provides services to one or more service areas.

4. The method according to claim 2 or 3, wherein, The capabilities of the first node include at least one of the following: The first node's ability to support device types; The first node's ability to support different business types; The first node's ability to support topology types.

5. The method according to any one of claims 2 to 4, wherein, The capacity information of the first node includes at least one of the following: Number of devices used in MC operations; The number of messages in the MC service; The number of tasks in the MC business; The number of sessions within the service area of ​​the MC service.

6. The method according to any one of claims 2 to 5, wherein, The priority information of the first node includes at least one of the following: Priorities related to business type; Priorities related to device type; Priorities related to topology type; Network-related priorities; Priorities related to consumers; Priorities related to network status; Priorities related to single-device services and group-device services.

7. The method according to any one of claims 1 to 6, 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.

8. The method according to any one of claims 1 to 7, 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.

9. The method according to claim 8, wherein, The second information is carried in the registration request message.

10. A communication method, executed 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 to the second node; The first node supports large-scale communication (MC) services.

11. The method according to claim 10, wherein, The first information includes at least one of the following: The type of the first node; The capabilities of the first node; Capacity 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 MC services supported by the first node; MC service parameters; 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 identification information of the owner of the MC device identifier; The identifier information of the group to which the first node belongs; External identification information of the MC services supported by the first node; The first node supports artificial intelligence (AI); The first node's multi-network support capability; Application Function AF identifies the event information for MC service subscriptions; The first node identifies the AF that the MC service supports; The identification information 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.

12. The method according to claim 11, wherein, The type of the first node includes at least one of the following: master node, auxiliary node, and service node; The master node is connected to at least one of the auxiliary nodes; The service node provides services to one or more service areas.

13. The method according to claim 11 or 12, wherein, The capabilities of the first node include at least one of the following: The first node's ability to support device types; The first node's ability to support different business types; The first node's ability to support topology types.

14. The method according to any one of claims 12 to 13, wherein, The capacity information of the first node includes at least one of the following: Number of devices used in MC operations; The number of messages in the MC service; The number of tasks in the MC business; The number of sessions within the service area of ​​the MC service.

15. The method according to any one of claims 11 to 14, wherein, The priority information of the first node includes at least one of the following: Priorities related to business type; Priorities related to device type; Priorities related to topology type; Network-related priorities; Priorities related to consumers; Priorities related to network status; Priorities related to single-device services and group-device services.

16. The method according to any one of claims 10 to 15, 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.

17. The method according to any one of claims 10 to 16, wherein, The method further includes: Save the configuration file for the first node.

18. The method according to any one of claims 10 to 17, 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.

19. The method according to claim 18, wherein, The second information is carried in the registration request message.

20. A communication method for a communication system, wherein, The communication system includes a first node and a second node; The method includes: The first node sends first information to the second node, wherein the first information is used to register the first node to the second node; The first node supports large-scale communication (MC) services.

21. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1-9 and 10-19.

22. A communication system, comprising a first node and a second node, wherein, The first node is configured to implement the communication method as described in any one of claims 1 to 9, and the second node is configured to implement the communication method as described in any one of claims 10 to 19.

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

24. A program product comprising at least one of a program and 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-9 and 10-19.

Images