CN114338404A - Network slice identifier distribution method and device, storage medium and electronic equipment - Google Patents
Network slice identifier distribution method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN114338404A CN114338404A CN202111665480.XA CN202111665480A CN114338404A CN 114338404 A CN114338404 A CN 114338404A CN 202111665480 A CN202111665480 A CN 202111665480A CN 114338404 A CN114338404 A CN 114338404A
- Authority
- CN
- China
- Prior art keywords
- network slice
- service
- slice identifier
- target
- tac
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 75
- 208000004605 Persistent Truncus Arteriosus Diseases 0.000 claims abstract description 175
- 208000037258 Truncus arteriosus Diseases 0.000 claims abstract description 175
- 238000004590 computer program Methods 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 abstract description 8
- 238000004891 communication Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 17
- 230000006870 function Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 6
- 238000011217 control strategy Methods 0.000 description 4
- 238000013507 mapping Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 101000831616 Homo sapiens Protachykinin-1 Proteins 0.000 description 2
- 102100024304 Protachykinin-1 Human genes 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 101000655188 Homo sapiens Tachykinin-3 Proteins 0.000 description 1
- 101000669528 Homo sapiens Tachykinin-4 Proteins 0.000 description 1
- 102100033009 Tachykinin-3 Human genes 0.000 description 1
- 102100039365 Tachykinin-4 Human genes 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The present disclosure provides a method and an apparatus for allocating network slice identifiers, a storage medium, and an electronic device, which relate to the field of communications technologies and can solve the problem in the related art that the number of network slice identifiers is consumed more when a terminal access area is restricted by a slice. The related network slice identifier distribution method comprises the following steps: acquiring a service request for accessing a target service area; determining a target tracking area code TAC corresponding to the target service area; if the target TAC comprises a single TAC, a network slice identifier used by a single tracking area service is allocated to the target TAC, and if the target TAC comprises at least two TACs, a network slice identifier used by a cross-tracking area service is allocated to the target TAC, wherein in the network slice identifiers used by the single tracking area service, the same network slice identifier is repeatedly used in different TACs. The embodiment of the disclosure can reduce the consumption of network slice identification when the terminal access area is limited by the slice.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for allocating network slice identifiers, a storage medium, and an electronic device.
Background
At present, compared with 4G (4th Generation Mobile Communication Technology, fourth Generation Mobile Communication Technology), 5G (5th Generation Mobile Communication Technology) introduces richer QoS (Quality of Service) characteristics, and can provide different forwarding scheduling policy guarantees for various services with different requirements on bandwidth, delay, and error rate. With the deep development and application of 5G network technology in each vertical industry, more and more service applications put forward high guarantee requirements on air interface transmission quality of a wireless side, but the extensive use of air interface priority scheduling technology such as GBR (Guaranteed Bit Rate) scheduling in the current network can seriously affect the application experience of common 2C service (also called C2C or CTC, which is electronic commerce between individuals) or other low-priority services. Therefore, it is necessary to introduce a terminal access area limiting manner for services using an absolute priority scheduling support technology such as GBR, to strictly limit the service access area range of the 5G terminal, and to implement reasonable allocation and scheduling of wireless resources by combining a resource checking and controlling means in the limited area range, so as to reduce the application experience influence of the GBR scheduling support services on the ordinary 2C services or other lower priority services.
At present, a method for restricting a terminal access area by slicing needs to allocate a slice ID (identity, hereinafter also referred to as an identifier) to each service, and configure the slice ID in a corresponding base station according to a service access area range to restrict the service access area of the terminal, so that the number of slice IDs is consumed more, which is not beneficial to service expansion. However, if a PCF (Policy Control Function) -based method of signing a tracking area access Control Policy is adopted, the granularity of access area restriction is too coarse, which is not favorable for resource management and Control on the wireless side.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure provides a method and an apparatus for allocating network slice identifiers, a storage medium, and an electronic device, which at least to some extent overcome the problem in the related art that the number of network slice IDs is consumed more when a terminal access area is restricted by a slice.
According to a first aspect of the present disclosure, there is provided a network slice identifier allocation method, including: acquiring a service request for accessing a target service area; determining a target tracking area code TAC corresponding to the target service area; if the target TAC comprises a single TAC, a network slice identifier used by a single tracking area service is allocated to the target TAC, and if the target TAC at least comprises two TACs, a network slice identifier used by a cross-tracking area service is allocated to the target TAC, wherein in the network slice identifiers used by the single tracking area service, the same network slice identifier is repeatedly used in different TACs.
Optionally, the method further includes: respectively maintaining an unallocated network slice identifier list for a single tracking area service and a cross-tracking area service, wherein a network slice identifier used by the unallocated single tracking area service is recorded in the unallocated network slice identifier list of the single tracking area service, and a network slice identifier used by the unallocated cross-tracking area service is recorded in the unallocated network slice identifier list of the cross-tracking area service; if the target TAC comprises a single TAC, a network slice identifier used by a single tracking area service is allocated to the target TAC, and if the target TAC comprises at least two TACs, a network slice identifier used by a cross-tracking area service is allocated to the target TAC, wherein the method comprises the following steps: if the target TAC comprises a single TAC, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to a single tracking area service; and if the target TAC at least comprises two TACs, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to the cross-tracking area service.
Optionally, the method further includes: and if the target TAC comprises a single TAC and the unallocated network slice identifier list corresponding to the single tracking area service does not contain the network slice identifier used by the unallocated single tracking area service, selecting the network slice identifier allocated to the target TAC from the unallocated network slice identifier list corresponding to the cross-tracking area service.
Optionally, the method further includes: a list of assigned slice identities is maintained for single tracking area traffic and cross-tracking area traffic, respectively.
Optionally, the method further includes: after the target TAC is allocated with the network slice identifier, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service, or updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross-tracking area service.
Optionally, the method further includes: and maintaining a used network slice identifier list, wherein the used network slice identifier list records the network slice identifiers which are used before the network slice identifier allocation is carried out.
Optionally, the method further includes: after the target TAC is allocated with the network slice identifier, determining whether the network slice identifier allocated to the target TAC is used according to the used slice identifier list; if the network slice identifier allocated to the target TAC is used, carrying out capacity expansion configuration on a network slice access area; and if the network slice identifier allocated to the target TAC is not used, performing network slice end-to-end configuration.
Optionally, determining the target tracking area code TAC corresponding to the target service area includes: acquiring the information of the circled geographical area; determining a base station identifier or a cell identifier corresponding to the target service area according to the circled geographical area information; and determining the target TAC according to the base station identifier or the cell identifier.
According to a second aspect of the present disclosure, there is provided a network slice identifier allocating apparatus, including: the acquisition module is used for acquiring a service request for accessing a target service area; a first determining module, configured to determine a target tracking area code TAC corresponding to the target service area; and the allocation module is used for allocating a network slice identifier used by a single tracking area service to the target TAC if the target TAC comprises a single TAC, and allocating a network slice identifier used by a cross-tracking area service to the target TAC if the target TAC comprises at least two TACs, wherein in the network slice identifiers used by the single tracking area service, the same network slice identifier is repeatedly used in different TACs.
According to a third aspect of the present disclosure, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the network slice identifier allocation methods provided by the embodiments of the present disclosure via executing the executable instructions.
According to a fourth aspect of the present disclosure, there is provided a computer-readable storage medium, on which a computer program is stored, the computer program, when executed by a processor, implementing any one of the network slice identity allocation methods provided by the embodiments of the present disclosure.
According to the network slice identifier allocation method, device, storage medium and electronic equipment in the embodiments of the present disclosure, after the corresponding target TAC is determined according to the acquired service request, the network slice identifier is allocated for the target TAC for the single tracking area service and the cross-tracking area service, and since the network slice identifier used by the single tracking area service can be reused in different tracking areas, the use of the network slice identifier can be reduced when the terminal access area is limited by the slice.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
Fig. 1 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
fig. 2 is a flow diagram of a network slice identification assignment method in accordance with one or more embodiments of the present disclosure;
fig. 3 is a schematic diagram of a slice identity assignment module in accordance with an embodiment of the present disclosure;
fig. 4 is a flow diagram illustrating a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
fig. 5 is a flow diagram of a network slice identification assignment method in accordance with one or more embodiments of the present disclosure;
fig. 6 is a flow diagram of a network slice identification assignment method in accordance with one or more embodiments of the present disclosure;
fig. 7 is a flow diagram of a network slice identification assignment method in accordance with one or more embodiments of the present disclosure;
fig. 8 is a flow diagram of a network slice identification assignment method in accordance with one or more embodiments of the present disclosure;
fig. 9 is a flow diagram of a network slice identification assignment methodology in accordance with one or more embodiments of the present disclosure;
fig. 10 is a schematic structural diagram of a network slice identifier distribution system according to one or more embodiments of the present disclosure;
fig. 11 is a flow diagram of a network slice identity assignment method in accordance with one or more embodiments of the present disclosure;
fig. 12 is a schematic structural diagram of a network slice identifier allocation apparatus according to one or more embodiments of the present disclosure;
fig. 13 is a schematic structural diagram of an electronic device according to one or more embodiments of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
Fig. 1 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, as shown in fig. 1, the method includes:
step S102: acquiring a service request for accessing a target service area;
optionally, the service request is used to request access to a target service area, and the target service area may be provided as a geographical area.
Step S104: determining a target TAC corresponding to the target service area;
optionally, the target service area may be mapped to a group of base stations or cell IDs, so that the target TAC may be mapped according to the base station ID or the cell ID, and thus, the allocated network slice identifier performs slice configuration on the base station ID or the cell ID of the service access service area, and slice access area limitation may be implemented.
Optionally, after the target TAC corresponding to the target service area is determined, a resource checking module may be further called to initiate resource checking, and checking may be performed according to necessary service provisioning conditions, for example, whether a related base station meets a requirement for wireless bearer resource reservation of the service, whether a requirement for slice ID configuration number is met, whether an air interface scheduling guarantee requirement of the service is met, and the following step S106 is executed after the resource checking is passed.
Step S106: if the target TAC comprises a single TAC, a network slice identifier used by a single tracking area service is allocated to the target TAC, and if the target TAC at least comprises two TACs, a network slice identifier used by a cross-tracking area service is allocated to the target TAC, wherein in the network slice identifiers used by the single tracking area service, the same network slice identifier is repeatedly used in different TACs.
Optionally, if a terminal allowed by one service is within a certain tracking area, it may be called a single tracking area service; conversely, if a service allows a terminal to access a range, which involves two or more tracking areas, it may be referred to as a cross-tracking-area service. If the target TAC comprises a single TAC, the current service is a single tracking area service, on the basis, a network slice identifier used by the single tracking area service is allocated to the target TAC, and if the target TAC comprises at least two TACs, a network slice identifier used by a cross-tracking area service is allocated to the target TAC.
According to the network slice identifier allocation method, after the corresponding target TAC is determined according to the acquired service request, the network slice identifier is allocated to the target TAC according to the single tracking area service and the cross-tracking area service, and the network slice identifier used by the single tracking area service can be reused in different tracking areas, so that the use of the network slice identifier can be reduced when the terminal access area is limited through slicing.
The network slice identifier allocation method of the embodiment of the disclosure adopts a mode of combining slice access area limitation and PCF signed tracking area access control strategies, and can realize fine control of the terminal service access area range. By allocating different network slice identifiers to services with overlapped PCF signed tracking areas (such as the cross-tracking area services), and multiplexing slice IDs among services with non-overlapped PCF signed tracking areas (such as the single tracking area services), the problems that the consumption of the number of service slice IDs is large due to the fact that access areas are limited based on slices and the control of refined access areas cannot be achieved based on the access control strategy of the PCF signed tracking areas are solved.
Fig. 2 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, and as shown in fig. 2, the method may further include, on the basis of the method shown in fig. 1:
step S202: respectively maintaining an unallocated network slice identifier list for a single tracking area service and a cross-tracking area service, wherein a network slice identifier used by the unallocated single tracking area service of each tracking area is recorded in the unallocated network slice identifier list of the single tracking area service, and a network slice identifier used by the unallocated cross-tracking area service is recorded in the unallocated network slice identifier list of the cross-tracking area service;
if the target TAC includes a single TAC, allocating a network slice identifier used by a single tracking area service to the target TAC, and if the target TAC includes at least two TACs, allocating a network slice identifier used by a cross-tracking area service to the target TAC, which may include:
step S2062: if the target TAC comprises a single TAC, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to a single tracking area service;
step S2064: and if the target TAC at least comprises two TACs, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to the cross-tracking area service.
Alternatively, the allocation of the network slice identity for the target TAC may be performed based on a slice identity allocation module. Exemplarily, fig. 3 is a schematic diagram of a slice identifier assignment module according to an embodiment of the present disclosure, and as shown in fig. 3, a slice identifier P used by a single TAC is included in an unassigned network slice identifier list corresponding to a single tracking area serviceM：X1、X2、X3、X4…XMThe distribution can be repeated in TAC1, TAC2, TAC3 and TAC4 …, wherein the slice identifier marked as 'divided' indicates that the slice identifier marked as 'divided' has been distributed, and the slice identifier marked as 'divided' indicates that the slice identifier marked as 'divided' has not been distributed; cross TAC usage in an unassigned network slice identity list corresponding to cross tracking area servicesSlice identification P ofN：Y1、Y2、Y3、Y4…YNThen no duplicates can be assigned and, as such, a slice identification identified as "divided" indicates that it has already been assigned and a slice identification identified as "not divided" does not yet have been assigned.
By maintaining the unallocated network slice identifier lists for the single tracking area service and the cross-tracking area service respectively, the unallocated network slice identifiers can be conveniently and quickly selected from the corresponding unallocated network slice identifier lists according to the type of the current TAC service when the network slice identifiers are allocated for the tracking areas, and the allocation efficiency of the network slice identifiers is improved.
In addition, since the services are single tracking area services in most scenes, the number of required network slice identifiers can be greatly saved by multiplexing the network slice identifiers in the single tracking area, and the network slice identifiers are not multiplexed in the cross-tracking area scenes, so that excessive consumption of the network slice identifiers is avoided. The method of the embodiment of the disclosure is simple to implement, and does not need to add complex network slice identifier selection logic.
Fig. 4 is a flowchart illustrating a network slice identifier allocation method according to one or more embodiments of the present disclosure, where as shown in fig. 4, the method may further include, on the basis of the method shown in fig. 1:
step S402: and if the target TAC comprises a single TAC and the unallocated network slice identifier list corresponding to the single tracking area service does not contain the network slice identifier used by the unallocated single tracking area service, selecting the network slice identifier allocated to the target TAC from the unallocated network slice identifier list corresponding to the cross-tracking area service. Based on this it can be ensured that the current service request is effectively responded to.
Fig. 5 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, and as shown in fig. 5, the method may further include, on the basis of the method shown in fig. 1:
step S502: a list of assigned network slice identities is maintained for single tracking area traffic and cross-tracking area traffic, respectively. Still taking the example shown in fig. 2, the network slice identifier identified as "divided" is the assigned network slice identifier. The distributed network slice identification lists are maintained for the single tracking area service and the cross-tracking area service respectively, so that the distributed network slice identification can be effectively recorded, the problem that the same network slice identification is repeatedly distributed when the network slice identification is subsequently distributed can be solved, and the distribution efficiency of the network slice identification is improved.
Fig. 6 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, and as shown in fig. 6, the method may further include, on the basis of the method shown in fig. 1:
step S602: after the target TAC is allocated with the network slice identifier, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service, or updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross-tracking area service. If the currently allocated network slice identifier is the network slice identifier used by the single tracking area service, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service; and if the currently allocated network slice identifier is the network slice identifier used by the cross-tracking area service, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross-tracking area service. After the network slice identifier is allocated to the TAC each time, the allocated network slice identifier and the unallocated network slice identifier corresponding to the single tracking area service are updated in time, so that a data basis is provided for allocating the network slice identifier to the TAC next time.
Fig. 7 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, and as shown in fig. 7, the method may further include, on the basis of the method shown in fig. 1:
step S702: and maintaining a used network slice identifier list, wherein the used network slice identifier list records the network slice identifiers which are used before the network slice identifier allocation is carried out.
The used network slice identifier may have been configured in other tracking areas, so that maintaining a list of used network slice identifiers in the service order system can effectively avoid the network slice identifiers from being repeatedly allocated.
Fig. 8 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, and as shown in fig. 8, the method may further include, on the basis of the method shown in fig. 1:
step S802: after the target TAC is allocated with the network slice identifier, determining whether the network slice identifier allocated to the target TAC is used according to the used network slice identifier list;
step S804: if the network slice identifier allocated to the target TAC is used, carrying out capacity expansion configuration on a network slice access area;
optionally, if the network slice identifier allocated to the target TAC is used, the service order system may transmit the network slice identifier allocated to the target TAC and the related service parameters to the arrangement control module, so as to initiate capacity expansion configuration of the slice access area, and bring the base station identifier or the cell identifier corresponding to the service access area into the slice access area.
Step S806: and if the network slice identifier allocated to the target TAC is not used, performing network slice end-to-end configuration.
Optionally, if the network slice identifier allocated to the target TAC is not used, the service order system may transmit the network slice identifier allocated to the target TAC and the related service parameters to the orchestration control module, initiate an end-to-end new slice configuration flow, and update the used network slice identifier list after the slice configuration is completed.
Fig. 9 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, and as shown in fig. 9, determining a target tracking area code TAC corresponding to the target service area may include:
step S2022: acquiring the information of the circled geographical area;
optionally, when the service order System accepts the service request, the service area location management module may be called to provide a Geographic Information System (GIS) map visualization selection interface, such as a GIS map. Based on this, an access service area (which is one example of the above-described target service area) can be specified by circling the regional area on the GIS map.
Step S2024: determining a base station ID or a cell ID corresponding to the target service area according to the circled geographical area information;
step S2026: and determining the target TAC according to the base station ID or the cell ID.
Optionally, the target TAC is mapped according to the circled geographical area and a group of base station IDs or cell IDs. Therefore, the distributed network slice identifier is subjected to slice configuration on the service access service area base station ID/cell ID, and slice access area limitation is realized.
Optionally, the user may also manually input the base station ID or the cell ID, or define a mapping relationship between the geographic location description and the base station ID or the cell ID in advance, and map the base station ID or the cell ID according to the location description.
Fig. 10 is a schematic structural diagram of a network slice identifier distribution system according to one or more embodiments of the present disclosure, as shown in fig. 10, the system mainly includes a service order system 1012, a service zone location management module 1014, a resource check module 1016, a slice ID distribution module 1018, an orchestration control module 1020, a 5G core network element 1022, and the like, where the 5G core network element may include: AMF (Access and Mobility Management Function), SMF (Session Management Function), UPF (User Plane Function), UDM (Unified Data Management Function), and PCF. The system combines the access control strategy based on slice access area limitation and PCF signed tracking area to realize the fine control of the terminal service access area range.
Partitioning network slice identities into single tracking area usage slice identity groups PMAnd using slice identification group P across tracking areasNTwo groups, denoted PM＝{X1，X2，…，XM}，PN＝{Y1，Y2，…，YNAre multiplied by
M + N is less than or equal to the maximum network slice identification number allowed to be configured by the base station.
Network slice identification is not reused among all cross-tracking area services, and a slice identification group P is used in the cross-tracking area no matter whether the areas of the cross-tracking area services are overlapped or notNAnd distributing network slice identification.
The slice ID distribution module respectively maintains a slice ID distribution table for the single tracking area service and the cross-tracking area service:
for single tracking area services: establishing a distributed network slice identification list and an unallocated network slice identification list for each tracking area, which are respectively marked as PTACiHas already been divided and PTACi undividedWherein i represents the i-th TAC, wherein PTACi has been classified into∪PTACi undivided＝PM，
For cross-tracking area traffic: establishing a distributed network slice identification list and an unallocated network slice identification list which are respectively marked as PN is already divided intoAnd PN is not divided intoIn which P isN is already divided into∪PN is not divided into＝PN，
When a service order system accepts a service request, the capacity of a service area position management module is called, a GIS map visual selection interface is provided, an access service area is mapped into a group of base station ID/cell ID, TAC is mapped according to the base station ID/cell ID, and a resource checking module is called to initiate resource checking.
After the resource check is passed, the business order system obtains TAC according to the base station ID/cell ID mapping, and requests a slice ID distribution module to distribute corresponding slice identifiers:
if the access is in the single tracking area, requesting to allocate the service of the single tracking area to use the network slice identifier to a slice ID allocation module according to the TAC, and receiving the request by the slice ID allocation module and then allocating the service of the single tracking area to the P corresponding to the TACTACi undividedSelecting a slice ID, feeding back to the service order system, and updating PTACi undividedAnd PTACi has been classified intoAnd (4) listing. In this step, e.g. of the corresponding TAC
Service can optionally be rejected or slave PN is not divided intoOne slice ID assignment is selected.
If the access is the cross-tracking area access, requesting the slice ID distribution module to distribute the cross-tracking area network slice identifier, and receiving the request by the slice ID distribution module, and then sending the request from the PN is not divided intoSelecting a slice ID, feeding back to the service order system, and updating PN is not divided intoAnd PN is already divided intoAnd (4) listing.
The business order system maintains a used slice ID table PHas been usedAfter the slice ID is acquired from the slice ID allocation module, the service order system first performs slice repeat judgment: if it is
(in the formula, P' already represents the used slice ID table before the current slice allocation), that is, the current acquired slice ID is the used slice ID (other services are already configured in other tracking areas), the service order system transmits the slice ID and the relevant service parameters to the arrangement control module, initiates capacity expansion configuration of the slice access area, and brings the base station ID/cell ID corresponding to the service access area into the slice access area; if it is
Then representing that the acquired slice ID is an unused slice ID, the service order system transmits the slice ID and related service parameters to the arranging control module,initiating end-to-end new slice configuration flow, and updating the used slice ID table after the slice configuration is completed to ensure that P is in a state of being in a state of being in a state ofHas been used＝P' used alreadyU { obtains slice ID }.
In the slice configuration process, the arranging control module transmits the TAC corresponding to the service access area to the PCF network element, and the PCF network element completes the creation of the service terminal access tracking area according to the TAC. And the TAC mapped based on the base station ID/cell ID is subjected to PCF user access control strategy configuration, so that the restriction of the terminal access tracking area can be realized. The creating of the service terminal admission tracking area may include: configuring a service area; configuring out-of-service area usage rules (blocking); configuring a strategy, and associating rules and trigger conditions; configuring packages, associating policies, and the like.
When a service initiates a terminal number subscription service (which may include associated service slice and DNN, and completes related policy reference through subscription configuration) request, a service order system issues subscription information to an orchestration control module, the orchestration control module completes basic session subscription configuration at a UDM network element, and completes service terminal access tracking area access control policy reference at a PCF. A configuration instruction can be generated in the PCF network element, and the terminal number refers to the above-mentioned configured policy.
Fig. 11 is a flowchart of a network slice identifier allocation method according to one or more embodiments of the present disclosure, which may be implemented based on the network slice identifier allocation system shown in fig. 10, as shown in fig. 11, and the method includes:
step S1101: inputting the service order system according to the service fulfillment requirement of the special slicing line;
the requirement for activating the slicing dedicated line service may include: the equipment installation addresses at two ends of the private line, the access mode of the private line, the service reliability requirement, the private line bandwidth requirement, the bandwidth guarantee requirement of the 5G terminal, the air interface 5QI scheduling requirement and the like.
Step S1102: the service order system calls the GIS circling and selecting capability;
step S1103: the service area position management module feeds back the service area obtained according to the circled mapping to the service order system;
step S1104: the service order system requests a resource checking module for resource checking;
step S1105: the resource checking module returns a resource checking result to the service order system;
step S1106: the service order system requests a slice ID distribution module to distribute the service slice ID;
step S1107: the slice ID distribution module feeds back a slice ID to the business order system;
step S1108: the service order system judges the slice ID again, if the slice ID is used, the capacity expansion of a slice access area is carried out, and if the slice ID is not used, the end-to-end configuration of the slice is carried out;
step S1109: the business order system sends a slice special line business configuration request to the arranging control module;
step S1110: the arrangement control module sends a network element configuration instruction to a 5G core network element;
step S1111: the arranging control module returns the slice special line service configuration result to the service order system;
step S1112: a service order system receives terminal number signing demand input;
step S1113: the service order system issues a terminal number signing configuration requirement to the arranging control module;
step S1114: the arrangement control module sends a network element configuration instruction to a 5G core network element;
step S1115: and the arrangement control module returns a terminal number signing configuration result to the service order system.
Fig. 12 is a schematic structural diagram illustrating a network slice identifier allocating apparatus according to one or more embodiments of the present disclosure, and as shown in fig. 12, the apparatus 1210 includes:
an obtaining module 1212, configured to obtain a service request for accessing a target service area;
a first determining module 1214, configured to determine a target tracking area code TAC corresponding to the target service area;
an allocating module 1216, configured to allocate, if the target TAC includes a single TAC, a network slice identifier used by a single tracking area service to the target TAC, and if the target TAC includes at least two TACs, allocate, to the target TAC, a network slice identifier used by a cross-tracking area service, where, in the network slice identifiers used by the single tracking area service, the same network slice identifier is reused in different TACs.
In one or more embodiments of the present disclosure, the network slice identification allocation apparatus may further include:
the system comprises a first maintenance module, a second maintenance module and a third maintenance module, wherein the first maintenance module is used for respectively maintaining an unallocated network slice identifier list for a single tracking area service and a cross-service TAC service, wherein a network slice identifier used by the unallocated single tracking area service is recorded in the unallocated network slice identifier list of the single tracking area service, and a network slice identifier used by the unallocated cross-tracking area service is recorded in the unallocated network slice identifier list of the cross-tracking area service;
the allocation module is specifically configured to: if the target TAC comprises a single TAC, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to a single tracking area service; and if the target TAC comprises at least two TACs, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to the cross-tracking area service.
In one or more embodiments of the present disclosure, the allocation module is specifically configured to:
and if the target TAC comprises a single TAC and the unallocated network slice identifier list corresponding to the single tracking area service does not contain the network slice identifier used by the unallocated single tracking area service, selecting the network slice identifier allocated to the target TAC from the unallocated network slice identifier list corresponding to the cross-tracking area service.
In one or more embodiments of the present disclosure, the network slice identification allocation apparatus may further include:
and the second maintenance module is used for maintaining the allocated slice identifier lists for the single tracking area service and the cross-tracking area service respectively.
In one or more embodiments of the present disclosure, the network slice identification allocation apparatus may further include:
and the updating module is used for updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service or updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross-tracking area service after the network slice identifier is allocated to the target TAC.
In one or more embodiments of the present disclosure, the network slice identification allocation apparatus may further include:
and the third maintenance module is used for maintaining a used network slice identifier list, and the used network slice identifier list records the network slice identifiers which are used before the network slice identifier allocation is carried out.
In one or more embodiments of the present disclosure, the network slice identification allocation apparatus may further include:
a second determining module, configured to determine, according to the used slice identifier list, whether a network slice identifier allocated to the target TAC is used after the network slice identifier is allocated to the target TAC;
the first configuration module is used for carrying out capacity expansion configuration on a network slice access area if the network slice identifier allocated to the target TAC is used;
and the second configuration module is used for carrying out end-to-end configuration on the network slice if the network slice identifier allocated to the target TAC is not used.
In one or more embodiments of the present disclosure, the first determining module is specifically operable to:
acquiring information of the circled geographical area;
determining a base station identifier or a cell identifier corresponding to the target service area according to the circled geographical area information;
and determining the target TAC according to the base station identifier or the cell identifier.
One or more embodiments of the present disclosure also provide an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the network slice identifier allocation methods provided by the embodiments of the present disclosure via executing the executable instructions.
One or more embodiments of the present disclosure also provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements any one of the network slice identifier allocation methods provided by the embodiments of the present disclosure.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 1300 according to this embodiment of the invention is described below with reference to fig. 13. The electronic device 1300 shown in fig. 13 is only an example and should not bring any limitations to the function and scope of use of the embodiments of the present invention.
As shown in fig. 13, the electronic device 1300 is in the form of a general purpose computing device. The components of the electronic device 1300 may include, but are not limited to: the at least one processing unit 1310, the at least one memory unit 1320, and the bus 1330 connecting the various system components including the memory unit 1320 and the processing unit 1310.
Wherein the memory unit stores program code that is executable by the processing unit 1310 to cause the processing unit 1310 to perform steps according to various exemplary embodiments of the present invention as described in the "exemplary methods" section above in this specification. For example, the processing unit 1310 may execute S102 shown in fig. 1, and obtain a service request for accessing a target service area; s104, determining a target TAC corresponding to the target service area; s106, if the target TAC comprises a single TAC, a network slice identifier used by a single tracking area service is allocated to the target TAC, and if the target TAC comprises at least two TACs, a network slice identifier used by a cross-tracking area service is allocated to the target TAC, wherein the network slice identifier used by the single tracking area service is included in the network slice identifiers used by the single tracking area service.
The storage 1320 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)13201 and/or a cache memory unit 13202, and may further include a read-only memory unit (ROM) 13203.
The electronic device 1300 may also communicate with one or more external devices 1400 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 1300, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 1300 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 1350. Also, the electronic device 1300 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) through the network adapter 1360. As shown, the network adapter 1360 communicates with other modules of the electronic device 1300 via the bus 1330. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with the electronic device 1300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
A program product for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage 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 program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, 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 fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (11)
1. A method for allocating network slice identifiers, comprising:
acquiring a service request for accessing a target service area;
determining a target tracking area code TAC corresponding to the target service area;
if the target TAC comprises a single TAC, a network slice identifier used by a single tracking area service is allocated to the target TAC, and if the target TAC at least comprises two TACs, a network slice identifier used by a cross-tracking area service is allocated to the target TAC, wherein in the network slice identifiers used by the single tracking area service, the same network slice identifier is repeatedly used in different TACs.
2. The method of claim 1, further comprising:
respectively maintaining an unallocated network slice identifier list for a single tracking area service and a cross-tracking area service, wherein a network slice identifier used by the unallocated single tracking area service is recorded in the unallocated network slice identifier list of the single tracking area service, and a network slice identifier used by the unallocated cross-tracking area service is recorded in the unallocated network slice identifier list of the cross-tracking area service;
if the target TAC comprises a single TAC, a network slice identifier used by a single tracking area service is allocated to the target TAC, and if the target TAC comprises at least two TACs, a network slice identifier used by a cross-tracking area service is allocated to the target TAC, wherein the method comprises the following steps:
if the target TAC comprises a single TAC, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to a single tracking area service;
and if the target TAC at least comprises two TACs, selecting a network slice identifier allocated to the target TAC from an unallocated network slice identifier list corresponding to the cross-tracking area service.
3. The method of claim 2, further comprising:
and if the target TAC comprises a single TAC and the unallocated network slice identifier list corresponding to the single tracking area service does not contain the network slice identifier used by the unallocated single tracking area service, selecting the network slice identifier allocated to the target TAC from the unallocated network slice identifier list corresponding to the cross-tracking area service.
4. The method of claim 2, further comprising:
a list of assigned slice identities is maintained for single tracking area traffic and cross-tracking area traffic, respectively.
5. The method of claim 4, further comprising:
after the target TAC is allocated with the network slice identifier, updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the single tracking area service, or updating an allocated network slice identifier list and an unallocated network slice identifier list corresponding to the cross-tracking area service.
6. The method of claim 1, further comprising:
maintaining a used network slice identifier list, wherein the used network slice identifier list records a network slice identifier that has been used before the network slice identifier is allocated.
7. The method of claim 6, further comprising:
after the target TAC is allocated with the network slice identifier, determining whether the network slice identifier allocated to the target TAC is used according to the used slice identifier list;
if the network slice identifier allocated to the target TAC is used, carrying out capacity expansion configuration on a network slice access area;
and if the network slice identifier allocated to the target TAC is not used, performing network slice end-to-end configuration.
8. The method according to any one of claims 1 to 7, wherein determining the target tracking area code TAC corresponding to the target service area comprises:
acquiring the information of the circled geographical area;
determining a base station identifier or a cell identifier corresponding to the target service area according to the circled geographical area information;
and determining the target TAC according to the base station identifier or the cell identifier.
9. A network slice identifier assignment device, comprising:
the acquisition module is used for acquiring a service request for accessing a target service area;
a first determining module, configured to determine a target tracking area code TAC corresponding to the target service area;
and the allocation module is used for allocating a network slice identifier used by a single tracking area service to the target TAC if the target TAC comprises a single TAC, and allocating a network slice identifier used by a cross-tracking area service to the target TAC if the target TAC comprises at least two TACs, wherein in the network slice identifiers used by the single tracking area service, the same network slice identifier is repeatedly used in different TACs.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the network slice identity assignment method of any of claims 1-8 via execution of the executable instructions.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the network slice identity assignment method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111665480.XA CN114338404B (en) | 2021-12-31 | 2021-12-31 | Network slice identifier distribution method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111665480.XA CN114338404B (en) | 2021-12-31 | 2021-12-31 | Network slice identifier distribution method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114338404A true CN114338404A (en) | 2022-04-12 |
| CN114338404B CN114338404B (en) | 2024-08-06 |
Family
ID=81020620
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111665480.XA Active CN114338404B (en) | 2021-12-31 | 2021-12-31 | Network slice identifier distribution method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114338404B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116170303A (en) * | 2022-12-02 | 2023-05-26 | 中国联合网络通信集团有限公司 | Data configuration method, device, server and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109429274A (en) * | 2017-09-04 | 2019-03-05 | 华为技术有限公司 | A kind of configuration method and corresponding intrument |
| CN111586667A (en) * | 2019-02-15 | 2020-08-25 | 华为技术有限公司 | Communication method, terminal equipment and core network equipment |
| CN111819887A (en) * | 2018-03-15 | 2020-10-23 | 诺基亚技术有限公司 | Network slice discovery in overlapping network slice deployments |
| US20210392617A1 (en) * | 2020-06-10 | 2021-12-16 | Nokia Technologies Oy | Radio access network notification area (rna) configuration based on service class |
-
2021
- 2021-12-31 CN CN202111665480.XA patent/CN114338404B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109429274A (en) * | 2017-09-04 | 2019-03-05 | 华为技术有限公司 | A kind of configuration method and corresponding intrument |
| CN111819887A (en) * | 2018-03-15 | 2020-10-23 | 诺基亚技术有限公司 | Network slice discovery in overlapping network slice deployments |
| CN111586667A (en) * | 2019-02-15 | 2020-08-25 | 华为技术有限公司 | Communication method, terminal equipment and core network equipment |
| US20210392617A1 (en) * | 2020-06-10 | 2021-12-16 | Nokia Technologies Oy | Radio access network notification area (rna) configuration based on service class |
Non-Patent Citations (1)
| Title |
|---|
| HUAWEI等: ""R2-2104004 Discussion on slice based cell reselection under network control"", 3GPP TSG-RAN WG2 MEETING #113BIS-E ELECTRONIC R2-2104004, 20 April 2021 (2021-04-20) * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116170303A (en) * | 2022-12-02 | 2023-05-26 | 中国联合网络通信集团有限公司 | Data configuration method, device, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114338404B (en) | 2024-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7183416B2 (en) | Time-dependent networking communication method and apparatus | |
| US12113667B2 (en) | Network slice configuration method, apparatus, and system | |
| EP3843440B1 (en) | Network slice selection method and device | |
| US10993127B2 (en) | Network slice instance management method, apparatus, and system | |
| CN111200878B (en) | Information transmission method and device | |
| CN109391490B (en) | Network slice management method and device | |
| JP4995808B2 (en) | Method and apparatus for enhanced content delivery over a data network | |
| CN109600768A (en) | Management method, equipment and the system of network slice | |
| CN109041248A (en) | A kind of car networking resource allocation methods, device, computing device and storage medium | |
| US20140379928A1 (en) | Method for implementing network using distributed virtual switch, apparatus for performing the same, and network system based on distributed virtual switch | |
| WO2016095524A1 (en) | Resource allocation method and apparatus | |
| Chang et al. | Slice orchestration for multi-service disaggregated ultra-dense RANs | |
| KR20090040907A (en) | Centralized radio resource allocation in communication networks | |
| WO2019024671A1 (en) | Method, device and system for deploying network slice | |
| JP2023521398A (en) | Resource determination method and equipment | |
| WO2019029704A1 (en) | Network object management method and apparatus therefor | |
| WO2019100924A1 (en) | Network performance guarantee method and device | |
| CN114338404B (en) | Network slice identifier distribution method and device, storage medium and electronic equipment | |
| WO2021032100A1 (en) | Network element allocation method and apparatus | |
| CN112887074A (en) | Information sending method, device, terminal, access network equipment and system | |
| CN111447077B (en) | Network element configuration method, device and storage medium | |
| CN109076545A (en) | Check the capacity for being used for Multimedia session | |
| CN115002686A (en) | Terminal communication method, device, computer storage medium and electronic equipment | |
| WO2023155720A1 (en) | Method and apparatus for feasibility evaluation | |
| EP4426018A1 (en) | Techniques to reduce energy emission of a service |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |