CN108810978B - Method and apparatus for communication resource management - Google Patents
Method and apparatus for communication resource management Download PDFInfo
- Publication number
- CN108810978B CN108810978B CN201710309622.6A CN201710309622A CN108810978B CN 108810978 B CN108810978 B CN 108810978B CN 201710309622 A CN201710309622 A CN 201710309622A CN 108810978 B CN108810978 B CN 108810978B
- Authority
- CN
- China
- Prior art keywords
- network device
- physical resource
- synchronization
- resource blocks
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/26—Resource reservation
Abstract
Embodiments of the present disclosure relate to communication methods and apparatus for communication resource management. For example, the communications method includes, at a first network device, obtaining a type of network slice and an indication of a number of physical resource blocks associated with the type; determining the position of a physical resource block reserved for the network slice according to the type; and synchronizing the location of the reserved physical resource blocks with a second network device, wherein the second network device is different from the first network device.
Description
Technical Field
The present disclosure relates generally to communication technology. In particular, the present disclosure relates to a method and apparatus for communication resource management.
Background
Currently, in next generation wireless communication development, three applications with different quality of service (QoS) requirements have been certified. Of these applications, large-scale internet of things (mtc) applications require coverage of a larger service area because they typically have a large number of users. Ultra-high reliable ultra-low delay communications (URLLC) have extremely high requirements in terms of end-to-end delay and reliability performance. Enhanced mobile broadband (eMBB) requires a high transmission rate to support High Definition (HD) video as well as Virtual Reality (VR).
Network slicing is a key feature of next generation networks, which relates to converting a static network mode suitable for all situations into a mode of logical network partitioning with suitable isolation, suitable resources and optimized topology, so that the logical network partitioning can be applied to the different service classes to improve the efficiency and performance of network architecture and configuration.
However, since users are distributed in unknown cells, the reserved resources required for a particular network slice cannot be fixed large, so the resources allocated to user equipment for scheduling may be less and the frequency selective gain is therefore degraded. In addition, the reserved resources may collide with neighboring strong interfering cells.
Disclosure of Invention
In general, embodiments of the present disclosure propose methods and apparatus for communication resource management.
In a first aspect, embodiments of the present disclosure provide a method for communication resource management. The method comprises the following steps: obtaining, at a first network device, a type of a network slice and an indication of a number of physical resource blocks associated with the type; determining the position of a physical resource block reserved for the network slice according to the type; and a location of the physical resource blocks reserved in synchronization with a second network device, the second network device being different from the first network device.
In a second aspect, embodiments of the present disclosure provide a network device for communication resource management. The network device includes at least one processor and a memory coupled to the at least one processor. The memory contains instructions stored therein that, when executed by the at least one processing unit, cause the apparatus to perform actions. The actions include: obtaining a type of a network slice and an indication of a number of physical resource blocks associated with the type; determining the position of a physical resource block reserved for the network slice according to the type; and synchronising the location of the reserved physical resource blocks with a second network device different from the device.
In a third aspect, a computer-readable medium has instructions stored thereon, which, when executed by at least one processing unit, cause the at least one processing unit to be configured to perform a method. The method comprises the following steps: obtaining, at a first network device, a type of a network slice and an indication of a number of physical resource blocks associated with the type; determining the position of a physical resource block reserved for the network slice according to the type; and a location of the physical resource blocks reserved in synchronization with a second network device, the second network device being different from the first network device.
It should be understood that the statements herein reciting aspects are not intended to limit the critical or essential features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. In the drawings, like or similar reference characters designate like or similar elements, and wherein:
FIG. 1 illustrates an example communication network in which embodiments of the present disclosure may be implemented;
fig. 2 illustrates a flow diagram of an example communication method in accordance with certain embodiments of the present disclosure;
fig. 3 illustrates a schematic diagram of physical resource blocks reserved for network slicing in accordance with certain embodiments of the present disclosure;
fig. 4 illustrates a schematic diagram of physical resource blocks reserved for network slicing in accordance with certain embodiments of the present disclosure;
fig. 5 illustrates a schematic diagram of reserving physical resource blocks for multiple network slices within the same subframe, in accordance with certain embodiments of the present disclosure;
fig. 6 illustrates a schematic diagram of determining network slice reserved physical resource blocks in one example manner, in accordance with certain embodiments of the present disclosure;
fig. 7 illustrates a schematic diagram of determining network slice reserved physical resource blocks in another exemplary manner in accordance with certain embodiments of the present disclosure;
FIG. 8 illustrates a schematic diagram of trigger synchronization in accordance with certain embodiments of the present disclosure;
FIG. 9 illustrates a schematic diagram of synchronization, in accordance with certain embodiments of the present disclosure;
FIG. 10 illustrates a schematic diagram of synchronization, in accordance with certain embodiments of the present disclosure;
FIG. 11 illustrates a schematic diagram of synchronization, in accordance with certain embodiments of the present disclosure;
FIG. 12 illustrates a block diagram of an apparatus according to certain embodiments of the present disclosure; and
fig. 13 illustrates a block diagram of an apparatus in accordance with certain embodiments of the present disclosure.
Throughout the drawings, the same or similar reference numbers refer to the same or similar elements.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
The term "network device" as used herein refers to a base station or other entity or node having a particular function in a communication network. A "base station" (BS) may represent a node B (NodeB or NB), an evolved node B (eNodeB or eNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, or a low power node such as a pico base station, a femto base station, or the like. In the context of the present disclosure, the terms "network device" and "base station" may be used interchangeably for purposes of discussion convenience, and may primarily be referred to as an eNB as an example of a network device.
The term "terminal equipment" or "user equipment" (UE) as used herein refers to any terminal equipment capable of wireless communication with a base station or with each other. As an example, the terminal device may include a Mobile Terminal (MT), a Subscriber Station (SS), a Portable Subscriber Station (PSS), a Mobile Station (MS), or an Access Terminal (AT), and the above-described devices in a vehicle. In the context of the present disclosure, the terms "terminal device" and "user equipment" may be used interchangeably for purposes of discussion convenience.
The terms "include" and variations thereof as used herein are inclusive and open-ended, i.e., "including but not limited to. The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment". Relevant definitions for other terms will be given in the following description.
The term "Network Slicing" as used herein is known to those skilled in the art and represents a set of Network functions and resources that run those Network functions that form a complete, instantiated logical Network and that satisfy specific Network characteristics required by a service instance. One network slice may be completely or partially, logically and/or physically separated from other network slices.
As mentioned above, network slicing is a key feature of next generation networks, which is related to transforming static network modes suitable for all situations into a mode of logical network partitioning with suitable isolation, suitable resources and optimized topology, so that the logical network partitioning can be adapted to the different service classes or individual users mentioned above. Network slicing techniques allow a physical network to be sliced into multiple virtual peer-to-peer networks, which are logically isolated and include device, access, transport, and core networks and are adapted for different service types with different characteristics and requirements.
In next generation wireless communication development, three applications with different quality of service (QoS) requirements have been certified. Of these applications, large-scale internet of things (mtc) applications require coverage of a larger service area because they typically have a large number of users. Ultra-high reliable ultra-low delay communications (URLLC) have extremely high requirements in terms of end-to-end delay and reliability performance. Enhanced mobile broadband (eMBB) requires a high transmission rate to support High Definition (HD) video as well as Virtual Reality (VR). In order to meet these different QoS requirements and characteristics of data transmission, a conventional communication system (e.g., LTE) having a single system architecture and system configuration will no longer be effective.
To further improve the performance of the network and to ensure a better isolation between different applications, network slices in the access network, in particular in the Radio Access Network (RAN), can be applied. In the next generation 5G radio access technology (new radio (NR)) discussed earlier, the physical layer resources can be organized in OFDM. Due to emerging applications with low latency requirements, such as mtc and URLLC, smaller transmission time intervals and flexible Multiple Access (MA) are proposed in this new radio technology. In order to implement network slicing in this context, it is required that different slices can be divided into predetermined resources on the physical layer. In other words, to isolate different slices, a specific frequency band is assigned to each slice, assuming that the user equipment already knows the physical layer characteristics of the allocated resources.
However, since users are distributed in unknown cells, the reserved resources required for a particular network slice cannot be fixed large, so the resources allocated to user equipment for scheduling may be less and the frequency selective gain is therefore degraded. In addition, the reserved resources may collide with neighboring strong interfering cells.
Therefore, there is a need for an efficient way to implement the partitioning of network slices for different user service types on the one hand and to reduce the inter-cell interference on the resources reserved for the slices on the other hand. To this end, embodiments of the present disclosure provide a communication method. According to the method, the type of the network slice is acquired by the network device. An indication of the number of physical resource blocks associated with the type, i.e. the data of the physical resource blocks reserved for the network slice on each subframe, is also obtained. According to the type, the position of the physical resource block reserved for the network slice is determined. And synchronizing the location of the reserved physical resource blocks with other network devices other than the network device.
In this way, corresponding network resources can be effectively reserved for user equipment of different service types, while ensuring that data is not interfered by other neighboring cells when transmitted using the reserved resources.
Fig. 1 illustrates an example communication network 100 in which embodiments of the present disclosure may be implemented. Communication network 100 includes two network devices, namely first network device 110 and second network device 120, and terminal device 130. First network device 110 and second network device 120 may communicate with terminal device 130.
It should be understood that the number of network devices and terminal devices shown in fig. 1 is for illustration purposes only and is not intended to be limiting. Network 100 may include any suitable number of network devices and terminal devices. For example, in some embodiments, the communication network 100 may also include a third network device 140 and a fourth network device 150. The third network device 140 and the fourth network device 150 are also capable of communicating with the terminal device 130. Third network device 140 is, for example, capable of communicating with first network device 110 and fourth network device 150 is, for example, capable of communicating with second network device 120.
As shown, in this example, first network device 110 hosts a first cell and second network device 120 hosts a second cell. The terminal device 130 is for example assigned to a first type of network slice. For example, assuming that the first network device 110 hosting the first cell is the primary serving cell for the terminal device 130, the terminal device 130 may experience very strong inter-cell interference from the second network device 120 hosting the second cell. To avoid such interference, the first network device 110 is to inform the second network device 120 of the specific resources reserved for the terminal device 130, such that the second network device 120 reduces transmission power or does not transmit data on the specified resources, thereby being able to protect the resources reserved for the terminal device 130 by the first network device 110 for scheduling and further being able to ensure the QoS requirements of, for example, the first type of network slice. Embodiments of this aspect will be described in detail later.
Communications in network 100 may be implemented in accordance with any suitable communication protocol, including, but not limited to, first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G) cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE)802.11, and/or any other protocol now known or later developed. Moreover, the communication may utilize any suitable wireless communication technique including, but not limited to, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple Input Multiple Output (MIMO), orthogonal frequency division multiple access (OFDM), and/or any other technique now known or later developed.
The principles and specific embodiments of the present disclosure will be described in detail below with reference to fig. 2-11, respectively, from the perspective of the first network device 110. Referring first to fig. 2, a flow diagram of an example communication method 200 is shown, in accordance with certain embodiments of the present disclosure. It is to be appreciated that the method 200 may be implemented, for example, at the first network device 110 as shown in fig. 1. For ease of description, the method 200 is described below in conjunction with fig. 1 and 2.
At 210, the first network device 110 obtains an indication of a network slice type and a number of physical resource blocks associated with the type.
When resource slicing is enabled and initialized in the RAN, the first network device 110 can reserve a certain number of physical resource blocks for the network slice according to the size of the required resources or according to preconfigured information. Fig. 3 and 4 show schematic diagrams of physical resource blocks reserved for network slicing according to an embodiment of the present invention. As shown in fig. 3, in some embodiments, the first network device 110 reserves one physical resource block on each subframe for the respective resource slice. In fig. 3, the reserved physical resource blocks are represented by legend 310. Optionally, as shown in fig. 4, in some embodiments, the first network device 110 may also reserve a plurality (e.g., 5) of physical resource blocks (represented by legend 410) for respective resource slices on each subframe.
In some embodiments, the first network device 110 is able to reserve different numbers of physical resource blocks for different network slices within the same subframe range. Fig. 5 shows a schematic diagram of physical resource blocks reserved for different network slices according to an embodiment of the invention. As shown in fig. 5, the first network device 110 can, for example, reserve a first number (e.g., 2) of physical resource blocks (represented by legend 510) per subframe for one type of network slice and a second number (e.g., 3) of physical resource blocks (represented by legend 520) per subframe for another type of network slice. It should be understood that the embodiment shown in fig. 5 is for illustrative purposes only and is not intended to limit the number of network slice types. The first network device 110 can also reserve a predetermined number of physical resource blocks for more than two network slices within the same subframe, in case the sum of the number of physical resource blocks reserved for different types of network slices does not exceed the number of physical resource blocks available for reservation on the subframe.
At 220, the first network device 110 may determine the locations of the physical resource blocks reserved for the network slice according to the type of the network slice that has been acquired.
According to some embodiments, the first network device 110 may acquire the type of the network slice while acquiring information of a position identical to the physical resource blocks determined to be reserved for the network slice. The information comprises, for example, at least an identification of a starting one of the physical resource blocks, coefficients for generating a frequency hopping sequence related to a position of the physical resource block, and a number of physical resource blocks that can be reserved over one subframe.
According to some embodiments, the first network device 110 may calculate the location of the physical resource block by the above information, for example, may find the frequency hopping sequence associated with the location of the physical resource block by the following formula (1):
wherein gamma is1(n) represents an identification of a starting one of the physical resource blocks, where n represents an ordinal number of the subframe. α and β denote reserved coefficients, which are coefficients for randomly generating the location of the physical resource block, that is, coefficients for generating a frequency hopping sequence associated with the location of the physical resource block.
Representing the number of physical resource blocks that can be reserved on one subframe. The function mod (A, B) represents the modulo of A and B in order to define the position of the physical resource blocks found to be within the range of the number of physical resource blocks that can be reserved on a subframeAnd (4) the following steps. Function(s)
Represents an integer close to A or less than or equal to A.
For example, fig. 6 illustrates a schematic diagram of determining physical resource blocks reserved by a network slice in one example manner, according to some embodiments of the present disclosure. For example, in this example, for a plurality (e.g., 3) network slices of physical resource blocks reserved per subframe, the distribution of reserved physical resource blocks 610 depends on the configuration of information, e.g.
α＝11，β＝13。
Since the first network device 110 may have multiple network slices with different network resource requirements on the same subframe for transmission, in order to avoid overlapping of reserved resources for different network slice types, at least for the first network device 110,
α and β are set to be the same.
Fig. 7 illustrates a schematic diagram of another exemplary manner of determining network slice reserved physical resource blocks in accordance with certain embodiments of the present disclosure. To ensure that the physical resource blocks 710 can be evenly distributed for any number of reserved physical resource blocks, the first network device can find the hopping sequence associated with the location of the physical resource block in equation (2):
wherein
For physical assignment to a particular network sliceThe number of resource blocks. Same, function
Represents an integer close to A or greater than or equal to A.
Referring again to fig. 6 and 7, it can be seen that the distribution of the reserved physical resource blocks found in formula (2) is more uniform than the distribution of the reserved physical resource blocks found in formula (1).
It should be appreciated that in some instances, the information described above for determining the location of the physical resource blocks can be extracted by the first network device 110 from the indication received at 210. In some instances, the information used to determine the location of the physical resource blocks can be determined by the first network device 110 from a set of predefined configurations based on the type of network slice obtained at 210.
In order to prevent the resources reserved by the first network device 110 for the network slice from being interfered by other network devices in the neighborhood, e.g. the second network device 120, the first network device 110 is to inform the second network device of the reserved resources. Thus, at 230, the first network device 110 synchronizes the location of the reserved physical resource blocks with the second network device 120.
In conventional approaches, if, for example, the frequency band used for transmission by the first network device 110 changes, other network devices, for example, the second network device 120, are notified by an update of the Relative Narrowband Transmit Power (RNTP) at the subframe where the frequency band hops. The second network device 120 can then implement frequency hopping synchronously with the first network device 110. However, in the concept of the present disclosure, the position of the physical resource block in the frequency domain is hopped on every subframe. Informing the second network device 120 of each hop through RNTP updates is difficult to implement.
It is therefore proposed to synchronize to the second network device 120 the identity of the physical resource blocks on the initially synchronized sub-frame of the first network device 110 and the corresponding coefficients of randomly generating the locations of the physical resource blocks and the rules of randomly generating the locations of the physical resource blocks, etc.
FIG. 8 shows a rootSchematic diagrams of trigger synchronization according to certain embodiments of the present disclosure. Referring to FIG. 8, a subframe 810 is shown on the abscissa1To 8109. In sub-frame 8101To 8104In the above, the physical resource blocks 820 for transmitting data are always transmitted in the same frequency domain. In sub-frame 8104Where, upon receiving an indication to trigger synchronization, physical resource blocks 820 are from subframe 8104Initially, the signaling is transmitted in such a way that frequency hopping is performed on every subframe.
Reserved resource synchronization according to some embodiments of the present disclosure is described below with reference to the interaction diagrams of fig. 9 to 11. It is to be appreciated that the processes illustrated in fig. 9-11 may be considered block 230 in fig. 2.
In the embodiment shown in fig. 9, as an implementation of block 230 in fig. 2, the synchronization between the first network device 110 and the second network device 120 is achieved by means of a notification mechanism. Specifically, in such an embodiment, first network device 110 sends 910 a notification about synchronization to second network device 120 to initiate the synchronization process. The first network device 110 then sends 920 parameters for synchronization to the second network device 120 in order to enable the second network device 120 to determine the location of the physical resource blocks.
It should be appreciated that the parameters sent by the first network device 110 for synchronization essentially relate to the parameters used in block 220 in fig. 2 for determining the location of the physical resource blocks reserved for the network slice, i.e. including the identity of the starting one of the physical resource blocks, the coefficients used for generating the frequency hopping sequence related to the location of the physical resource blocks and the number of physical resource blocks that can be reserved on one sub-frame. It is emphasized that for the second network device 120, the identification of the starting one of the physical resource blocks is at least one physical resource block located on the starting subframe of the synchronization indicated by the first network device 110 after the synchronization is triggered.
Further, in some embodiments, sending 920 parameters for synchronization to second network device 120 may also be included in sending 910 a notification about synchronization to second network device 120. That is, the notification about synchronization includes a parameter for synchronization.
Upon receiving the notification about synchronization and/or the parameters for synchronization, the second network device 120 configures 920 the location of the physical resource blocks of the second network device 120 for transmitting data with the parameters for synchronization, such that the reserved resources are agreed upon corresponding to the first network device 110, i.e. the location of the physical resource blocks can be determined. Since the second network device 120 acquires the same coefficient for generating the frequency hopping sequence related to the position of the physical resource block as the first network device 110, the same number of physical resource blocks that can be reserved in one subframe as the first network device 110, and the position of at least one physical resource block located in the starting subframe after the trigger synchronization, the position of the same physical resource block as the first network device 110 can be determined by the rule indicated by the above formula (1) or formula (2), for example.
Alternatively, in the embodiment shown in fig. 10, as a further implementation of block 230 in fig. 2, the synchronization between the first network device 110 and the second network device 120 can be implemented by means of a request and response communication mechanism. Specifically, in such an embodiment, first network device 110 can first send 1010 a request for synchronization to second network device 120. The request comprises the same parameters for resource synchronization reservation, the identities of the first network device 110 and the second network device 120, and the type of network slice as in the embodiment described in connection with fig. 9. After receiving the request from the first network device 110, if the second network device 120 is able to synchronize resource reservations with the first network device 110, the second network device 120 configures 1020 a location of physical resource blocks of the second network device 120 for transmitting data with parameters contained in the synchronization request. It should be understood that the rule and method for configuring the location of the physical resource block used for transmitting data by the second network device 120 in the embodiment described in connection with fig. 10 are essentially the same as those in the embodiment described in connection with fig. 9, and therefore, are not described again here. After the configuration is finished, the second network device 120 sends 1030 a response to the first network device 110. In some embodiments, coefficients for synchronization may also be included in the response sent by second network device 120. The response indicates that the location of the physical resource blocks of the second network device 120 has been synchronized with the first network device 110.
In certain embodiments, there is a fourth network device 150 hosting a fourth cell adjacent to the second cell hosted by second network device 120 and there is a third network device 140 hosting a third cell adjacent to the first cell hosted by first network device 110. While or after the second network device 120 configures 1020 the location of the physical resource blocks to be synchronized with the first network device 110, the second network device 120 can send 1040 the parameters for synchronization in the synchronization request to the fourth network device 150, such that the fourth network device 150 configures 1050 the location of the physical resource blocks to be synchronized identically to the second network device 120. Likewise, after receiving the response from the second network device 120, the first network device 110 can send 1060 the parameters for synchronization in the synchronization request to the third network device 140, so that the fourth network device 150 configures 1070 the location of the physical resource blocks to be synchronized identically to the first network device 110.
Alternatively, in the embodiment shown in fig. 11, as a further implementation of block 230 in fig. 2, the synchronization between the first network device 110 and the second network device 120 can be implemented by means of a communication mechanism of request, response and acknowledgement. Specifically, in such embodiments, first network device 110 can first send 1110 a request for synchronization to second network device 120. The request comprises the same parameters for resource synchronization reservation, the identities of the first network device 110 and the second network device 120, and the type of network slice as in the embodiment described in connection with fig. 9. Upon receiving the request from first network device 110, if second network device 120 is able to synchronize resource reservations with first network device 110, a response to the request is sent 1120 to first network device 110. After receiving the response from second network device 120, first network device 110 can send 1130 an acknowledgement for the response message to second network device 120. The second network device 120 configures 1140 the location of the physical resource blocks of the second network device 120 for transmitting data with the parameters contained in the synchronization request. It should be understood that the rule and method for configuring the location of the physical resource block used for transmitting data by the second network device 120 in the embodiment described in connection with fig. 11 are essentially the same as those in the embodiment described in connection with fig. 9, and therefore, are not described again here.
In certain embodiments, there is a fourth network device 150 hosting a fourth cell adjacent to the second cell hosted by second network device 120 and there is a third network device 140 hosting a third cell adjacent to the first cell hosted by first network device 110. Simultaneously with or after the second network device 120 configures 1140 the location of the physical resource blocks to be synchronized with the first network device 110, the second network device 120 can send 1150 the parameter for synchronization in the synchronization request to the fourth network device 150, such that the fourth network device 150 configures 1160 the location of the physical resource blocks to be synchronized identically to the second network device 120. Likewise, after sending the acknowledgement to the second network device 120, the first network device 110 can send 1170 the parameters for synchronization in the synchronization request to the third network device 140, so that the fourth network device 150 configures 1180 the location of the physical resource blocks to be synchronized as the first network device 110.
It should be understood that the rules and methods of configuring the locations of physical resource blocks used for transmitting data for the third network device 140 and the fourth network device 150, as well as other network devices to be synchronized that may not be included in the communication network 100 in embodiments that are not shown, are essentially the same as the embodiments described in connection with fig. 9.
It should be appreciated that the various embodiments described with respect to block 230 of the method 200 illustrated in fig. 2 in conjunction with fig. 9-11 can be combined in any combination and modified. The above-described embodiments are intended to be illustrative only and not limiting.
In certain embodiments, method 200 may further include ceasing synchronization of first network device 110 with second network device 120 with respect to the physical resource blocks.
In some embodiments, first network device 110 sends a request to stop synchronization to second network device 120 when synchronization is to be stopped. The second network device 120, upon receiving the request from the first network device 110, stops synchronization for the reserved resources and sends a response message to the request, such that the first network device 110 stops synchronization with the second network device 120 with respect to the physical resource blocks.
Fig. 12 illustrates a block diagram of an apparatus 1200 in accordance with certain embodiments of the present disclosure. It is to be appreciated that apparatus 1200 may be implemented on the first network device 110 side shown in fig. 1. As shown in fig. 7, the apparatus 1200 (e.g., the first network device 110) comprises a first obtaining unit 1210 configured to obtain a type of the network slice and an indication of a number of physical resource blocks associated with the type. The apparatus 1200 may further include a first determining unit 1220 configured to determine a location of a physical resource block reserved for the network slice according to the type. The apparatus 1200 may further comprise a first synchronization unit 1230 configured to synchronize a location of a reserved physical resource block with a second network device different from the network device.
In certain embodiments, the first determining unit 1220 further comprises a second determining unit configured to determine information related to physical resource blocks. The information indicates at least one of: an identification of a starting physical resource block among the physical resource blocks, coefficients for generating a frequency hopping sequence related to a location of the physical resource blocks, and a number of physical resource blocks that can be reserved on one subframe.
In some embodiments, the second determination unit further comprises a third determination unit configured to extract information from the received indication or to determine information from a set of predefined configurations based on the type of network slice.
In some embodiments, the first synchronization unit 1230 may include a first sending unit configured to send a notification about synchronization to the second network device and to send parameters for synchronization to the second network device to enable the second network device to determine the location of the physical resource blocks.
In some embodiments, the first synchronization unit 1230 may include a second sending unit configured to send a request for synchronization to the second network device. The request includes parameters for synchronization, identifications of the network device and the second network device, and a type of the network slice. The first synchronizing unit 1230 may comprise a first receiving unit configured to receive a response message from the second network device to the request and a third transmitting unit configured to transmit, in response to receiving the response message, a parameter for synchronization to a third network device hosting a third cell neighboring the first cell of the network device.
In some embodiments, the first synchronizing unit 1230 may include a fourth sending unit configured to send an acknowledgement for the response message to the second network device.
In certain embodiments, the above-mentioned parameter for synchronization indicates at least one of: the method comprises the steps of allocating a physical resource block to a base station, allocating at least one physical resource block located on a starting subframe among the physical resource blocks, synchronizing at least one reservation coefficient triggered on the starting subframe and used for generating a frequency hopping sequence related to the position of the physical resource block, and the number of the physical resource blocks which can be reserved on one subframe.
In some embodiments, the apparatus 1200 may further comprise a first stopping unit configured to stop said synchronization with the second network device with respect to the physical resource blocks.
In some embodiments, the first stopping unit may further include a fifth transmitting unit configured to transmit a request to stop synchronization to the second network device and the second stopping unit configured to stop synchronization with the second network device with respect to the physical resource block in response to receiving a response message to the request from the second network device.
It should be understood that each unit recited in the apparatus 1200 corresponds to each step in the method 200 described with reference to fig. 2-11, respectively. Therefore, the operations and features described above in conjunction with fig. 1 to 11 are also applicable to the apparatus 1200 and the units included therein, and have the same effects, and detailed description is omitted here.
The elements included in apparatus 1200 may be implemented in a variety of ways including software, hardware, firmware, or any combination thereof. In one embodiment, one or more of the units may be implemented using software and/or firmware, such as machine executable instructions stored on a storage medium. In addition to, or in the alternative to, machine-executable instructions, some or all of the elements in apparatus 1200 may be implemented at least in part by one or more hardware logic components. By way of example, and not limitation, exemplary types of hardware logic components that may be used include Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standards (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and so forth.
The elements shown in fig. 12 may be implemented partially or wholly as hardware modules, software modules, firmware modules, or any combination thereof. In particular, in some embodiments, the procedures, methods, or processes described above may be implemented by hardware in a network device or a terminal device. For example, a network device or a terminal device may implement the method 200 with its transmitter, receiver, transceiver, and/or processor or controller.
Fig. 13 illustrates a block diagram of a device 1300 suitable for implementing embodiments of the present disclosure. Device 1300 may be used to implement a network device, such as first network device 110 shown in fig. 1.
As shown, the device 1300 includes a controller 1310. The controller 1310 controls the operation and functions of the device 1300. For example, in certain embodiments, the controller 1310 may perform various operations by way of instructions 1330 stored in a memory 1320 coupled thereto. The memory 1320 may be of any suitable type suitable to the local technical environment and may be implemented using any suitable data storage technology, including but not limited to semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems. Although only a single memory unit is illustrated in FIG. 13, there may be multiple physically distinct memory units within the device 1300.
The controller 1310 may be of any suitable type suitable to the local technical environment, and may include, but is not limited to, one or more of a general purpose computer, a special purpose computer, a microcontroller, a digital signal controller (DSP), and a controller-based multi-core controller architecture. The device 1300 may also include a plurality of controllers 1310. The controller 1310 is coupled to a transceiver 1340 that may enable the transceiver 1340 to receive and transmit information via one or more antennas 1350 and/or other components.
When the device 1300 is acting as the first network device 110, the controller 1310 and the transceiver 1340 may cooperate to implement the method 200 described above with reference to fig. 2. All of the features described above with reference to fig. 2 apply to the apparatus 1300 and are not described in detail herein.
In summary, embodiments of the present disclosure provide a communication method for communication resource management and a corresponding network device. Compared with the prior art, the embodiment of the disclosure divides and configures the network slices for the users and/or the terminal devices with different service types, so that the network resources can be more effectively utilized for the users and/or the terminal devices with different service types. At the same time, in order to keep the data transmission on the reserved resources unaffected by the network equipment of the neighbouring cell. Synchronization of resource reservation is implemented between network devices. Thereby, the service quality of the communication is further improved.
In general, the various example embodiments of this disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While aspects of embodiments of the disclosure have been illustrated or described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
By way of example, embodiments of the disclosure may be described in the context of machine-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or divided between program modules as described. Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed facility, program modules may be located in both local and remote memory storage media.
Computer program code for implementing the methods of the present disclosure may be written in one or more programming languages. These computer program codes may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the computer or other programmable data processing apparatus, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. The program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server.
In the context of this disclosure, a machine-readable medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More detailed examples of a machine-readable storage medium include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical storage device, a magnetic storage device, or any suitable combination thereof.
Additionally, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking or parallel processing may be beneficial. Likewise, while the above discussion contains certain specific implementation details, this should not be construed as limiting the scope of any invention or claims, but rather as describing particular embodiments that may be directed to particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (19)
1. A method for communication resource management, comprising:
at a first network device, obtaining information of a type of a network slice, and a number and a position of physical resource blocks associated with the type of the network slice;
determining the position of the physical resource block reserved for the network slice according to the information of the type, the number and the position of the physical resource block; and
the location of the physical resource blocks reserved in synchronization with a second network device, the second network device being different from the first network device.
2. The method of claim 1, wherein obtaining the information comprises:
obtaining information of a location of the physical resource block while obtaining the type of the network slice, the information including:
an identification of a starting one of the physical resource blocks,
coefficients for generating a frequency hopping sequence related to the position of the physical resource block, an
The number of physical resource blocks that can be reserved on one subframe.
3. The method of claim 1, wherein obtaining the information comprises:
determining the information from a set of predefined configurations based on the type of the network slice.
4. The method of claim 1, wherein the synchronizing comprises:
sending a notification about the synchronization to the second network device; and
sending parameters for the synchronization to the second network device to enable the second network device to determine the location of the physical resource blocks.
5. The method of claim 1, wherein the synchronizing comprises:
sending a request for the synchronization to the second network device, the request comprising:
the parameters used for the said synchronization are,
an identification of the first network device and the second network device, an
The type of the network slice;
receiving a response message to the request from the second network device; and
in response to receiving the response message, sending the parameters for the synchronization to a third network device hosting a third cell neighboring the first cell of the first network device.
6. The method of claim 5, wherein the synchronizing further comprises:
sending an acknowledgement for the response message to the second network device.
7. The method of any of claims 4 to 6, wherein the parameters for the synchronization indicate at least one of:
at least one of the physical resource blocks located on a starting subframe on which the synchronization is triggered,
at least one reservation coefficient for generating a frequency hopping sequence related to the position of the physical resource block, an
The number of physical resource blocks that can be reserved on one subframe.
8. The method of claim 1, further comprising:
ceasing the synchronization with the second network device with respect to the physical resource blocks.
9. The method of claim 8, wherein stopping the synchronization comprises:
sending a request to the second network device to stop the synchronization; and
in response to receiving a response message from the second network device to the request, cease the synchronization with the second network device with respect to the physical resource blocks.
10. A first network device, comprising:
at least one processor; and
a memory coupled with the at least one processor, the memory containing instructions stored therein that, when executed by the at least one processing unit, cause the first network device to perform acts comprising:
acquiring the type of a network slice and the information of the number and the position of physical resource blocks associated with the type of the network slice;
determining the position of the physical resource block reserved for the network slice according to the information of the type, the number and the position of the physical resource block; and
synchronizing the location of the reserved physical resource blocks with a second network device different from the first network device.
11. The first network device of claim 10, wherein obtaining the information comprises:
obtaining information of a location of the physical resource block while obtaining the type of the network slice, the information including:
an identification of a starting one of the physical resource blocks,
coefficients for generating a frequency hopping sequence related to the position of the physical resource block, an
The number of physical resource blocks that can be reserved on one subframe.
12. The first network device of claim 10, wherein obtaining the information comprises:
determining the information from a set of predefined configurations based on the type of the network slice.
13. The first network device of claim 10, wherein the synchronizing comprises:
sending a notification about the synchronization to the second network device; and
sending parameters for the synchronization to the second network device to enable the second network device to determine the location of the physical resource blocks.
14. The first network device of claim 10, wherein the synchronizing comprises:
sending a request for the synchronization to the second network device, the request comprising:
the parameters used for the said synchronization are,
an identification of the network device and the second network device, an
The type of the network slice;
receiving a response message to the request from the second network device; and
in response to receiving the response message, sending the parameters for the synchronization to a third network device hosting a third cell neighboring the first cell of the network device.
15. The first network device of claim 14, wherein the synchronizing further comprises:
sending an acknowledgement for the response message to the second network device.
16. The first network device of any of claims 13-15, wherein the parameters for the synchronization indicate at least one of:
at least one of the physical resource blocks located on a starting subframe on which the synchronization is triggered,
at least one reservation coefficient for generating a frequency hopping sequence related to the position of the physical resource block, an
The number of physical resource blocks that can be reserved on one subframe.
17. The first network device of claim 10, the acts further comprising:
ceasing the synchronization with the second network device with respect to the physical resource blocks.
18. The first network device of claim 17, wherein ceasing the synchronization comprises:
sending a request to the second network device to stop the synchronization; and
in response to receiving a response message from the second network device to the request, cease the synchronization with the second network device with respect to the physical resource blocks.
19. A computer-readable medium having instructions stored thereon, which when executed by at least one processing unit, cause the at least one processing unit to be configured to perform a method comprising:
at a first network device, obtaining information of a type of a network slice, and a number and a position of physical resource blocks associated with the type of the network slice;
determining the position of the physical resource block reserved for the network slice according to the information of the type, the number and the position of the physical resource block; and
the location of the physical resource blocks reserved in synchronization with a second network device, the second network device being different from the first network device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710309622.6A CN108810978B (en) | 2017-05-04 | 2017-05-04 | Method and apparatus for communication resource management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710309622.6A CN108810978B (en) | 2017-05-04 | 2017-05-04 | Method and apparatus for communication resource management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108810978A CN108810978A (en) | 2018-11-13 |
| CN108810978B true CN108810978B (en) | 2022-03-18 |
Family
ID=64053629
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710309622.6A Active CN108810978B (en) | 2017-05-04 | 2017-05-04 | Method and apparatus for communication resource management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108810978B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109600262B (en) * | 2018-12-17 | 2021-08-10 | 东南大学 | Resource self-configuration and self-optimization method and device in URLLC transmission network slice |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2672777A1 (en) * | 2011-11-25 | 2013-12-11 | Huawei Technologies Co., Ltd | Radio resource optimization method, device and system |
| CN105791355A (en) * | 2014-12-23 | 2016-07-20 | 电信科学技术研究院 | Open multi-service cellular network system and service implementation method |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101662419B (en) * | 2008-08-27 | 2011-12-07 | 华为技术有限公司 | Method, device and system for realizing resource reservation |
| CN102781102A (en) * | 2011-03-31 | 2012-11-14 | 北京新岸线无线技术有限公司 | Method, site and central access point for resource request |
| CN102547871B (en) * | 2012-02-07 | 2015-07-29 | 华为技术有限公司 | Resource negotiation method and apparatus in a kind of D2D communication |
| US9338693B2 (en) * | 2013-03-14 | 2016-05-10 | Nec Corporation | Scheduling framework for adaptive video delivery over cellular networks |
| US10700936B2 (en) * | 2015-06-02 | 2020-06-30 | Huawei Technologies Co., Ltd. | System and methods for virtual infrastructure management between operator networks |
| CN106550410B (en) * | 2015-09-17 | 2020-07-07 | 华为技术有限公司 | Communication control method, controller, user equipment and related device |
| CN105979597B (en) * | 2016-06-27 | 2020-02-21 | 宇龙计算机通信科技(深圳)有限公司 | Communication resource allocation method, allocation device, base station and terminal |
| CN106572516B (en) * | 2016-09-28 | 2021-02-12 | 华为技术有限公司 | Network slice selection method, terminal equipment and network equipment |
| CN106455103B (en) * | 2016-11-30 | 2022-12-20 | 宇龙计算机通信科技(深圳)有限公司 | Resource allocation method and resource allocation device |
-
2017
- 2017-05-04 CN CN201710309622.6A patent/CN108810978B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2672777A1 (en) * | 2011-11-25 | 2013-12-11 | Huawei Technologies Co., Ltd | Radio resource optimization method, device and system |
| CN105791355A (en) * | 2014-12-23 | 2016-07-20 | 电信科学技术研究院 | Open multi-service cellular network system and service implementation method |
Non-Patent Citations (1)
| Title |
|---|
| R2-167845 "Consideration on the impact of NW slicing on RAN";ZTE等;《3GPP tsg_ran\WG2_RL2》;20161105;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108810978A (en) | 2018-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7232948B2 (en) | Terminal, random access method, base station, and communication system | |
| CN109565852B (en) | Dynamic resource allocation in wireless networks with wireless backhaul | |
| JP6988994B2 (en) | Random access power controllers, methods and communication systems | |
| CN110049557B (en) | Random access method and device | |
| CN107431902B (en) | Method and apparatus for transmitting and receiving signal in communication system supporting device-to-device scheme | |
| JP6731002B2 (en) | Frequency domain resource configuration method and apparatus | |
| EP3656164B1 (en) | Method and system for managing ue-to-ue interference in a mobile telecommunication network | |
| TWI675601B (en) | Coordination of signaling and resource allocation in a wireless network using radio access technology | |
| JP2018511990A (en) | Resource classification in millimeter wave networks | |
| CN109792417A (en) | The frequency adjustment of high speed LTE deployment | |
| EP3030030B1 (en) | Resource allocation method, device and system | |
| CN109561434B (en) | Method, apparatus, and computer-readable medium for guaranteeing communication service | |
| US9374748B2 (en) | Method of controlling interference in heterogeneous network | |
| US20210037432A1 (en) | Communications method and apparatus | |
| EP4022990A1 (en) | Techniques for adjusting timing in wireless networks | |
| CN108141712B (en) | Method, network node and wireless device for processing access information | |
| US20200008250A1 (en) | Wireless Connection Establishment Method And Apparatus | |
| JP2019533371A (en) | Method and apparatus for transmitting a downlink control signal | |
| CN113287282A (en) | Conflict handling | |
| US20190239257A1 (en) | Random access method, terminal device, and network device | |
| CN108810978B (en) | Method and apparatus for communication resource management | |
| JP2009111505A (en) | Wireless communication system, base station and transmitting method | |
| KR102509220B1 (en) | Method for controlling random access and apparatuses thereof | |
| WO2018024002A1 (en) | Signal transmission method and device, and computer storage medium | |
| CN106559885B (en) | Method for distributing cell wireless network temporary identifier, access network node and UE |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220113 Address after: 7 / F, 388 ningqiao Road, Pudong New Area pilot Free Trade Zone, Shanghai, 201206 Applicant after: Shanghai NOKIA Baer Software Co.,Ltd. Address before: No.388, ningqiao Road, Jinqiao, Pudong New Area, Shanghai, 201206 Applicant before: NOKIA SHANGHAI BELL Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |