Scheduling service method and device, equipment and storage medium

Abstract

Provided in an embodiment of the present application are a service scheduling method and device, and a storage medium, the method comprising: a first NAN device determining at least one first CRB corresponding to a first service according to a service type and / or a first priority of the first service and a second priority of each CRB in CRBs of a first NDC, the first service being scheduled in the at least one first CRB, the first NAN belongs to the first NDC, so that the differentiated scheduling of services is realized.

Description

A scheduling service method, device, equipment, and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a scheduling service method and apparatus, device, and storage medium. Background Art

[0002] The wireless LAN industry is one of the fastest-growing sectors in the data communications sector. As a supplement and extension of traditional wired LANs, wireless LAN solutions have gained widespread adoption among home network users, small and medium-sized offices, enterprises, and telecom operators due to their flexibility, mobility, scalability, and low investment costs.

[0003] The Wireless Fidelity (Wi-Fi) Alliance has developed a standard for Neighbor Awareness Network (NAN), which aims to quickly and efficiently discover services provided by surrounding devices before establishing a connection, using low power consumption.

[0004] With the rapid development of wireless network technology, people's demand for network quality continues to grow. Business traffic with different characteristics, such as videos, games, and wearable devices, continues to increase. Some services require low latency, some services require high reliability, and some services require high throughput. This requires NAN devices in the NAN network to be able to support different types of services.

[0005] Summary of the Invention

[0006] Embodiments of the present application provide a scheduling service method, apparatus, device, and storage medium.

[0007] The scheduling service method provided in the embodiment of the present application includes:

[0008] The first proximity awareness network NAN device determines at least one first CRB corresponding to the first service based on the service type and / or first priority of the first service and the second priority of each CRB in at least one common resource block (CRB) of a first NAN data cluster (NDC), the first service is scheduled within the at least one first CRB, and the first NAN belongs to the first NDC.

[0009] The first NAN device provided in an embodiment of the present application includes:

[0010] A first determining unit is configured to determine, based on a service type and / or a first priority of a first service and a second priority of each CRB in at least one common resource block CRB of a first NAN data cluster NDC, at least one first CRB corresponding to the first service, the first service being scheduled in the at least one first CRB, and the first NAN belonging to the first NDC

[0011] The communication device provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the communication device executes the above-mentioned scheduling service method.

[0012] The chip provided in the embodiment of the present application is used to implement the above-mentioned scheduling service method.

[0013] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned scheduling service method.

[0014] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, and the execution of the computer program enables the computer to execute the above-mentioned scheduling service method.

[0015] The computer program product provided in the embodiment of the present application includes computer program instructions, and the execution of the computer program instructions enables the computer to execute the above-mentioned scheduling service method.

[0016] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned scheduling service method.

[0017] Through the above technical solution, the first NAN device determines the first CRB 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 in the CRB of the first NDC, so that the NAN device determines the CRB for scheduling the service based on the priority of the service and the priority of the CRB, so that it can select the CRB for it according to the priority of the current service, and will not blindly determine the CRB for scheduling the service in the NDC scheduling table, so that resources are scheduled differently according to the priority of the current service, thereby ensuring differentiated scheduling of services. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] FIG1 is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0020] FIG2 is an optional schematic diagram of a NAN cluster according to an embodiment of the present application;

[0021] FIG3 is an optional schematic diagram of a DW scheduling table according to an embodiment of the present application;

[0022] FIG4 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0023] FIG5 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0024] FIG6 is a schematic diagram of an optional relationship between NDL and NDP according to an embodiment of the present application;

[0025] FIG7 is an optional schematic diagram of an NDC according to an embodiment of the present application;

[0026] FIG8 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0027] FIG9 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0028] FIG10 is an optional schematic diagram of a NAN cluster according to an embodiment of the present application;

[0029] FIG11 is an optional schematic diagram of an NDC scheduling table according to an embodiment of the present application;

[0030] FIG12 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0031] FIG13A is an optional schematic diagram of an NDC scheduling table according to an embodiment of the present application;

[0032] FIG13B is an optional schematic diagram of an NDC scheduling table according to an embodiment of the present application;

[0033] FIG14 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0034] FIG15 is an optional schematic diagram of an NDC scheduling table according to an embodiment of the present application;

[0035] FIG16 is a schematic diagram of an optional format of an SDF according to an embodiment of the present application;

[0036] FIG17 is a schematic diagram of an optional format of a service descriptor attribute according to an embodiment of the present application;

[0037] FIG18 is a schematic diagram of an optional format of a NAN availability attribute according to an embodiment of the present application;

[0038] FIG19 is a schematic diagram of an optional format of an availability entry subfield according to an embodiment of the present application;

[0039] FIG20 is a schematic diagram of an optional format of an attribute control field according to an embodiment of the present application;

[0040] FIG21 is a schematic diagram of an optional format of an NDC attribute according to an embodiment of the present application;

[0041] FIG22 is a schematic diagram of an optional format of a scheduling entry subfield according to an embodiment of the present application;

[0042] FIG23 is an optional schematic diagram of an NDC scheduling table according to an embodiment of the present application;

[0043] FIG24 is an optional schematic diagram of an NDC scheduling table according to an embodiment of the present application;

[0044] FIG25 is a schematic diagram of an optional format of the attribute control field in the NDC attribute according to an embodiment of the present application;

[0045] FIG26 is an optional schematic diagram of an NDC according to an embodiment of the present application;

[0046] FIG27 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0047] FIG28 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0048] FIG29 is an optional flowchart of a scheduling service method according to an embodiment of the present application;

[0049] FIG30 is an optional schematic diagram of an NDC according to an embodiment of the present application;

[0050] FIG31 is an optional schematic diagram of an NDC according to an embodiment of the present application;

[0051] FIG32 is a schematic diagram of an optional structure of a first NAN device according to an embodiment of the present application;

[0052] FIG33 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0053] FIG34 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0054] Figure 35 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0056] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), or other communication systems. WLAN can support frequency bands including, but not limited to, low frequency bands (2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (60 GHz).

[0057] FIG1 is an example of a communication system architecture applied in an embodiment of the present application.

[0058] As shown in FIG1 , the communication system 100 may include an AP 110 and a STA 120 that accesses the network through the AP 110. In some scenarios, the AP 110 may be referred to as an AP STA, meaning that, in a sense, the AP 110 is also a type of STA. In some scenarios, the STA 120 may be referred to as a non-AP STA. In some scenarios, the STA 120 may include both AP STAs and non-AP STAs. Communication in the communication system 100 may include communication between the AP 110 and the STA 120, communication between the STA 120 and another STA 120, or communication between the STA 120 and a peer STA. A peer STA may refer to a device communicating with the STA 120, for example, a peer STA may be an AP or a non-AP STA.

[0059] AP 110 can be used as a bridge between wired and wireless networks, connecting wireless network clients together and then connecting the wireless network to Ethernet. AP 110 can be a terminal device (such as a mobile phone) or a network device (such as a router) equipped with a WiFi chip.

[0060] It should be noted that the role of STA 120 in the communication system is not absolute. In other words, the role of STA 120 in the communication system can switch between AP and STA. For example, in some scenarios, when a mobile phone is connected to a router, the mobile phone is a STA. When the mobile phone is used as a hotspot for other mobile phones, the mobile phone plays the role of AP.

[0061] In some embodiments, AP 110 and STA 120 can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

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

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

[0064] In some embodiments, STA 120 may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, 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. that supports WLAN / WiFi technology.

[0065] For example, STA 120 can also be a wearable device. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are full-featured, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0066] It should be understood that Figure 1 is merely an example of the present application and should not be construed as limiting the present application. For example, Figure 1 only exemplarily illustrates one AP and two STAs. In some embodiments, the communication system 100 may include multiple APs and other numbers of STAs, which are not limited in this embodiment of the present application.

[0067] It should be noted that Figures 1, 2A, and 2B are merely examples of the systems to which this application applies. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships can exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " herein generally indicates that the associated objects are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an associated relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; it can also mean that A and B have an associated relationship. It should also be understood that the “correspondence” mentioned in the embodiments of the present application may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices), and the present application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol. It should also be understood that in the embodiments of the present application, the “protocol” may refer to a standard protocol in the field of communications, for example, it may include LTE protocols, NR protocols, and related protocols used in future communication systems, and the present application does not limit this.

[0068] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0069] NAN cluster architecture

[0070] A NAN cluster is a collection of NAN devices that share the same NAN parameters and synchronize the same Discovery Window (DW) schedule. 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.

[0071] DW: A periodic time window established by the NAN devices that establish the NAN cluster.

[0072] In one example, the DW scheduling table established by the NAN device that establishes the NAN cluster is shown in Figure 3, including: periodic time windows DW1 and DW2, and one period is 512 time units (TU), the channel of DW1 is channel 6, the channel of DW2 is channel 149, and the starting position of DW1 and the starting position of DW2 are separated by 128 TUs.

[0073] In a NAN cluster, NAN devices are divided into the following two roles:

[0074] Control terminal (Master);

[0075] Non-master.

[0076] Non-master NAN devices are divided into the following two states: Non-Sync state and Sync state. The state of the NAN device can be changed.

[0077] The master generates and sends beacon frames, which include synchronization beacon frames and discovery beacon frames. A non-master in the Non-Sync state will directly discard the synchronization beacon frame sent by the master, while a non-master in the Sync state will send out the synchronization beacon frame sent by the master.

[0078] It is understandable that if a NAN device is a master or a non-master in the sync state, the NAN device can send NAN synchronization beacon frames in the DW to maintain the synchronization of the NAN cluster; if a NAN device is a non-master in the non-sync state, the NAN device is not allowed to send synchronization beacon frames in the DW.

[0079] Each NAN device has a NAN master level, which consists of three parts: control preference (master preference), random factor (random factor) and NAN interface address (interface address). Among them, master preference accounts for the largest proportion of the three. Therefore, the higher the master preference value of a NAN device, the higher the NAN master level of the NAN device.

[0080] A NAN cluster has a special master: the anchor master, which is the NAN device with the highest master level in the cluster. The anchor master's role is to broadcast a synchronization beacon frame at the beginning of each DW to announce the timing synchronization function (TSF) and DW schedule of the entire NAN cluster.

[0081] NAN service discovery

[0082] In the DW, all NAN devices can send service discovery frames (SDFs). The service discovery process of NAN devices includes the following two types: an unsolicited service publishing process as shown in FIG4 ; and a requested service publishing process as shown in FIG5 .

[0083] In FIG4 and FIG5 , NAN device A is the publisher of the service (Publisher), and NAN device B is the subscriber of the service (Subscriber).

[0084] The unsolicited service publishing process is shown in Figure 4. At S401, NAN device A proactively publishes its services by broadcasting an SDF (Publish). This SDF carries a NAN availability attribute to announce one or more further availability windows (FAWs). It also carries a service descriptor attribute to announce filtering conditions and other service information. After receiving this SDF (Publish), if NAN device B wishes to subscribe to the service, it executes S402 and sends a unicast SDF (Follow-up) to the publisher of the service.

[0085] The filter conditions can be used to control the distance between devices where the service can be discovered, and can be configured as follows:

[0086] 1) It can only be detected by close-range devices;

[0087] 2) No distance limit;

[0088] The requested service publishing process is shown in Figure 5. In S501, NAN device A (the subscriber of the service) actively broadcasts SDF Subscribe. After the publisher of the service receives the SDF, it executes S502 to send SDF (Publish) to the subscriber. After the subscriber of the service receives the SDF sent by the publisher of the service, it executes S503 to negotiate using SDF Follow-up.

[0089] NAN Data Path (NDP) Establishment Process

[0090] In NAN, FAW is represented as a combination of time and channels owned by the NAN device itself. For example, a NAN device has a FAW that occupies multiple channels and occupies one time period or multiple time periods of the same period. Therefore, FAW can be represented by time and channel.

[0091] In NAN, CRBs are referred to as FAWs used for communication between devices. For example, the FAWs owned by NDL and NDC are called CRBs. For a NAN device, its CRBs are a subset of the FAWs it supports. In some cases, CRBs can also be understood as FAWs, but they are used for NDL.

[0092] In order for NAN devices to communicate with each other, a service requires the NAN device pair to establish an NDP. NDP is the path used by NAN devices to send or receive data frames for a service logically, and does not actually own any resources.

[0093] NAN device pairs negotiate to establish a NAN device link (NDL). Each NDL has a certain number of FAWs, which are called NDL CRBs. An NDL CRB must be able to support one or more NDPs between the NAN device pairs. A NAN device pair can only have one NDL.

[0094] Not all NDL CRBs are used for service communications. The NDC CRBs are truly used for service communications.

[0095] When establishing NDL, NAN device pairs also establish NDC. NDC also possesses a certain number of FAWs, called NDC CRBs. Within the NDC CRB, service communications between NAN device pairs occur. Therefore, NDC CRBs are a subset of NDL CRBs. NDL CRBs and NDC CRBs can be understood as NDL Schedules and NDC Schedules, respectively.

[0096] An NDC contains at least two NAN devices belonging to the same NAN cluster. Each NAN device in the NDC must establish an NDL with at least one other NAN device in the NDC. NAN devices can join multiple NDCs simultaneously, but the NDL between a pair of NAN devices can only join one NDC.

[0097] As shown in FIG6 , an NDL includes multiple NDPs.

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

[0099] After the service discovery process, the service subscriber will send a data path request frame to the service publisher within the FAW committed by the service publisher. At this time, the service subscriber acts as the NDP requester, and the service publisher acts as the NDP responder.

[0100] If the following conditions are met, the NDP requester needs to start NDP establishment and NDL schedule table establishment at the same time. If the following conditions are not met, the NDP requester can start NDP establishment directly:

[0101] 1) If there is no established NDL schedule between the NDP Requester and the NDP Responder, or

[0102] 2) There is an established NDL schedule between the NDP initiator and the NDP responder, but it does not meet the requirements of a new NDP.

[0103] The NDP establishment process is also divided into two cases. The first case is the establishment of a data path that does not require confirmation as shown in FIG8 , and the second case is the establishment of a data path that requires confirmation as shown in FIG9 .

[0104] As shown in Figure 8, it includes:

[0105] S801. The NDP requester sends a data path request frame to the NDP responder in the FAW or DW.

[0106] After service discovery, the NDP initiator sends a data path request frame to the NDP responder in the FAW or DW. The data path request frame carries the NDL Schedule Initial Proposal, NDP attributes, and NDL attributes. The Type subfield of the NDL attribute and the NDP attribute is set to "Request", indicating a request to establish NDL and NDP. In the NDL Schedule Initial Proposal:

[0107] 1) It must contain one or more NAN availability attributes, which are used to indicate at least one FAW owned by the device.

[0108] 2) It may contain one or more NDC attributes. The NDC attribute is associated with the corresponding NAN availability attribute through the Map ID field, thereby obtaining the frequency band, channel and other information of the NAN availability attribute. If the selected NDC flag in the schedule control field of the NDC attribute is 1, it means 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 means that the initiator wants to establish a new NDC. The NDC CRB in the NDC attribute is only a suggestion from the initiator and can be negotiated.

[0109] 3) Others.

[0110] S802: The NDP responder receives a data path response frame in response to the NDP request.

[0111] After receiving the above data path request frame, the NDP responder will respond with a data path response frame to the NDP requester. The data path response frame carries the NDL attributes, NDP attributes, and a possible NDL schedule counter proposal (NDL Schedule Counter Proposal). The Type subfield in the NDL attributes and NDP attributes is set to Response, and the status subfield in the NDL attributes can be set to: Accept, Continue, or Reject.

[0112] If the status is set to Reject, the error reason needs to be set in the Reason Code subfield. In this case, the data path response frame can optionally carry the NDL Schedule Suggest Proposal, where the NDL Schedule Suggest Proposal includes:

[0113] 1) One or more NAN availability attributes, which are used to indicate the FAWs owned by the device.

[0114] 2) An NDC attribute, the FAW proposed by the NDP responder as the NDC CRB.

[0115] If status is set to Accept, the data path establishment process does not require confirmation and requires an NDL Schedule Compliant Proposal. The NDL Schedule Compliant Proposal includes:

[0116] 1) One or more NAN availability attributes, which are used to indicate the FAWs owned by the device.

[0117] 2) One or more NDC attributes, which are the same as the FAW represented by the NDC attributes in the NDL Schedule Initial Proposal;

[0118] 3) Others.

[0119] If status is set to Continue, the data path establishment process that needs to be confirmed must include an NDL Schedule Counter Proposal, which contains:

[0120] 1) One or more NAN availability attributes, where the NAN availability attribute is used to indicate at least one FAW owned by the device;

[0121] 2) One or more NDC attributes indicating at least one FAW that the NDP responder can accept as an NDC CRB;

[0122] 3) Others.

[0123] After the NDP request receives a datapath response frame with the NDL attribute whose Type subfield is Response:

[0124] If the status subfield is Accept, both parties complete the establishment of the data path. The service parties use the FAW that overlaps with the other party and themselves during the negotiation process as the NDL CRB, and the FAW indicated by the NDC attribute in the NDL Schedule Compliant Proposal becomes the NDC CRB.

[0125] If the status subfield is Reject, both parties end the data path establishment. If an NDL Schedule Suggest Proposal is received, the initiator will try to establish the data path again based on it.

[0126] If the status subfield is Continue, the NDP requester can choose to accept or reject the NDL Schedule Counter Proposal of the NDP responder. At this time, as shown in Figure 9, the NDP requester executes S803 to send a data path confirmation frame with the Type subfield of the NDL attribute as Confirm to the responder.

[0127] In a data path confirmation frame where the Type subfield of the NDL attribute is Confirm, the Status subfield is set to Accpet or Reject:

[0128] 1) If the status is Accept, it means that the NDP requester accepts the NDL Schedule Counter Proposal of the NDP responder. Then, the NDL Schedule Confirm Proposal must be carried. The FAW indicated by the NDC attribute is the same as that in the NDL Schedule Counter Proposal.

[0129] 2) If status is Reject, it means that the NDP requester rejected the NDL Schedule Counter Proposal of the NDP responder.

[0130] When the NDP responder receives a data path confirmation frame with the Type subfield of the NDL attribute as Confirm, if the status subfield in the NDL attribute is Accept, the two parties complete the establishment of the data path. The service parties use the FAW that overlaps with each other during the negotiation process as the NDL CRB, and the FAW indicated by the NDC attribute in the NDL Schedule Confirm Proposal becomes the NDC CRB. If the status subfield in the NDL attribute is Reject, the two parties end the establishment of the data path.

[0131] NAN Scheduler

[0132] The NAN device is equipped with a NAN scheduler, which has the following functions:

[0133] 1) Record the schedules of other NAN devices around, including DW, FAW, etc.

[0134] 2) Publish its own schedule;

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

[0136] A NAN device carries Committed DWs information in the Device Capability attribute in the NAN management frame. A NAN device carries FAW information in the NAN Availability attribute in the NAN management frame. The NDL attribute, NDC attribute, Ranging Setup attribute, and Public Availability attribute in the NAN management frame carry the schedule for NAN operations and non-NAN operations.

[0137] The NAN scheduler publishes these DW, FAW and other schedule information during the cluster discovery, cluster synchronization, service discovery, data communication path establishment and other stages. When other NAN devices receive the NAN management frame with the schedule information, the scheduler will record the relevant schedule information.

[0138] During the negotiation phase of establishing data communication, the NAN devices on both sides select the appropriate FAW as the NDL and NDC CRB based on their own and the peer STA's scheduling table information.

[0139] In related technologies, Wi-Fi Aware technology does not prioritize services. Data frames of all services between two STAs share the NDC CRB of NDC without distinction. Within the NDC CRB, NAN devices can send data frames of any service according to the scheduling algorithm. This approach is fair, but not suitable for certain specific categories of services, such as low-latency services.

[0140] During the DW period, a NAN device sends an SDF containing its own FAW. Other devices that wish to communicate with the corresponding device can obtain the peer STA's FAW from the received SDF and negotiate the NDL and NDC schedules for the service using the corresponding FAW. The NDL CRB is composed of the overlapping FAWs of the negotiating devices, while the NDC CRB is obtained by negotiation between the two devices or by joining an existing NDC.

[0141] In one example, the NAN cluster is shown in Figure 10. STA3 and STA4 are neighbors of STA1 and STA2, respectively. That is, STA3's communication can interfere with STA1, and STA4's communication can interfere with STA2. STA5 and STA6 are far away from STA1 and STA2. If STA1 and STA2 join NDC1, STA3 and STA4 can receive the NDC scheduling table of NDC1 sent by STA1 and STA2. STA3 and STA4 need to refer to the NDC scheduling table of NDC1 when establishing a new NDC.

[0142] Assume that two services are established successively between STA1 and STA2, one of which is a low-latency service and the other is a normal service. The NDL and NDC CRB between STA1 and STA2 are shown in Figure 11. In the NDC CRB, STA1 and STA2 can send data frames for these two services. The two services are equal and share the same NDC CRB. However, this equality is not applicable to special services such as low latency. In Figure 11, NDC CRBs (1, 2) represents the NDC added by the at least one CRB used for the NDL between STA1 and STA2, which is the NDC CRB, and NDL CRBs (1, 2) represents the at least one CRB used for the NDL between STA1 and STA2, which is the NDL CRB. In Figure 11, FAW supported by STA2 but not supported by STA1 is also included.

[0143] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0144] The scheduling service method provided in the embodiment of the present application, as shown in FIG12 , includes:

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

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

[0147] The first NAN device belonging to the first NDC can be understood as the first NDC being added to the first NDC. The NDL between the first NAN device and the second NAN device is the first NDL, which is used to transmit the first service. The first NAN device and the second NAN device are added to the first NDC, and the first NDL is added to the first NDC. It is understood that the NAN devices in the first NDC may include other NAN devices in addition to the first NAN device.

[0148] The first NAN device and the second NAN device establish a first NDP in the first NDL for the first service to transmit the first service through the first NDP. At this time, the first NAN device determines at least one first CRB for scheduling the first service based on the service type and / or first priority of the first service and the second priority of each second CRB in at least one CRB of the first NDC.

[0149] If the first NAN device is the publisher of the first service, it competes for a channel for the first service on at least one first CRB, and transmits the first service on the contended channel. If the first NAN device is the subscriber of the first service, it competes for a channel for the first service on at least one first CRB, and receives the first service based on the contended channel. It is understood that scheduling the first service can be understood as scheduling data frames for the first service, and transmitting the first service can be understood as transmitting data frames for the first service.

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

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

[0152] 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 division of the first priority and the division of the second priority 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. At this time, the different 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, a first priority may have a corresponding second priority, but the number of second priorities corresponding to a first priority is 1 or more than 2, and the number of first priorities corresponding to a second priority is 1 or more than 2.

[0153] It is understandable that the higher the first priority of a service, the higher the latency requirement it has.

[0154] It is understandable that the higher the second priority of the CRB, the higher the access category (AC) it corresponds to.

[0155] In an embodiment of the present application, when it is determined that a CRB cannot carry all data frames of the first service, the transmission of data frames of the first service can be achieved through one or more CRBs based on other CRBs in the remaining CRBs that can carry the first service.

[0156] In an embodiment of the present application, the first NAN device determines the first CRB 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 in the CRB of the first NDC, so that the NAN device determines the CRB for scheduling the service based on the priority of the service and the priority of the CRB, so that it can select the CRB for it according to the priority of the current service, and will not blindly determine the CRB for scheduling the service in the NDC scheduling table, so that resources are scheduled differently according to the priority of the current service, thereby ensuring differentiated scheduling of services.

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

[0158] In some embodiments, S1201, the first NAN device determines, based on the first priority of the first service and the second priority of each CRB in the at least one CRB, at least one first CRB corresponding to the first service, including:

[0159] The first NAN device determines the at least one first CRB based on the type or first priority of the first service and the second priority of each CRB in the at least one CRB of the first NDC.

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

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

[0162] In some embodiments, the service type and / or the first priority are marked based on at least one of the following:

[0163] first indication information, where the first indication information is used to indicate a service type of the first service, where different service types correspond to different first priorities;

[0164] Second indication information, the second indication information is used to indicate whether the first service is a low-latency service, and the low-latency service has the highest first priority.

[0165] 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 may also be referred to as service type information.

[0166] The second indication information indicates whether the first service is a low-latency service. The second information may also be referred to as a first low-latency identifier, which 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 may be determined by the first indication information.

[0167] In some embodiments, the second priority is based on at least one of the following markings:

[0168] third indication information, where the third indication information is used to indicate a second priority level of the corresponding CRB;

[0169] The fourth indication information is used to indicate whether the corresponding CRB is used for low-latency service, and the CRB used for low-latency service has the highest second priority.

[0170] The third indication information of a CRB indicates the second priority of the CRB. Here, the third indication information may also be referred to as priority information.

[0171] The fourth indication information of a CRB indicates whether the CRB is used for low-latency service. If the fourth indication information indicates low-latency service, the CRB has the highest second priority. If the fourth indication information indicates that the corresponding CRB is not used for low-latency service, that is, used for non-low-latency service, the CRB is not the highest second priority. At this time, the second priority of the CRB can be determined by the third indication information.

[0172] In some embodiments, the second priority corresponding to the first priority of the service scheduled within a CRB is higher than or equal to the second priority of the CRB.

[0173] For a CRB of the first NDC, the CRB is only allowed to schedule services whose corresponding second priority is higher than or equal to 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.

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

[0175] In one example, the first priority and the second priority correspond one-to-one, and are 0 to 7 respectively. For a CRB with a second priority of 6, it is allowed to schedule services with a first priority of 6 and a first priority of 7.

[0176] In one example, the first priority and the second priority correspond one-to-one, ranging from 0 to 7 respectively. A service with a first priority of 7 is allowed to be scheduled on a CRB with any second priority ranging from 0 to 7.

[0177] In one example, the first priority includes 0 to 4, the second priority includes 0 to 7, and the first priority corresponding to 0 corresponds to the second priority 0 and 1, the first priority corresponding to 1 corresponds to the second priority 2 and 3, the first priority corresponding to 2 corresponds to the second priority 4 and 5, the first priority corresponding to 3 corresponds to the second priority 6 and 7, and for the CRB with a second priority of 5, the first priority allowed to be scheduled is 2 and the first priority 3.

[0178] In one example, the first priority includes 0 to 4, the second priority includes 0 to 7, and the first priority corresponding to 0 corresponds to the second priority 0 and 1, the first priority corresponding to 1 corresponds to the second priority 2 and 3, the first priority corresponding to 2 corresponds to the second priority 4 and 5, and the first priority corresponding to 3 corresponds to the second priority 6 and 7. For a service with a first priority of 3, it is allowed to be scheduled on a CRB with any second priority of 0 to 7.

[0179] In some embodiments, if at least two services are scheduled within a CRB, the first priorities of different services in the at least two services are the same or different.

[0180] For a CRB, one or more services can be scheduled simultaneously. If two services are scheduled in a CRB, the first priorities of different services in the at least two services are the same or different.

[0181] In some embodiments, among the at least two services, the first priority of the second service is higher than the first priority of the third service, and the priority of the access category AC of the second service is higher than the priority of the AC of the third service.

[0182] When scheduling at least two services within a CRB, the higher the first priority of a service, the higher the AC priority of the service. It is understandable that the higher the AC priority of a service, the higher the priority of the Enhanced Distributed Channel Access (EDCA) parameters for channel access of the service.

[0183] In some embodiments, if a CRB is marked as being used for low-latency services, only low-latency services are allowed to be scheduled within the CRB.

[0184] For a CRB marked as being used for low-latency services, only low-latency services are allowed to be scheduled, that is, non-low-latency services are not allowed to be scheduled.

[0185] In some embodiments, if the CRB is marked as being used for non-low-latency services, the services scheduled within the CRB include low-latency services and / or non-low-latency services.

[0186] For a CRB marked as being used for non-low-latency services, it is allowed to schedule both low-latency services and non-low-latency services.

[0187] For low-latency services, they are allowed to be scheduled in both low-latency CRBs and non-low-latency CRBs. For non-low-latency services, they are only allowed to be scheduled in non-low-latency CRBs. In this case, the first priority of the service can be determined based on the first indication information of the service, and the second priority of the CRB can be determined based on the third indication information of the CRB to determine whether the CRB can schedule the service.

[0188] In some embodiments, if the services scheduled within the CRB include low-latency services and non-low-latency services, the priority of the AC of the low-latency service is higher than or equal to the priority of the AC of the non-low-latency service.

[0189] In the case where at least two services are scheduled in a CRB for non-low latency, and the at least two scheduled services include a low latency service and a non-low latency service, the AC priority of the low latency service is higher.

[0190] In some embodiments, the first NAN device further performs the following processing:

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

[0192] The first NAN device determines a first NDC according to the service type and / or the first priority of the first service, and determines at least one CRB of the first NDC.

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

[0194] Before the first NAN device determines the first NDC, the following processing may be performed: the first NAN device sends first information and second information to the second NAN device, or receives first information and second information sent by the second NAN device, where the first information is used to indicate the first service, and the second information is used to indicate the service type and / or first priority of the first service.

[0195] If the first NAN device is the publisher of the service, the first NAN device sends the first information and the second information to the second NAN device to inform the second device of the first service that the first device can provide and the service type and / or first priority of the first service.

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

[0197] The first information and the second information may be carried in the same frame, and one piece of first information may correspond to one piece of second information.

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

[0199] The first NAN device sends a first frame or receives a first frame sent by a second NAN device during a service discovery phase, and the first frame carries the first information and the second information.

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

[0201] If the first NAN device is the publisher of the service, the SDF is the published SDF; if the first NAN device is the subscriber of the service, the SDF is the subscribed SDF.

[0202] In an embodiment of the present application, in a service discovery process, the first frame may be used to broadcast one or more services, wherein the first service may be any service among the services broadcast by the first frame. In the case where the first frame broadcasts multiple services, the first frame includes multiple first information, and different first information indicates different services, and for each first information, the first frame includes second information corresponding to each first information.

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

[0204] In some embodiments, the second information is located in a service information field in the service descriptor attributes.

[0205] In an embodiment of the present application, the service information field in the service description attribute of the SDF is modified so that the service information field not only includes specific information of the service indicated by the service information subfield, but also includes first priority information defining the first priority of the first service.

[0206] In some embodiments, the second information includes at least one of the following:

[0207] first indication information, where the first indication information is 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 subfield of the service information field;

[0208] Second indication information, the second indication information is used to indicate whether the first service is a low-latency service, the low-latency service has the highest first priority, and the second indication information is located in the second subfield of the service information field.

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

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

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

[0212] If the first NDC is an established NDC, the first NDL between the first NAN device and the second NAN device has already added the established NDC, or if it has not added the NDC, it adds the first NDC. Here, the CRB of the established NDC is located in the first NDC scheduling table. If the first NAN device is an established NDC, the first NDC scheduling table contains a CRB that meets the service type / first priority of the first service.

[0213] If the first NDC is a newly created NDC, the first NAN device and the second NAN device establish an NDC based on service 1. Here, it can be completely newly created, that is, a new NDC scheduling table can be newly created on the basis of no NDC scheduling table, or the NDC scheduling table can be modified based on the already established NDC scheduling table to obtain a new NDC scheduling table, thereby establishing a new NDC.

[0214] Here, when the NDC scheduling table can be modified based on the established NDC scheduling table to obtain a new NDC scheduling table, the established NDC scheduling table can be used for the first NDL between the first NAN device and the second NAN device, and can also be used for the second NDL between the first NAN device and the third NAN device.

[0215] In some embodiments, the case where the first NDC is an already established NDC includes:

[0216] The CRB of the established NDC includes a second CRB, and the second priority of the second CRB is lower than or equal to the first target priority. The first target priority is a second priority corresponding to the first priority of the first service.

[0217] At least one CRB of the established NDC includes a CRB with a second priority that meets the scheduling of the first service. At this time, the first NAN device does not need to establish a new NDC, and directly uses the original NDC or joins the existing NDC.

[0218] In one example, the first service is service 2, the first NAN device and the second NAN device establish an NDC based on service 1, and the CRB based on NDC can schedule service 1, so there is no need to establish a new NDC, and services 1 and 2 are transmitted in the same NDC.

[0219] In one example, 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 for scheduling of service 1, then the first NDL joins the NDC established based on service 1, at this time, the second NAN device joins the existing NDC, that is, the first NAN device, the second NAN device and the third NAN device join the same NDC.

[0220] In some embodiments, the case where the first NDC is a newly established NDC includes at least one of the following:

[0221] Case A: The first NAN device is not added to the established NDC;

[0222] Case B: the first NAN device has been added to the established NDC;

[0223] Case C: The first NAN device has been added to an established NDC, and the CRB of the established NDC includes a second CRB, the second priority of the second CRB is higher than or equal to the first target priority, and the first target priority is the second priority corresponding to the first priority of the first service;

[0224] Case D: The first NAN device has been added to the established NDC, and the CRB of the established NDC does not include the second CRB.

[0225] For case A, the first NAN device has not joined the DNC, and thus no NDC scheduling table exists. In this case, a new NDC scheduling table is established, that is, a first NDC including the first NAN device and the second NAN device is established.

[0226] In case B, the first NAN device has already joined an established NDC. In this case, the NDC can be the NDC joined by the first NDL or the NDC joined by the second NDL, where the second NDL is the NDL between the first NAN device and the third NAN device. If the first NAN device has already joined an NDC, it directly creates a new NDC. In this case, a new NDC schedule can be established based on the existing NDC schedule.

[0227] In one example, if a first NDL between a first NAN device and a second NAN device joins an already established NDC, and the first NAN device establishes a new NDC schedule based on the NDC schedule of the already established NDC, i.e., a new NDC, then the first NDL between the first NAN device and the second NAN device joins the newly established NDC. In this case, the first NDL does not belong to the already established NDC.

[0228] In one example, the second NDL between the first NAN device and the third NAN device joins the already established NDC, and the first NAN device establishes a new NDC scheduling table based on the NDC scheduling table of the already established NDC, that is, establishes a new NDC, then the first NDL between the first NAN device and the second NAN device joins the newly established NDC.

[0229] For case C, the first NAN device has joined the established NDC. At this time, even if the NDC scheduling table of the established NDC can meet the priority requirements of the first service, the first NAN device still creates a new NDC scheduling table. At this time, a new NDC scheduling table can be established based on the existing NDC scheduling table.

[0230] In one example, a first NDL between a first NAN device and a second NAN device joins an already established NDC. The already established NDC schedule meets the priority requirements of the first service. However, the first NAN device establishes a new NDC schedule based on the NDC schedule of the already established NDC, i.e., a new NDC. In this case, the first NDL between the first NAN device and the second NAN device joins the newly established NDC. In this case, the first NDL does not belong to the already established NDC.

[0231] In one example, the second NDL between the first NAN device and the third NAN device joins the established NDC, the established NDC scheduling table meets the priority requirements of the first service, and the first NAN device establishes a new NDC scheduling table based on the NDC scheduling table of the established NDC, that is, establishes a new NDC, then the first NDL between the first NAN device and the second NAN device joins the newly established NDC.

[0232] For situation D, the first NAN device has joined the established NDC, but the NDC scheduling table of the established NDC cannot meet the priority requirements of the first service. The first NAN device creates a new NDC scheduling table. At this time, a new NDC scheduling table can be established based on the existing NDC scheduling table.

[0233] In one example, a first NDL between a first NAN device and a second NAN device joins an already established NDC. The already established NDC schedule does not meet the priority requirements of the first service. The first NAN device establishes a new NDC schedule based on the NDC schedule 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. At this point, the first NDL does not belong to the already established NDC.

[0234] In one example, the second NDL between the first NAN device and the third NAN device joins the established NDC. The established NDC scheduling table does not meet the priority requirements of the first service. The first NAN device establishes a new NDC scheduling table based on the NDC scheduling table of the established NDC, that is, establishes a new NDC. Then the first NDL between the first NAN device and the second NAN device joins the newly established NDC.

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

[0236] In some embodiments, if the first NDC is a newly created NDC and the first NAN device has been added to an already established second NDC, and the second NDC is used for the second NDL, then the newly added CRB of the first NDC relative to the second NDC and the CRB of the second NDC partially overlap or do not overlap in the time domain and / or frequency domain.

[0237] In one example, the CRBs of the second NDC include CRB1, and the priority of CRB1 is 4. For the first service, the first NAN device adds CRB2 to CRB1, resulting in the CRBs of the first NDC: CRB1 and CRB2. CRB2 partially overlaps or does not overlap with CRB1 in the time domain and / or frequency domain.

[0238] In some embodiments, if the third CRB added to the second NDC relative to the first 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 higher than or equal to the second priority of the third CRB.

[0239] In some embodiments, if the priority of the fourth CRB is the same as that of the third CRB, in the overlapping part of 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.

[0240] In some embodiments, the first NAN device further performs the following processing:

[0241] The first NAN device receives a second frame sent by the second NAN device, or sends a second frame to the second NAN device, where 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.

[0242] In the embodiment of the present application, the second frame includes a link establishment request frame and a link establishment response frame.

[0243] If the first NAN device is the NDP requester and the second NAN device is the NDP responder, the first NAN device sends a link establishment request frame to the second NAN device and receives a NAN link establishment response frame sent by the second NAN device.

[0244] If 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 by the second NAN device and sends a NAN link establishment response frame to the second NAN device.

[0245] In some embodiments, if the first NDC is a newly established NDC, the second frame carries third information and fourth information, the third information is used to indicate a first further availability window FAW, and 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.

[0246] Here, the first FAW includes the following situations:

[0247] The first NAN device's own FAW;

[0248] The FAW of the second NAN device itself;

[0249] FAW confirmed by the first NAN device;

[0250] FAW confirmed by the second NAN device;

[0251] The second priority indicated by the second information corresponding to the first FAW is the second priority set in the NDP request.

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

[0253] It is understandable that the second frame may also carry other FAWs, and the second priority of the other FAWs is greater than the second priority corresponding to the first priority of the first service.

[0254] The fourth information is carried in the NDC attribute of the second frame.

[0255] Here, the NDC attribute may include the following fields: Attribute ID: indicating that the attribute is an NDC attribute; Length: the length of the NDC attribute;

[0256] NAN data cluster ID: unique identifier of NDC; attribute control: indicates whether the NDC indicated by the NDC attribute already exists; scheduling entry list: contains multiple scheduling entry subfields, each scheduling entry is one or some phase periodic NDC FAW or CRB.

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

[0258] In some embodiments, the fourth information includes at least one of the following:

[0259] fifth indication information, where the fifth indication information is used to indicate the priority of the first FAW, and the first indication information is located in the first subfield of the scheduling entry field;

[0260] The sixth indication information is used to indicate whether the first FAW is used for low-latency service, the first FAW used for low-latency service has the highest priority, and the second indication information is located in the second subfield of the scheduling entry field.

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

[0262] The first subfield in the schedule entry field includes fifth indication information indicating the priority of the first FAW. The first subfield in the schedule entry field may also be referred to as a priority subfield.

[0263] The second subfield in the scheduling entry field includes sixth indication information, namely, a low-latency flag, indicating whether the first FAW is used for low-latency service. The second subfield in the scheduling entry field may also be called a low-latency subfield.

[0264] In some embodiments, if the first NDC is an already established NDC and is used for the first NDL, the second frame does not carry the CRB of the already established NDC; or,

[0265] If the first NDC is an established NDC and is used for a second NDL, the second frame carries the CRB of the established NDC, and the second NDL is the NDL between the first NAN device and the third NAN device.

[0266] In the case where the first NDC is an established NDC and the established NDC is used for the first NDL, the second frame between the first NAN device and the second NAN device for establishing the NDP does not need to carry the CRB of the established NDC. At this time, the second frame between the first NAN device and the second NAN device is only used to establish the first NDP, that is, to confirm the need for communication, and does not need to carry the NDC attribute.

[0267] In the case where the first NDC is an already established NDC and the already established NDC is used for the second NDL, the second frame for establishing the NDP between the first NAN device and the second NAN device carries the CRB of the already established NDC.

[0268] In the embodiment of the present application, there are currently three devices in the NAN cluster, namely STA1, STA2 and STA3. STA1 has two services: service 4 and service 6, with service priorities of 4 and 6 respectively.

[0269] As the publisher, STA1 has two options:

[0270] Option 1: Release service 4 first, and then release service 6 after several DWs.

[0271] Select 2, one-time release service 4, 6.

[0272] For option 1, STA2 and STA1 subscribe to service 4 after the service discovery phase and proceed to the data path establishment phase through two handshakes. During the data path phase, the NDL Schedule Initial Proposal sent by STA1 to STA2 contains the NAN availability attribute and the NDC attribute. The NAN availability attribute is the available FAW of the NAN, and the NDC attribute is STA2's proposal for the NDC schedule. The schedule information in the NDC attribute is as follows: Bitmap ID 2, Channel, Bit Duration 16TU, Priority 4, Low Latency Flag 0, Time Bitmap: 11100.

[0273] The NAN availability attribute in the NDL Schedule Compliant Proposal replied by STA1 is also its own FAW. This is based on a two-way handshake, so the schedule in the NDC attribute is the same as above.

[0274] This is the first time that a schedule is established between STA1 and STA2, so the NDL schedule table and the NDC schedule table shown in FIG14A are established at the same time.

[0275] Next, STA1 and STA2 publish / subscribe to service 6. They notice that the established NDC schedule does not have a FAW with priority 6. There are two possible scenarios:

[0276] Case 1: You can select the existing NDC schedule. Although the current schedule does not have a FAW with a priority of 6, data frames of the service with a priority of 6 can be transmitted on the FAW with a priority of 4.

[0277] Case 2: A new NDC schedule can be created.

[0278] For case 1, the path establishment request or path establishment response in the data path establishment phase does not carry the NDC attribute. The process at this time is just for both parties to confirm that there is service 6 that needs to communicate (that is, to establish NDP).

[0279] For case two, the path establishment request or path establishment response in the data path establishment phase carries the NDC attribute, and the NDL scheduling table information in the NDC attribute includes: bitmap identifier (Map ID) 2 and 2, channel, bit duration 16TU and 16TU, priority 6 and 4, low latency identifier 0 and 0, time bitmap: 0000000000111 and 11100000000000.

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

[0281] At this time, if device 3 needs to subscribe to service 4 or service 6 or subscribe at the same time, because the data path is established between STA1 and STA3 for the first time, it is necessary to establish NDL and NDC scheduling tables at the same time. During the establishment process, if the NDL CRB between STA3 and STA1 can meet the NDC scheduling table between STA1 and STA2, it can be selected directly. If selected directly, the NDL scheduling table information carried in the NDC attribute includes: bitmap identification (Map ID) 2 and 2, channel, bit duration 16TU and 16TU, priority 6 and 4, low latency identification 0 and 0, time bitmap: 0000000000111 and 11100000000000.

[0282] If the NDC schedule shown in Figure 13B does not meet the service requirements between STA3 and STA1, a new NDC schedule needs to be established. If a new NDC schedule needs to be established, it is necessary to refer to the NDC schedule between STA1 and STA2, and try to stagger the time domain and frequency domain.

[0283] For case 2, during the first NDP establishment phase, the NDC attribute information carried by the path establishment request or path establishment response may simultaneously include CRBs with priorities 4 and 6. The generated NDC scheduling table and NDL scheduling table are shown in Figure 14B.

[0284] At this time, if device 3 needs to subscribe to service 4 or service 6 or both, because this is the first time that a data path is established between STA1 and STA3, it is necessary to establish NDL and NDC scheduling tables at the same time. During the establishment process, if the NDL CRB between STA2 and STA1 can satisfy the NDC scheduling table between STA1 and STA3, it can be directly selected. If it does not meet the requirements, a new NDC scheduling table needs to be established. If a new NDC scheduling table needs to be established, it is necessary to refer to the NDC scheduling table between STA1 and STA2, and the time domain and frequency domain should be staggered as much as possible.

[0285] Assume that STA1 and STA2 have established an NDC scheduling table. At this time, STA1 publishes service 6 and STA2 subscribes to service 6. In addition to the above two situations, the NDC scheduling table between the two devices actually has a special case, that is, the current NDL CRB cannot meet the new NDC scheduling table. In this case, the NDL scheduling table needs to be updated. During the update process, a new NDC scheduling table will be established at the same time. This new NDC scheduling table must meet the previous service 4 and the current service 6.

[0286] The updating process of the NDL schedule is exactly the same as the establishment process of NDL and NDC.

[0287] In some embodiments, if the established NDC is used for a second NDL, the method further includes:

[0288] The first NAN device receives the CRB of the second NDC sent by the third NAN device, where the second NDC is the established NDC for the second NDL.

[0289] As shown in Figure 14, it includes:

[0290] S1401. The first NAN device receives a CRB of a second NDC sent by the third NAN device.

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

[0292] In some embodiments, the first NAN device receives the CRB of the second NDC sent by the third NAN device, including:

[0293] The first NAN device receives a third frame sent by the third NAN device, where the third frame carries the CRB of the second NDC and is a broadcast frame.

[0294] After obtaining the CRB of the second NDC, the third NAN device broadcasts a third frame and carries the CRB of the second NDC in the third frame, so that NAN devices around the third NAN device, including the second NAN device, receive the NDC schedule of the third NAN device.

[0295] In some embodiments, the third frame further carries fifth information, where the fifth information is used to indicate whether the CRB of the second NDC carried by the third frame is broadcast instead by a NAN control device or a NAN non-control device in a synchronized state.

[0296] The NAN control device can be understood as the master, and the NAN non-control device in the synchronization state can be understood as the non-master in the synchronization state.

[0297] The Master and Non-Master can synchronize the NDC schedule to other NAN devices through synchronization beacon frames.

[0298] If the fifth information is used to indicate that the CRB of the second NDC carried by the third frame is broadcast instead by the NAN control device or the NAN non-control device in the synchronized state, then when the first NAN device is the Master or Non-master, the received CRB of the second NDC will be broadcast.

[0299] If the fifth information is used to indicate that the CRB of the second NDC carried by the third frame is not broadcast by the NAN control device or the NAN non-control device in the synchronized state, then when the first NAN device is a Master or Non-master, the CRB of the second NDC to be received is not broadcast.

[0300] In the embodiment of the present application, based on different values ​​of the fifth information, it can be used to indicate that the CRB of the second NDC is broadcast instead by the NAN control device or the NAN non-control device in the synchronized state, or that the CRB of the second NDC is not broadcast instead by the NAN control device or the NAN non-control device in the synchronized state.

[0301] In one example, if the value of the fifth information is 0, it indicates that the CRB of the second NDC is broadcast instead by the NAN control device or the NAN non-control device in the synchronized state; if the value of the fifth information is 1, it indicates that the CRB of the second NDC is not broadcast instead by the NAN control device or the NAN non-control device in the synchronized state.

[0302] If the first NAN device is a NAN control device or a NAN non-control device in a synchronized state, and the fifth information indicates that the CRB of the second NDC carried by the third frame is broadcast instead by the NAN control device or the NAN non-control device in a synchronized state, the method further includes:

[0303] The first NAN device sends a fourth frame, where the fourth frame carries the CRB of the second NDC, and the fourth frame is a broadcast frame.

[0304] Among them, when the first NAN device is Master or Non-master, the CRB of the second NDC can be broadcast through the fourth frame.

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

[0306] In some embodiments, the method further comprises:

[0307] The first NAN device does not receive the CRB of the second NDC in a first number of consecutive discovery windows DW, and the first NAN device deletes the CRB of the second NDC locally.

[0308] The first NAN device has a NAN scheduler. If the NAN scheduler does not receive the CRB of the second NDC in a first number of consecutive DWs, it is considered that the second NDC applied by the CRB of the second NDC has been released, and the CRB of the second NDC is deleted locally.

[0309] The size of the first quantity can be set according to actual needs, such as: 5, 8, 10, etc.

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

[0311] After determining the CRB of the first NDC, the first NAN device can broadcast the CRB of the first NDC so that the NAN devices adjacent to the first NAN device receive the CRB of the first NDC, know which CRBs have been used for service transmission, and the priority of each CRB among these CRBs, thereby establishing an NDC based on the known CRBs and the priority of the CRBs.

[0312] In some embodiments, the first NAN device broadcasts the CRB of the first NDC, including:

[0313] The first NAN device sends a fifth frame, where the fifth frame carries the CRB of the first NDC, and the fifth frame is a broadcast frame.

[0314] In some embodiments, the fifth frame further carries sixth information, where the sixth information is used to indicate whether the CRB schedule table of the first NDC carried by the fifth frame is broadcast instead by a NAN control device or a NAN non-control device in a synchronized state.

[0315] Here, the fifth information and the sixth information are information with the same function and located in different frames, wherein the fifth information is located in the third frame and the sixth information is located in the fifth frame.

[0316] If the first NAN device does not require the CRB of the first NDC to be broadcasted instead by the NAN control device or the NAN non-controlling device in a synchronized state, the sixth information may be set to indicate that the CRB of the first NDC is not broadcasted instead by the NAN control device or the NAN non-controlling device in a synchronized state. If the first NAN device wishes that the CRB of the first NDC be broadcasted instead by the NAN control device or the NAN non-controlling device in a synchronized state, the sixth information may be set to indicate that the CRB of the first NDC is broadcasted instead by the NAN control device or the NAN non-controlling device in a synchronized state.

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

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

[0319] Here, information indicating whether the CRB of the NDC is broadcasted instead by the NAN control device or the NAN non-control device in a synchronized state is carried in the reserved field of the DC attribute.

[0320] In some embodiments, the broadcast frame includes at least one of the following:

[0321] Service Discovery Frame (SDF);

[0322] Neighborhood Awareness Network Action Frame (NAF);

[0323] Synchronization beacon frame.

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

[0325] For SDF, it is broadcast by the service publisher when DW starts;

[0326] NAF is broadcast by the service publisher or service subscriber at any time, at which time the restriction on broadcasting within the DW is lifted.

[0327] Synchronous beacon frames are broadcast by the Master or a non-master in the synchronized state.

[0328] The first NAN device may broadcast the CRB of the first NDC by broadcasting a frame once or at least twice according to a scenario.

[0329] Assume that there is an NDC scheduling table between STA1 and STA2, and the surrounding devices are shown in Figure 14C:

[0330] In DW, STA1 and STA2 broadcast the NDC schedule. If STA3 receives such a broadcast frame, STA3 will know that an NDC schedule exists in the surrounding area, and STA3's scheduler will record this NDC schedule.

[0331] At some point, the service communication between STA1 and STA2 ends (assuming there is only one service), and then they will exit NDC (they may or may not exit, but we assume exit here). That is, STA1 and STA2 will no longer execute the NDC schedule, so in the next DW, STA1 and STA2 will no longer broadcast the NDC schedule. As a result, STA3 will not receive the original NDC schedule information in multiple consecutive DWs, and STA3 will believe that the original NDC schedule has been deleted, so the STA3 scheduler will also delete the original NDC schedule record.

[0332] STA3 will receive broadcast frames from surrounding devices. If the broadcast frames contain NDC schedule information, it will be recorded. If STA3 does not receive the recorded NDC schedule information within multiple consecutive DWs, it will be considered that the recorded NDC schedule is gone, and STA3 will delete the corresponding NDC schedule from its own records.

[0333] If there are two services (assuming priorities 4 and 6) between STA1 and STA2, and one of the services (assuming service 4) ends communication at a certain moment, then the NDC scheduling table at this time should still contain CRBs with priorities 4 and 6, but at this time there is only one service (service 6) between STA1 and STA2.

[0334] Below, taking the example that the service priority and the CRB priority are divided into 8 levels respectively, the scheduling service method provided in the embodiment of the present application is further explained.

[0335] This embodiment of the present application proposes a method for marking and classifying NDC CRBs, thereby enabling Wi-Fi Aware to better support different types of services or businesses. Certain FAWs in NDC are marked. Assume, as shown in Figure 10, the NDC CRBs (NDC CRB (1, 2)) added by the NDL between STA1 and STA2 are marked with priorities 7 and 4.

[0336] Data frames for low-latency services between STA1 and STA2 can be sent in CRBs used for low latency or in CRBs used for non-low latency with a priority of 4; data frames for services with a priority of 4 are only allowed to be sent in CRBs with a priority of 4.

[0337] The publisher and subscriber of the service need to actively broadcast the FAW or CRB marking status through SDF or NAF in DW:

[0338] If STA3 and STA4 receive the priorities of each CRB in the NDC CRB broadcast by STA1 and STA2 respectively, and use them as a reference when establishing a new NDC, services with the same or higher priority can use the same CRB or select another CRB based on their own resources; services with lower priority should avoid the marked CRB.

[0339] STA5 and STA6 cannot receive the broadcasts from STA1 and STA2, so these two STAs do not need to avoid the CRBs marked by STA1 and STA2 when establishing NDC.

[0340] In an embodiment of the present application, the NAN device divides the NDC CRB into different priorities according to the categories of services supported, that is, the service types. Data frames of services of different service types are scheduled preferentially in the FAW or CRB of the specified corresponding priority, and data frames of high-priority services can also be scheduled in the FAW or CRB of low priority.

[0341] A service type field is added to the service description attribute. During the service discovery phase, the NAN device sends a service discovery frame carrying the service description attribute. While broadcasting the services owned by the device, it can also broadcast the service category, allowing the NAN device to obtain the services and service categories of other surrounding NAN devices.

[0342] Modify the NDC attribute and add a priority field and a low latency flag bit to the NDC attribute. On the one hand, when the service publisher and the service subscriber negotiate the NDL CRB and NDC CRB during the data path establishment process, they can mark part of the negotiated NDC CRB as a FAW or CRB of the same priority or a FAW or CRB for low latency services based on the service category and whether it is a low latency service. The NDP establishment phase is divided into the following two cases:

[0343] Case 1: The NAN device already has an NDC schedule. If the NDC schedule contains a FAW or CRB with the same priority as or lower priority than the service, the device can directly select the existing NDC schedule. If the NDC schedule does not contain a FAW or CRB with the same priority as or lower priority than the service, the NAN device creates a new NDC. When creating a new NDC, if the current NDL CRB cannot meet the new NDC requirements, the NDL schedule update procedure is started. On the basis of meeting the existing service requirements, the NDL CRB and NDC CRB are updated to meet the new NDC. The NDL schedule update procedure is the same as the NDP establishment procedure.

[0344] Case 2: There is no NDC scheduling table for the NAN device pair. The NAN device pair needs to negotiate the FAW or CRB of NDL and NDC based on the service category, mark the FAW or CRB, and prioritize the FAW or CRB.

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

[0346] In scenarios where low-latency services are differentiated, the FAW or CRB used for low-latency services prioritizes the transmission of low-latency service data frames. Within the FAW or CRB for non-low-latency services, data frames for non-low-latency services are scheduled and transmitted. Data frames for low-latency services can also be transmitted within non-low-latency FAWs or CRBs. In this case, data frames for low-latency services use a high-priority access method, such as a priority 7 queue and EDCA parameters, while non-low-latency services use a low-priority access method.

[0347] In the scenario of distinguishing services of different priorities, in a FAW or CRB segment, data frames of services with a priority not lower than that of the FAW or CRB are allowed to be scheduled. In this case, data frames of high-priority services use a high-priority access method, such as a high-priority queuing queue and EDCA parameters, while data frames of low-priority services use a low-priority access method, such as a low-priority queuing queue and EDCA parameters.

[0348] On the other hand, after the data path is established, the service publisher and subscriber need to broadcast the negotiated NDC schedule containing the prioritized FAW or CRB in the subsequent DW using a service discovery frame or NAN action frame (NAF). Master or non-master sync devices can also be used to broadcast the schedule instead. A notification flag subfield is added to the attribute control field of the NDC attribute. When sending a frame containing the NDC schedule information for the prioritized FAW or CRB, the service publisher and subscriber can set the notification flag in the attribute control field of the NDC attribute to 0, indicating that they wish the master or non-master sync device to broadcast the NDC schedule information instead. After receiving the frame, the scheduler of the master or non-master sync device will record the NDC schedule information and broadcast it in the subsequent DW. The notification flag in the attribute control field of the NDC attribute is set to 1, indicating that the NDC schedule information in the frame is not intended to be broadcast by the master or non-master sync device.

[0349] After receiving the NDC schedule of the FAW or CRB with priority, the scheduler will record the NDC schedule of the FAW or CRB with priority. In the following time, if other devices want to establish or join NDC, they need to refer to the information in the existing NDC schedule. There are two specific cases:

[0350] Case 1: Distinguishing between low-latency and non-low-latency services

[0351] a) For FAWs or CRBs used for low-latency services in the NDC schedule, regardless of whether the service requested by the device itself is a low-latency service, priority must be given to ensuring that the negotiated FAWs or CRBs that meet the service requirements are staggered in time or frequency domain with the FAWs or CRBs used for low-latency services in the existing NDC schedule;

[0352] b) If the service requested by the device itself is a low-latency service, priority should be given to ensuring that the negotiated FAW or CRB that meets the service requirements is staggered in the time domain or frequency domain with the existing FAW or CRB in the existing NDC schedule;

[0353] c) In the NDC scheduling table, the FAW or CRB used for low-latency services may overlap with the FAW or CRB used for non-low-latency services in the time domain or frequency domain. In the overlapping FAW or CRB, priority is given to ensuring access to low-latency services. For example, low-latency services use EDCA parameters with a priority of 7 for channel contention, while non-low-latency services use EDCA parameters with a lower priority for channel contention.

[0354] Case 2: Scenario of distinguishing service priorities. According to the different service priorities, it can be divided into the following three cases:

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

[0356] b) The priority of the service is equal to the priority of the FAW or CRB included in the NDC schedule. The device can choose to establish a new NDC, that is, to establish a new NDC schedule. Similar to the previous method, the new NDC schedule can mark a new FAW or CRB, or it can select the FAW or CRB included in the original NDC schedule, that is, choose to directly join the current NDC and use the current NDC schedule.

[0357] c) If the priority of the service is lower than the priority of the FAW or CRB included in the NDC schedule, the device must establish a new NDC. The FAW or CRB included in the NDC schedule of the new NDC needs to avoid the FAW or CRB used for high-priority services in the original NDC schedule.

[0358] In the Wi-Fi Aware standard, services are published and subscribed to using the SDF format, which also includes a description of service information. The SDF format, shown in Figure 16, consists of the following fields: a category field (one subsection), an action field (one subsection), an Organizationally Unique Identifier (OUI) field (three subsections), an OUI type field (one subsection), and a variable NAN attribute field (one subsection).

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

[0360] Attribute ID field: The value is fixed to 0x03 and is used to confirm the type of NAN attribute;

[0361] Length: the length of the service description attribute;

[0362] Service ID: The value is the hash value of the service name;

[0363] Instance ID: The value is Publish_ID or Subscribe_ID, depending on the role of the device sending the frame;

[0364] Requester instance ID: the instance ID in the frame that triggers this frame;

[0365] Service control: defines some information of the service control bitmap;

[0366] Binding bitmap: used to indicate the post discovery connection attributes bound to the service description attributes;

[0367] Match filter field length: indicates whether the match filter field exists;

[0368] Match filter fields: some filter conditions for service discovery;

[0369] Service response filter field length: indicates whether the service response filter field exists;

[0370] Service Response Filter Field: Enables a potential responder to determine whether it should respond to a NAN SDF. This field will only be considered further if the responder satisfies the service ID and matches the filter criteria.

[0371] Service information field length: indicates whether the service information field exists;

[0372] Service information field: Contains service-specific information, specified by the upper-layer service.

[0373] In an embodiment of the present application, as shown in Figure 17, the first three bits in the service information field serve as the service type (Service Type) subfield, which is used to indicate the type or priority of the service represented by the service description attribute; the fourth bit serves as a low latency flag (Low latency flag) bit, indicating whether the service is a low latency type service.

[0374] The service type or priority corresponds to the eight user priorities (UP) in EDCA. The queuing queue of the service data frame and the parameters used when accessing the channel are determined according to the service type or priority.

[0375] The service priorities corresponding to the Service Type subfield values ​​are shown in Table 1:

[0376] Table 1. Service Type subfield examples

[0377] Service Type AC1AC_BK (Background) 2AC_BK0AC_BE (Best Effort) 3AC_BE4AC_VI (Video) 5AC_VI6AC_VO (Voice) 7AC_VO

[0378] Among them, the priorities of service types 0 to 7 increase in sequence, with service type 0 having the lowest priority and service type 7 having the highest priority.

[0379] For the low latency flag, if the value of the low latency flag is 1, it indicates that the service is a low latency service. The value of the service type subfield needs to be set to 7. When the data frame of the low latency service is transmitted in a FAW or CRB used for non-low latency, the highest priority EDCA parameters are used. The setting of the low latency flag bit can be shown in Table 2.

[0380] Table 2. Low latency flag setting example

[0381]

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

[0383] Attribute ID: indicates the type of the attribute;

[0384] Length: indicates the length of the NAN availability attribute;

[0385] Sequence ID: indicates the order of broadcasting availability scheduling information. A larger value indicates that the availability scheduling information is newer.

[0386] Attribute control: indicates some control information of the FAW represented in the NAN availability attribute, such as whether the availability scheduling information of the NAN device has changed;

[0387] Availability entry list: contains multiple availability entries, each of which represents one or a series of periodic FAWs.

[0388] The availability entry list field contains one or more availability entries. The format of each availability entry subfield is shown in Figure 19, including:

[0389] Length: indicates the length of the availability entry subfield;

[0390] Entry control: indicates some control information of the availability entry, such as the type of the availability entry;

[0391] Time bitmap control: indicates some control information of the time bitmap, such as the length of each bit;

[0392] Time bitmap length: indicates the length of the time bitmap field;

[0393] Time bitmap: indicates the time information of the availability entry;

[0394] Frequency band / channel entry list: indicates the frequency bands and channels supported by this availability entry.

[0395] Each availability entry represents one or more FAWs of the same period. A NAN device indicates the FAW it owns by carrying the NAN availability attribute in an SDF, beacon frame, or NAF.

[0396] One or more NAN availability attributes can be carried in a frame. The Map ID subfield in the attribute control field is used to distinguish different NAN availability attributes. The attribute control field format is shown in Figure 20 and includes:

[0397] Bitmap ID: unique identifier of NAN availability attribute;

[0398] And fields indicating whether the committed FAW, potential FAW, public availability attributes, NDC attributes and other information have changed.

[0399] The NDC attribute can also be carried in the SDF, beacon frame, or NAF. The NDC attribute format is shown in Figure 21 and includes the following fields:

[0400] Attribute ID: indicates that the attribute is an NDC attribute;

[0401] Length: the length of the NDC attribute;

[0402] NAN data cluster ID: unique identifier of NDC;

[0403] Attribute control: Indicates whether the NDC indicated by the NDC attribute already exists;

[0404] Scheduling entry list: contains multiple scheduling entry subfields, each scheduling entry is one or some phase periodic NDC FAW or CRB.

[0405] The Schedule Entry List field contains one or more schedule entries. The format of each schedule entry subfield is shown in Figure 22 and includes:

[0406] Bitmap ID: When the bitmap ID in this subfield is the same as the bitmap ID in the attribute control of the NAN availability attribute, it indicates that the scheduling entry is associated with the NAN availability attribute;

[0407] Time bitmap control: indicates some control information of the time bitmap;

[0408] Time bitmap length: indicates the length information of the time bitmap;

[0409] Time bitmap: represents the time information of the scheduling entry;

[0410] Entry Control: Indicates the category of the scheduling entry.

[0411] Each scheduling entry is one or more FAWs of the same period in the NDC CRB. The scheduling entry only indicates the time bitmap of the FAW but does not indicate information such as the channel and frequency band. By setting the Map ID and the Map ID value in the Attribute Control field of the NAN availability attribute to one, the scheduling entry is associated with the corresponding NAN availability attribute to obtain the channel, frequency band and other information of the associated NAN availability attribute.

[0412] In the embodiment of the present application, an entry control field is added to the scheduling entry subfield, which includes a priority subfield and a low latency flag. The encoding of the priority subfield is shown in Table 3.

[0413] Priority value 1203

[0414] 4567

[0415] The priority of a FAW corresponds to the type or priority of a service. Within a FAW with a specified priority, only data frames from services with a priority no lower than that of the FAW are allowed to be sent. Data frames from services with a higher priority are queued in the corresponding priority queue and access the channel using a higher priority method, such as using high-priority EDCA parameters. Data frames from services with a lower priority are accessed using a lower priority method, such as using low-priority EDCA parameters.

[0416] Data frames of high-priority services can be sent in low-priority FAW or CRB. At this time, because the data frames of high-priority services and the data frames of low-priority services are not in the same queue and the priority of the access channel is also different, the requirement of priority transmission of data frames of high-priority services can also be met.

[0417] In one example, the NAN availability attribute, the NDC attribute flag, and the FAW or CRB priority are shown in Table 4.

[0418] Table 4. Example of NAN availability attribute and NDC attribute marking FAW or CRB priority

[0419]

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

[0421] The bitmap ID is 1: the working channels are 36 and 149. The duration of each bit in the bitmap is 64 TUs (1 TU = 1024 μs). There are two availability entries. The entry for channel 36 indicates that the FAW duration is 64 to 127 TUs after the DW. The entry for channel 149 indicates that the FAW duration is 128 to 255 TUs after the DW.

[0422] Map ID 2: The operating channel is 6, there is one availability entry, and the duration of each bit is 16 TU. This entry represents the FAW operating on channel 6, with a duration of 0 to 63 TUs after the DW.

[0423] Table 4 shows only one NDC attribute, which has three Schedule Entries:

[0424] The first schedule entry has Map ID 1 and is associated with the NAN availability attribute with Map ID 1. Therefore, the working channels of this schedule entry are 36 and 149. Each bit lasts 16 TUs and has a priority value of 0. Therefore, this schedule entry indicates a priority 0 FAW with a duration of 64 to 95 TUs after the DW. Because FAWs during this period only occupy channel 36, the priority 0 FAW indicated by this schedule entry occupies channel 36.

[0425] The second schedule entry has Map ID 2 and is associated with the NAN availability attribute with Map ID 2. Therefore, the operating channel is 6. The Priority value of this schedule entry is 7, indicating that the priority of the FAW operating on channel 6 with a post-DW duration of 0 to 31 TUs is 7.

[0426] The third schedule entry has a Map ID of 2 but a Priority value of 0. Therefore, this entry indicates a priority 0 FAW operating on channel 6 with a post-DW duration of 32 to 63 TUs.

[0427] Assume that STA1 has three services with different priorities, namely 0, 6, and 7. During the data path establishment process, the NDL CRB, NDC CRB, and negotiated FAW or CRB priorities between STA1 and STA2 are shown in Figure 23.

[0428] The priorities of all FAWs or CRBs in NDC are divided into 0, 6, and 7:

[0429] During a FAW or CRB with priority 7, STA1 and STA2 will only send data frames for services with priority 7, and will not send data frames for services with other priorities.

[0430] During a FAW or CRB with priority 6, STA1 and STA2 can send data frames for services with priorities 7 and 6, but not for services with priority 0.

[0431] During the FAW or CRB period of priority 0: STA1 and STA2 can send data frames of any priority service;

[0432] The FAW or CRB is marked and classified according to the service priority, so that the device can only send data frames of services with a priority not lower than that of the FAW or CRB in the FAW or CRB. This can ensure the quality of services with specific priority.

[0433] During a FAW or CRB with priority 0, STA1 and STA2 can send data frames for three services. These three services have different priorities, so the data frames are queued in different queues and use different access channel parameters. The EDCA parameters used for data frames of higher-priority services have higher priority. This can, to a certain extent, meet the requirement of preferential transmission of data frames of higher-priority services within the same FAW or CRB.

[0434] The low-latency flag in the entry control field is used to indicate whether the entry is used for data frame transmission of low-latency service. The function of the low-latency flag is shown in Table 5.

[0435] Table 5. NAN availability attributes and NDC attribute flags FAW

[0436]

[0437] Based on Table 5, it can be determined that if the value of the low latency flag is 1, it means that the schedule is a schedule entry specifically for data frame transmission of low latency service, and the value of the priority subfield needs to be set to 7.

[0438] Table 6 shows examples of NAN availability attributes and NDC attributes marking FAW or CRB low latency categories.

[0439] Table 6. Example of NAN availability attribute and NDC attribute marking FAW or CRB priority

[0440]

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

[0442] Map ID is 1: The working channels are 36 and 149. The duration of each bit in the bitmap is 64 TUs (1 TU = 1024 μs). There are two availability entries. The entry for channel 36 indicates that the FAW duration is 64 to 127 TUs after the DW. The entry for channel 149 indicates that the FAW duration is 128 to 255 TUs after the DW.

[0443] Map ID 2: The operating channel is 6, there is one availability entry, and the duration of each bit is 16 TU. This entry represents the FAW operating on channel 6, with a duration of 0 to 63 TUs after the DW.

[0444] Table 6 contains only one NDC attribute, which has three Schedule Entries:

[0445] The first schedule entry has Map ID 1 and is associated with the NAN availability attribute with Map ID 1. Therefore, the working channels of this schedule entry are 36 and 149. Each bit lasts 16 TUs and has a priority value of 0. Therefore, this schedule entry indicates a priority 0 FAW with a duration of 64 to 95 TUs after the DW. Because FAWs during this period only occupy channel 36, the priority 0 FAW indicated by this schedule entry occupies channel 36.

[0446] The second schedule entry has Map ID 2 and is associated with the NAN availability attribute with Map ID 2. Therefore, the operating channel is 6. The Priority value of this schedule entry is 0, indicating that the priority of the FAW operating on channel 6 with a post-DW duration of 0 to 31 TUs is 0.

[0447] The third Schedule Entry has a Map ID of 2, a Priority value of 7, and a low latency flag of 1. Therefore, this entry represents a FAW for low-latency service operating on channel 6 with a post-DW duration of 32 to 63 TUs.

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

[0449] All FAWs or CRBs in NDC are divided into FAWs or CRBs used for low-latency services and FAWs or CRBs used for services with specific priorities:

[0450] In a FAW or CRB used for low-latency services, only data frames for low-latency services will be scheduled and transmitted;

[0451] Within a FAW with a priority of 5, data frames of the service with a priority of 5 are scheduled. Data frames of the low-latency service can also be scheduled. In this case, data frames of the low-latency service have a priority of 7 and use a high-priority access method, such as the EDCA queuing and parameters with a priority of 7. Data frames of the service with a priority of 5 use the EDCA queuing and parameters with a priority of 5.

[0452] Dividing FAWs or CRBs into FAWs or CRBs for low-latency services and FAWs or CRBs for non-low-latency services can meet the service requirements of low-latency services. If data frames for low-latency services need to be transmitted on FAWs or CRBs for non-low-latency services, a high-priority access method will be used, which can also meet the requirement of prioritizing the transmission of data frames for low-latency services to a certain extent.

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

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

[0455] Notification flag: Indicates whether the NDC attribute is broadcasted by the master or non-master sync device instead;

[0456] In this embodiment, one of the 7 bits originally reserved in the Attribute Control is selected as a notification flag. The notification flag is used to indicate whether the NDC schedule information of the FAW or CRB containing the priority is notified by both the service publisher and the service subscriber, or by the master and non-master sync devices instead. It is stipulated that after the NDC is established, the STAs of both parties need to send an SDF or NAF in the next DW, and carry the NDC schedule information of the FAW or CRB containing the priority. Among them:

[0457] 1. When the frames sent by the publisher or subscriber of the service contain the NDC schedule information of the priority FAW or CRB, the value of the notification flag is set to 0. If the devices of both parties do not want the master or non-master sync device to replace the broadcast, the value of the notification flag can also be set to 1;

[0458] 2. When the frames sent by the Master or non-master sync device carry the NDC schedule information of the FAW or CRB containing the priority, the value of the notification flag is set to 1;

[0459] 3. If the publisher or subscriber of the service is a master or non-master sync device, the value of the notification flag is set to 1 when the frame sent contains the NDC schedule information of the priority FAW or CRB;

[0460] 4. When the master or non-master sync device receives a frame with a notification flag of 0 and containing the NDC schedule information of the priority FAW or CRB, it needs to include the NDC schedule information of the priority FAW or CRB in the synchronization beacon frame sent in the next DW;

[0461] 5. When a master or non-master sync device receives a frame with the notification flag set to 1 and containing the NDC schedule information of a prioritized FAW or CRB, no replacement notification is required.

[0462] Assume that STA1 and STA2 have established NDC, and the FAW or CRB marking is as shown in Figure 23. Assume that the status of some devices in the NAN cluster is as shown in Figure 26. At this time, there are the following three situations:

[0463] Case 1: STA1 and STA3 create or join an NDC;

[0464] Case 2: STA3 and STA4 create or join NDC;

[0465] Case 3: STA5 and STA6 create or join an NDC.

[0466] For case 1: STA1 and STA3 negotiate during the communication path establishment process. STA1 will carry the NAN availability attribute and NDC attribute in the frame to inform STA3 of the current NDC CRB status, including the FAW tag 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, or choose to join the NDC carried by STA1. If the service priority between STA3 and STA1 is 6, then a new NDC can be established, and the NDC CRB cannot occupy a FAW with a priority of 7. If the service priority between STA3 and STA1 is 5 or lower, only a new NDC can be established, and the NDC CRB cannot occupy FAWs with priorities 6 or 7. The data path establishment process between STA1 and STA3 is shown in Figure 27, including: S2701, the NDP initiator, or NDP requester, sends a data path request frame to the NDP responder; S2702, the NDP responder sends a data path response frame to the NDP initiator; S2703, the NDP initiator sends a data path confirmation frame to the NDP responder. During the service discovery phase prior to the data path establishment process, the priority and low service latency flag values ​​in the NDC attributes are consistent with those 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 attributes is set to 0.

[0467] For case 2: During DW, STA1 can have the SDF or NAF carry the NAN availability attribute and the NDC attribute to broadcast the NDC schedule information between STA1 and STA2. STA2 can also have the NAF carry the NAN availability attribute and the NDC attribute to broadcast the NDC schedule information between STA1 and STA2. In addition, the master and non-mserver sync devices around STA1 and STA2 can also carry the NAN availability attribute and the NDC attribute in the synchronization beacon frame on behalf of STA1 and STA2 to broadcast the NDC schedule information between STA1 and STA2.

[0468] After STA3 and STA4 receive the NDC schedule information between STA1 and STA2, they use the NDC schedule information between STA1 and STA2 as a reference when establishing or joining 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 owned by both devices, or they can choose to join the NDC carried by STA1. If the service priority between STA3 and STA4 is 6, only a new NDC can be established, and the NDC CRB cannot occupy a FAW with a priority of 7. If the service priority between STA3 and STA4 is 5 or lower, only a new NDC can be established, and the NDC CRB cannot occupy FAWs with priorities 7 or 6. The data path establishment process between STA3 and STA4 is shown in Figure 28, including S2701 to S2703. Before the service discovery phase, STA3 receives the NDC schedule information between STA1 and STA2 broadcasted via the SDF or NAF, and STA4 receives the NDC schedule information between STA1 and STA2 broadcasted via the NAF. After receiving the NDC schedule information between STA1 and STA2, STA3 and STA4 broadcast it via a synchronization beacon frame. The notification flag value carried in the SDF or NAF broadcasted by STA1 and the NAF broadcasted by STA2 is 0, indicating that the master or non-master sync device will replace the broadcast of the NDC schedule between STA1 and STA2. At this time, if STA3 is the master or non-master sync device or STA4 is the master or non-master sync device, the received NDC schedule between STA1 and STA2 is broadcasted via a synchronization beacon frame. At this time, the notification flag value in the synchronization beacon frame is 1, indicating that the master or non-master sync device will no longer replace the broadcast of the NDC schedule between STA1 and STA2.

[0469] In case 3, STA5 and STA6 are far from STA1 and STA2. As shown in Figure 29, STA5 and STA6 cannot receive the SDF or NAF frames broadcast by STA1, or the NAF frames broadcast by STA2. They also cannot receive the synchronization beacon frames broadcast by STA4, acting as the master or non-master sync device, which carry the NDC schedule information between STA1 and STA2. Therefore, STA5 and STA6 are unaware of the current NDC schedule information between STA1 and STA2. STA5 and STA6 can then establish a new NDC based on their own resource availability. The data path establishment process between STA5 and STA6 is shown in Figure 29, including S2701 to S2703. Among them, the value of the notification identifier carried in the SDF or NAF broadcast by STA1 and the NAF broadcast by STA2 is 0, indicating that the master or non-master sync device replaces the broadcast of the NDC schedule table between STA1 and STA2. At this time, when STA4 is a master or non-master sync, the NDC schedule table between STA1 and STA2 received by the synchronization beacon frame is broadcast. At this time, the value of the notification identifier in the synchronization beacon frame is 1, indicating that the master or non-master sync device is no longer used to replace the broadcast of the NDC schedule table between STA1 and STA2.

[0470] In the service discovery process shown in Figure 29, the value of the service type in the service description attribute is set according to the service type, and if STA5 and STA6 do not receive the NDC scheduling table between STA1 and STA2, the SDF does not carry the NDC scheduling table between STA1 and STA2.

[0471] By using such a FAW marking and classification method, it can be ensured that only services with a priority not lower than the FAW priority are sent in the same FAW or CRB, thereby reducing the number of data frames to be sent in the same FAW or CRB and ensuring different types of service requirements in the NAN network.

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

[0473] As shown in Figure 30, multiple STAs subscribe to the same service; among them, STA2, STA3, and STA4 subscribe to the same service from STA1.

[0474] As shown in Figure 31, there are multiple services with a priority of 4, and there are multiple STA pairs; among them, STA2 subscribes to STA1's service and the priority of this service is 4, STA4 and STA5 subscribe to STA3's service and the priority of this service is 4.

[0475] For the first case, after STA1 and other subscribers terminate service communication, the frames sent no longer contain the NDC schedule information of the FAW or CRB with a priority of 4. When the master or non-master sync device does not receive a frame containing the NDC schedule information of the FAW or CRB with a priority of 4 and the value of the notification flag subfield in the NDC attribute is 0 within consecutive DWs, it will be considered that the FAW or CRB with a priority of 4 has been revoked, and the scheduler of the master or non-master sync device will delete the record containing the NDC schedule information of the FAW or CRB with a priority of 4.

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

[0477] In this way, it is possible to inform the network that the FAW or CRB with a priority of 4 has become a normal FAW.

[0478] For the second case, when the service with priority 4 is ended between STA1 and STA2, STA1 no longer broadcasts the NDC schedule information containing the FAW or CRB with priority 4, but ST A3, STA4, and STA5 continue to broadcast, so the master or non-master sync device can still receive the frame containing the NDC schedule information of the FAW with priority 4.

[0479] If the notification flag of the NDC attribute in the frame is 1, in the following DW, the synchronization beacon frame sent by the master or non-master sync device will still carry the NDC scheduling table information of the FAW with a priority of 4; if the notification flag of the NDC attribute in the frame is 0, in the following DW, the synchronization beacon frame sent by the master or non-master sync device will not carry the NDC scheduling table information of the FAW with a priority of 4.

[0480] Only when STA3 and the subscriber also end the service with priority 4, STA3 and its subscriber will no longer broadcast the NDC schedule information containing the FAW or CRB with priority 4. In this way, if the master or non-master sync device does not receive the NDC schedule information containing the FAW or CRB with priority 4 and the value of the notification flag subfield in the NDC attribute is 0 within the continuous DW, it will be considered that the FAW or CRB with priority 4 has been revoked. The scheduler of the master or non-master sync device will delete the record of the NDC schedule information containing the FAW or CRB with priority 4.

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

[0482] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0483] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0484] FIG32 is a schematic diagram of the structure of a first NAN device provided in an embodiment of the present application. As shown in FIG32 , the first NAN device 3200 includes:

[0485] The first determination unit 3201 is configured to determine at least one first CRB corresponding to the first service based on the service type and / or first priority of the first service and the second priority of each CRB in at least one common resource block CRB of the first NAN data cluster NDC, the first service is scheduled within the at least one first CRB, and the first NAN belongs to the first NDC.

[0486] It is understandable that the first NAN device further includes a communication unit for sending and receiving data.

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

[0488] In some embodiments, the service type and / or the first priority are marked based on at least one of the following:

[0489] first indication information, where the first indication information is used to indicate a service type of the first service, where different service types correspond to different first priorities;

[0490] Second indication information, the second indication information is used to indicate whether the first service is a low-latency service, and the low-latency service has the highest first priority.

[0491] In some embodiments, the second priority is based on at least one of the following markings:

[0492] third indication information, where the third indication information is used to indicate a second priority level of the corresponding CRB;

[0493] The fourth indication information is used to indicate whether the corresponding CRB is used for low-latency service, and the CRB used for low-latency service has the highest second priority.

[0494] In some embodiments, the second priority corresponding to the first priority of the service scheduled within a CRB is higher than or equal to the second priority of the CRB.

[0495] In some embodiments, if at least two services are scheduled within a CRB, the first priorities of different services in the at least two services are the same or different.

[0496] In some embodiments, among the at least two services, the first priority of the second service is higher than the first priority of the third service, and the priority of the access category AC of the second service is higher than the priority of the AC of the third service.

[0497] In some embodiments, if a CRB is marked as being used for low-latency services, only low-latency services are allowed to be scheduled within the CRB.

[0498] In some embodiments, if the CRB is marked as being used for non-low-latency services, the services scheduled within the CRB include low-latency services and / or non-low-latency services.

[0499] In some embodiments, if the services scheduled within the CRB include low-latency services and non-low-latency services, the priority of the AC of the low-latency service is higher than or equal to the priority of the AC of the non-low-latency service.

[0500] In some embodiments, the first NAN device further includes a second determination unit configured to determine a first NDC based on the service type and / or first priority of the first service, where the first NDC is the NDC to which the first NDL between the first NAN device and the second NAN device belongs, and the first service is provided by the first NAN device to the second NAN device, or the first service is provided by the second NAN device to the first NAN device.

[0501] In some embodiments, the first NAN device further includes: a first communication unit, configured to send first information and second information to the second NAN device, or receive first information and second information sent by the second NAN device, the first information being used to indicate the first service, and the second information being used to indicate the service type and / or first priority of the first service.

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

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

[0504] In some embodiments, the second information is located in a service information field in the service descriptor attributes.

[0505] In some embodiments, the second information includes at least one of the following:

[0506] first indication information, where the first indication information is 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 subfield of the service information field;

[0507] Second indication information, the second indication information is used to indicate whether the first service is a low-latency service, the low-latency service has the highest first priority, and the second indication information is located in the second subfield of the service information field.

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

[0509] In some embodiments, the case where the first NDC is an already established NDC includes:

[0510] The CRB of the established NDC includes a second CRB, and the second priority of the second CRB is lower than or equal to the first target priority. The first target priority is a second priority corresponding to the first priority of the first service.

[0511] In some embodiments, the case where the first NDC is a newly established NDC includes at least one of the following:

[0512] The first NAN device is not added to the established NDC;

[0513] The first NAN device has been added to the established NDC;

[0514] The first NAN device has been added to an established NDC, and the CRBs of the established NDC include a second CRB, a second priority of the second CRB is lower than or equal to a first target priority, and the first target priority is a second priority corresponding to the first priority of the first service;

[0515] The first NAN device has been added to the established NDC, and the CRB of the established NDC does not include the second CRB.

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

[0517] In some embodiments, if the first NDC is a newly created NDC and the first NAN device has been added to an already established second NDC, and the second NDC is used for the second NDL, then the newly added CRB of the first NDC relative to the second NDC and the CRB of the second NDC partially overlap or do not overlap in the time domain and / or frequency domain.

[0518] In some embodiments, if the third CRB newly added to the second NDC relative to 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 higher than or equal to the second priority of the third CRB.

[0519] In some embodiments, if the priority of the fourth CRB is the same as that of the third CRB, in the overlapping part of 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.

[0520] In some embodiments, the first NAN device further includes: a second communication unit configured to receive a second frame sent by the second NAN device, or to send a second frame to the second NAN device, wherein 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.

[0521] In some embodiments, if the first NDC is a newly established NDC, the second frame carries third information and fourth information, the third information is used to indicate a first further availability window FAW, and 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.

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

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

[0524] In some embodiments, the fourth information includes at least one of the following:

[0525] fifth indication information, where the fifth indication information is used to indicate the priority of the first FAW, and the first indication information is located in the first subfield of the scheduling entry field;

[0526] The sixth indication information is used to indicate whether the first FAW is used for low-latency service, the first FAW used for low-latency service has the highest priority, and the second indication information is located in the second subfield of the scheduling entry field.

[0527] In some embodiments, if the first NDC is an already established NDC and is used for the first NDL, the second frame does not carry the CRB of the already established NDC; or,

[0528] If the first NDC is an established NDC and is used for a second NDL, the second frame carries the CRB of the established NDC, and the second NDL is the NDL between the first NAN device and the third NAN device.

[0529] In some embodiments, the first NAN device further includes: a third communication unit configured to receive the CRB of the second NDC sent by the third NAN device if the established NDC is used for the second NDL, and the second NDC is the established NDC used for the second NDL.

[0530] In some embodiments, the third communication unit is further configured to receive a third frame sent by the third NAN device, where the third frame carries the CRB of the second NDC and is a broadcast frame.

[0531] In some embodiments, the third frame further carries fifth information, where the fifth information is used to indicate whether the CRB of the second NDC carried by the third frame is broadcast instead by a NAN control device or a NAN non-control device in a synchronized state.

[0532] In some embodiments, if the first NAN device is a NAN control device or a NAN non-control device in a synchronized state, and the fifth information indicates that the CRB of the second NDC carried by the third frame is broadcast instead by the NAN control device or the NAN non-control device in a synchronized state, the method further includes:

[0533] The first NAN device sends a fourth frame, where the fourth frame carries the CRB of the second NDC, and the fourth frame is a broadcast frame.

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

[0535] In some embodiments, the first NAN device further includes: a deleting unit configured to locally delete the CRB of the second NDC if the first NAN device fails to receive the CRB of the second NDC in a first number of consecutive discovery windows DWs.

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

[0537] In some embodiments, the fourth communication unit is further configured to send a fifth frame, where the fifth frame carries the CRB of the first NDC, and the fifth frame is a broadcast frame.

[0538] In some embodiments, the fifth frame further carries sixth information, where the sixth information is used to indicate whether the CRB schedule table of the first NDC carried by the fifth frame is broadcast instead by a NAN control device or a NAN non-control device in a synchronized state.

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

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

[0541] In some embodiments, the broadcast frame includes at least one of the following:

[0542] Service discovery frame;

[0543] Neighborhood Awareness Network Action Frame (NAF);

[0544] Synchronization beacon frame.

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

[0546] Figure 33 is a schematic structural diagram of a communication device 3300 provided in an embodiment of the present application. The communication device may be a first NAN device. The communication device 3300 shown in Figure 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.

[0547] Optionally, as shown in FIG33 , the communication device 3300 may further include a memory 3320. The processor 3310 may call and execute a computer program from the memory 3320 to implement the method in the embodiment of the present application.

[0548] The memory 3320 may be a separate device independent of the processor 3310 or may be integrated into the processor 3310 .

[0549] Optionally, as shown in FIG33 , 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 send information or data to other devices, or to receive information or data sent by other devices.

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

[0551] Optionally, the communication device 3300 may specifically be the first NAN device of the embodiment 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 embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0552] Figure 34 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 3400 shown in Figure 34 includes a processor 3410, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0553] Optionally, as shown in FIG34 , the chip 3400 may further include a memory 3420. The processor 3410 may call and execute a computer program from the memory 3420 to implement the method in the embodiment of the present application.

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

[0555] Optionally, the chip 3400 may further include an input interface 3430. The processor 3410 may control the input interface 3430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0556] Optionally, the chip 3400 may further include an output interface 3440. The processor 3410 may control the output interface 3440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0557] Optionally, the chip can be applied to the first NAN device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first NAN device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0558] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

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

[0560] Among them, the first NAN device 3510 can be used to implement the corresponding functions implemented by the first NAN device in the above method, and the second NAN device 35520 can be used to implement the corresponding functions implemented by the non-access point device in the above method. For the sake of brevity, they are not repeated here.

[0561] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can 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, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, 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 the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0562] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, 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 (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0563] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, 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 memories.

[0564] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0565] Optionally, the computer-readable storage medium can be applied to the first NAN device in the embodiment of the present application, and the execution of the computer program enables the computer to execute the corresponding processes implemented by the first NAN device in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0566] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0567] Optionally, the computer program product can be applied to the first NAN device in the embodiment of the present application, and the execution of the computer program instructions enables the computer to execute the corresponding processes implemented by the first NAN device in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0568] The embodiment of the present application also provides a computer program.

[0569] Optionally, the computer program can be applied to the first NAN device in the embodiment of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the first NAN device in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0570] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0572] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0573] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0574] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0575] If the functions are implemented 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, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0576] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A scheduling service method, the method comprising: The first proximity awareness network NAN device determines at least one first CRB corresponding to the first service based on the service type and / or first priority of the first service and the second priority of each CRB in at least one common resource block CRB of the first NAN data cluster NDC, the first service is scheduled within the at least one first CRB, and the first NAN belongs to the first NDC.

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

3. The method according to any one of claims 1 to 2, wherein The service type and / or the first priority are marked based on at least one of the following: first indication information, where the first indication information is used to indicate a service type of the first service, where different service types correspond to different first priorities; Second indication information, the second indication information is used to indicate whether the first service is a low-latency service, and the low-latency service has the highest first priority.

4. The method according to any one of claims 1 to 3, wherein The second priority is based on at least one of the following markings: third indication information, where the third indication information is used to indicate a second priority level of the corresponding CRB; The fourth indication information is used to indicate whether the corresponding CRB is used for low-latency service, and the CRB used for low-latency service has the highest second priority.

5. The method according to claim 2, wherein: The second priority corresponding to the first priority of the service scheduled within a CRB is higher than or equal to the second priority of the CRB.

6. The method according to claim 5, wherein: If at least two services are scheduled in one CRB, the first priorities of different services in the at least two services are the same or different.

7. The method according to claim 6, wherein: Among the at least two services, the first priority of the second service is higher than the first priority of the third service, and the priority of the access category AC of the second service is higher than the priority of the AC of the third service.

8. The method according to any one of claims 1 to 7, wherein If a CRB is marked as being used for low-latency services, only low-latency services are allowed to be scheduled within the CRB.

9. The method according to any one of claims 1 to 7, wherein If the CRB is marked as being used for non-low-latency services, the services scheduled within the CRB include low-latency services and / or non-low-latency services.

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

11. The method according to any one of claims 1 to 10, wherein The method further comprises: The first NAN device determines the first NDC based on the service type and / or first priority of the first service, where the first NDC is the NDC to which the first NDL between the first NAN device and the second NAN device belongs, and the first service is provided by the first NAN device to the second NAN device, or the first service is provided by the second NAN device to the first NAN device.

12. The method according to claim 11, wherein The method further comprises: The first NAN device sends first information and second information to the second NAN device, or receives first information and second information sent by the second NAN device, where the first information is used to indicate the first service, and the second information is used to indicate the service type and / or first priority of the first service.

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

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

15. The method according to claim 14, wherein The second information is located in the service information field in the service descriptor attributes.

16. The method according to claim 15, wherein The second information includes at least one of the following: first indication information, where the first indication information is 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 subfield of the service information field; Second indication information, the second indication information is used to indicate whether the first service is a low-latency service, the low-latency service has the highest first priority, and the second indication information is located in the second subfield of the service information field.

17. The method according to any one of claims 11 to 16, wherein The first NDC is an already established NDC or a newly established NDC.

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

19. The method according to claim 17, wherein The case where the first NDC is a newly established NDC includes at least one of the following: The first NAN device is not added to the established NDC; The first NAN device has been added to the established NDC; The first NAN device has been added to an established NDC, and the CRBs of the established NDC include a second CRB, a second priority of the second CRB is lower than or equal to 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 has been added to the established NDC, and the CRB of the established NDC does not include the second CRB.

20. The method according to claim 18 or 19, wherein The established NDC is used for the first NDL or the second NDL, where the second NDL is the NDL between the first NAN device and the third NAN device.

21. The method according to claim 20, wherein If the first NDC is a newly created NDC, and the first NAN device has been added to the established second NDC, and the second NDC is used for the second NDL, then the newly added CRB of the first NDC relative to the second NDC and the CRB of the second NDC partially overlap or do not overlap in the time domain and / or frequency domain.

22. The method according to claim 21, wherein If the third CRB newly added to the second NDC relative to 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 higher than or equal to the second priority of the third CRB.

23. The method according to claim 22, wherein If the fourth CRB and the third CRB have the same priority, in the overlapping part of 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.

24. The method according to any one of claims 11 to 23, wherein The method further comprises: The first NAN device receives a second frame sent by the second NAN device, or sends a second frame to the second NAN device, where 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.

25. The method according to claim 24, wherein If the first NDC is a newly established NDC, the second frame carries third information and fourth information, the third information is used to indicate a first further availability window FAW, and 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.

26. The method according to claim 25, wherein The fourth information is carried in the NDC attribute of the second frame.

27. The method according to claim 26, wherein The fourth information is carried in a schedule entry field in a schedule entry list of the NDC attribute.

28. The method according to claim 27, wherein The fourth information includes at least one of the following: fifth indication information, where the fifth indication information is used to indicate the priority of the first FAW, and the first indication information is located in the first subfield of the scheduling entry field; The sixth indication information is used to indicate whether the first FAW is used for low-latency service, the first FAW used for low-latency service has the highest priority, and the second indication information is located in the second subfield of the scheduling entry field.

29. The method according to claim 24, wherein If the first NDC is an established NDC and is used for the first NDL, the second frame does not carry the CRB of the established NDC; or, If the first NDC is an established NDC and is used for a second NDL, the second frame carries the CRB of the established NDC, and the second NDL is the NDL between the first NAN device and the third NAN device.

30. The method according to any one of claims 20 to 23 and 29, wherein If the established NDC is used for a second NDL, the method further includes: The first NAN device receives the CRB of the second NDC sent by the third NAN device, where the second NDC is the established NDC for the second NDL.

31. The method according to claim 30, wherein The first NAN device receiving the CRB of the second NDC sent by the third NAN device includes: The first NAN device receives a third frame sent by the third NAN device, where the third frame carries the CRB of the second NDC and is a broadcast frame.

32. The method according to claim 31, wherein The third frame further carries fifth information, where the fifth information is used to indicate whether the CRB of the second NDC carried by the third frame is broadcast instead by a NAN control device or a NAN non-control device in a synchronized state.

33. The method according to claim 32, wherein If the first NAN device is a NAN control device or a NAN non-control device in a synchronized state, and the fifth information indicates that the CRB of the second NDC carried by the third frame is broadcast instead by the NAN control device or the NAN non-control device in a synchronized state, the method further includes: The first NAN device sends a fourth frame, where the fourth frame carries the CRB of the second NDC, and the fourth frame is a broadcast frame.

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

35. The method according to any one of claims 30 to 34, wherein The method further comprises: The first NAN device does not receive the CRB of the second NDC in a first number of consecutive discovery windows DWs, and the first NAN device deletes the CRB of the second NDC locally.

36. The method according to any one of claims 1 to 35, wherein The method further comprises: The first NAN device broadcasts the CRB of the first NDC.

37. The method according to any one of claims 36, wherein The first NAN device broadcasts the CRB of the first NDC, including: The first NAN device sends a fifth frame, where the fifth frame carries the CRB of the first NDC, and the fifth frame is a broadcast frame.

38. The method of claim 37, wherein: The fifth frame further carries sixth information, where the sixth information is used to indicate whether the CRB schedule table of the first NDC carried by the fifth frame is broadcast instead by a NAN control device or a NAN non-control device in a synchronized state.

39. The method according to claim 38, wherein The sixth information is located in the first field of the NDC attribute in the fifth frame.

40. The method according to claim 34 or 39, wherein The first field is a reserved field.

41. The method according to any one of claims 31 to 33 and 37, wherein: The broadcast frame includes at least one of the following: Service discovery frame; Neighborhood Awareness Network Action Frame (NAF); Synchronization beacon frame.

42. A first NAN device, comprising: The first determination unit is configured to determine at least one first CRB corresponding to the first service based on the service type and / or first priority of the first service and the second priority of each CRB in at least one common resource block CRB of the first NAN data cluster NDC, 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, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the first NAN device performs the method according to any one of claims 1 to 41.

44. A chip comprising: A processor, configured to call and execute a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 41.

45. A computer-readable storage medium for storing a computer program, wherein the execution of the computer program causes a computer to perform the method according to any one of claims 1 to 41.

46. ​​A computer program product comprising computer program instructions, the execution of which causes a computer to perform the method according to any one of claims 1 to 41.

47. A computer program, the execution of which causes a computer to perform the method according to any one of claims 1 to 41.

Images