CN114175826A

CN114175826A - Resource allocation method, device and system

Info

Publication number: CN114175826A
Application number: CN201980098816.3A
Authority: CN
Inventors: 朱方园; 李岩; 刘建宁
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-30
Filing date: 2019-12-30
Publication date: 2022-03-11
Also published as: WO2021134347A1

Abstract

The embodiment of the application provides a resource allocation method, a device and a system. The method comprises the following steps: receiving synchronous scheduling indication information associated with terminal equipment, wherein the synchronous scheduling indication information is used for indicating that the terminal equipment needs to be synchronized with other terminal equipment in a user group where the terminal equipment is located to schedule resources at an air interface; and allocating the air interface scheduling resources to the terminal equipment according to the synchronous scheduling indication information. In the scheme, the same or adjacent time unit air interface scheduling resources are distributed to the terminal equipment in the user group according to the synchronous scheduling indication information, so that the network side can receive data sent by different terminal equipment in the user group in the shortest possible time delay, and the quality of data processing is improved.

Description

Resource allocation method, device and system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for resource allocation.

Background

In some application scenarios, a plurality of terminal devices need to cooperatively execute a certain service, and the terminal devices need to transmit data to a network side, and the network side performs comprehensive processing according to the data reported by each terminal device. Taking a concert scene as an example, a leading vocal, a bass hand, a guitar hand, a drummer and the like are taken as terminal devices, the terminal devices belong to the same mixed sound group (also called as a user group), the terminal devices need to respectively send the sound data generated by the terminal devices to a network side through a mobile network, and then the network side performs mixed sound processing according to the collected sound data and deterministic time (deterministic time), so that the final processing result is output and returned to the terminal devices.

In the same mixing group, since 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 the data sent by one or some terminal devices do not arrive within the certain time range, the mixing process cannot be executed, and the network side discards the data received from other terminal devices, which finally results in mixing failure.

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

Disclosure of Invention

The embodiment of the application provides a resource allocation method, a device and a system, which are used for optimizing time delay in deterministic media transmission so as to improve the quality of data processing.

In a first aspect, an embodiment of the present application provides a resource allocation method, including: receiving synchronous scheduling indication information associated with terminal equipment, wherein the synchronous scheduling indication information is used for indicating that the terminal equipment needs to be synchronized with other terminal equipment in a user group where the terminal equipment is located to schedule resources at an air interface; and allocating the air interface scheduling resources to the terminal equipment according to the synchronous scheduling indication information.

In the above scheme, the same or adjacent time unit air interface scheduling resources are allocated to the terminal devices in the user group according to the synchronous scheduling indication information, so that the network side can receive data sent by different terminal devices in the user group within a time delay as short as possible, and the quality of data processing is improved.

In a possible implementation method, when the synchronous scheduling indication information associated with the terminal devices in the user group is not received; the allocating, according to the synchronous scheduling indication information, the air interface scheduling resource to the terminal device includes: determining the identification of the user group according to the synchronous scheduling indication information; and allocating the air interface scheduling resources to the terminal equipment from the air interface resources corresponding to the user group according to the identifier of the user group.

In one possible implementation, receiving an identification of the user group; and allocating the air interface resources to the user group according to the identifier of the user group.

In a possible implementation method, a first reserved resource in the air interface resource is determined, where the first reserved resource is in the same time unit or in an adjacent time unit with an air interface scheduling resource allocated to the terminal device, and the first reserved resource is used for being allocated to other terminal devices in the user group.

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

In a possible implementation method, the synchronous scheduling indication information is determined according to an identifier 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, wherein the user group comprises at least two terminal devices; determining synchronous scheduling indication information according to the identifier of the user group, wherein the synchronous scheduling indication information is used for indicating that terminal equipment in the user group needs to be synchronized with other terminal equipment in the user group to schedule resources at an air interface; and sending the synchronous scheduling indication information to access network equipment.

In the above scheme, the session management network element may determine the synchronous scheduling indication information based on the identifier of the user group, and send the synchronous scheduling indication information to the access network device, and the access network device may allocate the air interface scheduling resources of the same or adjacent time units to the terminal devices in the user group according to the synchronous scheduling indication information, so that the network side may receive data sent by different terminal devices in the user group within a time delay as short as possible, which is helpful for improving the quality of data processing.

In one possible implementation method, the receiving the identifier of the user group includes: receiving an identification of the user group from a first terminal device, the first terminal device belonging to the user group; or; receiving an identification of the user group from an application function network element.

In a third aspect, an embodiment of the present application provides a resource allocation method, including: the method comprises the steps that terminal equipment sends an identification of a user group, and the terminal equipment in the user group needs air interface scheduling resources synchronous with other terminal equipment in the user group; and the terminal equipment receives air interface scheduling resources from the access network.

In a fourth aspect, an embodiment of the present application provides a communication apparatus, which may be an access network device and may also be a chip for an access network device. The apparatus has the functionality to implement the first aspect or embodiments of the first aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fifth aspect, an embodiment of the present application provides a communication apparatus, where the apparatus may be a session management network element, and may also be a chip for the session management network element. The apparatus having functionality to implement the second aspect or embodiments of the second aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a sixth aspect, an embodiment of the present application provides a communication apparatus, which may be a terminal device, and may also be a chip for the terminal device. The apparatus has the function of implementing the third aspect or each embodiment of the third aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a seventh aspect, an embodiment of the present application provides a communication apparatus, including a processor and a memory; the memory is configured to store computer-executable instructions, and when the apparatus is operated, the processor executes the computer-executable instructions stored by the memory to cause the apparatus to perform the method as described in the first to third aspects or the embodiments of the first to third aspects.

In an eighth aspect, an embodiment of the present application provides a communication apparatus, including means or means (means) for performing each step of the first to third aspects or the embodiments of the first to third aspects.

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

In a tenth aspect, an embodiment of the present application provides a communication apparatus, including a processor, configured to be connected to a memory, and configured to call a program stored in the memory, so as to execute the method in the first aspect to the third aspect or in each embodiment of the first aspect to the third aspect. The memory may be located within the device or external to the device. And the processor includes one or more.

In an eleventh aspect, this application further provides a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the processor to perform the method described in the foregoing first to third aspects or the embodiments of the first to third aspects.

In a twelfth aspect, embodiments of the present application further provide a computer program product including instructions, which when run on a computer, cause the computer to perform the method described in the foregoing first aspect to third aspect, or the embodiments of the first aspect to the third aspect.

In a thirteenth aspect, an embodiment of the present application further provides a chip system, including: a processor configured to perform the method according to the first to third aspects or the embodiments of the first to third aspects.

In a fourteenth aspect, an embodiment of the present application further 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, where the user group includes at least two terminal devices; determining synchronous scheduling indication information according to the identifier of the user group, wherein the synchronous scheduling indication information is used for indicating that terminal equipment in the user group needs to be synchronized with other terminal equipment in the user group to schedule resources at an air interface; sending the synchronous scheduling indication information associated with the first terminal device in the user group to the access network device; and the access network equipment is used for allocating the air interface scheduling resource to the first terminal equipment according to the synchronous scheduling indication information.

In a possible implementation method, when the access network device does not receive the synchronous scheduling indication information associated with the terminal devices in the user group; the access network device is specifically configured to determine an identifier of the user group according to the synchronous scheduling indication information; and allocating the air interface scheduling resource for the first terminal equipment from the air interface resource corresponding to the user group according to the identifier of the user group.

In a possible implementation method, the access network device is further configured to receive an identifier of the user group; and allocating the air interface resources to the user group according to the identifier of 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 resource, where the first reserved resource is in the same time unit or in an adjacent time unit as an air interface scheduling resource allocated to the first terminal device, and the first reserved resource is used for being allocated to other terminal devices in the user group.

In a possible implementation method, when the access network device receives the synchronous scheduling indication information associated with the terminal devices 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, where the second reserved resource is in the same time unit or in an adjacent time unit as the air interface scheduling resource already allocated to one or more terminal devices in the user group.

In a possible implementation method, the session management network element is configured to receive an identifier of a user group, and specifically includes: for receiving an identification of the user group from the first terminal device; or; for receiving an identification of said user group from an application function network element.

In a fifteenth aspect, an embodiment of the present application further provides a resource allocation method, including: a session management network element receives an identifier of a user group, wherein the user group comprises at least two terminal devices; the session management network element determines synchronous scheduling indication information according to the identifier of the user group, wherein the synchronous scheduling indication information is used for indicating that terminal equipment in the user group needs to be synchronized with air interface scheduling resources of other terminal equipment in the user group; the session management network element sends the synchronous scheduling indication information associated with the first terminal equipment in the user group to access network equipment; and the access network equipment allocates the air interface scheduling resource to the first terminal equipment according to the synchronous scheduling indication information.

Drawings

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

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

FIG. 2 is a schematic diagram of the components involved in a professional audio production communications system;

fig. 3 is a schematic diagram of a plurality of terminal devices generating a delay when transmitting uplink data;

fig. 4 is a schematic flowchart of a resource allocation method according to an embodiment of the present application;

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

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

fig. 6 is a schematic diagram illustrating an access network device allocating synchronized air interface scheduling resources to terminal devices in a user group;

fig. 7 is a schematic flowchart of another resource allocation method according to an embodiment of the present application;

fig. 8 is a schematic flowchart of another resource allocation method according to an embodiment of the present application;

fig. 9 is a schematic diagram of a communication device according to an embodiment of the present application;

fig. 10 is a schematic diagram of another communication device provided in the embodiment of the present application;

fig. 11 is a schematic diagram of an access network device according to an embodiment of the present application;

fig. 12 is a schematic diagram of a session management network element according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in further detail with reference to the accompanying drawings. The particular methods of operation in the method embodiments may also be applied to apparatus embodiments or system embodiments. In the description of the embodiments of the present application, the term "plurality" means two or more unless otherwise specified.

Fig. 1A 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, which are a terminal device part, a Data Network (DN) and an operator network part. The functions of some of the network elements will be briefly described below.

Wherein the operator network may comprise one or more of the following network elements: an Authentication Server Function (AUSF) Network element, a Network open Function (NEF) Network element, a Policy Control Function (PCF) Network element, a Unified Data Management (UDM) Network element, a Unified Data Repository (UDR), a Network storage Function (NRF) Network element, an Application Function (AF) Network element, an access and mobility management Function (AMF) Network element, a Session Management Function (SMF) Network element, a Radio Access Network (RAN), and a user plane Function (user plane, UPF) Network element, and the like. In the operator network described above, the parts other than the radio access network part may be referred to as core network parts.

A terminal device (terminal device), which is a device with a wireless transceiving function, can be deployed on land, including indoors or outdoors, and is handheld or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiving function, a Virtual Reality (VR) terminal, an Augmented Reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in home (smart home), a User Equipment (UE), a media device (e.g., an audio device with a communication device installed therein, such as a guitar, an audio stand drum, a microphone, etc.), and the like.

The terminal device may establish a connection with the carrier network through an interface (e.g., N1, etc.) provided by the carrier network, and use data and/or voice services provided by the carrier network. The terminal device may also access the DN via an operator network, use operator services deployed on the DN, and/or services provided by a third party. The third party may be a service party other than the operator network and the terminal device, and may provide services such as data and/or voice for the terminal device. The specific expression form of the third party may be determined according to an actual application scenario, and is not limited herein.

The RAN is a sub-network of the operator network and is an implementation system between the service node and the terminal device in the operator network. The terminal device is to access the operator network, first through the RAN, and then may be connected to a service node of the operator network through the RAN. A RAN device is a device that provides a terminal device with a wireless communication function, and is also called an access network device. RAN equipment includes, but is not limited to: next generation base station (G node B, gNB), evolved node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (e.g., home evolved node B, or home node B, HNB), Base Band Unit (BBU), transmission point (TRP), Transmission Point (TP), mobile switching center, etc. in 5G.

The AMF network element is responsible for mobility management of users, including mobility state management, user temporary identity distribution, user authentication and authorization and the like.

The SMF network element has the functions of session management, execution of control strategies issued by PCF, selection of UPF, allocation of UE Internet Protocol (IP) addresses, establishment, modification and release of load bearing, Quality of Service (QoS) control and the like.

And the UPF network element supports the functions of interconnecting the PDU session and a data network, routing and forwarding packets, detecting data packets and the like.

And the UDM network element is mainly responsible for functions of managing subscription data, user access authorization and the like.

The UDR stores and retrieves subscription data, strategy data, public architecture data and the like; for UDM, PCF and NEF to obtain relevant data. The UDR needs to have different data access authentication mechanisms aiming at different types of data, such as subscription data and strategy data, so as to ensure the security of data access; the UDR is to be able to return a failure response carrying a suitable cause value for an illegal servicing operation or data access request.

The NEF network element mainly supports a network capability opening function and opens network capability and service to the outside; third generation partnership project (3 GPP) NFs publish functions and events to other NFs through NEFs. The capability and events of NF openness can be securely opened to third party applications. NEF stores/retrieves structured data using the standardized interface (nurr) of the Unified Data Repository (UDR). And translating the exchange information of the AF and the exchange information of the internal network function.

The AF network element is used for providing a certain application layer service to the UE, and when providing the service to the UE, the AF has requirements on a QoS policy and a charging policy and needs to notify a network. Meanwhile, the AF also needs application-related information fed back by the core network.

The PCF network element is mainly responsible for performing policy control functions such as charging, QoS bandwidth guarantee, mobility management, UE policy decision, etc. for the session and service stream levels. In the framework, PCFs connected to the AMF and SMF correspond to AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management), respectively, and may not be the same PCF entity in an actual deployment scenario.

The NRF network element can be used for providing a network element discovery function and providing 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: it is primarily responsible for authenticating a user to determine whether the user or device is allowed to access the network.

The DN is a network outside the operator network, the operator network can access a plurality of DNs, and the DN can deploy a plurality of services and provide services such as data and/or voice for the terminal device. For example, the DN is a private network of a certain intelligent factory, a sensor installed in a workshop of the intelligent factory can be a terminal device, a control server of the sensor is deployed in the DN, and the control server can provide services for the sensor. The sensor can communicate with the control server, obtain the instruction of the control server, transmit the sensor data gathered to the control server, etc. according to the instruction. For another example, the DN is an internal office network of a company, the mobile phone or computer of the employee of the company may be a terminal device, and the mobile phone or computer of the employee may access information, data resources, and the like on the internal office network of the company.

Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 in FIG. 1A are interface serial numbers. The meaning of these interface sequence numbers can be referred to as that defined in the 3GPP standard protocol, and is not limited herein.

As shown in fig. 1B, the schematic diagram is a 5G network architecture based on a point-to-point interface, where introduction of functions of a network element may refer to introduction of functions of a corresponding network element in fig. 1A, and details are not described again. The main differences between fig. 1B and fig. 1A are: the interfaces between the various network elements in fig. 1B are point-to-point interfaces, rather than serviced interfaces.

In the architecture shown in fig. 1B, the interface names and functions between the network elements are as follows:

1) n7: the interface between the PCF and the SMF may be used to send a Protocol Data Unit (PDU) session granularity and a service data stream granularity control policy.

2) N15: the interface between PCF and AMF can be used to send down UE strategy and access control relative strategy.

3) N5: the interface between the AF and the PCF may be used for application service request issue and network event report.

4) N4: the interface between the SMF and the UPF may be used for transmitting information between the control plane and the user plane, including controlling the sending of forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and reporting information for the user plane.

5) N11: the interface between the SMF and the AMF may be used to transfer PDU session tunnel information between the RAN and the UPF, to transfer control messages to the UE, to transfer radio resource control information to the RAN, and so on.

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

7) N1: the interface between the AMF and the UE may be used to deliver QoS control rules, etc. to the UE.

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

9) N10: the interface between the SMF and the UDM may be used for the SMF to acquire the subscription data related to session management from the UDM, and for the SMF to register the current session related information of the UE with the UDM.

10) N35: and the interface between the UDM and the UDR can be used for the UDM to acquire the user subscription data information from the UDR.

11) N36: the interface between the PCF and the UDR may be used for the PCF to obtain policy related subscription data and application data related information from the UDR.

12) N12: the interface between the AMF and the AUSF can be used for initiating an authentication process from the AMF to the AUSF, wherein the SUCI can be carried as a subscription identifier;

13) n13: the interface between the UDM and the AUSF may be used for the AUSF to obtain the user authentication vector from the UDM to execute the authentication procedure.

It is to be understood that the above network elements or functions may be network elements in a hardware device, or may be software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). Optionally, the network element or the function may be implemented by one device, or may be implemented by multiple devices together, or may be a functional module in one device, which is not specifically limited in this 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 open function network element, and the user plane network element in this embodiment may be the AMF, the SMF, the PCF, the AF, the RAN, the NEF, and the UPF in fig. 1A or fig. 1B, respectively, or may be network elements having the functions of the AMF, the SMF, the PCF, the AF, the RAN, the NEF, and the UPF in a future communication such as a 6th generation (6G) network, which is not limited in this embodiment of the present application. For convenience of description, in the embodiments of the present application, a mobility management network element, a session management network element, a policy control network element, an application function network element, an access network device, a network open function network element, and a user plane network element are respectively exemplified by the AMF, SMF, PCF, AF, RAN, NEF, and UPF. Further, in the embodiment of the present application, the terminal device is simply referred to as UE.

A wireless audio system is a system that transmits audio signals using radio waves instead of a wired manner. Wireless audio systems typically include wireless microphone systems and wireless listen-back systems, as well as systems that wirelessly transmit audio over long distances in certain situations. Wireless audio systems have become an essential subsystem in today's large performances.

The wireless audio system can be applied to scenes such as large concerts, concerts and the like, and has high requirements on end-to-end delay (latency), transmission period, safety reliability and sound quality.

Fig. 2 is a schematic diagram of components involved in a professional audio production communication system. In one aspect, the system includes a wireless audio input, represented herein as a microphone. Audio is captured at an audio source and sent over a wireless connection to a mixing processing server, which may perform mixing, transcoding, equalization or other processing tasks of several audio inputs. The result of the audio processing is sent via a wireless connection to an output device, which may be a speaker, a general purpose device equipped with headphones, or other device.

For example, during an actual performance, it is common for multiple input devices to generate sound source data, such as a musician, guitar, drummer, and lead song, during a concert performance, where each of their input devices is essential sound source data for the entire performance. All the sound source data are sent to a sound mixing processing server at the network side through the access network equipment to be subjected to sound mixing or sound mixing processing. When different UEs send uplink data, the access network device schedules independently, allocates different air interface scheduling resources to different UEs (where the air interface scheduling resources include time resources and frequency resources, and the time resources may be represented by time units such as slots (slots) and mini-slots), and the audio mixing processing server performs audio mixing processing on input different sound source data, and then sends the audio mixed effect to the return-to-the-ear device of each performer through the access network device, so that each performer can hear the effect of the live performance. Generally, the mixing processing server needs to wait until uplink data of UEs in the same mixing group (also referred to as a user group) arrives before mixing. That is, in the same mixing group, the network side processes the received data according to a deterministic time, so it must be limited that the data sent by each UE needs to arrive within a certain time range, otherwise, once the data of a certain UE or some UEs do not arrive within the certain time range, the mixing process cannot be performed, and the network side will discard the data received from other UEs, eventually resulting in a mixing failure.

In the existing mechanism, when multiple UEs belonging to the same mixing group need to send uplink data through access network equipment, uplink data needs to be transmitted according to air interface scheduling resources allocated by the access network equipment. Time resources in air interface scheduling resources allocated to different UEs in the same mixing group may be in time units far apart, which results in a large delay difference between uplink data sent by different UEs and arriving at a mixing processing server. That is, the existing mechanism cannot guarantee the deterministic transmission delay of the uplink data sent by the UEs in the same mixing group, which may cause the mixing failure of the mixing processing server.

Fig. 3 is a schematic diagram illustrating a time delay generated when a plurality of UEs transmit uplink data. Assuming that the UE1 and the UE2 are already time-synchronized (the time of the two is the same), when the uplink data of the UE1 and the uplink data of the UE2 are transmitted, although the hardware device of the UE1 and the hardware device of the UE2 can ensure that each generates data at the same time point, the time units allocated by the RAN device to the UE1 and the UE2 may not be the same and far apart, so during the transmission over the air interface, the uplink data of the UE1 may be earlier than the uplink data of the UE2, and therefore, the uplink data of the UE1 and the uplink data of the UE2 are not scheduled in the same or adjacent time unit although they are transmitted through the same RAN device. This results in a large delay between the uplink data of the UE1 and the uplink data of the UE 2. In addition, when the subsequent RAN equipment transmits uplink data of UE1 and UE2, a transmission path on the network side may also introduce additional delay, and delay between the uplink data of UE1 and the uplink data of UE2 received by the mixer equipment may accumulate, resulting in further increase of delay.

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. The method is on the RAN side, and may be performed by the RAN device or a component (e.g., a chip, a circuit, etc.) for the RAN device; on the network side, this may be performed by the SMF or a component (e.g., chip, circuit, etc.) for the SMF. For convenience of explanation, the RAN device and the SMF will be described as examples to perform the method.

The method comprises the following steps:

at step 401, the SMF receives an identification of a user group.

The identity of the user group is used to indicate at least two UEs. Alternatively, the user group may also be referred to as a synchronous scheduling service group, a synchronous scheduling group, or the like.

Any UE in the user group needs air interface scheduling resources synchronized with other UEs in the user group. Or, it is understood that the UEs in the user group have a requirement of synchronous air interface scheduling resources. Or that the UEs within the user group have a requirement for synchronized scheduling among each other. The synchronized air interface scheduling resources refer to that the air interface scheduling resources allocated to the UEs in the same user group are in the same or adjacent time units.

In this embodiment of the application, the time unit may be a slot (slot) or a mini-slot (mini-slot), which is described here in a unified manner and will not be described in detail later.

As one implementation, the SMF may receive an identification of a user group from a first UE, the first UE belonging to the user group. That is, the first UE requests allocation of air interface scheduling resources, and carries the identifier of the user group to which the first UE belongs.

As yet another implementation, the SMF may receive a list of UEs and an identification of a user group from the AF. That is, the AF requests to allocate air interface scheduling resources to each UE in the UE list, and simultaneously carries the identifier of the user group to which each UE in the UE list belongs.

Step 402, the SMF determines synchronous scheduling indication information according to the identifier of the user group, where the synchronous scheduling indication information is used to indicate that the UE in the user group needs to synchronize with other UEs in the user group.

As an implementation manner, the SMF may pre-configure a corresponding relationship between the identifier of each user group and the synchronous scheduling indication information. After the SMF acquires the identifier of the user group, the SMF may determine the corresponding synchronous scheduling indication information according to the identifier of the user group.

As another implementation manner, the SMF may pre-configure a correspondence between the identification list of the user group and the synchronous scheduling indication information. The list of identities of user groups comprises identities of at least one user group. If the user group identification obtained by the SMF belongs to the list, the SMF may determine the corresponding synchronous scheduling indication information.

As another implementation manner, the SMF may also obtain, through another network element (e.g., a PCF network element), a corresponding relationship between the identifier of the user group and the synchronous scheduling indication information, which is not limited in this embodiment of the present application. It should be noted that UEs in the same user group may correspond to the same synchronous scheduling indication information.

In step 403, the SMF sends the synchronized scheduling indication information to the RAN. Accordingly, the RAN may receive the synchronized scheduling indication information.

In step 404, the RAN allocates air interface scheduling resources to the UE according to the synchronous scheduling indication information. Wherein, the air interface scheduling resource is used for UE to send uplink data.

It should be noted that, in step 401, if the SMF receives the identifier of the user group from the first UE, in step 404, the RAN specifically allocates air interface scheduling resources for the first UE. If the SMF receives the identifier of the user group from the AF in step 401, the RAN specifically allocates air interface scheduling resources to all UEs in the user group in sequence in step 404. 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, the SMF sends the synchronous scheduling indication information to the RAN multiple times, where each synchronous scheduling indication information is associated with each UE in the user group, and the RAN allocates an air interface scheduling resource to each UE according to the synchronous scheduling indication information.

The RAN may allocate air interface scheduling resources to the UE, for example:

in the first method, the RAN allocates air interface scheduling resources for the UE from idle resources according to the synchronous scheduling indication information.

For example, the RAN determines that the UE is the first UE in the user group requesting to allocate the air interface scheduling resource according to the received synchronous scheduling indication information, or determines that the synchronous scheduling indication information associated with the UE in the user group has not been received before, the RAN may allocate the air interface scheduling resource according to a normal procedure, for example, allocate the air interface scheduling resource to the UE according to a resource allocation manner in the prior art, that is, the RAN determines a time unit for uplink data scheduling of the UE according to its resource allocation condition, and sends a resource scheduling assignment (Grant) to the UE, so as to notify the UE to send the uplink data in a certain time unit. And the RAN locally stores the corresponding relation between the synchronous scheduling indication information and the scheduling resources. And the subsequent UE sends the uplink data to the RAN according to the air interface scheduling resource distributed by the RAN. After allocating the air interface scheduling resources to the UE, the RAN may also allocate reserved resources to other UEs in the user group, where the reserved resources are in the same time unit or in an adjacent time unit as the air interface scheduling resources already allocated to the UE. I.e. the reserved resources are applicable to other UEs within the user group.

It should be noted that, when the RAN determines that the UE is the first UE in the user group requesting to allocate the air interface scheduling resource or the RAN determines that the synchronous scheduling indication information associated with the UE in the user group has not been received before, the RAN determines that the synchronous scheduling indication information associated with the UE in the user group has not been received before a certain time range (for example, taking a concert scene as an example, a master song, a bass hand, a guitar hand, a drummer and the like have air interface scheduling synchronization requirements as the UEs in the user group, and a time range from the beginning to the end of a concert and the like). Based on the implementation manner, the air interface scheduling resources for transmitting data by a plurality of devices (such as media devices) in a time range can be scheduled and allocated uniformly, so that the time delay in deterministic transmission can be reduced.

For another example, the RAN determines, according to the received synchronous scheduling indication information, that the UE is not the first UE in the user group that requests to allocate the air interface scheduling resource, or the RAN determines that the synchronous scheduling indication information associated with the UE in the user group is received before, and then the RAN may allocate the air interface scheduling resource to the UE from the reserved resource.

It should be noted that, when the RAN determines that the UE is not the first UE in the user group requesting to allocate the air interface scheduling resource or the RAN determines that the synchronous scheduling indication information associated with the UE in the user group is received before, the RAN determines that the synchronous scheduling indication information associated with the UE in the user group is received before within a certain time range (for example, taking a concert scene as an example, a master song, a bass hand, a guitar hand, a drummer and the like have air interface scheduling synchronization requirements as the UEs in the user group, and the like within a time range from the beginning to the end of a concert).

In the second method, the RAN allocates air interface scheduling resources to the UE from air interface resources corresponding to the user group according to the synchronous scheduling indication information.

The air interface resource may be a fixed scheduling resource configured on the RAN and corresponding to the user group, 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 a registration procedure.

For example, the RAN determines that the UE is the first UE in the user group requesting to allocate the air interface scheduling resource according to the received synchronous scheduling indication information, or determines that the synchronous scheduling indication information associated with the UE in the user group has not been received before, the RAN may allocate the air interface scheduling resource for the UE from the air interface resource corresponding to the user group, that is, the RAN determines a time unit for uplink data scheduling of the UE according to its resource allocation condition, and sends a resource scheduling assignment (Grant) to the UE, and notifies the UE to send the uplink data in a certain time unit. And the subsequent UE sends the uplink data to the RAN according to the resources allocated by the RAN. After allocating the air interface scheduling resource to the UE, the RAN may also allocate a reserved resource to other UEs in the user group, where the reserved resource is a resource in the air interface resource and is in the same time unit as or adjacent to the resource already allocated to the UE. I.e. the reserved resources are applicable to other UEs within the user group.

It should be noted that, when the RAN determines that the UE is the first UE in the user group requesting to allocate the air interface scheduling resource or the RAN determines that the synchronous scheduling indication information associated with the UE in the user group has not been received before, the RAN determines that the synchronous scheduling indication information associated with the UE in the user group has not been received before in a certain time range (for example, taking a concert scene as an example, a master song, a bass hand, a guitar hand, a drummer and the like have air interface scheduling synchronization requirements as the UEs in the user group, and the like in a time range from the beginning to the end of a concert).

As an example, UE1 and UE2 belong to the same user group. For example, if the UE1 is the first UE in the user group requesting to allocate an air interface scheduling resource, the RAN may allocate an air interface scheduling resource for the UE1 from the idle resource or the air interface resource corresponding to the user group, and simultaneously allocate a reserved resource, where the reserved resource is in the same time unit as or adjacent to the scheduling resource allocated to the UE 1. Subsequently, the UE2 requests to allocate air interface scheduling resources, and the RAN may allocate air interface scheduling resources to the UE2 on the reserved resources. Therefore, the scheduling resources in the same or adjacent time units are distributed to the UE in the same user group.

For example, referring to fig. 5A and 5B, a schematic diagram of scheduling resources for allocating an empty port is shown. 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 for UE1 and UE2 are in adjacent time units.

Referring to fig. 5A, assuming that the UE1 is a first UE in a user group requesting to allocate an air interface scheduling resource, the RAN allocates an air interface scheduling resource to the UE1 from an idle resource (for the first method) or an air interface resource corresponding to the user group (for the second method), and then allocates a reserved resource from the idle resource (for the first method) or the air interface resource corresponding to the user group (for the second method), where the reserved resource is in the same time unit as the air interface scheduling resource allocated to the UE1, and at this time, the reserved resource includes the air interface scheduling resource allocated to the UE2 shown in fig. 5A and the reserved resource shown in fig. 5A. Subsequently, UE2 in the user group (i.e., the second UE in the user group requesting to allocate the air interface scheduling resource) requests to allocate the air interface scheduling resource, then the RAN allocates the air interface scheduling resource for UE2 from the above reserved resources, allocates the air interface scheduling resource for UE2, as shown in fig. 5A, and is in the same time unit as the allocation of the air interface scheduling resource for UE1, and at this time, the remaining reserved resource is as shown in fig. 5A.

Referring to fig. 5B, assuming that the UE1 is a first UE in a user group requesting to allocate an air interface scheduling resource, the RAN allocates an air interface scheduling resource to the UE1 from an idle resource (for the first method) or an air interface resource corresponding to the user group (for the second method), and then allocates a reserved resource from the idle resource (for the first method) or the air interface resource corresponding to the user group (for the second method), where the reserved resource is in the same time unit or adjacent to the time unit of the air interface scheduling resource allocated to the UE1, and at this time, the reserved resource includes the air interface scheduling resource allocated to the UE2 shown in fig. 5B and the reserved resource shown in fig. 5B. Subsequently, UE2 in the user group (i.e., the second UE in the user group requesting to allocate the air interface scheduling resource) requests to allocate the air interface scheduling resource, then the RAN allocates the air interface scheduling resource for UE2 from the above reserved resources, allocates the air interface scheduling resource for UE2 as shown in fig. 5B, and is located in a time unit adjacent to the time unit in which the air interface scheduling resource is allocated for UE1, where the remaining reserved resources are shown in fig. 5B.

Optionally, if, in step 401, the SMF receives an identifier of a user group from the first UE, in step 403, the SMF may further send, to the RAN, an identifier of a PDU session of the first UE, where the PDU session is a session associated with a synchronization service executed by the first UE in the user group. Further, in step 404, the RAN allocates an empty scheduling resource for the PDU session of the first UE according to the synchronous scheduling indication information.

Optionally, in step 401, if the SMF receives the identifier of the user group and the UE list from the AF, in step 403, the SMF may further determine, according to the UE list, PDU sessions respectively corresponding to each UE in the UE list, and send, to the RAN, the identifier of the PDU session respectively corresponding to each UE in the UE list, where the SMF sends, to the RAN, the identifier of the PDU session respectively corresponding to each UE in the UE list multiple times according to the number of UEs in the UE list, and the PDU session is a session associated with a synchronization service executed by the UE in the user group. Further, in step 404, the RAN allocates an air interface scheduling resource to the PDU sessions respectively corresponding to each UE in the UE list according to the synchronous scheduling indication information.

For example, UE1 and UE2 belong to the same user group, and fig. 5A and 5B are schematic diagrams of RAN allocating air interface scheduling resources for UE1 and UE 2. Subsequently, when UE1 and UE2 send uplink data, referring to fig. 6, the RAN may schedule the uplink data sent by UE1 and UE2 respectively, and if the RAN schedules the uplink data of UE1 and UE2 in the same time unit or in adjacent time when allocating air interface scheduling resources, it may be ensured that the uplink data of UE1 and UE2 are simultaneously transmitted to the network side as much as possible, so that when the network performs mixing processing, the uplink data of UE1 and UE2 may be received simultaneously as much as possible, thereby helping to ensure the effect and quality of the mixing processing.

In the above scheme, the network Side (SMF) may determine the synchronous scheduling indication information of the RAN side based on the identifier of the user group, and the RAN may allocate the same or neighboring time unit air interface scheduling resources to the UEs in the user group according to the synchronous scheduling indication information, so that the network side may receive data sent by different UEs in the user group within as short a time delay as possible, which is helpful to improve the quality of data processing.

The flow shown in fig. 4 will be described with reference to specific examples.

Fig. 7 is a schematic flow chart of another resource allocation method according to the embodiment of the present application. In the scheme, the UE sends the identifier of the user group where the UE is located to the network. The network can distribute the synchronous scheduling indication information based on the identification of the user group and send the synchronous scheduling indication information to the RAN, so that the RAN can perform special resource scheduling for the UE according to the synchronous scheduling indication information, namely perform resource synchronous scheduling on the UE in the same user group.

The precondition of the scheme is that: for example, the group identifier may be a user group identifier (UE group ID) (also may be referred to as an identifier of a user group) or a service group identifier (service group ID) (also may be referred to as an identifier of a service group), and the group identifier is used to identify a specific group of UEs, where each UE in the group has the same service type (e.g., media service), or the same service requirement (e.g., a synchronization requirement), and the like.

Optionally, the method for the UE to acquire the group identifier includes, but is not limited to, the following two methods:

a) in the registration process, the network generates a group identifier according to subscription data of the UE (e.g., generating a group identifier according to a service type subscribed by the UE), or the subscription data of the UE includes the group identifier to which the UE belongs, and then the network sends the group identifier to the UE in a registration accept message.

b) And locally configuring the group identification of the UE on the UE.

Taking the group identifier as the user group identifier as an example, the method comprises the following steps:

in step 701, the UE sends a first request to the AMF. Accordingly, the AMF may receive the first request.

The first request contains an identification of the PDU session (PDU session ID) and a user group identification, the identification of the PDU session being 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 sent the first request in this step 701 belongs to the user group.

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

At step 702, the AMF sends a second request to the SMF. Accordingly, the SMF may receive the second request.

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

And step 703, the SMF determines the synchronous scheduling indication information according to the user group identifier.

The implementation method for the SMF to determine the synchronous 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 is not described herein again.

It should be noted that, if the SMFs corresponding to PDU sessions of different UEs in the same user group are different, after receiving user group identifiers sent by different UEs, the synchronous scheduling indication information determined by different SMFs according to the same user group identifier is the same. It can be understood that different SMFs are configured with the same correspondence between the subscriber group identifier and the synchronous scheduling identifier, and therefore, different SMFs can determine the same synchronous scheduling indication information according to the same subscriber group identifier.

Optionally, in this process, the SMF may further update the session management related policy with the PCF.

At step 704, the SMF sends a second response to the AMF. Accordingly, the AMF may receive the second response.

The second response carries the synchronous scheduling indication information and also carries the identification of the PDU session. For example, the second response may carry an N2session management container (N2 SM container), and N2 SM container carries the above-mentioned isochronous scheduling indication information and the identification of the PDU session. The second response may also carry an N1 session management container (N1 SM container), and the N1 SM container carries the identification of the PDU session and the first response.

The AMF sends a third request to the RAN, step 705. Accordingly, the RAN may receive the third request.

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

In step 706, the RAN allocates the air interface scheduling resource to the UE according to the synchronous scheduling indication information and the PDU session identifier.

Wherein, the identification of the PDU session is used for indicating the PDU session needing to allocate the air interface scheduling resource.

The method for the RAN to allocate the air interface scheduling resource for the PDU session of the UE according to the synchronous scheduling indication information and the identification of the PDU session may be:

in the first method, the RAN allocates air interface scheduling resources for the UE from idle resources according to the synchronous scheduling indication information and the PDU session identifier.

For example, the RAN determines that the UE is the first UE in the user group requesting to allocate the air interface scheduling resource according to the received synchronous scheduling indication information, or the RAN determines that the synchronous scheduling indication information associated with the UE in the user group has not been received before, the RAN may allocate the air interface scheduling resource according to a normal procedure, for example, allocate the air interface scheduling resource for the PDU session of the UE from the idle resources according to a resource allocation manner in the prior art, that is, the RAN determines a time unit for uplink data scheduling of the UE according to its own resource allocation condition, and sends a resource scheduling assignment (Grant) to the UE, so as to notify the UE to send uplink data of the PDU session in a certain time unit. And the RAN locally stores the corresponding relation between the synchronous scheduling indication information and the scheduling resources. And the subsequent UE sends the uplink data to the RAN according to the air interface scheduling resource distributed by the RAN. After allocating the air interface scheduling resources for the PDU session of the UE, the RAN may also reserve resources for the allocation of the PDU session of other UEs within the user group, the reserved resources being in the same or adjacent time units as the air interface scheduling resources already allocated to the PDU session of the UE. That is, the reserved resources are applicable to PDU sessions of other UEs within the user group. For example, UE1 and UE2 belong to the same user group, and UE1 needs to synchronize air-interface scheduling resources with UE 2. Referring to fig. 5A and 5B, a schematic diagram of scheduling resources for allocating an empty port is shown. 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 for UE1 and UE2 are in adjacent time units.

For another example, the RAN determines, according to the received synchronous scheduling indication information, that the UE is not the first UE in the user group requesting to allocate the null scheduling resource, or the RAN determines that the synchronous scheduling indication information associated with the UE in the user group is received before, and then the RAN may allocate the null scheduling resource for the PDU session of the UE from the reserved resource.

And secondly, distributing air interface scheduling resources for the UE from air interface resources corresponding to the user group by the RAN according to the synchronous scheduling indication information and the PDU session identifier.

For example, the RAN determines that the UE is the first UE in the user group requesting to allocate the air interface scheduling resource according to the received synchronous scheduling indication information, or the RAN determines that the synchronous scheduling indication information associated with the UE in the user group has not been received before, the RAN may allocate the air interface scheduling resource for the PDU session of the UE from the air interface resource corresponding to the user group, that is, the RAN determines the time unit of uplink data scheduling of the UE according to the resource allocation condition of the RAN, and sends a resource scheduling assignment (Grant) to the UE, and notifies the UE to send the uplink data in a certain time unit. And the subsequent UE sends the uplink data to the RAN according to the resources allocated by the RAN. After allocating the air interface scheduling resource for the PDU session of the UE, the RAN may also allocate a reserved resource for the PDU session of other UEs in the user group, where the reserved resource is a resource in the air interface resource and is in the same time unit or an adjacent time unit as the air interface scheduling resource already allocated to the PDU session of the UE. That is, the reserved resources are applicable to PDU sessions of other UEs within the user group. For example, UE1 and UE2 belong to the same user group, and UE1 needs to synchronize air-interface scheduling resources with UE 2. Referring to fig. 5A and 5B, a schematic diagram of scheduling resources for allocating an empty port is shown. 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 for UE1 and UE2 are in adjacent time units.

It should be noted that, when the RAN determines that the UE is the first UE in the user group requesting to allocate the air interface scheduling resource or the RAN determines that the synchronous scheduling indication information associated with the UE in the user group is received before, the RAN determines that the synchronous scheduling indication information associated with the UE in the user group is not received before within a certain time range (for example, taking a concert scene as an example, a master song, a bass hand, a guitar hand, a drummer and the like have air interface scheduling synchronization requirements as the UEs in the user group, and the like within a time range from the beginning to the end of a concert).

It should be noted that, in the embodiment of the present application, different UEs in the same user group access the same RAN. Thus, even if the SMFs corresponding to PDU sessions of different UEs in the same user group are different, in step 703, the different SMFs determine the same synchronous scheduling indication information according to the same user group identifier, so that the RAN may allocate synchronous air interface scheduling resources to different UEs in the same user group.

In step 707, the RAN sends the air interface scheduling resource to the UE. Accordingly, the UE may receive the air interface scheduling resource.

The air interface scheduling resource is a scheduling resource for transmitting uplink data at the air interface side allocated by the RAN to the UE. The UE may perform local configuration according to the air interface scheduling resource sent by the RAN, and the subsequent UE sends the uplink data to the RAN according to the air interface scheduling resource allocated by the RAN.

In this step 707, the RAN may also send the above-described N1 SM container to the UE. After receiving the N1 SM container, the UE may acquire the first response and the identification of the PDU session therein.

In step 708, the RAN sends a third response to the AMF, which may be received by the AMF accordingly.

This step 708 is optional.

As an implementation scheme, the above embodiment may be performed in a PDU session establishment procedure after the UE registers to the network. In the PDU Session Establishment procedure, the first Request may be a PDU Session Establishment Request (PDU Session Establishment Request), the second Request may be a PDU Session Establishment Request (Nsmf _ PDU _ create _ mcontext Request), the first response may be a PDU Session Establishment Accept message (PDU Session Establishment Accept), the second response may be a PDU Session Establishment Request response (Nsmf _ PDU _ create _ mcontext response), the third Request may be an N2Session Request (N2Session Request), and the third response may be an N2Session response (N2Session response).

As an implementation solution, the above embodiment may be performed in a PDU session modification procedure after the UE registers to the network. In the PDU Session Modification procedure, the first Request may be a PDU Session Modification Request (PDU Session Modification Request), the second Request may be a PDU Session update Request (Nsmf _ PDU _ update _ smcontext Request), the first response may be a PDU Session Modification Request response message (PDU Session Modification ack), the second response may be a PDU Session update response (Nsmf _ PDU _ update _ smcontext response), the third Request may be an N2Session Request (N2Session Request), and the third response may be an N2Session response (N2Session response).

For example, UE1 and UE2 belong to the same user group, and fig. 5A and 5B are schematic diagrams of RAN allocating air interface scheduling resources for UE1 and UE 2. Subsequently, when UE1 and UE2 send uplink data, referring to fig. 6, the RAN may schedule the uplink data sent by UE1 and UE2 respectively, and if the RAN schedules the uplink data of UE1 and UE2 in the same time unit or in adjacent time when allocating air interface scheduling resources, it may be ensured that the uplink data of UE1 and UE2 are simultaneously transmitted to the network side as much as possible, so that when the network performs mixing processing, the uplink data of UE1 and UE2 may be received simultaneously as much as possible, thereby helping to ensure the effect and quality of the mixing processing. According to the scheme, the UE carries the user group identification in the first request, the network Side (SMF) can determine the synchronous scheduling indication information of the RAN side based on the user group identification, and the RAN can allocate the air interface scheduling resources in the same or adjacent time units to the UE in the user group according to the synchronous scheduling indication information, so that the network side can receive data sent by different UEs in the user group in as short a time delay as possible, and the quality of data processing is improved.

Fig. 8 is a schematic flow chart of another resource allocation method according to the embodiment of the present application. In the scheme, after the UE has established a session, the AF sends a request to the network, where the request carries a user group identifier, and thus, the network may determine synchronous scheduling indication information based on the user group identifier and then send the synchronous scheduling indication information to the RAN. In this way, the RAN can perform special resource scheduling for the UE, that is, perform resource synchronous scheduling for UEs in the same user group.

b) And locally configuring the group identification of the UE on the UE.

in step 801, the AF sends a policy update request (Npcf _ PolicyAuthorization update request) to the PCF. Accordingly, the PCF may receive the policy update request.

For example, the AF may send the policy update request to the PCF via 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 identities of one or more UEs, and the identities of the UEs in the UE list belong to the user group.

Step 802, the PCF triggers a PDU session related Policy update procedure (PCF initiated SMF Policy Association Modification), in which the PCF triggers a PDU session update of the SMF for the UE indicated by the UE list, and the PCF sends the user group identity and the UE list to the SMF.

Step 803, the SMF determines the synchronous scheduling indication information according to the user group identifier, and determines the PDU session identifier corresponding to each UE indicated by the UE list.

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

For example, the SMF may send the synchronization scheduling indication information and the identification of the PDU session to the AMF through the Namf _ Communication _ N1N2MessageTransfer request.

At step 805, the AMF sends an N2session request (N2session request) to the RAN. Accordingly, the RAN may receive the N2session request.

The N2Session request includes N2 SM container and N1 SM container, where N2 SM container includes isochronous scheduling indication information and an identifier of a PDU Session, and N1 SM container carries the identifier of the PDU Session and a PDU Session Modification response message (PDU Session Modification ack).

In step 806, the RAN allocates an empty scheduling resource to the UE according to the synchronous scheduling indication information and the PDU session identifier.

The RAN allocates the empty scheduling resource for the PDU session of the UE according to the synchronous scheduling indication information and the identification of the PDU session, which may refer to the related description of the embodiment corresponding to fig. 7 and is not described herein again.

It should be noted that, in the embodiment of the present application, different UEs in the same user group access the same RAN. Thus, even if the SMFs corresponding to the PDU sessions of different UEs in the same user group are different, in step 803, the different SMFs determine the same synchronous scheduling indication information according to the same user group identifier, so that the RAN may allocate synchronous air interface scheduling resources to different UEs in the same user group.

In step 807, the RAN sends the air interface scheduling resource to the UE. Accordingly, the UE may receive the air interface scheduling resource.

In this step 807, the RAN may also send the above-described N1 SM container to the UE. After receiving the N1 SM container, the UE may acquire the PDU session modification response message and the identification of the PDU session therein.

In step 808, the RAN sends an N2session response to the AMF, and accordingly, the AMF may receive the N2session response.

This step 808 is optional.

According to the scheme, the AF carries the user group identification in the strategy updating request, the network Side (SMF) can determine the synchronous scheduling indication information of the RAN side based on the user group identification, and the RAN can allocate the air interface scheduling resources in the same or adjacent time units to the UE in the user group according to the synchronous scheduling indication information, so that the network side can receive data sent by different UEs in the user group in as short a time delay as possible, and the quality of data processing is improved.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. It is to be understood that the above-described implementation of each network element includes, in order to implement the above-described functions, a corresponding hardware structure and/or software module for performing each function. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software, with the exemplary elements and algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is to be understood that, in the foregoing embodiments of the methods, the steps or operations implemented by the terminal device may also be implemented by a component (e.g., a chip or a circuit) configured in the terminal device, the steps or operations implemented by the access network device may also be implemented by a component (e.g., a chip or a circuit) configured in the access network device, the steps or operations implemented by the session management network element may also be implemented by a component (e.g., a chip or a circuit) configured in the session management network element.

Fig. 9 is a schematic diagram of a communication device according to an embodiment of the present application. The apparatus is configured to implement the steps performed by the corresponding access network device in the foregoing method embodiment, as shown in fig. 9, the apparatus 900 includes a receiving unit 910, a sending unit 920, and an allocating unit 930. Optionally, a determining unit 940 is further included. A receiving unit 910, configured to receive synchronous scheduling indication information associated with a terminal device, where the synchronous scheduling indication information is used to indicate that the terminal device needs to synchronize with an air interface scheduling resource of another terminal device in a user group where the terminal device is located; an allocating unit 930, configured to allocate the air interface scheduling resource to the terminal device according to the synchronous 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 synchronous scheduling indication information associated with the terminal devices in the user group; the allocating unit 930 is specifically configured to determine the identifier of the user group according to the synchronous scheduling indication information; and allocating the air interface scheduling resources to the terminal equipment from the air interface resources corresponding to the user group according to the identifier of 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 the air interface resource to the user group according to the identifier of the user group.

In a possible implementation method, the determining unit 940 is configured to determine a first reserved resource in the air interface resource, where the first reserved resource is located in a same time unit or an adjacent time unit as an air interface scheduling resource allocated to the terminal device, and the first reserved resource is used for being allocated to other terminal devices in the user group.

In a possible implementation method, when the receiving unit 910 receives the synchronous scheduling indication information associated with the terminal devices in the user group; the allocating unit 930 is specifically configured to allocate the air interface scheduling resource to the terminal device from a second reserved resource, where the second reserved resource and the air interface scheduling resource that has been allocated to one or more terminal devices in the user group are in the same or an adjacent time unit.

It is to be understood that the above units may also be referred to as modules, circuits, etc., and the above units may be provided independently or may be integrated wholly or partially.

In some possible implementations, the receiving unit 910 and the sending unit 920 may also be implemented by a transceiving unit, or the receiving unit 910 and the sending unit 920 may also be collectively referred to as a transceiving unit. The allocating unit 930 and the determining unit 940 may be implemented by a processing unit, or the allocating unit 930 and the determining unit 940 may be collectively referred to as a processing unit.

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

Optionally, the communication device 900 may further include a storage unit, which is used for storing data or instructions (also referred to as codes or programs), and the above units may interact with or be coupled to the storage unit to implement corresponding methods or functions. For example, the processing unit may read data or instructions in the storage unit, so that the communication device implements the method in the above-described embodiments.

Fig. 10 is a schematic diagram of a communication device according to an embodiment of the present application. The apparatus is configured to implement the steps performed by the corresponding session management network element in the foregoing method embodiment, as shown in fig. 10, the apparatus 1000 includes a receiving unit 1010, a sending unit 1020, and a determining unit 1030. A receiving unit 1010, configured to receive an identifier of a user group, where the user group includes at least two terminal devices; a determining unit 1030, configured to determine, according to the identifier of the user group, synchronous scheduling indication information, where the synchronous scheduling indication information is used to indicate that a terminal device in the user group needs to use an air interface scheduling resource that is synchronous with other terminal devices in the user group; a sending unit 1020, configured to send the synchronization scheduling indication information to an access network device.

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, where the first terminal device belongs to the user group; or; receiving an identification of the user group from an application function network element.

In some possible implementations, the receiving unit 1010 and the transmitting unit 1020 may also be implemented by a transceiver, or the receiving unit 1010 and the transmitting unit 1020 may also be collectively referred to as a transceiver. The above-mentioned determining unit 1030 may be implemented by a processing unit.

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

Optionally, the communication device 1000 may further include a storage unit, which is used for storing data or instructions (also referred to as codes or programs), and the above units may interact with or be coupled to the storage unit to implement corresponding methods or functions. For example, the processing unit may read data or instructions in the storage unit, so that the communication device implements the method in the above-described embodiments.

It should be understood that the division of the units in the above apparatus is only a division of logical functions, and the actual implementation may be wholly or partially integrated into one physical entity or may be physically separated. And the units in the device can be realized in the form of software called by the processing element; or may be implemented entirely in hardware; part of the units can also be realized in the form of software called by a processing element, and part of the units can be realized in the form of hardware. For example, each unit may be a processing element separately set up, or may be implemented by being integrated into a chip of the apparatus, or may be stored in a memory in the form of a program, and a function of the unit may be called and executed by a processing element of the apparatus. In addition, all or part of the units can be integrated together or can be independently realized. The processing element described herein may in turn be a processor, which may be an integrated circuit having signal processing capabilities. In the implementation process, the steps of the method or the units above may be implemented by integrated logic circuits of hardware in a processor element or in a form called by software through the processor element.

In one example, the units in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), or a combination of at least two of these Integrated Circuit formats. As another example, when a Unit in a device may be implemented in the form of a Processing element scheduler, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of invoking programs. As another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

The above unit for receiving (e.g., receiving unit) is an interface circuit of the apparatus for receiving a signal from other apparatus. For example, when the device is implemented in the form of a chip, the receiving unit is an interface circuit for the chip to receive signals from other chips or devices. The above unit for transmitting (e.g., the transmitting unit) is an interface circuit of the apparatus for transmitting a signal to other apparatuses. For example, when the device is implemented in the form of a chip, the transmitting unit is an interface circuit for the chip to transmit signals to other chips or devices.

Fig. 11 is a schematic structural diagram of an access network device according to an embodiment of the present application. The access network device is used for realizing the operation of the access network device in the above embodiment. As shown in fig. 11, the access network device includes: antenna 1110, rf 1120, and baseband 1130. The antenna 1110 is connected to a radio 1120. In the uplink direction, the rf device 1120 receives information transmitted by the terminal device through the antenna 1110, and transmits the information transmitted 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 the information to the radio frequency device 1120, and the radio frequency device 1120 processes the information of the terminal device and sends the information to the terminal device through the antenna 1110.

The baseband device 1130 may include one or more processing elements 1131, including, for example, a host CPU and other integrated circuits, and may also include an interface 1133. In addition, the baseband device 1130 may further include a storage element 1132, where the storage element 1132 is used to store programs and data; the interface 1133 is used for exchanging information with the radio frequency device 1120, and is, for example, a Common Public Radio Interface (CPRI). The above means for the access network apparatus may be located on the baseband means 1130, for example, the above means for the access network apparatus may be a chip on the baseband means 1130, the chip comprising at least one processing element and interface circuitry, wherein the processing element is configured to perform the steps of any of the methods performed by the above access network apparatus, and the interface circuitry is configured to communicate with other devices. In one implementation, the unit of the access network device for implementing each step in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for the access network device includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method executed by the access network device in the above method embodiment. The memory elements may be memory elements on the same chip as the processing element, i.e. on-chip memory elements, or may be memory elements on a different chip than the processing element, i.e. off-chip memory elements.

In another implementation, the unit of the access network device for implementing the steps in the above method may be configured as one or more processing elements, which are disposed on the baseband device, where the processing elements may be integrated circuits, for example: 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 may be integrated together to form a chip.

The units of the access network device for implementing the steps of the above method may 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 a storage element can be integrated in the chip, and the method executed by the access network equipment is realized in the form that the processing element calls the stored program of the storage element; or, at least one integrated circuit may be integrated in the chip, for implementing the method executed by the above access network device; alternatively, the above implementation modes may be combined, the functions of the partial units are implemented in the form of a processing element calling program, and the functions of the partial units are implemented in the form of an integrated circuit.

It can be seen that the above apparatus for an access network device may comprise at least one processing element and interface circuitry, wherein the at least one processing element is configured to perform the method performed by any one of the access network devices provided by the above method embodiments. The processing element may: namely, calling the program stored in the storage element to execute part or all of the steps executed by the access network equipment; it is also possible to: that is, some or all of the steps performed by the access network device are performed by way of integrated logic circuitry of hardware in the processor element in combination with instructions; of course, some or all of the steps performed by the above access network device may also be performed in combination with the first manner and the second manner.

The processing elements herein, like those described above, 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 microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. The storage element may be a memory or a combination of a plurality of storage elements.

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

The method performed by the session management network element in the above embodiments may 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, and the processor 1210 executes the method executed by the session management network element in the above method embodiment by calling a program in a memory. The processor here may be an integrated circuit with signal processing capabilities, such as a CPU. The apparatus for a session management network element may be implemented 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. Alternatively, the above implementations may be combined.

An embodiment of the present application further provides a communication system, including the communication apparatus shown in fig. 9 and the communication apparatus shown in fig. 10.

An embodiment of the present application further 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, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The various illustrative logical units and circuits described in this application may be implemented or operated upon by design of a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

In one or more exemplary designs, the functions described herein may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media that facilitate transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store program code in the form of instructions or data structures and which can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Additionally, any connection is properly termed a computer-readable medium, and, thus, is included if the software is transmitted from a website, server, or other remote source over a coaxial cable, fiber optic computer, twisted pair, Digital Subscriber Line (DSL), or wirelessly, e.g., infrared, radio, and microwave. The disk (disk) and Disc (Disc) include compact Disc, laser Disc, optical Disc, Digital Versatile Disc (DVD), floppy disk and blu-ray Disc, where the disk usually reproduces data magnetically, and the Disc usually reproduces data optically with laser. Combinations of the above may also be included in the computer-readable medium.

Those skilled in the art will recognize that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include such modifications and variations.

Claims

A method for resource allocation, comprising:

receiving synchronous scheduling indication information associated with terminal equipment, wherein the synchronous scheduling indication information is used for indicating that the terminal equipment needs to be synchronized with other terminal equipment in a user group where the terminal equipment is located to schedule resources at an air interface;

and allocating the air interface scheduling resources to the terminal equipment according to the synchronous scheduling indication information.
The method of claim 1, wherein when the synchronous scheduling indication information associated with terminal devices within the user group has not been received,

the allocating, according to the synchronous scheduling indication information, the air interface scheduling resource to the terminal device includes:

determining the identification of the user group according to the synchronous scheduling indication information;

and allocating the air interface scheduling resources to the terminal equipment from the air interface resources corresponding to the user group according to the identifier of the user group.
The method of claim 2, further comprising:

receiving an identification of the user group;

and allocating the air interface resources to the user group according to the identifier of the user group.
The method of claim 2 or 3, further comprising:

and determining a first reserved resource in the air interface resources, wherein the first reserved resource and the air interface scheduling resource allocated to the terminal equipment are in the same or adjacent time unit, and the first reserved resource is used for being allocated to other terminal equipment in the user group.
The method of claim 1, wherein when the synchronous scheduling indication information associated with terminal devices within the user group is received;

the allocating, according to the synchronous scheduling indication information, the air interface scheduling resource to the terminal device includes:

and allocating the air interface scheduling resources to the terminal equipment from second reserved resources, wherein the second reserved resources and the air interface scheduling resources allocated to one or more terminal equipments in the user group are in the same or adjacent time units.
The method of any of claims 1-5, wherein the synchronized scheduling indication information is determined based on an identification of the user group.
A method for resource allocation, comprising:

receiving an identifier of a user group, wherein the user group comprises at least two terminal devices;

determining synchronous scheduling indication information according to the identifier of the user group, wherein the synchronous scheduling indication information is used for indicating that terminal equipment in the user group needs to be synchronized with other terminal equipment in the user group to schedule resources at an air interface;

and sending the synchronous scheduling indication information to access network equipment.
The method of claim 7, wherein receiving the identification of the user group comprises:

receiving an identification of the user group from a first terminal device, the first terminal device belonging to the user group; or;

receiving an identification of the user group from an application function network element.
A communications apparatus, comprising:

a receiving unit, configured to receive synchronous scheduling indication information associated with a terminal device, where the synchronous scheduling indication information is used to indicate that the terminal device needs to synchronize with an air interface scheduling resource of another terminal device in a user group in which the terminal device is located;

and the allocation unit is used for allocating the air interface scheduling resources to the terminal equipment according to the synchronous scheduling indication information.
The apparatus of claim 9, wherein when the receiving unit has not received the synchronous scheduling indication information associated with terminal devices within the user group;

the allocation unit is specifically configured to determine an identifier of the user group according to the synchronous scheduling indication information; and allocating the air interface scheduling resources to the terminal equipment from the air interface resources corresponding to the user group according to the identifier of the user group.
The apparatus of claim 10, wherein the receiving unit is further configured to receive an identification 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 of claim 10 or 11, wherein the apparatus further includes a determining unit, configured to determine a first reserved resource in the air interface resources, where the first reserved resource is in a same time unit or an adjacent time unit as an air interface scheduling resource allocated to the terminal device, and the first reserved resource is used for being allocated to other terminal devices in the user group.
The apparatus of claim 9, wherein when the receiving unit receives the synchronous scheduling indication information associated with terminal devices within the user group;

the allocating unit is specifically configured to allocate the air interface scheduling resource to the terminal device from a second reserved resource, where the second reserved resource is in the same time unit or an adjacent time unit as the air interface scheduling resource allocated to one or more terminal devices in the user group.
The apparatus of any of claims 9-13, wherein the synchronized scheduling indication information is determined based on an identification of the user group.
A communications apparatus, comprising:

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

a determining unit, configured to determine synchronous scheduling indication information according to the identifier of the user group, where the synchronous scheduling indication information is used to indicate that a terminal device in the user group needs to use an air interface scheduling resource that is synchronous with other terminal devices in the user group;

and a sending unit, configured to send the synchronous scheduling indication information to an access network device.
The apparatus as claimed in claim 15, wherein said receiving unit is specifically configured to:

receiving an identification of the user group from a first terminal device, the first terminal device belonging to the user group; or;

receiving an identification of the user group from an application function network element.
A communication system comprising 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, where the user group includes at least two terminal devices; determining synchronous scheduling indication information according to the identifier of the user group, wherein the synchronous scheduling indication information is used for indicating that terminal equipment in the user group needs to be synchronized with other terminal equipment in the user group to schedule resources at an air interface; sending the synchronous scheduling indication information associated with the first terminal device in the user group to the access network device;

and the access network equipment is used for allocating the air interface scheduling resource to the first terminal equipment according to the synchronous scheduling indication information.
The system of claim 17, wherein when the access network device has not received the synchronized scheduling indication information associated with the terminal devices in the user group;

the access network device is specifically configured to determine an identifier of the user group according to the synchronous scheduling indication information; and allocating the air interface scheduling resource for the first terminal equipment from the air interface resource corresponding to the user group according to the identifier of the user group.
The system of claim 18, wherein the access network device is further configured to receive an identification of the user group; and allocating the air interface resources to the user group according to the identifier of the user group.
The system of claim 18 or 19, wherein the access network device is further configured to determine a first reserved resource in the air interface resources, where the first reserved resource is in a same time unit or an adjacent time unit as an air interface scheduling resource allocated to the first terminal device, and the first reserved resource is used for being allocated to other terminal devices in the user group.
The system of claim 17, wherein when the access network device receives the synchronous scheduling indication information associated with the terminal devices 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, where the second reserved resource is in the same time unit or in an adjacent time unit as the air interface scheduling resource already allocated to one or more terminal devices in the user group.
The system of any of claims 17-21, wherein the synchronized scheduling indication information is determined based on an identification of the user group.
The system according to any of claims 17 to 22, wherein the session management network element is configured to receive an identification of a user group, and specifically includes:

for receiving an identification of the user group from the first terminal device; or;

for receiving an identification of said user group from an application function network element.
A method for resource allocation, comprising:

a session management network element receives an identifier of a user group, wherein the user group comprises at least two terminal devices;

the session management network element determines synchronous scheduling indication information according to the identifier of the user group, wherein the synchronous scheduling indication information is used for indicating that terminal equipment in the user group needs to be synchronized with air interface scheduling resources of other terminal equipment in the user group;

the session management network element sends the synchronous scheduling indication information associated with the first terminal equipment in the user group to access network equipment;

and the access network equipment allocates the air interface scheduling resource to the first terminal equipment according to the synchronous scheduling indication information.
The method of claim 24, wherein when the access network device has not received the synchronized scheduling indication information associated with terminal devices within the user group;

the access network device is specifically configured to determine an identifier of the user group according to the synchronous scheduling indication information; and allocating the air interface scheduling resource for the first terminal equipment from the air interface resource corresponding to the user group according to the identifier of the user group.
The method of claim 24, wherein when the access network device receives the synchronous scheduling indication information associated with terminal devices within 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, where the second reserved resource is in the same time unit or in an adjacent time unit as the air interface scheduling resource already allocated to one or more terminal devices in the user group.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a program which, when called by a processor, performs the method of any of claims 1-6.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a program which, when called by a processor, performs the method of claim 7 or 8.
A computer program, characterized in that the method of any of claims 1-6 is performed when said program is called by a processor.
A computer program, characterized in that the method of claim 7 or 8 is performed when said program is called by a processor.