Network access method, apparatus and system, and communication device and storage medium

Abstract

The present application relates to a network access method, apparatus and system, and a communication device, a storage medium and a computer program product. The method comprises: sending a terminal capability of a target zero-power-consumption device by means of receiving a terminal capability query request, wherein the terminal capability comprises one or more of a device identifier attribute, a packet identifier attribute and a node type attribute (S102); and receiving the target packet identifier, updating the terminal capability on the basis of the target packet identifier, receiving a target communication scheduling policy, and communicating with a network on the basis of the target communication scheduling policy (S104).

Description

Network access method, device, system, communication equipment and storage medium

[0001] Related applications

[0002] This application claims priority to Chinese patent application number 2023110145097, filed on August 11, 2023, entitled “Network access method, device, system, communication equipment and storage medium,” the entire text of which is hereby incorporated by reference. Technical Field

[0003] The present application relates to the field of mobile communication technology, and in particular to a network access method, apparatus, system, communication equipment, storage medium, and computer program product. Background Art

[0004] With the continuous advancement of communication technology, the application of passive IoT is becoming increasingly widespread. The zero-power communication devices used in passive IoT typically do not have batteries, or only have small-capacity batteries or capacitors. RF energy can be converted into DC power and stored in the battery of the zero-power device, or it can directly drive the device for information collection, processing, and transmission.

[0005] Traditional RFID technology provides short-range passive IoT solutions for point-to-point or simple networking. In contrast, cellular passive IoT, leveraging base stations and combining RF energy harvesting, backscattering, and low-power computing, can extend transmission distances to hundreds of meters. Therefore, enabling IoT devices of all types to connect to 5G networks is a pressing issue.

[0006] Summary of the Invention

[0007] In a first aspect, the present application provides a network access method. Applied to a zero-power device, the method includes:

[0008] receiving a terminal capability query request, and sending terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute; and

[0009] Receive a target group identifier, update the terminal capability based on the target group identifier, and receive a target communication scheduling strategy, and communicate with the network based on the target communication scheduling strategy.

[0010] In one embodiment, receiving a terminal capability query request and sending the terminal capabilities of a target zero-power device include:

[0011] The terminal capability query request sent by the network through the intermediate node device is received, and the terminal capability of the target zero-power device is sent to the intermediate node device, where the target zero-power device is the present device.

[0012] In one embodiment, receiving a terminal capability query request and sending the terminal capabilities of a target zero-power device include:

[0013] Receive a terminal capability query request sent by the network, send the terminal capability of the zero-power device to the network, and the target zero-power device is the current device.

[0014] In one embodiment, the zero-power consumption device is an intermediate node device; receiving a terminal capability query request and sending the terminal capabilities of a target zero-power consumption device include:

[0015] Receive terminal capability query request sent by the network,

[0016] Sending a terminal capability query request to the zero-power device connected to the intermediate node device; and

[0017] The terminal capability sent by the zero-power device connected to the intermediate node device is received, and the terminal capability of the zero-power device connected to the intermediate node device is sent to the network, where the target zero-power device is the zero-power device connected to the intermediate node device.

[0018] In one embodiment, the terminal capability includes at least a group identification attribute; and updating the terminal capability based on the target group identification includes:

[0019] The target group identifier is determined to be the group identifier attribute in the updated terminal capability.

[0020] In one embodiment, the terminal capabilities do not include a group identifier attribute; and updating the terminal capabilities based on the target group identifier includes:

[0021] A group identification attribute is added to the terminal capability, and the target group identification is determined to be the group identification attribute in the updated terminal capability.

[0022] In one embodiment, communicating with a network based on a target communication scheduling policy includes:

[0023] Sending a zero-power terminal registration request based on the target communication scheduling policy; the zero-power terminal registration request is used to instruct the network to process the registration request; and

[0024] Receive a registration response message for a registration request to communicate with the network.

[0025] In one embodiment, the node type attribute includes a first device type, a second device type, and a third device type, the first device type is an Internet of Things device that communicates with a base station, the second device type is an intermediate node device, and the third device type is an Internet of Things device that communicates with a base station through an intermediate node device.

[0026] In one embodiment, the network is an access network or a core network.

[0027] In one embodiment, the access network includes a base station and an access gateway.

[0028] In a second aspect, the present application provides a network access method. Applied to a network, the method includes:

[0029] Send terminal capability query request;

[0030] Receive terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute;

[0031] Determining a target group identifier corresponding to the target zero-power device based on the contract information of the target zero-power device, and determining a target communication scheduling policy associated with the target zero-power device; and

[0032] Send target group identifier and target communication scheduling strategy.

[0033] In one embodiment, the zero-power device is an intermediate node device; receiving the terminal capabilities of the target zero-power device includes:

[0034] The terminal capability of the target zero-power device sent by the intermediate node device is received, where the target zero-power device is a zero-power device connected to the intermediate node device.

[0035] In one embodiment, based on the contract information of the target zero-power device, determining the target group identifier corresponding to the target zero-power device, determining the target communication scheduling policy associated with the target zero-power device, and sending the target group identifier and the target communication scheduling policy include:

[0036] Determining a target group identifier corresponding to the target zero-power device and a target communication scheduling strategy for the target zero-power device based on the contract information of the target zero-power device; and

[0037] The target group identifier corresponding to the target zero-power device and the target communication scheduling strategy are sent to the intermediate node device; the target group identifier is used to instruct the intermediate node device to send the target group identifier to the target zero-power device; the target communication scheduling strategy is used to instruct the intermediate node device to send the target communication scheduling strategy to the target zero-power device.

[0038] In one embodiment, the method further comprises:

[0039] After receiving the terminal capability of the target zero-power device sent by the intermediate node device, generating a communication scheduling strategy corresponding to the intermediate node device; and

[0040] Send the communication scheduling policy corresponding to the intermediate node device to the intermediate node device.

[0041] In one embodiment, determining a target group identifier corresponding to the target zero-power consumption device based on the contract information of the target zero-power consumption device includes:

[0042] Obtaining first contract information corresponding to the intermediate node device and second contract information of the target zero-power device;

[0043] If it is determined that the requirements are met based on the first contract information and the second contract information, a corresponding relationship between the intermediate node device and the target zero-power consumption device is established; and

[0044] Based on the second subscription information, a target group identifier corresponding to the target zero-power consumption device is determined.

[0045] In one embodiment, the network is an access network or a network.

[0046] In one embodiment, the access network includes a base station and an access gateway.

[0047] In a third aspect, the present application provides a network access device, which is applied to a zero-power device, and includes:

[0048] A first receiving module is configured to receive a terminal capability query request and send terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute; and

[0049] The second receiving module is configured to receive a target group identifier, update the terminal capability based on the target group identifier, receive a target communication scheduling strategy, and communicate with the network based on the target communication scheduling strategy.

[0050] In a fourth aspect, the present application provides a network access device, applied to a network, comprising:

[0051] A first sending module, configured to send a terminal capability query request;

[0052] A third receiving module is configured to receive terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute; and

[0053] The first determination module is used to determine the target group identifier corresponding to the target zero-power device based on the contract information of the target zero-power device, determine the target communication scheduling policy associated with the target zero-power device, and send the target group identifier and the target communication scheduling policy.

[0054] In a fifth aspect, the present application provides a network access system, which includes at least a zero-power device and a network, wherein:

[0055] Network, used to send terminal capability query requests;

[0056] A zero-power device, configured to receive a terminal capability query request and send terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute;

[0057] The network is further configured to receive the terminal capabilities of the target zero-power device, determine the target group identifier corresponding to the target zero-power device based on the contract information of the target zero-power device, determine the target communication scheduling policy associated with the target zero-power device, and send the target group identifier and the target communication scheduling policy; and

[0058] The zero-power device is further used to receive a target group identifier, update terminal capabilities based on the target group identifier, and receive a target communication scheduling strategy, and access the network based on the target communication scheduling strategy.

[0059] In a sixth aspect, the present application provides a communication device, comprising: a transmitter, a processor, and a receiver;

[0060] A receiver, configured to receive a terminal capability query request;

[0061] A transmitter, configured to transmit terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute; and

[0062] The processor is further configured to receive a target group identifier through a receiver, update the terminal capability based on the target group identifier, and receive a target communication scheduling strategy through the receiver, and communicate with the network based on the target communication scheduling strategy.

[0063] In a seventh aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0064] Receive a terminal capability query request, send the terminal capabilities of the target zero-power device, the terminal capabilities include one or more of the device identification attributes, group identification attributes and node type attributes; receive the target group identification, update the terminal capabilities based on the target group identification, and receive the target communication scheduling strategy, and communicate with the network based on the target communication scheduling strategy.

[0065] In an eighth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0066] Receive a terminal capability query request, send the terminal capabilities of the target zero-power device, the terminal capabilities include one or more of the device identification attributes, group identification attributes and node type attributes; receive the target group identification, update the terminal capabilities based on the target group identification, and receive the target communication scheduling strategy, and communicate with the network based on the target communication scheduling strategy.

[0067] The details of one or more embodiments of the present application are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the present application will become apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the conventional technology, the following briefly introduces the drawings required for use in the embodiments or the conventional technology descriptions. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the disclosed drawings without any creative work.

[0069] FIG1 is a schematic diagram of a flow chart of a network access method according to an embodiment;

[0070] FIG2 is a schematic diagram of a flow chart of steps for sending terminal capabilities via an intermediate node in one embodiment;

[0071] FIG3 is a schematic diagram of a process of sending a registration request in one embodiment;

[0072] FIG4 is a schematic diagram of a flow chart of a network access method in another embodiment;

[0073] FIG5 is a schematic diagram of a flow chart of a step of determining a group identifier in one embodiment;

[0074] FIG6 is a flow chart showing steps of sending a communication scheduling strategy corresponding to an intermediate node device in one embodiment;

[0075] FIG7 is a flow chart of the steps of obtaining contract information in one embodiment;

[0076] FIG8 is a signaling diagram of a network access method in one embodiment;

[0077] FIG9 is a structural block diagram of a network access device according to an embodiment;

[0078] FIG10 is a structural block diagram of a network access device in one embodiment; and

[0079] FIG11 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0080] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0081] In one embodiment, as shown in FIG1 , a network access method is provided. This embodiment uses the method applied to a zero-power consumption device as an example for illustration. The network access method includes the following steps:

[0082] Step 102: Receive a terminal capability query request and send the terminal capability of the target zero-power device.

[0083] Among them, the terminal capabilities include one or more of the device identification attributes, group identification attributes, and node type attributes. The zero-power device can configure one or more of the device identification attributes, group identification attributes, and node type attributes in the terminal capabilities. The device identification attribute can be the unique identification information of the zero-power device, the group identification attribute is the identification information used to characterize the group in which the zero-power device is located, and the node type attribute can be the method used to characterize the communication between the zero-power device and the network. For example, a zero-power device with the first node type attribute can communicate directly with the network, and a zero-power device with the second node type attribute can communicate with the network through an intermediate node device, and so on.

[0084] Specifically, if a zero-power device receives a terminal capability query request, the zero-power device can query the terminal capabilities of the local zero-power device based on the terminal capability query request, including one or more device identification attributes, group identification attributes, and node type attributes, and return the terminal capabilities of the device to the communication device that sends the terminal capability query.

[0085] In one example, the terminal capability can be configured with one or more of a device identification attribute, a group identification attribute, and a node type attribute. That is, the terminal capability of a zero-power device can be configured with a device identification attribute, the terminal capability of a zero-power device can be configured with a group identification attribute, or the terminal capability of a zero-power device can also be configured with a node type attribute, and so on.

[0086] Step 104: Receive a target group identifier, update the terminal capability based on the target group identifier, receive a target communication scheduling policy, and communicate with the network based on the target communication scheduling policy.

[0087] Among them, the target group identifier is the group identifier attribute sent to the zero-power device, which is used to update the terminal capabilities configured by the zero-power device; the target communication scheduling strategy is the strategy for communication between the zero-power device and the network, which may include communication time, communication duration, communication method, etc.; the target communication scheduling strategy can be a communication scheduling strategy for communication between the zero-power device and the base station, or it can be a communication scheduling strategy for communication between the zero-power device and the core network.

[0088] Specifically, the zero-power device can receive a target group identifier sent by another device, which can be an intermediate node device or a network. Based on the received target group identifier, the zero-power device can update its terminal capabilities, either by updating the group identifier attribute in the terminal capabilities or by adding a new group identifier attribute to the terminal capabilities. Furthermore, the zero-power device can receive a target communication scheduling policy and communicate with the network based on the target communication scheduling policy.

[0089] In the above-mentioned network access method, the terminal capabilities of the target zero-power device are sent by receiving a terminal capability query request, and the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute. The target group identification is received, the terminal capabilities are updated based on the target group identification, and the target communication scheduling strategy is received, and the network is communicated based on the target communication scheduling strategy. By adopting this method, by adding identification attributes, group identification attributes, and node type attributes to the terminal capabilities, it is possible to ensure that the network can issue a communication scheduling strategy that matches the zero-power terminal, realize communication between different types of zero-power devices and the network, ensure that different types of devices in the Internet of Things communication access the 5G network, and improve communication quality and communication efficiency.

[0090] In one embodiment, the specific processing of step 102 "receiving a terminal capability query request and sending the terminal capability of the target zero-power device" includes:

[0091] The terminal capability query request sent by the network through the intermediate node device is received, and the terminal capability of the target zero-power device is sent to the intermediate node device.

[0092] The target zero-power consumption device is the current device. The target zero-power consumption device may be a device that cannot directly communicate with the network, for example, a device that communicates with the network through an intermediate node device.

[0093] Specifically, the network can generate a terminal capability query request and send the terminal capability query request to the intermediate node device. Based on this, after receiving the terminal capability query request, the intermediate node device can forward the terminal capability query request to the zero-power device connected to the intermediate node device, that is, the local zero-power device. The local zero-power device can determine the local terminal capability based on the received terminal capability query request, that is, determine the local terminal capability as the terminal capability of the target zero-power device; in this way, this device can send the terminal capability of the target zero-power device to the intermediate node device, so that the intermediate node device can send the terminal capability of the target zero-power device to the network.

[0094] In this embodiment, by interacting with intermediate node devices, interaction between zero-power devices and the network can be achieved, ensuring that different types of devices in IoT communications can access the 5G network, thereby improving communication quality and efficiency.

[0095] In one embodiment, the specific processing of step 102 "receiving a terminal capability query request and sending the terminal capability of the target zero-power device" includes:

[0096] Receive a terminal capability query request sent by the network, and send the terminal capability of the zero-power device to the network.

[0097] The target zero-power consumption device is the current device, and the target zero-power consumption device may be a device that can directly communicate with the network.

[0098] Specifically, the network can generate a terminal capability query request and send the terminal capability query request to the local device (the target zero-power device). Based on this, after receiving the terminal capability query request sent by the network, the local device can determine the local terminal capabilities based on the locally stored configuration information, that is, determine the terminal capabilities of the local device as the terminal capabilities of the target zero-power device; thus, the local device can return the terminal capabilities of the target zero-power device to the network.

[0099] In this embodiment, by interacting with intermediate node devices, interaction between zero-power devices and the network can be achieved, ensuring that different types of devices in IoT communications can access the 5G network, thereby improving communication quality and efficiency.

[0100] In one embodiment, the zero-power device is an intermediate node device. Specifically, the device may be an intermediate node device, and multiple zero-power devices connected to the intermediate node device may be zero-power devices that can communicate with the network through the intermediate node device.

[0101] Accordingly, as shown in FIG2 , the specific processing of step 102 “receiving a terminal capability query request and sending the terminal capability of the target zero-power device” includes:

[0102] Step 202: Receive a terminal capability query request sent by the network.

[0103] Specifically, the network may send a terminal capability query request, and the current device (intermediate node device) may receive the terminal capability query request sent by the network.

[0104] Step 204: Send a terminal capability query request to the zero-power device connected to the intermediate node device.

[0105] The zero-power consumption device connected to the intermediate node may be a zero-power consumption device that is communicatively connected to the intermediate node device and needs to transfer messages through the intermediate node device.

[0106] Specifically, in the case where the zero-power consumption device is an intermediate node device, if the intermediate node device receives a terminal capability query request, it will forward the terminal capability query request to each zero-power consumption device end connected to the intermediate node device.

[0107] In one example, when the zero-power consumption device is an intermediate node device, if the intermediate node device receives a terminal capability query request, it will determine the zero-power consumption device corresponding to the terminal capability query request (hereinafter referred to as the target zero-power consumption device) among one or more zero-power consumption devices connected to the intermediate node device, and forward the terminal capability query request to the target zero-power consumption device.

[0108] Step 206: Receive the terminal capabilities sent by the zero-power device connected to the intermediate node device, and send the terminal capabilities of the zero-power device connected to the intermediate node device to the network.

[0109] The target zero-power device is a zero-power device connected to the intermediate node device.

[0110] Specifically, after receiving a terminal capability query request forwarded by the intermediate node device and sent from the network, the zero-power device connected to the intermediate node device will determine the terminal capabilities of the zero-power device based on the local configuration information of the zero-power device and send the received terminal capabilities to the intermediate node device. After receiving the terminal capabilities, the intermediate node device will return the terminal capabilities of the zero-power device connected to the intermediate node device to the network that sent the terminal capability query request, thereby implementing message interaction between multiple zero-power devices and the network as an intermediate node device.

[0111] In this embodiment, this device, acting as an intermediate node device, can receive terminal capability query requests issued by the network to other zero-power devices that cannot communicate directly with the network, and forward messages. Real-time message interaction between the network and zero-power devices that cannot communicate directly with the network is achieved through the intermediate node device, ensuring that different types of devices in IoT communications can access the 5G network, thereby improving communication quality and efficiency.

[0112] In one embodiment, the terminal capability includes at least a group identification attribute. Specifically, the group identification attribute may be attribute information used to ensure the group to which the zero-power device belongs. For example, the group attribute identification of the zero-power device may be determined based on the location information of the zero-power device.

[0113] Accordingly, the specific processing of step 104 "updating terminal capabilities based on the target group identifier" includes:

[0114] The target group identifier is determined to be the group identifier attribute in the updated terminal capability.

[0115] The target group identifier may be information sent by other devices and received by the zero-power consumption device.

[0116] Specifically, when the terminal capabilities of the zero-power device include at least a group identification attribute, if the zero-power device receives a target group identification, the zero-power device can update the group identification attribute contained in the terminal capabilities corresponding to the device, and determine the received target group identification as the updated group identification attribute of the zero-power terminal.

[0117] In one example, the zero-power device can be a zero-power device that can communicate directly with the network. The network can reconfigure the group identifier for the zero-power device, namely the target group identifier, and send the target group identifier to the zero-power device. Based on this, when the zero-power device receives the target group identifier sent by the network, it can update the group identifier attribute included in the terminal capabilities of the device and configure the target group identifier to the group identifier attribute included in the terminal capabilities of the device.

[0118] In another example, the zero-power device may be one that requires an intermediate node device to communicate with the network. Thus, the network may issue a target group identifier to the intermediate node device, which may receive the target group identifier issued by the network and send the target group identifier to the zero-power device connected to the intermediate node device. Thus, the zero-power device connected to the intermediate node device may update the group identifier attribute included in the local terminal capabilities based on the received target group identifier, and determine the target group identifier as the updated group identifier attribute.

[0119] In this embodiment, the target group identifier is sent down by the network to update the group identifier attributes included in the terminal capabilities of each zero-power device, ensuring the timeliness and accuracy of the group identifier attribute update of each zero-power device, and also providing a basis for the network to implement personalized configuration of each zero-power device.

[0120] In one embodiment, the terminal capability does not include a group identification attribute. Specifically, the terminal capability of the zero-power device may not include a group identification attribute, for example, may only include a device identification attribute, or only include a node type attribute, etc.

[0121] Accordingly, the specific processing of step 104 "updating terminal capabilities based on the target group identifier" includes:

[0122] A group identification attribute is added to the terminal capability, and the target group identification is determined to be the group identification attribute in the updated terminal capability.

[0123] Specifically, in the case where the terminal capabilities of the zero-power device do not include a group identification attribute, if the zero-power device receives a target group identification, the zero-power device can perform a new configuration on the terminal capabilities of the device, add a new group identification attribute to the terminal capabilities, and obtain an updated terminal capability. In other words, the zero-power device can update the terminal capabilities corresponding to the device based on the received target group identification, add the group identification attribute to the terminal capabilities, and obtain the terminal capabilities after the update. Accordingly, the zero-power device can also use the received target group identification as the newly added group identification attribute. That is, the specific data corresponding to the newly added group identification attribute is configured as the received target group identification.

[0124] In this embodiment, the target group identifier is issued by the network to update the terminal capabilities of each zero-power device, and the group identifier attribute is added to the terminal capabilities, providing a basis for the network to implement personalized configuration of the terminal capabilities of each zero-power device.

[0125] In one embodiment, as shown in FIG3 , the specific processing of step 104 “communicating with the network based on the target communication scheduling strategy” includes:

[0126] Step 302: Send a zero-power terminal registration request based on the target communication scheduling policy; the zero-power terminal registration request is used to instruct the network to process the registration request.

[0127] Among them, the target communication scheduling strategy can be a communication strategy used to instruct the zero-power device to communicate with the network, including communication time, communication method, communication frequency, etc. The zero-power device that receives the target communication scheduling strategy can communicate with the network based on the communication scheduling rules, communication time, communication method and communication frequency contained in the target communication scheduling strategy.

[0128] Specifically, the zero-power device can send a zero-power terminal registration request according to the communication scheduling rules, communication time, communication mode and communication frequency contained in the received target communication scheduling policy, so that the network that receives the zero-power terminal registration request can perform registration request operation processing.

[0129] In one example, the zero-power device is a terminal that can communicate directly with the network. In this way, the zero-power device can send a zero-power terminal registration request to the network based on the communication scheduling rules, communication time, communication mode and communication frequency included in the target communication scheduling policy. After receiving the zero-power terminal registration request, the network can verify the zero-power device, generate a registration response message after the verification is passed, and return the registration response message to the zero-power device that sent the zero-power terminal registration request.

[0130] In one example, the zero-power device is a terminal that can communicate with the network only through an intermediate node device. In this way, the zero-power device can generate a zero-power terminal registration request based on the communication scheduling rules, communication time, communication mode and communication frequency included in the target communication scheduling policy, and send the zero-power terminal registration request to the intermediate node device connected to the zero-power device. Based on this, after receiving the zero-power terminal registration request, the intermediate power-saving device can forward the zero-power terminal registration request to the network. After receiving the zero-power terminal registration request, the network can verify the zero-power device, generate a registration response message after the verification is passed, and return the registration response message to the intermediate node device. In this way, the intermediate node device can return the received registration response message to the zero-power device that sent the zero-power terminal registration request, and realize the communication between the zero-power device and the network through the intermediate node device.

[0131] Step 304: Receive a registration response message to the registration request to communicate with the network.

[0132] Specifically, the zero-power device can receive the registration response message sent by the network, determine that the zero-power device has been successfully registered with the network, and can communicate with the network according to the communication scheduling rules, communication time, communication method and communication frequency included in the target communication scheduling policy.

[0133] In this embodiment, communication between the zero-power consumption device and the network is achieved, and the communication quality and efficiency between the zero-power consumption device and the network are guaranteed.

[0134] In one embodiment, the node type attribute includes a first device type, a second device type, and a third device type, the first device type is an Internet of Things device that communicates with a base station, the second device type is an intermediate node device, and the third device type is an Internet of Things device that communicates with a base station through an intermediate node device.

[0135] Specifically, the node type attribute is attribute information used to characterize the way in which zero-power devices communicate with the network. The first device type is an Internet of Things device (zero-power device) that can communicate directly with the network or a base station. The zero-power device of the first device type can send messages directly to the network; the zero-power device of the third device type cannot communicate directly with the network or the base station, and needs to communicate with other devices before sending messages to the network or the base station; the zero-power device of the second device type can be an intermediate node device. The zero-power device of the second device type can serve as a relay device for communication between the zero-power device of the third device type and the network. The zero-power device of the third device type can send messages to the zero-power device of the second device type, so that the zero-power device of the second device type forwards the message to the network, and the communication between the zero-power device of the third device type and the network is realized through the zero-power device of the second device type.

[0136] In this embodiment, it can ensure that different types of IoT devices in IoT communication can access the 5G network, thereby improving communication quality and efficiency.

[0137] In one embodiment, the network is an access network or a core network, and the access network includes a base station and an access gateway. Specifically, the core network can be a 5G core network, etc.

[0138] In one embodiment, as shown in FIG4 , a network access method is provided. This embodiment uses the method applied to a network as an example for illustration. The network access method includes the following steps:

[0139] Step 402: Send a terminal capability query request.

[0140] Specifically, when a zero-power device establishes an RRC connection with the network, the network can generate a terminal capability query request and send the terminal capability query request. In one example, the network can send the terminal capability query request to a zero-power device that can directly connect to the network. In another example, for a zero-power device that cannot directly communicate with the network, the network can send the terminal capability query request to an intermediate node device connected to the zero-power device. After receiving the terminal capability query request, the intermediate node device can send the terminal capability query request to the zero-power device.

[0141] Step 404: Receive the terminal capabilities of the target zero-power device.

[0142] The terminal capabilities include one or more of the following: device identification attributes, group identification attributes, and node type attributes. The terminal capabilities of a zero-power device may include only the device identification attribute, group identification attribute, or node type attribute, or may include multiple of these attributes, depending on the actual configuration.

[0143] Specifically, the network can receive the terminal capabilities of the target zero-power device, which can be determined based on the terminal capability query request. The target zero-power device can send the terminal capabilities of the device to the network, or the target zero-power device can send the terminal capabilities of the device to an intermediate node device connected to the target zero-power device, so that the intermediate node device forwards the terminal capabilities of the target zero-power device to the network after receiving the terminal capabilities of the target zero-power device.

[0144] Step 406: Based on the contract information of the target zero-power device, determine the target group identifier corresponding to the target zero-power device and the target communication scheduling policy associated with the target zero-power device, and send the target group identifier and the target communication scheduling policy.

[0145] The contract information of the target zero-power device may be contract information pre-stored on the network side. The target communication scheduling policy associated with the target zero-power device may be a target communication scheduling policy associated with the target zero-power device, for example, it may include the communication scheduling policy of the target zero-power device, and may also include the communication scheduling policy of the device associated with the target zero-power device. For example, if the device associated with the target zero-power device may be an intermediate node device, then the communication scheduling policy of the device associated with the target zero-power device may be the communication scheduling policy of the intermediate node device.

[0146] Specifically, the network can determine the contract information corresponding to the identification information of the target zero-power device based on the identification information received, and determine the target group identifier corresponding to the target zero-power device and the target communication scheduling policy associated with the target zero-power device based on the contract information, and send the target group identifier corresponding to the target zero-power device and the target communication scheduling policy associated with the target zero-power device.

[0147] In this embodiment, a terminal capability query request is sent through the network side; the terminal capability of the target zero-power device is received, and the terminal capability includes one or more of a device identification attribute, a group identification attribute, and a node type attribute; based on the contract information of the target zero-power device, the target group identification corresponding to the target zero-power device is determined, and the target communication scheduling policy associated with the target zero-power device is determined, and the target group identification and target communication scheduling policy are sent. By adopting this method, by adding the identification attribute, group identification attribute, and node type attribute in the terminal capability, it is ensured that the network can issue a communication scheduling policy that matches the zero-power terminal, realize communication between different types of zero-power devices and the network, ensure that different types of devices in the Internet of Things communication access the 5G network, and improve communication quality and communication efficiency.

[0148] In one embodiment, the zero-power device communicating with the network may be an intermediate node device. Specifically, the zero-power device may be an intermediate node device, and the target zero-power device may be multiple zero-power devices connected to the intermediate node device. In other words, the target zero-power device may be a zero-power device that can only communicate with the network through the intermediate node device.

[0149] Accordingly, the specific processing of step 404 "receiving the terminal capability of the target zero-power device" includes:

[0150] Receive the terminal capabilities of the target zero-power device sent by the intermediate node device.

[0151] The target zero-power device is a zero-power device connected to the intermediate node device.

[0152] Specifically, the zero-power device connected to the intermediate node can be a target zero-power device. The target zero-power device can determine the terminal capabilities of the device based on the received terminal capability query request and send the terminal capabilities to the intermediate node device connected to the target zero-power device. In this way, after receiving the terminal capabilities, the intermediate node device can send the terminal capabilities of the target zero-power device to the network connected to the intermediate node device.

[0153] In this embodiment, by interacting with intermediate node devices, interaction between zero-power devices and the network can be achieved, ensuring that different types of devices in IoT communications can access the 5G network, thereby improving communication quality and efficiency.

[0154] In one embodiment, as shown in FIG5 , the specific processing of step 404 of “determining a target group identifier corresponding to the target zero-power device based on the contract information of the target zero-power device, determining a target communication scheduling policy associated with the target zero-power device, and sending the target group identifier and the target communication scheduling policy” includes:

[0155] Step 502: Based on the contract information of the target zero-power-consumption device, determine the target group identifier corresponding to the target zero-power-consumption device and the target communication scheduling strategy of the target zero-power-consumption device.

[0156] The target communication scheduling policy associated with the target zero-power consumption device may be the communication scheduling policy of the target zero-power consumption device.

[0157] Specifically, the network can determine the contract information corresponding to the identification information of the target zero-power device based on the identification information received, and determine the target group identifier corresponding to the target zero-power device based on the contract information, as well as the target communication scheduling strategy for instructing the target zero-power device to communicate with the network.

[0158] Step 504, sending the target group identifier corresponding to the target zero-power device and the target communication scheduling policy to the intermediate node device; the target group identifier is used to instruct the intermediate node device to send the target group identifier to the target zero-power device; the target communication scheduling policy is used to instruct the intermediate node device to send the target communication scheduling policy to the target zero-power device.

[0159] The terminal capabilities of the target zero-power consumption device received by the network may be the terminal capabilities of the target zero-power consumption device sent by the intermediate node device to the network.

[0160] Specifically, after determining the target group identifier of the target zero-power device and the target communication scheduling policy of the target zero-power device, the network can send the target group identifier corresponding to the target zero-power device and the target communication scheduling policy to the intermediate node device. In this way, the intermediate node device can send the target group identifier to the target zero-power device and send the target communication scheduling policy to the target zero-power device.

[0161] In one example, the intermediate node device may send the target group identifier and the target communication scheduling policy to the target zero-power device simultaneously; in another example, the intermediate node device may send the target group identifier and the target communication scheduling policy to the target zero-power device separately.

[0162] In this embodiment, by interacting with intermediate node devices, interaction between zero-power devices and the network can be achieved, ensuring that different types of devices in IoT communications can access the 5G network, thereby improving communication quality and efficiency.

[0163] In one embodiment, as shown in FIG6 , the network access method further includes:

[0164] Step 602: After receiving the terminal capability of the target zero-power device sent by the intermediate node device, generate a communication scheduling policy corresponding to the intermediate node device.

[0165] The terminal capabilities of the target zero-power consumption device received by the network may be the terminal capabilities of the target zero-power consumption device sent by the intermediate node device to the network.

[0166] Specifically, after receiving the terminal capabilities of the target zero-power device sent by the intermediate node device to the network, the network can determine the target group identifier and target communication scheduling policy corresponding to the target zero-power device. In addition, the network can also determine the communication scheduling policy of the intermediate node device. In the case where the intermediate node device is a node (P-node), the communication scheduling policy determined by the network for the intermediate node can be Rule-p.

[0167] Step 604: Send the communication scheduling policy corresponding to the intermediate node device to the intermediate node device.

[0168] Specifically, the network may directly send the determined communication scheduling policy of the intermediate node device to the intermediate node device.

[0169] In this embodiment, the communication scheduling strategy of the intermediate node device and the communication scheduling strategy of the zero-power device connected to the intermediate node device are determined by the network, so as to implement communication scheduling of each zero-power device and ensure that various types of devices can communicate with the network.

[0170] In one embodiment, as shown in FIG7 , the specific processing of step 502 “determining the target group identifier corresponding to the target zero-power consumption device based on the contract information of the target zero-power consumption device” includes:

[0171] Step 702: Acquire first subscription information corresponding to the intermediate node device and second subscription information of the target zero-power consumption device.

[0172] Specifically, the network can query the contract information corresponding to the identification information of the intermediate node device in the contract information database corresponding to the network based on the identification information of the intermediate node device, for example, the first contract information; accordingly, the network can query the contract information corresponding to the identification information of the target zero-power consumption device in the contract information database corresponding to the network based on the identification information of the target zero-power consumption device, for example, the second contract information.

[0173] Step 704: If it is determined that the requirements are met based on the first contract information and the second contract information, a corresponding relationship between the intermediate node device and the target zero-power consumption device is established.

[0174] Specifically, the network can determine whether the first contract information and the second contract information meet the requirements based on the determined first contract information and the second contract information. Specifically, the network obtains the first contract information S1 and the terminal capability of the intermediate node device. The terminal capability M1 may include, for example, the device identification attribute, the group identification attribute, and the node type attribute in the UE Capability IE, and searches for the second contract information S2 and the terminal capability of the target zero-power device. The terminal capability M2 may include, for example, the device identification attribute, the group identification attribute, and the node type attribute in the UE Capability IE. The network can determine whether the terminal capability M1 and the terminal capability M2 meet the corresponding first contract information S1 and the second contract information S2. If the network determines that the requirements are met, a corresponding relationship between the intermediate node device and the target zero-power device can be established, that is, the device identification of the intermediate node device P-node is bound to the device identification of device A (target zero-power device), allowing the intermediate node device P-node to assist device A in accessing the network, that is, device A can communicate with the network through the intermediate node device P-node.

[0175] Step 706: Determine the target group identifier corresponding to the target zero-power consumption device based on the second subscription information.

[0176] Specifically, the network may determine the target group identifier of the target zero-power consumption device carried in the second subscription information based on the second subscription information corresponding to the target zero-power consumption device.

[0177] In this embodiment, by judging whether the intermediate node device and the target zero-power device connected to the intermediate node device meet the requirements, the rationality of the intermediate node device assisting the target zero-power device in communicating with the network can be ensured.

[0178] In one embodiment, the network is an access network or a core network, and the access network includes a base station and an access gateway. Specifically, the core network can be a 5G core network, etc.

[0179] The following describes in detail the specific execution process of the above-mentioned network access method in conjunction with a specific embodiment, for example, it can be a specific execution process of a zero-power IoT device accessing a 5G network.

[0180] In the mobile communications sector, passive IoT can meet the demands for extremely small, ultra-low power terminal form factors and extremely low deployment costs. However, the zero-power devices used in passive IoT lack batteries or are equipped with only small-capacity batteries or capacitors. RF energy can be converted into DC power and stored in the battery of the zero-power device, or directly power the device for information collection, processing, and transmission. Traditional RFID technology can provide short-range passive IoT solutions for point-to-point or simple networking. Regarding related technologies, 3GPP is initiating research on passive IoT and ambient backscatter communications. Technical challenges to be addressed include how different types of IoT devices can access the 5G network and how the network can implement different communication scheduling policies based on device type and capabilities.

[0181] The network access method provided in the embodiment of the present application can ensure that the 5G network can issue corresponding scheduling strategies based on the communication capabilities of the device by adding attributes such as device ID (device identification attribute), device grouping (group identification attribute), and device node attributes (node ​​type attribute), thereby realizing access and communication scheduling of zero-power devices.

[0182] Step 1. Add elements such as device identification, device grouping attributes, and device node attributes to the UE Capability IE (terminal capability) of the zero-power device. Among them, the device ID (device identification attribute) is used to uniquely identify a single device. For those that do not support identification such as SUCI and IMEI, the 5G network uses the value of the device identification as the unique identification of the zero-power device; the device grouping (group identification attribute) is used to implement group management of multiple or a large number of devices; when the device is initialized to access the 5G network, it can be set to empty or to the default value; after the zero-power device accesses the 5G network, the network can maintain the grouping attribute value of the zero-power device unchanged according to the contract information, or reallocate a grouping attribute value (i.e., target group identification) to the zero-power device, which is assigned to the zero-power device when the 5G network issues the communication scheduling policy as a unique identifier to distinguish the group group to which the zero-power device belongs.

[0183] Among them, the node attributes of the device node attributes (node ​​type attributes) include at least: a first device type, a second device type, and a third device type. The first device type is an IoT device that communicates with a base station, the second device type is an intermediate node device, and the third device type is an IoT device that communicates with a base station through an intermediate node device. The first device type can be an IoT device with the ability to access an NR base station and communicate directly with the base station; the second device type can be an intermediate node device (Intermediate Node), which can communicate with an NR base station or with a zero-power device of the third device type; the third device type can be an IoT device that communicates through an intermediate node device (Intermediate Node) and cannot communicate directly with the base station.

[0184] Step 2: The network determines the communication scheduling strategy of the zero-power device and the communication scheduling strategy of the intermediate node device; Step 3: The network sends the communication scheduling strategy of the zero-power device and the communication scheduling strategy of the intermediate node device to the intermediate node device based on the zero-power device, so as to forward the communication scheduling strategy corresponding to the zero-power device to the zero-power device through the intermediate node device, and update the communication scheduling strategy of the zero-power device of the intermediate node device itself; Step 4: Execute the process of different types of devices accessing the 5G network.

[0185] The first type of zero-power device (referred to as device A) has the ability to directly access the network (e.g., the 5G core network) and can perform access and core network registration procedures according to 3GPP standards;

[0186] When device A establishes an RRC connection or the base station initiates a UE Capability Enquiry request, it carries the newly added elements of the UE Capability IE. The newly added elements may include device identifier, device group attributes, and device node attributes; the network determines the target group identifier corresponding to device A based on the contract information, and determines the communication scheduling strategy Rule-a of device A and sends it to device A.

[0187] The third type of zero-power device (referred to as device B) can register in the 5G core network through the intermediate node P-node of the second type of device:

[0188] The network obtains the device identifier, device group attributes, and device node attributes in the UE Capability IE of the intermediate node device P-node, which is called attribute set M1, and searches for the associated contract information (first contract information S1). The network obtains the device identifier, device group attributes, and device node attributes in the UE Capability IE of device B through the intermediate node device, which is called attribute set M2, and searches for the associated contract information (second contract information S2). The network determines whether the contract information requirements are met based on attribute sets M1, M2 and the associated contract information S1, S2. If the network determines that the requirements are met, the device identifier of the intermediate node device P-node can be bound to the device identifier of device B, and the intermediate node device P-node can be allowed to assist device B in accessing the core network. If the network determines that the requirements are not met, it sends an instruction to the intermediate node device P-node to refuse to assist device B in accessing, ending the access process.

[0189] The network assigns a new device group (i.e., target group identifier) ​​to the zero-power device B or maintains the original device group unchanged. The network can also determine the scheduling rule Rule-p of the intermediate node device P-node (the communication scheduling strategy of the intermediate node device); the intermediate node device P-node performs uplink and downlink signaling and data forwarding for the base station and device B according to Rule-p.

[0190] As shown in FIG8 , it may be a schematic diagram of a zero-power device registering through an intermediate node device P-node, including device B, intermediate node device P-node, RAN, AMF, and PCF.

[0191] In step 1, device B can initiate an initial connection with the help of the P-node. In step 2, the P-node can report the device capabilities (i.e., the terminal capabilities of device B) and send them to the core network through the RAN. In step 3, the AMF in the core network can initiate a device registration request, and the PCF generates scheduling rules applicable to the intermediate node and device B, and fines the policy update of the intermediate node. In step 4, the AMF generates a device registration response. In step 5, the AMF completes the device registration and returns it to the P-node. In step 6, the P-node can return information to device B, which may be the completion of the signaling plane connection. In addition, after registration, the PCF can also update the rules of the intermediate node and send the communication scheduling policy associated with device B to the intermediate node.

[0192] When the AMF initiates a device registration request, two scenarios correspond to different processes: one possible implementation method is that the AMF can detect the access of IoT device B through an intermediate node device and trigger the UE Policy Association Modification initiated by the AMF process; another possible implementation method is that the AMF notifies the PCF, and the PCF detects the access of zero-power device B through an intermediate node device and triggers the UE Policy Association Modification initiated by the PCF process. Finally, the network can update the communication scheduling policy Rule-p of the intermediate node device to the intermediate node device P-node.

[0193] In a specific embodiment, a zero-power device with a plug-in card or using an eSIM that has 5G network access capability can continue to use SUCI, IMEI, etc. to identify the device in accordance with the 3GPP standard. However, for devices that do not support NAS signaling or do not support the insertion of a physical SIM card (do not support eSIM), the device ID in the UE Capability IE is used as the unique identifier of the device. For example, the chip built into the RFID tag has a unique ID, uses a separate UID number, follows the encoding rules of the International Barcode Organization EPC, is unique, and cannot be copied. In scenarios where zero-power communication devices bound to certain RFID tags access the 5G network, RFID can be used as the identifier of the device.

[0194] In another specific embodiment, a terminal with 5G access capability can communicate directly with zero-power devices and upload the relevant data of these devices to the IoT server. However, if the terminal does not have the ability of an intermediate node, and these zero-power devices do not support NAS signaling and cannot communicate directly with the NR base station, the 5G network does not perceive these IoT devices, so these devices are usually not registered on the 5G network. A 5G terminal with an RFID card reader can read the data of surrounding RFID tag-bound devices and upload it to the application server. However, if the 5G network does not perceive the devices and data associated with these RFID tags, or there is no contract, these devices do not need to register on the 5G network.

[0195] In another specific embodiment, a card-inserted 5G terminal with an RFID card reader supports intermediate node communication capabilities and has signed a contract with the 5G network. After the terminal accesses the 5G network according to the standard process, it assists other zero-power devices in registering according to the registration process of Figure 8.

[0196] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0197] Based on the same inventive concept, embodiments of the present application also provide a network access device for implementing the aforementioned network access method. The implementation solution provided by this device is similar to the implementation solution described in the aforementioned method. Therefore, the specific limitations in one or more network access device embodiments provided below can be found in the above-mentioned limitations on the network access method and will not be further elaborated here.

[0198] In one embodiment, as shown in FIG9 , a network access device 900 is provided, which is applied to a zero-power consumption device and includes: a first receiving module 902 and a second receiving module 904 , wherein:

[0199] The first receiving module 902 is configured to receive a terminal capability query request and send the terminal capability of the target zero-power device, where the terminal capability includes one or more of a device identification attribute, a group identification attribute, and a node type attribute;

[0200] The second receiving module 904 is configured to receive a target group identifier, update the terminal capability based on the target group identifier, receive a target communication scheduling policy, and communicate with the network based on the target communication scheduling policy.

[0201] In one embodiment, the first receiving module is specifically configured to:

[0202] A terminal capability query request is received from a network via an intermediate node device, and terminal capabilities of a target zero-power consumption device are sent to the intermediate node device, where the target zero-power consumption device is the current device.

[0203] In one embodiment, the first receiving module is further configured to:

[0204] A terminal capability query request sent by a network is received, and the terminal capability of the zero-power consumption device is sent to the network, where the target zero-power consumption device is the current device.

[0205] In one embodiment, the zero-power consumption device is an intermediate node device, and the first receiving module is further specifically configured to:

[0206] Receive terminal capability query request sent by the network,

[0207] Sending the terminal capability query request to the zero-power device connected to the intermediate node device;

[0208] The terminal capability sent by the zero-power consumption device connected to the intermediate node device is received, and the terminal capability of the zero-power consumption device connected to the intermediate node device is sent to the network, wherein the target zero-power consumption device is the zero-power consumption device connected to the intermediate node device.

[0209] In one embodiment, the terminal capability includes at least a group identification attribute; and the second receiving module is specifically configured to:

[0210] The target group identifier is determined to be the updated group identifier attribute in the terminal capability.

[0211] In one embodiment, the terminal capability does not include a group identification attribute; and the second receiving module is further configured to:

[0212] A group identification attribute is newly added to the terminal capability, and the target group identification is determined to be the updated group identification attribute in the terminal capability.

[0213] In one embodiment, the second receiving module is further configured to:

[0214] Sending a zero-power terminal registration request based on the target communication scheduling strategy; the zero-power terminal registration request is used to instruct the network to process the registration request;

[0215] Receive a registration response message for a registration request to communicate with the network.

[0216] In one embodiment, as shown in FIG10 , a network access device 1000 is provided, which is applied to a network and includes: a first sending module 1002 , a third receiving module 1004 , and a first determining module 1006 , wherein:

[0217] A first sending module 1002 is configured to send a terminal capability query request;

[0218] The third receiving module 1004 is configured to receive terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute;

[0219] The first determination module 1006 is used to determine the target group identifier corresponding to the target zero-power device based on the contract information of the target zero-power device, determine the target communication scheduling policy associated with the target zero-power device, and send the target group identifier and the target communication scheduling policy.

[0220] In one embodiment, the zero-power consumption device is an intermediate node device; the third receiving module is specifically used to receive the terminal capability of the target zero-power consumption device sent by the intermediate node device, and the target zero-power consumption device is the zero-power consumption device connected to the intermediate node device.

[0221] In one embodiment, the first determination is specifically used to:

[0222] Determining, based on the contract information of the target zero-power consumption device, a target group identifier corresponding to the target zero-power consumption device and a target communication scheduling strategy for the target zero-power consumption device;

[0223] The target group identifier corresponding to the target zero-power consumption device and the target communication scheduling strategy are sent to the intermediate node device; the target group identifier is used to instruct the intermediate node device to send the target group identifier to the target zero-power consumption device; the target communication scheduling strategy is used to instruct the intermediate node device to send the target communication scheduling strategy to the target zero-power consumption device.

[0224] In one embodiment, the apparatus further comprises:

[0225] A generating module, configured to generate a communication scheduling strategy corresponding to the intermediate node device after receiving the terminal capability of the target zero-power device sent by the intermediate node device;

[0226] The second sending module is configured to send the communication scheduling policy corresponding to the intermediate node device to the intermediate node device.

[0227] In one embodiment, the first determination is specifically used to:

[0228] Obtaining first contract information corresponding to the intermediate node device and second contract information of the target zero-power consumption device;

[0229] If it is determined that the requirements are met based on the first contract information and the second contract information, a corresponding relationship between the intermediate node device and the target zero-power consumption device is established;

[0230] Based on the second subscription information, a target group identifier corresponding to the target zero-power consumption device is determined.

[0231] Each module in the aforementioned network access device may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0232] In one embodiment, a network access system is provided. The network access system includes at least a zero-power consumption device and a network, wherein:

[0233] Network, used to send terminal capability query requests;

[0234] A zero-power device, configured to receive a terminal capability query request and send terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute;

[0235] The network is further configured to receive the terminal capabilities of the target zero-power device, determine the target group identifier corresponding to the target zero-power device based on the contract information of the target zero-power device, determine the target communication scheduling policy associated with the target zero-power device, and send the target group identifier and the target communication scheduling policy;

[0236] The zero-power device is further used to receive a target group identifier, update terminal capabilities based on the target group identifier, and receive a target communication scheduling strategy, and access the network based on the target communication scheduling strategy.

[0237] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in FIG11 . The computer device includes a processor, a memory, and a network interface connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store relevant data of the zero-power device and network data. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a network access method is implemented.

[0238] Those skilled in the art will understand that the structure shown in FIG11 is merely a block diagram of a portion of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0239] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0240] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0241] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0242] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0243] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0244] The technical features of the above-mentioned embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above-mentioned embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0245] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A network access method, applied to a zero-power consumption device, comprising: Receive a terminal capability query request, and send the terminal capability of the target zero-power device, where the terminal capability includes one or more of a device identification attribute, a group identification attribute, and a node type attribute; as well as A target group identifier is received, the terminal capability is updated based on the target group identifier, and a target communication scheduling strategy is received, and the network is communicated based on the target communication scheduling strategy.

2. The method according to claim 1, wherein: The target zero-power consumption device is the present device, and the receiving terminal capability query request and sending the terminal capability of the target zero-power consumption device include: A terminal capability query request is received from the network through an intermediate node device, and the terminal capability of the target zero-power consumption device is sent to the intermediate node device.

3. The method according to claim 1, wherein: The target zero-power consumption device is this device; The receiving terminal capability query request and sending the terminal capability of the target zero-power consumption device includes: A terminal capability query request sent by a network is received, and the terminal capability of the zero-power consumption device is sent to the network.

4. The method according to claim 1, wherein: The zero-power consumption device is an intermediate node device; the target zero-power consumption device is a zero-power consumption device connected to the intermediate node device; The receiving terminal capability query request and sending the terminal capability of the target zero-power consumption device includes: Receiving a terminal capability query request sent by the network; Sending the terminal capability query request to the zero-power device connected to the intermediate node device; and The terminal capability sent by the zero-power consumption device connected to the intermediate node device is received, and the terminal capability of the zero-power consumption device connected to the intermediate node device is sent to the network.

5. The method according to claim 1, wherein: The terminal capability at least includes the group identifier attribute; and updating the terminal capability based on the target group identifier includes: The target group identifier is determined to be the updated group identifier attribute in the terminal capability.

6. The method according to claim 1, wherein: The terminal capability does not include the group identifier attribute; and updating the terminal capability based on the target group identifier includes: A group identification attribute is newly added to the terminal capability, and the target group identification is determined to be the updated group identification attribute in the terminal capability.

7. The method according to claim 1, wherein: The communicating with the network based on the target communication scheduling strategy includes: Based on the target communication scheduling strategy, sending a zero-power consumption terminal registration request; the zero-power consumption terminal registration request is used to instruct the network to perform registration request processing; and A registration response message is received to the registration request to communicate with the network.

8. The method according to any one of claims 1 to 7, wherein: The node type attributes include a first device type, a second device type, and a third device type, wherein the first device type is an Internet of Things device that communicates with a base station, the second device type is an intermediate node device, and the third device type is an Internet of Things device that communicates with the base station via the intermediate node device.

9. The method according to any one of claims 1 to 7, wherein: The network is an access network or a core network.

10. The method according to claim 9, wherein the access network comprises a base station and an access gateway.

11. A network access method, wherein: Applied to a network, the method comprises: Send a terminal capability query request; Receive terminal capabilities of a target zero-power device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute; Based on the contract information of the target zero-power-consumption device, determining a target group identifier corresponding to the target zero-power-consumption device, and determining a target communication scheduling strategy associated with the target zero-power-consumption device; and The target group identifier and the target communication scheduling strategy are sent.

12. The method according to claim 11, wherein: The terminal capability of the receiving target zero-power consumption device includes: The terminal capability of the target zero-power consumption device sent by the intermediate node device is received, where the target zero-power consumption device is a zero-power consumption device connected to the intermediate node device.

13. The method according to claim 12, wherein: The method of determining a target group identifier corresponding to the target zero-power consumption device based on the contract information of the target zero-power consumption device, determining a target communication scheduling strategy associated with the target zero-power consumption device, and sending the target group identifier and the target communication scheduling strategy includes: Based on the contract information of the target zero-power-consumption device, determining a target group identifier corresponding to the target zero-power-consumption device and a target communication scheduling strategy for the target zero-power-consumption device; and The target group identifier corresponding to the target zero-power consumption device and the target communication scheduling policy are sent to the intermediate node device; the target group identifier is used to instruct the intermediate node device to send the target group identifier to the target zero-power consumption device; the target communication scheduling policy is used to instruct the intermediate node device to send the target communication scheduling policy to the target zero-power consumption device.

14. The method according to claim 12, wherein: The method further comprises: After receiving the terminal capability of the target zero-power device sent by the intermediate node device, generating a communication scheduling strategy corresponding to the intermediate node device; and Sending a communication scheduling policy corresponding to the intermediate node device to the intermediate node device.

15. The method according to claim 13, wherein: The determining, based on the contract information of the target zero-power consumption device, a target group identifier corresponding to the target zero-power consumption device includes: Acquire first subscription information corresponding to the intermediate node device and second subscription information of the target zero-power consumption device; If it is determined that the requirements are met based on the first contract information and the second contract information, a corresponding relationship between the intermediate node device and the target zero-power consumption device is established; and Based on the second signing information, a target group identifier corresponding to the target zero-power consumption device is determined.

16. The method according to any one of claims 11 to 15, wherein: The network is an access network or a core network. The method according to claim 16 , wherein the access network comprises a base station and an access gateway.

18. A network access device, wherein: Applied to zero-power consumption equipment, the device comprises: A first receiving module, configured to receive a terminal capability query request and send terminal capabilities of a target zero-power device, wherein the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute; and The second receiving module is used to receive a target group identifier, update the terminal capability based on the target group identifier, receive a target communication scheduling strategy, and communicate with the network based on the target communication scheduling strategy.

19. A network access device, wherein: Applied to a network, the device comprises: A first sending module, used for sending a terminal capability query request; A third receiving module is used to receive terminal capabilities of a target zero-power consumption device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute; and The first determination module is used to determine the target group identifier corresponding to the target zero-power consumption device based on the contract information of the target zero-power consumption device, determine the target communication scheduling policy associated with the target zero-power consumption device, and send the target group identifier and the target communication scheduling policy.

20. A network access system, wherein: The network access system at least includes a zero-power consumption device and a network, wherein: The network is used to send a terminal capability query request; The zero-power consumption device is used to receive a terminal capability query request and send the terminal capability of the target zero-power consumption device, wherein the terminal capability includes one or more of a device identification attribute, a group identification attribute, and a node type attribute; The network is further used to receive the terminal capability of the target zero-power consumption device, determine the target group identifier corresponding to the target zero-power consumption device based on the contract information of the target zero-power consumption device, and determine the target communication scheduling policy associated with the target zero-power consumption device, and send the target group identifier and the target communication scheduling policy; and The zero-power consumption device is further used to receive a target group identifier, update the terminal capability based on the target group identifier, and receive a target communication scheduling strategy, and access the network based on the target communication scheduling strategy.

21. A communication device, wherein: include: transmitter, processor, and receiver; The receiver is used to receive a terminal capability query request; The transmitter is used to send the terminal capabilities of the target zero-power consumption device, where the terminal capabilities include one or more of a device identification attribute, a group identification attribute, and a node type attribute; The processor is further configured to receive a target group identifier through the receiver, update the terminal capability based on the target group identifier, and receive a target communication scheduling strategy through the receiver, and communicate with the network based on the target communication scheduling strategy.

22. A computer-readable storage medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 14 are implemented.

23. A computer program product comprising a computer program, wherein: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 14 are implemented.

Images