Device access method, network device, storage medium and computer program product

Abstract

The invention provides a device access method, a network device, a storage medium and a computer program product. The method comprises the following steps: acquiring one or more first data type information reported by a first device and / or one or more second data type information reported by a second device in a coverage area of the network device; sequentially configuring first resource information for the first equipment corresponding to each type of first data type information in the reported one or more types of first data type information, so that the first equipment can access the network equipment in a non-competitive manner based on the first resource information; and / or sequentially configuring second resource information for the second equipment corresponding to each piece of second data type information in the reported one or more pieces of second data type information, so that the second equipment competes to access the network equipment based on the second resource information.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a device access method, network device, storage medium, and computer program product. Background Technology

[0002] In related technologies, Ambient Internet of Things (A-IoT) random access technology is mainly divided into two types: non-contention-based random access and contention-based random access. During the access process, if tags contain multiple types of data (e.g., A, B, and C data simultaneously), these tags must randomly select uplink scheduling resources. When multiple tags select the same resource, a collision occurs, directly leading to access failure. This collision probability increases significantly, especially in scenarios with a large number of tags, severely impacting the success rate of normal tag access. Summary of the Invention

[0003] In view of this, embodiments of this application provide a device access method, a network device, a storage medium, and a computer program product, which can improve the success rate of tag access.

[0004] The technical solution of this application is implemented as follows: In a first aspect, this application provides a device access method, applied to a network device, the method comprising: Obtain one or more types of first data type information reported by a first device within the network device coverage area, and / or one or more types of second data type information reported by a second device; Configure first resource information for each type of first data type information that reports one or more types of first data type information in sequence, so that the first device can access the network device without contention based on the first resource information; And / or, configure second resource information for each of the second data types of information reported by the second device, so that the second device can compete for access to the network device based on the second resource information.

[0005] Secondly, this application provides a network device, the network device comprising: The acquisition unit is used to acquire one or more types of first data type information reported by a first device within the coverage area of ​​the network device, and / or one or more types of second data type information reported by a second device; The configuration unit is configured to configure first resource information for a first device that reports one or more first data types of information, for each type of first data type, so that the first device can access the network device without contention based on the first resource information; and / or, configure second resource information for a second device that reports one or more second data types of information, for each type of second data type, so that the second device can access the network device competitively based on the second resource information.

[0006] Thirdly, this application provides a network device, which includes a processor and a memory; the processor executes a running program stored in the memory to implement the above-described device access method.

[0007] Fourthly, this application provides a storage medium on which a computer program is stored, which, when executed by a processor, implements the above-described device access method.

[0008] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the above-described device access method.

[0009] This application provides a device access method, a network device, a storage medium, and a computer program product. The method includes: acquiring one or more first data type information reported by a first device within the coverage area of ​​the network device, and / or one or more second data type information reported by a second device; sequentially configuring first resource information for the first device corresponding to each of the reported one or more first data type information, so that the first device can access the network device non-contentiously based on the first resource information; and / or sequentially configuring second resource information for the second device corresponding to each of the reported one or more second data type information, so that the second device can access the network device competitively based on the second resource information. Using the above implementation scheme, for the first device and the second device under the coverage of the network device, the first data type information reported by the first device and the second data type information reported by the second device are determined respectively. For the first device, according to different first data type information, corresponding first resource information is configured for the first device, and the first device accesses the network device non-contentiously based on the corresponding first resource information. For the second device, according to different second data type information, corresponding second resource information is configured for the second device, and the second device accesses the network device competitively based on the corresponding second resource information. It is evident that the first and second devices use different access resources. The first and second devices, which report information of different data types, also use different access resources. Therefore, dividing the access resources of the first and second devices can effectively avoid collisions when the first and second devices of different data types access the network devices, thereby improving the success rate of access for the first and second devices. Attached Figure Description

[0010] Figure 1 A flowchart illustrating a non-contention-based random access method between a base station and a tag; Figure 2 This is a flowchart illustrating a contention-based random access process between a base station and a tag. Figure 3 This is an example of tag information for a base station coverage area before a new tag is added; Figure 4 This is an example of tag information for a base station coverage area after a new tag is added; Figure 5 A schematic flowchart illustrating a device access method provided in an embodiment of this application; Figure 6 This is a schematic diagram of the overall process of a device access method provided in an embodiment of this application; Figure 7 A schematic diagram of the composition structure of a network device provided in this application embodiment. Figure 1 ; Figure 8 A schematic diagram of the composition structure of a network device provided in this application embodiment. Figure 2 . Detailed Implementation

[0011] To gain a more detailed understanding of the features and technical content of the embodiments of this application, the technical solution of this application will be further described in detail below with reference to the accompanying drawings and specific embodiments. The accompanying drawings are for reference only and are not intended to limit the embodiments of this application.

[0012] Unless otherwise defined, all technical and scientific terms used in the embodiments of this application have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the embodiments of this application is for the purpose of describing the embodiments of this application only and is not intended to limit this application.

[0013] In the following description, references to "some embodiments" refer to a subset of all possible embodiments. It is understood that "some embodiments" may be the same or different subsets of all possible embodiments and may be combined with each other without conflict. It should also be noted that the terms "first / second / third" used in the embodiments of this application are merely for distinguishing similar objects and do not represent a specific ordering of objects. It is understood that "first / second / third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein.

[0014] In related technologies, Ambient Internet of Things (A-IoT) random access technology is mainly divided into two types: non-contention random access and contention random access. The distinction between non-contention random access and contention random access is primarily indicated by the third bit of the A-IoT paging message.

[0015] (1) For non-contention-based random access: The base station indicates the length of the paging message identifier (which can be expressed as Length of Paging ID), the Paging ID (similar to the tag's unique Application Specific ID (AS ID)), and uplink air interface resources. When a tag matches this Paging ID, it sends relevant data (such as Protocol Control (PC) and Electronic Product Code (EPC)) to the base station via uplink air interface resources. If the data is not completely sent, the tag instructs the base station to continue scheduling the tag via the second bit of the Device to Reader Upper Layer Data Transfer message (which can be expressed as D2R UpperLayer Data Transfer message).

[0016] The specific process is as follows: Figure 1 , Figure 1 A flowchart illustrating non-contention-based random access between a base station (such as a gNB) and a tag.

[0017] It should be noted that gNB is equivalent to a reader (which can be abbreviated as R), and the tag is equivalent to the device to be read (which can be abbreviated as D).

[0018] Should Figure 1 It includes step 1: the base station sends an A-IoT Paging message to the tag, and step 2: the tag sends a D2R Upper Layer Data Transfer message to the base station.

[0019] The content of the A-IoT Paging message is shown in Table 1 below.

[0020] The content of the D2R Upper Layer Data Transfer message is shown in Table 2 below.

[0021] Table 1

[0022] In Table 1, CFRA stands for Contention-Free Random Access.

[0023] Table 2

[0024] The aforementioned D2R scheduling info section (which can be expressed as "field" in English) consists of the physical layer parameters for D2R scheduling, mainly including: 1. Frequency domain resources of MSG1 and MSG3 (occupying 3 bits).

[0025] 2. Similar to MCS modulation and coding scheme (MCS) information (D2R transport block (TB) size) (occupies 7 bits).

[0026] 3. D2R Chip duration (3 bits). This refers to the duration of each D2R bit, measured in microseconds.

[0027] 4. Whether to perform block-level repetition, and how to do it (occupies 1 bit).

[0028] 5. Whether to perform forward error correction (FEC) (1 bit).

[0029] 6. Midamble and peramble length, i.e., D2R leader / middle sequence length indicators, are 7 bits or 31 bits (occupying 1 bit).

[0030] 7. The insertion interval of the Midamble (occupies 2 bits).

[0031] 8. Whether the DR2 instruction ends with a midamble (occupying 1 bit).

[0032] (2) For contention-based random access: The A-IoT Paging message indicates a Transaction ID (activation group, similar to an Ultra High Frequency Radio Frequency Identification Session, UHF RFID Session). When a tag matches this Transaction ID, it randomly selects uplink air interface resources and sends a randomly generated random ID to the base station. Upon receiving the Random ID, the base station confirms the Random ID via a Random ID Response message and configures the relevant AS ID and uplink air interface resources. When a tag matches this Random ID, it sends relevant data (such as PC, EPC) to the base station via uplink air interface resources. If the data is not completely transmitted, the tag instructs the base station to continue scheduling tags via the second bit of the D2R Upper Layer DataTransfer message. Specifically... Figure 2 , Figure 2 A flowchart illustrating the contention for random access between a base station (such as a gNB) and a tag.

[0033] Should Figure 2 The process includes: Step 1: gNB sends A-IoT Paging message to Tag; Step 2: Tag sends Random ID message to gNB; Step 3: gNB sends Random ID Response message to Tag; Step 4: Tag sends D2R data transfer message to gNB.

[0034] The content of the A-IoT Paging message is shown in Table 3 below, the content of the Random ID message is shown in Table 4 below, and the content of the Random ID Response message is shown in Table 5 below.

[0035] Table 3

[0036] Among them, CBRA stands for Contention-Based Random Access.

[0037] Number of Access Occasions: The number of access occupancy periods.

[0038] Table 4

[0039] Table 5

[0040] In the 3rd Generation Partnership Project (3GPP), three types of tags, namely Class A data, Class B data, and Class C data, are supported for reporting. Among them, Class A tags can perform backscatter communication, but have no independent signal generation and amplification capabilities, such as RFID tags. Class B tags have backscatter communication and energy storage, but no independent signal generation capabilities, and support the amplification of the tag's reverse signal. They are between Class A and Class C and belong to semi-active tags. Class C tags support independent signal generation, and the power consumption is in the milliwatt level. The communication capabilities of the three types are ranked from small to large as Class A < Class B < Class C.

[0041] When a new tag joins within the base station coverage area, the base station is in a non-perceptive state. It can neither pre-obtain the type information of the tag nor identify the device identifier (i.e., ID) of the newly joined tag, and it needs to rely on the access interaction initiated by the base station to complete subsequent cognition. Therefore, the base station needs to inventory the new tags through a competitive random access method. As Figure 3 shown, it is an exemplary tag information in the base station coverage area before the new tag joins. Figure 4 It is an exemplary tag information in the base station coverage area after the new tag joins.

[0042] If, during the process of the tag accessing the base station, tags reporting multiple data types are mixed, for example, tags reporting Class A data, Class B data, and Class C data can exist simultaneously, the existing technical drawbacks are relatively prominent. Specifically, the tag needs to randomly select uplink scheduling resources according to a specific algorithm. When multiple tags select the same resource, a collision will occur, directly resulting in access failure. Especially when the number of tags is large, the probability of such a collision will increase significantly, thereby seriously affecting the normal access of the tags. From the perspective of communication capabilities, tags of Class A data have relatively weak communication capabilities themselves, and are less capable of coping with collisions when facing resource competition, and the possibility of access failure is relatively higher; although the communication capabilities of tags of Class B data and Class C data increase in sequence, in the scenario where the number of tags is too large, it is still difficult to avoid access problems caused by resource collisions.

[0043] To solve the above problems, in the embodiments of the present application, a device access method is proposed to improve the utilization rate of spectrum resources and reduce the risk of access failure based on relevant cellular passive communication, and improve the access success rate.

[0044] The detailed technical solutions of this application embodiment are as follows: This application provides a device access method, such as... Figure 5 As shown, when applied to network devices, the method may include: S501. Obtain one or more types of first data type information reported by the first device within the coverage area of ​​the network device, and / or one or more types of second data type information reported by the second device.

[0045] In this embodiment, the network device can be a base station or other devices with tag access functionality. Specifically, the choice can be made according to the actual situation, and no specific limitation is made in this embodiment.

[0046] In this embodiment of the application, the first device may include all tags that the base station has already stored.

[0047] In this embodiment of the application, the second device may include all tags that the base station has not stored, which can be understood as tags newly added within the coverage area of ​​the base station.

[0048] In the embodiments of this application, one or more first data type information may include one or more of type A data, type B data, and type C data.

[0049] It should be noted that, in addition to the three types of data listed above (A, B, and C), the first data type information can also include other types of data, which can be determined according to the actual situation.

[0050] In this application embodiment, one or more second data type information may include one or more of type A data, type B data, and type C data.

[0051] It should be noted that, in addition to the three types of data listed above (A, B, and C), the second data type information can also include other types of data, which can be determined according to the actual situation.

[0052] In this embodiment, the first device is a tag previously stored by the base station. When the base station obtains one or more types of first data type information reported by the first device within the coverage area, it can determine the one or more types of first data type information reported by all previously stored tags by using the historical first data type information of the tags previously stored by the base station. For example, if the tags previously stored by the base station include tag 1, tag 2, and tag 3, and the tags report type a data, tag 1 reports type b data, and tag 3 reports type c data, then the base station can determine the data type information reported by the tags previously stored within the coverage area based on the aforementioned historical reported data type information.

[0053] In this embodiment of the application, the second data type information of the second device can be obtained by the second device actively reporting to the base station, or by the base station indicating to the second device the competition for resources of tags of different data types.

[0054] In this embodiment, the A-IoT Paging message for contention-based random access indicates whether access resources for tags of different data types are reported. Specifically, in the A-IoT Paging message for contention-based random access, the 7th bit indicates whether access resources for tags of different data types are divided within the A-IoT Paging message.

[0055] In this context, 0 represents "no," meaning no indication of data type is given, such as only indicating {number of accesses and scheduling information}. In this case, the second device can actively report the data. 1 represents "yes," meaning an indication of data type is given, such as {number of accesses, data type, and scheduling information}. In this case, the base station can indicate the competing resources of tags with different data types to the second device, where the order of the number of accesses and data types is not restricted. Specifically, the implementation can be done in the following two ways: In one embodiment of this application, obtaining one or more types of second data information reported by a second device within the coverage area of ​​a network device is achieved using the following method: Send first information to a second device and receive second information sent by the second device based on the first information, wherein the second information carries second data type information of the second device; obtain one or more second data type information of the second device from the second information.

[0056] In this embodiment of the application, if there are newly added tags in the coverage area of ​​the base station, that is, tags that the base station has not stored, the base station needs to obtain the second data type reported by the newly added tags, which is achieved by the tags actively reporting their own data type information to the base station.

[0057] In this embodiment of the application, the first information is the A-IoT Paging message.

[0058] In this embodiment of the application, the second information is the Random ID message.

[0059] In this embodiment, the base station sends a contention-based random access A-IoT Paging message to the second device. In this A-IoT Paging message, there is no indication of access resources of different data types (i.e., the indication information is 0). Several extra bits are reserved in the D2R Scheduling Info for the transport block size (TB) to be carried by the tag (i.e., the second device) when sending the Random ID message to the base station.

[0060] The base station identifies the data type or data type and size reported by the tag by receiving the Random ID message (the order of data type and data size is not restricted), and then optimizes the subsequent data reporting process according to different data types.

[0061] The A-IoT Paging message (data type not specified here) includes the following content as shown in Table 6.

[0062] The Random ID message includes the following content as shown in Tables 7 and 8 below. Table 7 corresponds to the data type of the message itself, and Table 8 corresponds to the data type and size of the message itself.

[0063] Table 6

[0064] Among them, Data Type Indication is the data type indicator. Table 7

[0065] Table 8

[0066] It should be noted that Tables 6, 7 and 8 above are only examples, and the parameters indicated by each bit can be selected according to the actual situation. No specific limitations are made in the embodiments of this application.

[0067] It should be noted that the number of bits occupied by parameters such as D2R Scheduling Info and Random ID in the table is not limited to the examples given in the embodiments of this application. Specifically, the selection can be made according to the actual situation.

[0068] Alternatively, one or more types of second-type data information reported by a second device within the network device's coverage area can be obtained using the following method two: Send first information to the second device, wherein the first information carries data type information and scheduling resources corresponding to the data type information; receive third information sent by the second device based on the scheduling resources, and obtain one or more second data type information of the second device based on the scheduling resources used by the second device to send the third information.

[0069] In this embodiment, the base station sends an A-IoT Paging message to the second device (i.e., all tags that have not been inventoried). The A-IoT Paging message indicates tags of different data types and their corresponding allocated scheduling resources. After receiving the A-IoT Paging message, the tag autonomously selects air interface resources from the corresponding scheduling resource group specified in the A-IoT Paging message and initiates contention for access based on the data attributes it reports. The base station receives the signal sent by the tag through the corresponding scheduling resource, and determines and confirms the data type that the tag needs to report by identifying the resource information used when the tag sends the signal (i.e., the third information). The base station optimizes the subsequent data reporting process according to different data types.

[0070] For example, the A-IoT Paging message indicates that Class A data uses scheduling resource 1 and Class B data uses scheduling resource 2. If tag 1 uses scheduling resource 1 for signal transmission, the base station can determine that tag 1 is reporting Class A data based on the scheduling resource 1 used by tag 1 when transmitting the signal. In this way, it is possible to confirm which type of data each tag is reporting.

[0071] In this case, the content indicated in the A-IoT Paging message is shown in Table 9 below.

[0072] It should be noted that Table 9 is only an example, and the parameters indicated by each bit can be selected according to the actual situation. No specific limitations are made in this embodiment.

[0073] It should be noted that the number of bits occupied by parameters such as D2R Scheduling Info and Number of Access Occasions in the table is not limited to the examples given in the embodiments of this application. Specifically, the selection can be made according to the actual situation.

[0074] Table 9

[0075] The values ​​and descriptions corresponding to Data Type are shown in Table 10 below: Table 10

[0076] S502, configure first resource information for each type of first data type information that reports one or more types of first data type information, so that the first device can access the network device without contention based on the first resource information; and / or, configure second resource information for each type of second data type information that reports one or more types of second data type information, so that the second device can access the network device competitively based on the second resource information.

[0077] In this embodiment of the application, the first data types reported by all the first devices that the base station has stored include Class A data, Class B data and Class C data as examples for illustration.

[0078] In this embodiment, the base station configures first uplink scheduling resources for tags that report Class A data, Class B data, and Class C data in sequence. Tags that report Class A data access the base station using the first uplink scheduling resources configured for the first device that reports Class A data, and access the base station in a non-contention access manner. Tags that report Class B data access the base station using the first uplink scheduling resources configured for the first device that reports Class B data, and access the base station in a non-contention access manner. Tags that report Class C data access the base station using the first uplink scheduling resources configured for the first device that reports Class C data, and access the base station in a non-contention access manner.

[0079] In this embodiment of the application, if there are tags (i.e., second devices) that have not been stored by the base station within the base station coverage area, the second data types reported by all second devices that have not been stored by the base station include Class A data, Class B data, and Class C data as an example for explanation.

[0080] In this embodiment, the base station configures second uplink scheduling resources for tags that report Class A data, Class B data, and Class C data in sequence. Tags that report Class A data use the second uplink scheduling resources configured for the second device that reports Class A data to access the base station in a contention-based access manner. Tags that report Class B data use the second uplink scheduling resources configured for the second device that reports Class B data to access the base station in a contention-based access manner. Tags that report Class C data use the second uplink scheduling resources configured for the second device that reports Class C data to access the base station in a contention-based access manner.

[0081] It should be noted that if only unstored tags exist, i.e. only the second device exists, then it is only necessary to execute the process of configuring the second uplink scheduling resource for the second device, and the second device accessing the network based on the second uplink scheduling resource.

[0082] It should be noted that if only the tags that have been stored exist, that is, only the first device exists, then it is only necessary to execute the process of configuring the first uplink scheduling resource for the first device and the first device accessing the network based on the first uplink scheduling resource.

[0083] It should be noted that if a first device and a second device exist, the process of configuring a first uplink scheduling resource for the first device and a second uplink scheduling resource for the second device needs to be executed. The first device accesses the network based on the first uplink scheduling resource, and the second device accesses the network based on the second uplink resource.

[0084] It is understood that the device access method provided in this application embodiment, for a first device and a second device under the coverage of a network device, determines the first data type information reported by the first device and the second data type information reported by the second device, respectively. For the first device, corresponding first resource information is configured for each different first data type, and the first device accesses the network device non-contentiously based on the corresponding first resource information. For the second device, corresponding second resource information is configured for each different second data type, and the second device accesses the network device contentiously based on the corresponding second resource information. It is evident that the first device and the second device use different access resources, and the first device and the second device reporting different data types of information also use different access resources. Thus, dividing the access resources for the first device and the second device can effectively avoid collisions when the first device and the second device with different data types access the network device, improving the success rate of access for both devices.

[0085] In one embodiment of this application, first resource information is configured for each type of first data type information that reports one or more types of first data type information in sequence, specifically implemented in the following manner: Determine the priority corresponding to each type of first data type, and determine the first access priority order corresponding to the first device for each type of first data type based on the priority; configure the first resource information for the first device in sequence according to the first access priority order.

[0086] In this embodiment of the application, the base station first determines the priority of each type of first data type information reported according to a preset data type priority order. For example, the priority of type A data is set to be higher than that of type B data, the priority of type B data is higher than that of type C data, and the priority of type C data is higher than that of type D data. If the first data type information reported by all first devices in the coverage area of ​​the base station includes type A data, type B data, and type C data, then it can be determined that the priority of type A data is higher than that of type B data, and the priority of type B data is higher than that of type C data.

[0087] In this embodiment, after determining the priority of each type of first data type reported, the access priority of the first device reporting type A data is determined to be higher than that of the first device reporting type B data, and the access priority of the first device reporting type B data is higher than that of the first device reporting type C data, according to the aforementioned priority order. For example, if the first devices reporting type A data are tags 1, 3, and 4, the first device reporting type B data is tag 2, and the first devices reporting type C data are tags 5 and 6, then the access priority of tags 1, 3, and 4 is higher than that of tag 2, and the access priority of tag 2 is higher than that of tags 5 and 6.

[0088] In this embodiment, according to the above method, when a base station accesses a tag that has already reported (or has been stored), the base station first sorts the tags according to the priority of the first data type information from high to low, such as high-level (A), medium-level (B), and low-level (C). This determines the access priority order of the first device reporting different data types of information based on priority. When the first device accesses, i.e., for tags that have already been stored, a non-contention-based random access method is used to perform the first round of storage, such as first issuing a paging ID and corresponding uplink scheduling resources to the tags that have already been stored. Specifically, the base station prioritizes allocating dedicated uplink resources to tags that need to report Class A data, and clarifies the mapping relationship between the Paging ID and the resources through downlink signaling; subsequently, the same processing is performed for tags reporting Class B data and Class C data in sequence.

[0089] It should be noted that, since the above implementation method adopts a non-competitive mechanism, there is no need for tags to compete for resources (such as between tags reporting type A data and between tags reporting type B data). Dedicated uplink scheduling resources can be matched based on the pre-allocated Paging ID to initiate access in an orderly manner.

[0090] In this embodiment, when configuring the first resource information for the first device in sequence according to the first access priority, a switching process for configuring the first resource information can be automatically initiated using a dynamic threshold triggering method. Specifically, this will be explained using the example of the first device including a first type of device, a second type of device, and a third type of device.

[0091] The first type of equipment can be understood as equipment that reports Class A data, the second type of equipment can be understood as equipment that reports Class B data, and the third type of equipment can be understood as equipment that reports Class C data.

[0092] In one embodiment of this application, the first resource information is configured for the first device in accordance with the first access priority order, specifically implemented in the following manner: If the number of devices of the first type is greater than the first threshold, configure the corresponding first resource information for the devices of the first type; if the number of devices of the first type is less than or equal to the first threshold and the number of devices of the second type is greater than the second threshold, configure the corresponding first resource information for the target devices of the second type; if the number of devices of the second type is less than or equal to the second threshold and the number of devices of the third type is greater than the third threshold, configure the corresponding first resource information for the devices of the third type.

[0093] Among them, the access priority of the first type of device is higher than that of the second type of device, and the access priority of the second type of device is higher than that of the third type of device.

[0094] In the embodiments of this application, the first threshold, the second threshold, and the third threshold are dynamic thresholds.

[0095] In this embodiment, the rapid switching of Class A, Class B, and Class C first resource information configurations under a non-contention mechanism is achieved primarily through a dynamic threshold triggering mechanism. This dynamic threshold triggering is an intelligent decision-making mechanism that automatically initiates the resource switching process based on real-time statistics of tag activity. The base station monitors the remaining active number of tags (i.e., the first device) in real time through a priority identifier interaction mechanism and presets multiple trigger thresholds. An example is a tag reporting Class A data: When the remaining number of tags reporting Class A data is less than or equal to the initial value ThrA, the resource allocation will automatically switch from the tags reporting Class A data to the tags reporting Class B data.

[0096] It should be noted that the ThrA threshold is not a fixed value, but is adjusted through dynamic calibration (such as based on the prediction of the label reduction rate over three historical cycles). If the rate of label reduction reported in Category A data accelerates, the threshold can be automatically increased to initiate the switchover in advance and avoid resource idleness. This ensures real-time matching between resource switching and changes in the number of labels, achieving a seamless transition where "high-priority labels are decommissioned and resources are released, while low-priority labels are taken over as needed."

[0097] It should be noted that the process of switching the tag resource configuration for reporting Category B data to the tag resource configuration for reporting Category C data can refer to the process of switching the tag resource configuration for reporting Category A data to the tag resource configuration for reporting Category B data, as described above, and will not be repeated here.

[0098] It should be noted that the setting of the first threshold (i.e., ThrA), the second threshold, and the third threshold can all refer to the setting method of the ThrA threshold mentioned above to achieve a dynamic adjustment process, which will not be elaborated here.

[0099] In one embodiment of this application, second resource information is configured for each type of second data type information in one or more second data type information, specifically implemented in the following manner: Determine the priority corresponding to each type of second data type information, and determine the second access priority order of the second device corresponding to each type of second data type information based on the priority; configure the second resource information for the second device in sequence according to the second access priority order.

[0100] In this embodiment of the application, the second resource information may include air interface resources.

[0101] In this embodiment, the base station determines the priorities corresponding to the second data type information reported by tags that have not been inventoried, and determines the second access priority order of the second device corresponding to each type of second data type information according to the priorities in the same way as the first access priority order for tags that have been inventoried in the aforementioned embodiment. Specifically: The base station first determines the priority of each type of secondary data information reported according to a preset data type priority order. For example, the priority of type A data is set to be higher than that of type B data, which is higher than that of type C data, which is higher than that of type D data. If the secondary data information reported by all secondary devices in the base station's coverage area includes type A, type B, and type C data, then it can be determined that the priority of type A data is higher than that of type B data, which is higher than that of type C data.

[0102] In this embodiment, after determining the priority of each type of second data information reported, the access priority of the second device reporting type A data is determined to be higher than that of the second device reporting type B data, and the access priority of the second device reporting type B data is higher than that of the second device reporting type C data, according to the aforementioned priority order. For example, if the second devices reporting type A data are tags 3 and 4, the first devices reporting type B data are tags 1 and 2, and the first device reporting type C data is tag 5, then the access priority of tags 3 and 4 is determined to be higher than that of tags 1 and 2, and the access priority of tags 1 and 2 is determined to be higher than that of tag 5.

[0103] In this embodiment, following the above method, when a base station accesses a tag that has not reported data, the base station first sorts the second data type information according to its priority from high to low, such as high-level (A), medium-level (B), and low-level (C). This determines the access priority order of the second devices reporting different data types based on priority. When the second device accesses, a contention-based random access method is used for data storage. Specifically, the base station prioritizes allocating uplink resources to tags that need to report type A data. These uplink resources are used for tags that have reported type A data to compete for access among all tags that have not yet reported data. Then, the same processing is performed on tags that report type B data and type C data in sequence.

[0104] It should be noted that, due to the use of a competition mechanism in the above implementation method, each tag needs to compete for resources to access the system.

[0105] In this embodiment, when configuring the second resource information for the second device according to the second access priority order, a dynamic threshold triggering method can be used to automatically initiate the switching process for configuring the second resource information. Specifically, this will be explained using the example of the second device including a first type of device, a second type of device, and a third type of device.

[0106] The first type of equipment can be understood as equipment that reports Class A data, the second type of equipment can be understood as equipment that reports Class B data, and the third type of equipment can be understood as equipment that reports Class C data.

[0107] In one embodiment of this application, the second resource information is configured for the second device in accordance with the second access priority order, specifically implemented in the following manner: If the number of devices of the first type is greater than the fourth threshold, configure the corresponding second resource information for the devices of the first type; if the number of devices of the first type is less than or equal to the fourth threshold and the number of devices of the second type is greater than the fifth threshold, configure the corresponding second resource information for the target devices of the second type; if the number of devices of the second type is less than or equal to the fifth threshold and the number of devices of the third type is greater than the sixth threshold, configure the second resource information for the devices of the third type.

[0108] Among them, the access priority of the first type of device is higher than that of the second type of device, and the access priority of the second type of device is higher than that of the third type of device.

[0109] In the embodiments of this application, the fourth threshold, the fifth threshold, and the sixth threshold are dynamic thresholds.

[0110] In this embodiment, the rapid switching of Class A, Class B, and Class C second resource information configurations under a competition mechanism can also be achieved through a dynamic threshold triggering mechanism. The base station monitors the remaining active number of tags (i.e., the second device) in real time through a priority identifier interaction mechanism and presets multiple trigger thresholds. An example is taken of all tags that have not reported data but are required to report Class A data: When the remaining number of tags reporting Class A data is less than or equal to the fourth threshold, the resource allocation will automatically switch from the tags reporting Class A data to the tags reporting Class B data.

[0111] It should be noted that the fourth threshold is not a fixed value and can be adjusted through dynamic calibration to ensure real-time matching between resource switching and changes in the number of tags.

[0112] It should be noted that the process of switching the tag resource configuration for reporting Category B data to the tag resource configuration for reporting Category C data can refer to the process of switching the tag resource configuration for reporting Category A data to the tag resource configuration for reporting Category B data, as described above, and will not be repeated here.

[0113] It should be noted that the setting of the fourth, fifth, and sixth thresholds can all be dynamically adjusted, which will not be elaborated here.

[0114] In one embodiment of this application, when the number of third-type devices is less than or equal to a sixth threshold, third resource information is configured for the second device so that the first-type devices, second-type devices and third-type devices included in the second device can compete for access to the network device based on the third resource information.

[0115] In this embodiment of the application, if the number of third-type devices is less than or equal to the sixth threshold, the second-type data information reported by the second device is not distinguished. The base station configures unified air interface resources for the second device, and all remaining second devices (such as second devices reporting A-type data, second devices reporting B-type data, second devices reporting C-type data, etc.) compete to access the base station based on the configured unified air interface resources.

[0116] In one embodiment of this application, when the number of first type devices is less than a seventh threshold, the first target resource information in the second resource information of the first type devices is reduced, and the first target resource information is added to the second resource information corresponding to the second type devices; when the number of second type devices is less than an eighth threshold, the second target resource information in the second resource information of the second type devices is reduced, and the second target resource information is added to the second resource information corresponding to the third type devices.

[0117] In this embodiment of the application, during the process of contention for random access, in order to avoid wasting resources, the configured second resource information can be dynamically adjusted.

[0118] In this embodiment, the seventh threshold and the eighth threshold can be selected according to the actual situation, and no specific limitation is made in this embodiment.

[0119] In this application embodiment, if the remaining number of first type devices is less than the seventh threshold, it means that the remaining number of first type devices is small. In this case, some resources in the second resource information configured for the first type devices can be reduced, and the reduced resources can be added to the second resource information of the second type devices.

[0120] In this application embodiment, if the remaining number of second type devices is less than the eighth threshold, it means that the remaining number of second type devices is small. In this case, some resources in the second resource information configured for the second type devices can be reduced to supplement the second resource information of the third type devices.

[0121] The following is a more detailed explanation of the above dynamic adjustment process: In this embodiment, one or more uplink scheduling resources are configured in the A-IoT Paging message for contention-based random access, based on the different reported data types of the second device. When adjusting the configured uplink scheduling resources, for example, when "the number of tags reporting type A data gradually decreases and the number of tags reporting type B data gradually increases," a multi-stage linkage strategy is used to achieve a smooth transition, ensuring that the resources for each type of tag dynamically adapt to the remaining quantity.

[0122] Phase 1: The number of tags reporting Category A data gradually decreases, while the number of tags reporting Category B data gradually increases. Triggering condition: The remaining number of labels in the reported Class A data is greater than a certain ratio of the initial number (ThrA_High).

[0123] Adjustment of uplink scheduling resources for tags reporting Class A data: The proportion decreases as the remaining quantity decreases, and the less remaining data, the faster the decrease, achieving dynamic decay.

[0124] Adjustment of uplink scheduling resources for tags reporting Category B data: Synchronously take over the resources reduced from Category A, gradually increasing the proportion, but not exceeding a certain upper limit ThrB.

[0125] Transition phase: The number of labels for reporting Category A data has decreased, while the number of labels for reporting Category B data remains sufficient. When the remaining quantity of tags reporting Class A data < ThrA_Low (i.e., the seventh threshold), but the remaining quantity of tags reporting Class B data ≥ ThrB_High, the tags reporting Class A data slowly decrease to the lowest proportion, and the tags reporting Class B data maintain a high proportion (to ensure the efficient access of tags reporting Class B data).

[0126] 2. Phase II: The tags reporting Class B data decrease, and the tags reporting Class C data increase (when the remaining tags reporting Class B data are less): Trigger condition: The remaining quantity of tags reporting Class B data < ThrB_Low (i.e., the eighth threshold).

[0127] Adjustment of the uplink scheduling resources of the tags reporting Class B data: The proportion decreases as the remaining quantity decreases, and the attenuation rate is slightly slower than that of Class A (to avoid mutations).

[0128] Adjustment of the uplink scheduling resources of the tags reporting Class C data: Synchronously take over the resources reduced by Class B, and the proportion gradually increases (automatically allocated by subtracting the resources of Class A and Class B from the total resources).

[0129] 3. Phase III: When the tags reporting Class C data decrease: Trigger condition: The remaining quantity of tags reporting Class C data < ThrC_Low.

[0130] At this time, the base station no longer accesses directly without distinguishing data types, but competes for access until the access time arrives and the access stops.

[0131] It should be noted that the tags in Phase I to Phase III are all tags that have not accessed the base station.

[0132] It should be noted that the above resource allocation mechanism has three significant advantages and can achieve efficient and fair resource allocation: 1. Smooth transition: Avoid resource mutations through dynamic attenuation factors and exponential moving averages.

[0133] 2. Adaptive adjustment: The speed of resource change is linked to the remaining number of devices reporting data (the more remaining, the smoother the adjustment; the less remaining, the more obvious the adjustment).

[0134] 3. Guarantee: Avoid any data type tags having no resources at all. When the resource requirements of high-priority tags are not saturated, the redundant resources are dynamically allocated to low-priority tags. This method can not only meet the resource demands of different priorities but also cover the basic resource needs of all tags reporting data types through the fallback mechanism, preventing the situation where a certain type of data is completely deprived of resources.

[0135] Based on the above embodiments, the embodiments of the present application also provide an overall flow schematic diagram of a device access method, as Figure 6As shown, the specific steps include: S1. The base station initiates tag access and begins resource scheduling.

[0136] S2. Are there any remaining tags that have been connected that are greater than the dynamic threshold 1? If yes, select the non-contention access method; if no, select the contention access method.

[0137] It should be noted that "connected tags" can be understood as either the first device or tags that have already been stored.

[0138] The non-contention-based access method includes the following steps: S3. Report whether the remaining amount of Class A data labels is greater than the dynamic threshold 2 (i.e., the first threshold). If yes, execute S4; otherwise, execute S5.

[0139] S4. Configure dedicated resources for reporting Class A data and initiate non-competitive access.

[0140] S5. Report whether the remaining amount of B-type data labels is greater than the dynamic threshold 3 (i.e., the second threshold). If yes, proceed to S6; otherwise, proceed to S7.

[0141] S6. Configure dedicated resources for reporting Class B data and initiate non-competitive access.

[0142] S7. Report whether the remaining amount of C-class data labels is greater than the dynamic threshold 4 (i.e., the third threshold). If yes, execute S8; if no, execute S2.

[0143] S8. Configure dedicated resources for reporting Class C data and initiate non-competitive access.

[0144] The competitive access method includes the following steps: S9. Report whether the remaining amount of Class A data labels is greater than the dynamic threshold 5 (i.e., the fourth threshold). If yes, execute S10; if no, execute S11.

[0145] S10. Configure air interface resources for reporting Class A data and initiate competitive access.

[0146] S11. Report whether the remaining amount of B-type data labels is greater than the dynamic threshold 6 (i.e., the fifth threshold). If yes, execute S12; if no, execute S13.

[0147] S12. Configure air interface resources for reporting Class B data and initiate competitive access.

[0148] S13. Report whether the remaining amount of C-class data labels is greater than the dynamic threshold 7 (i.e., the sixth threshold). If yes, execute S14; if no, execute S15 to S17.

[0149] S14. Configure air interface resources for reporting Class C data and initiate competitive access.

[0150] S15. Tags that report three types of data are allowed to compete for access.

[0151] S16. Configure unified air interface resources and initiate competitive access.

[0152] S17. Has the access time arrived? If yes, end; if no, execute S15 to S17.

[0153] It should be noted that the above example only illustrates the reporting of tags with three data types. This method is also applicable to the access of tags with more or fewer than three data types.

[0154] Based on the above embodiments, this application optimizes the passive random access method for tags, solving the collision problem during access for massive numbers of tags reporting different data types. It mainly involves the tag data type reporting process during contention-based random access, access methods for tags that have already been stored, and access methods for tags that have not been stored. Specifically, the tag data type reporting method has two approaches: one is to inform the tag of the air interface resource allocation in the A-IoT Paging message for contention-based random access using the format {number of accesses + data type + scheduling information}. After receiving the message, the tag will autonomously select air interface resources from the corresponding scheduling resource group specified in the message and initiate contention-based access based on its own data attributes. The base station then determines and confirms the tag's data type by identifying the resource information used when the tag sends signals. The other approach is to reserve a few extra bits in the TB size of the D2R SchedulingInfo when the base station sends the Random ID message if there is no {data type} indication. The tag then carries the reported data type or reported data type + data size when sending the Random ID message, facilitating subsequent optimization of tag scheduling by the base station.

[0155] For tags that have already reported data, the base station adopts a non-contention-based access mechanism. By using real-time statistics of active tags, it achieves rapid switching of tag sorting resource configurations for high-level (A), medium-level (B), and low-level (C) data types. For tags that have not reported data types, the base station adopts a contention-based access mechanism. It configures one or more uplink scheduling resources according to different data types, and gradually transitions to a contention-based access mode that does not distinguish between data types by progressively decreasing the number of tags reporting for A-type data and progressively increasing the number of tags reporting for B-type data. A multi-stage linkage strategy is employed to achieve smooth transition and adaptive adjustment of scheduling resources, resolving access problems caused by resource collisions in scenarios where tags with multiple priorities coexist and are numerous.

[0156] Compared with related technologies, the embodiments of this application have the following technical advantages: For passive tag-based data access scenarios, this method addresses access collisions caused by resource contention when a large number of tags with various priority data coexist. In practical applications, tags of different data types often have differentiated communication needs and capabilities. When a large number of tags simultaneously initiate access requests, traditional random access mechanisms are prone to resource allocation conflicts, leading to increased access latency, decreased success rate, and even prolonged network access failures for some tags. This embodiment of the application differentiates the priorities of reported A, B, and C types of data and employs dynamic resource allocation techniques to flexibly adjust resource allocation strategies based on the tag data reporting type and real-time access scale. This effectively reduces the probability of collisions, optimizes spectrum resource utilization, and ensures efficient and stable reporting of various data types even under large-scale concurrent scenarios.

[0157] Based on the above embodiments, another embodiment of this application provides a network device 1, such as... Figure 7 As shown, the network device 1 includes: The acquisition unit 10 is used to acquire one or more types of first data type information reported by the first device within the coverage area of ​​the network device, and / or one or more types of second data type information reported by the second device.

[0158] Configuration unit 11 is configured to configure first resource information for a first device that reports one or more first data types of information for each type of first data type, so that the first device can access the network device without contention based on the first resource information; and / or, configure second resource information for a second device that reports one or more second data types of information for each type of second data type, so that the second device can access the network device competitively based on the second resource information.

[0159] In one embodiment, network device 1 may further include: a transmitting unit and a receiving unit.

[0160] The sending unit is used to send the first information to the second device.

[0161] The receiving unit is used to receive second information sent by the second device based on the first information, wherein the second information carries second data type information of the second device.

[0162] The acquisition unit 10 is also used to acquire one or more second data type information of the second device from the second information.

[0163] Alternatively, the sending unit is further configured to send first information to the second device, wherein the first information carries data type information and scheduling resources corresponding to the data type information.

[0164] The receiving unit is also used to receive third information sent by the second device based on scheduling resources.

[0165] The acquisition unit 10 is also used to acquire one or more second data type information of the second device based on the scheduling resources used by the second device to send the third information.

[0166] In one embodiment, network device 1 may further include: a determining unit.

[0167] The determining unit is also used to determine the priority corresponding to each type of first data type information, and to determine the first access priority order corresponding to the first device for each type of first data type information based on the priority.

[0168] Configuration unit 11 is also used to configure first resource information for the first device in the order of first access priority.

[0169] In one embodiment, the first device includes a first type of device, a second type of device, and a third type of device.

[0170] The configuration unit 11 is also used to configure corresponding first resource information for the first type of devices when the number of first type devices is greater than the first threshold.

[0171] The configuration unit 11 is further configured to configure corresponding first resource information for the second type of target device when the number of the first type of device is less than or equal to the first threshold and the number of the second type of device is greater than the second threshold.

[0172] Configuration unit 11 is further configured to configure corresponding first resource information for the third type of devices when the number of second type devices is less than or equal to a second threshold and the number of third type devices is greater than a third threshold. Wherein, the access priority of the first type of devices is higher than the access priority of the second type of devices, and the access priority of the second type of devices is higher than the access priority of the third type of devices.

[0173] In one embodiment, the determining unit is further configured to determine the priority corresponding to each type of second data type information, and determine the second access priority order of the second device corresponding to each type of second data type information based on the priority.

[0174] Configuration unit 11 is also used to configure second resource information for the second device in the order of second access priority.

[0175] In one embodiment, the second device includes a first type of device, a second type of device, and a third type of device.

[0176] Configuration unit 11 is also used to configure corresponding second resource information for the first type of devices when the number of first type devices is greater than the fourth threshold.

[0177] Configuration unit 11 is also used to configure corresponding second resource information for the second type of target device when the number of first type devices is less than or equal to the fourth threshold and the number of second type devices is greater than the fifth threshold.

[0178] Configuration unit 11 is further configured to configure second resource information for the third type of devices when the number of second type devices is less than or equal to a fifth threshold and the number of third type devices is greater than a sixth threshold. Specifically, the access priority of the first type of devices is higher than that of the second type of devices, and the access priority of the second type of devices is higher than that of the third type of devices.

[0179] In one embodiment, the configuration unit 11 is further configured to configure third resource information for the second device when the number of third type devices is less than or equal to a sixth threshold, so that the first type devices, second type devices and third type devices included in the second device can compete for access to the network device based on the third resource information.

[0180] In one embodiment, the configuration unit 11 is further configured to, when the number of first type devices is less than a seventh threshold, reduce the first target resource information in the second resource information of the first type devices and supplement the first target resource information to the second resource information corresponding to the second type devices.

[0181] Configuration unit 11 is further configured to, when the number of second type devices is less than the eighth threshold, reduce the second target resource information in the second resource information of the second type devices and supplement the second target resource information to the second resource information corresponding to the third type devices.

[0182] This application provides a network device that acquires one or more first data type information reported by a first device within the network device's coverage area, and / or one or more second data type information reported by a second device; sequentially configures first resource information for each type of first data type information reported by the first device, so that the first device can access the network device non-contentionally based on the first resource information; and / or sequentially configures second resource information for each type of second data type information reported by the second device, so that the second device can access the network device competitively based on the second resource information. Therefore, the network device proposed in this application determines the first data type information reported by the first device and the second data type information reported by the second device for the first and second devices under the network device's coverage area. For the first device, corresponding first resource information is configured for each different type of first data type information, and the first device accesses the network device non-contentionally based on the corresponding first resource information. For the second device, corresponding second resource information is configured for each different type of second data type information, and the second device accesses the network device competitively based on the corresponding second resource information. It is evident that the first and second devices use different access resources. The first and second devices, which report information of different data types, also use different access resources. Therefore, dividing the access resources of the first and second devices can effectively avoid collisions when the first and second devices of different data types access the network devices, thereby improving the success rate of access for the first and second devices.

[0183] Figure 8 This is a schematic diagram of the composition structure of a network device 1 provided in an embodiment of this application. In practical applications, based on the same disclosed concept of the above embodiments, such as... Figure 8 As shown, the network device 1 in this embodiment includes a processor 12, a memory 13, and a communication bus 14.

[0184] In specific embodiments, the acquisition unit 10, configuration unit 11, sending unit, receiving unit, and determining unit described above can be implemented by a processor 12 located on the network device 1. The processor 12 can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), CPU, controller, microcontroller, and microprocessor. It is understood that for different devices, the electronic device used to implement the above processor functions can also be other types, and this application embodiment does not impose specific limitations.

[0185] In this embodiment, the communication bus 14 is used to realize the connection communication between the processor 12 and the memory 13; when the processor 12 executes the running program stored in the memory 13, it implements the following device access method: Obtain one or more first data type information reported by a first device within the network device's coverage area, and / or one or more second data type information reported by a second device; configure first resource information for the first device corresponding to each of the reported one or more first data type information, so that the first device can access the network device non-contention based on the first resource information; and / or, configure second resource information for the second device corresponding to each of the reported one or more second data type information, so that the second device can access the network device contention based on the second resource information.

[0186] In one embodiment, the processor 12 is further configured to send first information to the second device and receive second information sent by the second device based on the first information, wherein the second information carries second data type information of the second device; obtain one or more second data type information of the second device from the second information; or, send first information to the second device, wherein the first information carries data type information and scheduling resources corresponding to the data type information; receive third information sent by the second device based on the scheduling resources, and obtain one or more second data type information of the second device based on the scheduling resources used by the second device to send the third information.

[0187] In one embodiment, the processor 12 is further configured to determine the priority corresponding to each type of first data type information, and determine the first access priority order corresponding to the first device for each type of first data type information based on the priority; and configure the first resource information for the first device in sequence according to the first access priority order.

[0188] In one embodiment, the first device includes a first type of device, a second type of device, and a third type of device.

[0189] The processor 12 is further configured to configure corresponding first resource information for the first type of devices when the number of first type devices is greater than a first threshold; configure corresponding first resource information for the second type of target devices when the number of first type devices is less than or equal to the first threshold and the number of second type devices is greater than the second threshold; and configure corresponding first resource information for the third type of devices when the number of second type devices is less than or equal to the second threshold and the number of third type devices is greater than the third threshold; wherein the access priority of the first type of devices is higher than the access priority of the second type of devices, and the access priority of the second type of devices is higher than the access priority of the third type of devices.

[0190] In one embodiment, the processor 12 is further configured to determine the priority corresponding to each type of second data type information, and determine the second access priority order of the second device corresponding to each type of second data type information based on the priority; and configure the second resource information for the second device in sequence according to the second access priority order.

[0191] In one embodiment, the second device includes a first type of device, a second type of device, and a third type of device.

[0192] The processor 12 is further configured to configure corresponding second resource information for the first type of devices when the number of first type devices is greater than a fourth threshold; configure corresponding second resource information for the second type of target devices when the number of first type devices is less than or equal to the fourth threshold and the number of second type devices is greater than a fifth threshold; and configure second resource information for the third type of devices when the number of second type devices is less than or equal to the fifth threshold and the number of third type devices is greater than a sixth threshold; wherein the access priority of the first type of devices is higher than the access priority of the second type of devices, and the access priority of the second type of devices is higher than the access priority of the third type of devices.

[0193] In one embodiment, the processor 12 is further configured to configure third resource information for the second device when the number of third type devices is less than or equal to a sixth threshold, so that the first type devices, second type devices and third type devices included in the second device can compete for access to the network device based on the third resource information.

[0194] In one embodiment, the processor 12 is further configured to, when the number of first type devices is less than a seventh threshold, reduce the first target resource information in the second resource information of the first type devices and supplement the first target resource information to the second resource information corresponding to the second type devices; and when the number of second type devices is less than an eighth threshold, reduce the second target resource information in the second resource information of the second type devices and supplement the second target resource information to the second resource information corresponding to the third type devices.

[0195] Based on the above embodiments, this application provides a storage medium storing a computer program thereon. The computer-readable storage medium stores one or more programs, which can be executed by one or more processors and applied in a network device. The computer program implements the device access method described above.

[0196] Based on the above embodiments, this application provides a computer program product, including a computer program that can be executed by one or more processors and applied in a network device. The computer program implements the device access method described above.

[0197] It should be noted that, in the embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0198] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / random access memory (RAM), magnetic disk, optical disk), and includes several instructions to cause an image display device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the embodiments of this application.

[0199] The above description is merely a specific implementation of the embodiments of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the protection scope of this application.

Claims

1. A device access method, characterized in that, Applied to network devices, the method includes: Obtain one or more first data type information reported by a first device within the coverage area of ​​the network device, and / or one or more second data type information reported by a second device; First resource information is configured for each of the first data types of information reported by a first device, in turn, so that the first device can access the network device without contention based on the first resource information; And / or, configure second resource information for each of the second data types of information reported by the second device, so that the second device can compete for access to the network device based on the second resource information.

2. The method according to claim 1, characterized in that, The step of obtaining one or more second data type information reported by the second device within the coverage area of ​​the network device includes: Send first information to the second device and receive second information sent by the second device based on the first information, wherein the second information carries second data type information of the second device; Obtain one or more second data type information of the second device from the second information; Alternatively, send first information to the second device, wherein the first information carries data type information and scheduling resources corresponding to the data type information; Receive third information sent by the second device based on the scheduling resources, and obtain one or more second data type information of the second device based on the scheduling resources used by the second device to send the third information.

3. The method according to claim 1, characterized in that, The first device that sequentially reports one or more first data types of information is configured with first resource information, including: Determine the priority corresponding to each type of first data type information, and determine the first access priority order corresponding to the first device for each type of first data type information based on the priority; The first resource information is configured for the first device in the order of the first access priority.

4. The method according to claim 3, characterized in that, The first device includes a first type of device, a second type of device, and a third type of device. The step of configuring the first resource information for the first device sequentially according to the first access priority order includes: If the number of devices of the first type is greater than the first threshold, configure the corresponding first resource information for the devices of the first type. If the number of devices of the first type is less than or equal to the first threshold and the number of devices of the second type is greater than the second threshold, configure the corresponding first resource information for the target devices of the second type. If the number of devices of the second type is less than or equal to the second threshold, and the number of devices of the third type is greater than the third threshold, then configure the corresponding first resource information for the devices of the third type. The access priority of the first type of device is higher than that of the second type of device, and the access priority of the second type of device is higher than that of the third type of device.

5. The method according to claim 1, characterized in that, The second device is configured with second resource information for each of the second data types in the reported one or more second data type messages, including: Determine the priority corresponding to each type of second data type information, and determine the second access priority order of the second device corresponding to each type of second data type information based on the priority; Configure the second resource information for the second device in the order of the second access priority.

6. The method according to claim 5, characterized in that, The second device includes a first type of device, a second type of device, and a third type of device. The step of configuring the second resource information for the second device sequentially according to the second access priority order includes: If the number of devices of the first type is greater than the fourth threshold, configure the corresponding second resource information for the devices of the first type. If the number of devices of the first type is less than or equal to the fourth threshold and the number of devices of the second type is greater than the fifth threshold, then configure the corresponding second resource information for the target devices of the second type. If the number of devices of the second type is less than or equal to the fifth threshold, and the number of devices of the third type is greater than the sixth threshold, then configure the second resource information for the third type of devices. The access priority of the first type of device is higher than that of the second type of device, and the access priority of the second type of device is higher than that of the third type of device.

7. The method according to claim 6, characterized in that, The method further includes: If the number of the third type of devices is less than or equal to the sixth threshold, third resource information is configured for the second device so that the first type of devices, the second type of devices, and the third type of devices included in the second device can compete for access to the network device based on the third resource information.

8. The method according to claim 6, characterized in that, The method further includes: When the number of devices of the first type is less than the seventh threshold, the first target resource information in the second resource information of the first type of devices is reduced, and the first target resource information is added to the second resource information corresponding to the second type of devices. If the number of devices of the second type is less than the eighth threshold, reduce the second target resource information in the second resource information of the second type of devices, and supplement the second target resource information to the second resource information corresponding to the third type of devices.

9. A network device, characterized in that, The network device includes: The acquisition unit is used to acquire one or more first data type information reported by a first device within the coverage area of ​​the network device, and / or one or more second data type information reported by a second device; The configuration unit is configured to configure first resource information for a first device that reports one or more first data types of information, for each type of first data type, so that the first device can access the network device without contention based on the first resource information; and / or, configure second resource information for a second device that reports one or more second data types of information, for each type of second data type, so that the second device can access the network device competitively based on the second resource information.

10. A network device, characterized in that, The network device includes a processor and a memory; the processor executes a running program stored in the memory to implement the method as described in any one of claims 1 to 8.

11. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 8.

12. A computer program product, comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the method as described in any one of claims 1 to 8.

Images