Service scheduling method, device, and storage medium

Abstract

An embodiment of the present application provides a service scheduling method and its device, as well as a storage medium, the method including: a first NAN device determining at least one first CRB corresponding to a first service based on a service type and / or a first priority of the first service and a second priority of each CRB of a first NDC; the first service is scheduled within the at least one first CRB, and the first NAN belongs to the first NDC, thereby realizing differentiated scheduling of services.

Description

[Technical Field]

[0001] TECHNICAL FIELD The embodiments of the present application relate to the field of communication technology, and in particular to a service scheduling method, apparatus, device, and storage medium thereof. [Background technology]

[0002] The wireless local area network industry is one of the fastest growing in the entire data communications field today. As a complement and extension of traditional wired local area networks, wireless local area network solutions have gained support from home network users, small and medium-sized office users, a wide range of enterprise users, and telecom operators due to their advantages such as flexibility, mobility, scalability, and low investment costs, and are rapidly becoming popular.

[0003] The Wireless Fidelity (WI-FI) Alliance has developed a standard for Neighbor Awareness Networks (NANs), which aims to quickly discover services offered by peripheral devices before establishing a connection, all while using low power.

[0004] With the rapid development of wireless network technology, people's demands for network quality are also increasing. Various traffic with different characteristics, such as video, games, and wearable devices, continues to increase. Some services require low latency, some services require high reliability, and even some services require high throughput. This requires NAN devices within a NAN network to be able to support different types of services. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide a service scheduling method, an apparatus, a device, and a storage medium thereof. [Means for solving the problem]

[0006] A service scheduling method according to an embodiment of the present application includes: The method includes a first Neighborhood Sensing Network (NAN) device determining at least one first Common Resource Block (CRB) corresponding to a first service based on a service type and / or a first priority of the first service and a second priority of each CRB of at least one CRB of a first NAN Data Cluster (NDC), wherein the first service is scheduled within the at least one first CRB, and the first NAN belongs to the first NDC.

[0007] A first NAN device according to an embodiment of the present application includes: The present invention comprises a first determination unit configured to determine at least one first common resource block (CRB) corresponding to a first service based on a service type and / or a first priority of the first service and a second priority of each CRB of at least one CRB of a first NAN data cluster (NDC), wherein the first service is scheduled within the at least one first CRB and the first NAN belongs to the first NDC.

[0008] A communication device according to an embodiment of the present application includes a processor and a memory, the memory stores a computer program, and the processor invokes and executes the computer program stored in the memory to cause the communication device to perform the above service scheduling method.

[0009] A chip according to an embodiment of the present application is configured to implement the above service scheduling method.

[0010] Specifically, the chip includes a processor that retrieves and executes a computer program from a memory, causing the device in which the chip is installed to execute the service scheduling method described above.

[0011] A computer-readable storage medium according to an embodiment of the present application is configured to store a computer program for causing a computer to execute the above service scheduling method.

[0012] A computer program product according to an embodiment of the present application includes computer program instructions for causing a computer to perform the above service scheduling method.

[0013] A computer program according to an embodiment of the present application, when executed on a computer, causes the computer to perform the above service scheduling method. [Effects of the Invention]

[0014] With the above technical solution, the first NAN device determines the first CRB to be used for scheduling the first service based on the service type and / or first priority of the first service and the second priority of each CRB of the CRBs of the first NDC, thereby allowing the NAN device to determine the CRB to schedule the service based on the priority of the service and the priority of the CRB. Therefore, instead of blindly determining the CRB to schedule the service in the NDC schedule table, the CRB can be determined according to the priority of the current service, thereby realizing that resources are differentiated and scheduled according to the priority of the current service, and ensuring differentiated scheduling of services. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is an alternative schematic diagram of one application scenario of an embodiment of the present application; FIG. [Figure 2] 1 is an alternative schematic diagram of one NAN cluster in an embodiment of the present application. [Figure 3] FIG. 1 is a selectable schematic diagram of a DW schedule table in an embodiment of the present application. [Figure 4] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 5] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 6] FIG. 1 is a schematic diagram of selectable relationships between NDL and NDP in an embodiment of the present application. [Figure 7] 1 is a schematic diagram of an alternative NDC for an embodiment of the present application.

[0016] [Figure 8] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 9] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 10] 1 is an alternative schematic diagram of one NAN cluster in an embodiment of the present application. [Figure 11] FIG. 1 is a selectable schematic diagram of an NDC schedule table in an embodiment of the present application. [Figure 12] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 13A] FIG. 1 is a selectable schematic diagram of an NDC schedule table in an embodiment of the present application. [Figure 13B] FIG. 1 is a selectable schematic diagram of an NDC schedule table in an embodiment of the present application. [Figure 14] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 15] FIG. 1 is a selectable schematic diagram of an NDC schedule table in an embodiment of the present application. [Figure 16] FIG. 1 is a schematic diagram of selectable formats of an SDF according to an embodiment of the present application. [Figure 17]FIG. 2 is a schematic diagram of selectable formats of service descriptor attributes in an embodiment of the present application; [Figure 18] FIG. 2 is a schematic diagram of selectable formats of a NAN availability attribute in an embodiment of the present application. [Figure 19] FIG. 10 is a schematic diagram of selectable formats of the Availability Entry subfield of an embodiment of the present application. [Figure 20] FIG. 2 is a schematic diagram of selectable formats of the attribute control field in an embodiment of the present application. [Figure 21] FIG. 1 is a schematic diagram of selectable formats of NDC attributes in an embodiment of the present application. [Figure 22] FIG. 10 is a schematic diagram of selectable formats for schedule entry subfields in an embodiment of the present application. [Figure 23] FIG. 1 is a selectable schematic diagram of an NDC schedule table in an embodiment of the present application. [Figure 24] FIG. 1 is a selectable schematic diagram of an NDC schedule table in an embodiment of the present application. [Figure 25] FIG. 10 is a schematic diagram of selectable formats of attribute control fields within an NDC attribute in an embodiment of the present application. [Figure 26] 1 is a schematic diagram of an alternative NDC for an embodiment of the present application. [Figure 27] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 28] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 29] FIG. 2 is a schematic diagram of selectable processes of a service scheduling method according to an embodiment of the present application; [Figure 30] 1 is a schematic diagram of an alternative NDC for an embodiment of the present application. [Figure 31] 1 is a schematic diagram of an alternative NDC for an embodiment of the present application. [Figure 32] 1 is a schematic diagram of an alternative configuration of a first NAN device according to an embodiment of the present application; [Figure 33]1 is an exemplary structural diagram of a communication device according to an embodiment of the present application; [Figure 34] 1 is an exemplary structural diagram of a chip according to an embodiment of the present application; [Figure 35] 1 is an exemplary block diagram of a communication system according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0017] The above drawings are provided for a better understanding of the present application and constitute a part of the present application, and the illustrative examples of the present application and their description are used to explain the present application and do not constitute undue limitations on the present application.

[0018] The following describes the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application, but obviously, the described embodiments are only some of the embodiments of the present application, not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of the present application.

[0019] The technical solutions in the embodiments of the present application may be applied to various communication systems, such as systems such as Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), or other communication systems. Bands supported by WLAN may include, but are not limited to, low bands (2.4 GHz, 5 GHz, 6 GHz) and high bands (60 GHz).

[0020] FIG. 1 is an example of a communication system architecture applied to an embodiment of the present application.

[0021] As shown in FIG. 1 , the communication system 100 may include an AP 110 and STAs 120 that access a network via the AP 110. In some scenarios, the AP may also be referred to as an AP STA, i.e., in a sense, the AP is also an STA. In some scenarios, the STAs may also be referred to as non-AP STAs. In some scenarios, the STAs 120 may include AP STAs and non-AP STAs. Communication in the communication system 100 may include communication between the AP 110 and the STAs 120, communication between the STAs 120, or communication between the STAs 120 and a peer STA, where the peer STA may refer to a device communicating with the STA 120. For example, the peer STA may be an AP or a non-AP STA.

[0022] The AP 110 can be used as a bridge connecting to wired or wireless networks. Its main function is to connect various wireless network clients and further connect wireless networks to Ethernet. The AP 110 is a terminal device (such as a mobile phone) or a network device (such as a router) equipped with a WiFi chip.

[0023] Note that the role of the STA 120 in the communication system is not absolute, that is, the role of the STA 120 in the communication system can be switched between an AP and a STA. For example, in some scenarios, when a mobile phone is connected to a router, the mobile phone is a STA, and when the mobile phone is used as a hotspot for other mobile phones, the mobile phone functions as an AP.

[0024] In some embodiments, the AP 110 and the STA 120 may be devices applied to the Internet of Vehicles, IoT nodes in the Internet of Things (IoT), sensors, etc., smart cameras, smart remote controls, smart water meters, etc. in smart homes, sensors in smart cities, etc.

[0025] In some embodiments, the AP 110 may be a device that supports the 802.11be standard. The AP may be a device that supports multiple current and future WLAN standards in the 802.11 family, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. In some embodiments, the STA 120 may support the 802.11be standard. The STA may also support multiple current and future WLAN standards in the 802.11 family, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0026] In some embodiments, the AP 110 and / or STA 120 may be deployed indoors or outdoors, handheld, wearable, or on land, including vehicle-mounted, on water (such as a ship), or in the air (such as an airplane, balloon, satellite, etc.).

[0027] In some embodiments, the STA 120 may be a mobile phone supporting WLAN / WiFi technology, a tablet, a PC with wireless transceiver functionality, a virtual reality (VR) device, an augmented reality (AR) device, a wireless device in industrial control, a set-top box, a wireless device in self driving, an in-vehicle communication device, a wireless device in remote medical, a wireless device in a smart grid, a wireless device in transportation safety, a wireless device in a smart city, or a wireless device in a smart home, an in-vehicle communication device, a wireless communication chip / application specific integrated circuit (ASIC) / system on chip (SoC), etc.

[0028] For example, the STA 120 may be a wearable device. A wearable device, also known as a wearable smart device, is a collective term for wearable devices developed by applying wearable technology to intelligently design everyday clothing such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or incorporated into a user's clothing or accessories. Wearable devices are not only hardware devices but also realize powerful functions through software support, data interaction, cloud interaction, and the like. In a broad sense, wearable smart devices include devices that are full-featured, large in size, and can achieve full or partial functions independently of a smartphone, such as smart watches and smart glasses, as well as devices that focus only on certain application functions and require cooperation with other devices, such as smartphones, such as various smart bracelets and smart jewelry for monitoring physical condition.

[0029] It should be understood that Fig. 1 is merely an example of the present application and should not be understood as a limitation of the present application. For example, Fig. 1 exemplarily illustrates only one AP and two STAs, and in some embodiments, the communication system 100 may include multiple APs and other numbers of STAs, but the embodiments of the present application are not limited thereto.

[0030] 1, 2A, and 2B merely exemplify systems applicable to the present application, and the methods described in the embodiments of the present application can also be applied to other systems. Furthermore, the terms "system" and "network" are used interchangeably herein. The term "and / or" used herein merely indicates a relational relationship between associated objects and indicates that three relationships can exist. For example, A and / or B indicates three cases: when only A exists, when both A and B exist, and when only B exists. Furthermore, the symbol " / " used herein generally indicates that the relation between the associated objects before and after it is an "or" relationship. Furthermore, it should be understood that the "instruction" referred to in the embodiments of the present application may be a direct instruction, an indirect instruction, or may indicate the existence of an association relationship. For example, when A indicates B, it may indicate that A directly indicates B (e.g., B can be obtained by A), or that A indirectly supports B (e.g., A indicates C and B can be obtained by C), or it may indicate that there is an association relationship between A and B. Furthermore, it should be understood that the term "corresponding" used in the embodiments of the present application may indicate a direct or indirect correspondence relationship between the two, an association relationship between the two, or a relationship between an indicating and an indicated, a configuring and configured, or the like. It should also be understood that the "predefined" or "predefined rule" used in the embodiments of the present application may be realized by prestoring corresponding codes, tables, or other forms usable to indicate relationship information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation form. For example, "predefined" may refer to being "defined in a protocol." Furthermore, in the embodiments of the present application, the "protocol" may refer to a standard protocol in the communications field, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied to future communications systems, but the present application is not limited thereto.

[0031] In order to facilitate understanding of the technical solutions in the embodiments of the present application, the following describes the related technologies of the embodiments of the present application, and the following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the protection scope of the embodiments of the present application.

[0032] NAN Cluster Architecture A NAN cluster is a collection of NAN devices that share the same NAN parameters and synchronize the same Discovery Window (DW) schedule table. A NAN cluster is uniquely identified by a NAN cluster ID. As shown in Figure 2, a NAN cluster includes four NAN devices 201, and different NAN devices 201 can communicate with each other.

[0033] The DW is a periodic time window established by the NAN devices that establish a NAN cluster.

[0034] In one example, the DW schedule table established by the NAN device establishing the NAN cluster includes periodic time windows DW1 and DW2, as shown in FIG. 3, where one period is 512 time units (TU), the channel for DW1 is channel 6, the channel for DW2 is channel 149, and the interval between the start position of DW1 and the start position of DW2 is 128 TU.

[0035] In one NAN cluster, NAN devices: Control side (Master), They are classified into two roles:

[0036] A NAN device in a non-master role is further divided into two states: a non-sync state and a sync state, and the state of the NAN device can change.

[0037] The master generates and transmits beacon frames, which include synchronization beacon frames and discovery beacon frames. When a non-master in the non-sync state receives a synchronization beacon frame transmitted from the master, it discards it directly. When a non-master in the sync state receives a synchronization beacon frame transmitted from the master, it transmits it.

[0038] It can be understood that when a NAN device is a non-master in the master or sync state, the NAN device transmits NAN synchronization beacon frames within the DW to maintain synchronization of the NAN cluster, and when a NAN device is a non-master in the non-sync state, the NAN device is not allowed to transmit synchronization beacon frames within the DW.

[0039] Each NAN device is assigned a NAN master level, which is composed of three parts: master preference, random factor, and NAN interface address. Since master preference accounts for the largest proportion, the higher the master preference value of a NAN device, the higher the NAN master level of that NAN device.

[0040] Each NAN cluster has one special master, the anchor master, which is the NAN device with the highest master level in the NAN cluster. The role of the anchor master is to broadcast a synchronization beacon frame at the start of each DW to announce the timing synchronization function (TSF) and DW schedule table for the entire NAN cluster.

[0041] NAN Service Discovery Within the DW, all NAN devices can transmit service discovery frames (SDFs), and the service discovery process of NAN devices can be divided into two types: the unsolicited service issuance process shown in Figure 4, and the requested service issuance process shown in Figure 5.

[0042] In FIGS. 4 and 5, NAN device A is a service publisher, and NAN device B is a service subscriber.

[0043] The unsolicited service publishing process is shown in Figure 4. In step S401, NAN device A publishes its own service by broadcasting (publishing) an SDF. The SDF includes a NAN Availability attribute that advertises one or more Further Availability Windows (FAWs), and a Service Descriptor attribute that advertises filtering conditions and other service information. After receiving the Published SDF, if NAN device B needs to subscribe to the service, it executes step S402 and sends a unicast SDF (Follow-up) to the service publisher.

[0044] Here, filtering conditions can be used to control the distance between devices that the service can discover, and can be set as follows:

[0045] (1) Set it so that only short-range devices can be discovered.

[0046] (2) Set it so that there is no distance limit.

[0047] The process of issuing a service upon request is as shown in Figure 5. In S501, NAN device B (service subscriber) spontaneously broadcasts SDF Subscribe. After receiving the SDF, the service publisher executes S502 to send an SDF (Publish) to the subscriber. After receiving the SDF sent from the service publisher, the service subscriber executes S503 to negotiate using SDF Follow-up.

[0048] NAN Data Path (NDP) Establishment Process In the NAN, a FAW is represented as a combination of time and channel owned by the NAN device itself. For example, a NAN device has one FAW, and the FAW occupies multiple channels and one time period or multiple time periods with the same period, so the FAW can be represented by time and channel.

[0049] A CRB is represented in the NAN as a FAW used for device-to-device communication. For example, the FAWs held by the NDL and NDC may be called a CRB. For a NAN device, its CRB is a subset of the FAWs it supports. In some cases, a CRB is a FAW, and can be understood to simply be the FAW used by the NDL.

[0050] To communicate between a pair of NAN devices, a service must establish an NDP between them. The NDP is a logical path for sending and receiving data frames for a particular service between the pair of NAN devices, but does not actually own any resources.

[0051] Between a pair of NAN devices, a NAN Device Link (NDL) is established through negotiation. Each NDL has a certain number of FAWs, which are called NDL CRBs. The NDL CRBs must support the needs of one or more NDPs between the pair of NAN devices. There can only be one NDL between a pair of NAN devices.

[0052] Not all NDL CRBs are used for service communications; it is the NDC CRBs that are actually used for service communications.

[0053] In the process of establishing an NDL between a pair of NAN devices, an NDC is also established at the same time, and the NDC also has a certain number of FAWs. These FAWs are called NDC CRBs, and service communication between the pair of NAN devices is carried out within the NDC CRBs. Therefore, the NDC CRB is a subset of the NDL CRB. Here, the NDL CRB and the NDC CRB can be understood as the NDL Schedule and the NDC Schedule, respectively.

[0054] An NDC contains at least two NAN devices that belong to the same NAN cluster, and each NAN device in the NDC must establish at least one NDL with another NAN device in the NDC. An NAN device can join multiple NDCs simultaneously, but an NDL between a pair of NAN devices can only join one NDC.

[0055] As shown in Figure 6, one NDL contains multiple NDPs.

[0056] As shown in FIG. 7, an NDN cluster 701 includes multiple NAN devices, an NDC includes some of the NAN devices in the NAN cluster, and one NAN device in the NDC establishes one NDL with at least another NAN device in the NDC.

[0057] After the service discovery process, the service subscriber sends a data path request frame to the service publisher within the service publisher's accepted FAW, at which time the service subscriber becomes the NDP requester, and correspondingly, the service publisher becomes the NDP responder.

[0058] If the following conditions are met, the NDP requester must start the establishment of the NDP and the establishment of the NDL schedule table at the same time; if the following conditions are not met, the NDP requester can start the establishment of the NDP directly.

[0059] (1) There is no established NDL schedule between the NDP requester and the NDP responder, or (2) An established NDL schedule exists between the NDP initiator and the NDP responder, but does not meet the requirements of a new NDP.

[0060] The NDP establishment process is classified into the following two types: the first is the establishment of a data path that does not require confirmation, as shown in FIG. 8, and the second is the establishment of a data path that requires confirmation, as shown in FIG.

[0061] As shown in FIG. 8, it includes the following steps:

[0062] In step S801, the NDP requester sends a data path request frame to the NDP responder within a FAW or DW.

[0063] After service discovery, the NDP initiator sends a data path request frame to the NDP responder within a FAW or DW, and the data path request frame includes an NDL schedule table initial proposal, an NDP attribute, and an NDL attribute, where the Type subfields of the NDL attribute and the NDP attribute are set to "Request" to indicate a request to establish an NDL and an NDP. In the NDL Schedule Initial Proposal, (1) One or more NAN availability attributes must be included, and the NAN availability attributes are used to indicate at least one FAW that the device itself owns. (2) One or more NDC attributes may be included, and the NDC attribute and the corresponding NAN availability attribute are associated by the Map ID field, which allows obtaining information such as the band and channel of the NAN availability attribute. If the selected NDC flag in the schedule control field of the NDC attribute is 1, it indicates that the initiator has selected an existing NDC, and the NDC CRB is indicated by the NDC attribute. If the selected NDC flag is 0, it indicates that the initiator wishes to establish a new NDC, and the NDC CRB in the NDC attribute is merely a proposal by the initiator and is negotiable. (3) Other

[0064] In step S802, the NDP responder returns one data path response frame to the NDP requester.

[0065] After receiving the above Data Path Request frame, the NDP Responder sends back one Data Path Response frame to the NDP Requester, where the Data Path Response frame includes the NDL attribute, the NDP attribute, and a possible NDL Schedule Counter Proposal. The Type subfields in the NDL attribute and the NDP attribute are set as Response, and the status subfield in the NDL attribute can be set as Accept, Continue, or Reject.

[0066] If the status is set to Reject, the reason code subfield must be set to the error cause. In this case, the data path response frame can include an NDL Schedule Suggest Proposal, where the NDL Schedule Suggest Proposal includes the following:

[0067] (1) One or more NAN availability attributes. The NAN availability attributes are used to indicate the FAWs that the device itself has. (2) One NDC attribute, indicating the FAW as the NDC CRB proposed by the NDP responder.

[0068] If the status is set to Accept, it corresponds to the confirmation-free data path establishment process and must include an NDL ScheduleCompliant Proposal, where the NDL ScheduleCompliant Proposal includes:

[0069] (1) One or more NAN availability attributes. The NAN availability attributes are used to indicate the FAWs that the device itself has. (2) One or more NDC attributes, which are the same as the FAWs represented by the NDC attributes in the NDL Schedule Initial Proposal. (3)Others.

[0070] If status is set to Continue, it corresponds to the data path establishment process that needs to be confirmed and must include an NDL Schedule Counter Proposal, where the NDL Schedule Counter Proposal includes the following:

[0071] (1) One or more NAN availability attributes. The NAN availability attribute is used to indicate at least one FAW that the device itself has. (2) One or more NDC attributes, which indicate at least one FAW as an NDC CRB that the NDP responder can accept. (3)Others.

[0072] After an NDP requester receives a Data Path Response frame containing an NDL attribute with a Type subfield of Response: If the status subfield is Accept, both parties complete the establishment of the data path, and both parties to the service use the FAW that was overlapped during the negotiation process as the NDL CRB, and the FAW indicated in the NDC attribute in the NDL Schedule Compliant Proposal becomes the NDC CRB.

[0073] If the status subfield is Reject, both parties terminate the establishment of the data path, and if an NDL Schedule Suggest Proposal is received, the initiator retries the establishment of the data path based on this.

[0074] If the status subfield is Continue, the NDP requester can choose to accept or reject the NDP responder's NDL Schedule Counter Proposal. In this case, as shown in Figure 9, the NDP requester executes S803 and sends the responder a data path confirmation frame with the Type subfield of the NDL attribute set to Confirm.

[0075] In a data path confirm frame where the Type subfield of the NDL attribute is Confirm, the status subfield is set to Accept or Reject.

[0076] (1) If the status is Accept, it indicates that the NDP requester has accepted the NDP responder's NDL Schedule Counter Proposal. In this case, it must include an NDL Schedule Confirm Proposal, where the FAW indicated in the NDC attribute is the same as the FAW in the NDL Schedule Counter Proposal.

[0077] (2) If the status is Reject, it indicates that the NDP requester has rejected the NDP responder's NDL Schedule Counter Proposal.

[0078] After the NDP responder receives a data path confirmation frame with the Type subfield of the NDL attribute set to Confirm, if the status subfield in the NDL attribute is set to Accept, both parties complete the establishment of the data path, and the two service parties use the overlapping FAW during the negotiation process as the NDL CRB, and the FAW indicated in the NDC attribute in the NDL Schedule Confirm Proposal becomes the NDC CRB. If the status subfield in the NDL attribute is set to Reject, both parties terminate the establishment of the data path.

[0079] NAN Scheduler A NAN scheduler is located in the NAN device, and the functions of the NAN scheduler include the following:

[0080] (1) Record the schedule tables (including DW, FAW, etc.) of other NAN devices in the vicinity.

[0081] (2) Publish your own schedule table.

[0082] (3) Manage resources for the establishment, renewal, and termination of the NDL, NDP, and NDC.

[0083] One NAN device includes Committed DWs information in the Device Capability attribute of the NAN management frame, one NAN device includes FAW information in the NAN Availability attribute of the NAN management frame, and one NAN device includes a schedule table of NAN operations and non-NAN operations in the NDL attribute, NDC attribute, Ranging Setup attribute, and Public Availability attribute of the NAN management frame.

[0084] The NAN scheduler issues these DWs, FAWs, and other schedule table information during stages such as cluster discovery, cluster synchronization, service discovery, and data communication path establishment. After other NAN devices receive NAN management frames containing schedule table information, the scheduler records the associated schedule table information.

[0085] During the negotiation phase of establishing data communication, both NAN devices select appropriate FAWs as NDL and NDC CRB based on the schedule table information of their own and the peer STA.

[0086] In related technologies, Wi-Fi Aware technology does not classify services as a priority, and data frames of all services between two STAs share the NDC CRB of the NDC without distinction. Within the NDC CRB, the NAN device can transmit data frames of any service based on a scheduling algorithm. This method is fair, but is not suitable for certain types of services such as low-latency services.

[0087] The NAN device transmits an SDF during the DW period, and the frame includes its own FAW. When another device wishes to communicate with the corresponding device, it obtains the FAW of the peer station from the received SDF and can negotiate the NDL and NDC Schedule of the service with the peer STA within the corresponding FAW. The NDL CRB consists of the overlapping FAWs of both negotiating devices, and the NDC CRB is negotiated by both devices, or the corresponding NDC CRB can be obtained by joining an existing NDC.

[0088] In one example, the NAN cluster is as shown in FIG. 10, where STA3 and STA4 are near STA1 and STA2, respectively. That is, STA3's communication may interfere with STA1, and STA4's communication may interfere with STA2. Meanwhile, STA5 and STA6 are far from STA1 and STA2. In this case, when STA1 and STA2 join NDC1, STA3 and STA4 can receive the NDC schedule table of NDC1 sent from STA1 and STA2. When STA3 and STA4 establish a new NDC, they need to refer to the NDC schedule table of NDC1.

[0089] Assume that two services are sequentially established between STA1 and STA2, one of which is a low-latency service and the other is a normal service. The NDL and NDC CRB status between STA1 and STA2 is as shown in Figure 11. In the NDC CRB, STA1 and STA2 can transmit data frames for these two services. These two services are equal and share the same NDC CRB. However, this equality is not suitable for special services such as low-latency. In Figure 11, NDC CRBs(1,2) indicates that at least one CRB is an NDC CRB subscribed to by the NDL between STA1 and STA2. NDL CRBs(1,2) indicates that at least one CRB is an NDL CRB between STA1 and STA2. In Figure 11, FAWs supported by STA2 but not supported by STA1 are also included.

[0090] In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application will be described in detail below through specific examples. The above related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and all fall within the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents:

[0091] The service scheduling method according to the embodiment of the present application includes the following steps, as shown in FIG.

[0092] In step S1201, a first NAN device determines at least one first CRB corresponding to a first service based on a service type and / or a first priority of the first service and a second priority of each CRB of at least one CRB of a first NDC, wherein the first service is scheduled within the at least one first CRB, and the first NAN belongs to the first NDC.

[0093] In an embodiment of the present application, a first NAN device may be a publisher of a first service or a subscriber of a first service, where the first NAN device provides the first service to a second NAN device, or the first NAN device subscribes to the first service of the second NAN device.

[0094] A first NAN device belonging to a first NDC can be understood as the first NDC being subscribed to the first NDC. The NDL between the first NAN device and a second NAN device is a first NDL, and the first NDL is used to transmit a first service. Here, the first NAN device and the second NAN device are subscribed to the first NDC, and the first NDL is subscribed to the first NDC. It can be understood that the NAN devices in the first NDC may or may not include other NAN devices other than the first NAN device.

[0095] The first NAN device and the second NAN device establish a first NDP in the first NDL for the first service and transmit the first service via the first NDP, at which time the first NAN device combines the second priority of each second CRB of at least one CRB of the first NDC based on the service type and / or the first priority of the first service to determine at least one first CRB for scheduling the first service.

[0096] If the first NAN device is a publisher of the first service, it contends for a channel for the first service on at least one first CRB and transmits the first service on the contended-for channel. If the first NAN device is a subscriber of the first service, it contends for a channel for the first service on at least one first CRB and receives the first service based on the contended-for channel. As can be understood, scheduling of the first service can be understood as scheduling of data frames of the first service, and transmission of the first service can be understood as transmission of data frames of the first service.

[0097] In an embodiment of the present application, the first service indicates first priority information based on priority information, the first priority information is used to indicate a service type and / or a first priority, and the service type of the first service can indicate the first priority of the first service.

[0098] In the embodiment of the present application, the second priority information is indicated in each CRB in the first NDC, and the second priority information is used to indicate the second priority.

[0099] In the embodiment of the present application, the first priority can be understood as the priority of the service, and the second priority can be understood as the priority of the CRB or FAW. The first priority category and the second priority category can be the same or different. In one example, the lowest first priority and the lowest second priority are priority 0, and the highest first priority and the highest second priority are priority 7, where the priority levels of the first priority and the second priority correspond one-to-one. In one example, the lowest first priority and the lowest second priority are priority 0, the highest first priority is 3, and the highest second priority is priority 7. In the embodiment of the present application, there can be one second priority corresponding to one first priority, and the number of second priorities corresponding to one first priority can be one or more, and the number of first priorities corresponding to one second priority can be one or more.

[0100] Understandably, services with higher first priority have higher delay requirements.

[0101] As can be seen, a CRB with a higher second priority corresponds to a higher Access Category (AC).

[0102] In an embodiment of the present application, if it is determined that a CRB cannot carry all data frames of a first service, transmission of data frames of the first service can be realized using one or more CRBs based on other CRBs among the remaining CRBs that can carry the first service.

[0103] In an embodiment of the present application, the first NAN device determines the first CRB to be used to schedule the first service based on the service type and / or the first priority of the first service and the second priority of each CRB of the CRBs of the first NDC, so that the NAN device can determine the CRB to schedule the service based on the priority of the service and the priority of the CRB, thereby not blindly determining the CRB to schedule the service in the NDC schedule table, but can determine the CRB according to the priority of the current service, thereby realizing that resources are differentiated and scheduled according to the priority of the current service, and ensuring differentiated scheduling of services.

[0104] In an embodiment of the present application, the first NAN device can determine a CRB corresponding to each service for at least one service based on the priority of each CRB among the CRBs of the first NDC, where the first service is any service among the at least one service, and the first priorities of different services may be the same or different.

[0105] In some embodiments, the first NAN device determining at least one first CRB corresponding to the first service based on a first priority of the first service and a second priority of each CRB of the at least one CRB according to S1201 includes: The first NAN device determines the at least one first CRB based on the type or first priority of the first service and a second priority of each CRB of the at least one CRB of the first NDC.

[0106] Here, the CRB of the first NDC is located in the NDC in the first NDC schedule table.

[0107] It can be understood that the first NDL corresponds to an existing first NDL schedule table, and the first NDC schedule table is a subset of the first NDL schedule table.

[0108] In some embodiments, the service type and / or first priority is: first indication information used to indicate a service type of the first service, where different service types correspond to different first priorities; The first service is marked based on at least one of: second indication information used to indicate whether the first service is a low-latency service, where the low-latency service has the highest first priority.

[0109] The first indication information indicates a service type of the first service, and the first NAN device can determine a first priority of the first service based on the indicated service type. The first indication information is also referred to as service type information.

[0110] The second indication information indicates whether the first service is a low-latency service, and the second information is also called a first low-latency identifier and is a low-latency flag corresponding to the first service. If the second indication information indicates that the first service is a low-latency service, the first service has the highest first priority. If the second indication information indicates that the first service is not a low-latency service, i.e., a non-low-latency service, the first service does not have the highest first priority. In this case, the first priority of the first service can be determined by the first indication information.

[0111] In some embodiments, the second priority is: a third indication information used to indicate a second priority of the corresponding CRB; The CRB is marked based on at least one of the following: fourth indication information used to indicate whether the corresponding CRB is used for low-latency services, and a CRB used for low-latency services has the highest second priority.

[0112] The third indication information of one CRB indicates the second priority of the CRB, where the third indication information is also referred to as priority information.

[0113] The fourth indication information of one CRB indicates whether the CRB is used for a low-latency service, and if the fourth indication information indicates that the CRB is used for a low-latency service, the CRB has the highest second priority; if the fourth indication information indicates that the corresponding CRB is not used for a low-latency service, i.e., is used for a non-low-latency service, the CRB does not have the highest second priority, and in this case, the second priority of the CRB can be determined by the third indication information.

[0114] In some embodiments, the second priority corresponding to the first priority of a service scheduled within one CRB is equal to or greater than the second priority of said CRB.

[0115] For one CRB of the first NDC, the CRB is only allowed to schedule services whose corresponding second priority is equal to or greater than the second priority of the CRB, or is not allowed to schedule services whose corresponding second priority is lower than the second priority of the CRB.

[0116] For at least one first CRB, the second priority of each first CRB is equal to or lower than the second priority corresponding to the first priority of the first service.

[0117] In one example, the first priority and the second priority have a one-to-one correspondence, ranging from 0 to 7, and in the case of a CRB with a second priority of 6, services with first priorities of 6 and 7 are allowed to be scheduled.

[0118] In one example, the first priority and the second priority correspond one-to-one, ranging from 0 to 7, and for a service whose first priority is 7, scheduling is permitted on a second-priority CRB whose second priority is any one of 0 to 7.

[0119] In one example, the first priority includes 0 to 4, the second priority includes 0 to 7, the first priority 0 corresponds to the second priorities 0 and 1, the first priority 1 corresponds to the second priorities 2 and 3, the first priority 2 corresponds to the second priorities 4 and 5, the first priority 3 corresponds to the second priorities 6 and 7, and for a CRB with a second priority of 5, the first priorities that are allowed for scheduling are 2 and 3.

[0120] In one example, the first priority includes 0 to 4, the second priority includes 0 to 7, the first priority 0 corresponds to the second priorities 0 and 1, the first priority 1 corresponds to the seventh priorities 2 and 3, the first priority 2 corresponds to the second priorities 4 and 5, the first priority 3 corresponds to the second priorities 6 and 7, and for a service with a first priority of 3, scheduling is allowed on a second priority CRB with a second priority of any one of 0 to 7.

[0121] In some embodiments, when at least two services are scheduled within one CRB, the first priorities of different services in the at least two services are the same or different.

[0122] One or more services can be scheduled simultaneously in one CRB, and when two services are scheduled in one CRB, the first priorities of different services in the at least two services can be the same or different.

[0123] In some embodiments, in the at least two services, if the first priority of a second service is higher than the first priority of a third service, the priority of an Access Category (AC) of the second service is higher than the priority of an AC of the third service.

[0124] When at least two services are scheduled within one CRB, the higher the first priority of a service, the higher the AC priority of that service. It can be understood that the higher the AC priority of a service, the higher the priority of Enhanced Distributed Channel Access (EDCA) parameters for channel access of that service.

[0125] In some embodiments, if one CRB is designated for use with low latency services, only low latency services are allowed to be scheduled within that CRB.

[0126] In the case of a CRB marked for use with low latency services, only low latency services are permitted to be scheduled, i.e., non-low latency services are not permitted to be scheduled.

[0127] In some embodiments, if the CRB is designated for use with non-low latency services, the services scheduled within the CRB include low latency services and / or non-low latency services.

[0128] For a CRB marked for use with non-low latency services, it is permitted to schedule low latency services and also permits non-low latency services to be scheduled.

[0129] For a low-latency service, scheduling is permitted within a low-latency CRB, and also within a non-low-latency CRB. For a non-low-latency service, scheduling is permitted only within a non-low-latency CRB. In this case, the first priority of the service is determined based on the first instruction information of the service, and the second priority of the CRB is determined based on the third instruction information of the CRB, thereby determining whether scheduling of the service is permitted within the CRB.

[0130] In some embodiments, when the services scheduled within the CRB include a low latency service and a non-low latency service, the priority of the AC of the low latency service is equal to or greater than the priority of the AC of the non-low latency service.

[0131] If at least two services are scheduled within a non-low latency CRB, and the at least two scheduled services include a low latency service and a non-low latency service, the low latency service has a higher AC priority.

[0132] In some embodiments, the first NAN device further performs the following operations:

[0133] The first NAN device determines a first NDC based on the service type and / or first priority of the first service, the first NDC being an NDC to which a first NDL between the first NAN device and the second NAN device belongs, and the first service is provided from the first NAN device to the second NAN device, or the first service is provided from the second NAN device to the first NAN device.

[0134] The first NAN device determines a first NDC and determines at least one CRB for the first NDC based on a service type and / or a first priority of the first service.

[0135] The first NAN device may directly select an existing first NDC or establish a new first NDC based on the service type and / or the first priority of the first service. When directly selecting an existing first NDC, the first NDC is an already established NDC, and when establishing a new first NDC, the first NDC is a newly established NDC.

[0136] Before determining the first NDC, the first NAN device may perform the following process: the first NAN device transmits first information and second information to the second NAN device or receives first information and second information transmitted from the second NAN device, the first information being used to indicate the first service, and the second information being used to indicate a service type and / or a first priority of the first service.

[0137] If the first NAN device is a service issuer, the first NAN device sends the first information and the second information to the second NAN device to notify the second device of the first service that can be provided by the first device, and the service type and / or first priority of the first service.

[0138] If the first NAN device is a subscriber to the service, the first NAN device receives the first information and the second information sent from the second NAN device to notify the first service that can be provided by the second device, and the service type and / or first priority of the first service.

[0139] Here, the first information and the second information can be included in the same frame, and one piece of first information can correspond to one piece of second information.

[0140] In some embodiments, the first information and the second information are included in a first frame, and the first frame is used for service discovery.

[0141] The first NAN device transmits a first frame during a service discovery phase or receives a first frame transmitted from a second NAN device, the first frame including first information and second information.

[0142] Here, if the first frame is used in the service discovery phase, the first frame is a service discovery frame (SDF).

[0143] If the first NAN device is a publisher of the service, the SDF is a published SDF, and if the first NAN device is a subscriber of the service, the SDF is a subscribed SDF.

[0144] In an embodiment of the present application, in a service discovery process, a first frame can be used to broadcast one or more services, where the first service is any service among the services broadcast by the first frame; when the first frame broadcasts multiple services, the first frame includes multiple pieces of first information, where different pieces of first information indicate different services, and for each piece of first information, the first frame includes second information corresponding to each piece of first information.

[0145] In some embodiments, the second information is located in a service descriptor attribute of the first frame.

[0146] In some embodiments, the second information is located in a service information field within the service descriptor attribute.

[0147] In an embodiment of the present application, the service information field in the service description attribute of the SDF is modified so that when it contains only specific information of the service indicated by the service information subfield, the service information field also contains first priority information that defines the first priority of the first service.

[0148] In some embodiments, the second information comprises: first indication information used to indicate a service type of the first service, where different service types correspond to different first priorities, and the first indication information is located in a first sub-field of the service information field; second indication information used to indicate whether the first service is a low-latency service, where a low-latency service has the highest first priority, and the second indication information is located in a second subfield of the service information field.

[0149] In this case, the information service field may include at least one of a first subfield and a second subfield in addition to the service information subfield. The first field is used to indicate the service type of the first service and is also called a service type field. The second subfield is used to indicate whether the first service is a low-latency service and is also called a low-latency flag field. The information in the second subfield, i.e., the third indication information, is also called a low-latency flag. The second subfield may include one bit or multiple bits. If the second subfield is one bit, the low-latency flag is also called a low-latency flag bit.

[0150] In an embodiment of the present application, the first NDC is an already established NDC or a newly established NDC.

[0151] The first NDL between the first NAN device and the second NAN device is used for the first NDC, and the CRB of the first NDC is used to schedule and transmit the first service on the first NDP of the first NDL.

[0152] If the first NDC is an already established NDC, the first NDC between the first NAN device and the second NAN device is already subscribed to the already established NDC, or if not subscribed to an NDC, subscribes to the first NDC. Here, if the CRB of the already established NDC is located in the first NDC schedule table, if the first NAN device is an already established NDC, there is a CRB in the first NDC schedule table that satisfies the service type / first priority of the first service.

[0153] If the first NDC is a newly established NDC, the first NAN device and the second NAN device establish the NDC based on service 1, where the NDC may be established completely anew, i.e., in a situation where no NDC schedule table exists, or the new NDC may be established by modifying the NDC schedule table based on an already established NDC schedule table to obtain a new NDC schedule table.

[0154] Here, when a new NDC schedule table is obtained by modifying an already established NDC schedule table based on the NDC schedule table, the already established NDC schedule table may be used for the first NDL between the first NAN device and the second NAN device, or may be used for the second NDL between the first NAN device and the third NAN device.

[0155] In some embodiments, if the first NDC is an already established NDC: This includes cases where a second CRB is included in the CRB of the already established NDC, and the second priority of the second CRB is lower than or equal to the first target priority, and the first target priority is a second priority corresponding to the first priority of the first service.

[0156] At least one CRB of the already established NDC includes a CRB whose second priority satisfies the scheduling of the first service, in which case the first NAN device directly uses the original NDC or joins the existing NDC without the need to establish a new NDC.

[0157] In one example, if the first service is service 2, and the first and second NAN devices establish an NDC based on service 1 and can schedule service 1 based on the CRB of the NDC, service 1 and service 2 are transmitted on the same NDC without the need to establish a new NDC.

[0158] In one example, if the first service is service 2, the first NAN device and the third NAN device establish an NDC based on service 1, and the CRB in the first NDC can be used to schedule service 1, the first NDL will join the NDC established based on service 1, and in this case, the second NAN device will join the existing NDC, i.e., the first NAN device, the second NAN device, and the third NAN device will join the same NDC.

[0159] In some embodiments, if the first NDC is a newly established NDC: Case A, where the first NAN device has not joined an already established NDC; Case B: the first NAN device has already joined an established NDC; Case C: The first NAN device is subscribed to an already established NDC, and a second CRB is included in the CRB of the already established NDC, the second priority of the second CRB is equal to or greater than the first target priority, and the first target priority is a second priority corresponding to the first priority of the first service. Case D: The first NAN device is subscribed to an already established NDC, and the second CRB is not included in the CRB of the already established NDC.

[0160] For case A, if the first NAN device has not joined the DNC, there is no NDC schedule table, in which case a new NDC schedule table is established, that is, a first NDC between the first NAN device and the second NAN device is established.

[0161] In case B, if the first NAN device has already joined an established NDC, the NDC is the NDC to which the first NDL has joined or the NDC to which the second NDL has joined, where the second NDL is the NDC between the first NAN device and the third NAN device. If the first NAN device has already joined an NDC, a new NDC can be directly established, and a new NDC schedule table can be established based on the existing NDC schedule table.

[0162] In one example, when a first NDL between a first NAN device and a second NAN device is participating in an already established NDC, and the first NAN device establishes a new NDC schedule table based on the NDC schedule table of the already established NDC, i.e., establishes a new NDC, the first NDL between the first NAN device and the second NAN device participates in the newly established NDC, and in this case, the first NDL does not belong to the already established NDC.

[0163] In one example, when a second NDL between a first NAN device and a third NAN device joins an already established NDC, and the first NAN device establishes a new NDC schedule table based on the NDC schedule table of the already established NDC, i.e., establishes a new NDC, the first NDL between the first NAN device and the second NAN device joins the newly established NDC.

[0164] For case C, if the first NAN device has already subscribed to an already established NDC, even if the NDC schedule table of the already established NDC can meet the priority requirements of the first service, the first NAN device still establishes a new NDC schedule table, and at this time, the new NDC schedule table can be established based on the existing NDC schedule table.

[0165] In one example, when a first NDL between a first NAN device and a second NAN device is subscribed to an already established NDC, and the already established NDC schedule table satisfies the priority requirement of a first service, but the first NAN device establishes a new NDC schedule table based on the NDC schedule table of the already established NDC, i.e., establishes a new NDC, the first NDL between the first NAN device and the second NAN device subscribes to the newly established NDC, and in this case, the first NDL does not belong to the already established NDC.

[0166] In one example, when a second NDL between a first NAN device and a third NAN device is subscribed to an already established NDC, the already established NDC schedule table meets the priority requirements of a first service, and the first NAN device establishes a new NDC schedule table based on the NDC schedule table of the already established NDC, i.e., establishes a new NDC, the first NDL between the first NAN device and the second NAN device subscribes to the newly established NDC.

[0167] For case D, the first NAN device has joined an already established NDC, but the NDC schedule table of the already established NDC cannot meet the priority requirements of the first service, so the first NAN device establishes a new NDC schedule table. In this case, the new NDC schedule table can be established based on the existing NDC schedule table.

[0168] In one example, when a first NDL between a first NAN device and a second NAN device is subscribed to an already established NDC, and the already established NDC schedule table satisfies the priority requirement of a first service, and the first NAN device establishes a new NDC schedule table based on the NDC schedule table of the already established NDC, i.e., establishes a new NDC, the first NDL between the first NAN device and the second NAN device subscribes to the newly established NDC, and in this case, the first NDL does not belong to the already established NDC.

[0169] In one example, when a second NDL between a first NAN device and a third NAN device is subscribed to an already established NDC, and the already established NDC schedule table meets the priority requirements of a first service, and the first NAN device establishes a new NDC schedule table based on the NDC schedule table of the already established NDC, i.e., establishes a new NDC, the first NDL between the first NAN device and the second NAN device subscribes to the newly established NDC.

[0170] In some embodiments, the already established NDC is used for a first NDL or a second NDL, and the second NDL is an NDL between the first NAN device and a third NAN device.

[0171] In some embodiments, when the first NDC is a newly established NDC and the first NAN device has already subscribed to an already established second NDC, and the second NDC is used for the second NDC, the CRBs newly added to the second NDC of the first NDC and the CRBs of the second NDC partially overlap or do not overlap in the time domain and / or frequency domain.

[0172] In one example, the CRBs of the second NDC include CRB1, where the priority of CRB1 is 4, and for the first service, the first NAN device adds CRB2 based on CRB1 to obtain CRB1 and CRB2 as the CRBs of the first NDC, where CRB2 and CRB1 partially overlap or do not overlap in the time domain and / or frequency domain.

[0173] In some embodiments, when a third CRB added to the first NDC of the second NDC and a fourth CRB of the first NDC partially overlap in the time domain and / or frequency domain, the second priority of the fourth CRB is equal to or greater than the second priority of the third CRB.

[0174] In some embodiments, when the priorities of the fourth CRB and the third CRB are the same, in the overlapping portion between the third CRB and the fourth CRB, the priority of the AC of the service scheduled in the fourth CRB is higher than the priority of the AC of the service scheduled in the third CRB.

[0175] In some embodiments, the first NAN device further performs the following operations:

[0176] The first NAN device receives a second frame transmitted from the second NAN device or transmits a second frame to the second NAN device, the second frame is used to establish a first NDP in the first NDL, and the first NDP is used to transmit the first service.

[0177] In an embodiment of the present application, the second frame includes a link establishment request frame and a link establishment response frame; When the first NAN device is an NDP requester and the second NAN device is an NDP responder, the first NAN device transmits a link establishment request frame to the second NAN device and receives a NAN link establishment response frame transmitted from the second NAN device.

[0178] When the first NAN device is an NDP responder and the second NAN device is an NDP requester, the first NAN device receives a link establishment request frame sent from the second NAN device and sends a NAN link establishment response frame to the second NAN device.

[0179] In some embodiments, when the first NDC is a newly established NDC, the second frame includes third information and fourth information, the third information is used to indicate a first tier availability window (FAW), the fourth information is used to indicate a second priority of the first FAW, the second priority of the first FAW is a first target priority, and the first target priority is a second priority corresponding to the first priority of the first service.

[0180] Here, the first FAW is: First NAN equipment's own FAW, The second NAN equipment's own FAW, FAW confirmed by the 1st NAN equipment, FAW confirmed by the second NAN device, including several cases of The second priority indicated in the second information corresponding to the first FAW is the second priority set by the NDP requester.

[0181] The first NAN device and the second NAN device can use the first FAW as a CRB for the first NDC based on the second priority of the first FAW and the first priority of the first service.

[0182] It can be understood that the second frame may also include other FAWs, and the second priority of the other FAWs is higher than the second priority corresponding to the first priority of the first service.

[0183] The fourth information is included in the NDC attribute of the second frame.

[0184] Here, the NDC attribute may include fields such as attribute ID, length, NAN data cluster ID, attribute control, and schedule entry list, where the attribute ID indicates that the attribute is an NDC attribute, and the length is the length of the NDC attribute.

[0185] The NAN data cluster ID is a unique identifier of the NDC, the attribute control indicates whether the NDC indicated in the NDC attribute already exists, the schedule entry list includes multiple schedule entry subfields, and each schedule entry is one or several NDC FAWs or CRBs of the same period.

[0186] In some embodiments, the fourth information is included in a schedule entry field in a schedule entry list of the NDC attribute.

[0187] In some embodiments, the fourth information is: fifth indication information used to indicate the priority of the first FAW, the first indication information being located in a first sub-field of the schedule entry field; a sixth indication information used to indicate whether the first FAW is used for a low-latency service, where the first FAW used for a low-latency service has the highest priority, and the second indication information includes at least one of the sixth indication information located in a second sub-field of the schedule entry field.

[0188] The schedule entry field may include a first subfield, a second subfield, and a reserved subfield.

[0189] The first sub-field in the schedule entry field includes fifth indication information indicating the priority of the first FAW, and the first sub-field in the schedule entry field is also referred to as the priority sub-field.

[0190] The second subfield in the schedule entry field is sixth indication information, i.e., low delay flag, indicating whether the first FAW is used for low delay service, and the second subfield in the schedule entry field is also called low delay subfield.

[0191] In some embodiments, if the first NDC is an already established NDC and is used for the first NDC, the second frame does not include a CRB of the already established NDC; or If the first NDC is an already established NDC and is used for a second NDL, the second frame includes a CRB of the already established NDC, and the second NDL is an NDL between the first NAN device and a third NAN device.

[0192] If the first NDC is an already established NDC and the already established NDC is used for the first NDL, the second frame for establishing the NDP between the first NAN device and the second NAN device does not need to include the CRB of the already established NDC; in this case, the second frame between the first NAN device and the second NAN device is used only to establish the first NDP, i.e., to confirm that communication is required, and does not need to include NDC attributes.

[0193] If the first NDC is an already established NDC and the already established NDC is used for the second NDC, the second frame for establishing the NDP between the first NAN device and the second NAN device includes the CRB of the already established NDC.

[0194] In the embodiment of the present application, the current NAN cluster has three devices, STA1, STA2, and STA3, and STA1 has two services, service 4 and service 6, with service priorities of 4 and 6, respectively.

[0195] As an issuer, STA1 has two options:

[0196] In option 1, service 4 is issued first, and then service 6 is issued after a few DWs.

[0197] In option 2, services 4 and 6 are issued at the same time.

[0198] In the case of option 1, STA2 and STA1 subscribe to service 4 through the service discovery phase, and then perform two handshakes to establish the data path. In the data path phase, the NDL Schedule Initial Proposal sent by STA1 to STA2 includes the NAN availability attribute and the NDC attribute. The NAN availability attribute is the FAW available to STA1, and the NDC attribute is the NDC schedule table proposed by STA2. At this time, the schedule information in the NDC attribute is Map ID 2, channel, bit duration 16TU, priority 4, low latency identifier 0, and time bitmap 11100.

[0199] The NAN availability attribute of the NDL Schedule Compliant Proposal returned by STA1 is also its own FAW, and since it is a two-handshake, the schedule of the NDC attribute is also the same as above.

[0200] Since this is the first establishment between STA1 and STA2, the NDL schedule table and NDC schedule table shown in FIG. 14A are established at the same time.

[0201] Next, service 6 is published / subscribed again between STA1 and STA2, and at this time, there is no FAW with priority 6 in the already established NDC schedule table. In this case, the following two cases are possible:

[0202] In case 1, an existing NDC schedule table can be selected, and although there is no FAW with priority 6 in the current schedule table, a data frame of a service with priority 6 can be transmitted on an FAW with priority 4.

[0203] In case 2, a new NDC schedule table can be established.

[0204] In case 1, the path establishment request or path establishment response at the data path establishment stage does not include the NDC attribute, and the process at this time simply determines that both parties need to communicate service 6 (i.e., establish NDP).

[0205] In case 2, the path establishment request or path establishment response in the data path establishment phase includes an NDC attribute, and the NDL schedule table information in the NDC attribute includes map IDs 2 and 2, channel, bit durations 16TU and 16TU, priorities 6 and 4, low latency identifiers 0 and 0, and time bitmaps 0000000000111 and 11100000000000.

[0206] After the negotiation is completed, the NDC schedule table between STA1 and STA2 negotiated based on the above NDC schedule table information is as shown in Fig. 14B. The NDC schedule table shown in Fig. 14B is different from the original NDC schedule table shown in Fig. 13A, and the original NDC schedule table shown in Fig. 13A may still exist and may be used by other devices.

[0207] At this time, if device 3 needs to subscribe to service 4 or service 6 or subscribe to them simultaneously, since this is the first time a data path is established between STA1 and STA3, the NDL and NDC schedule tables must be established simultaneously. During the establishment process, if the NDL CRB between STA3 and STA1 can satisfy the NDC schedule table between STA1 and STA2, direct selection is possible. If direct selection is possible, the NDL schedule table information included in the NDC attribute includes map IDs 2 and 2, channel, bit durations 16TU and 16TU, priorities 6 and 4, low latency identifiers 0 and 0, and time bitmaps 0000000000111 and 11100000000000.

[0208] 13B cannot meet the service requirements between STA3 and STA1, a new NDC schedule table needs to be established. When a new NDC schedule table needs to be established, the NDC schedule table between STA1 and STA2 needs to be referenced, and the time domain and frequency domain need to be shifted as much as possible.

[0209] In case 2, in the initial NDP establishment stage, there is a possibility that the NDC attribute information contained in the path establishment request or path establishment response may simultaneously contain CRBs with priorities of 4 and 6, so the generated NDC schedule table and NDL schedule table are as shown in Figure 14B.

[0210] At this time, if device 3 needs to subscribe to service 4 or service 6 or subscribe to them simultaneously, since this is the first time a data path is established between STA1 and STA3, the NDL and NDC schedule tables need to be established simultaneously. During the establishment process, if the NDL CRB between STA2 and STA1 can satisfy the NDC schedule table between STA1 and STA3, it can be directly selected; if not, a new NDC schedule table needs to be established. When a new NDC schedule table needs to be established, the NDC schedule table between STA1 and STA2 should be referenced and the time and frequency domains should be shifted as much as possible.

[0211] Assuming that STA1 and STA2 have already established NDC schedule tables, if STA1 issues service 6 and STA2 subscribes to service 6, in addition to the two cases above, there is actually another special case in the NDC schedule tables between the two devices, which is the case where the current NDL CRB cannot satisfy the new NDC schedule table. In this case, the NDL schedule table needs to be updated, and a new NDC schedule table is established simultaneously during the update process. This new NDC schedule table needs to satisfy not only the previous service 4 but also the current service 6.

[0212] The process of updating the NDL schedule table is exactly the same as the process of establishing the NDL and NDC.

[0213] In some embodiments, when the already established NDC is used for a second NDC, the method further comprises: The method further includes the first NAN device receiving a CRB of a second NDC transmitted from the third NAN device, the second NDC being an already established NDC used for the second NDL.

[0214] As shown in FIG. 14, it includes the following steps:

[0215] In step S1401, the first NAN device receives the CRB of the second NDC transmitted from the third NAN device.

[0216] In step S1402, the first NAN device uses the CRB of the second NDC or establishes the CRB of the first NDC based on the CRB of the second NDC.

[0217] In some embodiments, the first NAN device receiving a CRB of a second NDC transmitted from the third NAN device includes: The first NAN device receives a third frame transmitted from the third NAN device, the third frame including a CRB of the second NDC, and the third frame belonging to a broadcast frame.

[0218] After acquiring the CRB of the second NDC, the third NAN device broadcasts a third frame and includes the CRB of the second NDC in the third frame, thereby enabling NAN devices, including the second NAN device, around the third NAN device to receive the NDC schedule table of the third NAN device.

[0219] In some embodiments, the third frame further includes fifth information, which is used to indicate whether the CRB of the second NDC included in the third frame is broadcast on behalf of a NAN-controlled device or a NAN-uncontrolled device in a synchronized state.

[0220] A NAN control device can be understood to be a master, and a NAN non-control device in a synchronized state can be understood to be a non-master in a synchronized state.

[0221] The Master and Non-master can synchronize the NDC schedule table with other NAN devices using a synchronization beacon frame.

[0222] If the fifth information is used to indicate that the CRB of the second NDC included in the third frame is broadcast on behalf of a NAN-controlled device or a NAN-non-controlled device in a synchronized state, when the first NAN device is a Master or Non-master, it broadcasts the CRB of the received second NDC.

[0223] If the fifth information is used to indicate that the CRB of the second NDC included in the third frame will not be broadcast on behalf of a NAN-controlled device or a NAN-non-controlled device in a synchronized state, when the first NAN device is a Master or Non-master, it does not broadcast the CRB of the received second NDC.

[0224] In an embodiment of the present application, depending on the value of the fifth information, it can be used to indicate that the CRB of the second NDC is broadcast on behalf of a NAN-controlled device or a non-NAN-controlled device in a synchronized state, or that the CRB of the second NDC is not broadcast on behalf of a NAN-controlled device or a non-NAN-controlled device in a synchronized state.

[0225] In one example, if the value of the fifth information is 0, it indicates that the CRB of the second NDC is broadcast on behalf of a NAN-controlled device or a NAN-non-controlled device in a synchronized state, and if the value of the fifth information is 1, it indicates that the CRB of the second NDC is not broadcast on behalf of a NAN-controlled device or a NAN-non-controlled device in a synchronized state.

[0226] When the first NAN device is a NAN-controlled device or a non-NAN-controlled device in a synchronized state, and the fifth information indicates that the CRB of the second NDC included in the third frame is broadcast on behalf of the NAN-controlled device or a non-NAN-controlled device in a synchronized state, the method includes: The method further includes the first NAN device transmitting a fourth frame, wherein the fourth frame includes a CRB of the second NDC, and the fourth frame belongs to a broadcast frame.

[0227] Here, if the first NAN device is a Master or Non-master, it can broadcast the CRB of the second NDC using the fourth frame.

[0228] In some embodiments, the fifth information is located in a first field of an NDC attribute of the third frame.

[0229] In some embodiments, the method further comprises: The method further includes the first NAN device locally deleting the CRB of the second NDC if the first NAN device does not receive the CRB of the second NDC in a first number of consecutive discovery windows (DWs).

[0230] A NAN scheduler is disposed in the first NAN device, and if the NAN scheduler does not receive a CRB of the second NDC in a first number of consecutive DWs, it considers the second NDC to which the CRB of the second NDC applies to be released and deletes the CRB of the second NDC from the local.

[0231] The size of the first quantity can be set according to actual needs, for example, 5, 8, 10, etc.

[0232] In some embodiments, the first NAN device broadcasts a CRB of the first NDC.

[0233] After determining the CRBs of the first NDC, the first NAN device broadcasts the CRBs of the first NDC, allowing NAN devices adjacent to the first NAN device to receive the CRBs of the first NDC and know which CRBs are used to transmit services and the priority of each of these CRBs, thereby establishing an NDC based on the known CRBs and CRB priorities.

[0234] In some embodiments, the first NAN device broadcasting the CRB of the first NDC comprises: The first NAN device transmits a fifth frame, the fifth frame including a CRB of the first NDC, and the fifth frame belonging to a broadcast frame.

[0235] In some embodiments, the fifth frame further includes sixth information, which is used to indicate whether the CRB schedule table of the first NDC included in the fifth frame is broadcast on behalf of a NAN-controlled device or a NAN-uncontrolled device in a synchronized state.

[0236] Here, the fifth information and the sixth information are located in different frames but have the same role, where the fifth information is located in the third frame and the sixth information is located in the fifth frame.

[0237] If the first NAN device does not need the CRB of the first NDC to be broadcast on its behalf by a NAN-controlled device or a non-NAN-controlled device in a synchronized state, the sixth information can be set to indicate that the CRB of the first NDC will not be broadcast on its behalf by a NAN-controlled device or a non-NAN-controlled device in a synchronized state.If the first NAN device wants the CRB of the first NDC to be broadcast on its behalf by a NAN-controlled device or a non-NAN-controlled device in a synchronized state, the sixth information can be set to indicate that the CRB of the first NDC will be broadcast on its behalf by a NAN-controlled device or a non-NAN-controlled device in a synchronized state.

[0238] In some embodiments, the sixth information is located in the first field of the NDC attribute of the fifth frame.

[0239] In some embodiments, the first field is a reserved field.

[0240] Here, information indicating whether the CRB of the NDC is broadcast on behalf of a NAN-controlled device or a NAN-uncontrolled device in a synchronized state is included in a reserved field of the DC attribute.

[0241] In some embodiments, the broadcast frame comprises: Service Discovery Frame (SDF), Neighbor Sense Network Action Frame (NAF), a synchronization beacon frame.

[0242] Here, the application scenarios of the SDF, NAF, and synchronization beacon frame are different.

[0243] In the case of SDF, it is broadcast by the service issuer at the start of the DW, In the case of NAF, it is broadcast at any timing by the service issuer or service subscriber, at which time the restriction of broadcasting within the DW is lifted.

[0244] A synchronization beacon frame is broadcast by a Master or a Non-master in a synchronized state.

[0245] The first NAN device may broadcast the CRB of the first NDC by broadcasting the broadcast frame once or at least twice, depending on the scenario.

[0246] Assuming there is one NDC schedule table between STA1 and STA2, the peripheral devices are as shown in FIG. 14C.

[0247] In DW, STA1 and STA2 broadcast the NDC schedule table, and STA3 can receive such a broadcast frame. Then, STA3 knows that there is an NDC schedule table around it, and the scheduler of STA3 records the NDC schedule table.

[0248] At some point, when the service communication between STA1 and STA2 ends (assuming there is only one service), both of them leave the NDC (they may or may not leave, but it is assumed here that they leave), meaning that STA1 and STA2 no longer execute the NDC schedule table, and therefore STA1 and STA2 no longer broadcast the NDC schedule table in subsequent DWs. As a result, STA3 is no longer able to receive information from the original NDC schedule table in multiple consecutive DWs, and STA3 considers the original NDC schedule table to have been deleted, and the STA3 scheduler also deletes the record of the original NDC schedule table.

[0249] STA3 receives a broadcast frame from a peripheral device, and if the broadcast frame contains NDC schedule table information, it records it. If STA3 does not receive the recorded NDC schedule table information in multiple consecutive DWs, it considers that the recorded NDC schedule table has disappeared, and STA3 deletes the corresponding NDC schedule table from its own records.

[0250] If there are two services between STA1 and STA2 (assuming priorities are 4 and 6) and one of the services (assuming service 4) terminates communication at some point, the NDC schedule table should still contain CRBs with priorities 4 and 6, but there will now only be one service (service 6) between STA1 and STA2.

[0251] In the following, the service scheduling method according to the embodiment of the present application will be further described by taking the example that the priority of the service and the priority of the CRB are the same, level 8.

[0252] The embodiments of the present application propose a method for labeling and classifying NDC CRBs, so that Wi-Fi Aware can better support different types of services. Let us assume that some FAWs in an NDC are labeled, and that the CRBs (NDC CRB(1,2)) of the NDC to which the NDL between STA1 and STA2 subscribes are labeled with priorities 7 and 4, as shown in FIG. 10 .

[0253] Data frames for low-latency services between STA1 and STA2 may be transmitted in a low-latency CRB or in a non-low-latency CRB with a priority of 4. On the other hand, data frames for services with a priority of 4 are only allowed to be transmitted in a CRB with a priority of 4.

[0254] Service publishers and subscribers must voluntarily broadcast the status of their FAW or CRB markings in the DW by their SDF or NAF.

[0255] When STA3 and STA4 receive the priority of each CRB of the NDC CRB broadcast by STA1 and STA2, respectively, and use it as a reference when establishing a subsequent new NDC, services with the same or higher priority may use a CRB of the same segment, or may select a CRB of another segment based on their own resources. Services with lower priority should avoid the marked CRB.

[0256] Since STA5 and STA6 cannot receive the broadcasts of STA1 and STA2, there is no need for these two STAs to avoid the CRBs marked by STA1 and STA2 when establishing NDC.

[0257] In an embodiment of the present application, the NAN device divides the NDC CRBs into different priorities according to the service categories, i.e., service types, it supports, and data frames of services of different service types are preferentially scheduled in FAWs or CRBs of corresponding predefined priorities, and data frames of high-priority services can also be scheduled in FAWs or CRBs of lower priorities.

[0258] A service type field is added to the service description attribute, and a NAN device transmits a service discovery frame including the service description attribute during the service discovery phase, broadcasting the services that the device has and also broadcasting the service categories, allowing the NAN device to obtain the services and service categories of other NAN devices in the vicinity.

[0259] The NDC attribute is modified to add a priority field and a low latency flag bit to the NDC attribute. Meanwhile, when the service issuer and service subscriber negotiate the NDL CRB and the NDC CRB in the data path establishment process, depending on the service category and whether it is a low latency service or not, the negotiated NDC CRB part can be marked as a FAW or CRB of the same priority, or a FAW or CRB for a low latency service. The NDP establishment phase is divided into the following two cases:

[0260] In Case 1, if the NAN device pair has one NDC schedule table and the NDC schedule table contains an FAW or CRB whose priority is the same as or lower than the service priority, the devices can directly select the existing NDC schedule table. If the NDC schedule table does not contain an FAW or CRB whose priority is the same as or lower than the service priority, the NAN device pair will establish a new NDC. When establishing a new NDC, if the current NDL CRB does not satisfy the new NDC requirements, an NDL scheduling update program is initiated to satisfy the existing service, and then the new NDC is satisfied by updating the NDL CRB and NDC CRB. The NDL scheduling update program is the same as the NDP establishment program.

[0261] In case 2, the NAN device pair does not have an NDC schedule table, and the NAN device pair must negotiate the NDL, NDC FAW or CRB based on the service category, mark the FAW or CRB, and distinguish the priority of the FAW or CRB.

[0262] After the data path is established, both NAN devices can prioritize and transmit data frames of the same or higher priority services in the FAW or CRB of the specified priority.

[0263] In a scenario where low-latency services are differentiated, the FAW or CRB for the low-latency service transmits the data frames of the low-latency service preferentially, and the data frames of the non-low-latency service are only scheduled and transmitted in the FAW or CRB of the non-low-latency service. The data frames of the low-latency service can also be transmitted within the non-low-latency FAW or CRB. In this case, the data frames of the low-latency service use a high-priority access method, for example, adopting a queue and EDCA parameters with a priority of 7, and the non-low-latency service uses a low-priority access method.

[0264] In a scenario where different priority services are differentiated, in a FAW or CRB of one segment, scheduling of data frames of services whose priority is equal to or higher than the priority of the FAW or CRB is allowed, in which case the data frames of the high priority service use a high priority access method, for example, adopting a high priority queue and EDCA parameters, and the data frames of the low priority service use a low priority access method, for example, adopting a low priority queue and EDCA parameters.

[0265] On the other hand, after the data path establishment is completed, the service publisher and the service subscriber need to broadcast the NDC schedule table of the FAW or CRB with the negotiated priority in the subsequent DW by the service discovery frame or NAN action frame (NAF), and can also use the master or non-master sync device to broadcast it on their behalf. A notification flag subfield is added to the attribute control field of the NDC attribute, and when the service publisher and the subscriber send a frame of the NDC schedule table information of the FAW or CRB with the priority, they set the notification flag in the attribute control field of the NDC attribute to 0 to indicate that they want the NDC schedule table information to be broadcast on their behalf by the master or non-master sync device. After the master or non-master sync device receives the frame, the scheduler records the NDC schedule table information and broadcasts it in the subsequent DW, where the notification flag in the attribute control field of the NDC attribute is set to 1 to indicate that they do not want the NDC schedule table information in the frame to be broadcast by the master or non-master sync device.

[0266] After another device receives the NDC schedule table of the FAW or CRB with priority, the scheduler records the NDC schedule table of this FAW or CRB with priority. If another device wants to establish or join NDC at a later time, it needs to refer to the information in the existing NDC schedule table. Specifically, there are two cases:

[0267] Case 1 is a scenario that distinguishes between low-latency and non-low-latency services.

[0268] (a) Regarding FAWs or CRBs for low-latency services in the NDC Schedule Table, regardless of whether the service requested by the device itself belongs to the low-latency service, it is necessary to ensure that the FAWs or CRBs negotiated under conditions that meet the service needs are shifted in the time domain or frequency domain from the FAWs or CRBs for low-latency services in the existing NDC Schedule Table.

[0269] (b) If the service requested by the device itself is a low-latency service, it is necessary to ensure that the negotiated FAW or CRB under conditions that meet the service needs is offset in the time domain or frequency domain from the existing FAW or CRB in the existing NDC schedule table.

[0270] (c) In a scenario where an FAW or CRB for a low-latency service in the NDC schedule table overlaps with an FAW or CRB for a non-low-latency service in the time domain or frequency domain, the low-latency service is given priority in access to the overlapping FAW or CRB, for example, the low-latency service will compete for the channel using EDCA parameters with a priority of 7, and the non-low-latency service will compete for the channel using EDCA parameters with a relatively lower priority.

[0271] Case 2 is a scenario that classifies service priorities, and can be divided into the following three cases according to service priorities.

[0272] (a) If the priority of a service is higher than the priority of the FAW or CRB included in the NDC schedule table, the device can selectively establish a new NDC, i.e., a new NDC schedule table, based on its own resources. The new NDC schedule table includes FAWs or CRBs whose priorities are the same as or lower than the priority of the service. The new NDC schedule table can also include FAWs or CRBs for low-priority services included in the original NDC schedule table. Data frames of high-priority services may be preferentially transmitted in high-priority FAWs or CRBs, or may be transmitted in low-priority FAWs or CRBs. In this case, data frames of high-priority services use the high-priority access method, and data frames of low-priority services use the low-priority access method. The device can also selectively directly join the current NDC based on its own resources and use the current NDC schedule table.

[0273] (b) If the priority of the service is equal to the priority of the FAW or CRB included in the NDC Schedule Table, the device can choose to establish a new NDC, i.e., establish a new NDC Schedule Table, and similarly to the above, the new NDC Schedule Table can mark a new FAW or CRB of one segment, or can select a FAW or CRB included in the original NDC Schedule Table, i.e., can choose to directly join the current NDC and use the current NDC Schedule Table.

[0274] (c) If the priority of the service is lower than the priority of the FAW or CRB included in the NDC Schedule Table, the device must establish a new NDC, and the FAW or CRB included in the NDC Schedule Table of the new NDC must avoid the FAW or CRB for the higher priority service in the original NDC Schedule Table.

[0275] In the Wi-Fi Aware standard, SDF is used to publish and subscribe to services, so the SDF also contains a description of service information. As shown in Figure 16, the SDF format includes a one-octet category field, a one-octet action field, a three-octet Organizationally Unique Identifier (OUI) field, a one-octet OUI type field, and a variable-octet NAN attribute field.

[0276] The service descriptor attribute of the NAN attribute contains information about the service. The format of the service descriptor attribute is shown in Figure 17 and includes the following fields:

[0277] Attribute ID field: The value is fixed to 0x03 and is used to identify the type of NAN attribute.

[0278] Length: The length of the service description attribute.

[0279] Service ID: The value is a hash value of the service name.

[0280] Instance ID: The value is either Publish_ID or Subscribe_ID depending on the role of the device sending the frame.

[0281] Requester Instance ID: The instance ID within the frame that triggers this frame.

[0282] Service Control: Some information that defines the service control bitmap.

[0283] Binding bitmap: Used to indicate the post discovery connection attributes bound to the service description attribute.

[0284] Match filter field length: Indicates whether the match filter field is present.

[0285] Match filter field: Some filtering conditions for service discovery.

[0286] Service Response Filter Field Length: Indicates whether a service response filter field is present.

[0287] Service Response Filter Field: Allows a potential responder to decide whether or not it should respond to the NAN SDF, and only considers the field further if the responder satisfies the service ID and match filter conditions.

[0288] Service Information Field Length: Indicates whether the service information field is present.

[0289] Service Information Field: Contains service specific information and is specified by the higher layer service.

[0290] In the embodiment of the present application, as shown in FIG. 17, the first three bits of the service information field are used as a Service Type subfield to indicate the type or priority of the service represented by the service description attribute, and the fourth bit is a Low latency flag bit to indicate whether the service is a low latency type service.

[0291] The service type or priority corresponds one-to-one with the eight user priorities (UP) of EDCA, and the queueing of data frames for the service and the parameters used when accessing the channel are determined based on the service type or priority.

[0292] The service priorities corresponding to the values ​​of the Service Type subfield are as shown in Table 1.

[0293] [Table 1]

[0294] Here, the priority of service type 0 to service type 7 increases in order, with service type 0 having the lowest priority and service type 7 having the highest priority.

[0295] Regarding the low latency flag bit, if the value of the low latency flag bit is 1, it indicates that the service is a low latency service, and the value of the service type subfield must be set to 7. When a data frame of a low latency service is transmitted within a non-low latency FAW or CRB, the highest priority EDCA parameters are adopted. An example of the setting of the low latency flag bit is shown in Table 2.

[0296] [Table 2]

[0297] The format of the NAN availability attribute in Wi-Fi Aware is shown in FIG. 18 and includes the following fields:

[0298] Attribute ID: Indicates the type of the attribute.

[0299] Length: NAN Indicates the length of the availability attribute.

[0300] Sequence ID: Indicates the broadcast order of availability scheduling information, with a larger value indicating newer availability scheduling information.

[0301] Control Attribute: Some control information that indicates the FAW represented by the NAN availability attribute, such as an indication of whether the availability scheduling information of the NAN device has changed.

[0302] Availability Entry List: Contains multiple availability entries, each of which represents one or a series of periodic FAWs.

[0303] The Availability Entry List field contains one or more availability entries, and the format of each availability entry subfield is as shown in FIG. 19, and includes the following fields:

[0304] Length: Indicates the length of the availability entry subfield.

[0305] Entry Control: Some control information that indicates the availability entry, such as the type of availability entry.

[0306] Time Bitmap Control: Some control information that indicates the time bitmap, such as the length of each bit.

[0307] Time Bitmap Length: Indicates the length of the Time Bitmap field.

[0308] Time bitmap: Time information indicating the availability entry.

[0309] Band / Channel Entry List: Indicates the bands and channels supported by the availability entry.

[0310] Each availability entry represents one or several FAWs of the same period, and a NAN device indicates the FAWs it owns by including a NAN availability attribute in its SDF, beacon frame, or NAF.

[0311] A frame can include one or more NAN availability attributes. The Map ID subfield in the Attribute Control field serves to distinguish between different NAN availability attributes. The format of the Attribute Control field is shown in Figure 20, and includes the following fields: A map ID, which is a unique identifier for the NAN availability attribute; and It includes fields that respectively indicate whether information such as accepted FAW, potential FAW, common availability attributes, and NDC attributes has changed.

[0312] The SDF, beacon frame or NAF may also include an NDC attribute, and the format of the NDC attribute includes the following fields as shown in FIG.

[0313] Attribute ID: Indicates that the attribute is an NDC attribute.

[0314] Length: The length of the NDC attribute.

[0315] NAN Data Cluster ID: A unique identifier for the NDC.

[0316] Attribute Control: Indicates whether the NDC indicated in the NDC attribute already exists.

[0317] Schedule entry list: Contains multiple schedule entry subfields, where each schedule entry is one or several NDC FAWs or CRBs of the same period.

[0318] The Schedule Entry List field contains one or more schedule entries, and the format of each schedule entry subfield is as shown in FIG. 22, and contains the following fields:

[0319] Map ID: If the map ID in this subfield is the same as the map ID in the attribute control of the NAN availability attribute, it indicates that the schedule entry is associated with the NAN availability attribute.

[0320] Time Bitmap Control: Some control information that indicates the time bitmap.

[0321] Time bitmap length: Indicates the length information of the time bitmap.

[0322] Time Bitmap: Indicates the time information of the schedule entry.

[0323] Entry Control: Indicates the category of the schedule entry.

[0324] Each schedule entry is one or several FAWs of the same period in the NDC CRB, and the schedule entry only indicates the time bitmap of the FAW, and does not indicate information such as channel, band, etc. By setting the value of Map ID to the same value as the value of Map ID in the Attribute Control field of the NAN availability attribute, the schedule entry and the corresponding NAN availability attribute are associated, and information such as channel, band, etc. of the associated NAN availability attribute is obtained.

[0325] In the embodiment of the present application, an entry control field is added to the schedule entry subfield, which includes a priority subfield and a low latency flag bit, where the priority subfield number is shown in Table 3.

[0326] [Table 3]

[0327] The priority of a FAW corresponds one-to-one with the type or priority of a service, and within a FAW of a specified priority, only data frames of services with a priority equal to or greater than the priority of the FAW are allowed to be transmitted. Data frames of high-priority services are queued in a queue corresponding to their priority and access the channel using a higher-priority scheme, e.g., using high-priority EDCA parameters, while data frames of low-priority services access the channel using a lower-priority scheme, e.g., using low-priority EDCA parameters.

[0328] Data frames of high-priority services can be transmitted in FAWs or CRBs of low-priority services. In this case, data frames of high-priority services and data frames of low-priority services do not belong to the same queue and have different channel access priorities, so the requirement that data frames of high-priority services be transmitted preferentially can also be met.

[0329] In one example, the notation of FAW or CRB priority by NAN availability attribute, NDC attribute is shown in Table 4.

[0330] [Table 4]

[0331] In Table 4, there are two NAN availability attributes:

[0332] The map identifier (Map ID) is 1, the operating channels are 36 and 149, the duration of each bit in the bitmap is 64 TU (1 TU = 1024 us), there are two Availability Entries, the duration of the FAW represented by the entry for channel 36 is 64 to 127 TU after the DW, and the duration of the FAW represented by the entry for channel 149 is 128 to 255 TU after the DW.

[0333] The Map ID is 2, the operating channel is 6, there is one Availability Entry, and the duration of each bit is 16 TU. This Entry represents an FAW that operates on channel 6 and has a duration of 0 to 63 TU after the DW.

[0334] In Table 4, there is only one NDC attribute, and that NDC attribute has three Schedule Entries.

[0335] The Map ID of the first Schedule Entry is 1, and is associated with a NAN availability attribute whose Map ID is 1, so the operating channels of that Schedule Entry are 36 and 149. The duration of each bit is 16 TU, and the Priority value is 0, so that Schedule Entry represents an FAW whose duration after DW is 64 to 95 TU and whose priority is 0, and FAWs during this period occupy only channel 36, so the FAW with priority 0 represented in that Schedule Entry occupies channel 36.

[0336] The Map ID of the second Schedule Entry is 2, and since it is associated with the NAN availability attribute whose Map ID is 2, the operating channel is 6, and the Priority value of the Schedule Entry is 7, which indicates that the priority of the FAW operating on channel 6 and having a duration of 0 to 31 TU after the DW is 7.

[0337] The third Schedule Entry has a Map ID of 2 and a Priority value of 0, and therefore represents a FAW that operates on channel 6, has a duration of 32 to 63 TU after DW, and has a priority of 0.

[0338] Assume that STA1 has three services with different priorities, and the service priorities are 0, 6, and 7, respectively. After the data path establishment process, the NDL CRB, NDC CRB, and negotiated FAW or CRB priority status between STA1 and STA2 are as shown in Figure 23.

[0339] Classify the priority of all FAWs or CRBs in the NDC as 0, 6, or 7.

[0340] During the FAW or CRB period of priority 7, STA1 and STA2 transmit only data frames of services with priority 7, and do not transmit data frames of services with other priorities.

[0341] During the FAW or CRB period of priority 6, STA1 and STA2 can transmit data frames of services with priorities 7 and 6, respectively, but do not transmit data frames of services with priority 0.

[0342] During the FAW or CRB period with a priority of 0, STA1 and STA2 can transmit data frames of services with any priority.

[0343] By marking and classifying FAWs or CRBs based on service priority, a device can only transmit data frames of services with a priority equal to or higher than the FAW or CRB priority in the FAW or CRB, thus ensuring the quality of service of a particular priority.

[0344] During a FAW or CRB period with a priority of 0, STA1 and STA2 can transmit data frames of three services. Since the priorities of these three services are different, the data frame ordering is different, and the parameters used for channel access are also different. Since the EDCA parameters used by data frames of high-priority services have higher priority, the requirement that data frames of high-priority services be transmitted preferentially within the same FAW or CRB can be met to some extent.

[0345] The low latency flag bit in the entry control field indicates whether the entry is used to transmit data frames of the low latency service. The role of the low latency flag bit is shown in Table 5.

[0346] [Table 5]

[0347] Based on Table 5, if the value of the low latency flag bit is 1, it indicates that the scheduling is a schedule entry dedicated to data frame transmission of low latency service, and the value of the priority subfield should be set to 7.

[0348] Examples of notation of the low latency category of FAW or CRB by NAN availability attribute and NDC attribute are shown in Table 6.

[0349] [Table 6]

[0350] In Table 6, there are two NAN availability attributes:

[0351] The Map ID is 1, the operating channels are 36 and 149, the duration of each bit in the map is 64 TU (1 TU = 1024 us), there are two Availability Entries, the duration of the FAW shown in the entry for channel 36 is 64 to 127 TU after DW, and the duration of the FAW shown in the entry for channel 149 is 128 to 255 TU after DW.

[0352] The Map ID is 2, the operating channel is 6, there is one Availability Entry, and the duration of each bit is 16 TU. This Entry represents an FAW that operates on channel 6 and has a duration of 0 to 63 TU after the DW.

[0353] In Table 6, there is only one NDC attribute, and that NDC attribute has three Schedule Entries.

[0354] The Map ID of the first Schedule Entry is 1, and it is associated with a NAN availability attribute whose Map ID is 1, so the operating channels of that Schedule Entry are 36 and 149. The duration of each bit is 16 TU, and the Priority value is 0, so that Schedule Entry represents an FAW with a duration of 64 to 95 TU after DW and a priority of 0, and FAWs during this period occupy only channel 36, so the FAW with a priority of 0 represented by that Schedule Entry occupies channel 36.

[0355] The Map ID of the second Schedule Entry is 2, and since it is associated with the NAN availability attribute whose Map ID is 2, the operating channel is 6, and the Priority value of the Schedule Entry is 0, which indicates that the priority of the FAW operating on channel 6 and having a duration of 0 to 31 TU after the DW is 0.

[0356] The third Schedule Entry has a Map ID of 2, a Priority value of 7, and a low latency flag bit of 1, so this entry represents a FAW for a low latency service that operates on channel 6 and has a duration of 32 to 63 TU after DW.

[0357] Assume that STA1 has two different services, one of which is a low-latency service and the other is a non-low-latency service, and the service priority is 5. After the data path establishment process, the NDL CRB, NDC CRB, and negotiated FAW or CRB priority status between STA1 and STA2 are as shown in Figure 24.

[0358] All FAWs or CRBs in the NDC are classified into FAWs or CRBs for low latency services and FAWs or CRBs for specific priority services.

[0359] Within the FAW or CRB for the low latency service, only data frames for the low latency service are scheduled and transmitted.

[0360] Within a FAW with a priority of 5, data frames of a service with a priority of 5 are scheduled, and data frames of a low-latency service can also be scheduled. In this case, the data frames of the low-latency service have a priority of 7 and use a high-priority access method, for example, an EDCA sequence matrix and parameters with a priority of 7, and data frames of a service with a priority of 5 use an EDCA sequence matrix and parameters with a priority of 5.

[0361] The service requirements of low-latency services can be met by dividing FAWs or CRBs into FAWs or CRBs for low-latency services and FAWs or CRBs for non-low-latency services. When a data frame of a low-latency service needs to be transmitted using a FAW or CRB for a non-low-latency service, a high-priority access method can be used to meet, to some extent, the requirement that data frames of low-latency services be preferentially transmitted.

[0362] The format of the Attribute Control field of the NDC attribute is shown in Figure 25 and includes the following fields:

[0363] Selected NDC: Indicates whether the FAW or CRB information indicated in the NDC attribute is the FAW or CRB of an existing NDC.

[0364] Notification flag: Indicates whether the NDC attribute is broadcast on behalf of a master or non-master sync device.

[0365] In the embodiment of the present application, one bit is selected from the seven bits originally reserved for Attribute Control and used as a notification flag, which is used to indicate whether the NDC schedule table information of the FAW or CRB with priority is notified by both the service issuer and the service subscriber, or is notified on behalf of the master or non-master sync device. After the NDC is established, both STAs must send an SDF or NAF in the subsequent DW, which includes the NDC schedule table information of the FAW or CRB with priority.

[0366] 1. If the frame sent by the service publisher or subscriber contains the NDC schedule table information of FAW or CRB with priority, the notification flag value may be set to 0, and if both devices of the service do not want to broadcast on behalf of the master or non-master sync device, the notification flag value may be set to 1.

[0367] 2. If the frame sent by the master or non-master sync device contains NDC schedule table information of FAW or CRB with priority, set the value of the notification flag to 1.

[0368] 3. If the service publisher or subscriber is a master or non-master sync device, if the frame to be transmitted contains NDC schedule table information of FAW or CRB with priority, set the notification flag value to 1.

[0369] 4. When a master or non-master sync device receives a frame with a notification flag of 0 and containing NDC schedule table information for a FAW or CRB with priority, it must include NDC schedule table information for a FAW or CRB with priority in the synchronization beacon frame it transmits in the subsequent DW.

[0370] 5. When a master or non-master sync device receives a frame containing NDC schedule table information of a FAW or CRB with a notification flag of 1 and a priority, there is no need to perform proxy notification.

[0371] Assume that STA1 and STA2 have already established NDC and the FAW or CRB marking status is as shown in Figure 23. Assume that the status of some devices in the NAN cluster is as shown in Figure 26. In this case, there are three cases:

[0372] In case 1, STA1 and STA3 create or subscribe to an NDC.

[0373] In case 2, STA3 and STA4 create or subscribe to an NDC.

[0374] In Case 3, STA5 and STA6 create or subscribe to NDC.

[0375] In case 1, STA1 and STA3 negotiate the communication path establishment process, and STA1 includes the NAN availability attribute and NDC attribute in the frame and notifies STA3 of the current NDC CRB status, including the FAW designation and classification information. If the service priority between STA3 and STA1 is 7, STA1 and STA3 can establish a new NDC. The new NDC can use any resources owned by both devices and can also choose to join the NDC included in STA1. If the service priority between STA3 and STA1 is 6, STA1 can choose to establish a new NDC, and the NDC CRB cannot occupy the FAW with priority 7. If the service priority between STA3 and STA1 is 5 or lower, STA1 can only choose to establish a new NDC, and the NDC CRB cannot occupy the FAW with priority 6 or 7. The data path establishment process between STA1 and STA3 is shown in Figure 27 and includes the following steps: In step S2701, the NDP initiator, i.e., the NDP requester, sends a data path request frame to the NDP responder. In step S2702, the NDP responder sends a data path response frame to the NDP initiator. In step S2703, the NDP initiator sends a data path confirmation frame to the NDP responder. Here, in the service discovery stage before the data path establishment process, the values ​​of the priority and low service delay flag in the NDC attribute are consistent with the values ​​in the NDC schedule table, the service type value in the service description attribute is set according to the service type, and the notification flag in the NDC attribute is set to 0.

[0376] For Case 2, during the DW period, STA1 can broadcast the NDC schedule table information between STA1 and STA2 by including the NAN availability attribute and NDC attribute in the SDF or NAF, and STA2 can also broadcast the NDC schedule table information between STA1 and STA2 by including the NAN availability attribute and NDC attribute in the NAF. In addition, master and non-master sync devices around STA1 and STA2 can also broadcast the NDC schedule table information between STA1 and STA2 by including the NAN availability attribute and NDC attribute in the synchronization beacon frame on behalf of STA1 and STA2.

[0377] After receiving the NDC schedule table information between STA1 and STA2, STA3 and STA4 use the NDC schedule table information between STA1 and STA2 as reference when establishing or joining an NDC. If the service priority between STA3 and STA4 is 7, STA4 and STA3 can establish a new NDC. The new NDC can use any resources possessed by both devices and can also choose to join the NDC included in STA1. If the service priority between STA3 and STA4 is 6, they can only choose to establish a new NDC, and the NDC CRB cannot occupy the FAW with a priority of 7. If the service priority between STA3 and STA4 is 5 or lower, they can only choose to establish a new NDC, and the NDC CRB cannot occupy the FAW with a priority of 7 or 6. The data path establishment process between STA3 and STA4 includes steps S2701 to S2703, as shown in FIG. 28. Before the service discovery phase, STA3 receives the NDC schedule table information between STA1 and STA2 broadcast by STA1 via the SDF or NAF, STA4 receives the NDC schedule table information between STA1 and STA2 broadcast by STA2 via the NAF, and after receiving the NDC schedule table information between STA1 and STA2, STA3 and STA4 broadcast it via a synchronization beacon frame.Here, the value of the notification identifier included in the SDF or NAF broadcast by STA1 and the NAF broadcast by STA2 is 0, indicating that the NDC schedule table between STA1 and STA2 is broadcast on behalf of the master or non-master sync device. In this case, if STA3 is a master or non-master sync device or STA4 is a master or non-master sync device, the received NDC schedule table between STA1 and STA2 is broadcast by a synchronization beacon frame. At this time, the value of the notification identifier in the synchronization beacon frame is 1, indicating that the NDC schedule table between STA1 and STA2 is not broadcast on behalf of the master or non-master sync device.

[0378] In Case 3, STA5 and STA6 are far from STA1 and STA2. Therefore, as shown in FIG. 29, STA5 and STA6 cannot receive the SDF or NAF broadcast by STA1 or the NAF frame broadcast by STA2. They also cannot receive the synchronization beacon frame broadcast by STA4, which acts as a master or non-master sync device and contains information about the NDC schedule table between STA1 and STA2. Therefore, STA5 and STA6 cannot know the current information about the NDC schedule table between STA1 and STA2. In this case, STA5 and STA6 can establish a new NDC based on their own resource status. The process of establishing a data path between STA5 and STA6 includes steps S2701 to S2703, as shown in FIG. 29. Here, the value of the notification identifier included in the SDF or NAF broadcast by STA1 and the NAF broadcast by STA2 is 0, indicating that the NDC schedule table between STA1 and STA2 is broadcast on behalf of the master or non-master sync device. In this case, if STA4 is the master or non-master sync device, it broadcasts the received NDC schedule table between STA1 and STA2 using a synchronization beacon frame. At this time, the value of the notification identifier in the synchronization beacon frame is 1, indicating that the NDC schedule table between STA1 and STA2 is not broadcast on behalf of the master or non-master sync device.

[0379] In the service discovery process shown in Figure 29, the value of the service type of the service description attribute is set according to the service type, and if STA5 and STA6 have not received the NDC schedule table between STA1 and STA2, the SDF does not include the NDC schedule table between STA1 and STA2.

[0380] Such FAW marking and classification scheme ensures that only services with a priority equal to or higher than the FAW priority are transmitted within a FAW or CRB of the same segment, thereby reducing the number of data frames transmitted within the same FAW or CRB and meeting the requirements of different types of services in the NAN network.

[0381] Assuming that the priority of the service in this embodiment is 4, there are two cases:

[0382] As shown in FIG. 30, multiple STAs subscribe to the same service, where STA2, STA3, and STA4 subscribe to the same service for STA1.

[0383] As shown in Figure 31, there are multiple services with a priority of 4 and multiple STA bears, where STA2 subscribes to the service of STA1 and the priority of that service is 4, and STA4 and STA5 subscribe to the service of STA3 and the priority of that service is 4.

[0384] In the first case, after STA1 and other subscribers finish communication for the service, the transmitted frame does not include NDC schedule table information including FAW or CRB with priority 4. If the master or non-master sync device does not receive a frame in consecutive DWs that includes NDC schedule table information including FAW or CRB with priority 4 and the notification flag subfield in the NDC attribute has a value of 0, it considers that the FAW or CRB with priority 4 has been canceled, and the scheduler of the master or non-master sync device deletes the record of the NDC schedule table information including the FAW or CRB with priority 4.

[0385] In the following DW, the master or non-master sync device will not include in the synchronization beacon frame the NDC schedule table information of the FAW or CRB with priority 4. If the synchronization beacon frame does not include the NDC schedule table information including the FAW or CRB with priority 4, other NAN devices will not receive the NDC schedule table information including the FAW or CRB with priority 4 in the following DW, and the schedulers of these NAN devices will also delete the record of this segment.

[0386] This method allows the network to notify that a FAW or CRB with priority 4 has become a normal FAW.

[0387] In the second case, if STA1 and STA2 terminate their services with priority 4, STA1 will not broadcast NDC schedule table information including FAWs or CRBs with priority 4, but STA3, STA4, and STA5 will continue to broadcast them, so master or non-master sync devices can still receive frames of NDC schedule table information including FAWs with priority 4.

[0388] If the notification flag of the NDC attribute in the frame is 1, in the subsequent DW, the synchronization beacon frame transmitted by the master or non-master sync device still includes NDC schedule table information including an FAW with a priority of 4, and if the notification flag of the NDC attribute in the frame is 0, in the subsequent DW, the synchronization beacon frame transmitted by the master or non-master sync device does not include NDC schedule table information including an FAW with a priority of 4.

[0389] Only after STA3 and its subscribers also terminate the service with priority 4, STA3 and its subscribers stop broadcasting NDC schedule table information containing FAWs or CRBs with priority 4, and as a result, if the master or non-master sync device does not receive a frame in consecutive DWs containing NDC schedule table information containing FAWs or CRBs with priority 4 and the notification flag subfield in the NDC attribute has a value of 0, it considers the FAWs or CRBs with priority 4 to be canceled, and the scheduler of the master or non-master sync device deletes the record of the NDC schedule table information containing FAWs or CRBs with priority 4.

[0390] In the following DW, the master or non-master sync device will not include in the synchronization beacon frame any NDC schedule table information containing a FAW or CRB with priority 4. If the synchronization beacon frame does not include any NDC schedule table information containing a FAW or CRB with priority 4, other NAN devices will not receive any NDC schedule table information containing a FAW or CRB with priority 4 in the following DW, and the schedulers of these NAN devices will also delete the record of this segment.

[0391] Although the preferred embodiments of the present application have been described above with reference to the drawings, the present application is not limited to the specific details of the above embodiments. Various simple modifications may be made to the technical solutions of the present application within the scope of the technical concept of the present application, and all such simple modifications are within the scope of protection of the present application. For example, the specific technical features described in the specific embodiments may be combined in any appropriate manner as long as no contradictions arise. To avoid unnecessary repetition, the present application does not specifically describe all possible combinations. In another example, various different embodiments of the present application may be arbitrarily combined, and as long as they do not contradict the spirit of the present application, they should also be considered as the content disclosed in the present application. In yet another example, as long as there is no conflict, each example and / or technical feature in each example described in the present application may be arbitrarily combined with existing technology, and the technical solution obtained by the combination should also be within the scope of protection of the present application.

[0392] It should be further understood that in various method embodiments of the present application, the magnitude of the numbers of the above processes does not indicate the order in which they are executed. The execution order of each process should be determined based on its function and internal logic, and does not limit the implementation of the embodiments of the present application. Furthermore, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of a signal or data, where "downlink" indicates the first direction in which the signal or data is transmitted from a station to a user equipment of a cell, "uplink" indicates the second direction in which the signal or data is transmitted from a user equipment of a cell to a station, and "sidelink" indicates the third direction in which the signal or data is transmitted from user equipment 1 to user equipment 2. For example, a "downlink signal" indicates that the transmission direction of the signal is the first direction. Furthermore, in the embodiments of the present application, the term "and / or" is used merely to indicate a relation between associated objects, and indicates that three relationships may exist. Specifically, A and / or B indicates three cases: when only A exists, when both A and B exist, or when only B exists. In addition, the symbol " / " in this specification generally indicates that the relationship between the associated objects before and after it is an "or" relationship.

[0393] FIG. 32 is a schematic diagram of the structural configuration of a first NAN device according to an embodiment of the present application. As shown in FIG. 32, the first NAN device 3200 includes: The system includes a first determination unit 3201 configured to determine at least one first common resource block (CRB) corresponding to a first service based on a service type and / or a first priority of the first service and a second priority of each CRB of at least one CRB of a first NAN data cluster (NDC), wherein the first service is scheduled within the at least one first CRB and the first NAN belongs to the first NDC.

[0394] It can be appreciated that the first NAN device further comprises a communication unit configured to transmit and receive data.

[0395] In some embodiments, the first determination unit is further configured to determine the at least one first CRB based on a type or a first priority of the first service and a second priority of each CRB of the at least one CRB of the first NDC.

[0396] In some embodiments, the service type and / or first priority is: first indication information used to indicate a service type of the first service, where different service types correspond to different first priorities; The first service is marked based on at least one of: second indication information used to indicate whether the first service is a low-latency service, where the low-latency service has the highest first priority.

[0397] In some embodiments, the second priority is: a third indication information used to indicate a second priority of the corresponding CRB; The CRB is marked based on at least one of the following: fourth indication information used to indicate whether the corresponding CRB is used for low-latency services, and a CRB used for low-latency services has the highest second priority.

[0398] In some embodiments, the second priority corresponding to the first priority of a service scheduled within one CRB is equal to or greater than the second priority of said CRB.

[0399] In some embodiments, when at least two services are scheduled within one CRB, the first priorities of different services in the at least two services are the same or different.

[0400] In some embodiments, in the at least two services, if the first priority of a second service is higher than the first priority of a third service, the priority of an Access Category (AC) of the second service is higher than the priority of an AC of the third service.

[0401] In some embodiments, if one CRB is designated for use with low latency services, only low latency services are allowed to be scheduled within that CRB.

[0402] In some embodiments, if the CRB is designated for use with non-low latency services, the services scheduled within the CRB include low latency services and / or non-low latency services.

[0403] In some embodiments, when the services scheduled within the CRB include a low latency service and a non-low latency service, the priority of the AC of the low latency service is equal to or greater than the priority of the AC of the non-low latency service.

[0404] In some embodiments, the first NAN device further comprises a second determination unit, the second determination unit configured to determine a first NDC based on a service type and / or a first priority of the first service, the first NDC being an NDC to which a first NDC between the first NAN device and a second NAN device belongs, and the first service is provided from the first NAN device to the second NAN device, or the first service is provided from the second NAN device to the first NAN device.

[0405] In some embodiments, the first NAN device further comprises a first communication unit configured to transmit first information and second information to the second NAN device or receive first information and second information transmitted from the second NAN device, the first information being used to indicate the first service and the second information being used to indicate a service type and / or a first priority of the first service.

[0406] In some embodiments, the first information and the second information are included in a first frame, and the first frame is used for service discovery.

[0407] In some embodiments, the second information is located in a service descriptor attribute of the first frame.

[0408] In some embodiments, the second information is located in a service information field within the service descriptor attribute.

[0409] In some embodiments, the second information comprises: first indication information used to indicate a service type of the first service, where different service types correspond to different first priorities, and the first indication information is located in a first sub-field of the service information field; second indication information used to indicate whether the first service is a low-latency service, where a low-latency service has the highest first priority, and the second indication information is located in a second subfield of the service information field.

[0410] In some embodiments, the first NDC is an already established NDC or a newly established NDC.

[0411] In some embodiments, if the first NDC is an already established NDC: This includes cases where a second CRB is included in the CRB of the already established NDC, and the second priority of the second CRB is lower than or equal to the first target priority, and the first target priority is a second priority corresponding to the first priority of the first service.

[0412] In some embodiments, if the first NDC is a newly established NDC: If the first NAN device is not already enrolled in an established NDC, If the first NAN device is already enrolled in an established NDC, If the first NAN device is subscribed to an already established NDC, and a second CRB is included in the CRB of the already established NDC, the second priority of the second CRB is equal to or lower than a first target priority, and the first target priority is a second priority corresponding to the first priority of the first service, The first NAN device is subscribed to an already established NDC, and the second CRB is not included in the CRB of the already established NDC.

[0413] In some embodiments, the already established NDC is used for a first NDL or a second NDL, and the second NDL is an NDL between the first NAN device and a third NAN device.

[0414] In some embodiments, when the first NDC is a newly established NDC and the first NAN device has already subscribed to an already established second NDC, and the second NDC is used for the second NDC, the CRBs newly added to the second NDC of the first NDC and the CRBs of the second NDC partially overlap or do not overlap in the time domain and / or frequency domain.

[0415] In some embodiments, when a third CRB newly added to the second NDC of the second NDC and a fourth CRB of the first NDC partially overlap in the time domain and / or frequency domain, the second priority of the fourth CRB is equal to or greater than the second priority of the third CRB.

[0416] In some embodiments, when the priorities of the fourth CRB and the third CRB are the same, in the overlapping portion between the third CRB and the fourth CRB, the priority of the AC of the service scheduled in the fourth CRB is higher than the priority of the AC of the service scheduled in the third CRB.

[0417] In some embodiments, the first NAN device further comprises a second communication unit, the second communication unit configured to receive a second frame transmitted from the second NAN device or transmit a second frame to the second NAN device, the second frame being used to establish a first NDP in the first NDL, and the first NDP being used to transmit the first service.

[0418] In some embodiments, when the first NDC is a newly established NDC, the second frame includes third information and fourth information, the third information is used to indicate a first tier availability window (FAW), the fourth information is used to indicate a second priority of the first FAW, the second priority of the first FAW is a first target priority, and the first target priority is a second priority corresponding to the first priority of the first service.

[0419] In some embodiments, the fourth information is included in an NDC attribute of the second frame.

[0420] In some embodiments, the fourth information is carried in a schedule entry field in a schedule entry list of the NDC attribute.

[0421] In some embodiments, the fourth information is: fifth indication information used to indicate the priority of the first FAW, the first indication information being located in a first sub-field of the schedule entry field; a sixth indication information used to indicate whether the first FAW is used for a low-latency service, where the first FAW used for a low-latency service has the highest priority, and the second indication information includes at least one of the sixth indication information located in a second sub-field of the schedule entry field.

[0422] In some embodiments, if the first NDC is an already established NDC and is used for the first NDC, the second frame does not include a CRB of the already established NDC; or If the first NDC is an already established NDC and is used for a second NDL, the second frame includes a CRB of the already established NDC, and the second NDL is an NDL between the first NAN device and a third NAN device.

[0423] In some embodiments, the first NAN device further comprises a third communication unit, the third communication unit configured to receive a CRB of a second NDC transmitted from the third NAN device when the already established NDC is used for a second NDL, and the second NDC is the already established NDC used for the second NDL.

[0424] In some embodiments, the third communication unit is further configured to receive a third frame transmitted from the third NAN device, the third frame including a CRB of the second NDC, and the third frame belonging to a broadcast frame.

[0425] In some embodiments, the third frame further includes fifth information, which is used to indicate whether the CRB of the second NDC included in the third frame is broadcast on behalf of a NAN-controlled device or a NAN-uncontrolled device in a synchronized state.

[0426] In some embodiments, when the first NAN device is a NAN-controlled device or a non-NAN-controlled device in a synchronized state, and the fifth information indicates that the CRB of the second NDC included in the third frame is broadcast on behalf of a NAN-controlled device or a non-NAN-controlled device in a synchronized state, the method includes: The method further includes the first NAN device transmitting a fourth frame, wherein the fourth frame includes a CRB of the second NDC, and the fourth frame belongs to a broadcast frame.

[0427] In some embodiments, the fifth information is located in a first field of an NDC attribute of the third frame.

[0428] In some embodiments, the first NAN device further comprises a deletion unit, and the deletion unit is configured to delete the CRB of the second NDC locally if the first NAN device has not received the CRB of the second NDC in a first number of consecutive discovery windows (DWs).

[0429] In some embodiments, the first NAN device further comprises a fourth communication unit configured to broadcast a CRB of the first NDC.

[0430] In some embodiments, the fourth communication unit is further configured to transmit a fifth frame, wherein the fifth frame includes a CRB of the first NDC, and the fifth frame belongs to a broadcast frame.

[0431] In some embodiments, the fifth frame further includes sixth information, which is used to indicate whether the CRB schedule table of the first NDC included in the fifth frame is broadcast on behalf of a NAN-controlled device or a NAN-uncontrolled device in a synchronized state.

[0432] In some embodiments, the sixth information is located in the first field of the NDC attribute of the fifth frame.

[0433] In some embodiments, the first field is a reserved field.

[0434] In some embodiments, the broadcast frame comprises: Service discovery frames, Neighbor Sense Network Action Frame (NAF), a synchronization beacon frame.

[0435] Those skilled in the art should understand that the relevant description of the above wireless communication device in the embodiment of the present application can be understood with reference to the relevant description of the service scheduling method in the embodiment of the present application.

[0436] 33 is an exemplary structural diagram of a communication device 3300 according to an embodiment of the present application. The communication device may be a first NAN device. The communication device 3300 shown in FIG. 33 includes a processor 3310, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0437] Optionally, as shown in Fig. 33, the communication device 3300 may further include a memory 3320. Here, the processor 3310 can implement the method in the embodiments of the present application by calling and executing a computer program from the memory 3320.

[0438] Here, the memory 3320 may be a separate device independent of the processor 3310 or may be integrated into the processor 3310.

[0439] Optionally, as shown in FIG. 33 , the communication device 3300 may further include a transceiver 3330, and the processor 3310 may control the transceiver 3330 to communicate with other devices, specifically to transmit information or data to other devices or to receive information or data transmitted by other devices.

[0440] Here, the transceiver 3330 may include a transmitter and a receiver. The transceiver 3330 may further include an antenna, and the number of antennas may be one or more.

[0441] Optionally, the communication device 3300 may specifically be the first NAN device in the embodiments of the present application, and the communication device 3300 may implement the corresponding processes implemented by the first NAN device in each method of the embodiments of the present application, and related details are omitted for brevity.

[0442] Fig. 34 is an exemplary structural diagram of a chip according to an embodiment of the present application. The chip 3400 shown in Fig. 34 includes a processor 3410, which can implement the method according to the embodiment of the present application by calling and executing a computer program from a memory.

[0443] Optionally, as shown in Figure 34, the chip 3400 may further include a memory 3420. Here, the processor 3410 can implement the methods in the embodiments of the present application by calling and executing computer programs from the memory 3420.

[0444] Here, the memory 3420 may be a separate device independent of the processor 3410 or may be integrated into the processor 3410.

[0445] Illustratively, the chip 3400 may further include an input interface 3430. Here, the processor 3410 may control the input interface 3430 to communicate with other devices or chips, and specifically, to obtain information or data transmitted by other devices or chips.

[0446] For example, the chip 3400 may further include an output interface 3440. Here, the processor 3410 may control the output interface 3440 to communicate with other devices or chips, specifically to output information or data to other devices or chips.

[0447] Optionally, the chip can be applied to the first NAN device in the embodiments of the present application, and the chip can realize the corresponding process realized by the first NAN device in the embodiments of the present application in various ways. For the sake of brevity, relevant details are omitted.

[0448] It should be understood that the chips referred to in the examples of this application may also be referred to as system level chips, system chips, systems of chips, or systems on chips.

[0449] 35 is an exemplary block diagram of a communication system 3500 according to an embodiment of the present application. As shown in FIG. 35, the communication system 3500 includes a first NAN device 3510 and a second NAN device 3520.

[0450] Here, the first NAN device 3510 can be configured to implement the corresponding functions implemented by the first NAN device in the above method, and the second NAN device 35520 can be configured to implement the corresponding functions implemented by the non-access point device in the above method, which will not be repeated here for the sake of brevity.

[0451] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing functions. In the implementation process, each step of the above method embodiments can be completed by an integrated logic circuit in the form of hardware within the processor or by instructions in the form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and may implement or execute each method, step, and logical block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application may be performed directly by a hardware decoding processor or by a combination of hardware and software modules within the decoding processor. The software modules may be located in conventional storage media such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in a memory, and a processor reads the information in the memory and completes the steps of the above method in combination with the hardware.

[0452] It should be understood that the memory in the embodiments of the present application may be volatile or nonvolatile memory, or may include both volatile and nonvolatile memory. Here, nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), used as an external cache. By way of example and not limitation, it should be noted that many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM), and that memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0453] It should be understood that the above-mentioned memories are examples and not limitations, and for example, the memories in the embodiments of the present application may further be RAMs such as static random access memory (SRAM: Static RAM), dynamic random access memory (DRAM: Dynamic RAM), synchronous dynamic random access memory (SDRAM: Synchronous DRAM), double data rate synchronous dynamic random access memory (DDRSDRAM: Double Data Rate SDRAM), enhanced synchronous dynamic random access memory (ESDRAM: Enhanced SDRAM), synchronous link dynamic random access memory (SLDRAM: Synchlink DRAM), and direct memory bus random access memory (DRRAM: Direct Rambus RAM), etc. Thus, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memory.

[0454] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon.

[0455] Optionally, the computer-readable storage medium may be applied to a first NAN device in an embodiment of the present application, and the computer program causes a computer to execute corresponding processes implemented by the first NAN device in each method of the embodiment of the present application, which will not be described repeatedly here for the sake of brevity.

[0456] Embodiments of the present application further provide a computer program product including computer program instructions.

[0457] Optionally, the computer program product may be applied to a first NAN device in an embodiment of the present application, and the computer program instructions cause a computer to perform corresponding processes implemented by the first NAN device in each method of the embodiment of the present application, and for the sake of brevity, will not be repeatedly described here.

[0458] An embodiment of the present application further provides a computer program.

[0459] Optionally, the computer program may be applied to the first NAN device in the embodiments of the present application, and when the computer program is executed on a computer, it causes the computer to perform corresponding processes implemented by the first NAN device in each method of the embodiments of the present application, which will not be described repeatedly here for the sake of brevity.

[0460] Those skilled in the art can understand that each exemplary unit and algorithm step described with reference to the embodiments disclosed herein may be realized by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraints of the technical solution. Professional engineers may use different methods for each specific application to realize the described functions, but such realization should not be considered beyond the scope of this application.

[0461] Those skilled in the art can clearly understand that for convenience and brevity of description, the specific operation processes of the above systems, devices and units can refer to the corresponding processes in the above method embodiments, and will not be repeated here.

[0462] In some embodiments provided in the present application, it should be understood that the disclosed system, device, and method can be realized in other ways. For example, the device embodiments described above are merely exemplary, and the division of the units is merely a division of logical functions. In actual implementation, other division methods may be used. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. In other respects, the couplings or direct couplings or communication connections shown or discussed between each other may be indirect couplings or communication connections via some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0463] The units described as separate parts may or may not be physically separated, and the parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units. Depending on actual needs, some or all of the units may be selected to achieve the objectives of the technical solutions in this embodiment.

[0464] Furthermore, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may be a separate, independent physical unit, or two or more units may be integrated into one unit.

[0465] When the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, an essential part of the technical solution of the present application, i.e., a part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program code, such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0466] The above content is only a specific embodiment of the present application, and the protection scope of the present application is not limited thereto. Any modifications or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A service scheduling method, comprising: A service scheduling method, comprising: a first neighbor sensing network (NAN) device determining at least one first common resource block (CRB) corresponding to a first service based on a service type and / or a first priority of the first service and a second priority of each CRB of at least one CRB of a first NAN data cluster (NDC), wherein the first service is scheduled within the at least one first CRB, and the first NAN belongs to the first NDC.

2. The first NAN device determines at least one first CRB corresponding to the first service based on a service type and / or a first priority of the first service and a second priority of each CRB of the at least one CRB, The first NAN device determines the at least one first CRB based on the type or first priority of the first service and a second priority of each CRB of the at least one CRB of the first NDC. The service scheduling method according to claim 1 .

3. The service type and / or first priority may be: first indication information used to indicate a service type of the first service, where different service types correspond to different first priorities; second indication information used to indicate whether the first service is a low-latency service, wherein a low-latency service has the highest first priority; A service scheduling method according to any one of claims 1 to 2.

4. The second priority is: Third indication information used to indicate the second priority of the corresponding CRB; fourth indication information used to indicate whether the corresponding CRB is used for a low-latency service, wherein the CRB used for the low-latency service has the highest second priority; A service scheduling method according to any one of claims 1 to 3.

5. a second priority corresponding to a first priority of a service scheduled within one CRB is equal to or greater than the second priority of the CRB; The service scheduling method according to claim 2 .

6. When at least two services are scheduled in one CRB, the first priorities of different services among the at least two services are the same or different; The service scheduling method according to claim 5.

7. In the at least two services, if a first priority of a second service is higher than a first priority of a third service, a priority of an Access Category (AC) of the second service is higher than a priority of an AC of the third service; The service scheduling method according to claim 6.

8. If one CRB is designated as being used for low latency services, only low latency services are allowed to be scheduled within the CRB. A service scheduling method according to any one of claims 1 to 7.

9. If the CRB is designated as being used for a non-low latency service, the services scheduled within the CRB include low latency services and / or non-low latency services. A service scheduling method according to any one of claims 1 to 7.

10. If the services scheduled within the CRB include a low latency service and a non-low latency service, the priority of the AC of the low latency service is equal to or greater than the priority of the AC of the non-low latency service. The service scheduling method according to claim 9.

11. The service scheduling method includes: The first NAN device further includes determining the first NDC based on a service type and / or a first priority of the first service, wherein the first NDC is an NDC to which a first NDL between the first NAN device and a second NAN device belongs, and the first service is provided from the first NAN device to the second NAN device, or the first service is provided from the second NAN device to the first NAN device. A service scheduling method according to any one of claims 1 to 10.

12. The service scheduling method includes: The method further includes the first NAN device transmitting first information and second information to the second NAN device or receiving the first information and second information transmitted from the second NAN device, wherein the first information is used to indicate the first service, and the second information is used to indicate a service type and / or a first priority of the first service. The service scheduling method according to claim 11.

13. the first information and the second information are included in a first frame, and the first frame is used for service discovery. The service scheduling method according to claim 12.

14. the second information is located in a service descriptor attribute of the first frame; The service scheduling method according to claim 12.

15. the second information is located in a service information field within the service descriptor attribute; 15. The service scheduling method of claim 14.

16. The second information is first indication information used to indicate a service type of the first service, where different service types correspond to different first priorities, and the first indication information is located in a first sub-field of the service information field; second indication information used to indicate whether the first service is a low-latency service, where a low-latency service has the highest first priority, and the second indication information is located in a second sub-field of the service information field; 16. The service scheduling method of claim 15.

17. The first NDC is an already established NDC or a newly established NDC; A service scheduling method according to any one of claims 11 to 16.

18. If the first NDC is an already established NDC: The CRB of the already established NDC includes a second CRB, wherein the second priority of the second CRB is equal to or lower than the first target priority, and the first target priority is a second priority corresponding to the first priority of the first service.

18. The service scheduling method of claim 17.

19. If the first NDC is a newly established NDC, If the first NAN device is not already a member of an established NDC, If the first NAN device is already subscribed to an established NDC, If the first NAN device is subscribed to an already established NDC, and a second CRB is included in the CRB of the already established NDC, the second priority of the second CRB is equal to or lower than a first target priority, and the first target priority is a second priority corresponding to the first priority of the first service, the first NAN device is subscribed to an already established NDC, and the second CRB is not included in the CRB of the already established NDC; 18. The service scheduling method of claim 17.

20. The already established NDC is used for a first NDL or a second NDL, and the second NDL is an NDL between the first NAN device and a third NAN device. A service scheduling method according to claim 18 or 19.

21. When the first NDC is a newly established NDC, and the first NAN device has already subscribed to an already established second NDC, and the second NDC is used for the second NDL, the CRBs newly added to the second NDC of the first NDC and the CRBs of the second NDC partially overlap or do not overlap in the time domain and / or the frequency domain.

21. A service scheduling method according to claim 20.

22. When the third CRB newly added to the second NDC of the second NDC and the fourth CRB of the first NDC partially overlap in the time domain and / or frequency domain, the second priority of the fourth CRB is equal to or higher than the second priority of the third CRB, 22. The service scheduling method of claim 21.

23. When the priorities of the fourth CRB and the third CRB are the same, in the overlapping portion between the third CRB and the fourth CRB, the priority of the AC of the service scheduled in the fourth CRB is higher than the priority of the AC of the service scheduled in the third CRB; 23. A service scheduling method according to claim 22.

24. The service scheduling method includes: The first NAN device further includes receiving a second frame transmitted from the second NAN device or transmitting a second frame to the second NAN device, the second frame being used to establish a first NDP in the first NDL, and the first NDP being used to transmit the first service. A service scheduling method according to any one of claims 11 to 23.

25. If the first NDC is a newly established NDC, the second frame includes third information and fourth information, the third information is used to indicate a first tier availability window (FAW), the fourth information is used to indicate a second priority of the first FAW, the second priority of the first FAW is a first target priority, and the first target priority is a second priority corresponding to the first priority of the first service; 25. A service scheduling method according to claim 24.

26. The fourth information is included in an NDC attribute of the second frame.

26. A service scheduling method according to claim 25.

27. the fourth information is included in a schedule entry field in a schedule entry list of the NDC attribute; 27. A service scheduling method according to claim 26.

28. The fourth information is Fifth indication information used to indicate the priority of the first FAW, the first indication information being located in a first sub-field of the schedule entry field; sixth indication information used to indicate whether the first FAW is used for a low-latency service, where the first FAW used for a low-latency service has the highest priority; and the second indication information includes at least one of sixth indication information located in a second sub-field of the schedule entry field; 28. A service scheduling method according to claim 27.

29. If the first NDC is an already established NDC and is used for the first NDL, the second frame does not include a CRB of the already established NDC; or When the first NDC is an already established NDC and is used for a second NDL, the second frame includes a CRB of the already established NDC, and the second NDL is an NDL between the first NAN device and a third NAN device.

25. A service scheduling method according to claim 24.

30. If the already established NDC is used for the second NDL, the service scheduling method comprises: The method further includes the first NAN device receiving a CRB of a second NDC transmitted from the third NAN device, the second NDC being an already established NDC used for the second NDL. A service scheduling method according to any one of claims 20 to 23 and 29.

31. The first NAN device receiving a CRB of a second NDC transmitted from the third NAN device, The first NAN device receives a third frame transmitted from the third NAN device, the third frame including a CRB of the second NDC, and the third frame belongs to a broadcast frame.

31. A service scheduling method according to claim 30.

32. The third frame further includes fifth information, and the fifth information is used to indicate whether the CRB of the second NDC included in the third frame is broadcast on behalf of a NAN control device or a NAN non-control device in a synchronized state.

32. A service scheduling method according to claim 31.

33. When the first NAN device is a NAN-controlled device or a NAN-uncontrolled device in a synchronized state, and the fifth information indicates that the CRB of the second NDC included in the third frame is broadcast on behalf of the NAN-controlled device or a NAN-uncontrolled device in a synchronized state, the service scheduling method includes: The method further includes the first NAN device transmitting a fourth frame, the fourth frame including a CRB of the second NDC, and the fourth frame belonging to a broadcast frame.

33. A service scheduling method according to claim 32.

34. The fifth information is located in the first field of the NDC attribute of the third frame. A service scheduling method according to claim 32 or 33.

35. The service scheduling method includes: If the first NAN device does not receive the CRB of the second NDC in a first number of consecutive discovery windows (DWs), the first NAN device may further delete the CRB of the second NDC from its local area. A service scheduling method according to any one of claims 30 to 34.

36. The service scheduling method includes: The first NAN device further includes broadcasting a CRB of the first NDC. A service scheduling method according to any one of claims 1 to 35.

37. The first NAN device broadcasting the CRB of the first NDC includes: The first NAN device transmits a fifth frame, the fifth frame including a CRB of the first NDC, and the fifth frame belongs to a broadcast frame.

37. A service scheduling method according to any one of claims 36.

38. The fifth frame further includes sixth information, and the sixth information is used to indicate whether the CRB schedule table of the first NDC included in the fifth frame is broadcast on behalf of a NAN control device or a NAN non-control device in a synchronized state.

38. A service scheduling method according to claim 37.

39. The sixth information is located in the first field of the NDC attribute of the fifth frame.

39. A service scheduling method according to claim 38.

40. the first field is a reserved field; A service scheduling method according to claim 34 or 39.

41. The broadcast frame Service discovery frames, Neighbor Sense Network Action Frame (NAF), a synchronization beacon frame; A service scheduling method according to any one of claims 31 to 33 and 37.

42. a first NAN device, A first NAN device comprising: a first determination unit configured to determine at least one first common resource block (CRB) corresponding to a first service based on a service type and / or a first priority of the first service and a second priority of each CRB of at least one CRB of a first NAN data cluster (NDC), wherein the first service is scheduled within the at least one first CRB and the first NAN belongs to the first NDC.

43. A first NAN device comprising a processor and a memory, wherein the memory stores a computer program, and the processor calls and executes the computer program stored in the memory, causing the first NAN device to perform the service scheduling method described in any one of claims 1 to 41.

44. A chip comprising a processor for retrieving and executing a computer program from a memory, and causing a device equipped with the chip to perform the service scheduling method according to any one of claims 1 to 41.

45. A computer-readable storage medium having stored thereon a computer program for causing a computer to execute the service scheduling method according to any one of claims 1 to 41.

46. A computer program product comprising computer program instructions for causing a computer to carry out the service scheduling method of any one of claims 1 to 41.

47. A computer program product causing a computer to carry out a service scheduling method according to any one of claims 1 to 41.

Images