WO2021134347A1

WO2021134347A1 - Resource allocation method, apparatus, and system

Info

Publication number: WO2021134347A1
Application number: PCT/CN2019/130179
Authority: WO
Inventors: 朱方园; 李岩; 刘建宁
Original assignee: 华为技术有限公司
Priority date: 2019-12-30
Filing date: 2019-12-30
Publication date: 2021-07-08
Also published as: CN114175826A

Abstract

Embodiments of the present application provide a resource allocation method, apparatus, and system. The method comprises: receiving synchronization scheduling indication information associated with a terminal device, wherein the synchronization scheduling indication information is used to indicate an air interface scheduling resource needed to be synchronized between the terminal device and other terminal devices in a user group that the terminal device belongs to; and allocating the air interface scheduling resource to the terminal device according to the synchronization scheduling indication information. In the present solution, the synchronization scheduling indication information is used to allocate, to terminal devices in a user group, an air interface scheduling resource in the same time unit or adjacent time units, such that a network side can receive data sent by the respective terminal devices in the user group with minimum delay, thus improving the quality of data processing.

Description

Resource allocation method, device and system

Technical field

This application relates to the field of communication technology, and in particular to resource allocation methods, devices and systems.

Background technique

In some application scenarios, multiple terminal devices need to perform a certain service in coordination, and these terminal devices need to send data to the network side, and the network side performs comprehensive processing based on the data reported by each terminal device. Taking the concert scene as an example, the vocalist, bassist, guitarist, drummer, etc. are used as terminal devices. These terminal devices belong to the same mixing group (also called user group), and the sound data generated by each needs to be separately generated through the mobile network. Send to the network side, and then the network side performs mixing processing according to the deterministic time according to each collected sound data, so as to output the final processing result and return it to each terminal device.

In the same mixing group, because the network side processes the received data according to the deterministic time, the data sent by each terminal device needs to arrive within a certain time range, otherwise once one or some terminal devices send If the data does not arrive within a certain time range, the audio mixing process cannot be performed, and the network side will discard the data received from other terminal devices, which will eventually cause the audio mixing to fail.

Therefore, how to optimize the delay in deterministic media transmission to improve the quality of data processing is a problem to be solved.

Summary of the invention

The embodiments of the present application provide a resource allocation method, device, and system to optimize the delay in deterministic media transmission to improve the quality of data processing.

In a first aspect, an embodiment of the present application provides a resource allocation method, including: receiving synchronization scheduling indication information associated with a terminal device, where the synchronization scheduling indication information is used to indicate that the terminal device needs to communicate with the user where the terminal device is located. Air interface scheduling resources synchronized by other terminal devices in the group; according to the synchronization scheduling indication information, the air interface scheduling resources are allocated to the terminal device.

In the above solution, the terminal devices in the user group are allocated air interface scheduling resources of the same or adjacent time units according to the synchronization scheduling instruction information, so that the network side can receive different terminal devices in the user group within the shortest possible time delay. The sent data helps to improve the quality of data processing.

In a possible implementation method, when the synchronization scheduling indication information associated with the terminal equipment in the user group has not been received; the allocation of the terminal equipment to the terminal equipment according to the synchronization scheduling indication information Air interface scheduling resources include: determining the identity of the user group according to the synchronization scheduling indication information; according to the identity of the user group, allocating the air interface scheduling to the terminal device from the air interface resources corresponding to the user group Resources.

In a possible implementation method, the identifier of the user group is received; and the air interface resource is allocated to the user group according to the identifier of the user group.

In a possible implementation method, the first reserved resource among the air interface resources is determined, where the first reserved resource and the air interface scheduling resource allocated to the terminal device are in the same or adjacent time unit, so The first reserved resource is used to allocate to other terminal devices in the user group.

In a possible implementation method, when the synchronization scheduling indication information associated with the terminal equipment in the user group has been received; the air interface is allocated to the terminal equipment according to the synchronization scheduling indication information The scheduling resource includes: allocating the air interface scheduling resource to the terminal device from the second reserved resource, the second reserved resource and the air interface that has been allocated to one or more terminal devices in the user group The scheduling resources are in the same or adjacent time units.

In a possible implementation method, the synchronization scheduling indication information is determined according to the identity of the user group.

In a second aspect, an embodiment of the present application provides a resource allocation method, including: receiving an identifier of a user group, the user group including at least two terminal devices; determining synchronization scheduling indication information according to the identifier of the user group, the The synchronization scheduling indication information is used to indicate that the terminal equipment in the user group needs to synchronize air interface scheduling resources with other terminal equipment in the user group; and the synchronization scheduling indication information is sent to the access network equipment.

In the above solution, the session management network element can determine the synchronization scheduling indication information based on the user group identifier, and send the synchronization scheduling indication information to the access network device, and the access network device can be the terminal equipment in the user group according to the synchronization scheduling indication information Allocate air interface scheduling resources of the same or adjacent time units, so that the network side can receive data sent by different terminal devices in the user group within the shortest possible time delay, which helps to improve the quality of data processing.

In a possible implementation method, the receiving the identifier of the user group includes: receiving the identifier of the user group from a first terminal device, the first terminal device belongs to the user group; or; receiving from an application The identifier of the user group of the functional network element.

In a third aspect, an embodiment of the present application provides a resource allocation method, including: a terminal device sends an identifier of a user group, and the terminal device in the user group needs air interface scheduling resources that are synchronized with other terminal devices in the user group; The terminal device receives air interface scheduling resources from the access network.

In a fourth aspect, an embodiment of the present application provides a communication device. The device may be an access network device or a chip for the access network device. The device has the function of realizing the above-mentioned first aspect or each embodiment of the first aspect. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a fifth aspect, an embodiment of the present application provides a communication device, which may be a session management network element, or a chip used for a session management network element. The device has the function of realizing the above-mentioned second aspect or each embodiment of the second aspect. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a sixth aspect, an embodiment of the present application provides a communication device. The device may be a terminal device or a chip for the terminal device. The device has the function of realizing the foregoing third aspect or the embodiments of the third aspect. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a seventh aspect, an embodiment of the present application provides a communication device including a processor and a memory; the memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory to enable The device executes the methods of the above-mentioned first aspect to third aspect or each embodiment of the first aspect to third aspect.

In an eighth aspect, an embodiment of the present application provides a communication device, including a unit or means for executing each step of the above-mentioned first aspect to the third aspect, or each embodiment of the first aspect to the third aspect.

In a ninth aspect, an embodiment of the present application provides a communication device, including a processor and an interface circuit, the processor is configured to communicate with other devices through the interface circuit, and execute the first aspect to the third aspect or the first aspect to The method of each embodiment of the third aspect. The processor includes one or more.

In a tenth aspect, an embodiment of the present application provides a communication device, including a processor, configured to be connected to a memory, and used to call a program stored in the memory to execute the first aspect to the third aspect, or the first aspect To the method of each embodiment of the third aspect. The memory can be located inside the device or outside the device. And the processor includes one or more.

In an eleventh aspect, an embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium stores instructions that, when run on a computer, cause a processor to execute the first to third aspects described above. Aspect, or the method described in each embodiment of the first aspect to the third aspect.

In the twelfth aspect, the embodiments of the present application also provide a computer program product including instructions, which when run on a computer, cause the computer to execute each of the first aspect to the third aspect, or the first aspect to the third aspect. The method described in the embodiment.

In a thirteenth aspect, an embodiment of the present application further provides a chip system, including a processor, configured to execute the methods described in the first aspect to the third aspect, or the embodiments of the first aspect to the third aspect.

In a fourteenth aspect, an embodiment of the present application also provides a communication system, including: a session management network element and an access network device; the session management network element is configured to receive an identifier of a user group, and the user group includes at least two Terminal equipment; determine synchronization scheduling indication information according to the user group identifier, the synchronization scheduling indication information is used to indicate that the terminal equipment in the user group needs to synchronize air interface scheduling with other terminal equipment in the user group Resource; sending the synchronization scheduling indication information associated with the first terminal device in the user group to the access network equipment; the access network equipment is configured to, according to the synchronization scheduling indication information, be the The first terminal device allocates the air interface scheduling resource.

In a possible implementation method, when the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically configured to The synchronization scheduling indication information determines the identity of the user group; according to the identity of the user group, the air interface scheduling resource is allocated to the first terminal device from the air interface resources corresponding to the user group.

In a possible implementation method, the access network device is further configured to receive the identifier of the user group; according to the identifier of the user group, the air interface resource is allocated to the user group.

In a possible implementation method, the access network device is further configured to determine a first reserved resource in the air interface resources, and the first reserved resource is the same as the air interface allocated to the first terminal device. The scheduling resources are in the same or adjacent time unit, and the first reserved resource is used for allocating to other terminal devices in the user group.

In a possible implementation method, when the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically configured to receive a second In the reserved resources, the air interface scheduling resources are allocated to the first terminal device, and the second reserved resources are the same or the same as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group. The adjacent time unit.

In a possible implementation method, the session management network element is used to receive the user group identifier, specifically including: used to receive the user group identifier from the first terminal device; or; used to receive The identifier of the user group from the application function network element.

In a fifteenth aspect, an embodiment of the present application also provides a resource allocation method, including: a session management network element receives an identifier of a user group, the user group includes at least two terminal devices; the session management network element is based on the user The group identifier determines synchronization scheduling indication information, the synchronization scheduling indication information is used to indicate that the terminal equipment in the user group needs to synchronize air interface scheduling resources with other terminal equipment in the user group; the session management network element Send the synchronization scheduling indication information associated with the first terminal equipment in the user group to the access network equipment; the access network equipment allocates the first terminal equipment to the first terminal equipment according to the synchronization scheduling indication information Air interface scheduling resources.

Description of the drawings

Figure 1A is a schematic diagram of a 5G network architecture based on a service-oriented architecture;

Figure 1B is a schematic diagram of a 5G network architecture based on a point-to-point interface;

Figure 2 is a schematic diagram of the components involved in the professional audio production communication system;

FIG. 3 is a schematic diagram of time delay caused by multiple terminal devices when sending uplink data;

FIG. 4 is a schematic flowchart of a resource allocation method provided by an embodiment of this application;

Figure 5A is a schematic diagram of allocating air interface scheduling resources;

FIG. 5B is another schematic diagram of allocating air interface scheduling resources;

6 is a schematic diagram of the access network device allocating synchronized air interface scheduling resources for the terminal devices in the user group;

FIG. 7 is a schematic flowchart of another resource allocation method provided by an embodiment of the application;

FIG. 8 is a schematic flowchart of another resource allocation method provided by an embodiment of the application;

FIG. 9 is a schematic diagram of a communication device provided by an embodiment of this application;

FIG. 10 is a schematic diagram of another communication device provided by an embodiment of this application;

FIG. 11 is a schematic diagram of an access network device provided by an embodiment of this application;

FIG. 12 is a schematic diagram of a session management network element provided by an embodiment of this application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings. The specific operation method in the method embodiment can also be applied to the device embodiment or the system embodiment. Wherein, in the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more than two.

As shown in Figure 1A, it is a schematic diagram of a fifth generation (5G) network architecture based on a service-oriented architecture. The 5G network architecture shown in FIG. 1A may include three parts, namely a terminal equipment part, a data network (DN), and an operator network part. The functions of some of the network elements are briefly introduced below.

Among them, the operator network may include one or more of the following network elements: Authentication Server Function (AUSF) network elements, network exposure function (NEF) network elements, policy control function (policy control) function, PCF) network element, unified data management (UDM) network element, unified database (Unified Data Repository, UDR), network storage function (Network Repository Function, NRF) network element, application function (AF) ) Network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, radio access network (RAN), and user plane Function (user plane function, UPF) network elements, etc. In the above-mentioned operator's network, the part other than the radio access network part may be referred to as the core network part.

Terminal device (terminal device) is a device with wireless transceiver function. It can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air ( For example, airplanes, balloons, satellites, etc.). The terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial control (industrial control) Wireless terminals in ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , Wireless terminals in smart cities, wireless terminals in smart homes, user equipment (UE), media equipment (such as electronic audio equipment installed with communication devices, such as electric guitars, Electronic drums, microphones, etc.) etc.

The above-mentioned terminal device may establish a connection with the operator's network through an interface (such as N1, etc.) provided by the operator's network, and use services such as data and/or voice provided by the operator's network. The terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN and/or the service provided by a third party. Among them, the above-mentioned third party may be a service party other than the operator's network and terminal equipment, and may provide other services such as data and/or voice for the terminal equipment. Among them, the specific form of expression of the above-mentioned third party can be determined according to actual application scenarios, and is not limited here.

RAN is a sub-network of an operator's network, and an implementation system between service nodes and terminal equipment in the operator's network. To access the operator's network, the terminal device first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN. RAN equipment is a type of equipment that provides wireless communication functions for terminal equipment. RAN equipment is also called access network equipment. RAN equipment includes but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (RNC), node B (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (BBU) , Transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.

The AMF network element is responsible for the mobility management of users, including mobility status management, assigning temporary user identities, authenticating and authorizing users, etc.

SMF network element, with session management, execution of PCF issuing control strategy, selection of UPF, UE internet protocol (IP) address allocation, bearer establishment, modification and release, quality of service (QoS) control And other functions.

UPF network element supports functions such as interconnecting PDU sessions with data networks, packet routing and forwarding, and data packet inspection.

The UDM network element is mainly responsible for functions such as management of contract data and user access authorization.

UDR, storing and retrieving contract data, policy data and public structure data, etc.; for UDM, PCF and NEF to obtain relevant data. UDR must be able to have different data access authentication mechanisms for different types of data such as contract data and policy data to ensure the security of data access; UDR must be able to return and carry appropriate data for illegal servicing operations or data access requests The failure response for the reason value.

NEF network elements mainly support network capability opening functions and open network capabilities and services to the outside world; the third generation partnership project (3GPP) NF publishes functions and events to other NFs through NEF. The capabilities and events opened by NF can be safely opened to third-party applications. NEF uses the standardized interface (Nudr) of the Unified Data Repository (UDR) to store/retrieve structured data. Translate AF exchange information and internal network function exchange information.

The AF network element is used to provide certain application layer services to the UE. When the AF provides services to the UE, it has requirements for QoS policies and charging policies and needs to notify the network. At the same time, AF also needs application-related information fed back from the core network.

The PCF network element is mainly responsible for policy control functions such as billing, QoS bandwidth guarantee and mobility management, and UE policy decision-making for the session and service flow levels. In this architecture, the PCF connected to the AMF and the SMF corresponds to AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management), and may not be the same PCF entity in actual deployment scenarios.

The NRF network element can be used to provide the network element discovery function, and provide the network element information corresponding to the network element type based on the request of other network elements. NRF also provides network element management services, such as network element registration, update, de-registration, and network element status subscription and push.

AUSF network element: Mainly responsible for authenticating users to determine whether users or devices are allowed to access the network.

A DN is a network located outside the operator's network. The operator's network can access multiple DNs. A variety of services can be deployed on the DN to provide terminal equipment with services such as data and/or voice. For example, DN is the private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminal devices. A control server for the sensors is deployed in the DN, and the control server can provide services for the sensors. The sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. For another example, the DN is the internal office network of a company. The mobile phones or computers of the employees of the company can be terminal devices, and the mobile phones or computers of the employees can access the information and data resources on the internal office network of the company.

In Figure 1A, Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. The meaning of these interface serial numbers can refer to the meaning defined in the 3GPP standard protocol, which is not limited here.

As shown in FIG. 1B, it is a schematic diagram of a 5G network architecture based on a point-to-point interface. For the introduction of the functions of the network elements therein, reference may be made to the introduction of the functions of the corresponding network elements in FIG. The main difference between Fig. 1B and Fig. 1A is that the interfaces between the various network elements in Fig. 1B are point-to-point interfaces, rather than service-oriented interfaces.

In the architecture shown in Figure 1B, the interface names and functions between each network element are as follows:

1) N7: The interface between PCF and SMF, which can be used to issue protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control strategy.

2) N15: The interface between PCF and AMF, which can be used to issue UE policies and access control related policies.

3) N5: The interface between AF and PCF, which can be used for application service request issuance and network event reporting.

4), N4: The interface between SMF and UPF, which can be used to transfer information between the control plane and the user plane, including controlling the issuance of user-oriented forwarding rules, QoS control rules, traffic statistics rules, etc., and user-plane Information reported.

5) N11: The interface between SMF and AMF, which can be used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to UE, and transfer radio resource control information sent to RAN.

6) N2: The interface between AMF and RAN, which can be used to transfer radio bearer control information from the core network side to the RAN.

7) N1: The interface between the AMF and the UE, which can be used to transfer QoS control rules to the UE.

8) N8: The interface between AMF and UDM, which can be used for AMF to obtain access and mobility management related subscription data and authentication data from UDM, and AMF to register UE current mobility management related information with UDM, etc.

9) N10: The interface between SMF and UDM, which can be used for SMF to obtain session management related subscription data from UDM, and SMF to register UE current session related information with UDM, etc.

10) N35: The interface between UDM and UDR, which can be used for UDM to obtain user subscription data information from UDR.

11) N36: The interface between the PCF and the UDR, which can be used for the PCF to obtain policy-related contract data and application data-related information from the UDR.

12) N12: The interface between AMF and AUSF, which can be used for AMF to initiate an authentication process to AUSF, where SUCI can be carried as a contract identifier;

13). N13: The interface between UDM and AUSF, which can be used for AUSF to obtain user authentication vector from UDM to execute the authentication process.

It is understandable that the aforementioned network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform). Optionally, the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in the embodiment of the present application.

The mobility management network element, the session management network element, the policy control network element, the application function network element, the access network device, the network opening function network element, and the user plane network element in the embodiments of the present application may be shown in FIG. 1A or FIG. 1B respectively. The AMF, SMF, PCF, AF, RAN, NEF, UPF, or future communications such as the 6th generation (6G) network with the above AMF, SMF, PCF, AF, RAN, NEF, UPF functions The network element of this application is not limited in this embodiment. For the convenience of description, in the embodiments of this application, the mobility management network element, the session management network element, the policy control network element, the application function network element, the access network device, the network opening function network element, and the user plane network element are respectively the above-mentioned AMF, SMF, PCF, AF, RAN, NEF, UPF are taken as examples for description. Further, in the embodiment of the present application, the terminal device is referred to as UE for short.

A wireless audio system is a system that uses radio waves instead of wired to transmit audio signals. Wireless audio systems usually include wireless microphone systems and wireless back-to-back systems, as well as systems that carry out long-distance audio transmission wirelessly in some specific occasions. The wireless audio system has become an indispensable subsystem in today's large-scale performances.

The wireless audio system can be applied to scenes such as large-scale concerts and concerts. The wireless audio system has higher requirements for end-to-end delay (lateny), transmission period, safety and reliability, and sound quality.

As shown in Figure 2, it is a schematic diagram of the components involved in the professional audio production communication system. On the one hand, the system includes a wireless audio input, which is denoted here as a microphone. The audio is captured at the audio source and sent to the mixing processing server through a wireless connection, which can perform the mixing, transcoding, equalization, or other processing tasks of several audio inputs. The result of the audio processing is sent to an output device via a wireless connection, which can be a speaker, a general-purpose device equipped with headphones, or other devices.

For example, in the actual performance process, multiple input devices usually generate sound source data. For example, in a concert performance, there are bassists, guitarists, drummers, and vocals. Each of them has a complete input device. Sound source data essential for a performance. All the sound source data is then sent to the mixing processing server on the network side through the access network device for sound mixing or mixing processing. When different UEs send uplink data, the access network equipment performs independent scheduling and allocates different air interface scheduling resources to different UEs (where air interface scheduling resources include time resources and frequency resources, and time resources can be used in time units such as time slots ( slot), mini-slot (mini-slot), the mixing processing server mixes the input data of different sound sources, and then sends the mixed effect to each performer through the access network equipment. In the ear-return device, every performer can hear the effect of the live performance. The audio mixing processing server generally needs to wait until the uplink data of the UEs in the same audio mixing group (also referred to as the user group) arrive before starting audio mixing. That is, in the same mixing group, the network side processes the received data according to the deterministic time. Therefore, it must be restricted that the data sent by each UE needs to arrive within a certain time range, otherwise once a certain or a certain If the data of some UEs does not arrive within a certain time range, the audio mixing process cannot be performed, and the network side will discard the data received from other UEs, resulting in audio mixing failure.

In the existing mechanism, when multiple UEs belonging to the same audio mixing group need to transmit uplink data through the access network device, they need to transmit the uplink data according to the air interface scheduling resources allocated by the access network device. The time resources in the air interface scheduling resources allocated to different UEs of the same audio mixing group may be in time units that are far apart, resulting in a large difference in the time delay for uplink data sent by different UEs to reach the audio mixing processing server. That is, the existing mechanism cannot guarantee the deterministic transmission delay of uplink data sent by UEs in the same audio mixing group, which may result in audio mixing failure of the audio mixing processing server.

As shown in FIG. 3, it is a schematic diagram of a delay caused by multiple UEs when sending uplink data. Assuming that UE1 and UE2 have been time synchronized (the time of the two is the same), the uplink data of UE1 and the uplink data of UE2 are sent, although the hardware equipment of UE1 and the hardware equipment of UE2 can ensure that they generate data at the same time point. However, the time units allocated by the RAN equipment for UE1 and UE2 may be different and far apart. In this way, during the air interface transmission, the uplink data of UE1 may be sent earlier than the uplink data of UE2, so although the two are sent through the same RAN device , But it is not scheduled in the same or adjacent time unit. This results in a large time delay between the uplink data of UE1 and the uplink data of UE2. In addition, when the subsequent RAN equipment transmits the uplink data of UE1 and UE2, the transmission path on the network side may also introduce additional time delay, and the time delay between the uplink data of UE1 and the uplink data of UE2 may occur between the mixer equipment. Accumulate, causing the time delay to increase further.

To solve the above problem, based on the network architecture shown in FIG. 1A or FIG. 1B, as shown in FIG. 4, an embodiment of the present application provides a resource allocation method. On the RAN side, this method can be executed by RAN equipment or components (such as chips, circuits, etc.) used for RAN equipment; on the network side, it can be executed by SMF or components (such as chips, circuits, etc.) used for SMF. For ease of description, the following uses the RAN device and the SMF to execute the method as an example for description.

The method includes the following steps:

Step 401: The SMF receives the identifier of the user group.

The identifier of the user group is used to indicate at least two UEs. Optionally, the user group may also be referred to as a synchronous scheduling service group, a synchronous scheduling group, and so on.

Any UE in the user group needs air interface scheduling resources synchronized with other UEs in the user group. Or it can be understood that the UEs in the user group have requirements for synchronized air interface scheduling resources with each other. Or it can be understood that the UEs in the user group have synchronization scheduling requirements with each other. Wherein, the synchronized air interface scheduling resource refers to that the air interface scheduling resources allocated to UEs in the same user group are in the same or adjacent time units.

In the embodiment of the present application, the time unit may be a slot or a mini-slot, which will be described in a unified manner here, and will not be repeated in the following.

As an implementation manner, the SMF may receive the identity of the user group from the first UE, and the first UE belongs to the user group. That is, the first UE requests the allocation of air interface scheduling resources, and at the same time carries the identity of the user group to which it belongs.

As yet another implementation manner, the SMF can receive the UE list and user group identifiers from the AF. That is, the AF requests the allocation of air interface scheduling resources for each UE in the UE list, and at the same time carries the identifier of the user group to which each UE in the UE list belongs.

Step 402: The SMF determines synchronization scheduling indication information according to the user group identifier, and the synchronization scheduling indication information is used to indicate that the UE in the user group needs to synchronize air interface scheduling resources with other UEs in the user group.

As an implementation manner, the corresponding relationship between the identifier of each user group and the synchronization scheduling indication information can be pre-configured on the SMF. After the SMF obtains the identifier of the user group, the SMF can determine the corresponding synchronization scheduling indication information according to the identifier of the user group.

As yet another implementation manner, the corresponding relationship between the identification list of the user group and the synchronization scheduling indication information can be pre-configured on the SMF. The user group identifier list contains at least one user group identifier. If the identifier of the user group obtained by the SMF belongs to the list, the SMF can determine the corresponding synchronization scheduling indication information.

As yet another implementation manner, the SMF may also obtain the correspondence between the identifier of the user group and the synchronization scheduling indication information through other network elements (for example, a PCF network element), which is not limited in the embodiment of the present application. It should be noted that UEs in the same user group can correspond to the same synchronization scheduling indication information.

Step 403: The SMF sends synchronization scheduling indication information to the RAN. Correspondingly, the RAN can receive the synchronization scheduling indication information.

Step 404: The RAN allocates air interface scheduling resources for the UE according to the synchronization scheduling indication information. Wherein, the air interface scheduling resource is used for the UE to send uplink data.

It should be noted that, if in step 401, the SMF is the identifier of the user group received from the first UE, then in step 404, the RAN specifically allocates air interface scheduling resources for the first UE. If in step 401, the SMF is the identifier of the user group received from the AF, then in step 404, the RAN specifically allocates air interface scheduling resources to all UEs in the user group in sequence. It can be understood that the SMF performs step 403 multiple times according to the number of UEs in the user group, that is, the number of UEs in the user group is multiple, and the SMF sends synchronization scheduling indication information to the RAN multiple times, where each synchronization scheduling indication information is the same as Each UE in the user group is associated, and the RAN allocates air interface scheduling resources for each UE according to the synchronization scheduling indication information.

The way that the RAN allocates air interface scheduling resources to the UE may be, for example:

Method 1: The RAN allocates air interface scheduling resources for the UE from idle resources according to the synchronization scheduling indication information.

For example, according to the received synchronization scheduling indication information, the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources, or the RAN determines that it has not received any information associated with the UE in the user group before. Synchronize scheduling indication information, the RAN can allocate air interface scheduling resources according to the normal process, for example, according to the resource allocation method in the prior art, allocate air interface scheduling resources from idle resources to the UE, that is, the RAN determines the UE according to its own resource allocation. The time unit for uplink data scheduling, and sends a resource scheduling assignment (Grant) to the UE to notify the UE to send the uplink data in a certain time unit. At the same time, the RAN locally stores the corresponding relationship between the synchronization scheduling indication information and the scheduling resource. Subsequently, the UE sends the uplink data to the RAN according to the air interface scheduling resources allocated by the RAN. After allocating air interface scheduling resources for the UE, the RAN may also allocate reserved resources for other UEs in the user group, where the reserved resources are in the same or adjacent time unit as the air interface scheduling resources allocated to the UE. That is, the reserved resources are applicable to other UEs in the user group.

It should be noted that if the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has not received the synchronization scheduling indication information associated with the UE in the user group before, it refers to , In a certain time range (for example, taking a concert scene as an example, the vocalist, bassist, guitarist, drummer, etc., as UEs in the user group have air-interface scheduling synchronization requirements, and the time from the beginning to the end of a concert Within range, etc.) The RAN determines that the synchronization scheduling indication information associated with the UE in the user group has not been received before. Based on this implementation manner, the air interface scheduling resources for sending data of multiple devices (such as media devices) within a time range can be uniformly scheduled and allocated, so that the delay in deterministic transmission can be reduced.

For another example, the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources according to the received synchronization scheduling indication information, or the RAN determines that it has previously received synchronization associated with UEs in the user group. According to the scheduling indication information, the RAN can allocate air interface scheduling resources for the UE from the reserved resources.

It should be noted that the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has previously received synchronization scheduling indication information associated with the UEs in the user group, which refers to: In a certain time range (for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc., has air-interface scheduling synchronization requirements, and the time range from the beginning to the end of a concert (Internal etc.) The RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.

Method 2: The RAN allocates air interface scheduling resources for the UE from the air interface resources corresponding to the user group according to the synchronization scheduling indication information.

The air interface resource here may be a fixed scheduling resource corresponding to the user group configured on the RAN, or the air interface resource may also be a fixed scheduling resource allocated by the RAN to the user group when the UE in the user group initiates the registration process.

For example, according to the received synchronization scheduling indication information, the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources, or the RAN determines that it has not received any information associated with the UE in the user group before. Synchronize scheduling indication information, the RAN can allocate air interface scheduling resources for the UE from the air interface resources corresponding to the user group, that is, the RAN determines the time unit for uplink data scheduling of the UE according to its own resource allocation, and sends resource scheduling to the UE Assignment (Grant) informs the UE to send the uplink data in a certain time unit. Subsequently, the UE sends the uplink data to the RAN according to the resources allocated by the RAN. After allocating air interface scheduling resources for the UE, the RAN can also allocate reserved resources for other UEs in the user group. The reserved resources are the resources in the above air interface resources and are the same as or adjacent to the resources already allocated to the UE. Time unit. That is, the reserved resources are applicable to other UEs in the user group.

It should be noted that if the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has not received the synchronization scheduling indication information associated with the UE in the user group before, it refers to , In a certain time range (for example, taking a concert scene as an example, the vocalist, bassist, guitarist, drummer, etc., as UEs in the user group have air-interface scheduling synchronization requirements, and the time from the beginning to the end of a concert Within range, etc.) The RAN determines that the synchronization scheduling indication information associated with the UE in the user group has not been received before.

As an example, UE1 and UE2 belong to the same user group. For example, if UE1 is the first UE in the user group to request the allocation of air interface scheduling resources, the RAN can allocate air interface scheduling resources to UE1 from idle resources or air interface resources corresponding to the user group, and also allocate reserved resources. The resource and the scheduling resource allocated for UE1 are in the same or adjacent time unit. Subsequently, UE2 requests the allocation of air interface scheduling resources again, and the RAN can allocate air interface scheduling resources for UE2 on the above reserved resources. In this way, the scheduling resources in the same or adjacent time units are allocated to UEs in the same user group.

For example, referring to FIG. 5A and FIG. 5B, schematic diagrams of allocating air interface scheduling resources. In FIG. 5A, the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit. In FIG. 5B, the scheduling resources allocated to UE1 and UE2 are in adjacent time units.

Referring to FIG. 5A, assuming that UE1 is the first UE in the user group to request the allocation of air interface scheduling resources, the RAN allocates UE1 from idle resources (for the above method 1) or the air interface resources corresponding to the user group (for the above method 2) Air interface scheduling resources, and then allocate reserved resources from idle resources (for the above method 1) or air interface resources corresponding to the user group (for the above method 2), and the reserved resources are in the same time unit as the air interface scheduling resources allocated for UE1, At this time, the reserved resources include the air interface scheduling resources allocated to UE2 shown in FIG. 5A and the reserved resources shown in FIG. 5A. Subsequently, UE2 in the user group (that is, the second UE in the user group that requests the allocation of air interface scheduling resources) requests the allocation of air interface scheduling resources, and the RAN allocates air interface scheduling resources for UE2 from the above reserved resources, and allocates air interface scheduling resources for UE2 As shown in FIG. 5A, it is in the same time unit as the allocation of air interface scheduling resources for UE1, and the remaining reserved resources at this time are shown in FIG. 5A.

Referring to Figure 5B, assuming that UE1 is the first UE in the user group to request the allocation of air interface scheduling resources, the RAN allocates UE1 from idle resources (for the above method 1) or the air interface resources corresponding to the user group (for the above method 2) Air interface scheduling resources, and then allocate reserved resources from idle resources (for the above method 1) or air interface resources corresponding to the user group (for the above method 2), and the reserved resources are the same as or adjacent to the air interface scheduling resources allocated for UE1 Time unit. At this time, the reserved resources include the air interface scheduling resources allocated to UE2 shown in FIG. 5B and the reserved resources shown in FIG. 5B. Subsequently, UE2 in the user group (that is, the second UE in the user group that requests the allocation of air interface scheduling resources) requests the allocation of air interface scheduling resources, and the RAN allocates air interface scheduling resources for UE2 from the above reserved resources, and allocates air interface scheduling resources for UE2 As shown in FIG. 5B, the time unit is adjacent to the allocation of air interface scheduling resources for UE1, and the remaining reserved resources at this time are shown in FIG. 5B.

Optionally, if in the above step 401, the SMF is the identifier of the user group received from the first UE, then in the above step 403, the SMF may also send the identifier of the PDU session of the first UE to the RAN, and the PDU session is with the above The session associated with the synchronization service performed by the first UE in the user group. Furthermore, in this step 404, the RAN allocates air interface scheduling resources for the PDU session of the first UE according to the synchronization scheduling indication information.

Optionally, if in step 401, the SMF is the user group identifier and the UE list received from the AF, then in step 403, the SMF may also determine the PDU session corresponding to each UE in the UE list according to the UE list, and Send the PDU session identifier corresponding to each UE in the UE list to the RAN. The SMF sends the PDU session identifier corresponding to each UE in the UE list to the RAN multiple times according to the number of UEs in the UE list. The PDU session is A session associated with the synchronization service performed by the UE in the above-mentioned user group. Furthermore, in this step 404, the RAN allocates air interface scheduling resources to the PDU sessions corresponding to each UE in the UE list according to the synchronization scheduling indication information.

For example, UE1 and UE2 belong to the same user group, and the schematic diagram of RAN allocating air interface scheduling resources to UE1 and UE2 can refer to FIG. 5A and FIG. 5B. Subsequent when UE1 and UE2 send uplink data, the RAN scheduling diagram of the uplink data sent by UE1 and UE2 respectively can refer to Figure 6. If the RAN allocates air interface scheduling resources, the uplink data of UE1 and UE2 are placed in the same time unit. Or scheduling in adjacent time, you can try to ensure that the uplink data of UE1 and UE2 are transmitted to the network side at the same time, so that when the network is performing mixing processing, it can receive the uplink data of UE1 and UE2 as much as possible. Helps ensure the effect and quality of the mixing process.

In the above solution, the network side (SMF) can determine the synchronization scheduling indication information on the RAN side based on the identity of the user group, and the RAN can allocate the air interface scheduling resources of the same or adjacent time unit to the UEs in the user group according to the synchronization scheduling indication information. Therefore, the network side can receive the data sent by different UEs in the user group within the shortest possible time delay, which helps to improve the quality of data processing.

The following describes the process shown in FIG. 4 in combination with specific examples.

As shown in FIG. 7, it is a schematic flowchart of another resource allocation method provided by an embodiment of this application. In this solution, the UE sends the identity of the user group in which it is located to the network. The network can allocate synchronization scheduling indication information based on the identity of the user group, and send the synchronization scheduling indication information to the RAN. In this way, the RAN can perform special resource scheduling for the UE according to the synchronization scheduling indication information, that is, perform special resource scheduling for UEs in the same user group. Synchronous scheduling of resources.

The prerequisite of this solution is that multiple UEs join the same user group and all obtain the same group ID. For example, the group ID can be a user group ID (UE group ID) (also called a user group). ID) or service group ID (also called service group ID). The group ID is used to identify a specific group of UEs. Each UE in the group has the same service type (such as media service). ), or the same business requirements (such as synchronization scheduling requirements), etc., which are not limited in the embodiment of the present application.

Optionally, the methods for the UE to obtain the group identity include but are not limited to the following two:

a) In the registration process, the network generates according to the UE's subscription data (for example, generates a group ID according to the service type that the UE subscribes to), or the UE's subscription data contains the group ID to which the UE belongs, and then in the registration acceptance message, Sent by the network to the UE.

b) The group identity to which the UE belongs is configured locally on the UE.

Taking the group ID as the user group ID as an example, the method includes the following steps:

Step 701: The UE sends a first request to the AMF. Correspondingly, the AMF can receive the first request.

The first request includes the PDU session ID (PDU session ID) and the user group ID, and the PDU session ID is used to identify the PDU session. Any UE in the user group needs air interface scheduling resources synchronized with other UEs in the user group.

The UE that sends the first request in step 701 belongs to the user group.

As an implementation of this step 701, the UE may send a NAS message (NAS message) to the AMF through the RAN, and the NAS message carries the above-mentioned first request.

Step 702: AMF sends a second request to SMF. Correspondingly, the SMF can receive the second request.

The second request carries the identifier of the PDU session and the user group identifier.

Step 703: The SMF determines synchronization scheduling indication information according to the user group identifier.

Wherein, the method for implementing the SMF to determine the synchronization scheduling indication information according to the user group identifier may refer to the related description of step 402 in the embodiment corresponding to FIG. 4, which will not be repeated here.

It should be noted that if the SMFs corresponding to the PDU sessions of different UEs in the same user group are different, then after different SMFs receive the user group identifiers sent by different UEs, different SMFs determine the synchronization scheduling based on the same user group identifier The instructions are the same. It can be understood that the corresponding relationship between the same user group identifier and the synchronization scheduling identifier is configured on different SMFs. Therefore, different SMFs can determine the same synchronization scheduling indication information according to the same user group identifier.

Optionally, in this process, the SMF and the PCF may further update the relevant policies for session management.

Step 704: The SMF sends a second response to the AMF. Correspondingly, the AMF can receive the second response.

The second response carries the aforementioned synchronization scheduling indication information and also carries the identifier of the PDU session. For example, the second response may carry an N2 session management container (N2 SM container), and the N2 SM container may carry the foregoing synchronization scheduling indication information and the identifier of the PDU session. The second response may also carry the N1 session management container (N1 SM container), and the N1 SM container carries the identifier of the PDU session and the first response.

Step 705: AMF sends a third request to the RAN. Correspondingly, the RAN can receive the third request.

The third request includes the N2 SM container and the N1 SM container, where the N2 SM container includes the synchronization scheduling indication information and the identifier of the PDU session.

Step 706: The RAN allocates air interface scheduling resources for the UE according to the synchronization scheduling indication information and the identifier of the PDU session.

Among them, the identifier of the PDU session is used to indicate the PDU session for which air interface scheduling resources need to be allocated.

The RAN allocates air interface scheduling resources for the UE's PDU session according to the synchronization scheduling indication information and the PDU session identifier, which can be:

Method 1: The RAN allocates air interface scheduling resources for the UE from idle resources according to the synchronization scheduling indication information and the PDU session identifier.

For example, according to the received synchronization scheduling indication information, the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources, or the RAN determines that it has not received any information associated with the UE in the user group before. Synchronous scheduling indication information, the RAN can allocate air interface scheduling resources according to the normal process, for example, according to the resource allocation method in the prior art, allocate air interface scheduling resources for the PDU session of the UE from idle resources, that is, the RAN can allocate air interface scheduling resources according to its own resource allocation. Determine the time unit for uplink data scheduling of the UE, and send a resource scheduling assignment (Grant) to the UE to notify the UE to send the uplink data of the PDU session in a certain time unit. At the same time, the RAN locally stores the corresponding relationship between the synchronization scheduling indication information and the scheduling resource. Subsequently, the UE sends the uplink data to the RAN according to the air interface scheduling resources allocated by the RAN. After allocating air interface scheduling resources for the PDU session of the UE, the RAN can also reserve resources for the allocation of PDU sessions of other UEs in the user group. The reserved resources are the same as the air interface scheduling resources of the PDU sessions that have been allocated to the UE. Or adjacent time units. That is, the reserved resources are applicable to PDU sessions of other UEs in the user group. For example, UE1 and UE2 belong to the same user group, and UE1 needs to synchronize air interface scheduling resources with UE2. Referring to FIG. 5A and FIG. 5B, it is a schematic diagram of allocating air interface scheduling resources. In FIG. 5A, the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit. In FIG. 5B, the scheduling resources allocated to UE1 and UE2 are in adjacent time units.

For another example, the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources according to the received synchronization scheduling indication information, or the RAN determines that it has previously received synchronization associated with UEs in the user group. According to the scheduling indication information, the RAN can allocate air interface scheduling resources for the PDU session of the UE from the reserved resources.

Method 2: The RAN allocates air interface scheduling resources for the UE from the air interface resources corresponding to the user group according to the synchronization scheduling indication information and the identifier of the PDU session.

For example, according to the received synchronization scheduling indication information, the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources, or the RAN determines that it has not received any information associated with the UE in the user group before. Synchronous scheduling indication information, the RAN can allocate air interface scheduling resources for the PDU session of the UE from the air interface resources corresponding to the user group, that is, the RAN determines the time unit for uplink data scheduling of the UE according to its own resource allocation, and gives it to the UE. Send a resource scheduling assignment (Grant) to notify the UE to send the uplink data in a certain time unit. Subsequently, the UE sends the uplink data to the RAN according to the resources allocated by the RAN. After allocating air interface scheduling resources for the PDU session of the UE, the RAN can also allocate reserved resources for the PDU sessions of other UEs in the user group. The reserved resources are the above-mentioned air interface resources and are different from those already allocated to the UE. The air interface scheduling resources of the PDU session are in the same or adjacent time unit. That is, the reserved resources are applicable to PDU sessions of other UEs in the user group. For example, UE1 and UE2 belong to the same user group, and UE1 needs to synchronize air interface scheduling resources with UE2. Referring to FIG. 5A and FIG. 5B, it is a schematic diagram of allocating air interface scheduling resources. In FIG. 5A, the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit. In FIG. 5B, the scheduling resources allocated to UE1 and UE2 are in adjacent time units.

It should be noted that the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group, which refers to: In a certain time range (for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc., has air-interface scheduling synchronization requirements, and the time range from the beginning to the end of a concert (Internal etc.) The RAN determines that it has not received the synchronization scheduling indication information associated with the UE in the user group before.

It should be noted that in this embodiment of the application, different UEs in the same user group access the same RAN. In this way, even if the SMFs corresponding to the PDU sessions of different UEs in the same user group are different, in step 703, different SMFs determine the same synchronization scheduling indication information according to the same user group identifier, so the RAN can be the same user group Different UEs in the internal allocation of synchronized air interface scheduling resources.

Step 707: The RAN sends air interface scheduling resources to the UE. Correspondingly, the UE can receive the air interface scheduling resource.

The air interface scheduling resource is the scheduling resource on the air interface side allocated by the RAN to the UE for sending uplink data. The UE can perform local configuration according to the air interface scheduling resources sent by the RAN, and subsequently the UE sends uplink data to the RAN according to the air interface scheduling resources allocated by the RAN.

In this step 707, the RAN may also send the aforementioned N1 SM container to the UE. After receiving the N1 SM container, the UE can obtain the first response and the PDU session identifier therein.

In step 708, the RAN sends a third response to the AMF, and accordingly, the AMF can receive the third response.

This step 708 is optional.

As an implementation solution, the foregoing embodiment may be executed in the PDU session establishment process after the UE is registered to the network. In the PDU session establishment process, the above-mentioned first request may be a PDU session establishment request (PDU Session establishment Request), the above-mentioned second request may be a PDU session establishment request (Nsmf_PDUSession_CreateSMContext request), and the above-mentioned first response may be a PDU session establishment acceptance message. (PDU Session Establishment Accept), the foregoing second response may be a PDU session establishment request response (Nsmf_PDUSession_CreateSMContext response), the foregoing third request may be an N2 session request (N2session request), and the foregoing third response may be an N2 session response (N2 session response) ).

As an implementation solution, the foregoing embodiment may be executed in the PDU session modification process after the UE is registered to the network. In the PDU session modification process, the above first request may be a PDU session modification request (PDU Session modification Request), the above second request may be a PDU session update request (Nsmf_PDUSession_UpdateSMContext request), and the above first response may be a PDU session modification request response. Message (PDU Session Modification ack), the above-mentioned second response may be a PDU session update response (Nsmf_PDUSession_UpdateSMContext response), the above-mentioned third request may be an N2 session request (N2session request), and the above-mentioned third response may be an N2 session response (N2 session response) ).

For example, UE1 and UE2 belong to the same user group, and the schematic diagram of RAN allocating air interface scheduling resources to UE1 and UE2 can refer to FIG. 5A and FIG. 5B. Subsequent when UE1 and UE2 send uplink data, the RAN scheduling diagram of the uplink data sent by UE1 and UE2 respectively can refer to Figure 6. If the RAN allocates air interface scheduling resources, the uplink data of UE1 and UE2 are placed in the same time unit. Or scheduling in adjacent time, you can try to ensure that the uplink data of UE1 and UE2 are transmitted to the network side at the same time, so that when the network is performing mixing processing, it can receive the uplink data of UE1 and UE2 as much as possible. Helps ensure the effect and quality of the mixing process. In the above solution, the UE carries the user group identifier in the first request, and the network side (SMF) can determine the synchronization scheduling indication information on the RAN side based on the user group identifier, and the RAN can assign the UEs in the user group the same according to the synchronization scheduling indication information. Or air interface scheduling resources of adjacent time units, so that the network side can receive data sent by different UEs in the user group within the shortest possible time delay, which helps to improve the quality of data processing.

As shown in FIG. 8, it is a schematic flowchart of another resource allocation method provided by an embodiment of this application. In this solution, after the UE has established a session, the AF sends a request to the network, and the request carries the user group identifier. In this way, the network can determine the synchronization scheduling indication information based on the user group identifier, and then send the synchronization scheduling indication information to the RAN. In this way, the RAN can perform special resource scheduling for the UE, that is, perform resource synchronization scheduling for UEs in the same user group.

b) The group identity to which the UE belongs is configured locally on the UE.

Step 801: The AF sends a policy update request (Npcf_Policy Authorization update request) to the PCF. Correspondingly, the PCF can receive the policy update request.

For example, the AF can send the aforementioned policy update request to the PCF through the NEF.

The policy update request carries a user group identifier and a UE list (UE list) corresponding to the user group identifier.

Any UE in the user group needs air interface scheduling resources synchronized with other UEs in the user group.

The UE list contains the identities of one or more UEs, and the identities of the UEs in the UE list belong to the aforementioned user group.

In step 802, the PCF triggers a PDU session-related policy update process (PCF initiated SMF Policy Association Modification). In this process, the PCF triggers the SMF to update the PDU session of the UE indicated by the UE list, and the PCF sends the user group identifier and the UE list to the SMF.

In step 803, the SMF determines the synchronization scheduling indication information according to the user group identifier, and determines the identifier of the PDU session corresponding to each UE indicated by the UE list.

In step 804, the SMF sends the synchronization scheduling indication information and the PDU session identifier to the AMF.

For example, SMF can send synchronization scheduling indication information and PDU session identifier to AMF through Namf_Communication_N1N2MessageTransfer request.

Step 805: The AMF sends an N2 session request (N2 session request) to the RAN. Correspondingly, the RAN can receive the N2 session request.

The N2 session request includes N2 SM container and N1 SM container, where N2 SM container includes synchronization scheduling indication information and PDU session identifier, and N1 SM container carries PDU session identifier and PDU session modification acknowledgement message (PDU Session Modification ack) .

Step 806: The RAN allocates air interface scheduling resources for the UE according to the synchronization scheduling indication information and the identifier of the PDU session.

For the implementation method for the RAN to allocate air interface scheduling resources for the PDU session of the UE according to the synchronization scheduling indication information and the identifier of the PDU session, reference may be made to the related description of the embodiment corresponding to FIG.

It should be noted that in this embodiment of the application, different UEs in the same user group access the same RAN. In this way, even if the SMFs corresponding to the PDU sessions of different UEs in the same user group are different, in step 803, different SMFs determine the same synchronization scheduling indication information according to the same user group identifier, so the RAN can be the same user group Different UEs in the internal allocation of synchronized air interface scheduling resources.

Step 807: The RAN sends air interface scheduling resources to the UE. Correspondingly, the UE can receive the air interface scheduling resource.

In step 807, the RAN may also send the aforementioned N1 SM container to the UE. After receiving the N1 SM container, the UE can obtain the PDU session modification response message and the PDU session identifier therein.

In step 808, the RAN sends an N2 session response to the AMF, and accordingly, the AMF can receive the N2 session response.

This step 808 is optional.

In the above solution, the AF carries the user group identifier in the policy update request, and the network side (SMF) can determine the synchronization scheduling indication information on the RAN side based on the user group identifier, and the RAN can assign the UEs in the user group to be in the same position according to the synchronization scheduling indication information. Or air interface scheduling resources of adjacent time units, so that the network side can receive data sent by different UEs in the user group within the shortest possible time delay, which helps to improve the quality of data processing.

The foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspective of interaction between various network elements. It can be understood that, in order to realize the above-mentioned functions, each network element described above includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.

It can be understood that, in each of the foregoing method embodiments, the steps or operations implemented by the terminal device can also be implemented by components (such as chips or circuits) configured in the terminal device, corresponding to the steps or operations implemented by the access network device. , Can also be implemented by components (such as chips or circuits) configured in the access network device, corresponding to the steps or operations implemented by the session management network element, or implemented by components (such as chips or circuits) configured in the session management network element .

Refer to FIG. 9, which is a schematic diagram of a communication device provided by an embodiment of this application. The device is used to implement the steps performed by the corresponding access network equipment in the foregoing method embodiments. As shown in FIG. 9, the device 900 includes a receiving unit 910, a sending unit 920, and a distribution unit 930. Optionally, a determining unit 940 is further included. The receiving unit 910 is configured to receive synchronization scheduling indication information associated with a terminal device, where the synchronization scheduling indication information is used to indicate that the terminal device needs to synchronize air interface scheduling resources with other terminal devices in the user group where the terminal device is located The allocation unit 930 is configured to allocate the air interface scheduling resource to the terminal device according to the synchronization scheduling indication information. The sending unit 920 is configured to send the air interface scheduling resource to the terminal device.

In a possible implementation method, when the receiving unit 910 has not received the synchronization scheduling indication information associated with the terminal equipment in the user group; the allocating unit 930 is specifically configured to perform according to the synchronization The scheduling indication information determines the identity of the user group; according to the identity of the user group, the air interface scheduling resource is allocated to the terminal device from the air interface resources corresponding to the user group.

In a possible implementation method, the receiving unit 910 is further configured to receive an identifier of the user group; the allocating unit 930 is further configured to allocate a user group to the user group according to the identifier of the user group. Said air interface resources.

In a possible implementation method, the determining unit 940 is configured to determine a first reserved resource among the air interface resources, where the first reserved resource is the same or the same as the air interface scheduling resource allocated to the terminal device. Adjacent time unit, the first reserved resource is used to allocate to other terminal devices in the user group.

In a possible implementation method, when the receiving unit 910 has received the synchronization scheduling indication information associated with the terminal equipment in the user group; the allocating unit 930 is specifically configured to reserve from the second In resources, the air interface scheduling resource is allocated to the terminal device, and the second reserved resource is in the same or adjacent time unit as the air interface scheduling resource that has been allocated to one or more terminal devices in the user group .

It can be understood that each of the above-mentioned units may also be referred to as a module or a circuit, etc., and each of the above-mentioned units may be provided independently, or may be fully or partially integrated.

In some possible implementation manners, the foregoing receiving unit 910 and sending unit 920 may also be implemented by a transceiver unit, or the receiving unit 910 and the sending unit 920 may also be collectively referred to as a transceiver unit. The foregoing allocation unit 930 and the determination unit 940 may also be implemented by a processing unit, or the allocation unit 930 and the determination unit 940 may also be collectively referred to as a processing unit.

The foregoing receiving unit 910, sending unit 920, or transceiving unit may also be referred to as a communication interface, and the foregoing processing unit may also be referred to as a processor.

Optionally, the aforementioned communication device 900 may further include a storage unit for storing data or instructions (also referred to as codes or programs), and each of the aforementioned units may interact or couple with the storage unit to implement the corresponding method or Features. For example, the processing unit may read data or instructions in the storage unit, so that the communication device implements the method in the foregoing embodiment.

Refer to FIG. 10, which is a schematic diagram of a communication device provided by an embodiment of this application. The device is used to implement the steps performed by the corresponding session management network element in the foregoing method embodiment. As shown in FIG. 10, the device 1000 includes a receiving unit 1010, a sending unit 1020, and a determining unit 1030. The receiving unit 1010 is configured to receive an identifier of a user group, the user group including at least two terminal devices; the determining unit 1030 is configured to determine synchronization scheduling indication information according to the identifier of the user group, and the synchronization scheduling indication information is used To indicate that the terminal equipment in the user group needs to synchronize air interface scheduling resources with other terminal equipment in the user group; the sending unit 1020 is configured to send the synchronization scheduling instruction information to the access network equipment.

In a possible implementation method, the receiving unit 1010 is specifically configured to receive an identifier of the user group from a first terminal device, and the first terminal device belongs to the user group; or; receiving from an application function The identifier of the user group of the network element.

In some possible implementation manners, the foregoing receiving unit 1010 and sending unit 1020 may also be implemented by a transceiver unit, or the receiving unit 1010 and the sending unit 1020 may also be collectively referred to as a transceiver unit. The above determination unit 1030 may be implemented by a processing unit.

The foregoing receiving unit 1010, sending unit 1020, or transceiver unit may also be referred to as a communication interface, and the foregoing processing unit may also be referred to as a processor.

Optionally, the above-mentioned communication device 1000 may further include a storage unit for storing data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or couple with the storage unit to implement the corresponding method or Features. For example, the processing unit may read data or instructions in the storage unit, so that the communication device implements the method in the foregoing embodiment.

It should be understood that the division of units in the above device is only a division of logical functions, and may be fully or partially integrated into one physical entity in actual implementation, or may be physically separated. In addition, the units in the device can be all implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; part of the units can also be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware. For example, each unit can be a separate processing element, or it can be integrated in a certain chip of the device for implementation. In addition, it can also be stored in the memory in the form of a program, which is called by a certain processing element of the device and executed Features. In addition, all or part of these units can be integrated together or implemented independently. The processing element described here can also become a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.

In an example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASICs), or, one or Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs), or a combination of at least two of these integrated circuits. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

The above receiving unit (for example, the receiving unit) is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices. The above unit for sending (for example, the sending unit) is an interface circuit of the device for sending signals to other devices. For example, when the device is implemented in the form of a chip, the sending unit is an interface circuit used by the chip to send signals to other chips or devices.

Refer to FIG. 11, which is a schematic structural diagram of an access network device provided by an embodiment of this application. The access network device is used to implement the operation of the access network device in the above embodiment. As shown in FIG. 11, the access network equipment includes: an antenna 1110, a radio frequency device 1120, and a baseband device 1130. The antenna 1110 is connected to the radio frequency device 1120. In the uplink direction, the radio frequency device 1120 receives the information sent by the terminal device through the antenna 1110, and sends the information sent by the terminal device to the baseband device 1130 for processing. In the downlink direction, the baseband device 1130 processes the information of the terminal device and sends it to the radio frequency device 1120, and the radio frequency device 1120 processes the information of the terminal device and sends it to the terminal device via the antenna 1110.

The baseband device 1130 may include one or more processing elements 1131, for example, a main control CPU and other integrated circuits, and an interface 1133. In addition, the baseband device 1130 may also include a storage element 1132, which is used to store programs and data; the interface 1133 is used to exchange information with the radio frequency device 1120, and the interface is, for example, a common public radio interface (CPRI) . The above apparatus for access network equipment may be located in the baseband apparatus 1130. For example, the above apparatus for access network equipment may be a chip on the baseband apparatus 1130. The chip includes at least one processing element and an interface circuit. In performing each step of any method performed by the above access network equipment, the interface circuit is used to communicate with other devices. In one implementation, the unit for the access network device to implement each step in the above method can be implemented in the form of a processing element scheduler. For example, the device for the access network device includes a processing element and a storage element, and the processing element calls the storage element to store To execute the method executed by the access network device in the above method embodiment. The storage element may be a storage element with the processing element on the same chip, that is, an on-chip storage element, or a storage element on a different chip from the processing element, that is, an off-chip storage element.

In another implementation, the unit for the access network device to implement each step in the above method may be configured as one or more processing elements, and these processing elements are provided on the baseband device. The processing elements here may be integrated circuits, such as : One or more ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.

The units of the access network equipment that implement each step in the above method can be integrated together and implemented in the form of an SOC. For example, the baseband device includes the SOC chip for implementing the above method. At least one processing element and storage element can be integrated in the chip, and the processing element can call the stored program of the storage element to implement the method executed by the above access network device; or, at least one integrated circuit can be integrated in the chip to implement The method executed by the above access network device; or, it can be combined with the above implementation. The functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.

It can be seen that the above apparatus for an access network device may include at least one processing element and an interface circuit, wherein at least one processing element is used to execute any method executed by the access network device provided in the above method embodiments. The processing element can execute part or all of the steps executed by the access network device in the first way: calling the program stored in the storage element; or in the second way: through the integrated logic circuit of the hardware in the processor element A part or all of the steps executed by the access network device can be executed in a manner of combining instructions; of course, part or all of the steps executed by the access network device can also be executed in combination with the first method and the second manner.

The processing element here is the same as the above description, and it may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or, one or more micro-processing DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. The storage element can be a memory or a collective term for multiple storage elements.

Referring to FIG. 12, a schematic structural diagram of a session management network element provided by an embodiment of this application, which is used to implement the operation of the session management network element in the above embodiment. As shown in FIG. 12, the session management network element includes: a processor 1210, an interface 1230, and optionally, a memory 1220. The interface 1230 is used to implement communication with other devices.

The method executed by the session management network element in the above embodiment can be implemented by the processor 1210 calling a program stored in a memory (which may be the memory 1220 in the session management network element or an external memory). That is, the apparatus for the session management network element may include a processor 1210 that calls a program in the memory to execute the method executed by the session management network element in the above method embodiment. The processor here may be an integrated circuit with signal processing capability, such as a CPU. The apparatus for the session management network element may be realized by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or, one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementations can be combined.

An embodiment of the present application also provides a communication system, including the communication device as shown in FIG. 9 and the communication device as shown in FIG. 10.

An embodiment of the present application also provides a communication system, including the access network device shown in FIG. 11 and the session management network element shown in FIG. 12.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

The various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions. The general-purpose processor may be a microprocessor. Alternatively, the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. achieve.

In one or more exemplary designs, the aforementioned functions described in this application can be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions can be stored on a computer-readable medium, or transmitted on the computer-readable medium in the form of one or more instructions or codes. Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special computer. For example, such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other program code media that can be read by general-purpose or special computers, or general-purpose or special processors. In addition, any connection can be appropriately defined as a computer-readable medium, for example, if the software is from a website, server, or other remote source through a coaxial cable, fiber optic computer, twisted pair, or digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless and microwave are also included in the definition of computer-readable media. The said disks and discs include compressed disks, laser disks, optical discs, digital versatile discs (English: Digital Versatile Disc, abbreviated as: DVD), floppy disks and Blu-ray discs. Disks usually copy data with magnetism. Discs usually use lasers to copy data optically. The combination of the above can also be contained in a computer readable medium.

Those skilled in the art should be aware that, in one or more of the foregoing examples, the functions described in this application can be implemented by hardware, software, firmware, or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium. The computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Although the application has been described in combination with specific features and embodiments, it is obvious that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary descriptions of the application as defined by the appended claims, and are deemed to cover any and all modifications, changes, combinations or equivalents within the scope of the application. Obviously, those skilled in the art can make various changes and modifications to the application without departing from the scope of the application. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these modifications and variations.

Claims

A resource allocation method, characterized in that it comprises:

Receiving synchronization scheduling indication information associated with a terminal device, where the synchronization scheduling indication information is used to indicate that the terminal device needs to synchronize air interface scheduling resources with other terminal devices in the user group in which the terminal device is located;

According to the synchronization scheduling indication information, the air interface scheduling resource is allocated to the terminal device.
The method according to claim 1, wherein when the synchronization scheduling indication information associated with the terminal device in the user group has not been received,

The allocating the air interface scheduling resource to the terminal device according to the synchronization scheduling indication information includes:

Determine the identity of the user group according to the synchronization scheduling indication information;

According to the identifier of the user group, the air interface scheduling resource is allocated to the terminal device from the air interface resource corresponding to the user group.
The method of claim 2, further comprising:

Receiving the identifier of the user group;

According to the identifier of the user group, the air interface resource is allocated to the user group.
The method according to claim 2 or 3, further comprising:

Determine the first reserved resource in the air interface resources, where the first reserved resource and the air interface scheduling resource allocated to the terminal device are in the same or adjacent time unit, and the first reserved resource is used for allocation To other terminal devices in the user group.
The method according to claim 1, wherein when the synchronization scheduling indication information associated with the terminal device in the user group has been received;

The allocating the air interface scheduling resource to the terminal device according to the synchronization scheduling indication information includes:

From the second reserved resources, the air interface scheduling resources are allocated to the terminal device, and the second reserved resources are the same as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group. Adjacent time unit.
The method according to any one of claims 1 to 5, wherein the synchronization scheduling indication information is determined according to the identity of the user group.
A resource allocation method, characterized in that it comprises:

Receiving an identifier of a user group, the user group including at least two terminal devices;

Determine synchronization scheduling indication information according to the identifier of the user group, where the synchronization scheduling indication information is used to indicate that terminal devices in the user group need to synchronize air interface scheduling resources with other terminal devices in the user group;

Sending the synchronization scheduling indication information to the access network device.
The method according to claim 7, wherein the receiving the identifier of the user group comprises:

Receiving an identifier of the user group from a first terminal device, where the first terminal device belongs to the user group; or;

Receiving the identifier of the user group from the application function network element.
A communication device, characterized in that it comprises:

A receiving unit, configured to receive synchronization scheduling indication information associated with a terminal device, where the synchronization scheduling indication information is used to indicate that the terminal device needs to synchronize air interface scheduling resources with other terminal devices in the user group where the terminal device is located;

The allocation unit is configured to allocate the air interface scheduling resource to the terminal device according to the synchronization scheduling indication information.
9. The apparatus according to claim 9, wherein when the receiving unit has not received the synchronization scheduling indication information associated with the terminal equipment in the user group;

The allocation unit is specifically configured to determine the identity of the user group according to the synchronization scheduling indication information; according to the identity of the user group, allocate the terminal device from the air interface resources corresponding to the user group Air interface scheduling resources.
10. The device according to claim 10, wherein the receiving unit is further configured to receive an identifier of the user group;

The allocation unit is further configured to allocate the air interface resource to the user group according to the identifier of the user group.
The apparatus according to claim 10 or 11, wherein the apparatus further comprises a determining unit, configured to determine a first reserved resource in the air interface resources, and the first reserved resource is different from the one allocated to the The air interface scheduling resources of the terminal device are in the same or adjacent time unit, and the first reserved resource is used for allocating to other terminal devices in the user group.
9. The apparatus according to claim 9, wherein when the receiving unit has received the synchronization scheduling indication information associated with the terminal equipment in the user group;

The allocation unit is specifically configured to allocate the air interface scheduling resource to the terminal device from a second reserved resource, and the second reserved resource is related to the one or more terminals that have been allocated to the user group The air interface scheduling resources of the equipment are in the same or adjacent time unit.
The apparatus according to any one of claims 9-13, wherein the synchronization scheduling indication information is determined according to the identity of the user group.
A communication device, characterized in that it comprises:

A receiving unit, configured to receive an identifier of a user group, the user group including at least two terminal devices;

The determining unit is configured to determine synchronization scheduling indication information according to the identifier of the user group, where the synchronization scheduling indication information is used to indicate the air interface of the terminal device in the user group that needs to be synchronized with other terminal devices in the user group Scheduling resources;

The sending unit is configured to send the synchronization scheduling indication information to the access network device.
The device according to claim 15, wherein the receiving unit is specifically configured to:

Receiving an identifier of the user group from a first terminal device, where the first terminal device belongs to the user group; or;

Receiving the identifier of the user group from the application function network element.
A communication system, characterized in that it includes a session management network element and an access network device;

The session management network element is configured to receive an identifier of a user group, the user group includes at least two terminal devices; according to the identifier of the user group, determine synchronization scheduling indication information, the synchronization scheduling indication information is used to indicate all The terminal devices in the user group need air interface scheduling resources that are synchronized with other terminal devices in the user group; and the synchronization scheduling instruction associated with the first terminal device in the user group is sent to the access network device information;

The access network device is configured to allocate the air interface scheduling resource to the first terminal device according to the synchronization scheduling indication information.
The system according to claim 17, wherein when the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group;

The access network device is specifically configured to determine the identity of the user group according to the synchronization scheduling indication information; according to the identity of the user group, it is the first terminal from the air interface resource corresponding to the user group The device allocates the air interface scheduling resource.
The system according to claim 18, wherein the access network device is further configured to receive the identifier of the user group; according to the identifier of the user group, the air interface resource is allocated to the user group.
The system according to claim 18 or 19, wherein the access network device is further configured to determine a first reserved resource among the air interface resources, and the first reserved resource is different from the one allocated to the The air interface scheduling resources of the first terminal device are in the same or adjacent time unit, and the first reserved resource is used for allocating to other terminal devices in the user group.
The system according to claim 17, wherein when the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group;

The access network device is specifically configured to allocate the air interface scheduling resource to the first terminal device from a second reserved resource, and the second reserved resource is the same as one that has been allocated to the user group Or air interface scheduling resources of multiple terminal devices are in the same or adjacent time units.
The system according to any one of claims 17-21, wherein the synchronization scheduling indication information is determined according to the identity of the user group.
The system according to any one of claims 17-22, wherein the session management network element is used to receive the identifier of the user group, specifically comprising:

Used to receive the identifier of the user group from the first terminal device; or;

It is used to receive the identifier of the user group from the application function network element.
A resource allocation method, characterized in that it comprises:

The session management network element receives the identifier of the user group, the user group including at least two terminal devices;

The session management network element determines synchronization scheduling indication information according to the identifier of the user group, and the synchronization scheduling indication information is used to indicate that the terminal equipment in the user group needs to be synchronized with other terminal equipment in the user group. Air interface scheduling resources;

Sending, by the session management network element, the synchronization scheduling indication information associated with the first terminal device in the user group to an access network device;

The access network device allocates the air interface scheduling resource to the first terminal device according to the synchronization scheduling indication information.
The method according to claim 24, wherein when the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group;

The access network device is specifically configured to determine the identity of the user group according to the synchronization scheduling indication information; according to the identity of the user group, it is the first terminal from the air interface resource corresponding to the user group The device allocates the air interface scheduling resource.
The method according to claim 24, wherein when the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group;

The access network device is specifically configured to allocate the air interface scheduling resource to the first terminal device from a second reserved resource, and the second reserved resource is the same as one that has been allocated to the user group Or air interface scheduling resources of multiple terminal devices are in the same or adjacent time units.
A computer-readable storage medium, wherein the computer-readable storage medium stores a program, and when the program is called by a processor, the method according to any one of claims 1 to 6 is executed.
A computer-readable storage medium, wherein the computer-readable storage medium stores a program, and when the program is called by a processor, the method according to claim 7 or 8 is executed.
A computer program, characterized in that when the program is called by a processor, the method according to any one of claims 1-6 is executed.
A computer program, characterized in that when the program is called by a processor, the method according to claim 7 or 8 is executed.