WO2021134347A1 - 资源分配方法、装置及*** - Google Patents
资源分配方法、装置及*** Download PDFInfo
- Publication number
- WO2021134347A1 WO2021134347A1 PCT/CN2019/130179 CN2019130179W WO2021134347A1 WO 2021134347 A1 WO2021134347 A1 WO 2021134347A1 CN 2019130179 W CN2019130179 W CN 2019130179W WO 2021134347 A1 WO2021134347 A1 WO 2021134347A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user group
- air interface
- indication information
- scheduling
- synchronization
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
Definitions
- This application relates to the field of communication technology, and in particular to resource allocation methods, devices and systems.
- multiple terminal devices need to perform a certain service in coordination, and these terminal devices need to send data to the network side, and the network side performs comprehensive processing based on the data reported by each terminal device.
- the vocalist, bassist, guitarist, drummer, etc. are used as terminal devices.
- These terminal devices belong to the same mixing group (also called user group), and the sound data generated by each needs to be separately generated through the mobile network.
- Send to the network side, and then the network side performs mixing processing according to the deterministic time according to each collected sound data, so as to output the final processing result and return it to each terminal device.
- the network side processes the received data according to the deterministic time, the data sent by each terminal device needs to arrive within a certain time range, otherwise once one or some terminal devices send If the data does not arrive within a certain time range, the audio mixing process cannot be performed, and the network side will discard the data received from other terminal devices, which will eventually cause the audio mixing to fail.
- the embodiments of the present application provide a resource allocation method, device, and system to optimize the delay in deterministic media transmission to improve the quality of data processing.
- an embodiment of the present application provides a resource allocation method, including: receiving synchronization scheduling indication information associated with a terminal device, where the synchronization scheduling indication information is used to indicate that the terminal device needs to communicate with the user where the terminal device is located. Air interface scheduling resources synchronized by other terminal devices in the group; according to the synchronization scheduling indication information, the air interface scheduling resources are allocated to the terminal device.
- the terminal devices in the user group are allocated air interface scheduling resources of the same or adjacent time units according to the synchronization scheduling instruction information, so that the network side can receive different terminal devices in the user group within the shortest possible time delay.
- the sent data helps to improve the quality of data processing.
- Air interface scheduling resources include: determining the identity of the user group according to the synchronization scheduling indication information; according to the identity of the user group, allocating the air interface scheduling to the terminal device from the air interface resources corresponding to the user group Resources.
- the identifier of the user group is received; and the air interface resource is allocated to the user group according to the identifier of the user group.
- the first reserved resource among the air interface resources is determined, where the first reserved resource and the air interface scheduling resource allocated to the terminal device are in the same or adjacent time unit, so The first reserved resource is used to allocate to other terminal devices in the user group.
- the air interface is allocated to the terminal equipment according to the synchronization scheduling indication information
- the scheduling resource includes: allocating the air interface scheduling resource to the terminal device from the second reserved resource, the second reserved resource and the air interface that has been allocated to one or more terminal devices in the user group
- the scheduling resources are in the same or adjacent time units.
- the synchronization scheduling indication information is determined according to the identity of the user group.
- an embodiment of the present application provides a resource allocation method, including: receiving an identifier of a user group, the user group including at least two terminal devices; determining synchronization scheduling indication information according to the identifier of the user group, the The synchronization scheduling indication information is used to indicate that the terminal equipment in the user group needs to synchronize air interface scheduling resources with other terminal equipment in the user group; and the synchronization scheduling indication information is sent to the access network equipment.
- the session management network element can determine the synchronization scheduling indication information based on the user group identifier, and send the synchronization scheduling indication information to the access network device, and the access network device can be the terminal equipment in the user group according to the synchronization scheduling indication information Allocate air interface scheduling resources of the same or adjacent time units, so that the network side can receive data sent by different terminal devices in the user group within the shortest possible time delay, which helps to improve the quality of data processing.
- the receiving the identifier of the user group includes: receiving the identifier of the user group from a first terminal device, the first terminal device belongs to the user group; or; receiving from an application The identifier of the user group of the functional network element.
- an embodiment of the present application provides a resource allocation method, including: a terminal device sends an identifier of a user group, and the terminal device in the user group needs air interface scheduling resources that are synchronized with other terminal devices in the user group; The terminal device receives air interface scheduling resources from the access network.
- an embodiment of the present application provides a communication device.
- the device may be an access network device or a chip for the access network device.
- the device has the function of realizing the above-mentioned first aspect or each embodiment of the first aspect. This function can be realized by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above-mentioned functions.
- an embodiment of the present application provides a communication device, which may be a session management network element, or a chip used for a session management network element.
- the device has the function of realizing the above-mentioned second aspect or each embodiment of the second aspect. This function can be realized by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above-mentioned functions.
- an embodiment of the present application provides a communication device.
- the device may be a terminal device or a chip for the terminal device.
- the device has the function of realizing the foregoing third aspect or the embodiments of the third aspect. This function can be realized by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above-mentioned functions.
- an embodiment of the present application provides a communication device including a processor and a memory; the memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory to enable The device executes the methods of the above-mentioned first aspect to third aspect or each embodiment of the first aspect to third aspect.
- an embodiment of the present application provides a communication device, including a unit or means for executing each step of the above-mentioned first aspect to the third aspect, or each embodiment of the first aspect to the third aspect.
- an embodiment of the present application provides a communication device, including a processor and an interface circuit, the processor is configured to communicate with other devices through the interface circuit, and execute the first aspect to the third aspect or the first aspect to The method of each embodiment of the third aspect.
- the processor includes one or more.
- an embodiment of the present application provides a communication device, including a processor, configured to be connected to a memory, and used to call a program stored in the memory to execute the first aspect to the third aspect, or the first aspect To the method of each embodiment of the third aspect.
- the memory can be located inside the device or outside the device.
- the processor includes one or more.
- an embodiment of the present application also provides a computer-readable storage medium.
- the computer-readable storage medium stores instructions that, when run on a computer, cause a processor to execute the first to third aspects described above. Aspect, or the method described in each embodiment of the first aspect to the third aspect.
- the embodiments of the present application also provide a computer program product including instructions, which when run on a computer, cause the computer to execute each of the first aspect to the third aspect, or the first aspect to the third aspect. The method described in the embodiment.
- an embodiment of the present application further provides a chip system, including a processor, configured to execute the methods described in the first aspect to the third aspect, or the embodiments of the first aspect to the third aspect.
- an embodiment of the present application also provides a communication system, including: a session management network element and an access network device; the session management network element is configured to receive an identifier of a user group, and the user group includes at least two Terminal equipment; determine synchronization scheduling indication information according to the user group identifier, the synchronization scheduling indication information is used to indicate that the terminal equipment in the user group needs to synchronize air interface scheduling with other terminal equipment in the user group Resource; sending the synchronization scheduling indication information associated with the first terminal device in the user group to the access network equipment; the access network equipment is configured to, according to the synchronization scheduling indication information, be the The first terminal device allocates the air interface scheduling resource.
- the access network device when the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically configured to The synchronization scheduling indication information determines the identity of the user group; according to the identity of the user group, the air interface scheduling resource is allocated to the first terminal device from the air interface resources corresponding to the user group.
- the access network device is further configured to receive the identifier of the user group; according to the identifier of the user group, the air interface resource is allocated to the user group.
- the access network device is further configured to determine a first reserved resource in the air interface resources, and the first reserved resource is the same as the air interface allocated to the first terminal device.
- the scheduling resources are in the same or adjacent time unit, and the first reserved resource is used for allocating to other terminal devices in the user group.
- the access network device when the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically configured to receive a second In the reserved resources, the air interface scheduling resources are allocated to the first terminal device, and the second reserved resources are the same or the same as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group.
- the adjacent time unit when the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically configured to receive a second In the reserved resources, the air interface scheduling resources are allocated to the first terminal device, and the second reserved resources are the same or the same as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group.
- the synchronization scheduling indication information is determined according to the identity of the user group.
- the session management network element is used to receive the user group identifier, specifically including: used to receive the user group identifier from the first terminal device; or; used to receive The identifier of the user group from the application function network element.
- an embodiment of the present application also provides a resource allocation method, including: a session management network element receives an identifier of a user group, the user group includes at least two terminal devices; the session management network element is based on the user The group identifier determines synchronization scheduling indication information, the synchronization scheduling indication information is used to indicate that the terminal equipment in the user group needs to synchronize air interface scheduling resources with other terminal equipment in the user group; the session management network element Send the synchronization scheduling indication information associated with the first terminal equipment in the user group to the access network equipment; the access network equipment allocates the first terminal equipment to the first terminal equipment according to the synchronization scheduling indication information Air interface scheduling resources.
- the access network device when the access network device has not received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically configured to The synchronization scheduling indication information determines the identity of the user group; according to the identity of the user group, the air interface scheduling resource is allocated to the first terminal device from the air interface resources corresponding to the user group.
- the access network device when the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically configured to receive a second In the reserved resources, the air interface scheduling resources are allocated to the first terminal device, and the second reserved resources are the same or the same as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group.
- the adjacent time unit when the access network device has received the synchronization scheduling indication information associated with the terminal device in the user group; the access network device is specifically configured to receive a second In the reserved resources, the air interface scheduling resources are allocated to the first terminal device, and the second reserved resources are the same or the same as the air interface scheduling resources that have been allocated to one or more terminal devices in the user group.
- Figure 1A is a schematic diagram of a 5G network architecture based on a service-oriented architecture
- Figure 1B is a schematic diagram of a 5G network architecture based on a point-to-point interface
- Figure 2 is a schematic diagram of the components involved in the professional audio production communication system
- FIG. 3 is a schematic diagram of time delay caused by multiple terminal devices when sending uplink data
- FIG. 4 is a schematic flowchart of a resource allocation method provided by an embodiment of this application.
- Figure 5A is a schematic diagram of allocating air interface scheduling resources
- FIG. 5B is another schematic diagram of allocating air interface scheduling resources
- FIG. 6 is a schematic diagram of the access network device allocating synchronized air interface scheduling resources for the terminal devices in the user group;
- FIG. 7 is a schematic flowchart of another resource allocation method provided by an embodiment of the application.
- FIG. 8 is a schematic flowchart of another resource allocation method provided by an embodiment of the application.
- FIG. 9 is a schematic diagram of a communication device provided by an embodiment of this application.
- FIG. 10 is a schematic diagram of another communication device provided by an embodiment of this application.
- FIG. 11 is a schematic diagram of an access network device provided by an embodiment of this application.
- FIG. 12 is a schematic diagram of a session management network element provided by an embodiment of this application.
- FIG. 1A it is a schematic diagram of a fifth generation (5G) network architecture based on a service-oriented architecture.
- the 5G network architecture shown in FIG. 1A may include three parts, namely a terminal equipment part, a data network (DN), and an operator network part.
- DN data network
- Operator network part The functions of some of the network elements are briefly introduced below.
- the operator network may include one or more of the following network elements: Authentication Server Function (AUSF) network elements, network exposure function (NEF) network elements, policy control function (policy control) function, PCF) network element, unified data management (UDM) network element, unified database (Unified Data Repository, UDR), network storage function (Network Repository Function, NRF) network element, application function (AF) ) Network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, radio access network (RAN), and user plane Function (user plane function, UPF) network elements, etc.
- AUSF Authentication Server Function
- NEF network exposure function
- policy control policy control function
- PCF policy control function
- UDM unified data management
- UDR Unified Data Repository
- NRF Network Repository Function
- AMF access and mobility management function
- SMS session management function
- RAN radio access network
- UPF user plane Function
- Terminal device is a device with wireless transceiver function. It can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air ( For example, airplanes, balloons, satellites, etc.).
- the terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial control (industrial control) Wireless terminals in ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , Wireless terminals in smart cities, wireless terminals in smart homes, user equipment (UE), media equipment (such as electronic audio equipment installed with communication devices, such as electric guitars, Electronic drums, microphones, etc.) etc.
- VR virtual reality
- AR augmented reality
- industrial control industrial control
- Wireless terminals in wireless terminals in self-driving
- wireless terminals in remote medical wireless terminals in smart grid
- wireless terminals in transportation safety Wireless terminals in smart cities, wireless terminals in smart homes, user equipment (UE), media equipment (such as electronic audio equipment installed with communication devices, such as electric guitars, Electronic drums, microphones, etc.) etc.
- the above-mentioned terminal device may establish a connection with the operator's network through an interface (such as N1, etc.) provided by the operator's network, and use services such as data and/or voice provided by the operator's network.
- the terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN and/or the service provided by a third party.
- the above-mentioned third party may be a service party other than the operator's network and terminal equipment, and may provide other services such as data and/or voice for the terminal equipment.
- the specific form of expression of the above-mentioned third party can be determined according to actual application scenarios, and is not limited here.
- RAN is a sub-network of an operator's network, and an implementation system between service nodes and terminal equipment in the operator's network.
- the terminal device To access the operator's network, the terminal device first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN.
- RAN equipment is a type of equipment that provides wireless communication functions for terminal equipment.
- RAN equipment is also called access network equipment.
- RAN equipment includes but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (RNC), node B (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (BBU) , Transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.
- next-generation base stations gnodeB, gNB
- 5G evolved node B (evolved node B, eNB), radio network controller (RNC), node B (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (BBU) , Transmission point (transmitting and receiving
- the AMF network element is responsible for the mobility management of users, including mobility status management, assigning temporary user identities, authenticating and authorizing users, etc.
- SMF network element with session management, execution of PCF issuing control strategy, selection of UPF, UE internet protocol (IP) address allocation, bearer establishment, modification and release, quality of service (QoS) control And other functions.
- IP internet protocol
- UPF network element supports functions such as interconnecting PDU sessions with data networks, packet routing and forwarding, and data packet inspection.
- the UDM network element is mainly responsible for functions such as management of contract data and user access authorization.
- UDR storing and retrieving contract data, policy data and public structure data, etc.; for UDM, PCF and NEF to obtain relevant data.
- UDR must be able to have different data access authentication mechanisms for different types of data such as contract data and policy data to ensure the security of data access; UDR must be able to return and carry appropriate data for illegal servicing operations or data access requests The failure response for the reason value.
- NEF network elements mainly support network capability opening functions and open network capabilities and services to the outside world; the third generation partnership project (3GPP) NF publishes functions and events to other NFs through NEF. The capabilities and events opened by NF can be safely opened to third-party applications.
- 3GPP third generation partnership project
- NEF uses the standardized interface (Nudr) of the Unified Data Repository (UDR) to store/retrieve structured data.
- Nudr Unified Data Repository
- the AF network element is used to provide certain application layer services to the UE.
- the AF provides services to the UE, it has requirements for QoS policies and charging policies and needs to notify the network.
- AF also needs application-related information fed back from the core network.
- the PCF network element is mainly responsible for policy control functions such as billing, QoS bandwidth guarantee and mobility management, and UE policy decision-making for the session and service flow levels.
- the PCF connected to the AMF and the SMF corresponds to AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management), and may not be the same PCF entity in actual deployment scenarios.
- the NRF network element can be used to provide the network element discovery function, and provide the network element information corresponding to the network element type based on the request of other network elements.
- NRF also provides network element management services, such as network element registration, update, de-registration, and network element status subscription and push.
- AUSF network element Mainly responsible for authenticating users to determine whether users or devices are allowed to access the network.
- a DN is a network located outside the operator's network.
- the operator's network can access multiple DNs.
- a variety of services can be deployed on the DN to provide terminal equipment with services such as data and/or voice.
- DN is the private network of a smart factory.
- the sensors installed in the workshop of the smart factory can be terminal devices.
- a control server for the sensors is deployed in the DN, and the control server can provide services for the sensors.
- the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
- the DN is the internal office network of a company.
- the mobile phones or computers of the employees of the company can be terminal devices, and the mobile phones or computers of the employees can access the information and data resources on the internal office network of the company.
- Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
- the meaning of these interface serial numbers can refer to the meaning defined in the 3GPP standard protocol, which is not limited here.
- FIG. 1B it is a schematic diagram of a 5G network architecture based on a point-to-point interface.
- FIG. 1B For the introduction of the functions of the network elements therein, reference may be made to the introduction of the functions of the corresponding network elements in FIG.
- the main difference between Fig. 1B and Fig. 1A is that the interfaces between the various network elements in Fig. 1B are point-to-point interfaces, rather than service-oriented interfaces.
- N7 The interface between PCF and SMF, which can be used to issue protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control strategy.
- protocol data unit protocol data unit
- PDU protocol data unit
- N15 The interface between PCF and AMF, which can be used to issue UE policies and access control related policies.
- N5 The interface between AF and PCF, which can be used for application service request issuance and network event reporting.
- N4 The interface between SMF and UPF, which can be used to transfer information between the control plane and the user plane, including controlling the issuance of user-oriented forwarding rules, QoS control rules, traffic statistics rules, etc., and user-plane Information reported.
- N11 The interface between SMF and AMF, which can be used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to UE, and transfer radio resource control information sent to RAN.
- N2 The interface between AMF and RAN, which can be used to transfer radio bearer control information from the core network side to the RAN.
- N1 The interface between the AMF and the UE, which can be used to transfer QoS control rules to the UE.
- N8 The interface between AMF and UDM, which can be used for AMF to obtain access and mobility management related subscription data and authentication data from UDM, and AMF to register UE current mobility management related information with UDM, etc.
- N10 The interface between SMF and UDM, which can be used for SMF to obtain session management related subscription data from UDM, and SMF to register UE current session related information with UDM, etc.
- N35 The interface between UDM and UDR, which can be used for UDM to obtain user subscription data information from UDR.
- N36 The interface between the PCF and the UDR, which can be used for the PCF to obtain policy-related contract data and application data-related information from the UDR.
- N12 The interface between AMF and AUSF, which can be used for AMF to initiate an authentication process to AUSF, where SUCI can be carried as a contract identifier;
- N13 The interface between UDM and AUSF, which can be used for AUSF to obtain user authentication vector from UDM to execute the authentication process.
- the aforementioned network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
- a platform for example, a cloud platform.
- the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in the embodiment of the present application.
- the mobility management network element, the session management network element, the policy control network element, the application function network element, the access network device, the network opening function network element, and the user plane network element in the embodiments of the present application may be shown in FIG. 1A or FIG. 1B respectively.
- 6G 6th generation
- the mobility management network element, the session management network element, the policy control network element, the application function network element, the access network device, the network opening function network element, and the user plane network element are respectively the above-mentioned AMF, SMF, PCF, AF, RAN, NEF, UPF are taken as examples for description.
- the terminal device is referred to as UE for short.
- a wireless audio system is a system that uses radio waves instead of wired to transmit audio signals.
- Wireless audio systems usually include wireless microphone systems and wireless back-to-back systems, as well as systems that carry out long-distance audio transmission wirelessly in some specific occasions.
- the wireless audio system has become an indispensable subsystem in today's large-scale performances.
- the wireless audio system can be applied to scenes such as large-scale concerts and concerts.
- the wireless audio system has higher requirements for end-to-end delay (lateny), transmission period, safety and reliability, and sound quality.
- the system includes a wireless audio input, which is denoted here as a microphone.
- the audio is captured at the audio source and sent to the mixing processing server through a wireless connection, which can perform the mixing, transcoding, equalization, or other processing tasks of several audio inputs.
- the result of the audio processing is sent to an output device via a wireless connection, which can be a speaker, a general-purpose device equipped with headphones, or other devices.
- multiple input devices usually generate sound source data.
- Sound source data essential for a performance.
- All the sound source data is then sent to the mixing processing server on the network side through the access network device for sound mixing or mixing processing.
- the access network equipment performs independent scheduling and allocates different air interface scheduling resources to different UEs (where air interface scheduling resources include time resources and frequency resources, and time resources can be used in time units such as time slots ( slot), mini-slot (mini-slot), the mixing processing server mixes the input data of different sound sources, and then sends the mixed effect to each performer through the access network equipment.
- the audio mixing processing server generally needs to wait until the uplink data of the UEs in the same audio mixing group (also referred to as the user group) arrive before starting audio mixing. That is, in the same mixing group, the network side processes the received data according to the deterministic time. Therefore, it must be restricted that the data sent by each UE needs to arrive within a certain time range, otherwise once a certain or a certain If the data of some UEs does not arrive within a certain time range, the audio mixing process cannot be performed, and the network side will discard the data received from other UEs, resulting in audio mixing failure.
- the existing mechanism when multiple UEs belonging to the same audio mixing group need to transmit uplink data through the access network device, they need to transmit the uplink data according to the air interface scheduling resources allocated by the access network device.
- the time resources in the air interface scheduling resources allocated to different UEs of the same audio mixing group may be in time units that are far apart, resulting in a large difference in the time delay for uplink data sent by different UEs to reach the audio mixing processing server. That is, the existing mechanism cannot guarantee the deterministic transmission delay of uplink data sent by UEs in the same audio mixing group, which may result in audio mixing failure of the audio mixing processing server.
- FIG. 3 it is a schematic diagram of a delay caused by multiple UEs when sending uplink data.
- the uplink data of UE1 and the uplink data of UE2 are sent, although the hardware equipment of UE1 and the hardware equipment of UE2 can ensure that they generate data at the same time point.
- the time units allocated by the RAN equipment for UE1 and UE2 may be different and far apart. In this way, during the air interface transmission, the uplink data of UE1 may be sent earlier than the uplink data of UE2, so although the two are sent through the same RAN device , But it is not scheduled in the same or adjacent time unit.
- the transmission path on the network side may also introduce additional time delay, and the time delay between the uplink data of UE1 and the uplink data of UE2 may occur between the mixer equipment. Accumulate, causing the time delay to increase further.
- an embodiment of the present application provides a resource allocation method.
- this method can be executed by RAN equipment or components (such as chips, circuits, etc.) used for RAN equipment; on the network side, it can be executed by SMF or components (such as chips, circuits, etc.) used for SMF.
- RAN equipment or components such as chips, circuits, etc.
- SMF components
- the method includes the following steps:
- Step 401 The SMF receives the identifier of the user group.
- the identifier of the user group is used to indicate at least two UEs.
- the user group may also be referred to as a synchronous scheduling service group, a synchronous scheduling group, and so on.
- any UE in the user group needs air interface scheduling resources synchronized with other UEs in the user group.
- the UEs in the user group have requirements for synchronized air interface scheduling resources with each other.
- the UEs in the user group have synchronization scheduling requirements with each other.
- the synchronized air interface scheduling resource refers to that the air interface scheduling resources allocated to UEs in the same user group are in the same or adjacent time units.
- the time unit may be a slot or a mini-slot, which will be described in a unified manner here, and will not be repeated in the following.
- the SMF may receive the identity of the user group from the first UE, and the first UE belongs to the user group. That is, the first UE requests the allocation of air interface scheduling resources, and at the same time carries the identity of the user group to which it belongs.
- the SMF can receive the UE list and user group identifiers from the AF. That is, the AF requests the allocation of air interface scheduling resources for each UE in the UE list, and at the same time carries the identifier of the user group to which each UE in the UE list belongs.
- Step 402 The SMF determines synchronization scheduling indication information according to the user group identifier, and the synchronization scheduling indication information is used to indicate that the UE in the user group needs to synchronize air interface scheduling resources with other UEs in the user group.
- the corresponding relationship between the identifier of each user group and the synchronization scheduling indication information can be pre-configured on the SMF. After the SMF obtains the identifier of the user group, the SMF can determine the corresponding synchronization scheduling indication information according to the identifier of the user group.
- the corresponding relationship between the identification list of the user group and the synchronization scheduling indication information can be pre-configured on the SMF.
- the user group identifier list contains at least one user group identifier. If the identifier of the user group obtained by the SMF belongs to the list, the SMF can determine the corresponding synchronization scheduling indication information.
- the SMF may also obtain the correspondence between the identifier of the user group and the synchronization scheduling indication information through other network elements (for example, a PCF network element), which is not limited in the embodiment of the present application. It should be noted that UEs in the same user group can correspond to the same synchronization scheduling indication information.
- Step 403 The SMF sends synchronization scheduling indication information to the RAN.
- the RAN can receive the synchronization scheduling indication information.
- Step 404 The RAN allocates air interface scheduling resources for the UE according to the synchronization scheduling indication information.
- the air interface scheduling resource is used for the UE to send uplink data.
- step 401 the SMF is the identifier of the user group received from the first UE
- step 404 the RAN specifically allocates air interface scheduling resources for the first UE. If in step 401, the SMF is the identifier of the user group received from the AF, then in step 404, the RAN specifically allocates air interface scheduling resources to all UEs in the user group in sequence.
- the SMF performs step 403 multiple times according to the number of UEs in the user group, that is, the number of UEs in the user group is multiple, and the SMF sends synchronization scheduling indication information to the RAN multiple times, where each synchronization scheduling indication information is the same as Each UE in the user group is associated, and the RAN allocates air interface scheduling resources for each UE according to the synchronization scheduling indication information.
- the way that the RAN allocates air interface scheduling resources to the UE may be, for example:
- Method 1 The RAN allocates air interface scheduling resources for the UE from idle resources according to the synchronization scheduling indication information.
- the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources, or the RAN determines that it has not received any information associated with the UE in the user group before.
- Synchronize scheduling indication information the RAN can allocate air interface scheduling resources according to the normal process, for example, according to the resource allocation method in the prior art, allocate air interface scheduling resources from idle resources to the UE, that is, the RAN determines the UE according to its own resource allocation.
- the time unit for uplink data scheduling and sends a resource scheduling assignment (Grant) to the UE to notify the UE to send the uplink data in a certain time unit.
- the RAN locally stores the corresponding relationship between the synchronization scheduling indication information and the scheduling resource. Subsequently, the UE sends the uplink data to the RAN according to the air interface scheduling resources allocated by the RAN. After allocating air interface scheduling resources for the UE, the RAN may also allocate reserved resources for other UEs in the user group, where the reserved resources are in the same or adjacent time unit as the air interface scheduling resources allocated to the UE. That is, the reserved resources are applicable to other UEs in the user group.
- the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has not received the synchronization scheduling indication information associated with the UE in the user group before, it refers to , In a certain time range (for example, taking a concert scene as an example, the vocalist, bassist, guitarist, drummer, etc., as UEs in the user group have air-interface scheduling synchronization requirements, and the time from the beginning to the end of a concert Within range, etc.) The RAN determines that the synchronization scheduling indication information associated with the UE in the user group has not been received before. Based on this implementation manner, the air interface scheduling resources for sending data of multiple devices (such as media devices) within a time range can be uniformly scheduled and allocated, so that the delay in deterministic transmission can be reduced.
- the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources according to the received synchronization scheduling indication information, or the RAN determines that it has previously received synchronization associated with UEs in the user group. According to the scheduling indication information, the RAN can allocate air interface scheduling resources for the UE from the reserved resources.
- the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has previously received synchronization scheduling indication information associated with the UEs in the user group, which refers to: In a certain time range (for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc., has air-interface scheduling synchronization requirements, and the time range from the beginning to the end of a concert (Internal etc.) The RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.
- a certain time range for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc.
- the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.
- Method 2 The RAN allocates air interface scheduling resources for the UE from the air interface resources corresponding to the user group according to the synchronization scheduling indication information.
- the air interface resource here may be a fixed scheduling resource corresponding to the user group configured on the RAN, or the air interface resource may also be a fixed scheduling resource allocated by the RAN to the user group when the UE in the user group initiates the registration process.
- the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources, or the RAN determines that it has not received any information associated with the UE in the user group before.
- Synchronize scheduling indication information the RAN can allocate air interface scheduling resources for the UE from the air interface resources corresponding to the user group, that is, the RAN determines the time unit for uplink data scheduling of the UE according to its own resource allocation, and sends resource scheduling to the UE Assignment (Grant) informs the UE to send the uplink data in a certain time unit. Subsequently, the UE sends the uplink data to the RAN according to the resources allocated by the RAN.
- the UE Assignment informs the UE to send the uplink data in a certain time unit.
- the RAN can also allocate reserved resources for other UEs in the user group.
- the reserved resources are the resources in the above air interface resources and are the same as or adjacent to the resources already allocated to the UE. Time unit. That is, the reserved resources are applicable to other UEs in the user group.
- the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has not received the synchronization scheduling indication information associated with the UE in the user group before, it refers to , In a certain time range (for example, taking a concert scene as an example, the vocalist, bassist, guitarist, drummer, etc., as UEs in the user group have air-interface scheduling synchronization requirements, and the time from the beginning to the end of a concert Within range, etc.) The RAN determines that the synchronization scheduling indication information associated with the UE in the user group has not been received before.
- the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources according to the received synchronization scheduling indication information, or the RAN determines that it has previously received synchronization associated with UEs in the user group. According to the scheduling indication information, the RAN can allocate air interface scheduling resources for the UE from the reserved resources.
- the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has previously received synchronization scheduling indication information associated with the UEs in the user group, which refers to: In a certain time range (for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc., has air-interface scheduling synchronization requirements, and the time range from the beginning to the end of a concert (Internal etc.) The RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.
- a certain time range for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc.
- the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.
- UE1 and UE2 belong to the same user group. For example, if UE1 is the first UE in the user group to request the allocation of air interface scheduling resources, the RAN can allocate air interface scheduling resources to UE1 from idle resources or air interface resources corresponding to the user group, and also allocate reserved resources. The resource and the scheduling resource allocated for UE1 are in the same or adjacent time unit. Subsequently, UE2 requests the allocation of air interface scheduling resources again, and the RAN can allocate air interface scheduling resources for UE2 on the above reserved resources. In this way, the scheduling resources in the same or adjacent time units are allocated to UEs in the same user group.
- FIG. 5A and FIG. 5B schematic diagrams of allocating air interface scheduling resources.
- the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit.
- the scheduling resources allocated to UE1 and UE2 are in adjacent time units.
- the RAN allocates UE1 from idle resources (for the above method 1) or the air interface resources corresponding to the user group (for the above method 2) Air interface scheduling resources, and then allocate reserved resources from idle resources (for the above method 1) or air interface resources corresponding to the user group (for the above method 2), and the reserved resources are in the same time unit as the air interface scheduling resources allocated for UE1, At this time, the reserved resources include the air interface scheduling resources allocated to UE2 shown in FIG. 5A and the reserved resources shown in FIG. 5A.
- UE2 in the user group (that is, the second UE in the user group that requests the allocation of air interface scheduling resources) requests the allocation of air interface scheduling resources, and the RAN allocates air interface scheduling resources for UE2 from the above reserved resources, and allocates air interface scheduling resources for UE2 As shown in FIG. 5A, it is in the same time unit as the allocation of air interface scheduling resources for UE1, and the remaining reserved resources at this time are shown in FIG. 5A.
- the RAN allocates UE1 from idle resources (for the above method 1) or the air interface resources corresponding to the user group (for the above method 2) Air interface scheduling resources, and then allocate reserved resources from idle resources (for the above method 1) or air interface resources corresponding to the user group (for the above method 2), and the reserved resources are the same as or adjacent to the air interface scheduling resources allocated for UE1 Time unit.
- the reserved resources include the air interface scheduling resources allocated to UE2 shown in FIG. 5B and the reserved resources shown in FIG. 5B.
- UE2 in the user group (that is, the second UE in the user group that requests the allocation of air interface scheduling resources) requests the allocation of air interface scheduling resources, and the RAN allocates air interface scheduling resources for UE2 from the above reserved resources, and allocates air interface scheduling resources for UE2
- the time unit is adjacent to the allocation of air interface scheduling resources for UE1, and the remaining reserved resources at this time are shown in FIG. 5B.
- the SMF may also send the identifier of the PDU session of the first UE to the RAN, and the PDU session is with the above The session associated with the synchronization service performed by the first UE in the user group.
- the RAN allocates air interface scheduling resources for the PDU session of the first UE according to the synchronization scheduling indication information.
- the SMF may also determine the PDU session corresponding to each UE in the UE list according to the UE list, and Send the PDU session identifier corresponding to each UE in the UE list to the RAN.
- the SMF sends the PDU session identifier corresponding to each UE in the UE list to the RAN multiple times according to the number of UEs in the UE list.
- the PDU session is A session associated with the synchronization service performed by the UE in the above-mentioned user group.
- the RAN allocates air interface scheduling resources to the PDU sessions corresponding to each UE in the UE list according to the synchronization scheduling indication information.
- UE1 and UE2 belong to the same user group, and the schematic diagram of RAN allocating air interface scheduling resources to UE1 and UE2 can refer to FIG. 5A and FIG. 5B.
- the RAN scheduling diagram of the uplink data sent by UE1 and UE2 respectively can refer to Figure 6.
- the uplink data of UE1 and UE2 are placed in the same time unit. Or scheduling in adjacent time, you can try to ensure that the uplink data of UE1 and UE2 are transmitted to the network side at the same time, so that when the network is performing mixing processing, it can receive the uplink data of UE1 and UE2 as much as possible. Helps ensure the effect and quality of the mixing process.
- the network side can determine the synchronization scheduling indication information on the RAN side based on the identity of the user group, and the RAN can allocate the air interface scheduling resources of the same or adjacent time unit to the UEs in the user group according to the synchronization scheduling indication information. Therefore, the network side can receive the data sent by different UEs in the user group within the shortest possible time delay, which helps to improve the quality of data processing.
- the UE sends the identity of the user group in which it is located to the network.
- the network can allocate synchronization scheduling indication information based on the identity of the user group, and send the synchronization scheduling indication information to the RAN.
- the RAN can perform special resource scheduling for the UE according to the synchronization scheduling indication information, that is, perform special resource scheduling for UEs in the same user group. Synchronous scheduling of resources.
- the group ID can be a user group ID (UE group ID) (also called a user group). ID) or service group ID (also called service group ID).
- UE group ID also called a user group
- ID service group ID
- the group ID is used to identify a specific group of UEs.
- Each UE in the group has the same service type (such as media service). ), or the same business requirements (such as synchronization scheduling requirements), etc., which are not limited in the embodiment of the present application.
- the methods for the UE to obtain the group identity include but are not limited to the following two:
- the network In the registration process, the network generates according to the UE's subscription data (for example, generates a group ID according to the service type that the UE subscribes to), or the UE's subscription data contains the group ID to which the UE belongs, and then in the registration acceptance message, Sent by the network to the UE.
- the UE's subscription data for example, generates a group ID according to the service type that the UE subscribes to
- the UE's subscription data contains the group ID to which the UE belongs
- the group identity to which the UE belongs is configured locally on the UE.
- the method includes the following steps:
- Step 701 The UE sends a first request to the AMF.
- the AMF can receive the first request.
- the first request includes the PDU session ID (PDU session ID) and the user group ID, and the PDU session ID is used to identify the PDU session.
- PDU session ID PDU session ID
- the PDU session ID is used to identify the PDU session. Any UE in the user group needs air interface scheduling resources synchronized with other UEs in the user group.
- the UE that sends the first request in step 701 belongs to the user group.
- the UE may send a NAS message (NAS message) to the AMF through the RAN, and the NAS message carries the above-mentioned first request.
- NAS message NAS message
- Step 702 AMF sends a second request to SMF.
- the SMF can receive the second request.
- the second request carries the identifier of the PDU session and the user group identifier.
- Step 703 The SMF determines synchronization scheduling indication information according to the user group identifier.
- the method for implementing the SMF to determine the synchronization scheduling indication information according to the user group identifier may refer to the related description of step 402 in the embodiment corresponding to FIG. 4, which will not be repeated here.
- the SMF and the PCF may further update the relevant policies for session management.
- Step 704 The SMF sends a second response to the AMF.
- the AMF can receive the second response.
- the second response carries the aforementioned synchronization scheduling indication information and also carries the identifier of the PDU session.
- the second response may carry an N2 session management container (N2 SM container), and the N2 SM container may carry the foregoing synchronization scheduling indication information and the identifier of the PDU session.
- the second response may also carry the N1 session management container (N1 SM container), and the N1 SM container carries the identifier of the PDU session and the first response.
- Step 705 AMF sends a third request to the RAN.
- the RAN can receive the third request.
- the third request includes the N2 SM container and the N1 SM container, where the N2 SM container includes the synchronization scheduling indication information and the identifier of the PDU session.
- Step 706 The RAN allocates air interface scheduling resources for the UE according to the synchronization scheduling indication information and the identifier of the PDU session.
- the identifier of the PDU session is used to indicate the PDU session for which air interface scheduling resources need to be allocated.
- the RAN allocates air interface scheduling resources for the UE's PDU session according to the synchronization scheduling indication information and the PDU session identifier, which can be:
- Method 1 The RAN allocates air interface scheduling resources for the UE from idle resources according to the synchronization scheduling indication information and the PDU session identifier.
- the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources, or the RAN determines that it has not received any information associated with the UE in the user group before.
- Synchronous scheduling indication information the RAN can allocate air interface scheduling resources according to the normal process, for example, according to the resource allocation method in the prior art, allocate air interface scheduling resources for the PDU session of the UE from idle resources, that is, the RAN can allocate air interface scheduling resources according to its own resource allocation.
- Grant resource scheduling assignment
- the RAN locally stores the corresponding relationship between the synchronization scheduling indication information and the scheduling resource. Subsequently, the UE sends the uplink data to the RAN according to the air interface scheduling resources allocated by the RAN.
- the RAN can also reserve resources for the allocation of PDU sessions of other UEs in the user group.
- the reserved resources are the same as the air interface scheduling resources of the PDU sessions that have been allocated to the UE. Or adjacent time units. That is, the reserved resources are applicable to PDU sessions of other UEs in the user group. For example, UE1 and UE2 belong to the same user group, and UE1 needs to synchronize air interface scheduling resources with UE2. Referring to FIG.
- FIG. 5A and FIG. 5B it is a schematic diagram of allocating air interface scheduling resources.
- the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit.
- the scheduling resources allocated to UE1 and UE2 are in adjacent time units.
- the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has not received the synchronization scheduling indication information associated with the UE in the user group before, it refers to , In a certain time range (for example, taking a concert scene as an example, the vocalist, bassist, guitarist, drummer, etc., as UEs in the user group have air-interface scheduling synchronization requirements, and the time from the beginning to the end of a concert Within range, etc.) The RAN determines that the synchronization scheduling indication information associated with the UE in the user group has not been received before.
- the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources according to the received synchronization scheduling indication information, or the RAN determines that it has previously received synchronization associated with UEs in the user group. According to the scheduling indication information, the RAN can allocate air interface scheduling resources for the PDU session of the UE from the reserved resources.
- the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has previously received synchronization scheduling indication information associated with the UEs in the user group, which refers to: In a certain time range (for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc., has air-interface scheduling synchronization requirements, and the time range from the beginning to the end of a concert (Internal etc.) The RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.
- a certain time range for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc.
- the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.
- Method 2 The RAN allocates air interface scheduling resources for the UE from the air interface resources corresponding to the user group according to the synchronization scheduling indication information and the identifier of the PDU session.
- the air interface resource here may be a fixed scheduling resource corresponding to the user group configured on the RAN, or the air interface resource may also be a fixed scheduling resource allocated by the RAN to the user group when the UE in the user group initiates the registration process.
- the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources, or the RAN determines that it has not received any information associated with the UE in the user group before.
- Synchronous scheduling indication information the RAN can allocate air interface scheduling resources for the PDU session of the UE from the air interface resources corresponding to the user group, that is, the RAN determines the time unit for uplink data scheduling of the UE according to its own resource allocation, and gives it to the UE.
- Send a resource scheduling assignment (Grant) to notify the UE to send the uplink data in a certain time unit.
- the UE sends the uplink data to the RAN according to the resources allocated by the RAN.
- the RAN can also allocate reserved resources for the PDU sessions of other UEs in the user group.
- the reserved resources are the above-mentioned air interface resources and are different from those already allocated to the UE.
- the air interface scheduling resources of the PDU session are in the same or adjacent time unit. That is, the reserved resources are applicable to PDU sessions of other UEs in the user group. For example, UE1 and UE2 belong to the same user group, and UE1 needs to synchronize air interface scheduling resources with UE2. Referring to FIG. 5A and FIG.
- FIG. 5B it is a schematic diagram of allocating air interface scheduling resources.
- the scheduling resources allocated to UE1 and UE2 on the air interface side are in the same time unit.
- the scheduling resources allocated to UE1 and UE2 are in adjacent time units.
- the RAN determines that the UE is the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group, which refers to: In a certain time range (for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc., has air-interface scheduling synchronization requirements, and the time range from the beginning to the end of a concert (Internal etc.) The RAN determines that it has not received the synchronization scheduling indication information associated with the UE in the user group before.
- a certain time range for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc.
- the RAN determines that it has not received the synchronization scheduling indication information associated with the UE in the user group before.
- the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources according to the received synchronization scheduling indication information, or the RAN determines that it has previously received synchronization associated with UEs in the user group. According to the scheduling indication information, the RAN can allocate air interface scheduling resources for the PDU session of the UE from the reserved resources.
- the RAN determines that the UE is not the first UE in the user group to request the allocation of air interface scheduling resources or the RAN determines that it has previously received synchronization scheduling indication information associated with the UEs in the user group, which refers to: In a certain time range (for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc., has air-interface scheduling synchronization requirements, and the time range from the beginning to the end of a concert (Internal etc.) The RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.
- a certain time range for example, taking a concert scene as an example, the UE in the user group as the lead singer, bassist, guitarist, drummer, etc.
- the RAN determines that it has previously received synchronization scheduling indication information associated with the UE in the user group.
- step 703 different SMFs determine the same synchronization scheduling indication information according to the same user group identifier, so the RAN can be the same user group Different UEs in the internal allocation of synchronized air interface scheduling resources.
- Step 707 The RAN sends air interface scheduling resources to the UE.
- the UE can receive the air interface scheduling resource.
- the air interface scheduling resource is the scheduling resource on the air interface side allocated by the RAN to the UE for sending uplink data.
- the UE can perform local configuration according to the air interface scheduling resources sent by the RAN, and subsequently the UE sends uplink data to the RAN according to the air interface scheduling resources allocated by the RAN.
- the RAN may also send the aforementioned N1 SM container to the UE.
- the UE After receiving the N1 SM container, the UE can obtain the first response and the PDU session identifier therein.
- step 708 the RAN sends a third response to the AMF, and accordingly, the AMF can receive the third response.
- This step 708 is optional.
- the foregoing embodiment may be executed in the PDU session establishment process after the UE is registered to the network.
- the above-mentioned first request may be a PDU session establishment request (PDU Session establishment Request)
- the above-mentioned second request may be a PDU session establishment request (Nsmf_PDUSession_CreateSMContext request)
- the above-mentioned first response may be a PDU session establishment acceptance message.
- the foregoing second response may be a PDU session establishment request response (Nsmf_PDUSession_CreateSMContext response)
- the foregoing third request may be an N2 session request (N2session request)
- the foregoing third response may be an N2 session response (N2 session response) ).
- the foregoing embodiment may be executed in the PDU session modification process after the UE is registered to the network.
- 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 response.
- the above-mentioned second response may be a PDU session update response (Nsmf_PDUSession_UpdateSMContext response)
- the above-mentioned third request may be an N2 session request (N2session request)
- the above-mentioned third response may be an N2 session response (N2 session response) ).
- UE1 and UE2 belong to the same user group, and the schematic diagram of RAN allocating air interface scheduling resources to UE1 and UE2 can refer to FIG. 5A and FIG. 5B.
- the RAN scheduling diagram of the uplink data sent by UE1 and UE2 respectively can refer to Figure 6. If the RAN allocates air interface scheduling resources, the uplink data of UE1 and UE2 are placed in the same time unit. Or scheduling in adjacent time, you can try to ensure that the uplink data of UE1 and UE2 are transmitted to the network side at the same time, so that when the network is performing mixing processing, it can receive the uplink data of UE1 and UE2 as much as possible.
- the UE carries the user group identifier in the first request, and the network side (SMF) can determine the synchronization scheduling indication information on the RAN side based on the user group identifier, and the RAN can assign the UEs in the user group the same according to the synchronization scheduling indication information.
- SMS network side
- the network side can determine the synchronization scheduling indication information on the RAN side based on the user group identifier, and the RAN can assign the UEs in the user group the same according to the synchronization scheduling indication information.
- air interface scheduling resources of adjacent time units so that the network side can receive data sent by different UEs in the user group within the shortest possible time delay, which helps to improve the quality of data processing.
- FIG. 8 it is a schematic flowchart of another resource allocation method provided by an embodiment of this application.
- the AF sends a request to the network, and the request carries the user group identifier.
- the network can determine the synchronization scheduling indication information based on the user group identifier, and then send the synchronization scheduling indication information to the RAN.
- the RAN can perform special resource scheduling for the UE, that is, perform resource synchronization scheduling for UEs in the same user group.
- the group ID can be a user group ID (UE group ID) (also called a user group). ID) or service group ID (also called service group ID).
- UE group ID also called a user group
- ID service group ID
- the group ID is used to identify a specific group of UEs.
- Each UE in the group has the same service type (such as media service). ), or the same business requirements (such as synchronization scheduling requirements), etc., which are not limited in the embodiment of the present application.
- the methods for the UE to obtain the group identity include but are not limited to the following two:
- the network In the registration process, the network generates according to the UE's subscription data (for example, generates a group ID according to the service type that the UE subscribes to), or the UE's subscription data contains the group ID to which the UE belongs, and then in the registration acceptance message, Sent by the network to the UE.
- the UE's subscription data for example, generates a group ID according to the service type that the UE subscribes to
- the UE's subscription data contains the group ID to which the UE belongs
- the group identity to which the UE belongs is configured locally on the UE.
- the method includes the following steps:
- Step 801 The AF sends a policy update request (Npcf_Policy Authorization update request) to the PCF.
- the PCF can receive the policy update request.
- the AF can send the aforementioned policy update request to the PCF through the NEF.
- the policy update request carries a user group identifier and a UE list (UE list) corresponding to the user group identifier.
- Any UE in the user group needs air interface scheduling resources synchronized with other UEs in the user group.
- the UE list contains the identities of one or more UEs, and the identities of the UEs in the UE list belong to the aforementioned user group.
- the PCF triggers a PDU session-related policy update process (PCF initiated SMF Policy Association Modification).
- PCF PCF initiated SMF Policy Association Modification
- the PCF triggers the SMF to update the PDU session of the UE indicated by the UE list, and the PCF sends the user group identifier and the UE list to the SMF.
- the SMF determines the synchronization scheduling indication information according to the user group identifier, and determines the identifier of the PDU session corresponding to each UE indicated by the UE list.
- the method for implementing the SMF to determine the synchronization scheduling indication information according to the user group identifier may refer to the related description of step 402 in the embodiment corresponding to FIG. 4, which will not be repeated here.
- step 804 the SMF sends the synchronization scheduling indication information and the PDU session identifier to the AMF.
- SMF can send synchronization scheduling indication information and PDU session identifier to AMF through Namf_Communication_N1N2MessageTransfer request.
- Step 805 The AMF sends an N2 session request (N2 session request) to the RAN.
- the RAN can receive the N2 session request.
- the N2 session request includes N2 SM container and N1 SM container, where N2 SM container includes synchronization scheduling indication information and PDU session identifier, and N1 SM container carries PDU session identifier and PDU session modification acknowledgement message (PDU Session Modification ack) .
- N2 SM container includes synchronization scheduling indication information and PDU session identifier
- N1 SM container carries PDU session identifier and PDU session modification acknowledgement message (PDU Session Modification ack) .
- Step 806 The RAN allocates air interface scheduling resources for the UE according to the synchronization scheduling indication information and the identifier of the PDU session.
- the identifier of the PDU session is used to indicate the PDU session for which air interface scheduling resources need to be allocated.
- step 803 different SMFs determine the same synchronization scheduling indication information according to the same user group identifier, so the RAN can be the same user group Different UEs in the internal allocation of synchronized air interface scheduling resources.
- Step 807 The RAN sends air interface scheduling resources to the UE.
- the UE can receive the air interface scheduling resource.
- the air interface scheduling resource is the scheduling resource on the air interface side allocated by the RAN to the UE for sending uplink data.
- the UE can perform local configuration according to the air interface scheduling resources sent by the RAN, and subsequently the UE sends uplink data to the RAN according to the air interface scheduling resources allocated by the RAN.
- the RAN may also send the aforementioned N1 SM container to the UE.
- the UE After receiving the N1 SM container, the UE can obtain the PDU session modification response message and the PDU session identifier therein.
- step 808 the RAN sends an N2 session response to the AMF, and accordingly, the AMF can receive the N2 session response.
- This step 808 is optional.
- UE1 and UE2 belong to the same user group, and the schematic diagram of RAN allocating air interface scheduling resources to UE1 and UE2 can refer to FIG. 5A and FIG. 5B.
- the RAN scheduling diagram of the uplink data sent by UE1 and UE2 respectively can refer to Figure 6.
- the uplink data of UE1 and UE2 are placed in the same time unit. Or scheduling in adjacent time, you can try to ensure that the uplink data of UE1 and UE2 are transmitted to the network side at the same time, so that when the network is performing mixing processing, it can receive the uplink data of UE1 and UE2 as much as possible. Helps ensure the effect and quality of the mixing process.
- the AF carries the user group identifier in the policy update request
- the network side can determine the synchronization scheduling indication information on the RAN side based on the user group identifier, and the RAN can assign the UEs in the user group to be in the same position according to the synchronization scheduling indication information.
- air interface scheduling resources of adjacent time units so that the network side can receive data sent by different UEs in the user group within the shortest possible time delay, which helps to improve the quality of data processing.
- each network element described above includes hardware structures and/or software modules corresponding to each function.
- the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.
- the steps or operations implemented by the terminal device can also be implemented by components (such as chips or circuits) configured in the terminal device, corresponding to the steps or operations implemented by the access network device.
- the device 900 includes a receiving unit 910, a sending unit 920, and a distribution unit 930.
- a determining unit 940 is further included.
- the receiving unit 910 is configured to receive synchronization scheduling indication information associated with a terminal device, where the synchronization scheduling indication information is used to indicate that the terminal device needs to synchronize air interface scheduling resources with other terminal devices in the user group where the terminal device is located
- the allocation unit 930 is configured to allocate the air interface scheduling resource to the terminal device according to the synchronization scheduling indication information.
- the sending unit 920 is configured to send the air interface scheduling resource to the terminal device.
- the allocating unit 930 is specifically configured to perform according to the synchronization
- the scheduling indication information determines the identity of the user group; according to the identity of the user group, the air interface scheduling resource is allocated to the terminal device from the air interface resources corresponding to the user group.
- the receiving unit 910 is further configured to receive an identifier of the user group; the allocating unit 930 is further configured to allocate a user group to the user group according to the identifier of the user group. Said air interface resources.
- the determining unit 940 is configured to determine a first reserved resource among the air interface resources, where the first reserved resource is the same or the same as the air interface scheduling resource allocated to the terminal device. Adjacent time unit, the first reserved resource is used to allocate to other terminal devices in the user group.
- the allocating unit 930 is specifically configured to reserve from the second In resources, the air interface scheduling resource is allocated to the terminal device, and the second reserved resource is in the same or adjacent time unit as the air interface scheduling resource that has been allocated to one or more terminal devices in the user group .
- the synchronization scheduling indication information is determined according to the identity of the user group.
- each of the above-mentioned units may also be referred to as a module or a circuit, etc., and each of the above-mentioned units may be provided independently, or may be fully or partially integrated.
- the foregoing receiving unit 910 and sending unit 920 may also be implemented by a transceiver unit, or the receiving unit 910 and the sending unit 920 may also be collectively referred to as a transceiver unit.
- the foregoing allocation unit 930 and the determination unit 940 may also be implemented by a processing unit, or the allocation unit 930 and the determination unit 940 may also be collectively referred to as a processing unit.
- the foregoing receiving unit 910, sending unit 920, or transceiving unit may also be referred to as a communication interface, and the foregoing processing unit may also be referred to as a processor.
- the aforementioned communication device 900 may further include a storage unit for storing data or instructions (also referred to as codes or programs), and each of the aforementioned units may interact or couple with the storage unit to implement the corresponding method or Features.
- the processing unit may read data or instructions in the storage unit, so that the communication device implements the method in the foregoing embodiment.
- FIG. 10 is a schematic diagram of a communication device provided by an embodiment of this application.
- the device is used to implement the steps performed by the corresponding session management network element in the foregoing method embodiment.
- the device 1000 includes a receiving unit 1010, a sending unit 1020, and a determining unit 1030.
- the receiving unit 1010 is configured to receive an identifier of a user group, the user group including at least two terminal devices; the determining unit 1030 is configured to determine synchronization scheduling indication information according to the identifier of the user group, and the synchronization scheduling indication information is used To indicate that the terminal equipment in the user group needs to synchronize air interface scheduling resources with other terminal equipment in the user group; the sending unit 1020 is configured to send the synchronization scheduling instruction information to the access network equipment.
- the receiving unit 1010 is specifically configured to receive an identifier of the user group from a first terminal device, and the first terminal device belongs to the user group; or; receiving from an application function The identifier of the user group of the network element.
- each of the above-mentioned units may also be referred to as a module or a circuit, etc., and each of the above-mentioned units may be provided independently, or may be fully or partially integrated.
- the foregoing receiving unit 1010 and sending unit 1020 may also be implemented by a transceiver unit, or the receiving unit 1010 and the sending unit 1020 may also be collectively referred to as a transceiver unit.
- the above determination unit 1030 may be implemented by a processing unit.
- the foregoing receiving unit 1010, sending unit 1020, or transceiver unit may also be referred to as a communication interface, and the foregoing processing unit may also be referred to as a processor.
- the above-mentioned communication device 1000 may further include a storage unit for storing data or instructions (also referred to as codes or programs), and each of the above-mentioned units may interact or couple with the storage unit to implement the corresponding method or Features.
- the processing unit may read data or instructions in the storage unit, so that the communication device implements the method in the foregoing embodiment.
- each unit in the device can be all implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; part of the units can also be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware.
- each unit can be a separate processing element, or it can be integrated in a certain chip of the device for implementation.
- it can also be stored in the memory in the form of a program, which is called by a certain processing element of the device and executed Features.
- all or part of these units can be integrated together or implemented independently.
- the processing element described here can also become a processor, which can be an integrated circuit with signal processing capabilities.
- each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.
- the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASICs), or, one or Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs), or a combination of at least two of these integrated circuits.
- ASICs application specific integrated circuits
- DSPs digital singnal processors
- FPGAs Field Programmable Gate Arrays
- the unit in the device can be implemented in the form of a processing element scheduler
- the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs.
- CPU central processing unit
- these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
- the above receiving unit is an interface circuit of the device for receiving signals from other devices.
- the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
- the above unit for sending is an interface circuit of the device for sending signals to other devices.
- the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
- the access network equipment includes: an antenna 1110, a radio frequency device 1120, and a baseband device 1130.
- the antenna 1110 is connected to the radio frequency device 1120.
- the radio frequency device 1120 receives the information sent by the terminal device through the antenna 1110, and sends the information sent by the terminal device to the baseband device 1130 for processing.
- the baseband device 1130 processes the information of the terminal device and sends it to the radio frequency device 1120
- the radio frequency device 1120 processes the information of the terminal device and sends it to the terminal device via the antenna 1110.
- the baseband device 1130 may include one or more processing elements 1131, for example, a main control CPU and other integrated circuits, and an interface 1133.
- the baseband device 1130 may also include a storage element 1132, which is used to store programs and data; the interface 1133 is used to exchange information with the radio frequency device 1120, and the interface is, for example, a common public radio interface (CPRI) .
- the above apparatus for access network equipment may be located in the baseband apparatus 1130.
- the above apparatus for access network equipment may be a chip on the baseband apparatus 1130.
- the chip includes at least one processing element and an interface circuit. In performing each step of any method performed by the above access network equipment, the interface circuit is used to communicate with other devices.
- the unit for the access network device to implement each step in the above method can be implemented in the form of a processing element scheduler.
- the device for the access network device includes a processing element and a storage element, and the processing element calls the storage element to store To execute the method executed by the access network device in the above method embodiment.
- the storage element may be a storage element with the processing element on the same chip, that is, an on-chip storage element, or a storage element on a different chip from the processing element, that is, an off-chip storage element.
- the unit for the access network device to implement each step in the above method may be configured as one or more processing elements, and these processing elements are provided on the baseband device.
- the processing elements here may be integrated circuits, such as : One or more ASICs, or, one or more DSPs, or, one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
- the units of the access network equipment that implement each step in the above method can be integrated together and implemented in the form of an SOC.
- the baseband device includes the SOC chip for implementing the above method.
- At least one processing element and storage element can be integrated in the chip, and the processing element can call the stored program of the storage element to implement the method executed by the above access network device; or, at least one integrated circuit can be integrated in the chip to implement The method executed by the above access network device; or, it can be combined with the above implementation.
- the functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.
- the above apparatus for an access network device may include at least one processing element and an interface circuit, wherein at least one processing element is used to execute any method executed by the access network device provided in the above method embodiments.
- the processing element can execute part or all of the steps executed by the access network device in the first way: calling the program stored in the storage element; or in the second way: through the integrated logic circuit of the hardware in the processor element
- a part or all of the steps executed by the access network device can be executed in a manner of combining instructions; of course, part or all of the steps executed by the access network device can also be executed in combination with the first method and the second manner.
- the processing element here is the same as the above description, and it may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or, one or more micro-processing DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
- the storage element can be a memory or a collective term for multiple storage elements.
- the session management network element includes: a processor 1210, an interface 1230, and optionally, a memory 1220.
- the interface 1230 is used to implement communication with other devices.
- the method executed by the session management network element in the above embodiment can be implemented by the processor 1210 calling a program stored in a memory (which may be the memory 1220 in the session management network element or an external memory). That is, the apparatus for the session management network element may include a processor 1210 that calls a program in the memory to execute the method executed by the session management network element in the above method embodiment.
- the processor here may be an integrated circuit with signal processing capability, such as a CPU.
- the apparatus for the session management network element may be realized by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or, one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementations can be combined.
- An embodiment of the present application also provides a communication system, including the communication device as shown in FIG. 9 and the communication device as shown in FIG. 10.
- An embodiment of the present application also provides a communication system, including the access network device shown in FIG. 11 and the session management network element shown in FIG. 12.
- the computer program product includes one or more computer instructions.
- the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
- the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
- the computer instructions may be transmitted from a website, computer, server, or data center.
- the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
- the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
- the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
- the general-purpose processor may be a microprocessor.
- the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
- the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. achieve.
- the aforementioned functions described in this application can be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions can be stored on a computer-readable medium, or transmitted on the computer-readable medium in the form of one or more instructions or codes.
- Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special computer.
- Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other program code media that can be read by general-purpose or special computers, or general-purpose or special processors.
- any connection can be appropriately defined as a computer-readable medium, for example, if the software is from a website, server, or other remote source through a coaxial cable, fiber optic computer, twisted pair, or digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless and microwave are also included in the definition of computer-readable media.
- DSL digital subscriber line
- the said disks and discs include compressed disks, laser disks, optical discs, digital versatile discs (English: Digital Versatile Disc, abbreviated as: DVD), floppy disks and Blu-ray discs.
- Disks usually copy data with magnetism.
- Discs usually use lasers to copy data optically.
- the combination of the above can also be contained in a computer readable medium.
- the functions described in this application can be implemented by hardware, software, firmware, or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
- the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
- the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请实施例提供资源分配方法、装置及***。该方法包括:接收与终端设备关联的同步调度指示信息,所述同步调度指示信息用于指示所述终端设备需要与所述终端设备所在的用户组内的其它终端设备同步的空口调度资源;根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源。该方案中,根据该同步调度指示信息为用户组内的终端设备分配相同或相邻时间单元的空口调度资源,从而网络侧可以在尽可能短的时延内接收到用户组内的不同终端设备发送的数据,有助于提升数据处理的质量。
Description
本申请涉及通信技术领域,尤其涉及资源分配方法、装置及***。
在一些应用场景,多个终端设备之间需要协同执行某个业务,这些终端设备需要各自将数据发送到网络侧,由网络侧根据各个终端设备上报的数据进行综合处理。以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为终端设备,这些终端设备属于同一个混音组(也可以称为用户组),需要分别通过移动网络将各自产生的声音数据发送至网络侧,然后网络侧根据收集的各个声音数据按照确定性时间(deterministic time)进行混音处理,从而将最终的处理结果进行输出,并返回给各个终端设备。
同一个混音组中,由于网络侧是按照确定性时间来处理接收到的数据,因此需要各个终端设备发送的数据在确定的某个时间范围内到达,否则一旦某个或某些终端设备发送的数据没有在确定的时间范围内到达,就无法执行混音处理,并且网络侧将会丢弃从其他终端设备接收到的数据,最终导致混音失败。
因此,如何优化确定性媒体传输中的时延,以提升数据处理的质量,是有待解决的问题。
发明内容
本申请实施例提供资源分配方法、装置及***,用以优化确定性媒体传输中的时延,以提升数据处理的质量。
第一方面,本申请实施例提供一种资源分配方法,包括:接收与终端设备关联的同步调度指示信息,所述同步调度指示信息用于指示所述终端设备需要与所述终端设备所在的用户组内的其它终端设备同步的空口调度资源;根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源。
上述方案中,根据该同步调度指示信息为用户组内的终端设备分配相同或相邻时间单元的空口调度资源,从而网络侧可以在尽可能短的时延内接收到用户组内的不同终端设备发送的数据,有助于提升数据处理的质量。
在一种可能的实现方法中,当未收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源,包括:根据所述同步调度指示信息,确定所述用户组的标识;根据所述用户组的标识,从所述用户组对应的空口资源中为所述终端设备分配所述空口调度资源。
在一种可能的实现方法中,接收所述用户组的标识;根据所述用户组的标识,为所述用户组分配所述空口资源。
在一种可能的实现方法中,确定所述空口资源中的第一预留资源,所述第一预留资源与分配给所述终端设备的空口调度资源处于相同或相邻的时间单元,所述第一预留资源用于分配给所述用户组内的其他终端设备。
在一种可能的实现方法中,当收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源,包括:从第二预留资源中,为所述终端设备分配所述空口调度资源,所述第二预留资源与已经分配给所述用户组内的一个或多个终端设备的空口调度资源处于相同或相邻的时间单元。
在一种可能的实现方法中,所述同步调度指示信息是根据所述用户组的标识确定的。
第二方面,本申请实施例提供一种资源分配方法,包括:接收用户组的标识,所述用户组包括至少两个终端设备;根据所述用户组的标识,确定同步调度指示信息,所述同步调度指示信息用于指示所述用户组内的终端设备需要与所述用户组内的其它终端设备同步的空口调度资源;向接入网设备发送所述同步调度指示信息。
上述方案中,会话管理网元可以基于用户组的标识确定同步调度指示信息,并向接入网设备发送同步调度指示信息,接入网设备可以根据该同步调度指示信息为用户组内的终端设备分配相同或相邻时间单元的空口调度资源,从而网络侧可以在尽可能短的时延内接收到用户组内的不同终端设备发送的数据,有助于提升数据处理的质量。
在一种可能的实现方法中,所述接收用户组的标识,包括:接收来自第一终端设备的所述用户组的标识,所述第一终端设备属于所述用户组;或者;接收来自应用功能网元的所述用户组的标识。
第三方面,本申请实施例提供一种资源分配方法,包括:终端设备发送用户组的标识,所述用户组内的终端设备需要与所述用户组内的其他终端设备同步的空口调度资源;所述终端设备从接入网接收空口调度资源。
第四方面,本申请实施例提供一种通信装置,该装置可以是接入网设备,还可以是用于接入网设备的芯片。该装置具有实现上述第一方面或第一方面的各实施例的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面,本申请实施例提供一种通信装置,该装置可以是会话管理网元,还可以是用于会话管理网元的芯片。该装置具有实现上述第二方面或第二方面的各实施例的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面,本申请实施例提供一种通信装置,该装置可以是终端设备,还可以是用于终端设备的芯片。该装置具有实现上述第三方面或第三方面的各实施例的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面,本申请实施例提供一种通信装置,包括处理器和存储器;该存储器用于存储计算机执行指令,当该装置运行时,该处理器执行该存储器存储的该计算机执行指令,以使该装置执行如上述第一方面至第三方面、或第一方面至第三方面的各实施例的方法。
第八方面,本申请实施例提供一种通信装置,包括用于执行上述第一方面至第三方面、或第一方面至第三方面的各实施例的各个步骤的单元或手段(means)。
第九方面,本申请实施例提供一种通信装置,包括处理器和接口电路,所述处理器用于通过接口电路与其它装置通信,并执行上述第一方面至第三方面、或第一方面至第三方面的各实施例的方法。该处理器包括一个或多个。
第十方面,本申请实施例提供一种通信装置,包括处理器,用于与存储器相连,用于调用所述存储器中存储的程序,以执行上述第一方面至第三方面、或第一方面至第三方面的各实施例的方法。该存储器可以位于该装置之内,也可以位于该装置之外。且该处理器包括一个或多个。
第十一方面,本申请实施例还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得处理器执行上述第一方面至第三方面、或第一方面至第三方面的各实施例所述的方法。
第十二方面,本申请实施例还提供一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第一方面至第三方面、或第一方面至第三方面的各实施例所述的方法。
第十三方面,本申请实施例还提供一种芯片***,包括:处理器,用于执行上述第一方面至第三方面、或第一方面至第三方面的各实施例所述的方法。
第十四方面,本申请实施例还提供一种通信***,包括:会话管理网元和接入网设备;所述会话管理网元,用于接收用户组的标识,所述用户组包括至少两个终端设备;根据所述用户组的标识,确定同步调度指示信息,所述同步调度指示信息用于指示所述用户组内的终端设备需要与所述用户组内的其它终端设备同步的空口调度资源;向所述接入网设备发送与所述用户组内的第一终端设备关联的所述同步调度指示信息;所述接入网设备,用于根据所述同步调度指示信息,为所述第一终端设备分配所述空口调度资源。
在一种可能的实现方法中,当所述接入网设备未收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述接入网设备,具体用于根据所述同步调度指示信息,确定所述用户组的标识;根据所述用户组的标识,从所述用户组对应的空口资源中为所述第一终端设备分配所述空口调度资源。
在一种可能的实现方法中,所述接入网设备,还用于接收所述用户组的标识;根据所述用户组的标识,为所述用户组分配所述空口资源。
在一种可能的实现方法中,所述接入网设备,还用于确定所述空口资源中的第一预留资源,所述第一预留资源与分配给所述第一终端设备的空口调度资源处于相同或相邻的时间单元,所述第一预留资源用于分配给所述用户组内的其他终端设备。
在一种可能的实现方法中,当所述接入网设备收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述接入网设备,具体用于从第二预留资源中,为所述第一终端设备分配所述空口调度资源,所述第二预留资源与已经分配给所述用户组内的一个或多个终端设备的空口调度资源处于相同或相邻的时间单元。
在一种可能的实现方法中,所述同步调度指示信息是根据所述用户组的标识确定的。
在一种可能的实现方法中,所述会话管理网元,用于接收用户组的标识,具体包括:用于接收来自所述第一终端设备的所述用户组的标识;或者;用于接收来自应用功能网元的所述用户组的标识。
第十五方面,本申请实施例还提供一种资源分配方法,包括:会话管理网元接收用户组的标识,所述用户组包括至少两个终端设备;所述会话管理网元根据所述用户组的标识,确定同步调度指示信息,所述同步调度指示信息用于指示所述用户组内的终端设备需要与所述用户组内的其它终端设备同步的空口调度资源;所述会话管理网元向接入网设备发送与所述用户组内的第一终端设备关联的所述同步调度指示信息;所述接入网设备根据所述 同步调度指示信息,为所述第一终端设备分配所述空口调度资源。
在一种可能的实现方法中,当所述接入网设备未收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述接入网设备,具体用于根据所述同步调度指示信息,确定所述用户组的标识;根据所述用户组的标识,从所述用户组对应的空口资源中为所述第一终端设备分配所述空口调度资源。
在一种可能的实现方法中,当所述接入网设备收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述接入网设备,具体用于从第二预留资源中,为所述第一终端设备分配所述空口调度资源,所述第二预留资源与已经分配给所述用户组内的一个或多个终端设备的空口调度资源处于相同或相邻的时间单元。
图1A为基于服务化架构的5G网络架构示意图;
图1B为基于点对点接口的5G网络架构示意图;
图2为专业音频制作通信***中涉及的组成部分示意图;
图3为多个终端设备在发送上行数据时产生时延的示意图;
图4为本申请实施例提供的一种资源分配方法流程示意图;
图5A为分配空口调度资源的一个示意图;
图5B为分配空口调度资源的又一个示意图;
图6为接入网设备为具有用户组内的终端设备分配同步的空口调度资源示意图;
图7为本申请实施例提供的又一种资源分配方法流程示意图;
图8为本申请实施例提供的又一种资源分配方法流程示意图;
图9为本申请实施例提供的一种通信装置示意图;
图10为本申请实施例提供的又一种通信装置示意图;
图11为本申请实施例提供的一种接入网设备示意图;
图12为本申请实施例提供的一种会话管理网元示意图。
为了使本申请实施例的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施例作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或***实施例中。其中,在本申请实施例的描述中,除非另有说明,“多个”的含义是两个或两个以上。
如图1A所示,为基于服务化架构的第五代(5th generation,5G)网络架构示意图。图1A所示的5G网络架构中可包括三部分,分别是终端设备部分、数据网络(data network,DN)和运营商网络部分。下面对其中的部分网元的功能进行简单介绍说明。
其中,运营商网络可包括以下网元中的一个或多个:鉴权服务器功能(Authentication Server Function,AUSF)网元、网络开放功能(network exposure function,NEF)网元、策略控制功能(policy control function,PCF)网元、统一数据管理(unified data management,UDM)网元、统一数据库(Unified Data Repository,UDR)、网络存储功能(Network Repository Function,NRF)网元、应用功能(application function,AF)网元、接入与移动性管理功能 (access and mobility management function,AMF)网元、会话管理功能(session management function,SMF)网元、无线接入网(radio access network,RAN)以及用户面功能(user plane function,UPF)网元等。上述运营商网络中,除无线接入网部分之外的部分可以称为核心网络部分。
终端设备(terminal device),是一种具有无线收发功能的设备,可以部署在陆地上,包括室内或室外、手持或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality,VR)终端、增强现实(augmented reality,AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、用户设备(user equipment,UE)、媒体设备(如安装有通信装置的电音设备,如电音吉他、电音架子鼓、麦克风等)等。
上述终端设备可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接,使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问DN,使用DN上部署的运营商业务,和/或第三方提供的业务。其中,上述第三方可为运营商网络和终端设备之外的服务方,可为终端设备提供他数据和/或语音等服务。其中,上述第三方的具体表现形式,具体可根据实际应用场景确定,在此不做限制。
RAN是运营商网络的子网络,是运营商网络中业务节点与终端设备之间的实施***。终端设备要接入运营商网络,首先是经过RAN,进而可通过RAN与运营商网络的业务节点连接。RAN设备,是一种为终端设备提供无线通信功能的设备,RAN设备也称为接入网设备。RAN设备包括但不限于:5G中的下一代基站(g nodeB,gNB)、演进型节点B(evolved node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved nodeB,或home node B,HNB)、基带单元(baseBand unit,BBU)、传输点(transmitting and receiving point,TRP)、发射点(transmitting point,TP)、移动交换中心等。
AMF网元,负责用户的移动性管理,包括移动状态管理,分配用户临时身份标识,认证和授权用户等。
SMF网元,具有会话管理、PCF下发控制策略的执行、UPF的选择、UE互联网协议(internet protocol,IP)地址分配、承载的建立、修改和释放,服务质量(Quality of Service,QoS)控制等功能。
UPF网元,支持将PDU会话与数据网络互连、分组路由和转发、数据包检测等功能。
UDM网元,主要负责管理签约数据、用户接入授权等功能。
UDR,存储和检索签约数据、策略数据和公共架构数据等;供UDM、PCF和NEF获取相关数据。UDR要能够针对不同类型的数据如签约数据、策略数据有不同的数据接入鉴权机制,以保证数据接入的安全性;UDR对于非法的服务化操作或者数据接入请求要能够返回携带合适原因值的失败响应。
NEF网元,主要支持网络能力开放功能,对外开放网络能力和服务;第三代合作伙伴计划(3rd generation partnership project,3GPP)NF通过NEF向其他NF发布功能和事件。 NF开放的能力和事件可以安全地开放给第三方应用。NEF使用统一数据存储库(UDR)的标准化接口(Nudr)将结构化数据进行存储/检索。将AF的交换信息与内部网络功能的交换信息进行翻译。
AF网元,用于向UE提供某种应用层服务,AF在向UE提供服务时,对QoS策略和计费策略有要求,且需要通知网络。同时,AF也需要核心网反馈的应用相关的信息。
PCF网元,主要负责针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、UE策略决策等策略控制功能。该架构中,AMF与SMF所连接的PCF分别对应AM PCF(PCF for Access and Mobility Control)和SM PCF(PCF for Session Management),在实际部署场景中可能不是同一个PCF实体。
NRF网元,可用于提供网元发现功能,基于其他网元的请求,提供网元类型对应的网元信息。NRF还提供网元管理服务,如网元注册、更新、去注册以及网元状态订阅和推送等。
AUSF网元:主要负责对用户进行鉴权,以确定是否允许用户或设备接入网络。
DN,是位于运营商网络之外的网络,运营商网络可以接入多个DN,DN上可部署多种业务,可为终端设备提供数据和/或语音等服务。例如,DN是某智能工厂的私有网络,智能工厂安装在车间的传感器可为终端设备,DN中部署了传感器的控制服务器,控制服务器可为传感器提供服务。传感器可与控制服务器通信,获取控制服务器的指令,根据指令将采集的传感器数据传送给控制服务器等。又例如,DN是某公司的内部办公网络,该公司员工的手机或者电脑可为终端设备,员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1A中Nausf、Nnef、Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4,以及N6为接口序列号。这些接口序列号的含义可参见3GPP标准协议中定义的含义,在此不做限制。
如图1B所示,为基于点对点接口的5G网络架构示意图,其中的网元的功能的介绍可以参考图1A中对应的网元的功能的介绍,不再赘述。图1B与图1A的主要区别在于:图1B中的各个网元之间的接口是点对点的接口,而不是服务化的接口。
在图1B所示的架构中,各个网元之间的接口名称及功能如下:
1)、N7:PCF与SMF之间的接口,可以用于下发协议数据单元(protocol data unit,PDU)会话粒度以及业务数据流粒度控制策略。
2)、N15:PCF与AMF之间的接口,可以用于下发UE策略及接入控制相关策略。
3)、N5:AF与PCF之间的接口,可以用于应用业务请求下发以及网络事件上报。
4)、N4:SMF与UPF之间的接口,可以用于控制面与用户面之间传递信息,包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
5)、N11:SMF与AMF之间的接口,可以用于传递RAN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给RAN的无线资源控制信息等。
6)、N2:AMF与RAN之间的接口,可以用于传递核心网侧至RAN的无线承载控制信息等。
7)、N1:AMF与UE之间的接口,可以用于向UE传递QoS控制规则等。
8)、N8:AMF与UDM间的接口,可以用于AMF向UDM获取接入与移动性管理相 关签约数据与鉴权数据,以及AMF向UDM注册UE当前移动性管理相关信息等。
9)、N10:SMF与UDM间的接口,可以用于SMF向UDM获取会话管理相关签约数据,以及SMF向UDM注册UE当前会话相关信息等。
10)、N35:UDM与UDR间的接口,可以用于UDM从UDR中获取用户签约数据信息。
11)、N36:PCF与UDR间的接口,可以用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
12)、N12:AMF和AUSF间的接口,可以用于AMF向AUSF发起鉴权流程,其中可携带SUCI作为签约标识;
13)、N13:UDM与AUSF间的接口,可以用于AUSF向UDM获取用户鉴权向量,以执行鉴权流程。
可以理解的是,上述网元或者功能既可以是硬件设备中的网络元件,也可以是在专用硬件上运行软件功能,或者是平台(例如,云平台)上实例化的虚拟化功能。可选的,上述网元或者功能可以由一个设备实现,也可以由多个设备共同实现,还可以是一个设备内的一个功能模块,本申请实施例对此不作具体限定。
本申请实施例中的移动性管理网元、会话管理网元、策略控制网元、应用功能网元、接入网设备、网络开放功能网元、用户面网元分别可以是图1A或图1B中的AMF、SMF、PCF、AF、RAN、NEF、UPF,也可以是未来通信如第六代(6th generation,6G)网络中具有上述AMF、SMF、PCF、AF、RAN、NEF、UPF的功能的网元,本申请实施例对此不限定。为方便说明,本申请实施例以移动性管理网元、会话管理网元、策略控制网元、应用功能网元、接入网设备、网络开放功能网元、用户面网元分别为上述AMF、SMF、PCF、AF、RAN、NEF、UPF为例进行说明。进一步地,本申请实施例中将终端设备简称为UE。
无线音频***是使用无线电波代替有线方式传输音频信号的***。无线音频***通常包括无线传声器***和无线返听***,也包括在一些特定场合中通过无线方式进行远距离音频传输的***。无线音频***在当下的大型演出中已成为必不可少的子***。
无线音频***可以应用于大型音乐会、演唱会等场景,无线音频***对于端到端时延(lateny)、传输周期、安全性可靠性以及声音的质量具有较高的要求。
如图2所示,为专业音频制作通信***中涉及的组成部分示意图。一方面,该***包括无线音频输入,在此将其表示为麦克风。在音频源处捕获音频,并通过无线连接发送到混音处理服务器,该服务器可以执行几种音频输入的混合,代码转换,均衡或其他处理任务。音频处理的结果通过无线连接发送至输出设备,该输出设备可以是扬声器,配备耳机的通用设备或其他设备。
比如,在实际演出过程中,通常是多个输入设备生成声源数据,如在一个音乐会演出活动中,有贝斯手,吉他手,架子鼓手以及主唱,他们每一个人的输入设备都是整场演出必不可少的声源数据。所有的声源数据再通过接入网设备发送到网络侧的混音处理服务器做合音或混音处理。当不同的UE发送上行数据时,接入网设备独立进行调度,为不同的UE分配不同的空口调度资源(其中,空口调度资源包括时间资源和频率资源,时间资源可以用时间单元如时隙(slot)、迷你时隙(mini-slot)来表示),混音处理服务器将输入的 不同声源数据进行混音处理,然后将混音后的效果通过接入网设备发送到每一个表演者的耳返设备中,这样每一个表演者就能听到现场表演的效果。混音处理服务器一般需要等到同一混音组(也称为用户组)的UE的上行数据都到达时,才开始进行混音。也即,在同一个混音组中,网络侧是按照确定性时间来处理接收到的数据,因此必须限定各个UE发送的数据需要在确定的某个时间范围内到达,否则一旦某个或某些UE的数据没有在确定的时间范围内到达,就无法执行混音处理,网络侧将会丢弃从其他UE接收到的数据,最终导致混音失败。
现有机制中,属于同一个混音组的多个UE需要通过接入网设备发送上行数据时,需要分别按照接入网设备分配的空口调度资源来传输上行数据。同一个混音组的不同UE被分配的空口调度资源中的时间资源可能处于相隔较远的时间单元,导致不同的UE发送的上行数据到达混音处理服务器的时延相差较大。也即,现有机制无法保证同一混音组的UE发送的上行数据的确定性传输时延,因而可能导致混音处理服务器混音失败。
如图3所示,为多个UE在发送上行数据时产生时延的示意图。假设UE1和UE2已经做了时间同步(二者的时间相同),UE1的上行数据与UE2的上行数据在发送时,尽管UE1的硬件设备和UE2的硬件设备可以保证各自在相同时间点生成数据,但是RAN设备为UE1和UE2分配的时间单元可能不一样并且相隔较远,这样在空口传输过程中,UE1的上行数据可能早于UE2的上行数据发送,因此二者虽然是通过同一个RAN设备发送,但是却不在相同或相邻的时间单元调度。这样导致UE1的上行数据和UE2的上行数据之间产生了较大时延。此外,后续RAN设备在传输UE1和UE2的上行数据的时候,网络侧的传输路径也可能额外引入时延,混音器设备接收UE1的上行数据和UE2的上行数据之间的时延可能会发生累积,造成时延进一步增大。
为解决上述问题,基于图1A或图1B所示的网络架构,如图4所示,本申请实施例提供一种资源分配方法。该方法在RAN侧,可以由RAN设备或用于RAN设备的部件(如芯片、电路等)执行;在网络侧,可以由SMF或用于SMF的部件(如芯片、电路等)执行。为便于说明,下面以RAN设备和SMF执行该方法为例进行说明。
该方法包括以下步骤:
步骤401,SMF接收用户组的标识。
该用户组的标识用于指示至少两个UE。可选的,该用户组也可以称为同步调度业务组、同步调度组等。
该用户组内的任意一个UE需要与该用户组内的其他UE同步的空口调度资源。或者理解为,该用户组内的UE相互之间具有同步的空口调度资源的需求。或者理解为,该用户组内的UE相互之间具有同步调度的需求。其中,同步的空口调度资源指的是,为同一用户组内的UE分配的空口调度资源处于相同或相邻的时间单元。
本申请实施例中,时间单元可以是时隙(slot)、或迷你时隙(mini-slot),这里统一说明,后续不再赘述。
作为一种实现方式,SMF可以接收来自第一UE的用户组的标识,该第一UE属于该用户组。也即,第一UE请求分配空口调度资源,同时携带自己所属的用户组的标识。
作为又一种实现方式,SMF可以接收来自AF的UE列表和用户组的标识。也即,AF 请求为UE列表的各个UE分配空口调度资源,同时携带该UE列表的各个UE所属的用户组的标识。
步骤402,SMF根据用户组的标识,确定同步调度指示信息,该同步调度指示信息用于指示所述用户组内的UE需要与所述用户组内的其它UE同步的空口调度资源。
作为一种实现方式,SMF上可以预先配置每一个用户组的标识与同步调度指示信息之间的对应关系。SMF获取用户组的标识之后,SMF可以根据用户组的标识,确定对应的同步调度指示信息。
作为又一种实现方式,SMF上可以预先配置用户组的标识列表与同步调度指示信息之间的对应关系。用户组的标识列表包含至少一个用户组的标识。如果SMF获取的用户组的标识属于该列表内,那么SMF可以确定对应的同步调度指示信息。
作为又一种实现方式,SMF还可以通过其他网元(例如PCF网元)获取用户组的标识与同步调度指示信息之间的对应关系,本申请实施例不做限定。需要说明的是,同一个用户组内的UE可以对应相同的同步调度指示信息。
步骤403,SMF向RAN发送同步调度指示信息。相应的,RAN可以接收到该同步调度指示信息。
步骤404,RAN根据同步调度指示信息,为UE分配空口调度资源。其中,该空口调度资源用于UE发送上行数据。
需要说明的是,若上述步骤401中,SMF是从第一UE接收到用户组的标识,则该步骤404中,RAN具体为该第一UE分配空口调度资源。若上述步骤401中,SMF是从AF接收到用户组的标识,则该步骤404中,RAN具体为该用户组内的所有UE依次分配空口调度资源。可以理解为,SMF根据用户组内UE的数量多次执行步骤403,即用户组内UE的数量为多个,SMF向RAN多次发送同步调度指示信息,其中,每一个同步调度指示信息均与用户组内的每一个UE关联,RAN根据同步调度指示信息,为每一个UE分配空口调度资源。
RAN为UE分配空口调度资源的方式,比如可以是:
方法一,RAN根据同步调度指示信息从空闲资源中,为UE在分配空口调度资源。
比如,RAN根据接收到的同步调度指示信息,确定该UE是用户组内的第一个请求分配空口调度资源的UE,或者,RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息,则RAN可以按照正常流程分配空口调度资源,比如按照现有技术中的资源分配方式,从空闲资源中为该UE分配空口调度资源,即RAN根据自身的资源分配情况确定该UE的上行数据调度的时间单元,并给UE发送资源调度指派(Grant),通知UE在某个时间单元发送该上行数据。同时RAN本地保存该同步调度指示信息与该调度资源的对应关系。后续UE将上行数据按照RAN分配的空口调度资源发送给RAN。在为UE分配空口调度资源之后,RAN还可以为用户组内的其他UE分配预留资源,该预留资源与已经分配给该UE的空口调度资源处于相同或相邻的时间单元。即,该预留资源适用于用户组内的其他UE。
需要说明的是,RAN确定该UE是用户组内的第一个请求分配空口调度资源的UE或者RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息,指的是,在某个时间范围内(比如,以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为用户组内的UE具有空口调度同步需求,在一场演唱会的开始到结束的时间范围内等)RAN确定之 前未收到过与所述用户组内的UE关联的同步调度指示信息。基于该实现方式,可以对一个时间范围内的多个设备(如媒体设备)发送数据的空口调度资源进行统一调度和分配,从而可以实现减少确定性传输中的时延。
再比如,RAN根据接收到的同步调度指示信息确定该UE不是用户组内的第一个请求分配空口调度资源的UE,或者,RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,则RAN可以从该预留资源中,为该UE分配空口调度资源。
需要说明的是,RAN确定该UE不是用户组内的第一个请求分配空口调度资源的UE或者RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,指的是,在某个时间范围内(比如,以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为用户组内的UE具有空口调度同步需求,在一场演唱会的开始到结束的时间范围内等)RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息。
方法二,RAN根据同步调度指示信息从用户组对应的空口资源中,为该UE分配空口调度资源。
这里的空口资源可以是RAN上配置的与用户组对应的固定调度资源,或者空口资源也可以是用户组内的UE发起注册流程时,RAN为该用户组分配的固定调度资源。
比如,RAN根据接收到的同步调度指示信息,确定该UE是用户组内的第一个请求分配空口调度资源的UE,或者,RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息,则RAN可以从该用户组对应的空口资源中为该UE分配空口调度资源,即RAN根据自身的资源分配情况确定该UE的上行数据调度的时间单元,并给UE发送资源调度指派(Grant),通知UE在某个时间单元发送该上行数据。后续UE将上行数据按照RAN分配的资源发送给RAN。在为UE分配空口调度资源之后,RAN还可以为用户组内的其他UE分配预留资源,该预留资源是上述空口资源中的资源,且与已经分配给该UE的资源处于相同或相邻的时间单元。即,该预留资源适用于用户组内的其他UE。
需要说明的是,RAN确定该UE是用户组内的第一个请求分配空口调度资源的UE或者RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息,指的是,在某个时间范围内(比如,以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为用户组内的UE具有空口调度同步需求,在一场演唱会的开始到结束的时间范围内等)RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息。
再比如,RAN根据接收到的同步调度指示信息确定该UE不是用户组内的第一个请求分配空口调度资源的UE,或者,RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,则RAN可以从该预留资源中,为该UE分配空口调度资源。
需要说明的是,RAN确定该UE不是用户组内的第一个请求分配空口调度资源的UE或者RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,指的是,在某个时间范围内(比如,以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为用户组内的UE具有空口调度同步需求,在一场演唱会的开始到结束的时间范围内等)RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息。
作为一个示例,UE1和UE2属于同一个用户组。比如,UE1是用户组内的第一个请求分配空口调度资源的UE,则RAN可以从空闲资源或用户组对应的空口资源中为UE1分配空口调度资源,同时还分配预留资源,该预留资源与为UE1分配的调度资源处于相同或相邻的时间单元。后续,UE2再请求分配空口调度资源,则RAN可以在上述预留资源 上为UE2分配空口调度资源。从而实现了为处于同一个用户组的UE分配处于相同或相邻时间单元的调度资源。
例如,参考图5A和图5B,为分配空口调度资源的示意图。图5A中,在空口侧为UE1和UE2分配的调度资源处于相同的时间单元。图5B中,为UE1和UE2分配的调度资源处于相邻的时间单元。
参考图5A,假设UE1是用户组内的第一个请求分配空口调度资源的UE,则RAN从空闲资源(针对上述方法一)或用户组对应的空口资源(针对上述方法二)中为UE1分配空口调度资源,然后从空闲资源(针对上述方法一)或用户组对应的空口资源(针对上述方法二)中分配预留资源,该预留资源与为UE1分配空口调度资源处于相同的时间单元,此时,该预留资源包括图5A中所示的为UE2分配的空口调度资源和图5A中所示的预留资源。后续,用户组内UE2(即用户组内的第二个请求分配空口调度资源的UE)请求分配空口调度资源,则RAN从上述预留资源中为UE2分配空口调度资源,为UE2分配空口调度资源如图5A所示,与为UE1分配空口调度资源处于相同的时间单元,此时剩下的预留资源如图5A所示。
参考图5B,假设UE1是用户组内的第一个请求分配空口调度资源的UE,则RAN从空闲资源(针对上述方法一)或用户组对应的空口资源(针对上述方法二)中为UE1分配空口调度资源,然后从空闲资源(针对上述方法一)或用户组对应的空口资源(针对上述方法二)中分配预留资源,该预留资源与为UE1分配空口调度资源处于相同或相邻的时间单元,此时,该预留资源包括图5B中所示的为UE2分配的空口调度资源和图5B中所示的预留资源。后续,用户组内UE2(即用户组内的第二个请求分配空口调度资源的UE)请求分配空口调度资源,则RAN从上述预留资源中为UE2分配空口调度资源,为UE2分配空口调度资源如图5B所示,与为UE1分配空口调度资源处于相邻的时间单元,此时剩下的预留资源如图5B所示。
可选的,若上述步骤401中,SMF是从第一UE接收到用户组的标识,则上述步骤403中,SMF还可以向RAN发送第一UE的PDU会话的标识,该PDU会话是与上述用户组内的第一UE执行的同步业务相关联的会话。进而,该步骤404中,RAN根据同步调度指示信息,为第一UE的该PDU会话分配空口调度资源。
可选的,若上述步骤401中,SMF是从AF接收到用户组的标识以及UE列表,则上述步骤403中,SMF还可以根据UE列表确定UE列表内的各个UE分别对应的PDU会话,并向RAN发送UE列表内的各个UE分别对应的PDU会话的标识,其中,SMF根据UE列表内的UE数量向RAN多次发送UE列表内的各个UE分别对应的PDU会话的标识,该PDU会话是与上述用户组内的UE执行的同步业务相关联的会话。进而,该步骤404中,RAN根据同步调度指示信息,为UE列表内的各个UE分别对应的PDU会话分配空口调度资源。
例如,UE1和UE2属于同一个用户组,RAN为UE1和UE2分配空口调度资源的示意图可参考图5A和图5B。后续当UE1和UE2发送上行数据时,RAN对UE1和UE2分别发送的上行数据的调度示意图可参考图6,如果RAN在分配空口调度资源时,将UE1和UE2的上行数据放在同一个时间单元或相邻时间中进行调度,则可以尽量地保证UE1和UE2的上行数据同时传输到网络侧,这样网络进行混音处理的时候,可以尽可能地同时收到UE1和UE2的上行数据,从而有助于保证混音处理的效果和质量。
上述方案中,网络侧(SMF)可以基于用户组的标识确定RAN侧的同步调度指示信息,RAN可以根据该同步调度指示信息为用户组内的UE分配相同或相邻时间单元的空口调度资源,从而网络侧可以在尽可能短的时延内接收到用户组内的不同UE发送的数据,有助于提升数据处理的质量。
下面结合具体示例,对上述图4所示的流程进行介绍说明。
如图7所示,为本申请实施例提供的又一种资源分配方法流程示意图。该方案中,UE向网络发送自身所在的用户组的标识。网络可以基于用户组的标识分配同步调度指示信息,并将同步调度指示信息发送给RAN,如此,RAN可以根据同步调度指示信息为该UE进行特殊的资源调度,即对处于同一用户组的UE进行资源的同步调度。
该方案的前提条件是:多个UE加入到同一个用户组并均获取到相同的组标识(group ID),比如该组标识可以是用户组标识(UE group ID)(也可以称为用户组的标识)或者业务组标识(serice group ID)(也可以称为业务组的标识),该组标识用于标识一组特定的UE,组内的每一个UE具备相同的业务类型(如媒体业务),或者相同的业务需求(如同步调度需求)等等,本申请实施例不做限定。
可选的,UE获取组标识的方法包括但不限于以下两种:
a)在注册流程中,网络根据UE的签约数据生成(如,根据UE签约的业务类型生成组标识),或者UE的签约数据中包含了该UE所属的组标识,然后在注册接受消息中,由网络发送给UE。
b)UE上本地配置该UE所属的组标识。
以组标识为用户组标识为例,该方法包括以下步骤:
步骤701,UE向AMF发送第一请求。相应的,AMF可以接收到该第一请求。
该第一请求包含PDU会话的标识(PDU session ID)以及用户组标识,PDU会话的标识用于标识该PDU会话。该用户组内的任意一个UE需要与该用户组内的其他UE同步的空口调度资源。
该步骤701中发送第一请求的UE,属于该用户组。
作为该步骤701的一种实现方式,UE可以通过RAN,向AMF发送NAS消息(NAS message),该NAS消息中携带上述第一请求。
步骤702,AMF向SMF发送第二请求。相应的,SMF可以接收到该第二请求。
该第二请求携带上述PDU会话的标识以及用户组标识。
步骤703,SMF根据用户组标识,确定同步调度指示信息。
其中,SMF根据用户组标识确定同步调度指示信息的实现方法可以参考图4对应的实施例的步骤402的相关描述,这里不再赘述。
需要说明的是,如果同一个用户组内不同的UE的PDU会话对应的SMF不同,那么不同的SMF接收到不同UE发送的用户组标识之后,不同的SMF根据同一个用户组标识确定的同步调度指示信息是相同的。可以理解为,不同的SMF上配置相同的用户组标识与同步调度标识之间的对应关系,因此,不同的SMF就能根据相同的用户组标识确定相同的同步调度指示信息。
可选的,在该过程中,SMF还可以与PCF进一步更新会话管理相关策略。
步骤704,SMF向AMF发送第二响应。相应的,AMF可以接收到该第二响应。
该第二响应携带上述同步调度指示信息,以及还携带PDU会话的标识。例如,可以在第二响应携带N2会话管理容器(N2 SM container),N2 SM container中携带上述同步调度指示信息和PDU会话的标识。该第二响应还可以携带N1会话管理容器(N1 SM container),N1 SM container中携带PDU会话的标识以及第一响应。
步骤705,AMF向RAN发送第三请求。相应的,RAN可以接收到该第三请求。
该第三请求包含N2 SM container和N1 SM container,其中,N2 SM container包含同步调度指示信息和PDU会话的标识。
步骤706,RAN根据同步调度指示信息和PDU会话的标识,为UE分配空口调度资源。
其中,PDU会话的标识用于指示需要分配空口调度资源的PDU会话。
RAN根据同步调度指示信息和PDU会话的标识,为UE的PDU会话分配空口调度资源的实现方法,可以是:
方法一,RAN根据同步调度指示信息和PDU会话的标识,从空闲资源中为UE在分配空口调度资源。
比如,RAN根据接收到的同步调度指示信息,确定该UE是用户组内的第一个请求分配空口调度资源的UE,或者,RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息,则RAN可以按照正常流程分配空口调度资源,比如按照现有技术中的资源分配方式,从空闲资源中为该UE的PDU会话分配空口调度资源,即RAN根据自身的资源分配情况确定该UE的上行数据调度的时间单元,并给UE发送资源调度指派(Grant),通知UE在某个时间单元发送该PDU会话的上行数据。同时RAN本地保存该同步调度指示信息与该调度资源的对应关系。后续UE将上行数据按照RAN分配的空口调度资源发送给RAN。在为UE的PDU会话分配空口调度资源之后,RAN还可以为用户组内的其他UE的PDU会话的分配预留资源,该预留资源与已经分配给该UE的PDU会话的空口调度资源处于相同或相邻的时间单元。即,该预留资源适用于用户组内的其他UE的PDU会话。例如,UE1和UE2属于同一个用户组,且UE1需要与UE2同步空口调度资源。参考图5A和图5B,为分配空口调度资源的示意图。图5A中,在空口侧为UE1和UE2分配的调度资源处于相同的时间单元。图5B中,为UE1和UE2分配的调度资源处于相邻的时间单元。
需要说明的是,RAN确定该UE是用户组内的第一个请求分配空口调度资源的UE或者RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息,指的是,在某个时间范围内(比如,以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为用户组内的UE具有空口调度同步需求,在一场演唱会的开始到结束的时间范围内等)RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息。
再比如,RAN根据接收到的同步调度指示信息确定该UE不是用户组内的第一个请求分配空口调度资源的UE,或者,RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,则RAN可以从该预留资源中,为该UE的PDU会话分配空口调度资源。
需要说明的是,RAN确定该UE不是用户组内的第一个请求分配空口调度资源的UE或者RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,指的是,在某个时间范围内(比如,以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为用户组内的UE具有空口调度同步需求,在一场演唱会的开始到结束的时间范围内等)RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息。
方法二,RAN根据同步调度指示信息和PDU会话的标识,从用户组对应的空口资源 中,为该UE分配空口调度资源。
这里的空口资源可以是RAN上配置的与用户组对应的固定调度资源,或者空口资源也可以是用户组内的UE发起注册流程时,RAN为该用户组分配的固定调度资源。
比如,RAN根据接收到的同步调度指示信息,确定该UE是用户组内的第一个请求分配空口调度资源的UE,或者,RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息,则RAN可以从该用户组对应的空口资源中为该UE的PDU会话分配空口调度资源,即RAN根据自身的资源分配情况确定该UE的上行数据调度的时间单元,并给UE发送资源调度指派(Grant),通知UE在某个时间单元发送该上行数据。后续UE将上行数据按照RAN分配的资源发送给RAN。在为UE的PDU会话分配空口调度资源之后,RAN还可以为用户组内的其他UE的PDU会话分配预留资源,该预留资源是上述空口资源中的资源,且与已经分配给该UE的PDU会话的空口调度资源处于相同或相邻的时间单元。即,该预留资源适用于用户组内的其他UE的PDU会话。例如,UE1和UE2属于同一个用户组,且UE1需要与UE2同步空口调度资源。参考图5A和图5B,为分配空口调度资源的示意图。图5A中,在空口侧为UE1和UE2分配的调度资源处于相同的时间单元。图5B中,为UE1和UE2分配的调度资源处于相邻的时间单元。
需要说明的是,RAN确定该UE是用户组内的第一个请求分配空口调度资源的UE或者RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,指的是,在某个时间范围内(比如,以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为用户组内的UE具有空口调度同步需求,在一场演唱会的开始到结束的时间范围内等)RAN确定之前未收到过与所述用户组内的UE关联的同步调度指示信息。
再比如,RAN根据接收到的同步调度指示信息确定该UE不是用户组内的第一个请求分配空口调度资源的UE,或者,RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,则RAN可以从该预留资源中,为该UE的PDU会话分配空口调度资源。
需要说明的是,RAN确定该UE不是用户组内的第一个请求分配空口调度资源的UE或者RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息,指的是,在某个时间范围内(比如,以演唱会场景为例,主唱、贝斯手、吉他手、鼓手等作为用户组内的UE具有空口调度同步需求,在一场演唱会的开始到结束的时间范围内等)RAN确定之前收到过与所述用户组内的UE关联的同步调度指示信息。
需要注意的是,本申请实施例中,同一个用户组内不同的UE接入的是同一个RAN。这样即便是同一个用户组内不同的UE的PDU会话对应的SMF不同,但在步骤703中,不同的SMF根据相同的用户组标识确定相同的同步调度指示信息,因此RAN可以为同一个用户组内不同的UE分配同步的空口调度资源。
步骤707,RAN向UE发送空口调度资源。相应的,UE可以接收到该空口调度资源。
该空口调度资源即为RAN为UE分配的空口侧的用于发送上行数据的调度资源。UE可以根据RAN发送的空口调度资源进行本地配置,后续UE将上行数据按照RAN分配的空口调度资源发送给RAN。
该步骤707中,RAN还可以向UE发送上述N1 SM container。UE在接收到N1 SM container之后,可以获取到其中的第一响应和PDU会话的标识。
步骤708,RAN向AMF发送第三响应,相应的,AMF可以接收到该第三响应。
该步骤708为可选。
作为一种实现方案,上述实施例可以是UE注册至网络之后,在PDU会话建立流程中执行。在PDU会话建立流程中,上述第一请求可以是PDU会话建立请求(PDU Session establishment Request),上述第二请求可以是PDU会话建立请求(Nsmf_PDUSession_CreateSMContext request),上述第一响应可以是PDU会话建立接受消息(PDU Session Establishment Accept),上述第二响应可以是PDU会话建立请求响应(Nsmf_PDUSession_CreateSMContext response),上述第三请求可以是N2会话请求(N2session request),上述第三响应可以是N2会话响应(N2 session response)。
作为一种实现方案,上述实施例可以UE注册至网络之后,在PDU会话修改流程中执行。在PDU会话修改流程中,上述第一请求可以是PDU会话修改请求(PDU Session modification Request),上述第二请求可以是PDU会话更新请求(Nsmf_PDUSession_UpdateSMContext request),上述第一响应可以是PDU会话修改请求应答消息(PDU Session Modification ack),上述第二响应可以是PDU会话更新响应(Nsmf_PDUSession_UpdateSMContext response),上述第三请求可以是N2会话请求(N2session request),上述第三响应可以是N2会话响应(N2 session response)。
例如,UE1和UE2属于同一个用户组,RAN为UE1和UE2分配空口调度资源的示意图可参考图5A和图5B。后续当UE1和UE2发送上行数据时,RAN对UE1和UE2分别发送的上行数据的调度示意图可参考图6,如果RAN在分配空口调度资源时,将UE1和UE2的上行数据放在同一个时间单元或相邻时间中进行调度,则可以尽量地保证UE1和UE2的上行数据同时传输到网络侧,这样网络进行混音处理的时候,可以尽可能地同时收到UE1和UE2的上行数据,从而有助于保证混音处理的效果和质量。上述方案,UE在第一请求中携带用户组标识,网络侧(SMF)可以基于用户组标识确定RAN侧的同步调度指示信息,RAN可以根据该同步调度指示信息为用户组内的UE分配处于相同或相邻时间单元的空口调度资源,从而网络侧可以在尽可能短的时延内接收到用户组内的不同UE发送的数据,有助于提升数据处理的质量。
如图8所示,为本申请实施例提供的又一种资源分配方法流程示意图。该方案中,在UE已经建立了会话之后,AF向网络发送请求,请求中携带用户组标识,如此,网络可以基于用户组标识确定同步调度指示信息,然后将同步调度指示信息发送给RAN。如此,RAN可以为该UE进行特殊的资源调度,即对处于同一用户组的UE进行资源的同步调度。
该方案的前提条件是:多个UE加入到同一个用户组并均获取到相同的组标识(group ID),比如该组标识可以是用户组标识(UE group ID)(也可以称为用户组的标识)或者业务组标识(serice group ID)(也可以称为业务组的标识),该组标识用于标识一组特定的UE,组内的每一个UE具备相同的业务类型(如媒体业务),或者相同的业务需求(如同步调度需求)等等,本申请实施例不做限定。
可选的,UE获取组标识的方法包括但不限于以下两种:
a)在注册流程中,网络根据UE的签约数据生成(如,根据UE签约的业务类型生成组标识),或者UE的签约数据中包含了该UE所属的组标识,然后在注册接受消息中,由网络发送给UE。
b)UE上本地配置该UE所属的组标识。
以组标识为用户组标识为例,该方法包括以下步骤:
步骤801,AF向PCF发送策略更新请求(Npcf_PolicyAuthorization update request)。相应的,PCF可以接收到该策略更新请求。
比如,AF可以通过NEF向PCF发送上述策略更新请求。
该策略更新请求中携带用户组标识和该用户组标识对应的UE列表(UE list)。
该用户组内的任意一个UE需要与该用户组内的其他UE同步的空口调度资源。
UE列表包含一个或多个UE的标识,UE列表中的UE的标识属于上述用户组。
步骤802,PCF触发PDU会话相关策略更新流程(PCF initiated SMF Policy Association Modification),在该过程中PCF触发SMF针对UE列表指示的UE的PDU会话更新,PCF将用户组标识和UE列表发送给SMF。
步骤803,SMF根据用户组标识确定同步调度指示信息,以及确定UE列表指示的各个UE分别对应的PDU会话的标识。
其中,SMF根据用户组标识确定同步调度指示信息的实现方法可以参考图4对应的实施例的步骤402的相关描述,这里不再赘述。
需要说明的是,如果同一个用户组内不同的UE的PDU会话对应的SMF不同,那么不同的SMF接收到不同UE发送的用户组标识之后,不同的SMF根据同一个用户组标识确定的同步调度指示信息是相同的。可以理解为,不同的SMF上配置相同的用户组标识与同步调度标识之间的对应关系,因此,不同的SMF就能根据相同的用户组标识确定相同的同步调度指示信息。
步骤804,SMF向AMF发送同步调度指示信息和PDU会话的标识。
比如,SMF可以通过Namf_Communication_N1N2MessageTransfer request,向AMF发送同步调度指示信息和PDU会话的标识。
步骤805,AMF向RAN发送N2会话请求(N2 session request)。相应的,RAN可以接收到该N2会话请求。
该N2会话请求包含N2 SM container和N1 SM container,其中,N2 SM container包含同步调度指示信息和PDU会话的标识,N1 SM container中携带PDU会话的标识以及PDU会话修改应答消息(PDU Session Modification ack)。
步骤806,RAN根据同步调度指示信息和PDU会话的标识,为UE分配空口调度资源。
其中,PDU会话的标识用于指示需要分配空口调度资源的PDU会话。
RAN根据同步调度指示信息和PDU会话的标识,为UE的PDU会话分配空口调度资源的实现方法,可以参考图7对应的实施例的相关描述,这里不再赘述。
需要注意的是,本申请实施例中,同一个用户组内不同的UE接入的是同一个RAN。这样即便是同一个用户组内不同的UE的PDU会话对应的SMF不同,但在步骤803中,不同的SMF根据相同的用户组标识确定相同的同步调度指示信息,因此RAN可以为同一个用户组内不同的UE分配同步的空口调度资源。
步骤807,RAN向UE发送空口调度资源。相应的,UE可以接收到该空口调度资源。
该空口调度资源即为RAN为UE分配的空口侧的用于发送上行数据的调度资源。UE可以根据RAN发送的空口调度资源进行本地配置,后续UE将上行数据按照RAN分配的空口调度资源发送给RAN。
该步骤807中,RAN还可以向UE发送上述N1 SM container。UE在接收到N1 SM container之后,可以获取到其中的PDU会话修改应答消息和PDU会话的标识。
步骤808,RAN向AMF发送N2会话响应,相应的,AMF可以接收到该N2会话响应。
该步骤808为可选。
例如,UE1和UE2属于同一个用户组,RAN为UE1和UE2分配空口调度资源的示意图可参考图5A和图5B。后续当UE1和UE2发送上行数据时,RAN对UE1和UE2分别发送的上行数据的调度示意图可参考图6,如果RAN在分配空口调度资源时,将UE1和UE2的上行数据放在同一个时间单元或相邻时间中进行调度,则可以尽量地保证UE1和UE2的上行数据同时传输到网络侧,这样网络进行混音处理的时候,可以尽可能地同时收到UE1和UE2的上行数据,从而有助于保证混音处理的效果和质量。
上述方案,AF在策略更新请求中携带用户组标识,网络侧(SMF)可以基于用户组标识确定RAN侧的同步调度指示信息,RAN可以根据该同步调度指示信息为用户组内的UE分配处于相同或相邻时间单元的空口调度资源,从而网络侧可以在尽可能短的时延内接收到用户组内的不同UE发送的数据,有助于提升数据处理的质量。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是,上述实现各网元为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本发明的范围。
可以理解的是,上述各个方法实施例中,对应由终端设备实现的步骤或者操作,也可以由配置于终端设备的部件(例如芯片或者电路)实现,对应由接入网设备实现的步骤或者操作,也可以由配置于接入网设备的部件(例如芯片或者电路)实现,对应由会话管理网元实现的步骤或者操作,也可以由配置于会话管理网元的部件(例如芯片或者电路)实现。
参考图9,为本申请实施例提供的一种通信装置的示意图。该装置用于实现上述方法实施例中对应接入网设备所执行的各个步骤,如图9所示,该装置900包括接收单元910、发送单元920和分配单元930。可选的,还包括确定单元940。接收单元910,用于接收与终端设备关联的同步调度指示信息,所述同步调度指示信息用于指示所述终端设备需要与所述终端设备所在的用户组内的其它终端设备同步的空口调度资源;分配单元930,用于根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源。发送单元920用于向终端设备发送所述空口调度资源。
在一种可能的实现方法中,当所述接收单元910未收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述分配单元930,具体用于根据所述同步调度指示信息,确定所述用户组的标识;根据所述用户组的标识,从所述用户组对应的空口资源中为所述终端设备分配所述空口调度资源。
在一种可能的实现方法中,所述接收单元910,还用于接收所述用户组的标识;所述分配单元930,还用于根据所述用户组的标识,为所述用户组分配所述空口资源。
在一种可能的实现方法中,确定单元940,用于确定所述空口资源中的第一预留资源, 所述第一预留资源与分配给所述终端设备的空口调度资源处于相同或相邻的时间单元,所述第一预留资源用于分配给所述用户组内的其他终端设备。
在一种可能的实现方法中,当所述接收单元910收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述分配单元930,具体用于从第二预留资源中,为所述终端设备分配所述空口调度资源,所述第二预留资源与已经分配给所述用户组内的一个或多个终端设备的空口调度资源处于相同或相邻的时间单元。
在一种可能的实现方法中,所述同步调度指示信息是根据所述用户组的标识确定的。
可以理解的是,上述各个单元也可以称为模块或者电路等,并且上述各个单元可以独立设置,也可以全部或者部分集成。
一些可能的实现方式中,上述接收单元910和发送单元920也可以通过收发单元实现,或者说接收单元910和发送单元920也可以统称为收发单元。上述分配单元930和确定单元940也可以通过处理单元实现,或者说分配单元930和确定单元940也可以统称为处理单元。
上述接收单元910、发送单元920或者收发单元也可称为通信接口,上述处理单元也可以称为处理器。
可选的,上述通信装置900还可以包括存储单元,该存储单元用于存储数据或者指令(也可以称为代码或者程序),上述各个单元可以和存储单元交互或者耦合,以实现对应的方法或者功能。例如,处理单元可以读取存储单元中的数据或者指令,使得通信装置实现上述实施例中的方法。
参考图10,为本申请实施例提供的一种通信装置的示意图。该装置用于实现上述方法实施例中对应会话管理网元所执行的各个步骤,如图10所示,该装置1000包括接收单元1010、发送单元1020和确定单元1030。接收单元1010,用于接收用户组的标识,所述用户组包括至少两个终端设备;确定单元1030,用于根据所述用户组的标识,确定同步调度指示信息,所述同步调度指示信息用于指示所述用户组内的终端设备需要与所述用户组内的其它终端设备同步的空口调度资源;发送单元1020,用于向接入网设备发送所述同步调度指示信息。
在一种可能的实现方法中,所述接收单元1010,具体用于接收来自第一终端设备的所述用户组的标识,所述第一终端设备属于所述用户组;或者;接收来自应用功能网元的所述用户组的标识。
可以理解的是,上述各个单元也可以称为模块或者电路等,并且上述各个单元可以独立设置,也可以全部或者部分集成。
一些可能的实现方式中,上述接收单元1010和发送单元1020也可以通过收发单元实现,或者说接收单元1010和发送单元1020也可以统称为收发单元。上述确定单元1030可以通过处理单元实现。
上述接收单元1010、发送单元1020或者收发单元也可称为通信接口,上述处理单元也可以称为处理器。
可选的,上述通信装置1000还可以包括存储单元,该存储单元用于存储数据或者指令(也可以称为代码或者程序),上述各个单元可以和存储单元交互或者耦合,以实现对应的方法或者功能。例如,处理单元可以读取存储单元中的数据或者指令,使得通信装置 实现上述实施例中的方法。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分,实际实现时可以全部或部分集成到一个物理实体上,也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现;也可以全部以硬件的形式实现;还可以部分单元以软件通过处理元件调用的形式实现,部分单元以硬件的形式实现。例如,各个单元可以为单独设立的处理元件,也可以集成在装置的某一个芯片中实现,此外,也可以以程序的形式存储于存储器中,由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起,也可以独立实现。这里所述的处理元件又可以成为处理器,可以是一种具有信号的处理能力的集成电路。在实现过程中,上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中,以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路,例如:一个或多个特定集成电路(Application Specific Integrated Circuit,ASIC),或,一个或多个微处理器(digital singnal processor,DSP),或,一个或者多个现场可编程门阵列(Field Programmable Gate Array,FPGA),或这些集成电路形式中至少两种的组合。再如,当装置中的单元可以通过处理元件调度程序的形式实现时,该处理元件可以是通用处理器,例如中央处理器(Central Processing Unit,CPU)或其它可以调用程序的处理器。再如,这些单元可以集成在一起,以片上***(system-on-a-chip,SOC)的形式实现。
以上用于接收的单元(例如接收单元)是一种该装置的接口电路,用于从其它装置接收信号。例如,当该装置以芯片的方式实现时,该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元(例如发送单元)是一种该装置的接口电路,用于向其它装置发送信号。例如,当该装置以芯片的方式实现时,该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
参考图11,为本申请实施例提供的一种接入网设备的结构示意图。该接入网设备用于实现以上实施例中接入网设备的操作。如图11所示,该接入网设备包括:天线1110、射频装置1120、基带装置1130。天线1110与射频装置1120连接。在上行方向上,射频装置1120通过天线1110接收终端设备发送的信息,将终端设备发送的信息发送给基带装置1130进行处理。在下行方向上,基带装置1130对终端设备的信息进行处理,并发送给射频装置1120,射频装置1120对终端设备的信息进行处理后经过天线1110发送给终端设备。
基带装置1130可以包括一个或多个处理元件1131,例如,包括一个主控CPU和其它集成电路,以及还包括接口1133。此外,该基带装置1130还可以包括存储元件1132,存储元件1132用于存储程序和数据;接口1133用于与射频装置1120交互信息,该接口例如为通用公共无线接口(common public radio interface,CPRI)。以上用于接入网设备的装置可以位于基带装置1130,例如,以上用于接入网设备的装置可以为基带装置1130上的芯片,该芯片包括至少一个处理元件和接口电路,其中处理元件用于执行以上接入网设备执行的任一种方法的各个步骤,接口电路用于与其它装置通信。在一种实现中,接入网设备实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现,例如用于接入网设备的装置包括处理元件和存储元件,处理元件调用存储元件存储的程序,以执行以上方法实施例中接入网设备执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件,即片内存储元件,也可以为与处理元件处于不同芯片上的存储元件,即片外存储元件。
在另一种实现中,接入网设备实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件,这些处理元件设置于基带装置上,这里的处理元件可以为集成电路,例如:一个或多个ASIC,或,一个或多个DSP,或,一个或者多个FPGA,或者这些类集成电路的组合。这些集成电路可以集成在一起,构成芯片。
接入网设备实现以上方法中各个步骤的单元可以集成在一起,以SOC的形式实现,例如,基带装置包括该SOC芯片,用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件,由处理元件调用存储元件的存储的程序的形式实现以上接入网设备执行的方法;或者,该芯片内可以集成至少一个集成电路,用于实现以上接入网设备执行的方法;或者,可以结合以上实现方式,部分单元的功能通过处理元件调用程序的形式实现,部分单元的功能通过集成电路的形式实现。
可见,以上用于接入网设备的装置可以包括至少一个处理元件和接口电路,其中至少一个处理元件用于执行以上方法实施例所提供的任一种接入网设备执行的方法。处理元件可以以第一种方式:即调用存储元件存储的程序的方式执行接入网设备执行的部分或全部步骤;也可以以第二种方式:即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行接入网设备执行的部分或全部步骤;当然,也可以结合第一种方式和第二种方式执行以上接入网设备执行的部分或全部步骤。
这里的处理元件同以上描述,可以是通用处理器,例如CPU,还可以是被配置成实施以上方法的一个或多个集成电路,例如:一个或多个ASIC,或,一个或多个微处理器DSP,或,一个或者多个FPGA等,或这些集成电路形式中至少两种的组合。存储元件可以是一个存储器,也可以是多个存储元件的统称。
参考图12,为本申请实施例提供的一种会话管理网元的结构示意图,用于实现以上实施例中会话管理网元的操作。如图12所示,该会话管理网元包括:处理器1210和接口1230,可选的,还包括存储器1220。该接口1230用于实现与其他设备进行通信。
以上实施例中会话管理网元执行的方法可以通过处理器1210调用存储器(可以是会话管理网元中的存储器1220,也可以是外部存储器)中存储的程序来实现。即,用于会话管理网元的装置可以包括处理器1210,该处理器1210通过调用存储器中的程序,以执行以上方法实施例中的会话管理网元执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路,例如CPU。用于会话管理网元的装置可以通过配置成实施以上方法的一个或多个集成电路来实现。例如:一个或多个ASIC,或,一个或多个微处理器DSP,或,一个或者多个FPGA等,或这些集成电路形式中至少两种的组合。或者,可以结合以上实现方式。
本申请实施例还提供一种通信***,包括如图9所示的通信装置和如图10所示的通信装置。
本申请实施例还提供一种通信***,包括如图11所示的接入网设备和如图12所示的会话管理网元。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算 机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘(solid state disk,SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器,数字信号处理器,专用集成电路(ASIC),现场可编程门阵列(FPGA)或其它可编程逻辑装置,离散门或晶体管逻辑,离散硬件部件,或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器,可选地,该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现,例如数字信号处理器和微处理器,多个微处理器,一个或多个微处理器联合一个数字信号处理器核,或任何其它类似的配置来实现。
在一个或多个示例性的设计中,本申请所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现,这些功能可以存储与电脑可读的媒介上,或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如,这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置,或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外,任何连接都可以被适当地定义为电脑可读媒介,例如,如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘(英文:Digital Versatile Disc,简称:DVD)、软盘和蓝光光盘,磁盘通常以磁性复制数据,而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本领域技术人员应该可以意识到,在上述一个或多个示例中,本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时,可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质,其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
尽管结合具体特征及其实施例对本申请进行了描述,显而易见的,在不脱离本申请的精神和范围的情况下,可对其进行各种修改和组合。相应地,本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明,且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术 的范围之内,则本申请也意图包括这些改动和变型在内。
Claims (30)
- 一种资源分配方法,其特征在于,包括:接收与终端设备关联的同步调度指示信息,所述同步调度指示信息用于指示所述终端设备需要与所述终端设备所在的用户组内的其它终端设备同步的空口调度资源;根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源。
- 如权利要求1所述的方法,其特征在于,当未收到过与所述用户组内的终端设备关联的所述同步调度指示信息,所述根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源,包括:根据所述同步调度指示信息,确定所述用户组的标识;根据所述用户组的标识,从所述用户组对应的空口资源中为所述终端设备分配所述空口调度资源。
- 如权利要求2所述的方法,其特征在于,还包括:接收所述用户组的标识;根据所述用户组的标识,为所述用户组分配所述空口资源。
- 如权利要求2或3所述的方法,其特征在于,还包括:确定所述空口资源中的第一预留资源,所述第一预留资源与分配给所述终端设备的空口调度资源处于相同或相邻的时间单元,所述第一预留资源用于分配给所述用户组内的其他终端设备。
- 如权利要求1所述的方法,其特征在于,当收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源,包括:从第二预留资源中,为所述终端设备分配所述空口调度资源,所述第二预留资源与已经分配给所述用户组内的一个或多个终端设备的空口调度资源处于相同或相邻的时间单元。
- 如权利要求1-5任一所述的方法,其特征在于,所述同步调度指示信息是根据所述用户组的标识确定的。
- 一种资源分配方法,其特征在于,包括:接收用户组的标识,所述用户组包括至少两个终端设备;根据所述用户组的标识,确定同步调度指示信息,所述同步调度指示信息用于指示所述用户组内的终端设备需要与所述用户组内的其它终端设备同步的空口调度资源;向接入网设备发送所述同步调度指示信息。
- 如权利要求7所述的方法,其特征在于,所述接收用户组的标识,包括:接收来自第一终端设备的所述用户组的标识,所述第一终端设备属于所述用户组;或者;接收来自应用功能网元的所述用户组的标识。
- 一种通信装置,其特征在于,包括:接收单元,用于接收与终端设备关联的同步调度指示信息,所述同步调度指示信息用于指示所述终端设备需要与所述终端设备所在的用户组内的其它终端设备同步的空口调度资源;分配单元,用于根据所述同步调度指示信息,为所述终端设备分配所述空口调度资源。
- 如权利要求9所述的装置,其特征在于,当所述接收单元未收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述分配单元,具体用于根据所述同步调度指示信息,确定所述用户组的标识;根据所述用户组的标识,从所述用户组对应的空口资源中为所述终端设备分配所述空口调度资源。
- 如权利要求10所述的装置,其特征在于,所述接收单元,还用于接收所述用户组的标识;所述分配单元,还用于根据所述用户组的标识,为所述用户组分配所述空口资源。
- 如权利要求10或11所述的装置,其特征在于,所述装置还包括确定单元,用于确定所述空口资源中的第一预留资源,所述第一预留资源与分配给所述终端设备的空口调度资源处于相同或相邻的时间单元,所述第一预留资源用于分配给所述用户组内的其他终端设备。
- 如权利要求9所述的装置,其特征在于,当所述接收单元收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述分配单元,具体用于从第二预留资源中,为所述终端设备分配所述空口调度资源,所述第二预留资源与已经分配给所述用户组内的一个或多个终端设备的空口调度资源处于相同或相邻的时间单元。
- 如权利要求9-13任一所述的装置,其特征在于,所述同步调度指示信息是根据所述用户组的标识确定的。
- 一种通信装置,其特征在于,包括:接收单元,用于接收用户组的标识,所述用户组包括至少两个终端设备;确定单元,用于根据所述用户组的标识,确定同步调度指示信息,所述同步调度指示信息用于指示所述用户组内的终端设备需要与所述用户组内的其它终端设备同步的空口调度资源;发送单元,用于向接入网设备发送所述同步调度指示信息。
- 如权利要求15所述的装置,其特征在于,所述接收单元,具体用于:接收来自第一终端设备的所述用户组的标识,所述第一终端设备属于所述用户组;或者;接收来自应用功能网元的所述用户组的标识。
- 一种通信***,其特征在于,包括会话管理网元和接入网设备;所述会话管理网元,用于接收用户组的标识,所述用户组包括至少两个终端设备;根据所述用户组的标识,确定同步调度指示信息,所述同步调度指示信息用于指示所述用户组内的终端设备需要与所述用户组内的其它终端设备同步的空口调度资源;向所述接入网设备发送与所述用户组内的第一终端设备关联的所述同步调度指示信息;所述接入网设备,用于根据所述同步调度指示信息,为所述第一终端设备分配所述空口调度资源。
- 如权利要求17所述的***,其特征在于,当所述接入网设备未收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述接入网设备,具体用于根据所述同步调度指示信息,确定所述用户组的标识;根 据所述用户组的标识,从所述用户组对应的空口资源中为所述第一终端设备分配所述空口调度资源。
- 如权利要求18所述的***,其特征在于,所述接入网设备,还用于接收所述用户组的标识;根据所述用户组的标识,为所述用户组分配所述空口资源。
- 如权利要求18或19所述的***,其特征在于,所述接入网设备,还用于确定所述空口资源中的第一预留资源,所述第一预留资源与分配给所述第一终端设备的空口调度资源处于相同或相邻的时间单元,所述第一预留资源用于分配给所述用户组内的其他终端设备。
- 如权利要求17所述的***,其特征在于,当所述接入网设备收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述接入网设备,具体用于从第二预留资源中,为所述第一终端设备分配所述空口调度资源,所述第二预留资源与已经分配给所述用户组内的一个或多个终端设备的空口调度资源处于相同或相邻的时间单元。
- 如权利要求17-21任一所述的***,其特征在于,所述同步调度指示信息是根据所述用户组的标识确定的。
- 如权利要17-22任一所述的***,其特征在于,所述会话管理网元,用于接收用户组的标识,具体包括:用于接收来自所述第一终端设备的所述用户组的标识;或者;用于接收来自应用功能网元的所述用户组的标识。
- 一种资源分配方法,其特征在于,包括:会话管理网元接收用户组的标识,所述用户组包括至少两个终端设备;所述会话管理网元根据所述用户组的标识,确定同步调度指示信息,所述同步调度指示信息用于指示所述用户组内的终端设备需要与所述用户组内的其它终端设备同步的空口调度资源;所述会话管理网元向接入网设备发送与所述用户组内的第一终端设备关联的所述同步调度指示信息;所述接入网设备根据所述同步调度指示信息,为所述第一终端设备分配所述空口调度资源。
- 如权利要求24所述的方法,其特征在于,当所述接入网设备未收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述接入网设备,具体用于根据所述同步调度指示信息,确定所述用户组的标识;根据所述用户组的标识,从所述用户组对应的空口资源中为所述第一终端设备分配所述空口调度资源。
- 如权利要求24所述的方法,其特征在于,当所述接入网设备收到过与所述用户组内的终端设备关联的所述同步调度指示信息;所述接入网设备,具体用于从第二预留资源中,为所述第一终端设备分配所述空口调度资源,所述第二预留资源与已经分配给所述用户组内的一个或多个终端设备的空口调度资源处于相同或相邻的时间单元。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储程序,所述程序被处理器调用时,权利要求1-6任一所述的方法被执行。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储程序,所述程序被处理器调用时,权利要求7或8所述的方法被执行。
- 一种计算机程序,其特征在于,当所述程序被处理器调用时,权利要求1-6任一所述的方法被执行。
- 一种计算机程序,其特征在于,当所述程序被处理器调用时,权利要求7或8所述的方法被执行。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201980098816.3A CN114175826A (zh) | 2019-12-30 | 2019-12-30 | 资源分配方法、装置及*** |
PCT/CN2019/130179 WO2021134347A1 (zh) | 2019-12-30 | 2019-12-30 | 资源分配方法、装置及*** |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2019/130179 WO2021134347A1 (zh) | 2019-12-30 | 2019-12-30 | 资源分配方法、装置及*** |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021134347A1 true WO2021134347A1 (zh) | 2021-07-08 |
Family
ID=76687523
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/130179 WO2021134347A1 (zh) | 2019-12-30 | 2019-12-30 | 资源分配方法、装置及*** |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN114175826A (zh) |
WO (1) | WO2021134347A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024008181A1 (zh) * | 2022-07-08 | 2024-01-11 | 大唐移动通信设备有限公司 | 同步传输组确定方法、终端及核心网网元 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103687034A (zh) * | 2012-08-30 | 2014-03-26 | 电信科学技术研究院 | 一种组调度方法及装置 |
CN107197517A (zh) * | 2017-08-02 | 2017-09-22 | 电子科技大学 | 基于ta分组的lte卫星上行链路同步方法 |
US20180041988A1 (en) * | 2015-05-10 | 2018-02-08 | Lg Electronics Inc. | Method for supporting sporadic high-capacity packet service and apparatus therefor |
CN110493880A (zh) * | 2019-08-30 | 2019-11-22 | 成都天奥集团有限公司 | 广覆盖场景下基于终端侧等待的多用户上行资源调度方法 |
-
2019
- 2019-12-30 CN CN201980098816.3A patent/CN114175826A/zh active Pending
- 2019-12-30 WO PCT/CN2019/130179 patent/WO2021134347A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103687034A (zh) * | 2012-08-30 | 2014-03-26 | 电信科学技术研究院 | 一种组调度方法及装置 |
US20180041988A1 (en) * | 2015-05-10 | 2018-02-08 | Lg Electronics Inc. | Method for supporting sporadic high-capacity packet service and apparatus therefor |
CN107197517A (zh) * | 2017-08-02 | 2017-09-22 | 电子科技大学 | 基于ta分组的lte卫星上行链路同步方法 |
CN110493880A (zh) * | 2019-08-30 | 2019-11-22 | 成都天奥集团有限公司 | 广覆盖场景下基于终端侧等待的多用户上行资源调度方法 |
Non-Patent Citations (2)
Title |
---|
HUAWEI, HISILICON: "Transmission in preconfigured UL resources", 3GPP DRAFT; R1-1911907, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, USA; 20191118 - 20191122, 9 November 2019 (2019-11-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 23, XP051823089 * |
LG ELECTRONICS: "Feature lead summary of Enhancements on Multi-beam Operations", 3GPP DRAFT; R1-1912277, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, USA; 20191118 - 20191122, 19 November 2019 (2019-11-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051826596 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024008181A1 (zh) * | 2022-07-08 | 2024-01-11 | 大唐移动通信设备有限公司 | 同步传输组确定方法、终端及核心网网元 |
Also Published As
Publication number | Publication date |
---|---|
CN114175826A (zh) | 2022-03-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020220747A1 (zh) | 一种tsn业务的处理方法、装置及*** | |
WO2020224463A1 (zh) | 一种数据分析方法及装置 | |
WO2021037175A1 (zh) | 一种网络切片的管理方法及相关装置 | |
WO2021017550A1 (zh) | 一种事件报告的发送方法、装置及*** | |
WO2021227559A1 (zh) | 通信方法、装置及*** | |
WO2021051241A1 (zh) | 一种通信方法、装置及*** | |
US20220330294A1 (en) | Communication method, apparatus, and system | |
WO2021051420A1 (zh) | 一种dns缓存记录的确定方法及装置 | |
WO2021147687A1 (zh) | 一种通信的方法及装置和*** | |
JP2022530333A (ja) | 通信方法、通信装置、及び通信システム | |
WO2020248709A1 (zh) | 一种mdbv的确定方法、装置及*** | |
WO2022222745A1 (zh) | 一种通信方法及装置 | |
WO2021159724A1 (zh) | 通信方法、装置及*** | |
WO2021134347A1 (zh) | 资源分配方法、装置及*** | |
WO2022237505A1 (zh) | 一种通信方法、设备及*** | |
WO2021057342A1 (zh) | 一种网络切片的计费方法及装置 | |
WO2021057020A1 (zh) | 一种网络切片的计费方法及装置 | |
WO2021218244A1 (zh) | 通信方法、装置及*** | |
WO2021138784A1 (zh) | 一种接入网络的方法、装置及*** | |
CN116868603A (zh) | 针对af会话的外部参数提供的新方法 | |
WO2021159415A1 (zh) | 通信方法、装置及*** | |
WO2021147105A1 (zh) | 通信方法及装置 | |
CN115915196A (zh) | 一种链路状态检测方法、通信装置及通信*** | |
WO2021042381A1 (zh) | 一种通信方法、装置及*** | |
WO2021081712A1 (zh) | 一种dns查询方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19958658 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19958658 Country of ref document: EP Kind code of ref document: A1 |