Resource allocation method, device and system

Abstract

The embodiments of the present application provide a resource allocation method, device, and system. The method includes: receiving synchronization scheduling indication information associated with a terminal device, the synchronization scheduling indication information being used to indicate that the terminal device needs to synchronize air interface scheduling resources with other terminal devices in the user group where the terminal device is located; and allocating the air interface scheduling resources to the terminal device based on the synchronization scheduling indication information. In this solution, air interface scheduling resources of the same or adjacent time units are allocated to the terminal devices in the user group based on the synchronization scheduling indication information, so that the network side can receive data sent by different terminal devices in the user group within the shortest possible delay, which helps to improve the quality of data processing.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a resource allocation method, device, and system. Background Art

[0002] In some application scenarios, multiple terminal devices need to collaborate to perform a service. These terminal devices need to send their data to the network, which then performs comprehensive processing based on the data reported by each terminal device. For example, at a concert, the lead singer, bassist, guitarist, and drummer, among other terminal devices, belong to the same mixing group (also known as a user group). Each of these devices needs to send its own sound data to the network via the mobile network. The network then mixes the collected sound data in a deterministic manner, outputting the final processing results and returning them to each terminal device.

[0003] In the same mixing group, since the network side processes the received data according to deterministic time, the data sent by each terminal device must arrive within a certain time range. Otherwise, if the data sent by one or some terminal devices does not arrive within the determined time range, the mixing processing cannot be performed, and the network side will discard the data received from other terminal devices, eventually causing mixing failure.

[0004] Therefore, how to optimize the latency in deterministic media transmission to improve the quality of data processing is a problem that needs to be solved. Summary of the Invention

[0005] Embodiments of the present application provide a resource allocation method, apparatus, and system for optimizing the latency in deterministic media transmission to improve the quality of data processing.

[0006] In the first aspect, an embodiment of the present application provides a resource allocation method, comprising: receiving synchronization scheduling indication information associated with a terminal device, the synchronization scheduling indication information being used to indicate that the terminal device needs to synchronize air interface scheduling resources with other terminal devices in the user group where the terminal device is located; and allocating the air interface scheduling resources to the terminal device according to the synchronization scheduling indication information.

[0007] In the above scheme, air interface scheduling resources of the same or adjacent time units are allocated to 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 the shortest possible delay, which helps to improve the quality of data processing.

[0008] In a possible implementation method, when the synchronous scheduling indication information associated with the terminal device in the user group has not been received; the air interface scheduling resources are allocated to the terminal device based on the synchronous scheduling indication information, including: determining the identifier of the user group based on the synchronous scheduling indication information; and allocating the air interface scheduling resources to the terminal device from the air interface resources corresponding to the user group based on the identifier of the user group.

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

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

[0011] In a possible implementation method, when the synchronization scheduling indication information associated with the terminal device in the user group is received; the air interface scheduling resources are allocated to the terminal device based on the synchronization scheduling indication information, including: allocating the air interface scheduling resources to the terminal device from the second reserved resources, and the second reserved resources are in the same or adjacent time unit as the air interface scheduling resources already allocated to one or more terminal devices in the user group.

[0012] In a possible implementation method, the synchronization scheduling indication information is determined according to an identifier of the user group.

[0013] In the second aspect, an embodiment of the present application provides a resource allocation method, including: receiving an identifier of a user group, the user group including at least two terminal devices; determining synchronization scheduling indication information based on the identifier of the user group, the synchronization scheduling indication information being used to indicate that the terminal devices in the user group need to synchronize air interface scheduling resources with other terminal devices in the user group; and sending the synchronization scheduling indication information to an access network device.

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

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

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

[0017] In a fourth aspect, embodiments of the present application provide a communications device, which may be an access network device or a chip for an access network device. The device has the functions of implementing the first aspect or each embodiment of the first aspect. The functions may be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0018] In a fifth aspect, embodiments of the present application provide a communications device, which may be a session management network element (SME) or a chip for a SME. The device implements the functions of the aforementioned second aspect or each embodiment of the second aspect. The functions may be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0019] In a sixth aspect, embodiments of the present application provide a communications device, which may be a terminal device or a chip for a terminal device. The device has the functions of implementing the third aspect or each embodiment of the third aspect described above. The functions may be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0020] In the seventh aspect, an embodiment of the present application provides a communication device, comprising a processor and a memory; the memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory to enable the device to execute the method of the above-mentioned first to third aspects, or each embodiment of the first to third aspects.

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

[0022] In a ninth aspect, an embodiment of the present application provides a communication device, comprising a processor and an interface circuit, wherein the processor is configured to communicate with another device via the interface circuit and execute the method of any of the first to third aspects, or any of the embodiments of the first to third aspects. The processor may comprise one or more.

[0023] In a tenth aspect, an embodiment of the present application provides a communication device, comprising a processor, configured to be connected to a memory and configured to call a program stored in the memory to execute the method of the first to third aspects, or each embodiment of the first to third aspects, described above. The memory may be located within or outside the device. The processor may include one or more processors.

[0024] In the eleventh aspect, an embodiment of the present application also provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is run on a computer, the processor executes the method described in the above-mentioned first to third aspects, or the embodiments of the first to third aspects.

[0025] In the twelfth aspect, an embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the above-mentioned first to third aspects, or the embodiments of the first to third aspects.

[0026] In the thirteenth aspect, an embodiment of the present application further provides a chip system, comprising: a processor for executing the method described in the above-mentioned first to third aspects, or each embodiment of the first to third aspects.

[0027] In the fourteenth aspect, an embodiment of the present application also provides a communication system, including: a session management network element and an access network device; the session management network element is used to receive an identifier of a user group, the user group including at least two terminal devices; based on the identifier of the user group, synchronization scheduling indication information is determined, the synchronization scheduling indication information is used to indicate that the terminal devices in the user group need to synchronize air interface scheduling resources with other terminal devices in the user group; the synchronization scheduling indication information associated with the first terminal device in the user group is sent to the access network device; the access network device is used to allocate the air interface scheduling resources to the first terminal device based on the synchronization scheduling indication information.

[0028] In a possible implementation method, when the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically used to determine the identifier of the user group based on the synchronization scheduling indication information; and according to the identifier of the user group, allocate the air interface scheduling resources to the first terminal device from the air interface resources corresponding to the user group.

[0029] In a possible implementation method, the access network device is further configured to receive an identifier of the user group; and allocate the air interface resources to the user group according to the identifier of the user group.

[0030] In a possible implementation method, the access network device is also used to determine a first reserved resource in the air interface resources, where the first reserved resource and the air interface scheduling resource allocated to the first terminal device are in the same or adjacent time unit, and the first reserved resource is used to be allocated to other terminal devices in the user group.

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

[0032] In a possible implementation method, the synchronization scheduling indication information is determined according to an identifier of the user group.

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

[0034] In the fifteenth aspect, an embodiment of the present application also provides a resource allocation method, including: a session management network element receives an identifier of a user group, the user group including at least two terminal devices; the session management network element determines synchronization scheduling indication information based on the identifier of the user group, the synchronization scheduling indication information being used to indicate that the terminal devices in the user group need to synchronize air interface scheduling resources with other terminal devices in the user group; the session management network element sends the synchronization scheduling indication information associated with the first terminal device in the user group to the access network device; the access network device allocates the air interface scheduling resources to the first terminal device based on the synchronization scheduling indication information.

[0035] In a possible implementation method, when the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically used to determine the identifier of the user group based on the synchronization scheduling indication information; and according to the identifier of the user group, allocate the air interface scheduling resources to the first terminal device from the air interface resources corresponding to the user group.

[0036] In one possible implementation method, when the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically used to allocate the air interface scheduling resources to the first terminal device from the second reserved resources, and the second reserved resources are in the same or adjacent time unit as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1A This is a schematic diagram of the 5G network architecture based on service-oriented architecture;

[0038] Figure 1B This is a schematic diagram of the 5G network architecture based on point-to-point interfaces;

[0039] Figure 2 Schematic diagram of the components involved in producing communication systems for professional audio;

[0040] Figure 3 A schematic diagram illustrating the time delay caused by multiple terminal devices when sending uplink data;

[0041] Figure 4 A schematic diagram of a resource allocation method provided in an embodiment of the present application;

[0042] Figure 5A A schematic diagram for allocating air interface scheduling resources;

[0043] Figure 5B Another schematic diagram for allocating air interface scheduling resources;

[0044] Figure 6 A schematic diagram of allocating synchronized air interface scheduling resources for terminal devices in a user group by an access network device;

[0045] Figure 7 A schematic diagram of a flow chart of another resource allocation method provided in an embodiment of the present application;

[0046] Figure 8 A schematic diagram of a flow chart of another resource allocation method provided in an embodiment of the present application;

[0047] Figure 9 A schematic diagram of a communication device provided in an embodiment of the present application;

[0048] Figure 10 A schematic diagram of another communication device provided in an embodiment of the present application;

[0049] Figure 11 A schematic diagram of an access network device provided in an embodiment of the present application;

[0050] Figure 12A schematic diagram of a session management network element provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] To make the purpose, technical solutions, and advantages of the embodiments of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings. The specific operating methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" is two or more.

[0052] like Figure 1A Figure 2 shows a schematic diagram of the fifth generation (5G) network architecture based on a service-oriented architecture. Figure 1A The 5G network architecture shown here can include three parts: the terminal equipment part, the data network (DN), and the operator network part. The functions of some of these network elements are briefly described below.

[0053] The operator network may include one or more of the following network elements: authentication server function (AUSF) network element, network exposure function (NEF) network element, policy control function (PCF) network element, unified data management (UDM) network element, unified data repository (UDR) network element, network repository function (NRF) network element, application function (AF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, radio access network (RAN) and user plane function (UPF) network element. In the above operator network, the part other than the radio access network part can be referred to as the core network part.

[0054] A terminal device is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water (such as ships); and can also be deployed in the air (such as airplanes, balloons, and satellites). The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in smart grids, a wireless terminal in transportation safety, a wireless terminal in smart cities, a wireless terminal in smart homes, user equipment (UE), a media device (such as an electronic music device equipped with a communication device, such as an electric guitar, an electric drum set, a microphone, etc.), etc.

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

[0056] The RAN is a subnetwork of the operator network and serves as the implementation system between service nodes and terminal devices within the operator network. To access the operator network, a terminal device first passes through the RAN, and then connects to the operator network's service nodes through the RAN. RAN equipment provides wireless communication capabilities for terminal devices and is also known as access network equipment. RAN equipment includes, but is not limited to, the following: next-generation base stations (gNBs) in 5G, evolved node Bs (eNBs), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved node Bs, or HNBs), baseband units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), and mobile switching centers.

[0057] The AMF network element is responsible for user mobility management, including mobile status management, allocation of user temporary identities, authentication and authorization of users, etc.

[0058] The SMF network element has functions such as session management, execution of PCF control policy, UPF selection, UE Internet Protocol (IP) address allocation, bearer establishment, modification and release, and Quality of Service (QoS) control.

[0059] The UPF network element supports functions such as interconnecting PDU sessions with data networks, packet routing and forwarding, and data packet detection.

[0060] The UDM network element is mainly responsible for managing contract data, user access authorization and other functions.

[0061] The UDR stores and retrieves contract data, policy data, and public architecture data, providing access to relevant data for the UDM, PCF, and NEF. The UDR must implement different data access authentication mechanisms for different types of data, such as contract data and policy data, to ensure data access security. The UDR must be able to return a failure response with an appropriate reason value for illegal service-based operations or data access requests.

[0062] The NEF network element primarily supports network capability exposure, exposing network capabilities and services. Third Generation Partnership Project (3GPP) NFs publish capabilities and events to other NFs through the NEF. NF-exposed capabilities and events can be securely exposed to third-party applications. The NEF uses the standardized interface (Nudr) of the Unified Data Repository (UDR) to store and retrieve structured data. It also translates information exchanged between the AF and internal network functions.

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

[0064] The PCF network element is primarily responsible for policy control functions such as session and service flow-level billing, QoS bandwidth assurance, mobility management, and UE policy decision-making. In this architecture, the PCFs to which the AMF and SMF connect correspond to the AM PCF (PCF for Access and Mobility Control) and the SM PCF (PCF for Session Management), respectively. In actual deployment scenarios, they may not be the same PCF entity.

[0065] NRF network elements can be used to provide network element discovery capabilities, providing network element information corresponding to the network element type based on requests from other network elements. NRF also provides network element management services such as network element registration, update, and deregistration, as well as network element status subscription and push.

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

[0067] A DN is a network located outside of a carrier network. A carrier network can connect to multiple DNs, and a variety of services can be deployed on the DN, providing data and / or voice services to terminal devices. For example, a DN is the private network of a smart factory. Sensors installed in the workshop can be terminal devices. The DN houses a sensor control server, which provides services to the sensors. Sensors can communicate with the control server, receive instructions from the control server, and transmit collected sensor data to the control server based on the instructions. Another example is a DN that is a company's internal office network. An employee's mobile phone or computer can be a terminal device, allowing them to access information and data resources on the company's internal office network.

[0068] Figure 1AWhere Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the 3GPP standard protocol and are not limited here.

[0069] like Figure 1B The following is a schematic diagram of the 5G network architecture based on point-to-point interfaces. The functions of the network elements can be found in Figure 1A The introduction of the functions of the corresponding network elements will not be repeated here. Figure 1B and Figure 1A The main differences are: Figure 1B The interfaces between network elements in a network are point-to-point interfaces, not service-oriented interfaces.

[0070] exist Figure 1B In the architecture shown, the interface names and functions between the various network elements are as follows:

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

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

[0073] 3) N5: The interface between AF and PCF, which can be used to issue application service requests and report network events.

[0074] 4) N4: The interface between SMF and UPF can be used to transmit information between the control plane and the user plane, including the control of the forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and the reporting of information on the user plane.

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

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

[0077] 7) N1: The interface between AMF and UE, which can be used to deliver QoS control rules to UE.

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

[0079] 9) N10: The interface between SMF and UDM, which can be used by SMF to obtain session management related contract data from UDM, and SMF to register UE current session related information with UDM.

[0080] 10) N35: The interface between UDM and UDR, which can be used by UDM to obtain user contract data information from UDR.

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

[0082] 12) N12: The interface between AMF and AUSF, which can be used by AMF to initiate the authentication process to AUSF, which can carry SUCI as the contract identifier;

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

[0084] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or function can be implemented by a single device, or by multiple devices, or can be a functional module within a single device, and this is not specifically limited in the embodiments of the present application.

[0085] The mobility management network element, session management network element, policy control network element, application function network element, access network equipment, network open function network element, and user plane network element in the embodiment of the present application can be Figure 1A or Figure 1B The AMF, SMF, PCF, AF, RAN, NEF, and UPF in the embodiment may also be network elements having the functions of the above-mentioned AMF, SMF, PCF, AF, RAN, NEF, and UPF in future communications such as the sixth generation (6G) network. This embodiment of the present application is not limited to this. For the convenience of explanation, the embodiment of the present application takes the mobility management network element, session management network element, policy control network element, application function network element, access network equipment, network open function network element, and user plane network element as examples for explanation. Furthermore, in the embodiment of the present application, the terminal device is referred to as UE.

[0086] A wireless audio system uses radio waves instead of wires to transmit audio signals. These systems typically include wireless microphone systems and wireless monitoring systems, but they also include systems that enable long-distance wireless audio transmission in certain situations. Wireless audio systems have become an essential subsystem in today's large-scale performances.

[0087] Wireless audio systems can be used in scenarios such as large-scale concerts and performances. Wireless audio systems have high requirements for end-to-end latency, transmission cycle, security and reliability, and sound quality.

[0088] like Figure 2 Figure 1 shows a schematic diagram of the components involved in a professional audio production communication system. On one hand, the system includes a wireless audio input, represented here as a microphone. Audio is captured at the source and sent via a wireless connection to a mixing processing server, which can perform mixing, transcoding, equalization, or other processing tasks on the various audio inputs. The results of the audio processing are then sent via a wireless connection to an output device, which can be a speaker, a general-purpose device equipped with headphones, or other devices.

[0089] For example, during an actual performance, multiple input devices typically generate sound source data. For example, at a concert, there may be a bassist, guitarist, drummer, and lead singer. Each of their input devices contributes essential sound source data to the entire performance. All of this sound source data is then sent via the access network equipment to a network-side mixing server for harmonization or mixing. When different UEs send uplink data, the access network equipment independently schedules and allocates different air interface scheduling resources (wherein air interface scheduling resources include time resources and frequency resources, and time resources can be represented by time units such as slots or mini-slots) to each UE. The mixing server mixes the different input sound source data and then sends the resulting mix to each performer's in-ear monitoring device via the access network equipment, allowing each performer to hear the live performance. The mixing server typically waits until all uplink data from UEs in the same mixing group (also called a user group) has arrived before it begins mixing. That is, in the same mixing group, the network side processes the received data according to a deterministic time. Therefore, the data sent by each UE must be limited to arrive within a certain time range. Otherwise, if the data of one or some UEs does not arrive within the determined time range, the mixing processing cannot be performed, and the network side will discard the data received from other UEs, which will eventually lead to mixing failure.

[0090] In the existing mechanism, when multiple UEs belonging to the same mixing group need to send uplink data through the access network device, they need to transmit the uplink data according to the air interface scheduling resources allocated by the access network device. The time resources in the air interface scheduling resources allocated to different UEs in the same mixing group may be in time units that are far apart, resulting in large differences in the delays of uplink data sent by different UEs reaching the mixing processing server. In other words, the existing mechanism cannot guarantee the deterministic transmission delay of uplink data sent by UEs in the same mixing group, which may cause mixing failure of the mixing processing server.

[0091] like Figure 3 The figure shows a schematic diagram of the delay caused by multiple UEs when sending uplink data. Assuming that UE1 and UE2 have been time synchronized (their time is the same), when UE1's uplink data and UE2's uplink data are sent, although UE1's hardware equipment and UE2's hardware equipment can ensure that they generate data at the same time point, the time units allocated by the RAN device to UE1 and UE2 may be different and far apart. In this way, during the air interface transmission process, UE1's uplink data may be sent earlier than UE2's uplink data. Therefore, although the two are sent through the same RAN device, they are not scheduled in the same or adjacent time units. This results in a large delay between UE1's uplink data and UE2's uplink data. In addition, when the subsequent RAN device transmits the uplink data of UE1 and UE2, the transmission path on the network side may also introduce additional delay. The delay between the mixer device receiving UE1's uplink data and UE2's uplink data may accumulate, causing the delay to increase further.

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

[0093] The method comprises the following steps:

[0094] Step 401: The SMF receives an identifier of a user group.

[0095] The identifier of the user group is used to indicate at least two UEs. Optionally, the user group may also be called a synchronous scheduling service group, a synchronous scheduling group, etc.

[0096] Any UE in the user group requires synchronized air interface scheduling resources with other UEs in the user group. Alternatively, the UEs in the user group require synchronized air interface scheduling resources. Alternatively, the UEs in the user group require synchronized scheduling. Synchronized air interface scheduling resources refer to air interface scheduling resources allocated to UEs in the same user group within the same or adjacent time units.

[0097] In the embodiment of the present application, the time unit can be a time slot (slot) or a mini-time slot (mini-slot), which is uniformly explained here and will not be repeated later.

[0098] As an implementation manner, the SMF may receive an identifier of a user group from the first UE, to which the first UE belongs. That is, the first UE requests allocation of air interface scheduling resources and carries the identifier of the user group to which it belongs.

[0099] As another implementation, the SMF may receive the UE list and the identifier of the user group from the AF. That is, the AF requests allocation of air interface scheduling resources for each UE in the UE list, and carries the identifier of the user group to which each UE in the UE list belongs.

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

[0101] As an implementation method, the SMF may pre-configure the correspondence between the identifier of each user group and the synchronization scheduling indication information. After the SMF obtains the identifier of the user group, the SMF may determine the corresponding synchronization scheduling indication information according to the identifier of the user group.

[0102] As another implementation, the SMF may pre-configure a correspondence between a list of user group identifiers and synchronization scheduling indication information. The user group identifier list includes at least one user group identifier. If the user group identifier obtained by the SMF belongs to the list, the SMF may determine the corresponding synchronization scheduling indication information.

[0103] As another implementation method, the SMF can also obtain the correspondence between the user group identifier and the synchronization scheduling indication information through other network elements (such as PCF network elements), which is not limited in the embodiment of the present application. It should be noted that UEs in the same user group can correspond to the same synchronization scheduling indication information.

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

[0105] Step 404: The RAN allocates air interface scheduling resources to the UE according to the synchronization scheduling indication information, wherein the air interface scheduling resources are used by the UE to send uplink data.

[0106] It should be noted that if, in step 401 above, the SMF receives the identifier of the user group from the first UE, then in step 404, the RAN specifically allocates air interface scheduling resources to the first UE. If, in step 401 above, the SMF receives the identifier of the user group from the AF, then in step 404, the RAN specifically allocates air interface scheduling resources to all UEs in the user group in sequence. It can be understood that the SMF performs step 403 multiple times based on the number of UEs in the user group, that is, the number of UEs in the user group is multiple, and the SMF sends synchronization scheduling indication information to the RAN multiple times, where each synchronization scheduling indication information is associated with each UE in the user group, and the RAN allocates air interface scheduling resources to each UE based on the synchronization scheduling indication information.

[0107] The RAN allocates air interface scheduling resources to the UE in the following ways, for example:

[0108] Method 1: RAN allocates air interface scheduling resources to UE from idle resources according to the synchronization scheduling indication information.

[0109] For example, if the RAN determines, based on the received synchronization scheduling indication information, that the UE is the first UE in the user group to request allocation of air interface scheduling resources, or if the RAN determines that it has not previously received synchronization scheduling indication information associated with a UE in the user group, the RAN may allocate air interface scheduling resources according to normal procedures, such as allocating air interface scheduling resources to the UE from idle resources according to conventional resource allocation methods. Specifically, the RAN determines the time unit for uplink data scheduling for the UE based on its own resource allocation and sends a resource scheduling grant (Grant) to the UE, instructing the UE to transmit uplink data within a specific time unit. The RAN also locally stores the correspondence between the synchronization scheduling indication information and the scheduling resources. Subsequently, the UE transmits uplink data to the RAN according to the air interface scheduling resources allocated by the RAN. After allocating air interface scheduling resources to the UE, the RAN may also allocate reserved resources for other UEs in the user group. The reserved resources are in the same or adjacent time units as the air interface scheduling resources already allocated to the UE. In other words, the reserved resources are applicable to other UEs in the user group.

[0110] It should be noted that the RAN's determination that the UE is the first UE in the user group to request allocation of air interface scheduling resources, or the RAN's determination that no synchronization scheduling indication information associated with UEs in the user group has been received, refers to the RAN's determination that no synchronization scheduling indication information associated with UEs in the user group has been received within a certain time range (for example, in a concert scenario, the lead singer, bassist, guitarist, drummer, etc., as UEs in the user group, have air interface scheduling synchronization requirements, and the time range from the start to the end of a concert, etc.). Based on this implementation, air interface scheduling resources for data transmission by multiple devices (such as media devices) within a time range can be uniformly scheduled and allocated, thereby reducing latency in deterministic transmission.

[0111] For another example, the RAN determines, based on the received synchronization scheduling indication information, that the UE is not the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group, then the RAN can allocate air interface scheduling resources to the UE from the reserved resources.

[0112] It should be noted that the RAN determines that the UE is not the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group, which means that within a certain time range (for example, taking a concert scenario as an example, the lead singer, bassist, guitarist, drummer, etc. as UE in the user group have air interface scheduling synchronization requirements, within the time range from the start to the end of a concert, etc.), the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.

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

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

[0115] For example, if the RAN determines, based on the received synchronization scheduling indication information, that the UE is the first UE in the user group to request allocation of air interface scheduling resources, or if the RAN determines that it has not previously received synchronization scheduling indication information associated with a UE in the user group, the RAN may allocate air interface scheduling resources to the UE from the air interface resources corresponding to the user group. That is, the RAN determines the time unit for uplink data scheduling of the UE based on its own resource allocation and sends a resource scheduling grant (Grant) to the UE, informing the UE to send the uplink data in a certain time unit. The UE subsequently sends the uplink data to the RAN according to the resources allocated by the RAN. After allocating air interface scheduling resources to the UE, the RAN may also allocate reserved resources to other UEs in the user group. The reserved resources are resources from the above-mentioned air interface resources and are in the same or adjacent time units as the resources already allocated to the UE. That is, the reserved resources are applicable to other UEs in the user group.

[0116] It should be noted that the RAN determines that the UE is the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that no synchronization scheduling indication information associated with the UE in the user group has been received before, which means that within a certain time range (for example, taking a concert scenario as an example, the lead singer, bassist, guitarist, drummer, etc. as UEs in the user group have air interface scheduling synchronization requirements, within the time range from the start to the end of a concert, etc.), the RAN determines that no synchronization scheduling indication information associated with the UE in the user group has been received before.

[0117] For another example, the RAN determines, based on the received synchronization scheduling indication information, that the UE is not the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group, then the RAN can allocate air interface scheduling resources to the UE from the reserved resources.

[0118] It should be noted that the RAN determines that the UE is not the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group, which means that within a certain time range (for example, taking a concert scenario as an example, the lead singer, bassist, guitarist, drummer, etc. as UE in the user group have air interface scheduling synchronization requirements, within the time range from the start to the end of a concert, etc.), the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.

[0119] As an example, UE1 and UE2 belong to the same user group. For example, if UE1 is the first UE in the user group to request air interface scheduling resources, the RAN can allocate air interface scheduling resources to UE1 from idle resources or the air interface resources corresponding to the user group. It can also allocate reserved resources, which are in the same or adjacent time units as the scheduling resources allocated to UE1. Subsequently, if UE2 requests air interface scheduling resources again, the RAN can allocate air interface scheduling resources to UE2 using the reserved resources. This allows UEs in the same user group to be allocated scheduling resources in the same or adjacent time units.

[0120] For example, reference Figure 5A and Figure 5B , which is a schematic diagram of allocating air interface scheduling resources. Figure 5A In the example, the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit. Figure 5B In the example, the scheduling resources allocated to UE1 and UE2 are in adjacent time units.

[0121] refer to Figure 5A Assuming that UE1 is the first UE in the user group to request allocation of air interface scheduling resources, the RAN allocates air interface scheduling resources to UE1 from idle resources (for the above method 1) or the air interface resources corresponding to the user group (for the above method 2), and then allocates reserved resources from idle resources (for the above method 1) or the air interface resources corresponding to the user group (for the above method 2). The reserved resources and the air interface scheduling resources allocated to UE1 are in the same time unit. At this time, the reserved resources include Figure 5A The air interface scheduling resources allocated to UE2 are shown in Figure 5A Subsequently, UE2 in the user group (i.e., the second UE in the user group that requests allocation of air interface scheduling resources) requests allocation of air interface scheduling resources, and the RAN allocates air interface scheduling resources to UE2 from the above reserved resources. Figure 5A As shown, the time unit is the same as the time unit in which the air interface scheduling resources are allocated to UE1. The remaining reserved resources are as follows: Figure 5A shown.

[0122] refer to Figure 5B Assuming that UE1 is the first UE in the user group to request allocation of air interface scheduling resources, the RAN allocates air interface scheduling resources to UE1 from idle resources (for the above method 1) or the air interface resources corresponding to the user group (for the above method 2), and then allocates reserved resources from idle resources (for the above method 1) or the air interface resources corresponding to the user group (for the above method 2). The reserved resources and the air interface scheduling resources allocated to UE1 are in the same or adjacent time units. At this time, the reserved resources include Figure 5BThe air interface scheduling resources allocated to UE2 are shown in Figure 5B Subsequently, UE2 in the user group (i.e., the second UE in the user group that requests allocation of air interface scheduling resources) requests allocation of air interface scheduling resources, and the RAN allocates air interface scheduling resources to UE2 from the above reserved resources. Figure 5B As shown, the time unit is adjacent to the time unit in which the air interface scheduling resources are allocated to UE1. At this time, the remaining reserved resources are as follows: Figure 5B shown.

[0123] Optionally, if in step 401, the SMF receives a user group identifier from the first UE, then in step 403, the SMF may further send an identifier of a PDU session of the first UE to the RAN, where the PDU session is associated with a synchronous service executed by the first UE in the user group. Furthermore, in step 404, the RAN allocates air interface scheduling resources to the PDU session of the first UE based on the synchronization scheduling indication information.

[0124] Optionally, if in step 401 above, the SMF receives the user group identifier and the UE list from the AF, then in step 403 above, the SMF may further determine, based on the UE list, the PDU sessions corresponding to each UE in the UE list, and send the identifiers of the PDU sessions corresponding to each UE in the UE list to the RAN. The SMF sends the identifiers of the PDU sessions corresponding to each UE in the UE list to the RAN multiple times based on the number of UEs in the UE list. The PDU sessions are sessions associated with synchronous services executed by the UEs in the user group. Furthermore, in step 404, the RAN allocates air interface scheduling resources to the PDU sessions corresponding to each UE in the UE list based on the synchronous scheduling indication information.

[0125] For example, UE1 and UE2 belong to the same user group. The schematic diagram of RAN allocating air interface scheduling resources to UE1 and UE2 can be referred to Figure 5A and Figure 5B When UE1 and UE2 send uplink data, the scheduling diagram of RAN for uplink data sent by UE1 and UE2 can be referred to Figure 6 If the RAN schedules the uplink data of UE1 and UE2 in the same time unit or adjacent time when allocating air interface scheduling resources, it can ensure that the uplink data of UE1 and UE2 are transmitted to the network side at the same time. In this way, when the network performs mixing processing, it can receive the uplink data of UE1 and UE2 at the same time as much as possible, which helps to ensure the effect and quality of mixing processing.

[0126] In the above solution, the network side (SMF) can determine the synchronization scheduling indication information on the RAN side based on the identifier of the user group. The RAN can allocate air interface scheduling resources of the same or adjacent time units to the UEs in the user group based on the synchronization scheduling indication information. In this way, the network side can receive data sent by different UEs in the user group within the shortest possible delay, which helps to improve the quality of data processing.

[0127] The following is a specific example of the above Figure 4 The process shown is introduced and explained.

[0128] like Figure 7 FIG2 is a flow chart of another resource allocation method provided in an embodiment of the present application. In this solution, the UE sends the identifier of the user group to the network. The network can allocate synchronization scheduling indication information based on the user group identifier and send the synchronization scheduling indication information to the RAN. In this way, the RAN can perform special resource scheduling for the UE based on the synchronization scheduling indication information, that is, synchronize resource scheduling for UEs in the same user group.

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

[0130] Optionally, methods for the UE to obtain the group ID include but are not limited to the following two:

[0131] a) In the registration process, the network generates a group identifier based on the UE's subscription data (e.g., a group identifier based on the service type subscribed to by the UE), or the UE's subscription data includes the group identifier to which the UE belongs, which is then sent by the network to the UE in a registration accept message.

[0132] b) The UE locally configures the group identifier to which the UE belongs.

[0133] Taking the group identifier as a user group identifier as an example, the method includes the following steps:

[0134] Step 701: The UE sends a first request to the AMF. Correspondingly, the AMF may receive the first request.

[0135] The first request includes a PDU session identifier (PDU session ID) and a user group identifier, wherein the PDU session identifier is used to identify the PDU session. Any UE in the user group requires air interface scheduling resources that are synchronized with other UEs in the user group.

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

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

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

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

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

[0141] Among them, the implementation method of SMF determining the synchronization scheduling indication information according to the user group identifier can refer to Figure 4 The relevant description of step 402 of the corresponding embodiment will not be repeated here.

[0142] It should be noted that if the PDU sessions of different UEs within the same user group correspond to different SMFs, then after different SMFs receive user group identifiers sent by different UEs, the synchronization scheduling indication information determined by different SMFs based on the same user group identifier is the same. This can be understood as configuring the same correspondence between the user group identifier and the synchronization scheduling identifier on different SMFs. Therefore, different SMFs can determine the same synchronization scheduling indication information based on the same user group identifier.

[0143] Optionally, during this process, SMF and PCF may further update session management related policies.

[0144] Step 704: The SMF sends a second response to the AMF. Correspondingly, the AMF may receive the second response.

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

[0146] In step 705, the AMF sends a third request to the RAN. Accordingly, the RAN may receive the third request.

[0147] The third request includes an N2 SM container and an N1 SM container, wherein the N2 SM container includes synchronization scheduling indication information and an identifier of a PDU session.

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

[0149] The PDU session identifier is used to indicate the PDU session to which air interface scheduling resources need to be allocated.

[0150] The RAN may allocate air interface scheduling resources for the UE's PDU session based on the synchronization scheduling indication information and the PDU session identifier by:

[0151] Method 1: RAN allocates air interface scheduling resources to the UE from idle resources according to the synchronization scheduling indication information and the identifier of the PDU session.

[0152] For example, if the RAN determines, based on the received synchronization scheduling indication information, that the UE is the first UE in the user group to request allocation of air interface scheduling resources, or if the RAN determines that it has not previously received synchronization scheduling indication information associated with a UE in the user group, the RAN may allocate air interface scheduling resources according to normal procedures, such as allocating air interface scheduling resources from idle resources for the UE's PDU session according to conventional resource allocation methods. Specifically, the RAN determines the time unit for uplink data scheduling for the UE based on its own resource allocation and sends a resource scheduling grant (Grant) to the UE, instructing the UE to transmit uplink data for the PDU session within a specific time unit. The RAN also locally stores the correspondence between the synchronization scheduling indication information and the scheduling resources. Subsequently, the UE transmits uplink data to the RAN according to the air interface scheduling resources allocated by the RAN. After allocating air interface scheduling resources for the UE's PDU session, the RAN may also reserve resources for PDU sessions of other UEs in the user group. The reserved resources are in the same or adjacent time units as the air interface scheduling resources allocated to the UE's PDU session. In other words, the reserved resources are applicable to PDU sessions of other UEs in the user group. For example, UE1 and UE2 belong to the same user group, and UE1 needs to synchronize air interface scheduling resources with UE2. Figure 5A and Figure 5B , which is a schematic diagram of allocating air interface scheduling resources. Figure 5A In the example, the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit. Figure 5B In the example, the scheduling resources allocated to UE1 and UE2 are in adjacent time units.

[0153] It should be noted that the RAN determines that the UE is the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that no synchronization scheduling indication information associated with the UE in the user group has been received before, which means that within a certain time range (for example, taking a concert scenario as an example, the lead singer, bassist, guitarist, drummer, etc. as UEs in the user group have air interface scheduling synchronization requirements, within the time range from the start to the end of a concert, etc.), the RAN determines that no synchronization scheduling indication information associated with the UE in the user group has been received before.

[0154] For another example, the RAN determines, based on the received synchronization scheduling indication information, that the UE is not the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group. In this case, the RAN can allocate air interface scheduling resources for the PDU session of the UE from the reserved resources.

[0155] It should be noted that the RAN determines that the UE is not the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group, which means that within a certain time range (for example, taking a concert scenario as an example, the lead singer, bassist, guitarist, drummer, etc. as UE in the user group have air interface scheduling synchronization requirements, within the time range from the start to the end of a concert, etc.), the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.

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

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

[0158] For example, the RAN determines, based on the received synchronization scheduling indication information, that the UE is the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has not previously received synchronization scheduling indication information associated with the UE in the user group. In this case, the RAN can allocate air interface scheduling resources for the PDU session of the UE from the air interface resources corresponding to the user group, that is, the RAN determines the time unit for uplink data scheduling of the UE based on its own resource allocation, and sends a resource scheduling assignment (Grant) to the UE, informing the UE to send the uplink data in a certain time unit. The UE will subsequently send the uplink data to the RAN according to the resources allocated by the RAN. After allocating air interface scheduling resources for the PDU session of the UE, the RAN can also allocate reserved resources for the PDU sessions of other UEs in the user group. The reserved resources are resources in the above-mentioned air interface resources and are in the same or adjacent time units as the air interface scheduling resources that have been allocated to the PDU session of the UE. That is, the reserved resources are applicable to the PDU sessions of other UEs in the user group. For example, UE1 and UE2 belong to the same user group, and UE1 needs to synchronize air interface scheduling resources with UE2. Reference Figure 5A and Figure 5B , which is a schematic diagram of allocating air interface scheduling resources. Figure 5A In the example, the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit. Figure 5B In the example, the scheduling resources allocated to UE1 and UE2 are in adjacent time units.

[0159] It should be noted that the RAN determines that the UE is the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that the synchronization scheduling indication information associated with the UE in the user group has been received before, which means that within a certain time range (for example, taking a concert scenario as an example, the lead singer, bassist, guitarist, drummer, etc. as UEs in the user group have air interface scheduling synchronization requirements, within the time range from the start to the end of a concert, etc.), the RAN determines that the synchronization scheduling indication information associated with the UE in the user group has not been received before.

[0160] For another example, the RAN determines, based on the received synchronization scheduling indication information, that the UE is not the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group. In this case, the RAN can allocate air interface scheduling resources for the PDU session of the UE from the reserved resources.

[0161] It should be noted that the RAN determines that the UE is not the first UE in the user group to request allocation of air interface scheduling resources, or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group, which means that within a certain time range (for example, taking a concert scenario as an example, the lead singer, bassist, guitarist, drummer, etc. as UE in the user group have air interface scheduling synchronization requirements, within the time range from the start to the end of a concert, etc.), the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.

[0162] 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 PDU sessions of different UEs in the same user group correspond to different SMFs, in step 703, different SMFs determine the same synchronization scheduling indication information based on the same user group identifier. Therefore, the RAN can allocate synchronized air interface scheduling resources to different UEs in the same user group.

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

[0164] The air interface scheduling resources are the scheduling resources allocated by the RAN to the UE on the air interface side for sending uplink data. The UE can perform local configuration based on the air interface scheduling resources sent by the RAN, and subsequently send uplink data to the RAN based on the air interface scheduling resources allocated by the RAN.

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

[0166] In step 708, the RAN sends a third response to the AMF. Accordingly, the AMF may receive the third response.

[0167] This step 708 is optional.

[0168] As an implementation scheme, the above embodiment may be executed in the PDU session establishment process after the UE registers with the network. In the PDU session establishment process, the above first request may be a PDU session establishment request (PDU Sessionestablishment Request), the above second request may be a PDU session establishment request (Nsmf_PDUSession_CreateSMContext request), the above first response may be a PDU session establishment accept message (PDU SessionEstablishment Accept), the above second response may be a PDU session establishment request response (Nsmf_PDUSession_CreateSMContext response), the above third request may be an N2 session request (N2session request), and the above third response may be an N2 session response (N2 session response).

[0169] As an implementation scheme, the above embodiment can be executed in the PDU session modification process after the UE registers with the network. In the PDU session modification process, the above first request may be a PDU session modification request (PDU Session Modification Request), the above second request may be a PDU session update request (Nsmf_PDUSession_UpdateSMContext request), the above first response may be a PDU session modification request acknowledgment message (PDUSession Modification ack), the above second response may be a PDU session update response (Nsmf_PDUSession_UpdateSMContext response), the above third request may be an N2 session request (N2 session request), and the above third response may be an N2 session response (N2 session response).

[0170] For example, UE1 and UE2 belong to the same user group. The schematic diagram of RAN allocating air interface scheduling resources to UE1 and UE2 can be referred to Figure 5A and Figure 5B When UE1 and UE2 send uplink data, the scheduling diagram of RAN for uplink data sent by UE1 and UE2 can be referred to Figure 6 If the RAN schedules the uplink data of UE1 and UE2 in the same time unit or adjacent time when allocating air interface scheduling resources, it can ensure that the uplink data of UE1 and UE2 are transmitted to the network side at the same time as much as possible. In this way, when the network performs mixing processing, it can receive the uplink data of UE1 and UE2 at the same time as much as possible, which helps to ensure the effect and quality of mixing processing. In the above scheme, the UE carries the user group identifier in the first request. The network side (SMF) can determine the synchronization scheduling indication information on the RAN side based on the user group identifier. The RAN can allocate air interface scheduling resources in the same or adjacent time units to the UEs in the user group based on the synchronization scheduling indication information. Therefore, the network side can receive data sent by different UEs in the user group within the shortest possible delay, which helps to improve the quality of data processing.

[0171] like Figure 8 The figure shows a flow chart of another resource allocation method provided by an embodiment of the present application. In this solution, after the UE has established a session, the AF sends a request to the network, which carries a user group identifier. In this way, the network can determine synchronization scheduling indication information based on the user group identifier and then send the synchronization scheduling indication information to the RAN. In this way, the RAN can perform special resource scheduling for the UE, that is, synchronize resource scheduling for UEs in the same user group.

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

[0173] Optionally, methods for the UE to obtain the group ID include but are not limited to the following two:

[0174] a) In the registration process, the network generates a group identifier based on the UE's subscription data (e.g., a group identifier based on the service type subscribed to by the UE), or the UE's subscription data includes the group identifier to which the UE belongs, which is then sent by the network to the UE in a registration accept message.

[0175] b) The group identifier to which the UE belongs is locally configured on the UE.

[0176] Taking the group identifier as a user group identifier as an example, the method includes the following steps:

[0177] Step 801: The AF sends a policy update request (Npcf_PolicyAuthorization updaterequest) to the PCF. Correspondingly, the PCF may receive the policy update request.

[0178] For example, the AF may send the above policy update request to the PCF through the NEF.

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

[0180] Any UE in the user group requires air interface scheduling resources that are synchronized with other UEs in the user group.

[0181] The UE list includes one or more UE identifiers, and the UE identifiers in the UE list belong to the above user group.

[0182] Step 802: PCF triggers a PDU session-related policy update process (PCF initiated SMF PolicyAssociationModification). In this process, PCF triggers SMF to update the PDU session of the UE indicated by the UE list, and PCF sends the user group identifier and UE list to SMF.

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

[0184] Among them, the implementation method of SMF determining the synchronization scheduling indication information according to the user group identifier can refer to Figure 4 The relevant description of step 402 of the corresponding embodiment will not be repeated here.

[0185] It should be noted that if the PDU sessions of different UEs within the same user group correspond to different SMFs, then after different SMFs receive user group identifiers sent by different UEs, the synchronization scheduling indication information determined by different SMFs based on the same user group identifier is the same. This can be understood as configuring the same correspondence between the user group identifier and the synchronization scheduling identifier on different SMFs. Therefore, different SMFs can determine the same synchronization scheduling indication information based on the same user group identifier.

[0186] Step 804: SMF sends synchronization scheduling indication information and PDU session identifier to AMF.

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

[0188] In step 805, the AMF sends an N2 session request to the RAN. Correspondingly, the RAN may receive the N2 session request.

[0189] The N2 session request includes an N2 SM container and an N1 SM container, wherein the N2 SM container includes synchronization scheduling indication information and a PDU session identifier, and the N1 SM container carries the PDU session identifier and a PDU session modification response message (PDU Session Modification ack).

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

[0191] The PDU session identifier is used to indicate the PDU session to which air interface scheduling resources need to be allocated.

[0192] The implementation method of RAN allocating air interface scheduling resources for UE's PDU session based on the synchronization scheduling indication information and the PDU session identifier can be referred to Figure 7 The relevant description of the corresponding embodiments will not be repeated here.

[0193] 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 PDU sessions of different UEs in the same user group correspond to different SMFs, in step 803, different SMFs determine the same synchronization scheduling indication information based on the same user group identifier. Therefore, the RAN can allocate synchronized air interface scheduling resources to different UEs in the same user group.

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

[0195] The air interface scheduling resources are the scheduling resources allocated by the RAN to the UE on the air interface side for sending uplink data. The UE can perform local configuration based on the air interface scheduling resources sent by the RAN, and subsequently send uplink data to the RAN based on the air interface scheduling resources allocated by the RAN.

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

[0197] In step 808, the RAN sends an N2 session response to the AMF. Accordingly, the AMF may receive the N2 session response.

[0198] This step 808 is optional.

[0199] For example, UE1 and UE2 belong to the same user group. The schematic diagram of RAN allocating air interface scheduling resources to UE1 and UE2 can be referred to Figure 5A and Figure 5B When UE1 and UE2 send uplink data, the scheduling diagram of RAN for uplink data sent by UE1 and UE2 can be referred to Figure 6 If the RAN schedules the uplink data of UE1 and UE2 in the same time unit or adjacent time when allocating air interface scheduling resources, it can ensure that the uplink data of UE1 and UE2 are transmitted to the network side at the same time. In this way, when the network performs mixing processing, it can receive the uplink data of UE1 and UE2 at the same time as much as possible, which helps to ensure the effect and quality of mixing processing.

[0200] In the above solution, the AF carries the user group identifier in the policy update request. The network side (SMF) can determine the synchronization scheduling indication information on the RAN side based on the user group identifier. The RAN can allocate air interface scheduling resources in the same or adjacent time units to the UEs in the user group based on the synchronization scheduling indication information. In this way, the network side can receive data sent by different UEs in the user group within the shortest possible delay, which helps to improve the quality of data processing.

[0201] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between various network elements. It can be understood that in order to realize the above functions, the above-mentioned network elements include hardware structures and / or software modules corresponding to the execution of each function. It should be easy for those skilled in the art to realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0202] It can be understood that in the above-mentioned method embodiments, the steps or operations corresponding to those implemented by the terminal device can also be implemented by components (such as chips or circuits) configured in the terminal device, the steps or operations corresponding to those implemented by the access network device can also be implemented by components (such as chips or circuits) configured in the access network device, and the steps or operations corresponding to those implemented by the session management network element can also be implemented by components (such as chips or circuits) configured in the session management network element.

[0203] refer to Figure 9 , is a schematic diagram of a communication device provided in an embodiment of the present application. The device is used to implement the various steps performed by the corresponding access network device in the above method embodiment, such as Figure 9 As shown, the apparatus 900 includes a receiving unit 910, a sending unit 920, and an allocating unit 930. Optionally, it further includes a determining unit 940. The receiving unit 910 is configured to receive synchronization scheduling indication information associated with a terminal device, where the synchronization scheduling indication information is used to indicate an air interface scheduling resource that the terminal device needs to synchronize with other terminal devices in the user group to which the terminal device belongs; the allocating unit 930 is configured to allocate the air interface scheduling resource to the terminal device based on the synchronization scheduling indication information. The sending unit 920 is configured to send the air interface scheduling resource to the terminal device.

[0204] In a possible implementation method, when the receiving unit 910 has not received the synchronization scheduling indication information associated with the terminal device in the user group; the allocation unit 930 is specifically used to determine the identifier of the user group based on the synchronization scheduling indication information; and according to the identifier of the user group, allocate the air interface scheduling resources to the terminal device from the air interface resources corresponding to the user group.

[0205] In a possible implementation method, the receiving unit 910 is further configured to receive an identifier of the user group; and 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.

[0206] In one possible implementation method, the determination unit 940 is used to determine a first reserved resource in the air interface resources, where the first reserved resource and the air interface scheduling resource allocated to the terminal device are in the same or adjacent time unit, and the first reserved resource is used to be allocated to other terminal devices in the user group.

[0207] In a possible implementation method, when the receiving unit 910 has received the synchronization scheduling indication information associated with the terminal device in the user group; the allocation unit 930 is specifically used to allocate the air interface scheduling resources to the terminal device from the second reserved resources, and the second reserved resources are in the same or adjacent time unit as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group.

[0208] In a possible implementation method, the synchronization scheduling indication information is determined according to an identifier of the user group.

[0209] It is understandable that the above-mentioned units may also be referred to as modules or circuits, etc., and the above-mentioned units may be independently provided or fully or partially integrated.

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

[0211] The above-mentioned receiving unit 910, sending unit 920 or transceiver unit can also be called a communication interface, and the above-mentioned processing unit can also be called a processor.

[0212] Optionally, the communication device 900 may further include a storage unit for storing data or instructions (also referred to as code or program). The aforementioned units may interact or couple with the storage unit to implement corresponding methods or functions. For example, the processing unit may read the data or instructions in the storage unit, causing the communication device to implement the methods in the aforementioned embodiments.

[0213] refer to Figure 10 , is a schematic diagram of a communication device provided in an embodiment of the present application. The device is used to implement the various steps performed by the corresponding session management network element in the above method embodiment, such as Figure 10 As shown, the apparatus 1000 includes a receiving unit 1010, a sending unit 1020, and a determining unit 1030. The receiving unit 1010 is configured to receive an identifier of a user group, where the user group includes at least two terminal devices; the determining unit 1030 is configured to determine synchronization scheduling indication information based on the identifier of the user group, where the synchronization scheduling indication information is used to indicate an air interface scheduling resource that a terminal device in the user group needs to synchronize with other terminal devices in the user group; and the sending unit 1020 is configured to send the synchronization scheduling indication information to an access network device.

[0214] 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 receive an identifier of the user group from an application function network element.

[0215] It is understandable that the above-mentioned units may also be referred to as modules or circuits, etc., and the above-mentioned units may be independently provided or fully or partially integrated.

[0216] In some possible implementations, the receiving unit 1010 and the sending unit 1020 may also be implemented by a transceiver unit, or the receiving unit 1010 and the sending unit 1020 may also be collectively referred to as a transceiver unit. The determining unit 1030 may be implemented by a processing unit.

[0217] The above-mentioned receiving unit 1010, sending unit 1020 or transceiver unit can also be called a communication interface, and the above-mentioned processing unit can also be called a processor.

[0218] Optionally, the communication device 1000 may further include a storage unit for storing data or instructions (also referred to as code or program). The above-mentioned units may interact or couple with the storage unit to implement corresponding methods or functions. For example, the processing unit may read the data or instructions in the storage unit, so that the communication device implements the method in the above embodiment.

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

[0220] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application-specific integrated circuits (ASICs), one or more digital singnal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can 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 that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0221] The above-mentioned unit for receiving (e.g., receiving unit) is an interface circuit of the device, which is used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is the interface circuit of the chip used to receive signals from other chips or devices. The above-mentioned unit for sending (e.g., sending unit) is an interface circuit of the device, which is used to send signals to other devices. For example, when the device is implemented as a chip, the sending unit is the interface circuit of the chip used to send signals to other chips or devices.

[0222] refer to Figure 11 , is a schematic diagram of the structure of an access network device provided in an embodiment of the present application. The access network device is used to implement the operations of the access network device in the above embodiment. Figure 11 As shown, the access network device includes an antenna 1110, a radio frequency device 1120, and a baseband device 1130. Antenna 1110 is connected to radio frequency device 1120. In the uplink direction, radio frequency device 1120 receives information sent by terminal devices via antenna 1110 and sends the information to baseband device 1130 for processing. In the downlink direction, baseband device 1130 processes the information from the terminal devices and sends it to radio frequency device 1120. Radio frequency device 1120 then processes the information and sends it to the terminal devices via antenna 1110.

[0223] The baseband device 1130 may include one or more processing elements 1131, such as a main control CPU and other integrated circuits, and an interface 1133. Furthermore, the baseband device 1130 may include a storage element 1132 for storing programs and data, and an interface 1133 for exchanging information with the radio frequency device 1120. The interface 1133 may be, for example, a common public radio interface (CPRI). The above-mentioned apparatus for access network devices may be located in the baseband device 1130. For example, the above-mentioned apparatus for access network devices may be a chip on the baseband device 1130, the chip including at least one processing element and an interface circuit, wherein the processing element is configured to execute each step of any of the methods performed by the access network devices, and the interface circuit is configured to communicate with other devices. In one implementation, the unit for implementing each step of the above-mentioned method in the access network device may be implemented in the form of a processing element scheduler. For example, the apparatus for access network devices includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method performed by the access network device in the above-mentioned method embodiments. The storage element may be a storage element on the same chip as the processing element, ie, an on-chip storage element, or a storage element on a different chip from the processing element, ie, an off-chip storage element.

[0224] In another implementation, the unit of the access network device that implements each step of the above method may be configured as one or more processing elements, which are provided on the baseband device. The processing elements may be integrated circuits, such as one or more ASICs, one or more DSPs, one or more FPGAs, or a combination of these integrated circuits. These integrated circuits may be integrated together to form a chip.

[0225] The units implementing the various steps of the above method in the access network device can be integrated together and implemented in the form of a SOC. For example, the baseband device includes this SOC chip to implement the above method. The chip can integrate at least one processing element and a storage element, and the processing element can call the program stored in the storage element to implement the above method performed by the access network device. Alternatively, the chip can integrate at least one integrated circuit to implement the above method performed by the access network device. Alternatively, the above implementation methods can be combined, with the functions of some units implemented by the processing element calling the program, and the functions of some units implemented by the integrated circuit.

[0226] As can be seen, the above-mentioned apparatus for access network devices may include at least one processing element and an interface circuit, wherein the at least one processing element is configured to execute any of the methods provided in the above method embodiments. The processing element may execute some or all of the steps executed by the access network device in a first manner, namely, by invoking a program stored in a storage element; or in a second manner, namely, by executing some or all of the steps executed by the access network device through the hardware integrated logic circuit in the processor element in combination with instructions. Of course, the first and second manners may also be combined to execute some or all of the steps executed by the above-mentioned access network device.

[0227] The processing element herein, as described above, may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above method, such as one or more ASICs, one or more microprocessors (DSPs), one or more FPGAs, or a combination of at least two of these integrated circuit forms. The storage element may be a single memory or a collective term for multiple storage elements.

[0228] refer to Figure 12 , is a structural diagram of a session management network element provided in an embodiment of the present application, which is used to implement the operation of the session management network element in the above embodiment. Figure 12 As shown, the session management network element includes: a processor 1210 and an interface 1230, and optionally, a memory 1220. The interface 1230 is used to implement communication with other devices.

[0229] The methods performed by the session management network element in the above embodiments can be implemented by the processor 1210 calling a program stored in a memory (which can 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 the processor 1210, which executes the methods performed by the session management network element in the above method embodiments by calling the program in the memory. The processor here can be an integrated circuit with signal processing capabilities, such as a CPU. The apparatus for the session management network element can be implemented by one or more integrated circuits configured to implement the above methods. For example, one or more ASICs, one or more microprocessors (DSPs), one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, a combination of the above implementations can be used.

[0230] The embodiment of the present application also provides a communication system, including: Figure 9 The communication device shown and Figure 10 The communication device shown.

[0231] The present application also provides a communication system, including: Figure 11The access network equipment shown and Figure 12 The session management network element is shown.

[0232] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can 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 the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0233] The various illustrative logic units and circuits described in the embodiments of the present application can be implemented or operated by 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, a discrete gate or transistor logic, a discrete hardware component, or the design of any combination thereof. The general-purpose processor can be a microprocessor, alternatively, the general-purpose processor can also be any traditional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration to implement.

[0234] In one or more exemplary designs, the above-described functions described herein may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions may be stored on a computer-readable medium or transmitted in the form of one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one location to another. Storage media can be any available medium that can be accessed by a general-purpose or specialized computer. For example, such computer-readable media may 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 that can be used to carry or store program code in the form of instructions or data structures and other forms that can be read by a general-purpose or specialized computer, or a general-purpose or specialized processor. In addition, any connection can be appropriately defined as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote resource via a coaxial cable, fiber optic cable, twisted pair cable, digital subscriber line (DSL), or wirelessly, such as infrared, wireless, and microwave, it is also included in the definition of computer-readable media. Disks and discs include compact disks, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while discs typically reproduce data optically using lasers. Combinations of these may also be included in computer-readable media.

[0235] Those skilled in the art will appreciate that, in one or more of the examples above, the functions described herein may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0236] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, the present application is intended to include such modifications and variations if they fall within the scope of the claims of the present application and their equivalents.

Claims

1. A resource allocation method, characterized in that: Chips used in or within access network equipment include: Receiving synchronization scheduling indication information associated with a terminal device, the synchronization scheduling indication information is used to indicate that the terminal device needs to synchronize air interface scheduling resources with other terminal devices in the user group to which the terminal device belongs, and the synchronized air interface scheduling resources refer to air interface scheduling resources allocated to terminal devices in the same user group in the same or adjacent time units; Allocate the air interface scheduling resources to the terminal device according to the synchronous scheduling indication information.

2. The method according to claim 1, wherein When the synchronization scheduling indication information associated with the terminal equipment in the user group has not been received, The allocating the air interface scheduling resource to the terminal device according to the synchronization scheduling indication information includes: determining an identifier of the user group according to the synchronization scheduling indication information; According to the identifier of the user group, the air interface scheduling resources are allocated to the terminal device from the air interface resources corresponding to the user group.

3. The method according to claim 2, wherein Also includes: receiving an identifier of the user group; The air interface resources are allocated to the user group according to the identifier of the user group.

4. The method according to claim 2, wherein Also includes: Determine a first reserved resource in the air interface resources, where the first reserved resource and the air interface scheduling resource allocated to the terminal device are in the same or adjacent time unit, and the first reserved resource is used to be allocated to other terminal devices in the user group.

5. The method according to claim 1, wherein When the synchronization scheduling indication information associated with the terminal device in the user group has been received; The allocating the air interface scheduling resource to the terminal device according to the synchronization scheduling indication information includes: The air interface scheduling resources are allocated to the terminal device from the second reserved resources, where the second reserved resources and the air interface scheduling resources that have been allocated to one or more terminal devices in the user group are in the same or adjacent time units.

6. The method according to any one of claims 1 to 5, characterized in that: The synchronization scheduling indication information is determined according to the identifier of the user group.

7. A resource allocation method, characterized in that: Chips used in or within session management network elements include: receiving an identifier of a user group, where the user group includes at least two terminal devices; Determining, based on the identifier of the user group, synchronization scheduling indication information, the synchronization scheduling indication information being used to indicate that terminal devices in the user group need to synchronize air interface scheduling resources with other terminal devices in the user group, the synchronized air interface scheduling resources referring to air interface scheduling resources allocated to terminal devices in the same user group being in the same or adjacent time units; Send the synchronization scheduling indication information to the access network device.

8. The method according to claim 7, wherein The receiving user group identifier includes: receiving an identifier of the user group from a first terminal device, the first terminal device belonging to the user group; or; An identifier of the user group is received from an application function network element.

9. A communication device, characterized in that: The communication device is an access network device or a chip in the access network device, including: a receiving unit, configured to receive synchronization scheduling indication information associated with a terminal device, the synchronization scheduling indication information being used to indicate that the terminal device needs to synchronize air interface scheduling resources with other terminal devices in the user group to which the terminal device belongs, the synchronized air interface scheduling resources referring to air interface scheduling resources allocated to terminal devices in the same user group being in the same or adjacent time units; An allocation unit is used to allocate the air interface scheduling resources to the terminal device according to the synchronization scheduling indication information.

10. The device according to claim 9, wherein When the receiving unit has not received the synchronization scheduling indication information associated with the terminal device in the user group; The allocation unit is specifically configured to determine an identifier of the user group according to the synchronization scheduling indication information; and allocate the air interface scheduling resources to the terminal device from the air interface resources corresponding to the user group according to the identifier of the user group.

11. The device according to claim 10, wherein The receiving unit is further configured to receive an identifier of the user group; The allocation unit is further configured to allocate the air interface resources to the user group according to the identifier of the user group.

12. The device according to claim 10, wherein The device also includes a determination unit for determining a first reserved resource in the air interface resources, where the first reserved resource and the air interface scheduling resource allocated to the terminal device are in the same or adjacent time unit, and the first reserved resource is used to be allocated to other terminal devices in the user group.

13. The device according to claim 9, wherein When the receiving unit has received the synchronization scheduling indication information associated with the terminal device in the user group; The allocation unit is specifically used to allocate the air interface scheduling resources to the terminal device from the second reserved resources, and the second reserved resources are in the same or adjacent time units as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group.

14. The device according to any one of claims 9 to 13, characterized in that: The synchronization scheduling indication information is determined according to the identifier of the user group.

15. A communication device, characterized in that: The communication device is a session management network element or a chip within the session management network element, including: 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, based on an identifier of the user group, synchronization scheduling indication information, the synchronization scheduling indication information being used to indicate that a terminal device in the user group needs to synchronize air interface scheduling resources with other terminal devices in the user group, the synchronized air interface scheduling resources referring to air interface scheduling resources allocated to terminal devices in the same user group being in the same or adjacent time units; A sending unit is used to send the synchronization scheduling indication information to the access network device.

16. The device according to claim 15, characterized in that The receiving unit is specifically configured to: receiving an identifier of the user group from a first terminal device, the first terminal device belonging to the user group; or; An identifier of the user group is received from an application function network element.

17. A communication system, characterized in that: Including session management network elements and access network equipment; The session management network element is configured to receive an identifier of a user group, the user group including at least two terminal devices; determine synchronization scheduling indication information based on the identifier of the user group, the synchronization scheduling indication information being used to indicate that the terminal devices in the user group need to synchronize air interface scheduling resources with other terminal devices in the user group, the synchronized air interface scheduling resources referring to air interface scheduling resources allocated to the terminal devices in the same user group being in the same or adjacent time units; and send the synchronization scheduling indication information associated with a first terminal device in the user group to the access network device; The access network device is used to allocate the air interface scheduling resources to the first terminal device according to the synchronization scheduling indication information.

18. The system according to claim 17, wherein: When the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group; The access network device is specifically used to determine the identifier of the user group according to the synchronization scheduling indication information; and allocate the air interface scheduling resources to the first terminal device from the air interface resources corresponding to the user group according to the identifier of the user group.

19. The system of claim 18, wherein: The access network device is further configured to receive an identifier of the user group; and allocate the air interface resources to the user group according to the identifier of the user group.

20. The system of claim 18, wherein: The access network device is also used to determine a first reserved resource in the air interface resources, where the first reserved resource and the air interface scheduling resource allocated to the first terminal device are in the same or adjacent time unit, and the first reserved resource is used to be allocated to other terminal devices in the user group.

21. The system of claim 17, wherein: When the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group; The access network device is specifically used to allocate the air interface scheduling resources to the first terminal device from the second reserved resources, and the second reserved resources are in the same or adjacent time unit as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group.

22. The system according to any one of claims 17 to 21, wherein: The synchronization scheduling indication information is determined according to the identifier of the user group.

23. The system according to any one of claims 17 to 21, wherein: The session management network element is configured to receive an identifier of a user group, specifically including: used to receive the identifier of the user group from the first terminal device; or; Used to receive the identifier of the user group from the application function network element.

24. A resource allocation method, characterized in that: include: The session management network element receives an identifier of a user group, where the user group includes at least two terminal devices; The session management network element determines, based on the identifier of the user group, synchronization scheduling indication information, where the synchronization scheduling indication information is used to indicate that terminal devices in the user group need to synchronize air interface scheduling resources with other terminal devices in the user group, where the synchronized air interface scheduling resources refer to air interface scheduling resources allocated to terminal devices in the same user group in the same or adjacent time units; The session management network element sends the synchronization scheduling indication information associated with the first terminal device in the user group to the access network device; The access network device allocates the air interface scheduling resources to the first terminal device according to the synchronization scheduling indication information.

25. The method of claim 24, wherein: When the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group; The access network device is specifically used to determine the identifier of the user group according to the synchronization scheduling indication information; and allocate the air interface scheduling resources to the first terminal device from the air interface resources corresponding to the user group according to the identifier of the user group.

26. The method of claim 24, wherein: When the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group; The access network device is specifically used to allocate the air interface scheduling resources to the first terminal device from the second reserved resources, and the second reserved resources are in the same or adjacent time unit as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group.

27. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a program, and when the program is called by a processor, the method according to any one of claims 1 to 6 is executed.

28. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a program, and when the program is called by a processor, the method according to claim 7 or 8 is executed.

29. A computer program product, characterized in that When the program in the computer program product is called by a processor, the method according to any one of claims 1 to 6 is executed.

30. A computer program product, characterized in that When the program in the computer program product is called by a processor, the method according to claim 7 or 8 is executed.

Images